At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
1) EPEL.next (EPIC or EPEL-rolling, etc) 2) Formalizing various amounts of unwritten rules for package addition, removal and maintenance in current repos. 3) Lower workload on Kevin Fenzi and Dennis Gilmore as they have been EPEL since the last EPSCO was around.
At that meeting the following people were nominated to the committee:
Dennis Gilmore Kevin Fenzi Stephen Smoogen Jim Perrin
Todays (2014-08-29) meeting this was 'formalized' with people attending the meeting. Added to that was a beginning proposal of committee governance:
The governance structure will be a short term organization to set up policies and procedues in place for continual maintenance of EPEL. The term of the committee will end 3 months after either new repos are setup or voted not going to happen by said committee. If a longer term running committee is required, the previous board will set up policies for elections and term lengths before the short term committee ends.
After the meeting I realized that wasn't a good deadline so would like to alter it these changes should be completed by the Fedora 22 release date.
Working Motto: We put the SCO in Enterprise Linux
Hi
On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote:
At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
- EPEL.next (EPIC or EPEL-rolling, etc)
Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories
Rahul
On 29 August 2014 15:03, Rahul Sundaram metherid@gmail.com wrote:
Hi
On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote:
At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
- EPEL.next (EPIC or EPEL-rolling, etc)
Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories
Not yet. It is a good idea to bring up at this point. Are there any IUS people on the list already? Or do you know people we should contact? [The IUS lists I am on are very very quiet so I am not sure who that would be these days.]
Hi
On Fri, Aug 29, 2014 at 5:12 PM, Stephen John Smoogen smooge@gmail.com wrote:
On 29 August 2014 15:03, Rahul Sundaram metherid@gmail.com wrote:
Hi
On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote:
At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
- EPEL.next (EPIC or EPEL-rolling, etc)
Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories
Not yet. It is a good idea to bring up at this point. Are there any IUS people on the list already? Or do you know people we should contact? [The IUS lists I am on are very very quiet so I am not sure who that would be these days.]
I am adding their contact email in CC
Rahul
Howdy!
Currently the ius-release package depends on epel-release. This is because several of our packages have dependencies from EPEL. Would these new proposed repos be supplementary to the current EPEL, or something else?
Here are the current IUS mailing lists.
Core developers: coredev@iuscommunity.org ius-coredev@lists.launchpad.net
Community members: ius-community@lists.launchpad.net
Carl George Rackspace GNU/Linux Engineer ________________________________ From: Rahul Sundaram [metherid@gmail.com] Sent: Friday, August 29, 2014 07:38 PM To: EPEL Development List Cc: coredev@iuscommunity.org Subject: Re: EPEL Reformed Steering Committee
Hi
On Fri, Aug 29, 2014 at 5:12 PM, Stephen John Smoogen <smooge@gmail.commailto:smooge@gmail.com> wrote:
On 29 August 2014 15:03, Rahul Sundaram <metherid@gmail.commailto:metherid@gmail.com> wrote: Hi
On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote: At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
1) EPEL.next (EPIC or EPEL-rolling, etc)
Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories
Not yet. It is a good idea to bring up at this point. Are there any IUS people on the list already? Or do you know people we should contact? [The IUS lists I am on are very very quiet so I am not sure who that would be these days.]
I am adding their contact email in CC
Rahul
On 08/29/2014 08:32 PM, Carl George wrote:
Howdy!
Currently the ius-release package depends on epel-release. This is because several of our packages have dependencies from EPEL. Would these new proposed repos be supplementary to the current EPEL, or something else?
Correct. EPEL currently has a large user-base, and some basic expectation for how it should function. Changing that would do more harm than good.
These repositories would be in addition to the existing EPEL structure.
Here are the current IUS mailing lists.
Core developers: coredev@iuscommunity.org ius-coredev@lists.launchpad.net
Community members: ius-community@lists.launchpad.net
Carl George Rackspace GNU/Linux Engineer ________________________________ From: Rahul Sundaram [metherid@gmail.com] Sent: Friday, August 29, 2014 07:38 PM To: EPEL Development List Cc: coredev@iuscommunity.org Subject: Re: EPEL Reformed Steering Committee
Hi
On Fri, Aug 29, 2014 at 5:12 PM, Stephen John Smoogen <smooge@gmail.commailto:smooge@gmail.com> wrote:
On 29 August 2014 15:03, Rahul Sundaram <metherid@gmail.commailto:metherid@gmail.com> wrote: Hi
On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote: At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
- EPEL.next (EPIC or EPEL-rolling, etc)
Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories
Not yet. It is a good idea to bring up at this point. Are there any IUS people on the list already? Or do you know people we should contact? [The IUS lists I am on are very very quiet so I am not sure who that would be these days.]
I am adding their contact email in CC
Rahul
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Fri, Aug 29, 2014 at 11:48 AM, Stephen John Smoogen smooge@gmail.com wrote:
At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
- EPEL.next (EPIC or EPEL-rolling, etc)
- Formalizing various amounts of unwritten rules for package addition,
removal and maintenance in current repos. 3) Lower workload on Kevin Fenzi and Dennis Gilmore as they have been EPEL since the last EPSCO was around.
Are EPEL.next and current EPEL going to be steered by the same people?
At that meeting the following people were nominated to the committee:
Dennis Gilmore Kevin Fenzi Stephen Smoogen Jim Perrin
Todays (2014-08-29) meeting this was 'formalized' with people attending the meeting. Added to that was a beginning proposal of committee governance:
Is the meeting time also formalized? I can make this most of the time, but forgot this morning. (Added to calendar now).
The governance structure will be a short term organization to set up policies and procedues in place for continual maintenance of EPEL. The term of the committee will end 3 months after either new repos are setup or voted not going to happen by said committee. If a longer term running committee is required, the previous board will set up policies for elections and term lengths before the short term committee ends.
After the meeting I realized that wasn't a good deadline so would like to alter it these changes should be completed by the Fedora 22 release date.
When is this project release date? On https://fedoraproject.org/wiki/Releases/22/Schedule?rd=Releases/22 I see 2015-XX-XX. That's a lot of leeway.
Working Motto: We put the SCO in Enterprise Linux
Nice
On 29 August 2014 16:15, Michael Stahnke stahnma@puppetlabs.com wrote:
On Fri, Aug 29, 2014 at 11:48 AM, Stephen John Smoogen smooge@gmail.com wrote:
At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items:
- EPEL.next (EPIC or EPEL-rolling, etc)
- Formalizing various amounts of unwritten rules for package addition,
removal and maintenance in current repos. 3) Lower workload on Kevin Fenzi and Dennis Gilmore as they have been EPEL since the last EPSCO was around.
Are EPEL.next and current EPEL going to be steered by the same people?
At the moment yes.
At that meeting the following people were nominated to the committee:
Dennis Gilmore Kevin Fenzi Stephen Smoogen Jim Perrin
Todays (2014-08-29) meeting this was 'formalized' with people attending the meeting. Added to that was a beginning proposal of committee governance:
Is the meeting time also formalized? I can make this most of the time, but forgot this morning. (Added to calendar now).
Yes the meetings will be Friday 1600 UTC in #epel until changed. Any changes will be announced on this list.
The governance structure will be a short term organization to set up policies and procedues in place for continual maintenance of EPEL. The term of the committee will end 3 months after either new repos are setup or voted not going to happen by said committee. If a longer term running committee is required, the previous board will set up policies for elections and term lengths before the short term committee ends.
After the meeting I realized that wasn't a good deadline so would like to alter it these changes should be completed by the Fedora 22 release date.
When is this project release date? On https://fedoraproject.org/wiki/Releases/22/Schedule?rd=Releases/22 I see 2015-XX-XX. That's a lot of leeway.
There is nothing more formal than that. I would expect that it will be 6 months after F21 which I am expecting to be in November/December of 2014 which would put 22 around June 2015. I think that getting all the items done by November/December is hard to meet but by June should be done. The committee can stand down at any time also.
Working Motto: We put the SCO in Enterprise Linux
Nice
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Fri, Aug 29, 2014 at 3:52 PM, Stephen John Smoogen smooge@gmail.com wrote:
On 29 August 2014 16:15, Michael Stahnke stahnma@puppetlabs.com wrote:
The governance structure will be a short term organization to set up policies and procedues in place for continual maintenance of EPEL. The term of the committee will end 3 months after either new repos are setup or voted not going to happen by said committee. If a longer term running committee is required, the previous board will set up policies for elections and term lengths before the short term committee ends.
After the meeting I realized that wasn't a good deadline so would like to alter it these changes should be completed by the Fedora 22 release date.
When is this project release date? On https://fedoraproject.org/wiki/Releases/22/Schedule?rd=Releases/22 I see 2015-XX-XX. That's a lot of leeway.
There is nothing more formal than that. I would expect that it will be 6 months after F21 which I am expecting to be in November/December of 2014 which would put 22 around June 2015. I think that getting all the items done by November/December is hard to meet but by June should be done. The committee can stand down at any time also.
Can we set a concrete date? Ends June 1 2015? That's better IMO than tracking the moving Fedora release date.
-Jeff
epel-devel@lists.fedoraproject.org
-
Carl George -
Jeff Sheltren -
Jim Perrin -
Michael Stahnke -
Rahul Sundaram -
Stephen John Smoogen