Re: EPEL Notes from .next discussion.

2014-08-18 Thread Jeff Sheltren
On Wed, Aug 13, 2014 at 11:04 PM, Michael Stahnke stah...@puppetlabs.com wrote: snip lots of stuff Smooge thanks for the write-up. Great points are being brought up by all parties here. I think I'm +1 on a second repo that moves faster and can be incompatible with the right type of

Re: EPEL Notes from .next discussion.

2014-08-14 Thread Michael Stahnke
snip lots of stuff Smooge thanks for the write-up. Great points are being brought up by all parties here. I think I'm +1 on a second repo that moves faster and can be incompatible with the right type of announce-list. (maybe even put the uri for that list in the .repo file or something). It

Re: EPEL Notes from .next discussion.

2014-08-13 Thread Kevin Fenzi
On Tue, 12 Aug 2014 21:05:07 +0200 Stephen John Smoogen smo...@gmail.com wrote: At FLOCK this year, I did a short workshop on what was labeled EPEL.Next. At that we went over a bit of what EPEL has done in the past, what its current challenges are, and what could be its future. Toshio

Re: EPEL Notes from .next discussion.

2014-08-13 Thread Stephen John Smoogen
On 13 August 2014 06:28, Dennis Gilmore den...@ausil.us wrote: On Wed, 13 Aug 2014 01:25:04 +0200 Stephen John Smoogen smo...@gmail.com wrote: On 12 August 2014 21:56, Dennis Gilmore den...@ausil.us wrote: * Example: When RHEL7.1 comes out we have a 30 day window to get packages

Re: EPEL Notes from .next discussion.

2014-08-13 Thread Jim Perrin
On 08/13/2014 09:23 AM, Kevin Fenzi wrote: On Tue, 12 Aug 2014 21:05:07 +0200 Stephen John Smoogen smo...@gmail.com wrote: At FLOCK this year, I did a short workshop on what was labeled EPEL.Next. At that we went over a bit of what EPEL has done in the past, what its current challenges

EPEL Notes from .next discussion.

2014-08-12 Thread Stephen John Smoogen
At FLOCK this year, I did a short workshop on what was labeled EPEL.Next. At that we went over a bit of what EPEL has done in the past, what its current challenges are, and what could be its future. Toshio Kuratomi was great in capturing what was said at the meeting and EPEL * Extra packages

Re: EPEL Notes from .next discussion.

2014-08-12 Thread Dennis Gilmore
On Tue, 12 Aug 2014 21:05:07 +0200 Stephen John Smoogen smo...@gmail.com wrote: At FLOCK this year, I did a short workshop on what was labeled EPEL.Next. At that we went over a bit of what EPEL has done in the past, what its current challenges are, and what could be its future. Toshio

Re: EPEL Notes from .next discussion.

2014-08-12 Thread Brian Stinson
On Aug 13 01:25, Stephen John Smoogen wrote: I think that would be something with softwarecollections.org as that seems in line with their way of packaging items. I think that for some sorts of packages and libraries it makes sense for that, but I don't know if EPEL would mix and match like

Re: EPEL Notes from .next discussion.

2014-08-12 Thread Stephen John Smoogen
On 12 August 2014 18:52, Brian Stinson bstin...@ksu.edu wrote: I know that this proposal needs a lot more fleshing out, but I think it covers the use cases many users of EPEL need for long term usage of packages. -- Stephen J Smoogen. Were there plans made (at flock or elsewhere)