Dealing with the "my packages" problem

[Christopher]

On Thu, Nov 19, 2015 at 9:44 AM, Orion Poplawski <orion at cora.nwra.com> wrote:
> On 11/18/2015 02:49 PM, Adam Williamson wrote:
>>
>> Just as a general note on this thread: if you're a packager and you
>> have a genuine reason why people should be careful about touching your
>> package, or follow some specific process when doing so, or there's
>> something that people might think they should change but they
>> shouldn't, there is already a pretty effective way of dealing with
>> this:
>>
>> ** PUT A COMMENT IN THE SPEC FILE **
>>
>> this is extremely easy to do, and extremely difficult for anyone who
>> touches it to claim they didn't see.
>
>
> I like this and think it covers this issue pretty well.  Coupled with a much
> needed "get over it - it's not *your* package" attitude shift.
>

+1, also good git commit logs are helpful in addition to inline comments.

I also think it'd be easier to suggest changes to maintainers if we
had a good pull request system (I know it's been suggested before...
possibly by using mirrors on GitHub) to deal with the occasional
one-off drive-by fix.