1 |
On Sat, Jun 22, 2013 at 6:20 AM, Michael Weber <xmw@g.o> wrote: |
2 |
> Bottom line: I think we need more of a culture of mutual trust than a |
3 |
> ton of metadata. |
4 |
> |
5 |
|
6 |
I have to agree with this. The culture should be that we're doing |
7 |
this work FOR GENTOO. Sure, we're getting benefits out of it as well |
8 |
so it should be a win/win, but we're all in this together. |
9 |
|
10 |
I do think there is some metadata that would be useful. Rather than |
11 |
capturing a "keep out" flag, perhaps it would make more sense to |
12 |
capture more "factual" information, like a comment for humans to read, |
13 |
and maybe a status for scripts. This shouldn't be about who is and |
14 |
isn't allowed to touch things, but rather WHY somebody might think |
15 |
twice about touching things. |
16 |
|
17 |
For example, many system packages should get the white glove treatment |
18 |
because they're, well, system packages. I'd like to think that even |
19 |
the greenest of recruits would appreciate that glibc isn't the best |
20 |
package in the world to experiment on, but a script might not catch |
21 |
that. |
22 |
|
23 |
Useful and informative comments to humans might be useful as well. |
24 |
For example, I might mark my package as "do-not-stabilize" for the |
25 |
scripts and add a comment "game client interfaces with external game |
26 |
server that changes API without warning and requires instant updates." |
27 |
|
28 |
Anybody running scripts on the tree should be careful from the start - |
29 |
perhaps we should even require pre-announcement on -dev. Manual |
30 |
changes are less of a risk, especially if there is warning. |
31 |
|
32 |
All that said, I'm not opposed to there being some kind of flag. |
33 |
However, I think we need to set the expectation that this is about |
34 |
helping us all to collaborate better, and not about putting up |
35 |
razorwire. |
36 |
|
37 |
Rich |