incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bernd.fonderm...@googlemail.com>
Subject Re: r0.1 tracking in JIRA
Date Wed, 01 Dec 2010 13:54:47 GMT
On Wed, Dec 1, 2010 at 13:11, Kevin Meyer <kevin@kmz.co.za> wrote:
>
> Hmm - I'd have to disagree - unless maintainer means something else
> in "Developer English", to me, a maintainer (again) does work, and
> possibly "owns", whereas co-ordinator just co-ordinates. ;)
>
> In this case, the [insert word here] *are* currently actively doing
> the work, but this need not always be the case... and the goal is
> to get to the stage where the [insert word here] (at most) oversees
> the contributions and ensures that the module functionality is not
> being compromised/degraded (for example)..
>
> But yes, they are also the first point of contact, should anyone
> require help regarding either usage (as an application developer) or
> guidance (as a framework developer).
>
> Finally, if someone breaks a module, a maintainer would be expected
> to fix it, but a co-ordinator would just tell the person who broke it
> to do so! ;0
>
> What do you think?

I think that this discussion is going into the wrong direction,
whatever you call it, be it lead, FPoC, maintainer, whatever.
In practice, of course, committer A will work more on code subset A1
and B on B1. But this should really be the committer's (daily) choice,
and not be carved in stone.

  Bernd

Mime
View raw message