| 1 |
On Thu, Jul 09, 2015 at 08:20:06PM +0200, "Paweł Hajdan, Jr." wrote: |
| 2 |
> On 7/9/15 6:05 PM, William Hubbs wrote: |
| 3 |
> > * Gentoo needs consistency in terms of policies. For example, right now |
| 4 |
> > we have https://devmanual.gentoo.org and |
| 5 |
> > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Policies. The qa |
| 6 |
> > policies page contradicts some things in the developer manual, so there |
| 7 |
> > is no clear way to point to the official policies. |
| 8 |
> |
| 9 |
> Could you give examples of the inconsistencies? |
| 10 |
|
| 11 |
The big one in my mind has to do with removing old stable versions when |
| 12 |
an architecture team falls behind on stabilizations. |
| 13 |
|
| 14 |
According to the dev manual, you can't remove an older version until a |
| 15 |
newer one is stable on the same architectures with some limited |
| 16 |
exceptions. According to the qa page, after 90 days, the removal policy |
| 17 |
applies to any architecture unless you break the depgraph. |
| 18 |
|
| 19 |
> Please consider e.g. filing bugs for each issue. |
| 20 |
|
| 21 |
The problem is, it isn't clear which path is official. The qa team |
| 22 |
approved the global policy, but every time the council tries to back it |
| 23 |
architecture teams seem to step up and say they will catch up and |
| 24 |
convince the council to back down. |
| 25 |
|
| 26 |
> > * The Gentoo Code of Conduct still needs to be revisited. We started |
| 27 |
> > that process this term, but it was not completed. |
| 28 |
> |
| 29 |
> Could you elaborate on that? I'd agree Code of Conduct is important, |
| 30 |
> just wondering what specifically would you like to do. |
| 31 |
|
| 32 |
We need to define harassment, discrimination etc and also ask the |
| 33 |
trustees to support applying the CoC to foundation members. |
| 34 |
|
| 35 |
> > * The council should only be asked to make a decision on an issue when |
| 36 |
> > the issue cannot be settled by the community itself. As it has been said |
| 37 |
> > by others, the council should do what it can to stay out |
| 38 |
> > of the way of innovations, which should come from the developers. |
| 39 |
> |
| 40 |
> Yup, I can't agree more with this. |
| 41 |
> |
| 42 |
> Curious though - do you think the current Council wasn't acting |
| 43 |
> according to above approach? If so, could you give examples? |
| 44 |
|
| 45 |
No, I can't think of any specific examples from the current council. |
| 46 |
Again, it was just a general statement that the council shouldn't get |
| 47 |
involved to the level of requiring certain implementations of things. |
| 48 |
|
| 49 |
William |
Archives