You received this message because you are subscribed to the Google Groups "GoOSe-Linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to goose-linux...@googlegroups.com.
To post to this group, send email to goose...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
One of the major values of the EL rebuild ecosystem is the ability to interoperate, or the ability to fork from the upstream. This provides purpose in many ways, choice being the most heralded. Since the CentOS community has teamed up with Red Hat to allow for Special Interest Groups to join them, it seems that there might be a bit less of an ecosystem available. The goal of the Interoperability SIG is to ensure that the ability to fork and rebuild still exist.
Our communities already exist outside of the CentOS community purview. They are currently the GoOSe Project and the Ascendos Project. This shared community will serve as a "reference implementation", yet will still be operated and marketed as a product and community separate from CentOS. Consider it something of CentOS "embassy" of sorts.
It would seem that this SIG could be construed as contrary to the goals of the CentOS project. However, we believe there is value added to the CentOS project. We are interested in improving the CentOS community in at least a few ways.
* Providing feedback and collaboration on common issues. Including, but not limited to, reporting bugs, providing patches, discussing packaging techniques, rebuilding variants, QA, ISO building, etc.
* Collaboration on documentation of the rebuild process, rebranding of documentation, providing new documentation, etc.
* Build or maintain tools to ease rebranding of upstream packages as to ease adoption by companies who build upon and release software based on CentOS.
* Providing tools to help monitor statuses of builds, repositories, releases, etc. Whether they be part of the CentOS community or otherwise.
With these goals in mind, we'd like to formally request an Interoperability Special Interest Group within the CentOS community. Please let us know how to further proceed.
Lead Developer, GoOSe project
On 01/28/2014 09:46 PM, Clint Savage wrote:
> With these goals in mind, we'd like to formally request an
> Interoperability Special Interest Group within the CentOS community.
> Please let us know how to further proceed.
Couple of comments here, consider the in abstract:
1) everything you mentioned here, we already do and will only increase
2) with the actual instance metadata in the public ( and on github! ) -
there is very little cross-checking needed, since the result of the
scripts is what gets published anyway ( and git log will history for
anyone who cares ).
3) given the intention and direction for some of the points, duplicating
effort also means diluting the single tooling effort - then at that
point why would you not want to just contribute ( as people, not as
projects ) into the common pool anyway ? ( ie. whats the justification
for Goose to exist ? )
finally, not sure what makes this into a SIG, the content being
addressed would be all in the public on git repos, so anyone can come
along and 'help get better'.