JDK Updates Maintainer process

[Rob McKenna]

Hi Volker,

> I just wonder why the Project Lead alone selects the new Lead
> Maintainer from the list of candidates who have nominated themselves
> and the Project's Committers and Reviewers can only ratify the Project
> Lead's selection? From my point of view, this process is not very
> "democratic" and give the Project Lead too much power compared to the
> Project's Committers and Reviewers. Wouldn't it be more transparent if
> the Committers and Reviewers could directly elect the new Lead
> Maintainer from the list of candidates (in the same way how At-Large
> Members are voted into the Governing Board [3]).
> 

As we've moved to a single project / multiple repository model we
wanted to simply transpose the existing mechanics to the new environment.
For example, in 8u candidates nominate themselves and a new Project Lead
is chosen by the Sponsoring Group Lead. (the difference here being that
the existing group lead will make the selection)

> And by the way, who came up with these rules from the "Repository
> Maintainers" page [2] ? I'm aware of the "[PROPOSED]: New JDK Updates
> Maintainer process" [4] thread, but these rules haven't been discussed
> there. It's very well possible that I've simply missed that discussion
> in which case I'd kindly ask for a reference to it.

The "Repository Maintainers" page is an extention of the discussion you
have linked to. We are open to suggested changes.

    -Rob