Thank you! I have a couple other people who have expressed interest, so I will send an email to all of you about the next steps (location of the repo, etc, those sorts of logistics).
Thanks, On 4/9/24 18:47, Priscila Gutierres wrote: > Hello David, > > I would like to contribute. Will be an excellent learning opportunity. > > Priscila. > > On Tue, Apr 9, 2024 at 6:14 PM Kevin Fenzi <ke...@scrye.com > <mailto:ke...@scrye.com>> wrote: > > On Tue, Apr 09, 2024 at 01:55:41PM -0400, David Cantrell wrote: > > Hello all, > > > > I am looking for multiple people to help be upstream stewards of the > rpminspect-data-fedora project. This is a project that contains config files > and rules for running rpminspect on Fedora builds. It is a package > containing distribution policy. It needs people to look over it and review > and merge contributions from other developers, do occassional releases, and > ensure that it is updated as new releases of Fedora are started (and we get > new dist tags). > > > > The project currently lives here: > > > > https://github.com/rpminspect/rpminspect-data-fedora > <https://github.com/rpminspect/rpminspect-data-fedora> > > > > But absolutely can move depending on the desires of the individuals who > take over maintenance. I created these rules files in the data package for > rpminspect so that different vendors can customize how rpminspect runs and > reacts to findings. Maintenance of the rules is independent of the software > maintenance. > > > > If you are interested, please email me directly and we can get going on > the logistics. If you have general questions, feel free to ask here. > > I wonder if this isn't something we should have the QE or releng teams > manage... ie, adding new branch info (releng), adjusting tests (qe)? > > kevin > -- > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > <mailto:devel@lists.fedoraproject.org> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > <mailto:devel-le...@lists.fedoraproject.org> > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > <https://fedoraproject.org/wiki/Mailing_list_guidelines> > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > <https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org> > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > <https://pagure.io/fedora-infrastructure/new_issue> > > > -- > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- David Cantrell <dcantr...@redhat.com> Red Hat, Inc. | Boston, MA | EST5EDT -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
