How is "Core SIG needs to update it's charter" moving along? Any updates?
-Connie Sieh
On 03/18/2014 08:18 PM, Connie Sieh wrote:
How is "Core SIG needs to update it's charter" moving along? Any updates?
The Core SIG is defined as a part of the project governance with a very clear definition on what its required to execute on ( http://www.centos.org/about/governance/sigs/ )
We do however, seem to have an issue with website navigation, the homepage-> About -> SIG's url goes to http://wiki.centos.org/SpecialInterestGroup and not http://www.centos.org/about/governance/sigs/ ( which might be a better target ) and we can link to the wiki using appropriate content from the SIG page on the site. And the Core SIG page on the wiki could potentially be expanded a bit.
The only additional thing that the core sig is working on at the moment, apart from the primary charger, is that the entire infra team overlaps the core sig team ( and that isnt by design, it can easily diverge, as it does in some specific exceptions. eg: website and ipv6 infra ).
Are there any specific questions you have about the charter and what you might like to see being updated / expanded on ?
On Wed, 19 Mar 2014, Karanbir Singh wrote:
On 03/18/2014 08:18 PM, Connie Sieh wrote:
How is "Core SIG needs to update it's charter" moving along? Any updates?
The Core SIG is defined as a part of the project governance with a very clear definition on what its required to execute on ( http://www.centos.org/about/governance/sigs/ )
We do however, seem to have an issue with website navigation, the homepage-> About -> SIG's url goes to http://wiki.centos.org/SpecialInterestGroup and not http://www.centos.org/about/governance/sigs/ ( which might be a better target ) and we can link to the wiki using appropriate content from the SIG page on the site. And the Core SIG page on the wiki could potentially be expanded a bit.
The only additional thing that the core sig is working on at the moment, apart from the primary charger, is that the entire infra team overlaps the core sig team ( and that isnt by design, it can easily diverge, as it does in some specific exceptions. eg: website and ipv6 infra ).
Are there any specific questions you have about the charter and what you might like to see being updated / expanded on ?
On http://www.centos.org/about/governance/sigs/
"Build the CentOS release"
A definition of "CentOS release" is needed.
-Connie Sieh
On 03/19/2014 11:32 AM, Connie Sieh wrote:
On Wed, 19 Mar 2014, Karanbir Singh wrote:
On 03/18/2014 08:18 PM, Connie Sieh wrote:
How is "Core SIG needs to update it's charter" moving along? Any updates?
The Core SIG is defined as a part of the project governance with a very clear definition on what its required to execute on ( http://www.centos.org/about/governance/sigs/ )
We do however, seem to have an issue with website navigation, the homepage-> About -> SIG's url goes to http://wiki.centos.org/SpecialInterestGroup and not http://www.centos.org/about/governance/sigs/ ( which might be a better target ) and we can link to the wiki using appropriate content from the SIG page on the site. And the Core SIG page on the wiki could potentially be expanded a bit.
The only additional thing that the core sig is working on at the moment, apart from the primary charger, is that the entire infra team overlaps the core sig team ( and that isnt by design, it can easily diverge, as it does in some specific exceptions. eg: website and ipv6 infra ).
Are there any specific questions you have about the charter and what you might like to see being updated / expanded on ?
On http://www.centos.org/about/governance/sigs/
"Build the CentOS release"
A definition of "CentOS release" is needed.
-Connie Sieh
The CentOS Linux core OS .. so:
mirror.centos.org/centos/<number>/ directory and all the repos that are complete rebuilds of RHEL code ... so:
SCL cr fasttrack isos os updates
Currently also these directories:
centosplus extras
Although, we could move extras and centosplus to SIG controlled in the future.
Also, we could populate the contrib (c5 and c6) or addon (c5 only right now) repos and they could be sig controlled.
xen4 repo (c6) is already controlled by the xen4centos SIG.
So, the Core team will create what basically what is CentOS right now, its not complicated. We are looking to add SIGs to do things that we are not currently doing and to put the code they create in other repos that are not listed in the 6 that are listed as rebuilds of RHEL code.
On Wed, 19 Mar 2014, Johnny Hughes wrote:
On 03/19/2014 11:32 AM, Connie Sieh wrote:
On Wed, 19 Mar 2014, Karanbir Singh wrote:
On 03/18/2014 08:18 PM, Connie Sieh wrote:
How is "Core SIG needs to update it's charter" moving along? Any updates?
The Core SIG is defined as a part of the project governance with a very clear definition on what its required to execute on ( http://www.centos.org/about/governance/sigs/ )
We do however, seem to have an issue with website navigation, the homepage-> About -> SIG's url goes to http://wiki.centos.org/SpecialInterestGroup and not http://www.centos.org/about/governance/sigs/ ( which might be a better target ) and we can link to the wiki using appropriate content from the SIG page on the site. And the Core SIG page on the wiki could potentially be expanded a bit.
The only additional thing that the core sig is working on at the moment, apart from the primary charger, is that the entire infra team overlaps the core sig team ( and that isnt by design, it can easily diverge, as it does in some specific exceptions. eg: website and ipv6 infra ).
Are there any specific questions you have about the charter and what you might like to see being updated / expanded on ?
On http://www.centos.org/about/governance/sigs/
"Build the CentOS release"
A definition of "CentOS release" is needed.
-Connie Sieh
The CentOS Linux core OS .. so:
mirror.centos.org/centos/<number>/ directory and all the repos that are complete rebuilds of RHEL code ... so:
SCL cr fasttrack isos os updates
Currently also these directories:
centosplus extras
Although, we could move extras and centosplus to SIG controlled in the future.
Also, we could populate the contrib (c5 and c6) or addon (c5 only right now) repos and they could be sig controlled.
xen4 repo (c6) is already controlled by the xen4centos SIG.
So, the Core team will create what basically what is CentOS right now, its not complicated. We are looking to add SIGs to do things that we are not currently doing and to put the code they create in other repos that are not listed in the 6 that are listed as rebuilds of RHEL code.
Just wanted it defined.
Thanks
-connie sieh