<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Oct 1, 2014 at 12:32 AM, "Christoph Schäfer" <span dir="ltr"><<a href="mailto:christoph-schaefer@gmx.de" target="_blank">christoph-schaefer@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> Gesendet: Dienstag, 30. September 2014 um 22:18 Uhr<br>
> Von: "Craig Bradney" <<a href="mailto:cbradney@scribus.info">cbradney@scribus.info</a>><br>
> An: <a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
> Betreff: Re: [scribus-dev] correction needed recent commit r19543<br>
<div><div class="h5">><br>
> On 30/09/2014 8:57 pm, Kunda Loves Scribus wrote:<br>
> > On Tue, Sep 30, 2014 at 1:46 AM, "Christoph Schäfer" <<a href="mailto:christoph-schaefer@gmx.de">christoph-schaefer@gmx.de</a><br>
> > <mailto:<a href="mailto:christoph-schaefer@gmx.de">christoph-schaefer@gmx.de</a>>> wrote:<br>
> ><br>
> ><br>
> > And? Neither the bugtracker nor the commit list need to follow the rules of bureaucracy.<br>
> > Moreover, the developer mailing list and Mantis do record any changes reliably (let alone svn).<br>
> > Please don't try to turn Scribus into the equivalent of a public agency with obligatory,<br>
> > voluminous and unnecessary paper trails.<br>
> ><br>
> > You can be pedantic when it comes to Scribus itself, or licensing issues (I'm infamous for doing<br>
> > so), but we cannot waste our time by introducing bureaucratic rules that may suffocate development.<br>
> ><br>
> > Also: Please use Plain Text, not HTML, for your ML postings.<br>
> ><br>
> > Kind regards,<br>
> ><br>
> > Christoph<br>
> > *Gesendet:* Dienstag, 30. September 2014 um 00:18 Uhr<br>
> > *Von:* "Kunda Loves Scribus" <<a href="mailto:scribus.user@gmail.com">scribus.user@gmail.com</a> <mailto:<a href="mailto:scribus.user@gmail.com">scribus.user@gmail.com</a>>><br>
> > *An:* "Scribus Dev Mailing List" <<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
> > <mailto:<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a>>><br>
> > *Betreff:* [scribus-dev] correction needed recent commit r19543<br>
> > Commit message for r19543 is actually #12733 and not #2733<br>
> ><br>
> > /Kunda<br>
> > _______________________________________________ scribus-dev mailing list<br>
> > <a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a> <mailto:<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a>><br>
> > <a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" target="_blank">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br>
> ><br>
> > Hi Christoph,<br>
> ><br>
> > re: Plain text<br>
> > I'm usually thinking about such things. Honestly, I'm not fully used to using this type of ML<br>
> > technology. Sometimes switching from between different types of lists that exist today can cause<br>
> > some forgetfulness. These are things that I try to pay attention to as best as possible as well. As<br>
> > for responding in pure text I need to examine gmail further to see if I can specify that. Will look<br>
> > in to it. I'm pretty sure that reply to this email will _not_ send it in plain text. For just this<br>
> > moment forgive me for doing so.<br>
> ><br>
> > re: bureaucracy<br>
> > I see. Given your response I can feel that this is an important issue for you and therefore I'm<br>
> > noting your position on it for future considerations. Though I am pretty certain that my intention<br>
> > for pointing out what I was pointing out was purely out of 'future friendly' concern. In other<br>
> > words, to be able to correctly and efficiently track down the correct revisions based on the commit<br>
> > message. Also, I was following the intelligent behavior that has been modeled and that I've learned<br>
> > to appreciate existing in the SVN commit process.<br>
> ><br>
> > Just to be clear, I have no intention of asserting my ego, quirks, or privileges on anybody let<br>
> > alone 'suffocate development' or introduce unneeded protocols. I, just like all of us who<br>
> > participate, want to see Scribus succeed.<br>
> ><br>
> > Now if you see behavior that you'd prefer me to reflect on and change I would be willing to listen<br>
> > and examine your feedback.<br>
> ><br>
> > I am in agreement with you to keep Scribus as free as possible from bureaucracy.<br>
> ><br>
> > Thank you,<br>
> > /Kunda<br>
><br>
> Kunda - Please ignore Christoph in this case. :)<br>
><br>
> Christoph - lay off the war path :)<br>
<br>
<br>
</div></div>Im not on a war path, but I must admit I love to fight government and corporate bureaucracies -- remember that I'm living in the land of red tape. If in doubt, look at this Australian's humourous description: <a href="http://www.livhambrett.com/everything-i-know-about-germany-germans/what-i-know-about-germans/" target="_blank">http://www.livhambrett.com/everything-i-know-about-germany-germans/what-i-know-about-germans/</a> (#80 and 81, both very true) ;) When I smell demands for an action that doesn't make sense, but simply serves bureaucratic pedantry, all alarm bells start ringing. Thus, demanding that a typo in a commit message must be corrected automatically triggers a NO in super-sized capital letters, bold and italics ;)<br>
<br>
<br>
No need to worry, though. I'm still relaxed and appreciate Kunda's work :)<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Christoph</font></span></blockquote><br>Thanks fellas :)<br><br>Christoph, pretty funny link. I had this visual of you actually rolling around in freshly printed Scribus SVN commit messages enjoying the scent of the fresh paper and ink. Now if I could just find a squeegee to clean my minds eye of that visual, that would be great.<br><br>I appreciate everybody's work as well. Onward!<br><br>Tschüss!<br>/Kunda<br></div></div></div>