As mentioned in the issue, should sidebar indicate proper way to report bugs on Github?
agree. never saw answers in #bug posts. useless thing.
tags are not federated correctly and we can loose messages that way. The only good point is, if someone post on diaspora, other users will probably answer him. so it will not overload github (especially if it is a duplicate) and it can be done in the mother tongue of the user
Some instruction might be nice, like: Use #bug to discuss potential bugs in diaspora*, report bugs at [link to Github]
There are instructions at https://wiki.diasporafoundation.org/How_to_report_a_bug - so perhaps we need to link to that.
I suggest that the instructions in the side-bar should be to post first on diaspora*, and then once the bug has been confirmed by others (preferably including people on other pods), report it on Github, with details.
I have refactored the right bar now I can work on that. @goob any concrete mockup?
I'm against keeping a suggestion to first post and wait for answer and only then report bugs. This path leads to user dissatisfaction as the bug will never get fixes.
The only way to get bugs to developers is to tell people to register bugs in the bug tracker. Promising any other ways for bugs to be looked at is just lying :) Please let's abolish the #bug and #feature tags - we shouldn't promise to users that any action will be done when they post with either of them.
The idea of linking to the wiki is a good idea, supported. But let's abolish the tags. It's common to point users to bug trackers - because it is the only way bugs will surely end up for tracking.
I am certain that giving the average user instruction to discuss bugs on Github will result in more ordinary features being reported than actual bugs. I don't think that Github is the place for the annoyingly high number of complaints about how diaspora was designed to work.
I agree with Seth. d* may (hopefully) grow to millions of users including less tech oriented people, and git is not the place to report bugs for everyone. Users may overwhelm it with duplications, feature requests and things which a are not actually bugs.
From what I've seen, people using the #bug tag many times do get replies from more experienced users, so it's not so bad.
I'd say let's keep the #bug and #feature tags for casual reports, and provide a link to the wiki article which should expain what is gut and exactly how bugs should be reported to it.
I'm going to prepare a mockup