On Tue, Mar 12, 2019 at 8:35 AM Mikolaj Izdebski <mizdebsk@xxxxxxxxxx> wrote: > > On Tue, Mar 12, 2019 at 12:36 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > This whole process was handled in the worst possible way. To sum up: > > * No one knew Java SIG was having manpower issues because Mikolaj > > didn't know how to ask for help > > You did not know that, but the situation in Java SIG is well known to > Java SIG members. Statistics speak for themselves. > I'm not a Java SIG member, so how would I know? > For example, the packager who owns the most of Java packages (point of > contacts for 480 Java packages) made his last commit in February 2017. > The second maintainer (PoC for 94 Java packages) had last commit in > 2015. The fourth (PoC of 55 packages) - last commit in March 2017. And > so on. > > Situation on mailing list is not much better. Less than 20 mail > threads in each of years 2018 and 2017. Compare with more than 150 > threads in year 2013. > > The last Java SIG IRC meeting took place in February 2013. > > > * Now it's too late because he orphaned nearly 1700 packages to force > > modularization > > I did not orphan that many packages. I orphaned about 250 packages only. > Sorry, you're right, it affects nearly that many though. > It is not too late for anything. Orphaned packages can still be > adopted. That's the whole point of this thread. > > > We could have avoided the bad ending if at any point there was an > > official call for help to increase Java SIG manpower. There wasn't. We > > could have avoided this if there was a discussion before the > > orphaning. There wasn't. > > We don't have any official process for calling for help. Other distros > (at least Debian) have it, but not Fedora. > The reason Debian has one is because people generally don't know how to work with each other there. That said, if we need a process for this for some people to be more comfortable, then that probably should be requested from FESCo. > Discussion requires more than one participating party. I started a > thread on java-devel list where I explained the situation and my plans > in detail. There was no reply on the list, not a single message. I > only had one or two private conversations about this problem. > > > We could have avoided the bad ending if people dependent on Java > > packages were given the opportunity to help. As you say, this is a > > community distro. That goes both ways. But that didn't happen. > > IMHO I've been very patient. I've given the community a lot of > opportunity to help. I never refused any help. I was and I am still > working with new contributors that want to become packagers. > At the risk of overwhelming myself with yet another SIG (I'm in Python, Go, and Rust already!), I'm willing to help as a SIG member if that's what it takes to prevent this. I don't know much about Java packaging (I have only a single Java based package), though. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
