1 |
On Tuesday 13 September 2005 01:09 pm, Ciaran McCreesh wrote: |
2 |
> On Tue, 13 Sep 2005 12:22:32 -0400 Jon Portnoy <avenj@g.o> wrote: |
3 |
> | On Tue, Sep 13, 2005 at 07:33:59AM -0500, Lance Albertson wrote: |
4 |
> | > The actual powers/role of devrel has always been a grey area. |
5 |
> | |
6 |
> | No it hasn't, unless by 'gray area' you mean 'a few people who don't |
7 |
> | like devrel claim it shouldn't be able to do anything because |
8 |
> | drobbins set it up' |
9 |
> | |
10 |
> | Recruitment, conflict resolution, disciplinary issues. I.e., |
11 |
> | 'managing developers.' |
12 |
> |
13 |
> * devrel doesn't do "broke the tree" enforcement, that's QA's job |
14 |
> * devrel doesn't do "broke the tree" enforcement, that's the council's |
15 |
> job |
16 |
> * devrel doesn't do "broke the tree" enforcement, that's the |
17 |
> management's job |
18 |
> * devrel are the only people who do enforcement, and that they decide |
19 |
> when they do it |
20 |
> * devrel are the only people who do enforcement, and that they need to |
21 |
> be told by QA when they need to do something |
22 |
> * devrel are the only people who do enforcement, and that they need to |
23 |
> be told by a manager when they need to do something |
24 |
|
25 |
ive heard some of these ... personally i see it as: |
26 |
- the council puts policies/guidelines/etc into effect based on developer |
27 |
community |
28 |
- QA team uses these policies/guidelines/etc to validate Gentoo and makes |
29 |
other developers aware of their mistakes in a friendly manner |
30 |
- in the case of developers who do not wish to follow accepted |
31 |
policies/guidelines/etc even after being enlightened, devrel is notified and |
32 |
takes appropriate corrective action |
33 |
|
34 |
the idea of course is that policies/guidelines/etc dont come out of nowhere as |
35 |
they should be generally accepted before they are instituted |
36 |
-mike |
37 |
-- |
38 |
gentoo-dev@g.o mailing list |