Re: [tsc-devel] On the Continuation of TSC

Marvin Gülker | Fri, 22 Sep 2017 09:06:00 UTC

Hi everyone,

I am surprised by the mainly positive response to my rather
controversial message. I am relieved that nobody took it as an offense
regarding their work on TSC.

First of all, I of course value kirbyfan's activity on the AppImages
issue and have no intention to torpedo it. That specific issue is not
tied to the current codebase of TSC as it is concerned mainly with the
build system and I see no reason why such efforts could not be pulled
into a rewrite. I do have one note on this, though. It'd be nice if the
commit messages would be a little more useful :-)

Next, on the existing 2.1-dev code. I don't see myself working on 2.1
much, though I may lap into it every now and then. I will not veto any
work that anyone of you intends to do on 2.1. Given that the rewrite
will take a (very) long time, it is likely that if some of you work on
2.1 further, there can be a 2.1 release before the rewrite is
finished.

Following are some specific responses to datahead. I will further follow
up with a new thread on the shape of the rewrite in a new message.

Am 20. September 2017 um 22:05 Uhr -0500 schrieb Chris Jacobsen <…9@y…>:
> The development is slower than it was when Quintus was on board, though
> it is not dead.  Quintus was a bit more aggressive than the average
> developer when he developed.

I will not reach this aggressivity again I guess, but some kind of
continuous work on TSC is possible, with exceptions probably.

> Yes, I was a proponent against a complete rewrite.

Yes. You however have retracted from both work on the code and the
assistant lead position on your own free decision, so I felt that I can
go forward with my position nevertheless.

> Nothing is fruitless if you enjoy it.  I am sorry for effectively
> overturning a decision before, as doubling back on decisions tends to be
> counterproductive.  We could at least see how the rewrite goes and
> discuss it as it progresses.

Sure, I think we can do this.

Marvin

-- 
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F