[Scummvm-devel] ScummVM leadership
Eugene Sandulenko
sev at scummvm.org
Mon Aug 15 17:38:10 CEST 2011
Hi Team,
I am back from the holidays, and it is time to revive and finally
resolve the old topic of the project leadership.
Currently the project is at a big risk, since Max physically
disconnected himself from several key infrastructures (he still pays
for the forums/wiki hosting and keeps some of the project money,
nothing beyond that), and in case something will happen with me, there
will be inconveniences for the team.
Still, unfortunately, there is no person who wanted to fill in role of
a co-leader and whom I myself found adequately qualified for the job.
I gave offer to wjp and Kirben, and both declined for different and
sound reasons.
Thus, to mitigate the risk, I would like to employ a different approach.
I am constituting two new entities 'Core Team' and 'PR Office'.
Core Team will govern over OSystem, the project path and architecture,
it will have to decide on important turns in the project history and
development.
PR Office will handle all administrative tasks. This includes press@
handling, legal paperwork, admin accounts on sf.net, git and
HostEurope, project membership, being spokespersons for the team,
handling internal human resource issues. Also keeping any project
keys, such as Android Market keys.
The Core Team will consist of: LordHoto, sev, wjp.
The PR Office will consist of: sev, Strangerke.
As you see, only myself will be in both entities, thus formally we are
narrowing down to a single project lead.
Core Team membership is open, that is, if there are additional
candidates in the future, there are no issues with extending it, still
it cannot grow too much because of the added overhead on the
decisions.
For the decisions on the engine inclusion, new platforms, general
technical questions, the Core Team will be responsible. However, I
will keep a right to veto any decisions.
I already spoke with Arnaud, Johannes and Willem, so what I need to
hear is either there are any questions, clarifications or suggestions
for a better approach.
Eugene
More information about the Scummvm-devel
mailing list