[virgo-dev] Virgo Project Leadership [was: Fwd: Virgo Project Leadership

[Glyn Normington <gnormington@xxxxxxxxxxxxx>]

I now need to step down as Virgo project lead. The RT PMC will decide if/when to terminate the project.

If anyone subsequently decides to step forward as a project lead, I will happily be available for consultation to ensure a smooth transition of leadership.

Finally, I'd like to say how much I have enjoyed working on Virgo and interacting with numerous friends and colleagues in the Eclipse community.

All the best for the future,
Glyn

On 11 Jul 2013, at 13:58, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:

From the RT PMC's perspective the Virgo project must have a project lead going forward.  Existing Virgo committers need to be aware that without a project lead the Virgo project will eventually be considered for a termination review.  Any stakeholders interested in the Virgo project should not take Glyn's request for a replacement lightly.  Please consider stepping up as a lead for Virgo.

Begin forwarded message:

From: Glyn Normington <gnormington@xxxxxxxxxxxxx>

Subject: Virgo Project Leadership and request to committers

Date: 8 July 2013 09:17:42 BST

To: Virgo Project <virgo-dev@xxxxxxxxxxx>

I can no longer devote sufficient time to Virgo to lead it in the way I would like to. Eclipse projects have been known to limp along for a while without an active leader, but it's not a particularly good state of affairs. So I'm looking for someone to take over the leadership role. I will be available for consultation, so if there are any tricky issues, the new leader won't be on their own.

I estimate leading Virgo takes about half a day per week. The duties include the following, but these are just a guideline as a new leader could set their own agenda:

* Participating in the RT PMC (the minimum is to join a bi-weekly 30 minute call)

* Running a bi-weekly community call (although this is usually not needed these days)

* Keeping an eye on the forum and virgo-dev and dispatching any important unanswered questions to suitable experts

* Coaching potential new committers

* Processing occasional contributions

* In discussion with other committers, agreeing the content of each release

* Preparing release documentation

Of course, it will be simplest if a current committer is willing to take on this role, so may I ask current committers to consider this and respond by 20 July 2013. (I will be on vacation next week, so if there are any questions, please raise them this week.) 

Regards,
Glyn