with another vote being upfront the door, I deemed it necessary to
finally come to a resolution regarding the voting procedure. Please find
my draft attached. I stripped out any technical details as they’re not
relevant to the interpretation of a voting result, leaving the door open
for whatever exact technical means are useful in the future. This
document thus concentrates on the following issues:
* Who is allowed to vote?
- We have already decided earlier in the last GD that voting should be
restricted to the people who are member of the Secretchronicles
organisation on GitHub. I’ve included that into the document.
* Voting announcements
- Announcement of Vote, Call for Votes, Declaration of Results.
- Two announcements make sure everyone who cares notices.
* Voting procedure complaint
- To ensure the voting procedure is followed properly, each team
member can request it is checked up to 14 days after the declaration
- This is not a measure to enforce a new vote if you missed it. It is
intended for ensuring everyone had equal chance to vote.
- For reference, all vote-related stuff is archived.
The document is short (2 pages), with lots of space between the
different sections. Please read it, comment on it, propose changes if
I want that the document, when all changes are commited, is accepted in
consent by everyone from the team (who cares to participate). This will
generate the democratic legitimation that a voting procedure needs.
PS: For those reading this on the forums (or are to lazy to read
attachments), I put up the draft on my TSC team page:
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNED MESSAGE-----
well. Errm. Hm....
*looks around shyly*
Hrrrm-hrm. I have tagged and released the First Release Candidate (RC1)
of TSC 2.0.0 today. This means we’re on the road to the 2.0.0 final
release pretty far. Finally, after months of delay.
The release files, both sourcecode tarball and Windows setup installer,
will appear on our FTP server ftp.secretchronicles.de as soon as the
upload with my poor Internet connection permits. Once this is done, I
will announce the release also on the website’s news page.
Download links and checksums:
FTP server: ftp.secretchronicles.de
(permits anonymous logins)
File name | MD5 checksum
TSC-2.0.0-rc1.tar.xz | 2642ac8013f10cb4bd53a47241435194
TSC-2.0.0-rc1-win32.exe | 89e18675d2b44a4388da0210fb35a92d
There are detached GPG signatures by me as well (.sig files) on the
server as well.
The RC phase is the last phase in the release process before the final
release. We will be cautiously watching the issue tracker for any new
issues for two weeks after each release candidate. If an important issue
is reported, we’re going to fix it as soon as possible and immediately
issue a new release candidate. Then the two-week phase starts anew.
If no issues are reported within the two-week phase, the final release
TSC project lead.
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
We have released the first release candidate of version 2.0 of SMC on 07/27/2015. We were wondering if you still might be able to request the people from your YouTube channel help with testing for this candidate. This would help us to ensure stability of the game.
The current schedule is to do a new release candidate every two weeks until no bugs are found. If no bugs are found, the release candidate is released as version 2.0 to all players. Thus in the current schedule, the game could be released on August 10, 2015 at the earliest. If you are able to help with testing, though, we can look into the possibility of extending this date to allow you more time with the testers. Without proper testing, there is a risk of an unstable release.
Also, the name of the game is now "The Secret Chronicles of Dr. M" (abbreviated TSC), and the hero's name has been changed to Alex. The new website is: http://www.secretchronicles.de/en/. The mailing list info is at: The Secret Chronicles from the mailinglist archive.