[scribus-dev] correction needed recent commit r19543

["Christoph Schäfer"]

> Gesendet: Dienstag, 30. September 2014 um 22:18 Uhr
> Von: "Craig Bradney" <cbradney at scribus.info>
> An: scribus-dev at lists.scribus.net
> Betreff: Re: [scribus-dev] correction needed recent commit r19543
>
> On 30/09/2014 8:57 pm, Kunda Loves Scribus wrote:
> > On Tue, Sep 30, 2014 at 1:46 AM, "Christoph Schäfer" <christoph-schaefer at gmx.de
> > <mailto:christoph-schaefer at gmx.de>> wrote:
> > 
> >      
> >     And? Neither the bugtracker nor the commit list need to follow the rules of bureaucracy.
> >     Moreover, the developer mailing list and Mantis do record any changes reliably (let alone svn).
> >     Please don't try to turn Scribus into the equivalent of a public agency with obligatory,
> >     voluminous and unnecessary paper trails.
> >      
> >     You can be pedantic when it comes to Scribus itself, or licensing issues (I'm infamous for doing
> >     so), but we cannot waste our time by introducing bureaucratic rules that may suffocate development.
> >      
> >     Also: Please use Plain Text, not HTML, for your ML postings.
> >      
> >     Kind regards,
> >      
> >     Christoph
> >     *Gesendet:* Dienstag, 30. September 2014 um 00:18 Uhr
> >     *Von:* "Kunda Loves Scribus" <scribus.user at gmail.com <mailto:scribus.user at gmail.com>>
> >     *An:* "Scribus Dev Mailing List" <scribus-dev at lists.scribus.net
> >     <mailto:scribus-dev at lists.scribus.net>>
> >     *Betreff:* [scribus-dev] correction needed recent commit r19543
> >     Commit message for r19543 is actually #12733 and not #2733
> >      
> >     /Kunda
> >     _______________________________________________ scribus-dev mailing list
> >     scribus-dev at lists.scribus.net <mailto:scribus-dev at lists.scribus.net>
> >     http://lists.scribus.net/mailman/listinfo/scribus-dev
> > 
> > Hi Christoph,
> > 
> > re: Plain text
> > I'm usually thinking about such things. Honestly, I'm not fully used to using this type of ML
> > technology. Sometimes switching from between different types of lists that exist today can cause
> > some forgetfulness. These are things that I try to pay attention to as best as possible as well. As
> > for responding in pure text I need to examine gmail further to see if I can specify that. Will look
> > in to it. I'm pretty sure that reply to this email will _not_ send it in plain text. For just this
> > moment forgive me for doing so. 
> > 
> > re: bureaucracy
> > I see. Given your response I can feel that this is an important issue for you and therefore I'm
> > noting your position on it for future considerations. Though I am pretty certain that my intention
> > for pointing out what I was pointing out was purely out of 'future friendly' concern. In other
> > words, to be able to correctly and efficiently track down the correct revisions based on the commit
> > message. Also, I was following the intelligent behavior that has been modeled and that I've learned
> > to appreciate existing in the SVN commit process. 
> > 
> > Just to be clear, I have no intention of asserting my ego, quirks, or privileges on anybody let
> > alone 'suffocate development' or introduce unneeded protocols. I, just like all of us who
> > participate, want to see Scribus succeed. 
> > 
> > Now if you see behavior that you'd prefer me to reflect on and change I would be willing to listen
> > and examine your feedback. 
> > 
> > I am in agreement with you to keep Scribus as free as possible from bureaucracy. 
> > 
> > Thank you,
> > /Kunda 
> 
> Kunda - Please ignore Christoph in this case. :)
> 
> Christoph - lay off the war path :)


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: http://www.livhambrett.com/everything-i-know-about-germany-germans/what-i-know-about-germans/ (#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 ;)


No need to worry, though. I'm still relaxed and appreciate Kunda's work :)


Christoph