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