Position rotation and secretchronicles.de domain
by Marvin Gülker
Hi everyone,
since nobody expressed interested in a GD, there is no reason to hold
one. What remains can be managed via the ML.
xet7 has offered to take over the project lead position and take over
the old secretchronicles.de domain indefinitely. Since I believe that
everyone should have a chance to take the position, I want to publically
ask whether this is fine or whether someone else is interested as
well. The only requirement for application is that you're a TSC team
member and have too much time available™.
Please apply for the project lead position until 2017-04-09 00:00 UTC by
publically posting your application here on the mailinglist. If
required, a vote will be held subsequently. Whoever takes over will
receive all rights that I have (and has the not really nice task to talk
to our sponsor and tell him that he takes over the server).
The project lead position means managing the tracker, asking people to
do things, hang around in the chatroom and answer any questions that
might arise in the forum. Release planning is also a thing. The
assistant lead helps with all of that, so you don't have to do it all
alone. The probably most important duty is to ensure the project does
not enter a “sleep” state where everybody loses interest.
I am going to transfer the old secretchronicles.de domain to xet7 anyway
unless someone objects, because he's responsible for the administration
anyway already.
If it's desired, I can further maintain TSC's bank account, but since as
of now exactly no income was generated there, I will cancel it as soon
as its balance reaches zero. It currently has 12,53 EUR on it, monthly
upkeep is 2 EUR.
Valete,
Marvin
--
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F
1 year, 12 months
Assistant lead position rotation
by xet7
Hi everyone,
datahead has resigned as assistant lead, as he needs to
concentrate finishing his game. I thank him for all his work
as assistant lead. He will still be aroúnd for some changes
to TSC, but won't be merging pull requests or managing issues.
This opens up assistant lead position for new applicants.
The assistant lead position means helping me managing the
tracker, asking people to do things, hang around in the
chatroom and answer any questions that might arise in the
forum. Assistant lead also helps with release planning.
The probably most important duty is to ensure the project
does not enter a “sleep” state where everybody loses
interest, so assistant lead needs to remind me what needs
to be done, on IRC or email.
Please apply for the assistant lead position until
2017-06-25 00:00 UTC by publically posting your application
here on the mailinglist. If required, a vote will be held
subsequently.
BR,
xet7
2 years, 1 month
Re: Re: Re: [tsc-devel] Assistant lead position rotation
by rymg19＠gmail.com
👍
As for the IRC...the main difficulty is just that, given that I have
college work to do, it's really impractical to have my IRC client open too
often. (That's why I've taken to liking Discord and Gitter: they both show
what's new since your last visit, and the latter sends out emails on new
messages.)
--
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jun 8, 2017 at 1:42 PM, <Marvin Gülker <m-guelker(a)phoenixmail.de>>
wrote:
On Thu, Jun 08, 2017 at 02:01:22PM -0400, rymg19(a)gmail.com wrote:
> ...ok, I've been doing a lot of thinking, and I'd like to volunteer to be
> assistant lead.
Whoa, chapeau! I am honestly surprised, and I do wish you all the
best. Your and xet7's difficult task will be the permanent project
steering: making the release plan, make people implement the
plan. Respond to PRs (yes, we get external PRs, see here[1]). Keep
people motivated. Dig out old issues from the tracker. Hang around in
the IRC channel (yes sometimes new users crop up there). And so on. And
then there needs to be some coding, because all planning is void if
there comes no code. Keeping TSC alive is possible, but it requires that
someone dedicates a substancial amount of time to the project with the
definite goal to do something with it.
I remain further available until I tell otherwise, but other than that,
my situation has not really changed. I cannot contribute code in the
magnitude I did before, but I will do my best in answering any questions
on the current codebase, and taking part in discussions. But this alone
is not enough to keep the project alive. On a side note, I am currently
planning to meet xet7 in person later this year and we will surely have
opportunity to talk about TSC.
kirbyfan, if you really assume this position, you should be around in
IRC more often. New ideas are often given birth there before they are
laid out in detail on the ML or (more often) the tracker. It's true that
it can happen that there are days of nothing happening, but one can
usually passively hang around and have the IRC client print a
notification if one's nick is mentioned. Feel free to just start some
smalltalk to one of the team members there, the channel logs reveal
we're not always on topic. It helps strengthening the social
relationship anyway.
And, if you indeed want to pursue further development of TSC, persuade
xet7 to finally get the infrastructure upgrade through since Debian
Wheezy is about to fall out of support :-)
> Admittedly, this seems kind of random (and partly pointless, as my
> motherboard is incapacitated ATM...), but I really think this project has
> too much potential to just "die".
I share your views. If you are ready to place your energy into the
project, it may work out. We at least have been noticed.
> That being said, I do think maybe a full rewrite of the codebase would be
> impractical at this point, but I really think it's possible to try and get
> a release out. I mean, Final Fantasy I had a single programmer. There's no
> way this can fail, especially given that we have a capable (crappy, and
> horrible, but capable) engine already in place.
A nice description of TSC's current state. Regarding rewrite, I will
support whatever the rest decides. I have no right to make a decision
without contributing.
Greetings
Marvin
[1]: https://github.com/Secretchronicles/TSC/pull/612
--
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F
2 years, 2 months
Re: Re: [tsc-devel] Assistant lead position rotation
by rymg19＠gmail.com
...ok, I've been doing a lot of thinking, and I'd like to volunteer to be
assistant lead.
Admittedly, this seems kind of random (and partly pointless, as my
motherboard is incapacitated ATM...), but I really think this project has
too much potential to just "die".
That being said, I do think maybe a full rewrite of the codebase would be
impractical at this point, but I really think it's possible to try and get
a release out. I mean, Final Fantasy I had a single programmer. There's no
way this can fail, especially given that we have a capable (crappy, and
horrible, but capable) engine already in place.
:(
--
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jun 7, 2017 at 9:43 AM, <Marvin Gülker <m-guelker(a)phoenixmail.de>>
wrote:
On Wed, Jun 07, 2017 at 09:25:12AM +0000, xet7 wrote:
> datahead has resigned as assistant lead, as he needs to
> concentrate finishing his game.
Ah. I understand this decision, but unless sydney or kirbyfan are
determined to pursue TSC to the next release now, I expect the position
will stay vacant. The team falls apart; I have doubts there will ever
be a 2.1 release. A shame it is! But that is they way open-source
projects go. We should probably admit this and give the project a
proper burial rather than having it die away slowly.
I hope that we as the team can stay in contact further even aside of
TSC. Maybe we can even join again our forces on a different project.
Greetings
Marvin
--
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F
2 years, 2 months
