Retaining old IRC logs...
by datahead
Post via forum by datahead <cjj_009@xxxxxxxxxx>:
Regarding the discussion about purging old IRC logs, I do not think we should just delete all logs older than 6 months.
If we want to move them off the server, that is fine, but I think they should be kept somewhere. Major meeting and some important discussions are in the logs.
Having a search function, however, would make the old logs much more useful.
--
Sent by Chessboard.
4 years, 1 month
Personal update
by skarfester
Post via forum by skarfester <skarfester@xxxxxxxxxx>:
Today I finally read the general discussion summary on the web. I was cheking the forum almost daily, but forgot the news section. Sorry for that.
Thank you all for adding me to the TSC team. I'm glad to be part of it.
I had just opened a github account so you can add me there.
As for my work for the project I recognise I'm quite idle lately. I have a couple world graphics in mind, nothing big.
As for level design I stopped completely, due to programming changes and specialy to the upcoming game mechanics changes.
I'm not aware of the programming status, but when you have a working beta I offer myself for testing it and editing the world maps so the new release can take profit of the new graphics.
See you around.
--
Sent by Chessboard.
4 years, 2 months
Changed E-Mail Address
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi everyone,
I changed my main e-mail address to <m-guelker(a)phoenixmail.de> and am
going to post under my clear name in the future. Any further e-mails
will come from that e-mail address.
Quintus aka Marvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXFLGXAAoJEPHYeZ+8yLxP8zIH/0Dy9voiczcyVPVKM0nWdLZK
TPHv64mEzLRG+NbkhAfRIgVzrdfz80jPXU4CjLfbFajEeKW93olaoyQOuj/NLNea
p7K2ghrurKg6uCGbzwoN1Ot9Jebrs4c1Ci/vM3oKkHufJb+wFR4gueLX3P171qeD
wTFJaNjzWpRgxQ2HdJ6nT/4KDBAb53JkkOlp02cGZG3+NGRjopHJiFYhp+k2968E
s9LltRwzdV8CwrUTy9HY6Gn2rnPVXkN7t1MxJculHwNtc8ftK54KwPiX1QPjq9zO
KOEut2VNs86nb2MgiZzrZHn6dllVQM2PZJZT1OCGbiYuZzWNLh8VQ6Pi3TqrDAw=
=RNT0
-----END PGP SIGNATURE-----
4 years, 2 months
Game Controllers Working In Linux?
by datahead
Post via forum by datahead <cjj_009@xxxxxxxxxx>:
Has anyone tested a game controller against the latest build in devel, with the SFML changes present?
I could not seem to get the directional pad or analog stick to make Alex move. The arrow keys on the keyboard worked.
I was testing with:
* Ubuntu 12
* An XBox 360 controller
I tried restarting the game and resetting the controls.
--
Sent by Chessboard.
4 years, 2 months
VOTE ANNOUNCEMENT: Translation software
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
A N N O U N C E M E N T O F V O T E
8th vote April 11th, 2016
This is a formal vote announcement as per § 5 of the Voting Rules
(VotR), which are available online[1]. A vote that is accepted by the
team results in a final decision on a topic and determines how to
proceed.
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.
Proponent
°°°°°°°°°
datahead <cjj_009(a)yahoo.com>
Vote Subject
°°°°°°°°°°°°
In the 2nd General Discussion, the vote for deciding about a translation
software to use failed because of a remis situation of 2:2 votes with 1
abstination. Since that vote thus had no binding result, it is hereby
repeated on the long way on the asynchronous infrastructure of the TSC
project, such that we can finally get this evergreen of a discussion
topic resolved by means of more involvement (than the 5 members that
were in IRC).
Vote Options
°°°°°°°°°°°°
1. Accept translations only through submitted PO files (i.e. keep current state, no change)
2. Accept translations only through Transifex, reject submitted PO files
3. Accept translations both through Transifex and via submitted PO files
4. Accept translations only through Weblate, reject submitted PO files
5. Accept translations both through Weblate and via submitted PO files
6. Custom solution
Voting for any option involving Weblate means setting up our own Weblate
instance (hooking it up to our planned LDAP for a single sign on with
only one single username/password combination for the entire project
infrastructure).
Voting Period
°°°°°°°°°°°°°
The voting period starts on 2016-04-26 00:00 UTC, and it ends on
2016-05-10 00:00 UTC.
Procedure
°°°°°°°°°
On 2016-04-26 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, posting it to the forum
into the topic containing this announcement, or commenting on the issue
on GitHub in the ticket this announcement was posted in.
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, to allow you making last efforts in
convincing others from your opinion, and to decide whether you request a
covert vote (see below).
If no single option receives the most votes (but multiple ones win), a
second vote is held with the set of options reduced to those options
which received the most votes.
There is nothing special about this vote, which means it can be decided
by simple majority.
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
later requests for covert votes are ignored.
Quintus
TSC project lead.
[1]: https://github.com/Secretchronicles/documents/raw/master/votingrules/voti...
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXDAH8AAoJEPHYeZ+8yLxPX74IAKcQlGpC3NzBmvWpbRitDKwY
HnWwn0BVkvPR6QHVyIThSdtqVY2YVEZgkCkuDiZl0Dwc2H2uPkigZb3+JaMRRDVE
mA3667ZTF76+j4WLfkTygsV7S6ejkQTYdeQJZkZZDYpGRjCvA9nlomBjRiG9b3mo
DXYn2r+KGsE3ba49cP2jawkDfwMEJGw71wN1zfk1Hf5q+lYOsqvJoxHMRkIqIcSL
XRkWqQyPl2eA4HtlzLdGcOLsbED5XBXuQ0hLFVZkDiqCQLWjp/Jm/DQ2Oe0Uvzrg
lJ+eko74J9SBxhrC1CxAGT8xRk2E363v6AMcl0CMbXRyhoh4oPtzp9Un+qSiTtY=
=v2/P
-----END PGP SIGNATURE-----
4 years, 3 months
TSC bug tracking software: Please inform yourself!
by Quintus
Hi everyone,
from recent discussions in IRC it is foreseeable that different project
members prefer different bugtrackers. At least three different programs
are favoured each by a team member, so expect a dense discussion on the
topic in the upcoming GD.
I thus politely ask every team member to inform himself about
the bugtracking software programs we are considering, which are mainly
GitLab, Gogs, Redmine, Bugzilla, and Trac. This is important because it
is unlikely that we quickly switch away from what we choose later
again.
For Redmine and Gogs we have live demonstration instances containing at
least parts of our real TSC data. They don’t contain the complete set of
more than 500 tickets, but enough to browse and explore. If you want a
test account, email me or xet7 for credentials (the instances are not
open for registration for spam and security reasons).
Gogs instance by xet7:
https://git.xet7.org/Secretchronicles/TSC/
Redmine instance by me:
http://montblanc.guelkerdev.de:3000/projects/tsc
For the others, you have to use other installations by projects
different from us. Might not be as authentic for a demonstration, but
should still serve the purpose. Here are some links:
GitLab:
https://gitlab.com/gitlab-org/gitlab-ce/
(GitLab selfhosting its own infrastructure)
Bugzilla:
https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox
(Mozilla’s Bugzilla project page for Firefox)
Trac:
https://trac.edgewall.org/demo-1.0
(Trac’s own demo site)
Valete,
Quintus
PS: If you got spammed by Redmine emails today, this way my fault! I
forgot to disable sending of notifications when I imported lots of
GitHub tickets!
--
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
4 years, 3 months
CALL FOR VOTES: Voting Rules Change
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
C A L L F O R V O T E S
3rd vote April 4th, 2016
Hi everyone,
this is a formal Call for Votes (CfV) as per § 9 VotR. It officially
opens the voting period for the vote described below, that is, you are
now free to exercise your right to vote. A vote that is accepted by the
team results in a final decision on a topic and determines how to
proceed, so please take care before you participate.
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.
Proponent
°°°°°°°°°
The vote was proposed by datahead <cjj_009(a)yahoo.com> and me,
Quintus <quintus(a)quintilianus.eu>.
Vote Subject
°°°°°°°°°°°°
We make the following proposal to adapt the voting rules so they are
more consistant and more flexible:
- --------------------------------------------------------------------------------
Art. 1
§2(2) is changed to “The vote requires that two thirds of the team
members voting are in favour of adding the new person to the team.”.
§3(1)(Nr.3)(2nd sentence) is changed to “This requires a two thirds
majority of those voting, and the candidate for removal is not allowed
to participate in the vote.”
In §20 the words “of the team members” are replaced with “of all
existing team members”.
Art. 2
A new §5a is introduced after §5 with the following text:
§5a IRC Voting Announcement
(1) For votings held in IRC — as an exception to § 5(2)(Nr.3) — it is
sufficient to announce all available voting options in IRC prior to
taking the votes.
(2) If at least three team members are available in IRC and are not just
idling, it is possible to waive the two-week preparation interval and
vote immediately. The waiver requires all non-idling team members in the
chatroom to agree on it.
(3) Any team member can challenge a voting made under the conditions
of (2) above until two weeks after the declaration of results have
passed by approaching the project lead accordingly. If the voting is
challenged, it is treated the same way as if it failed (§12).
Art. 3
These changes enter into force immediately after the Declaration of
Results of the vote for accepting them.
Any votes running at the moment these changes enter into force are
transferred to the changed version of the rules and do not remain under
the old version.
- --------------------------------------------------------------------------------
For your convienience, you can find a diff of the voting rules in the ML
archive at the end of the voting announcement message[1].
Vote Options
°°°°°°°°°°°°
Option 1: Yes (Accept the change)
Option 2: No (Reject the change)
Voting Period
°°°°°°°°°°°°°
The voting period has started now. It ends on 2016-04-18 00:00 UTC. It
also ends if the sufficient 2/3 majority has been reached.
Note that the General Discussion is scheduled for 2016-04-09. If there
is no final result until that date, the voting will be completed at the
beginning of the General Discussion!
Procedure
°°°°°°°°°
As nobody requested a covert vote, this vote will be held as an open
vote. Please vote by sending an email indicating the option you voted
for to the mailinglist, make an according post to the forum topic
corresponding to this message, or post on the tracker in the ticket
where the vote announcement was published as well. Everybody has only
one vote. If you have a GPG keypair, please use it to sign the message
(this is optional, but recommended).
If you haven’t voted until the General Discussion on 2016-04-09, you can
also vote in IRC on that date once the topic is announced.
If no single option receives the most votes (but multiple ones win), a
second vote is held with the same options (there are only two).
This vote is a special vote. As per §20 VotR, changes to the voting
rules document require a 2/3 majority of ALL TEAM MEMBERS. So please:
every team member should vote on this!
Quintus
TSC project lead.
[1]: http://lists.secretchronicles.de/tsc-devel/2016/03/0000042.html
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXAiJpAAoJEPHYeZ+8yLxPW88H/jDDEzzsLrBiOgHSvxXOT5Me
3Gc70Sh2FMOnUbb3zEDm6Yn42WABeGZW0qQEMfqZxwrSUHhyxEc+zZSCjkJbYgHP
6ZYLNyaUwoqnjHp6x4g5E96A9hKQLtkuoZM4xfrCoataZy1OTThp4p2/EcNjHFYd
6aKAxLx1TbIBmowmSwTulngI6qe9yCW33AEilaRlgPNTQoG7uaYDaAryt0nHpzNh
NfIDKw3VyBP34mx2X4TNA1WMhKreue1Nh+T44neBqnVmJBlsOauHj1Xrmqrhcbur
11NYVZ0bFiIQit2YyYgRs8KOEh/f57soWnTxT+oqGpwHRR2aRsGlzm173dKQI8w=
=8/Cj
-----END PGP SIGNATURE-----
4 years, 3 months
[Document 16/6] Suggestions on different meeting topics by skarfester
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi everyone,
after having been victim of repeated persuation attempts from datahead,
I have given up and have converted skarfester’s post at [1] to a
document. I have to say that I still find this a needless copy of
contents already on the ML, but datahaed insisted we must have that as a
document.
We should probably discuss guidelines on documents. I was intending them
to be used for really large proposals such as story documents of several
pages.
Document info:
Title: Input on Meeting Topics
Author: skarfester
DNr: 16/6
Link: https://github.com/Secretchronicles/documents/raw/master/gd/documents/pdf...
Abstract:
> [ A few comments by skarfester on several different points on the
> discussion schedule of the 2nd General Discussion.
> — note by Quintus ]
Quintus
TSC project lead.
[1]: http://forum.secretchronicles.de/topics/387/posts/1977
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXAipaAAoJEPHYeZ+8yLxPHlYH/1El1fyTxOuFXqawidFAxboF
bNLhqpuD4rRDFoRgrthzJwIFUvFCw36wH2YrQDkTFD5CJf4Ga+f/+V4eljUl4wsr
rtwNIVU+M50K41MzMm0CYfTZ5VUUsO0RdS5VOtd/COFLCnqNryY6CivtW5A7Jm7m
CGd1IvvYUFoFLEMt77f/3nvbaoW1kNz4u5WIu0H+qKyUTL8kS17OUYBowNYSoN+v
7KFimdt9n8fBq8fe7HVhhv6x48HoWMlzZKQ2nNZD/gk7eZ4qxN+5/hDFOztM4ot+
N7Gh9v4qEkO82iKQ+Q9vW9yDZgJbropuK0vmiCEQ2aCO8iOV6n4j7L4GZbgTktU=
=o9uQ
-----END PGP SIGNATURE-----
4 years, 3 months
LaTeX class file for document submissions
by Quintus
Hi everyone,
I wrote a LaTeX class file this evening that I recommend to use for
document submissions as it gives all submitted documents a uniform
layout that provides all required information. The layout has a large
right margin so that you can easily make notes on the printed out
document. I think I managed to set the default paper size to "letter",
but I’m not completely sure if it worked out. I think "letter" is the
best option, because A4 printers can print letter paper usually, but not
the other way round.
The LaTeX class file is available for download here:
https://github.com/Secretchronicles/documents/blob/master/gd/gd-document.cls
Click the "raw" button to download it from that page.
In order to use it, drop it into your local TEXMF tree
(~/.texmf/tex/latex on a default TeXLive distribution) and run
$ mktexlsr ~/.texmf
afterwards. Once done, the new class "gd-document" is available for
use. The class is not really different from standard article
(resp. KOMA-Script's modified scrartcl, which this class is based on),
but it provides the mentioned standardised layout and a useful title
page. For a usage example, see the sources of the 16/1 document, which I
made available here:
https://github.com/Secretchronicles/documents/blob/master/gd/documents/te...
Take care to fill in all the meta information before \maketitle and then
be sure to call \maketitle. You don’t need to supply the document number
if you submit the TeX sources rather than the PDF file, then I can fill
it in.
Typeset your document with "lualatex", not with "pdflatex" please. The
class uses the fontspec package, which is incompatible with pdflatex.
Feel free to make any suggestions on additional commands to define in
that class file so that they’re available to everyone who wants to
submit documents.
Of course, you can continue submitting documents in any other format you
want, as long as it supports copy+paste. I can then transform it into
the unform layout. If however you chose to use this particular LaTeX
class, things will be easier for me.
Valete,
Quintus
--
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
4 years, 3 months
[Document 16/5] Suggestions on different meeting topics by datahead
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi everyone,
the following document has been submitted.
Title: Additional Meeting Topic Suggestions
Author: Chris Jacobsen (datahead)
DNr: 16/5
Link: https://github.com/Secretchronicles/documents/raw/master/gd/documents/pdf...
Abstract:
> [ A few comments by datahead on several different points on the discussion
> schedule of the 2nd General Discussion.
> — note by Quintus ]
Quintus
TSC project lead.
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXADW9AAoJEPHYeZ+8yLxPtE4H/ivGbHpOb68rXgOB7NreO5Vi
I54U7NGS0W/DNIuv/mlCCuuQQZX/smUQNMTvlyKzFqEXjh7SR9Kuu15BsgW0mReg
uMIz9i/rcbwgWZss5Ks1v8rxc9htQ5Ju4psLBtrPeatYzZObn9XSXrR0MhYl2mvX
/dolKw5+1Hs38YPo2RKc22Z/bclWYUKONY/f/qKi75fdsPRCVu3zNtuLD0TB7cwG
vTpahjSJnx34F74hIbLEREojQc0ndHXEzZ05+tpmSK2btAcQeD+Kso6qcaCdo4IZ
cRB+I8FBz87bnmogOxl3hx9Tj2hOngRI9P4plKCJMTz+ljo8yLyhYV7O0l6a8wQ=
=f5gb
-----END PGP SIGNATURE-----
4 years, 3 months
