On 11/03/2016 03:16 AM, Jason A. Donenfeld wrote: > Hey guys, > > Every other day on IRC, I see people arguing about touching each > others packages, despite our policies against it. (Sometimes it's even > me who's doing the touching!) My instinctive reaction is always, > "can't everybody calm down and be happy somebody is doing your work > for you?" The answer to this question is, of course, that it depends > who the developer is and how competent you are. > > So, nothing new here. I don't want to bikeshed about it. Business as usual. > > Perhaps we can come up with something more formal for solving this, > that works a bit better than my package-policy.txt idea (see other > thread). > > A few have proposed in the past adding this kind of "attitude > information" to metadata.xml. Does anybody have any concrete proposals > for what this would look like?
I must have missed the latest IRC conversation on this. Was the issue really about someone else doing the work or was it about someone committing changes without informing the actual maintainer(s) first? If it's the first, there's no issue and nothing needs to be done in my opinion (well maybe the maintainer(s) should take note and solve the issue(s) faster next time). If it's the latter, then I think a much easier solution would be to file a PR, write a bug, or send an email before committing the change. None of those options are particularly difficult to do and it keeps the maintainer in the loop. Just doing that one little thing would have prevented or shutdown the arguments I have seen. Thanks, Nicholas Vinson > > Thanks, > Jason >
signature.asc
Description: OpenPGP digital signature
