Bug reporting method too hard to find

Bug reporting method too hard to find

[Francis Irving]

I could not find out how to report a bug. In the end, a colleague
had to tell me.

Some suggested improvements:


1) Explicitly mention the word "bug" on the home page, or have
a page which Google will find called "Reporting bugs".


2) I did eventually get to the Community page:
http://git-scm.com/community

Alas, when I scanned the headline "Mailing List" I ignored that
whole section because I didn't want to join a mailing list - I just
wanted to report a bug.

I'd call it maybe "Mailing List and Bug Reporting". Or have a 
separate bugs section below called "Bug Reporting" which refers
to the mailing list.


3) I definitely wasn't going to subscribe to a mailing list to report
a bug (no idea why - I'm just reporting my instinct which lots of
people likely have). 

I am only doing so because I saw that I don't have to subscribe.

I'm not sure how to make it clearer, but it needs to be as it is
highly unintuitive. These days, you have to join most email lists to
post to them.


This all matters, because Git is likely losing lots of basic bugs,
particularly ones to do with usability for beginner users.

Thanks for a great tool!

Francis

Re: Bug reporting method too hard to find

[Jeff King]

On Wed, Oct 29, 2014 at 11:58:57AM +0000, Francis Irving wrote:

> I could not find out how to report a bug. In the end, a colleague
> had to tell me.

Thanks for your suggestions; they all seem like improvements.  I just
opened:

  https://github.com/git/git-scm.com/pull/462

which implements most of them. Unlike development of git itself, which
happens on the mailing list, development of the website is centered
around that GitHub repository; if you have further suggestions for the
site, they'll probably get more attention by opening an issue there.

-Peff