[tsc-devel] [ANN] Luiji steps down as project assistant lead

Quintus | Sat, 09 Jan 2016 10:48:17 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi everyone,

on 2016-01-05 Luiji notified me that the timeframe he has available is
too limited for him to further support the TSC project as assistant
lead. He is happy to remain with the project to some extend, but judges
it unreasonable to have a higher position than others who invest more
time than him. That is, Luiji will continue to be a part of the TSC team
with repository access and voting rights, and we will occasionally see
contributions from him, even if they’re just of a communicative nature.

I think I can speak in the name of the entire TSC team to express our
greatest gratitude to Luiji, who played a central part during the early
days of the project and made a fork look reasonable and
possible. Without him, his administrative and programming efforts TSC
would not be where it is today: A stable version 2.0.0 released and on
the road to further improvements. We hope that you enjoy your further
pathes and wish you all the best.

With Luiji’s retirement the position of the project assistant lead
becomes vacant. I invite everyone from the team to think about taking
over this position; it’s duties aren’t of a too grave nature. The
project assistant lead:

* Guides votings if the project lead (me currently) is unavailable
  (§5(3) VotR), which means posting the vote announcements and counting
  the votes and
* Can be asked to check and thus invalidate votings which violate the
  formal voting process (§§14 ff. VotR).

Apart from these formal duties, he:

* Acts in place of the project lead if that one is unavailable for
  whatever reason,
* Should watch the tracker more closely than others and ensure important
  tickets don’t fall asleep,
* Should have an open ear for complaints by team members and non-team members
  about social issues in the team and the TSC community, and if
  required, try to resolve them, and
* Will occasionally be emailed by the project lead about issues
  affecting the project as a whole.

To summarise, he should simply have a closer look at what is going on in
the project. It does not mean you have to hang around in IRC all day
long or post to the tracker permanently. But if you find that a PR has
not been answered for two weeks by anybody, you should do that.

It is worth to point out that it’s okay for the project assistant lead
to not contribute much code or assets to the game. It’s more of an
administrative position that is meant to ensure that the project stays
in a healthy overall state. Since all his work is usually done together
with the project lead that is usually not too much. If you once every
one or two weeks take a look and answer the important stuff, you’re
usually doing fine.

Before I make any suggestions about who I think would fit into the
position I’d like to encourage you to think about taking it yourself. As
always, I would like to reach a consent between all team members about
that.

Quintus
TSC project lead.

- -- 
#!/sbin/quintus
Blog: http://www.guelkerdev.de

GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWkOV5AAoJEPHYeZ+8yLxPASMH/itbsiAF/ktOHsPpzlMlkL2F
VaUziDoPc2ANDAAxS6uADc5oucjm3ycDwm4Rhxu2KHYwAnJs9IweMmZZB0d/9oam
EmjkGDfjIVfd53qqgoN0r4qguj1swz412qnN9Pc29IRZTBS7PNMp2ELfqEEc4zwH
QW4AY5rFZwML6hBk4wtuSFqNGVhqIs8jtPW5YW8pgKXeHuYFCRHl9Lfls2CaVMIX
fDwbFwar8MCFJy1RInEO9mF6f96rB5UnagLxZFd+7yE8JV5mHHUlyYck5TRY0HSR
3oY3pc2t7J1GWN+u1y326cRIhmom/qwppXTVB3yvVqf/BRb/QfEYpFk135I12zA=
=7Yhd
-----END PGP SIGNATURE-----