Hi!
No, not happy~!
On Wed, Jun 18, 2008 at 8:38 PM, Alex Ionescu <ionucu(a)videotron.ca> wrote:
Man, I wonder where you guys were when I was getting
shit for breaking
the kernel due to *valid* changes.... and cooperating.
LOL! I was there giving you a hard time on IRC.. See,,, I understand
where you are going with the changes so I did not go out of my way to
kill your access to the project. The outcomes in the future out weight
the short term. That was 2006, now we see~
I love Greatlord but, it's not the fact he's
breaking stuff that I
think Aleksey is tired off... it's breaking stuff, promising to
change, and then still break stuff. Looking over commits, I don't
think anyone has broken the OS more than Greatlord except myself. I
also don't think anyone has committed more code than myself (And
probably w3seek). So yes, there does seem to be a valid proportion.
Both greatlord and I were massive regressors, but also massive
changers... that doesn't make it RIGHT though. It was probably wrong
even during my time... I can't get away by saying "ah yes, but my
changes were correct!!!!". So I will probably say that lenience was
given to me (not always though, I did get into some pretty big
fights)...
For some reason he started committing on anger and stop testing the
changes. Before I could stop him it was all done. Afterward he left
IRC and was off line for awhile. So things stayed broken and I could
not go fix it, since I was called in to work that day.
Greatlord's breakage of the trunk, although
proportional to his
commits, reflects a bigger problem -- your development model SUCKS,
and you need to fix it. So I don't think Aleksey is being -unfair-...
I think he's incorrectly attacking the person who "abused" the relaxed
rules the most... what he should REALLY fix is the rules themselves,
because any other dev in Greatlord's position would've probably acted
the same. Greatlord is just being the scapegoat.
I like Magnus and he has become a good friend and project colleague.
I've broken my share too and I always, oneway or another come around
to fixing them.
The spelling thing does come off as a bit raciest. Due to my relapse
into predictive programming.
The development model? I'm to busy to worry ATM.
James