2008/2/2 Aaron J. Seigo <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>>:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Friday 01 February 2008, Sebastian Sauer wrote:<br>> The reason why I cc-mailed <a href="mailto:panel-devel@kde.org">panel-devel@kde.org</a> on commit r769216 was btw<br>> for review-purpose and it was working very well and rather fast. The code<br>
> was in the repositry and ppl could try it out without first<br>> downloading+applying a patch + I even got a hint that this triggers another<br>> bug what in turn lead me to fix the other bug.<br><br></div>i understand where you are coming from. however, this is not how we work<br>
together on this code base. your commits in this case have become<br>increasingly wrong, revision by revision. you're not actually working faster,<br>you're just working wronger (ok, that's not a word). please get these things<br>
peer reviewed, because right now there's now a small mess to sort out that<br>should never have gone in this way.<br><div class="Ih2E3d"><br>> That all was done in rather short time and if I compare that with how some<br>
> commercial development happens (review, documentation, bunches of ppl<br>> involved, lot of "wait-time" till you are able to continue to work on<br>> something and probably you even can't let the solution grow in svn but need<br>
> to have a perfect solution before beeing able to ask for review, etc.) then<br>> it's not only faster but also more direct.<br><br></div>evidently you've missed how quickly plasma has been developing, then. because<br>
it goes quickly. most importantly, it usually goes quickly in good directions<br>rather than randomly this way or that.<br><br>you may have gotten quicker to where *you* wanted it to go, but your patches<br>in this stream have been full of incorrect changes that now other people will<br>
have to go through and fix or at the very least point out the issues to you<br>so that you can fix them.<br><br>honestly, i'm just going to go through and fix the problems. so you've ended<br>up wasting other people's time in a way that was completely unnavoidable.<br>
<br>so regardless of what you personally feel, believe or think about this process<br>as a whole ... stop barreling ahead and start working with the others working<br>on plasma. there are several of us, and if we would like that to continue<br>
it's pretty important that we:<br><br>* ensure the code base does not become a piss pile of hacks that make it<br>unpleasant to hack on and difficult to maintain (your patches here fail in<br>this way)<br><br>* coordinate our efforts so we don't duplicate efforts and annoy each other<br>
(ruphy's time has been wasted here)<br><br>* try to remember that this isn't your own personal project but that of a<br>group<br><font color="#888888"><br>--<br>Aaron J. Seigo<br>humru othro a kohnu se<br>GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>KDE core developer sponsored by Trolltech</font><br></blockquote></div><br>Ok, now Aaron, please breath, and calm down. :-)<br><br>We don't want to piss off our other Sebastian, no? ;-)<br><br>Sebastian, nothing happened for now, remember for next time that, for non-trivial changes <br>
to the lib, please submit the patches into the nifty tool we just got set up. =)<br><br>And please do! I wanna try out the new toy! :D<br>I want to review some non-lame patches, comment them, commit, and have fun! =)<br>Please, do it for me as a personal favour, pleeease!!!! :D<br>
<br>Wow, 1 smiley per sentence! :D What a funny mail! :P<br><br>Okokok sebas... I'll stop smoking your crack. ;-)<br><br>Bye,<br clear="all">-Riccardo<br>-- <br>GPG key:<br>3D0F6376<br>When encrypting, please encrypt also for this subkey:<br>
9EBD7FE1<br>-----<br>Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平<br>Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch<br>Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화