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.
2 years, 9 months
[ANN] 2nd General Discussion - Request for Agenda
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi everyone,
datahead has requested to hold a General Discussion (GD). For those of
you who have not yet attended one (well, there has only been one yet),
see further below.
This email is to find the agenda of the 2nd GD. PLEASE MAKE SUGGESTIONS
FOR THE SCHEDULE now so that we can handle as many topics as
possible. Having the entire team available in chat is a rare
opportunity, so make use of the situation BY SUBMITTING AGENDA
SUGGESTIONS. Simply reply to this post on the ML or the forum to make an
agenda suggestion.
Furthermore, we need to find a date for the GD. Remember that the last
GD took over 3 hours, so before making a suggestion ensure you really
have time at that day. While everyone can make a suggestion on the date,
please respect that the suggestions made by the TSC team members are
more likely to be accepted as those are the people making the final
decisions, and hence need to be available.
Note that §5 VotR mandates that at least two weeks have to pass between
the final agenda announcement and the actual GD. Holding the GD
immediately after laying down the schedule would have been a bad idea
anyway. People need to prepare.
As a difference to the last GD, datahead has suggested to prepare the GD
by publically submitting documents prior to it. I think this is a good
idea; maybe it allows to go through the meeting more quickly then last
time if everybody is well-prepared. To submit a document, please email
it in PDF format to the ML or to datahead or me. We will upload the
document to the TSC-documents repository then so it is available for
everyone. The document thereby is assigned a number, so you can easily
reference it if you want to write up a reply.
Documents can be used to lay down basic facts or to outline a long and
complex argument which might not be possible in the hastiness of
speaking live. When speaking, you should still give a short summary of
your main arguments, though.
Please only submit documents that actually relate to a topic on the
agenda. If necessary, request your topic to be taken to the agenda
first. Nobody has time to read through wealths of documents about topics
that will not even be covered in the meeting.
Two weeks before the GD there will be a document submission
deadline. Documents submitted after this deadline are ignored. This is
to give people time to read through all of them.
What is a GD?
A General Discussion is a scheduled IRC meeting of the entire TSC team and
a means to intensely discuss and subsequently vote on difficult
topics. Of course, anybody interested is invited to join and bring
forward his point of view and his arguments, even if he is not a member
of the TSC team, but allowed to finally vote are, in accordance with the
voting rules, only members of the team.
The discussion is moderated and follows a previously layed down
agenda. For each of the topics on the agenda, everyone who has announced
it previously will speak on it. IRC voicing is used to ensure the
speaker will not be interrupted; while he speaks, questions can of
course be submitted which will then be answered once he is done. When
all speakers have finished, open discussion starts (i.e. the IRC voicing
restriction is released). After that, a voting is held if it is
impossible to reach a consent.
There will be a more detailed announcement of the precedure prior to the
GD, so don’t worry if you didn’t fully understand how it works. To get
an impression, take a look at the last GD’s announcement[1] and the
actual log of the discussion[2]. In any case, be prepared to spend a lot
of time on it -- the last GD took over 3 hours, with only a 15 minute
break.
Quintus
TSC project lead.
[1]: http://team.secretchronicles.de/~quintus/general-discussions/1st-general-...
[2]: http://chatlogs.secretchronicles.de/htmllogs/2015-03-21.log.html#msg-2015...
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWuG9KAAoJEPHYeZ+8yLxPPJ8IAKHQEcy+PO5uKmcSQ9DKGF4Y
UUIiJvXjr8vEU9FdGzPhLs8XYUO5Jrso4ZWCtpobLlGLnmaJnV0s3pWUbsAkAJan
oX2BPI+ywpolDABnQoTt/xe9hDntKX7R/mR/f67pk9fRYzFLLEoU0deiwafCffgi
1IMCfjMT3FDn9xiNiSvkIYyjSx4ol1Cq22eVwR/dh343Ci3h8I3Arc6UDGjGiFb6
RJVWWiRn3aZ/WjZdzrCzWoE+JV6y+88xnsN0p0UsMNJwRJdFZTbXgkQG9/wKu6SF
SmjNEuned7FTH5JcoaRUMt6HgjJ+6j7T/vJXRHNhdPrM/CCLUYeKDE2oqISchpo=
=EAUG
-----END PGP SIGNATURE-----
2 years, 10 months
Team Nominations...
by Chris Jacobsen
I would like to nominate the following two people for membership to the
Secret Chronicles team:
*skarfester - Several art contributions as well as involvement in
general art discussions
*kirbyfan64 - Two accepted songs and reasonably involved programming
contributions for the SFML port
Per the voting rules at
https://github.com/Secretchronicles/documents/blob/master/votingrules/vot...
we must hold a vote for each person above. The rules state that a two
thirds majority must be reached out of all existing team members.
If interpreted literally, people who don't find time to vote will be
interpreted as votes against membership, which would make it difficult
to add people ever.
Technically, the only way to change this is by holding a vote on
changing the voting rules document itself, which takes time. If anyone
has any suggestions
about how to resolve this, please share them.
In the meantime, we should allow a little time for people to offer
thoughts before we hold the vote. Please feel free to share any
suggestions in favor
of our against the nomination.
-datahead
--
Chris Jacobsen
http://www.jacobsensoftware.com
2 years, 11 months
Project management software / server OS
by Quintus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi everyone,
xet7 yesterday decided that we are going to install Sandstorm as the OS
on alexandria. I read the corresponding email today, and I want to put
this before the entire team to decide on.
Here is the IRC log from yesterday, 2016-01-16:
- ----------------------------------------
16:23 -->lambda-11235 entered #secretchronicles.
16:23 xet7 | Quintus_q head8debian: I now have access to new donated VPS. For comparison: Alexandria 2 GB RAM, 240 GB disk space where 64 GB used - mostly backups that are 44.6 GB, kernel 2.6.32. New VPS, running at DigitalOcean Frankfurt datacenter: 1 GB RAM, 30 GB disk space where 2.2 GB used. Running Ubuntu 14.04 64bit, with kernel 3.13.0-71. TSC website would need to thank DigitalOcean for providing hosting. I will use https://sandstorm.i
16:23 xet7 | o platform on the server. Server is donated by Sandstorm, that had DigitalOcean free credits. They will check progress after one year. I have been translating Sandstorm projects to Finnish, and will continue that.
16:25 xet7 | Anyway, alexandria server will remain as is now, until I have tested and configured all on new server.
16:25 xet7 | New kernel also makes possible to use OpenVPN on server, if needed.
16:27 xet7 | Sandstorm has lot of security features that require newer kernel.
17:21 <--DarkAceZ left the IRC network (Read error: Connection reset by peer)
17:21 -->DarkAceZ entered #secretchronicles.
17:49 --datahead8888 is now known as datahead7777
18:57 ZenWalker | datahead7777: thanks
19:01 head8debian | xet7: Why didn't you jsut ask Firstroot for another server? They would have been glad to give us one.
19:03 <--Tobbi left the IRC network (Remote host closed the connection)
19:03 -->Tobbi entered #secretchronicles.
19:04 xet7 | head8debian: Really? I can ask sure.
19:06 xet7 | head8debian: I could really use more RAM and disk space, it that is possible. I'll send Firstroot a ticket.
19:12 datahead7777 | lambda-11235, I merged your PR earlier today
19:22 lambda-11235 | datahead7777: I saw that.
19:51 head8debian | xet7: I'd talke to QUintus first. ;)
19:51 head8debian | talk*
19:52 datahead7777 | head8debian, are there advantages if we can get a second server with First Root rather than having two different providers?
19:53 xet7 | I already sent Firstroot a ticket .. did I act too fast?
19:53 head8debian | datahead7777: Not really, except that First root knows us quite well, and has been very generous and willing in the past.
19:53 head8debian | I guess we just sit back and see...
19:53 head8debian | I was hoping to hear Quintus's opinion, since he has worked with them quite a bit.
19:57 xet7 | head8debian: I tried to be polite etc in my ticket to Firstroot. And previously at this channel Quintus said "<Quintus_q> head8debian: It would be nice if you took the time and work together with xet7 for upgrading alexandria and setting up our own project infrastructure"
19:59 xet7 | Plan was first to upgrade alexandria current server, but using Sandstorm for infra would be much easier and secure for upgrades etc, and Sandstorm requires newer kernel.
20:00 xet7 | I will send Quintus email about current status.
20:03 datahead7777 | I was thinking in the back of my mind if there was any chance they think we're asking too much of them to try to get another server, though it really depends on our relationship with them
20:04 datahead7777 | I guess it depends on how we approach it, too
20:04 head8debian | datahead7777: Yes it does.
20:05 datahead7777 | head8debian, well, having one provider simplifies are administration
20:05 datahead7777 | We'd have one company to contact for any needs
20:05 head8debian | datahead7777: From what i can tell from QUintus's convos is that they are quite impressed with what we have done so far, and are quite happy to keep helping us, but i could be wrong.
20:05 head8debian | Anyways, im afk...
20:05 datahead7777 | Having a release makes a differences
20:05 datahead7777 | We'll need to get another release semi-soon to show more progress
20:10 xet7 | I sent email to Quintus.
20:32 datahead7777 | Okay, let us know if there's anything we should be aware of. The mailing list is probably a good place to announce anything.
20:32 datahead7777 | Or discuss anything
20:33 datahead7777 | Thanks, xet7
20:36 xet7 | datahead7777: Yes I will let you know. Currently I'm testing various infra software etc, so no actual changes to any current system yet.
- ----------------------------------------
I have neither heard of nor have I tried Sandstorm previously. This
doesn’t have to say anything, though. However, a quick view on the
website of this software makes me sceptic about how it fits our current
workflow. It is more like a complete collaboration platform that
replaces everything we currently have. This is a fairly major switch
that I want to see appreciated by more people on the team. As for my
part, I think it is a known fact that I am a commandline hacker who has
not a lot of use for fancy UIs. I mostly communicate by means of email,
and I recently complained to GitHub their email notifications on PRs do
not contain a link to the full URL needed for $ git pull so that I am
forced to visit the website. My ideal project issue tracker is fully
email-transparent and mostly acts like a mailinglist; it doesn’t have to
be entirely like this, but to some degree I need my email interface. I
recognise I am of a somewhat singular opinion in this regard, but I hope
not completely alone.
To be clear, I don’t want an email-only thing only either. I do know it
is difficult for some people to use, although I can only point out how
much more productive one is this way. If there’s a web interface, that
is okay, just don’t force me to use it in a project I work on
voluntaryly. TSC does not have a large amount of contributors anyway,
and thus it is important that first and foremost any software we use
fits our workflow and only on a secondary level is easy to use for
non-core TSC contributors. As it stands, I fear we’re about to change
our current workflow from a rather classic, commandlineish, emailish OSS
one to a modern hyped one. If it wasn’t clear from the above, I am a
fairly conservative nature.
I realise I am not in the position to dictate the team what it has to
use as software, but neither is xet7. I will call for a vote on this if
you really want to impose this newly-fangled stuff on me.
It would be unfair of me if I forced xet7 to make a server only fitting
my very own views after I told him to think about stuff himself. I would
thus of course take over server maintenance myself again, so he is not
covered with work arising only from my queer views of how to administer
a project and a server. For the work he already put in the server OS and
software reserach, I do say thank you. It was me whose wording in IRC
was unclear; I expected to get a little more feedback before someone of
us runs out and asks other companies for support. For this I apologise.
Any input from anybody is appreciated.
Valete,
Quintus
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWm5prAAoJEPHYeZ+8yLxP1hoH/ijChoyJc6V0cKP3WdH7vaBf
8LvaeeG3RPxQUhIVMjzT6wD8QlzBORs8BJsMTvRdsQFTevLZhYOHm2JC5SWtqZrA
j10a/alUI8NNJxmku8sR7YEBPglTFC4h1Sjfei0U5WkeMjLioC6u62njrsTKsaGo
VrbbRUq6DgOAzhEfD2hV8B22xELWkdL8aAY/aBfsqEt4Vappzi89Rrjr9tlOIEhh
1fpCTnC6D6lbesCSaw9MUxKgRBXNXeb1xIsUZIVtXuKTfIVIusf+HOH2XWkwvGfP
FpfIFhy4gnbDACu5tSRw/XZQCcp43lEkFbG2zrOfUj92MCAeVXAbp8Fq4+7Bgdo=
=6/ZS
-----END PGP SIGNATURE-----
2 years, 11 months
State of the SFML port
by Quintus
Hi everyone,
today I completed my work on the sfml-port-input branch. For the first
time in our SFML porting efforts I was able to actually compile, run,
and play the game. I successfully finished lvl_1.
The sfml-port-input branch has now been merged into feature-sfml-port2,
which thereby now contains a roughly playable version of TSC mostly
ported to SFML. The port still has its issues, but I think the largest
part now has been moved over. The biggest thing remaining is the porting
of the audio system from SDL_mixer to SFML’s audio module, but thanks to
kirbyfan there is a PR available for that already[1] which will
drastically simplyfy things. If I have a correct view on the topic, it
is possible for us to wipe the SDL1 dependency from the codebase after
merging kirbyfan’s audio PR.
The SFML port in feature-sfml-port2 is, as outlined, roughly
playable. It has some issues we now need to tackle:
1. Mouse button input doesn’t work. You have to navigate the game with
the keyboard, including menus.
2. Graphical glitch with blue arrows in the HUD and everywhere points
should occur. This is probably due to an unported call to
glPixelStorei() in video.cpp[2] that I don’t know how to
handle. datahead, Luiji, would be nice if one of you OpenGL people can
take a look at that and estimate what that line intended to do (and even
better, fix the problem).
There are probably numerous further issues that I haven’t spot by simply
running through lvl_1. Please compile and test feature-sfml-port2 now,
and even more important, please contribute to it. The lengthy part of
the SFML porting should be over now, so let’s finish this.
Before starting the game, move away or delete your
~/.config/tsc/config.xml file. SFML doesn’t understand the SDL
key codes (obviously) and you would be unable to input anything with
your keyboard. Deleting that file causes the game to recreate it with
the default values (jump = s, fire/iceballs = space, etc.).
If you run ArchLinux or another rolling release distribution, beware
issue #500[3]. There is an incompatibility between our old CEGUI version
and the newest version of freetype2. This doesn’t specifically affect
the feature-sfml-port2 branch, but also devel and all versions of TSC
and probably even SMC alike. The issue tracker contains a workaround for
the problem.
Let’s work on completing the move to SFML. Happy coding!
Valete,
Quintus
[1]: https://github.com/Secretchronicles/TSC/pull/488
[2]: https://github.com/Secretchronicles/TSC/blob/f1a7838e6265ac2fb154ec24cfea...
[3]: https://github.com/Secretchronicles/TSC/issues/500
--
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
2 years, 11 months
