1 |
> On Nov 3, 2016, at 8:21 AM, Jason A. Donenfeld <zx2c4@g.o> wrote: |
2 |
> |
3 |
>> On Thu, Nov 3, 2016 at 1:15 PM, Nick Vinson <nvinson234@×××××.com> wrote: |
4 |
>> Just doing that one little thing would have prevented or shutdown the |
5 |
>> arguments I have seen. |
6 |
> |
7 |
> Yes, obviously of course. |
8 |
> |
9 |
> But sometimes it's just easier and quicker to meddle in somebody |
10 |
> else's ebuild to improve a particular situation. The question is thus |
11 |
> how do we make this permissible? My proposal is adding a metadata.xml |
12 |
> tag -- <yes-you-can-meddle-in-my-affairs>. |
13 |
> |
14 |
> Jason |
15 |
> |
16 |
|
17 |
Although metadata.xml is one way to do this, since it is more of a social thing than a technical one I think it might be better to wikify it instead -- each dev can list their "please fix my package" preferences in a per package or per anything-with-them-as-maintainer spec in one location. |
18 |
|
19 |
The previous round of this had a bunch of devs make comments to effect of its fine for any dev to commit changes as long as the committee takes responsibility for it, it'll take a bit of time but we can probably compile those from irc logs and -dev@ and start the list. Thoughts? |