Re: Re: [tsc-devel] Assistant lead position rotation

datahead | Sat, 10 Jun 2017 05:37:47 UTC

> It is not a question of motivation, but of time. Regardless which route TSC takes, I do not gain more time for the project from it. After law school I am probably going to be even thinner on time than I am now.

Motivation may have been poor word choice, though I mistakenly assumed you might not be as encouraged to work with the code after law school due to its currently bad state.  I fully understand what you are saying about time.

On another note, it is perfectly fine if you eventually reach a point where you conclude that you have spent enough time with TSC and just need to move on; you have already done a lot for the project.  I was planning on probably cutting my own time back a lot after release 2.1.

> I disagree. Both cases were about getting rid of legacy dependencies that would have prevented getting TSC to run at all on modern distros due to lack of inclusion of those dependencies in them. There was no choice but doing them first.

I have no doubt it all needed to get done; I just think that two releases would have broken it into more bite size chunks and put team focus on testing and resolving each of them, as well as draw the community more into our testing.  Instead we got bogged down a bit with bug resolution.