On Tue, 2019-03-12 at 13:43 +0200, Aleksandar Kurtakov wrote: > On Tue, Mar 12, 2019 at 1:36 PM Neal Gompa <ngompa13@xxxxxxxxx> > wrote: > > > On Tue, Mar 12, 2019 at 7:29 AM Aleksandar Kurtakov < > > akurtako@xxxxxxxxxx> > > wrote: > > > On Tue, Mar 12, 2019 at 1:17 PM Dominik 'Rathann' Mierzejewski < > > dominik@xxxxxxxxxxxxxx> wrote: > > > > On Tuesday, 12 March 2019 at 12:02, Mikolaj Izdebski wrote: > > > > > On Tue, Mar 12, 2019 at 11:49 AM Jakub Jelen < > > > > > jjelen@xxxxxxxxxx> > > wrote: > > > > > > Is there already a way to package the java application as a > > > > > > module > > or > > > > > > we will really remove all these package from Fedora? > > > > > > > > > > Most of Java packages listed in this thread are already > > > > > packaged as > > > > > modules. Their retirement in rawhide won't directly cause > > > > > their > > > > > removal from distribution. > > > > > > > > Maybe, but it will cause the removal of other packages that > > > > depend on > > > > their regular (non-modular) builds. You are forcing the hands > > > > of their > > > > maintainers before the infrastructure to make modular packages > > > > available > > > > as build dependencies to regular packages is in place to remake > > > > their > > > > packages into modules, let them be retired or pick up your > > > > orphans. If > > > > it were ready, your moving these packages to modules would be a > > > > non-event for everyone concerned except you. Instead of helping > > > > with > > > > that (or just waiting), you are about to cause the retirement > > > > of quite a > > > > few packages whose maintainers want nothing to do with > > > > Modularity. > > > > That's not excellent. > > > > > > Dominik, that is totally ugly reply to Mikolaj! Whole Java RPM > > > community > > (note not only Fedora but Mageia and etc. too) relied on his work > > to keep > > hundreds (or maybe even thousands) of packages rpm installable. And > > he has > > done that for years without ever complaining! Even more he is one > > of the > > most helpful maintainers whenever someone faces an issue. Respect > > should be > > shown when deserved, blaming like that causes nothing but ill > > feelings. > > > Everyone should remember that this is *COMMUNITY* project and > > > if/when > > someone needs something they should be ready to jump in and do the > > work - > > whether taking packages or helping infra guys or whatever but no > > one owes > > others anything. > > > P.S. As Eclipse stack maintainers we are directly hit by this and > > already working towards turning it into module as we don't have the > > manpower to take over the maintainership of pristine rpms that > > Mikolaj > > maintains. Whoever things that's easy job is welcome to try it out! > > > > 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 > > * Now it's too late because he orphaned nearly 1700 packages to > > force > > modularization > > * This caused everyone dependent on those packages to freak > > * And here we are in the bad ending... > > > > 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 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. > > > > Hmm, > https://lists.fedoraproject.org/archives/list/java-devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/MQMRQVENBLDRS67WLNQ7EOCMSDI5WIET/ > seems that people had a lot of time to act and get involved. Unfortunately not everyone who happens to maintain a java package is in the java SIG and reading the mails there so I think this mail should have been sent at least to fedora-devel too, maybe even announce since it is touching so many packages (dependencies). I used to have one java package inherited from inactive maintainer then one more and now comes third. I have them because I want to be able to use and update my application in Fedora. I really do not care if they will be built in Fedora or Arbitrary branching. I see that Mikolaj already did a lot of work of moving his packages to the modules, so a mail with simple instructions "this is a list of things that I did for my packages and if you depend on them, do it also", would save many maintainers as me hours of searching the sparse modularity documentation. If there are no such steps, I will jump for the packages that I need, but if the Java in Fedora future should be modular, lets do that. But remember: We do not know how. Regards, -- Jakub Jelen Software Engineer Security Technologies Red Hat, Inc. _______________________________________________ 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
