----- Original Message ----- > From: "Steve Dickson" <SteveD@xxxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx>, "Charalampos Stratakis" > <cstratak@xxxxxxxxxx> > Cc: "Zbigniew Jędrzejewski-Szmek" <zbyszek@xxxxxxxxx>, "Yaakov Selkowitz" <yselkowi@xxxxxxxxxx> > Sent: Friday, December 8, 2017 5:46:03 PM > Subject: Re: What to I have to do.... > > > > On 12/08/2017 11:21 AM, Charalampos Stratakis wrote: > > The kernel is actually blacklisted from proven packager access, you can't > > make changes there. > This is good to know... how do you get on that list? ;-) > > > > Apart from that though, I don't really see any reasons for creating this > > thread. > > > > Proven packagers do trivial and non-trivial cleanups all the time. While I > > agree that a PR would be better, > > when dealing with changes on a vast amount of packages that should be > > ideally done in a timely manner, waiting for a > > timely response from every single maintainer of the respective packages is > > just not realistic. > I understand the need to make massive changes... I no problem with that... > The problem is random people are making non-critical, non-massive > changes because they "feel" its the right thing to do. Those > changes should go through the maintainer. > > steved. > You will have to realize though, that at the moment you are currently talking from your perspective and only, so basically about your "feels" on the matter. And while certainly there might have been cases where a proven packager acted inappropriately, I don't see that particular case as such. A proven packager is not someone random, they were given access based on various criteria and that IMHO includes the fact that their perception or "feels" about what has to be done on other people's packages, is aligned with what has to be done for the overall improvement of the distribution. -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, Red Hat _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
