* Christopher: > My main point here was that treating the community as a single SIG > makes no more sense than treating all packages whose software is > written in C as a single "C SIG" community. It's too overwhelming for > people to be able to know how to step in and help. I'm not sure this is actually true. Debian has Python and Perl packaging teams which are quite successful, and the Java packaging may also be in better shape there. I think the difference to C is that these languages come with their own packaging/build systems, so creating a distribution package needs a certain number of kludges, but once you've figured those out, you can maintain a large number of packages. I thought that Java used to be like this, too, thanks to ant and later Maven, but maybe this has changed with Gradle, SBT, and whatnot. Thanks, Florian _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
