> Please feel free to come up with a different criterion if the GitHub
organisation doesn’t work for you.

We also could account for things such as activity on the forums/tracker, engagement in IRC, and help with beta testing.  This would allow
people who provide repeated feedback or help with things other than content production to have a real voice.

Having people who are in the organization be the ones who vote is the easiest as you said.  Thus the easiest solution would be to add
people who have made non-content-based contributions to the organization in order to formalize their voting power.

> but try to find something that is not as vague as “I think he should be allowed to”.

In giby's case, besides working on the French translation, he has also been active in IRC, led the recommendation to use Transifex (not
used but spurred discussion), has been active occasionally on other tracker tickets, and had offered to help with the Mac port if possible.

First it would make sense to verify giby wants to be in the Secret Chronicles organization.  If he says yes, we could hold a vote to see
if the existing people (about all of whom were members before he became involved) are fine with him being added.  Once this is decided
we could then proceed to the vote for the god mode ticket.

-datahead



On Friday, July 17, 2015 3:49 AM, Quintus <quintus@quintilianus.eu> wrote:


Chris Jacobsen <cjj_009@yahoo.com> writes:

> Will giby be allowed to vote? I think he should.  Alternatively, we
> could just add him to the contributor list because of his French
> translation, though the issue of people who contribute a lot of ideas
> in IRC only will eventually come up.

Under the current draft, he wouldn’t be allowed to. Thing is, we need a
definite criterion for telling who is allowed to vote and who not;
restricting to the people listed publically as members of the GitHub
organisation is fairly easy. What I would like to prevent is that we
have a different set of people for each vote we take, as there will
always be a lot of people who do the game a favour in some way or
another. Member of this organisation will be who repeatedly contributed
good work to the game, where one-time contributions won’t suffice. It
acts as a filter that allows only those people to vote who actually stay
a longer time with us.

There might be other options, like allowing everyone who has at least
one commit included into the “devel” branch or so, but this will quickly
result in a pretty large amount of people allowed to vote, and will
include lots of people who have only once contributed to TSC in
years. Also, people might leave the project, and while it’s easy to
remove them from the GitHub organisation in such a case, removing them
from the commit log is neither possible nor desired.

Please feel free to come up with a different criterion if the GitHub
organisation doesn’t work for you, but try to find something that is not
as vague as “I think he should be allowed to”. You notice that this very
discussion is reason why we need such a document and criterion;
otherwise we’re going to have such a discussion on who can vote and who
not before each and every vote, because something in the circumstances
changed as new people appear and older disappear.


Vale,
Quintus

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

GnuPG key: F1D8799FBCC8BC4F