11Fermer13
Kevin KoflerLe 21/09/2009 à 00:20
Lionel Debroux (./11) :
We've already written many times that we got soooo tired up by most of our ideas and wished being rejected as a whole by you, the sole remaining member of TIGCC, that we gave up.

Why didn't you (all of you) ask yourself why your ideas and wishes got rejected? Or actually bothered reading my replies where I've always given the reason? You're just too proud to realize that not all your ideas are actually good ideas.
When you announced completely irrealistic todo list items (on which you have made zero
progress, more than one year and a month later, and counting !)

Such as? Getting KTIGCC working with kdewin isn't unrealistic at all and most likely we'd already be there if you guys helped with it instead of forking TIGCC and working on pointless things such as your unnecessary changes to the build scripts (e.g. changing #!/bin/bash to #!/bin/sh and then having to change stuff like echo -n; there was no bug there, as echo is a bash builtin, so echo -n is always available in a #!/bin/bash script!)…
while there are much more pressing issues on TIGCC

Such as? TIGCC 0.96 Beta 8 is very reliable, there are just a few minor bugs to fix.
(on a side note, hardly any of those have been tackled by you - of your six commits in TIGCC since January 2009, four are GCC4TI backports that tackle some of them, and the two others are trivialities), we said "let's do something together".

Why not together with me? Because I didn't let one of you become the head of the project out of the blue? Sorry, things don't work like that, as a new contributor, you start by sending patches, then you get commit after approval and only when you earned the trust of the existing contributors, you can get full comaintainership. (But of course, after what you did, none of you will ever get that level of trust. You should have thought of the consequences of your actions before doing them.)
That's what we did, and we left you alone in the dust.

You are the ones left alone in the dust, TIGCC is the real TIGCC, GCC4TI is just crap nobody uses.
If it wasn't enough, several months later, you've tried to turn TIEmu and TILP into a dictatorship (by flat out refusing to cooperate with someone who went in through meritocracy), thereby negating all of Julien's and Romain's good work and good relationship towards the community - and added yourself a lot of workload and unneeded work by forking them. Good job.

That's a complete misrepresentation of what happened to those projects. What did happen is that you got Julien and Romain to add you after sending a few minor contributions. (IIRC, the patches you sent before getting commit access can be counted on one hand, and they were all fairly small changes, some even buggy and incomplete (the IMG_INFO changes, which you've still not fixed, by the way).) Those folks never bothered to ask the other existing contributors (Tyler and me) for whether they trust you (hint: we don't, see above).

And then Julien and Romain not accepting me as Romain's successor even though I've been the #2 contributor after him for years, and also ignoring Tyler (the original author of the Group File Manager) was just too much. We still see ourselves as the legitimate successors of the old LPG, your projects as forks and you as usurpators of the project names.
What are you exactly trying to do with this kind of statements, Kevin ? Pissing us off so we moderate your posts or even ban you from this board ? No way, sorry wink

I'm just telling the truth.