Re: [tsc-devel] General Team Discussion in IRC
Chris Jacobsen |
Mon, 02 Mar 2015 19:56:22 UTC
I think we need to add resolving https://github.com/Secretchronicles/TSC/issues/298 to the discussion list. We will also need to decide whether to allow eyes on a handful of other scenery objects or not. It is probably best to resolve this before the release, since we will be making first impressions then.
-datahead
On Monday, March 2, 2015 8:22 AM, Sydney Dykstra <…d@o…> wrote:
That should work for me, but as always, i cannot garuntee anything.
-Sydney
On 03/02/2015 08:01 AM, Chris Jacobsen wrote:
We might consider posting this in a github ticket -- some people use neither the forums nor the mailing list or check them infrequently. Hopefully this will start to be less of an issue when we move off github :)
-datahead
On Monday, March 2, 2015 6:19 AM, Quintus <…s@q…> wrote:
(I’m also going to post this on the forums)
Hi everyone,
it has turned out that there are some issues regarding TSC lying around
that should be resolved once and for all by having a larger general
discussion in IRC on them. The main issue is probably what has been
suggested by datahead in IRC recently, namely the handling of the 2.x
development branch after the 2.0.0 release. Apart from that there are
some further issues we ought to discuss, and I think best way to do that
is to have everyone from the team join an organised (i.e. ordered by
topics) IRC discussion session. This requires first and foremost to find
a date and time that allows every team member to join. I suggest the
following for now:
2015-03-21 20:00:00 UTC
Please object immediately if you know you are unavailable at this date
or time.
Discussion schedule until now:
1. Determing the voting process (proponent: Quintus)
2. Maintenance of the 2.x branch and opening of the 3.x branch
(proponent: datahead)
3. Release date of the 2.0.0 release (proponent: Quintus)
4. Translation tools and services (proponent: Quintus)
PLEASE SUBMIT MORE TOPICS FOR DISCUSSION! We don’t have the entire team
in real-time chat that often. Take this opportunity and submit some
topic that needs discussion and a binding result.
As usual, for each topic we shall try to find a consent. If this isn’t
possible, we shall vote on the topic. As we’ve not yet defined a proper
voting process, I’ve put that topic first on the schedule, and am going
to propose a voting procedure. By popular demand I’ll make a hopefully
more easy suggestion than what I send to the mailinglist recently (needs
are different in IRC anyway).
I’ll post a more complete announcement with more detailed information on
each of the topics and IRC modalities once we have the topics list
complete by say, 2015-03-16. Please object if you don’t like this
deadline.
If you submit a topic, thus please give a short paragraph of overview
that I can include into that announcement then so that even those people
who don’t have followed this discussion can get a short overview of
what’s going to be going on.
PLEASE SUBMIT MORE TOPICS FOR DISCUSSION!
Valete,
Quintus
--
Blog: http://www.quintilianus.eu
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung:
https://www.gnupg.org | https://de.wikipedia.org/wiki/GnuPG
My key fingerprint: | Mein Schlüsselabdruck:
B1FE 958E D5E8 468E AA20 | B1FE 958E D5E8 468E AA20
8F4B F1D8 799F BCC8 BC4F | 8F4B F1D8 799F BCC8 BC4F