| 1 |
On Sun, Sep 2, 2012 at 8:03 AM, hasufell <hasufell@g.o> wrote: |
| 2 |
> PMS is a fraction of what is to consider when writing an ebuild. It does |
| 3 |
> not include QA policies, gentoo policies and whatnot. |
| 4 |
|
| 5 |
True, although at least somebody bothers to write PMS down... |
| 6 |
|
| 7 |
Much of the rest is word of mouth, posts on mailing lists, maybe |
| 8 |
council meeting minutes, and whatever somebody decides to put in a bug |
| 9 |
report or ping you with on IRC. There are the GLSAs, and then stuff |
| 10 |
like guides and the devmanual, which are a blend of must-do, best |
| 11 |
practices (which presumably are discretionary), and just illustrative |
| 12 |
examples. |
| 13 |
|
| 14 |
Bottom line is that what a developer MUST do is a matter of what |
| 15 |
people will bother to complain to Devrel about, and what Devrel will |
| 16 |
bother to enforce. For the most part this boils down to common sense. |
| 17 |
That's why most "developers must do foo" proposals don't end up going |
| 18 |
anywhere. In six months somebody new will join the project and not |
| 19 |
even know what they "must" do simply by virtue of the fact that we |
| 20 |
won't bother to write it down anyway. |
| 21 |
|
| 22 |
Rich |
Archives