Project proposal: Shenandoah

Mario Torre neugens at
Wed Mar 25 15:05:33 UTC 2015

On Wed, 2015-03-25 at 14:49 +0100, Volker Simonis wrote:
> On Wed, Mar 25, 2015 at 12:55 PM, dalibor topic
> <dalibor.topic at> wrote:
> >
> >
> > On 25.03.2015 10:52, Volker Simonis wrote:
> >>
> >> So we should either introduce OpenJDK mail aliases which can be easily
> >> forwarded to new email addresses or make it possible to somehow
> >> contact people who are listed on the OpenJDK census page. This should
> >> be especially true for function owners like project leads.
> >
> >
> > The Bylaws provide ways to handle transition of Group & Project Leads
> > without requiring publication of (potentially) private (contact)
> > information.
> >
> > The simplest mode of transition is for a person to resign from a leadership
> > role, followed by nomination of another. Details depend on the role in
> > question, of course.
> >
> All I can find in the Bylaws is the provision for the case where a
> Group or Project Lead resigns or departs. As to my knowledge non of
> these two cases happened, according to the Bylaws John is still the
> Hotspot Group Lead. And as I wrote before - I would really appreciate
> to have a HotSpot group lead who is not an Oracle employee.
> But we can not know what John's plans are, so the only possibility I
> can find in the Bylaws for this situation is to raise a motion to
> remove him as group lead. On the other hand that seems unnecessarily
> harsh to me.

Well according to census[1], John Coomes is still the HotSpot project
lead, so giving the benefit of doubt I would wait a couple days before
doing it (just in case he is in holiday or such).

As you note too, I didn't see any email going around to announcing him
to resign or a new lead to be proposed.

I think bringing this up formally to the Bylaw would be pretty harsh
indeed, I don't think that bringing the issue this situation is causing
is though.

> I think the only ones who can handle this a little more gracefully are
> the people from the HotSpot group within Oracle. So maybe somebody can
> speak up? I can not imagine you guys are really surprised by this
> situation :)



More information about the discuss mailing list