Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection of bugs for Gobolinux - central sites #1

Open
ghost opened this issue Aug 5, 2016 · 6 comments
Open

Collection of bugs for Gobolinux - central sites #1

ghost opened this issue Aug 5, 2016 · 6 comments
Labels
proposal Awaiting assessment question

Comments

@ghost
Copy link

ghost commented Aug 5, 2016

This does not fully fit into the "Documentation" area - my apologies.

We used to have the old mantis tracker at bugs.gobolinux.org

I assume that most people prefer git + github including the issue requests.

It probably may not be worth to manually carry over any old bug reports, since many things have possibly changed anyway:

http://bugs.gobolinux.org/my_view_page.php

May it be possible to have a similar collection of bug reports here? Something like an overview, with different components? Right now we do have the issue requests at Scripts, Recipes etc... but no simple way to see which are all the issues in general (unless I may be missing something; one thing that mantis had going was the overview part; in terms of usability, I consider the github issue request better due to a better interface).

PS: You may close this here at any moment in time. :)
(If nobody else does, I'll close it ~after a year or so.)

@AitorATuin
Copy link

Hello shevegen, I was talking with @lucasvr on irc last week and we both agreed that github is better for keeping issues (at project level if possible). We should add some doc in the Documentation project pointing users to each project issue page, explaining them also where to report a problem.
We also agreed that is really interesting what you exposed about the convenience of having a general overview of the issues that are opened but keeping two systems is going to be a big mess imho. We were thinking about creating a project for each release (016 next one) where we can keep the issues that are too general to fit in any project. What do you think? /cc @hishamhm @mwh @detsch

@lucasvr
Copy link
Member

lucasvr commented Jan 8, 2017

Please note that the search interface at Github enables one to list all open issues at once:
https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Agobolinux

It's also possible to filter by specific projects:
https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+repo%3Agobolinux%2FScripts

What's missing now is just an interface to collect the output of that search and render it into a nice web page. Any volunteers?

@hishamhm
Copy link
Member

hishamhm commented Jan 8, 2017

What's missing now is just an interface to collect the output of that search and render it into a nice web page.

What's not nice about that first link? I can't really think of any way to improve it.

@lucasvr
Copy link
Member

lucasvr commented Jan 8, 2017

The output itself looks good, but I wanted to have a link on our github page pointing to that very query. Right now we either need to bookmark that page or fill-in the search terms every time we want to look at all the bugs.

@lucasvr
Copy link
Member

lucasvr commented Jan 8, 2017

Alternatively, we could simply create a link to that page on gobolinux.org/community.html.

@hishamhm
Copy link
Member

hishamhm commented Jan 8, 2017

Alternatively, we could simply create a link to that page on gobolinux.org/community.html

That works, but note that this is not the best entry point for users. There's no "new issue" button there; they still have to find the correct project and enter the issue. I added CONTRIBUTING.md pages to the various projects so that they get an intro note when posting a bug — haven't had issues posted to the wrong repo since.

@Nuc1eoN Nuc1eoN added proposal Awaiting assessment question labels Oct 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Awaiting assessment question
Projects
None yet
Development

No branches or pull requests

4 participants