Re: git maintenance bug tracker sooner better than later

[Johannes Gilger <heipei@hackvalue.de>]

On 2009-02-04, jidanni@jidanni.org <jidanni@jidanni.org> wrote:
> Anyway, I have this file
>   -rw-r--r--  1   19561 2009-01-13 03:26 DietCherries17
> where I have 17 tiny documentation patches that sent to
> git@vger.kernel.org but nothing happened.

As I recall a lot of those things were replied to (at least for the 
first few patches) as being not quite right (or plain wrong). Once you 
even said "oh, if you could fix this for me before applying it". At some 
point the time it takes to review patches and to write a quick fix for 
the bugs/typos yourself stands in no relation whatsoever.

> Perhaps I could send them to a volunteer who could see if any of them
> are useful and then do something with them. Thanks.

Or you could make one big "typo-fix"-patch out of them and one 
"i-didnt-understand-the-manpage-there"-patch. Then these patches could 
be reviewed and you could revise them.

A second solution would be to tackle real problems, earn the respect of 
the maintainer and those close to him, have your patches merged and 
_then_ when you come up with nitpicks about documentation, those people 
would be sure of your abilities and would put more trust in you to not 
mess up when writing documentation.

About the bug-tracker-thing: I am quite happy that git is one of those 
projects where everything happens in one spot: Development, 
bug-reporting and general discussion. It makes it a lot easier than 
disconnected systems where information is easily duplicated and becomes 
stale at other ends.

But that's just my oppinion,
Greetings, Jojo

-- 
Johannes Gilger <heipei@hackvalue.de>
http://hackvalue.de/heipei/
GPG-Key: 0x42F6DE81
GPG-Fingerprint: BB49 F967 775E BB52 3A81  882C 58EE B178 42F6 DE81