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

Sydney Dykstra | Thu, 21 Sep 2017 00:43:02 UTC

 I would like to see this project thrive, as we all would, but I am not
in a personal position to start doing major things for the project, and
I also don't know a great deal about coding.

 Either way, whatever happens I will back up this project (unless
someone does something major I don't agree with, of course, but I don't
see that happening any time too soon) and help out where I can, as I
have been in the past.

Re: Ryan, I'm not sure if there any bandwidth limitations that we can
excede with the Project's server, but I don't see why we couldn't host
the Appimages on it. If that is not doable, I might be able to host them
on my personal VPS, but I am limited to 1TB of bandwidth per year, so we
would have to make them weekly or something. Or I could pay for more
bandwidth... that always fixes things. I also only have about 5GB of
free HDD space left. But it would work.

-Sydney

On 09/20/2017 06:16 PM, …9@g… wrote:
> FWIW I *have* been doing some work on trying to make AppImages, though I
> got stuck at finding a hosting provider that would handle ~200MB
> Travis-generated images...
> 
> 
> --
> Ryan (ライアン)
> Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
> http://refi64.com
> 
>> On Sep 20, 2017 at 9:47 AM, <Marvin Gülker
>> <mailto:…r@p…>> wrote:
>>
>> Hi everyone,
>>
>>
>>
>> since I retired from the lead position, there has not been much move in
>>
>> TSC's development; taking a look at `$ git log' for `devel' proofs
>>
>> that. xet7 and I have recently met in Finland (physically) and have
>>
>> spoken about the matter; in that, xet7 outlined that his main focus is
>>
>> -- rightly, as he commercially uses it -- on Wekan. kirbyfan has assumed
>>
>> the position as assistant lead, but that was about it (no offense; I
>>
>> know this is free time).
>>
>>
>>
>> During the last months, I have observed what happens around TSC when I
>>
>> abstain from it mostly, and found that it wasn't much. This inevitably
>>
>> must lead to the project's death.
>>
>>
>>
>> This finding entitles me to make a suggestion. I cannot and will not
>>
>> return to work on TSC as intensly as I did earlier, for my studies have
>>
>> taken over most of my time. I however intend to do *something*, which is
>>
>> more in any case than what has happened here in the last months. I have
>>
>> often enough made my position towards the current codebase clear and
>>
>> have been met with opposition by people who are now not working on
>>
>> materialising their view of TSC. I feel the desire to experiment with
>>
>> something new. My suggestion is that therefore, I will start the
>>
>> previously mentioned rewrite. I invite everyone to join or to oppose,
>>
>> but in order to have a word in the decisions made in that rewrite I
>>
>> think you should actually contribute to it in the part you want to
>>
>> decide something on[1].
>>
>>
>>
>> Someone is going to point out that this is fruitless effort, as I don't
>>
>> have the time I used to have and a rewrite takes time. Surely this
>>
>> person is correct, but this is not the entire story. If I don't do the
>>
>> rewrite, I won't work on the current state of TSC either because --
>>
>> sorry -- I don't feel like doing so; it is my hobby free time after
>>
>> all. Thus, nobody would work on it. This would be fruitless as well. TSC
>>
>> is not meant to fulfill any kind of commercial requirement; the coding
>>
>> on it should be hobby, thus fun and goal in itself.
>>
>>
>>
>> I want to blow some fresh air into the stalled development. Accept the
>>
>> rewrite as a baseline, come and sit down with me scatching how the new
>>
>> TSC should be coded. If you don't want, I will fork.
>>
>>
>>
>> Marvin
>>
>>
>>
>> [1] Personally, I have come to the conclusion that the Voting Rules are
>>
>> too formal for a small project. The idea of a law student in early
>>
>> semestres. We should abandon them in favour of the mentioned approach;
>>
>> if you want it formally, we can vote on the abondonment of the Voting
>>
>> Rules (which would require a 2/3 majority as outlined in the Voting
>>
>> Rules).
>>
>>
>>
>> --  
>>
>> Blog: https://www.guelkerdev.de
>>
>> PGP/GPG ID: F1D8799FBCC8BC4F
>>
>>
>>