Website, domain and bugtracker(s)

[Riccardo Mottola]

Hi,

we need to think better about bug tracking. In my opinion it is one of 
the most important parts of a website. Not just for developers, but also 
for plain users who installed GNUstep with their distribution but 
experience a problem.

The original setup was very effective:
* single url: http://bugs.gnustep.org/ redirecting to savannah
* this single URL is prominently referred on the website, extremely easy 
to access ("one click")
* one single point of entry, leaving the user enter the bug and be 
classified later (how can the user know in which library the error is?)

I also note that savannah is still open and there are old open bugs as 
well as some new bug

Now we have a parallel bugtracking system which is being gradually or in 
parallel used since we use github.
* we don't have a bugtracker anymore! there is "one per project"
* given the above issue, we cannot easily make a "bugs.gnustep.org" link
* given the above, we cannot put a simple "report issue" on the website

What can we do to improve this major issue? This usability issue was not 
thought after when pushing github.

Foreword: I will regard any comment as "github war" as idiotic. I also 
know that savannah bug tracker is quite crude, but the github one isn't 
nice either compared to stuff "I use at work".

Some ideas:
1) use a third single tracking system which can allow a base root URL, 
shut down both savannah & github trackers
2) see if on github a "project" bugtracker can be activated and 
reference that from the base URL
3) stick to savannah
4) ignore the issue, declare bugs.gnustep.org dead, remove quick bug 
referencing from the website
5) create an intermediary "disambiguation" page which points to all 
separate github issue trackers and reference that as bugs.gnustep.org
6) <put your idea here>

right now, I can only think of 5) but it I find it ugly.
Also, who could update the bugs.gnustep.org redirect when we agree on a 
solution?


Riccardo