You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, trophy ideas, or ways to improve the website, or report bugs.
Github: It is not intuitive to require a user to sign up to and navigate through github to report issues. The repo is primarily for people interested in development.
junethack: This is somewhat intuitive, however it is a fleeting medium and issues reported here are either dealt with in passing or forgotten unless also reported at github. NB: If at the time of reporting the reporting user happens to meet with a developer who is present, capable and willing to solve the issue at that moment, it may be solved at that point, however:
this does not happen often (present, capable and willing)
this does not take advantage of the whole team's knowledge to provide an answer
this is not visible to future developers looking back at previous years' projects unless it was also noted in the log or issues page.
Suggestions
Add a feedback/contact form on the website itself that would post issues to github
Allow a bot in #junethack to post issues to github (would require moderation)
Allow a bot in #junethack to collect suggestions and feedback from users for later perusal by developers willing to register or deal with the issues themselves.
The text was updated successfully, but these errors were encountered:
@stenno suggests a form on the website to provide for users suggesting trophy ideas. The suggestions would then be displayed publicly for users to vote on to be implemented for the next year. He thinks this part would also not be difficult to implement, having a similar functionality to the qdb.
For example, trophy ideas, or ways to improve the website, or report bugs.
junethack: This is somewhat intuitive, however it is a fleeting medium and issues reported here are either dealt with in passing or forgotten unless also reported at github. NB: If at the time of reporting the reporting user happens to meet with a developer who is present, capable and willing to solve the issue at that moment, it may be solved at that point, however:
Suggestions
The text was updated successfully, but these errors were encountered: