<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/09/2013 04:48 AM, Frank Lanitz
wrote:<br>
</div>
<blockquote
cite="mid:20130609134848.2c274d72369643258c83edc1@frank.uvena.de"
type="cite">
<pre wrap="">On Sun, 09 Jun 2013 03:54:05 -0700
Roger Booth <a class="moz-txt-link-rfc2396E" href="mailto:rbooth@kabooth.com"><rbooth@kabooth.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I assume you are surprised by this. How dare the user of our docs not
study to great lengths the implementations of the shit we (and others
that have come before us) have produced. Nobody should have the
effrontery to attempt to interface our code without spending a
sufficient amount of time appreciating the edifice we have erected.
</pre>
</blockquote>
<pre wrap="">
Please don't be a party-puper. Geany is FLOSS and everybody is welcome
to improve ... also the documentation. You recognized that the
documentation might not be clear in all cases. .. yepp. That's true.
But it's hard to find such things for somebody who knows the code from
deep inside the heard that Geany-Version -> API-Version -> ABI-Version.
so no need to document it for them.
Please take a look at github and improve the parts of documentation.
Complaining on the mailing list that the whole documentation suckz just
is making people spending a lot of spare time sad and sending them into
aggro-mode.
Would be really happy to see a patch improving that aspect from
documentation as well as the Plugin-HowTo.
cheers,
Frank
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.geany.org">Devel@lists.geany.org</a>
<a class="moz-txt-link-freetext" href="https://lists.geany.org/cgi-bin/mailman/listinfo/devel">https://lists.geany.org/cgi-bin/mailman/listinfo/devel</a>
</pre>
</blockquote>
Me? party-puper? Not! :-) <br>
<br>
Geany is a great editor - the best I've found since I switched to
Linux. The documentation is best of class. But I saw there were a
few places where fixes could be suggested. Because it is FLOSS I did
feel that I should contribute and I did. I have submitted
documentation patches for the editor documentation. If my patches
are accepted, there will be no more "to to"s and no more "Furter"s
(at least the instances I caught).<br>
<br>
But my last submission of patches left me a bit confused.<br>
<br>
I know *git* is a version control thingie. So be it. I don't do
version control. So my preferred submission method is via patch
file. So I submitted patches. And got zero feedback.<br>
<br>
What should I expect?<br>
<br>
If I do this, if I submit patches to, in my opinion, write the best
damn doc about versions ever written, who reads and edits my tome
(not that it would ever need editing:).<br>
I edited the text file documenting the main Geany editor and
submitted the patch file and I haven't heard boo about it since.
Maybe I screwed it up. OK, tell my what I did wrong and I'll do it
over and fix it. Maybe you / they don't like the edits I made. OK,
lets talk. Why don't they like the edits? etc.<br>
<br>
Its frustrating to submit changes that just seem to get filed in the
garbage.<br>
</body>
</html>