On Tue, 2022-11-29 at 19:10 +0100, Sandro Mani wrote: > > > > Hi everyone, > > > > > > The moby-engine package [1] (also known as Docker) has been > > > orphaned in Fedora and is looking for a new maintainer. The > > > waiting period will soon be over and the package will be retired > > > if nobody steps in. > > > > > > This means that the package will be unavailable starting with the > > > next release of Fedora (Fedora 38) that should happen in > > > approximately 5 to 6 months. > > > > > > If you are using this package and are interested in helping > > > maintaining it, now is the time to come forward! > > I'm using docker for $dayjob and would be willing to help out a > > bit, but I will not be the main maintainer, as I don't feel > > comfortable taking such a huge package and lack the cycles for > > that. > > As I also heavily use docker for my dayjob, and I see that moby- > engine > is still unmaintained (and I guess a couple of days away from > retirement), I intend to give it a shot to keep the package alive. I > don't have expertise in this specific field beyond regular docker and > docker-compose usage, so clearly help is very much appreciated. I'd > proceed by taking the package by the end of the week if it still > unmaintained at that point. >
I also would like keep moby-engine (also known as Docker) and I will help if you need . After analyze go packages, I think we got the same kind of problems of nodejs, which is, too many packages and each package has very few lines of code and make other packages have enormous number of dependencies . In conclusion to maintain it, we will spend a lot of time. I'm thinking for example docker should include all other specific deps like golang- github-containerd-* , golang-github-moby-* So we should try to solve this problem. I'm against this fragmentation of the packages, i.e. in packages guidelines allow may have different sources same package . Best regards, > Sandro > _______________________________________________ > 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 -- Sérgio M. B. _______________________________________________ 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
