Supporting other repositories.

[Karsten 'quaid' Wade]

On Fri, Nov 07, 2008 at 11:10:08AM -0700, Stephen John Smoogen wrote:
> Ok loaded term but I was wondering if we could work with spacewalk,
> ipa, ds, etc to support their work by including at least a
> spacewalk-release or similar item. This would allow us to 'test' the
> waters of working closer with the other layered upstreams. Basically
> instead of having to hunt around for every different repository, we
> work with the upstream project ot have a signed release that works
> with the EPEL releases.

I'm the POC in Community Architecture for Fedora Directory Server,
FreeIPA, and Dogtag.  It would be really cool to work more directly
with them on the layered products stuff.  They share a common clued
product manager (Kevin Unthank).  They have a strong interest in
working with us on community development.

Should we invite Kevin and the lead developers for those three
products, plus any other interested team mates, to epel-devel-l to
discuss?

Let's clear out the tough question, which I have not seen addressed.

Part of the original premise (promise?) of EPEL is that it would *not*
replicate Red Hat's layered products.  We sat down with Tim Burke and
Daniel Riek (RHEL engineering and product management) at FUDCon in
Boston, and that was a clear and important point from their end of the
conversation.

How are we planning on addressing that?

For one, I think going to the individual layered products, one at a
time, and working with them on EPEL strategy makes sense.  A bottom-up
approach, otherwise we'll never get to the point of resolving the
actual problems of the setup.

Any other thoughts?

- Karsten
-- 
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/epel-devel-list/attachments/20081107/4b51f37c/attachment.sig>