https://bugzilla.redhat.com/show_bug.cgi?id=815018 Toshio Ernie Kuratomi <a.badger@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.badger@xxxxxxxxx --- Comment #43 from Toshio Ernie Kuratomi <a.badger@xxxxxxxxx> --- Could we all take a moment to think of other ways to resolve our problems? I think that language differences are playing a role in inflating the differences here but that there's also a basic conflict that we should try to address calmly. Fedora is a Project as well as a Product. The project aims not just to produce the Fedora distribution but also to teach people how to be better packagers and to foster a collaborative environment for people to make that eventual Fedora distribution the best that it can be. @adrian - you do have experience with rpm packaging. But there are many things about packaging for Fedora and working on upstream projects that you may not have experience with. The free software ecosystem is very large and diverse so this is always going to be the case. I have been working on the Packaging Guidelines since the beginning of Fedora and there are definitely types of packages that I *would* be a newbie at packaging. There's no shame in this. With this package, we're running across some things that you might not have dealt with before. What is a bundled library? How do I deal with them? What changes to the upstream code do I have to make to fix those? Some of those answers are on the http://fedoraproject.org/wiki/Packaging:Treatment_Of_Bundled_Libraries page that has already been linked. Others are expected to be general knowledge by people who are doing packaging. Still others require someone to learn the programming language the upstream is written in, become involved with the upstream communities, and submit patches to them to fix issues. These are big commitments of time and effort. sgallagh has started investing that time. Unless you are willing to put in that time and start examining the source code, figuring out what changes have been made, looking for ways to merge those patches upstream, and in general, becoming just as much a member of the upstream community as you are a member of the Fedora community, it would be extremely beneficial for you to do everything in your power to accommodate him. @mrunge - In Fedora, we give people the opportunity to succeed or fail and more importantly, the opportunity to learn while they are failing and then correct their mistakes. We cannot pay people with money for the work that they are willing to do. Instead we "pay" them by teaching them to be better packagers and helping them to achieve things that they could not do on their own. In some cases, like this, it may well be faster and more efficient to do the work yourself than to have to teach another person as you're doing that work. But if we don't take the time to teach we'll gradually marginalize people outside of our "inner circle" and then Fedora will shrink and die. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review