On Tue, Feb 12, 2019 at 12:15 PM Fabio Valentini <decatho...@gmail.com> wrote:
> On Tue, Feb 12, 2019 at 12:09 PM Adam Samalik <asama...@redhat.com> wrote: > > > > The Modularity Team works on enabling default modules to be present in > the traditional buildroot. The work is tracked here: > https://tree.taiga.io/project/modularity-wg/epic/12 > > > > We would love to contributions towards that. I'm willing to mentor > anyone interested regarding Modularity. However, we might be quite close > now. And I believe this example raises the priority quite a bit, right? (cc > Stephen & Petr) > > The difference being: I'm suggesting something that can definitely be > done now (maybe even today), and not about "maybe soon"s. > > I don't want to sound disrespectful, and I see that a lot of work is > being poured into the Modularity effort. > However, I don't want to see fedora broken as a result of unfinished > solutions, where there's not even a visible agreement on the way > forward. > Ah, I haven't taken that as a disrespectful or anything! :-) Actually, thanks for stepping up and offering help. Definitely agree that this might be a much faster temporary workaround before the proper fix comes. I just wanted to make sure that people understand that it's something we're working on. > Fabio > > > On Tue, Feb 12, 2019 at 11:56 AM Fabio Valentini <decatho...@gmail.com> > wrote: > >> > >> Hi everybody, > >> > >> In the past few weeks, it has come up regularly that future > >> "module-only" packages are orphaned (and hence will soon be retired), > >> and nobody stepped up to fix this issue - especially for non-leaf > >> packages. I don't think fedora as a project has a solution for this > >> yet. > >> > >> I propose to create a "Stewardship" Group / SIG that will take care of > >> such packages - either until a new main maintainer steps up, or until > >> modularity matures enough so it won't be necessary anymore. (Or, until > >> it dies a quiet death, which is always a possibility.) However, I > >> think this is necessary until the situation stabilizes. > >> > >> Comments and future contributors are very welcome. > >> > >> Fabio > >> _______________________________________________ > >> devel mailing list -- devel@lists.fedoraproject.org > >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org > >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > >> List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > > > > > -- > > > > Adam Šamalík > > --------------------------- > > Software Engineer > > Red Hat > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Adam Šamalík --------------------------- Software Engineer Red Hat
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
