Re: Summary/Minutes from today's FESCo Meeting (2020-11-11)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm opposed to this change as well, due to, imo, making it harder/less obvious/more confusing to see
where I have to pull from any given package that I want to consume as an end-user on my system,
or as a package maintainer in my buildroot.

I've however found myself having to maintain packages that I only needed as builddeps
for the packages that I really care about. So that's definitely not ideal, however:

I like the notion of a 'metadata-based' approach, where labels are added to packages
(or rather, their respective dist-git repos) that potentially fall under the 'lightly maintained' category.

These labels could be processed by the distro internally and acted upon accordingly in some way,
but I certainly don't want that maintenance status to manifest in the package being made available
in one repo or the other (and even potentially moving from one to the other between releases per
changes in their apparent quality of maintenance).

Cheers,

Christian

On Fri, Nov 20, 2020 at 12:44 AM Dan Čermák <dan.cermak@xxxxxxxxxxxxxxxxxxx> wrote:
Emmanuel Seyman <emmanuel@xxxxxxxxx> writes:

>> However, I'm not stuck on that one and it's probably not useful to stay
>> stuck on it if there's not enough support to do it. So, let's find a
>> different solution.
>
> What exactly do you want to do with this list of lightly-maintained
> packages?

I have been wondering this myself: what advantage will this bring,
besides a bit more peace of mind for the maintainer?

I'd also like to point out that we actually have a concept for lightly
maintained packages that cannot reach end users: modularity. I know its
not popular, but it would be an option for this. However, I wouldn't be
a fan if it being used like this.


Cheers,

Dan
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux