1 |
On Dec 2, 2012 6:09 PM, "Rich Freeman" <rich0@g.o> wrote: |
2 |
> |
3 |
> On Sun, Dec 2, 2012 at 10:21 AM, hasufell <hasufell@g.o> wrote: |
4 |
> > Only question is now what is a sane soft limit, before you go on and fix |
5 |
> > stuff. |
6 |
> > From a discussion in #gentoo-dev we thought 2-4 weeks depending on the |
7 |
> > severity of the bug is fine. Ofc this should exclude major changes or |
8 |
> > delicate packages from base-system/core/toolchain. |
9 |
> |
10 |
> Seems reasonable - I'd say 2 weeks is plenty. Of course, if the |
11 |
> maintainer explicitly rejects the change in a posting on the bug, then |
12 |
> it is hands off without some kind of escalation. Non-maintainers who |
13 |
> are concerned about a package can always step up to maintain, as long |
14 |
> as it involves real commitment. |
15 |
> |
16 |
> Oh, and on a side note Markos raises a valid point on the bug about |
17 |
> whether the devmanual is a good place for policy. The problem is that |
18 |
> I'm not sure we really have a good place, especially with the ebuild |
19 |
> docs gone in favor of the devmanual now. |
20 |
> |
21 |
> Rich |
22 |
> |
23 |
|
24 |
Maybe adding some bits here[1] is preferred instead of the devmanual. |
25 |
Unless we agree to make devmanual a technical and non-technical document, |
26 |
which I personally don't like because it will end up being huge without |
27 |
some sort of indexing/search textbox for quick queries. |
28 |
|
29 |
[1] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=2 |