[tsc-devel] VOTE ANNOUNCEMENT: Votings in the General Discussion

Quintus | Fri, 25 Mar 2016 22:39:49 UTC

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

Hi everyone,

this is the

                A N N O U N C E M E N T   O F   V O T E

for the votes we are doing in the General Discussion on April 9th. Since
nobody submitted any voting options, I’ll make some up for now so we
have something to vote on even if we don’t get the required majority for
changing the voting rules.

Still I do hope we get that one through so we don’t get cought in an
overly formalistic voting procedure. I apologise for not having seen the
problem of IRC meetings when writing the first version of the
rules. This is why we should change them. But that’s for the other
topic.

Allowed to vote is any team member, which as per § 1 VotR is everybody
who is publically listed as a member of the “Secretchronicles”
organisation on GitHub.

The voting period starts on 2016-04-09 with the opening of the
respective voting process in the General Discussion, and closes with the
closing of the respective voting process in the General Discussion.

In the General Discussion, each of the topics will be announced,
discussed, and then voted on (call for votes) if no consent is
found. When the voting is finished and all votes have been counted, the
declaration of results happens directly in the GD. The results will also
be published on the ML.

Any vote given before the call for votes is ignored. If no option
receives the most votes (but multiple ones win), a second vote is held
with the set of options reduced to those that got the most votes.

Each team member has the right to request a covert vote. A covert vote
means that a technical procedure is employed that prevents everyone from
seeing how anyone else has voted. It is intended to prevent conflicts
within the team or between users and specific team members, and you
should only request this if you really think this is required. More
openness is better for the project.

If the request is made, it must be honoured. I will announce the
technical procedure in that case.

The request must be made before the Call for Votes has been posted, any
further requests for covert votes are ignored.

The voting rules change vote has already been announced, so it is not
included in this Announcement.

Team membership I
°°°°°°°°°°°°°°°°°

Vote subject: Inclusion of kirbyfan into the team
Vote proponent: datahead

Vote options:

1. Yes
2. No

As per §2(2) VotR, this vote requires a 2/3 majority of *all* team
members. Different only if we accept the voting rules changes before
voting on this.

Team membership II
°°°°°°°°°°°°°°°°°°

Vote subject: Inclusion of skarfester into the team
Vote proponent: datahead

Vote options:

1. Yes
2. No

As per §2(2) VotR, this vote requires a 2/3 majority of *all* team
members. Different only if we accept the voting rules changes before
voting on this.

Bugtracker software
°°°°°°°°°°°°°°°°°°°

Vote subject: Which bugtracking software to use for TSC
Vote proponent: Quintus

Vote options:

1. Bugzilla
2. Custom solution
3. Flyspray
4. GitLab
5. Gogs
6. Mailinglist only
7. Mantis
8. Redmine
9. Trac

Translation software
°°°°°°°°°°°°°°°°°°°°

Vote subject: Which tooling to use for translations
Vote proponent: datahead

Vote options:

1. Provide only PO files (i.e. keep current state, no change)
2. Transifex, no PO files
3. Transifex + PO files
4. Weblate, no PO files
5. Weblate + PO files
6. Custom solution

Audience
°°°°°°°°

Vote subject: Whom to address with the game
Vote proponent: datahead

Vote options:

1. Adults
2. Everyone
3. Old children
4. Young and old children
5. Young children

Depth of story
°°°°°°°°°°°°°°

Vote subject: How deep should the story be?
Vote proponent: datahead

Vote options:

1. Complex story critically required to enjoy the game
2. Good story, understanding increases value of the game
3. A bit of story, the game is more about playing a level
4. No story at all

Themes
°°°°°°

Vote subject: Which themes to focus on?
Vote proponent: datahead

Vote options:

1. Shakespeare and his works
2. Mario references
3. Food
4. Zombies
5. Futurism
6. Magic
7. No specific theme

Narration
°°°°°°°°°

Vote subject: How to tell the story?
Vote proponent: datahead

Vote options:

1. All by text
2. Cinematic scenes with text
3. Cinematic scenes with speech, text as fallback if localisation is not
   available
4. Cinematic scenes with speech, English as fallback if localisation is not
   available
5. Videos, with text as fallback if localisation is not available
6. Videos, with English as fallback if localisation is not available

Lifes and energy
°°°°°°°°°°°°°°°°

Vote subject: Changing the life system to an energy system
Vote proponent: datahead

Vote options:

1. Yes
2. No

CEGUI/SFGUI
°°°°°°°°°°°

Vote subject: Which GUI system to use
Vote proponent: Quintus (on suggestion of skarfester [not TSC team])

Vote options:

1. CEGUI
2. SFGUI

Quintus
TSC project lead.

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

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

iQEcBAEBCAAGBQJW9b2rAAoJEPHYeZ+8yLxPZWcH/jtlbYJ8QFJBAeCxptc0ICsi
WlHRUb0GwGrvgOR87sLI7u363HsQDHptGjEO0StDUQAjfeumenIl4dQkdewGJChJ
gqxn+YX+303rRCINltGTZMvIc2IbgDh8nQQqnLjCxRIfNpenJQyuarLisYIuNBqE
xuSSsUnmklFztt9HBSN1u6Nv7wHadNynMXrWMEPObu+rmnApQfHE9E1eKfXa3v0o
GfhPynZiuIkJF34JmPSe62GfjPCLBXpLny1eE2l2ZJ7DRpYjH3GgJI926ylQjUrD
SD7HpIrR5gQe5h6EFU7EvE00HSYUh+MaaMvFUFqtobP2NljOwY8R60JNLPdUlHU=
=o9/c
-----END PGP SIGNATURE-----