Hi Donald,
I made the distinction as contribution of code has possible
copyright implications (and may add copyright holders to Quagga) while
reviewers never have this consideration. Does this make sense?
Lou
On 3/15/2016 11:04 AM, Donald Sharp wrote:
> In general I like this proposal. I would state though I don't see a
> need to differentiate between a contributor and reviewer. I would
> like to see more people spending time reviewing incoming code.
>
> donald
>
> On Thu, Mar 10, 2016 at 11:31 AM, Lou Berger <[email protected]
> <mailto:[email protected]>> wrote:
>
>
> Hi Donald, (and anyone else who may have an opinion)
>
> I'm not really sure who to direct this question, but you're mail
> prompted me to send this message - so it's going to you. My
> question is?
>
> On 3/10/2016 10:46 AM, Donald Sharp wrote:
> > Call for more gatekeepers
>
> What is a gatekeeper and where are Quagga project roles defined?
>
> From my vantage points I see that there are:
>
> Users:
> Folks who use quagga, and may also fill other project roles. Users
> also report issues they may find and provide feedback on planned
> changes.
>
> Contributors:
> Folks like me/LabN which (occasionally) write code that is
> submitted back to the project. I'm including both folks that fix bugs
> and author new code in this category. Some may subdivide this
> category,
> but I haven't for simplicity sake.
>
> Reviewers:
> Folks that review submitted code and provide feedback. I'm also
> including folks that test contributions and candidate releases.
> (I/LabN
> have also done some of this.)
>
> Maintainers:
> Those who help Contributors get their submissions into a branch &
> mainline and shepherd a release. These folks are able to devote
> substantial time to the project either through apparent direct
> financial
> support for their activity or otherwise make their time available.
>
> Advisors:
> The 'grey beards' who have long(er) term perspective on the
> project.
>
> I can see where I and others on quagga-dev fit into this
> breakdown, but
> don't really see this type of breakdown documented anywhere and the
> recent discussion on this topic have (frankly) been a bit
> confusing to me.
>
> Thanks,
> Lou
>
> PS I'm hoping for a simple answer, but suspect there isn't one - at
> least yet.
>
>
>
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
