August 2015 - tsc-devel - lists.secretchronicles.org

by Quintus

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, I am proud to announce that as of today, the final stable version 2.0.0 has been released. This release happens exactly six years after the last release of SMC, and is the result of the joint development efforts of our wonderful team. For those who enjoy history courses, there’s a more torough posting going to appear on the TSC website in the next days (when xet7 has finished the Finnish translation) that describes how we got to this point. The code of the final 2.0.0 release is not different from RC1, because no fatal bugs were found in the two-week grace period. The only thing that has changed is that the windows setup installer is now compiled in release mode, and that the version number now says “2.0.0” rather then “2.0.0-RC1”. Please enjoy this first release of our fork! The source tarball and the windows setup installer are available from the project’s FTP server: Address: alexandria.secretchronicles.de Directory: /releases Files: TSC-2.0.0.tar.xz (MD5: 54688db473103299d867b0e52c39f51e) TSC-2.0.0-win32.exe (MD5: e20d66fdf171e0b6d5f065803fcfcd02) There are GPG signatures for these files on the FTP server as well (.sig files). They’re signed by my private key (which is also used to sign this message). Quintus TSC project lead. - -- #!/sbin/quintus Blog: http://www.guelkerdev.de GnuPG key: F1D8799FBCC8BC4F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV0kZ5AAoJEPHYeZ+8yLxPzoUIAJSTMY64gRHAxCPBg3oeBDKX YIcRXJgdEboT7uLT1l1AeldtlIOu1/TnJoVyshiQqXVkLAdBa9Eia8VdrbRMUzBo ew8TbgGg2wZvd3pgll8joQ92LnxxRXoPW8AqS4pLCnRuPd+qsyWChsrpH/4CSG7A 6EkGWsV5Ri2uZ98uEQOugfQIT+wyqXzsUz7LveqEJfoqDH9SZlwiBjbeUZa9G6yZ iJeKLIP52LRvqqjEoUijZoAdUDz6QwPO0IzjSC831WI1Yj2+S3jXdlQVGo5/EltB gAxjS7XyND4UFS32kQAQH/XMARVQ/b6FXZqTdT5WJYnsdyV2fpWNZqs6sHQWS+s= =8xnb -----END PGP SIGNATURE-----

3 years, 6 months

2
3
0 / 0

Need to build a list of websites where we can post to announce the TSC release...

by datahead

Post via forum by datahead <cjj_009@xxxxxxxxxx>: Now that we are releasing, it's time to think about how to announce it to the world. This is a forum posting / mailing list discussion where we can build a list of websites at which we can post. Respond with any websites you think need to have the announcement. This is important, since it may be some time before TSC gets into any Linux repositories or other game websites. Here are a few to get us started: gamedev.net - http://www.gamedev.net/forum/6-your-announcements freegamedev.net - http://forum.freegamedev.net/viewforum.php?f=22 Open Game Art - http://opengameart.org/forums/show-your-project (We might point out we used sound effects posted on their site) -- Sent by Chessboard.

3 years, 6 months

1
0
0 / 0

VOTE ANNOUNCEMENT: Voting Rules Document

by Quintus

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, it is time to decide on the voting document we have been discussing over the last month. As per its § 21, once at least two thirds of the team have accepted it, it will be in force. Consequently, if more than one third rejects it, it is definitely rejected. Here is again the link to the document we are going to vote over: http://team.secretchronicles.de/~quintus/votingrules/votingrules-2015-08-... Keep in mind that once the document is accepted, changes to it will required a 2/3 majority. Following is the official A N N O U N C E M E N T O F V O T E 1st vote August 15th, 2015 This is the formal announcement as per § 5 of the voting rules document. These are the required pieces of information: Proponent °°°°°°°°° The voting was proposed by me, Quintus <quintus(a)quintilianus.eu>. Vote subject °°°°°°°°°°°° This vote is aimed at the ratification of the voting rules document itself. Vote options °°°°°°°°°°°° These are the possible voting options: Option 1: Accept the voting rules document Option 2: Reject the voting rules document Voting period °°°°°°°°°°°°° The voting period starts on 2015-08-31 00:00 UTC, and it ends on 2015-09-30 23:59 UTC, or if the required majority of two thirds in favour or one third against the proposal have accumulated. The vote is failed and void if the required majority is not reached by 2015-09-30. Procedure °°°°°°°°° On 2015-08-31 I will post the public Call for Votes (CfV) that officially opens the voting period. After that you may vote by either emailing your chosen option to the mailinglist or posting it to the forum into the topic containing this announcement. Any vote given before that CfV was posted is ignored. The timespan of two weeks between this announcement and the CfV is intended to give you time to decide and prepare, and to decide whether you request a covert vote (see below). Once the result if definitive I will post an according notice to the mailinglist. If the acceptance option wins, the current voting document draft becomes final and binding for any further votes. If the rejection option wins, the document must be revised before it is voted on again. If not enough people participate in the vote, the document may be voted on again without changes. Covert vote °°°°°°°°°°° 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. Personally, I advise you to not request a covert vote for this specific vote. Quintus TSC project lead. - -- #!/sbin/quintus Blog: http://www.guelkerdev.de GnuPG key: F1D8799FBCC8BC4F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVz1pqAAoJEPHYeZ+8yLxPmtcH/3aBbboh9LEIKtTm1KFQGmA0 gE+GXnL496/+qXeOZPbHC7X7+2ZcNgmJ9NNpkizQyNPaJfv7KDuqxFOfESWEY80E dWyrIyea/KRCjoef7UKOKIS7+5TTnvlkndPvffmFSB+uB+I4cVRugtH/Wlp3k1yX ZEu4NdKvfLouOGWqjm/U8dfgISJMur0vcywLeGaozg4lRLrB2mnUMX6/7cNKsNVz ZLtNiA8MhTvoZqeWKapaK0VxS9kkPhT4aVbsJLbTebiSsoHgkKCGUShiuufPFByu YzA8YYS4wH+S8cItFXoHWsl2bMlJnU2RQGOZD9WlDyG5/VmEbNF9Jg7P7AYY39w= =ekVR -----END PGP SIGNATURE-----

3 years, 6 months

1
0
0 / 0

RFC: Voting rules draft

by Quintus

Hi everyone, 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 of results. - 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. * Archiving - 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 you want. 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. Valete, Quintus 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: http://team.secretchronicles.de/~quintus/votingrules/ -- #!/sbin/quintus Blog: http://www.guelkerdev.de GnuPG key: F1D8799FBCC8BC4F

3 years, 6 months

4
21
0 / 0

[ANN] TSC 2.0.0 RC1 released

by Quintus

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone... 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 is made. Quintus TSC project lead. - -- #!/sbin/quintus Blog: http://www.guelkerdev.de GnuPG key: F1D8799FBCC8BC4F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVthzxAAoJEPHYeZ+8yLxPMS4H/izMJWzMBJVqde4+S7YKl4kt Uux0fy8fRh5AIihrSEQ+PcdU+zRWgCObr2truGur0m8ET91fBKnRCKTcGs1nfbQZ /WA3z/qbOuOqTZwlajvT3sABkLdDkU+9zEX8Ps1B287XqpouKwTSoEognrQFwx2S qzIDZYpviZSUAMzbANFKENxMsX3J+KXjUfa6LQxHYdo9X9bxwxXx2Zair2S1uACN PMNbPLOk9CJ5m6n4iVSvW8RbwGu/jXTgiKuoppGCDRn9CbSfpD53MTXuKSnae7Jq 3QxjeAXyPM8jAOo8rRnwipNYcHYXZ8R6LdrpVe2VcyTSIWrJBixiv5/ts038JWk= =SzvT -----END PGP SIGNATURE-----

3 years, 6 months

2
5
0 / 0

Building on Debian Jessie

by Brian Allen Vanderburg II

I have successfully built the latest devel branch on Debian Jessie x64. I did run into a small problem, so these are the steps I used: Installed updated boost (also make sure other deps are installed as needed): sudo apt-get install libboost1.55-all-dev Created a new build directory: cd /path/to/checkout mkdir build-devel cd build-devel Prepared the build. This is the tricky part. It seems that libboost installs the library files in a multi-arch location on Jessie instead of the accustomed /usr/lib. This means the boost libraries are installed to /usr/lib/x86_64-linux-gnu. The default FindBoost module seems to expect it in /usr/lib, and needs to be convinced to search in the correct location: cmake -DCMAKE_INSTALL_PREFIX=$PWD/install -DBOOST_LIBRARYDIR=/usr/lib/x86_64-linux-gnu ../tsc I get a warning about cegui-0.7 target not being found, but it generates the build files anyway. Afterward I build. On a multi-core system I use -j to compile multiple files at once. Reduces total compile time form ~12 minutes to ~2 minutes: make -j6 make install Tested that it runs: cd install bin/tsc Side note: I'm currently working now and have to drive a bit to get to work and back. So I don't have much time to work on my personal projects during the week now. Maybe I'll move closer to work eventually and get some of that time back. Brian Allen Vanderburg II

3 years, 6 months

2
1
0 / 0

2019

2018

2017

2016

2015

2014

tsc-devel August 2015