[Rdo-list] [RFC] RDO Big Tent projects acceptance guidelines

[Tim Bell]

> -----Original Message-----
> From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com]
> On Behalf Of Haïkel
> Sent: 05 September 2015 22:26
> To: rdo-list at redhat.com
> Subject: [Rdo-list] [RFC] RDO Big Tent projects acceptance guidelines
> 
> Hi,
> 
> RDO is growing, and with upstream Big Tent initiative, many people offered
> to integrate more projects into RDO.
> 
> As a truly open community, we need to set proper guidelines to define
which
> projects should be accepted or not in RDO.
> Below, you'll find a draft for such guidelines, and I would like to
receive your
> feedback
> 
> Projects have to
> 1. be part of the OpenStack upstream ecosysem (e.g licenses) 2. have an
> identified downstream maintainer
> 
> Maintainers have to
> 1. provides packages that complies with Fedora packaging guidelines minus
> exceptions granted by the RDO team [1] 2. commit to fix tickets reported
on
> RDO bug tracker 3. fix FTBFS[2] in stable and master branches 4. commit to
> integrate and maintain their project in RDO CI 5. agree to license
packaging
> under the MIT license (default) or any approved license by Fedora Legal.
> 

To understand the requirement 2, does this mean fixing tickets related to
the packaging or tickets related to the upstream project ? CERN are
certainly interested in contributing our packaging of some components not
yet in RDO (such as the ec2-api and Murano packages we're already working
on), but there would be concerns if we take on commitments for the upstream
project rather than just the package maintenance.

One other requirement that is more specific to OpenStack than to Fedora is
the maintenance of packages for newer versions of OpenStack. At what stage
during the lifecycle of a release such as Liberty would it be expected that
packages be updated ? And for how many older releases would it be expected
to be maintained ?

> As long as all these conditions are respected, any project is welcome
under
> RDO :)
> 
> If everyone agrees, we will publish these guidelines on our website.
> 
> Regards,
> H.
> 
> [1] RDO team to be understood as the community behind the maintenance
> of RDO, not RDO Engineering which is an internal team from Red Hat.
> [2] Fail to Build From Source
> 
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
> 
> To unsubscribe: rdo-list-unsubscribe at redhat.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7349 bytes
Desc: not available
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20150906/088d7fed/attachment.p7s>