[rvm-core] Organizing the team roles

[Ian Rogers]

Hi,

following another successful Google summer of code (there's lots of work
to do merging in the patches) I would like to improve the way mentors
are accepted and acknowledged. It is great that we get volunteer mentors
and so I would like to see them acknowledged on the web site. Hopefully
this will encourage other mentors to apply and reward the current
mentors, or those who applied to be, for their good will and work.

In the current organization web page we identify the following roles:
user, contributor, project member, core team member, steering committee
member. We also identify a Jikes RVM and MMTk core team, with the MMTk
core team being a subset of Jikes RVM's.

I propose we revise the roles in the organization to: user, contributor,
mentor (some one who promotes the use of Jikes RVM through supervision
within colleges or the summer of code), core team member and steering
committee member. I think we should just have one core team.

Related to this I'd like to see the students that successfully completed
the summer of code become core team members when their projects are
successfully merged into the trunk.

Regards,
Ian

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core

[Tony Hosking]

Yes, good plan!

Antony Hosking | Associate Professor | Computer Science | Purdue University

305 N. University Street | West Lafayette | IN 47907 | USA

Office [phone] | Mobile [phone]

On 7 Nov 2008, at 11:54, Ian Rogers wrote:

Hi,

following another successful Google summer of code (there's lots of work
to do merging in the patches) I would like to improve the way mentors
are accepted and acknowledged. It is great that we get volunteer mentors
and so I would like to see them acknowledged on the web site. Hopefully
this will encourage other mentors to apply and reward the current
mentors, or those who applied to be, for their good will and work.

In the current organization web page we identify the following roles:
user, contributor, project member, core team member, steering committee
member. We also identify a Jikes RVM and MMTk core team, with the MMTk
core team being a subset of Jikes RVM's.

I propose we revise the roles in the organization to: user, contributor,
mentor (some one who promotes the use of Jikes RVM through supervision
within colleges or the summer of code), core team member and steering
committee member. I think we should just have one core team.

Related to this I'd like to see the students that successfully completed
the summer of code become core team members when their projects are
successfully merged into the trunk.

Regards,
Ian

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core

[David P Grove]

Ian Rogers <rogers.email@...> wrote on 11/07/2008 06:54:03 AM:
>
> I propose we revise the roles in the organization to: user, contributor,
> mentor (some one who promotes the use of Jikes RVM through supervision
> within colleges or the summer of code), core team member and steering
> committee member. I think we should just have one core team.

This seems reasonable to me.

>
> Related to this I'd like to see the students that successfully completed
> the summer of code become core team members when their projects are
> successfully merged into the trunk.
>

I think we already have an adequate process for this.  At the end of the summer of code, if the mentor believes the project was successful and the student would be a good addition to the core team, then they should follow our normal process for proposing a new core team member.

--dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core

[Steve Blackburn]

On 08/11/2008, at 6:05 AM, David P Grove wrote:

> I propose we revise the roles in the organization to: user, contributor,
> mentor (some one who promotes the use of Jikes RVM through supervision
> within colleges or the summer of code), core team member and steering
> committee member. I think we should just have one core team.

This seems reasonable to me.

To be clear, I think Ian is suggesting two things:

1. That we drop "project member" and instead have "mentor".   This seems sensible, and provides a way of formally acknowledging those who are engaged with the project but are not contributing code.

2. That we remove the formal distinction between Jikes RVM and MMTk core teams.  I think it is fine to drop that distinction---in practice we have not made any use of it.

Currently only a very small fraction of the core team is active.  I would like to try to get those inactive members engaged, or else encourage them to become mentors, rather than inactive core team members.

>
> Related to this I'd like to see the students that successfully completed
> the summer of code become core team members when their projects are
> successfully merged into the trunk.
>

I think we already have an adequate process for this.  At the end of the summer of code, if the mentor believes the project was successful and the student would be a good addition to the core team, then they should follow our normal process for proposing a new core team member.

I agree with Dave here.  Moreover, I really don't think it helps the project to encourage inactive core team members.

--Steve

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jikesrvm-core mailing list
Jikesrvm-core@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-core