On Thu, Jun 08, 2017 at 02:01:22PM -0400, firstname.lastname@example.org 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). 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
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
PGP/GPG ID: F1D8799FBCC8BC4F