OpenUserJS
Adding Discuss (and Review) Section to Scripts
Sometimes people are looking for some features and these features are not issues(just ideas or questions), so logically it would be good to add Discuss Section (Almost identical copy of Issues Section).
Also Script Reviews would be good solutions to understand users opinions on this or that script.
What do you think?
P.S. I can implement it, if you'll accept this idea.
( https://openuserjs.org/corner/I_suggest_adding_Discuss_%28and_Review%29_Section_to_Scripts )
This is actually two issues:
-
I believe that @sizzlemctwizzle has already stated that the Issues section of a script are a type of Discussion and is inclusive to promotion of changes to a script and other questions and ideas. See also some definitions of "Issue" that may be applicable at http://dictionary.reference.com/browse/issue
-
Review discussions is related to #461. It is being considered that a modal prompt be presented on down voting and is part of https://github.com/OpenUserJs/OpenUserJS.org/issues/262#issuecomment-57592127
-
I have a feeling it's a stronger word than needed, few users that use my CFS send me private letters discussing needed features, after that why I've written: "Guys, please leave new features requests, comments and bug reports in Issues section." I only came back on working with it, and found absence of reviews and discussion section a bit of a problem for communication. A lot of users are used to userscripts type of communication ( I had 300+ discussions and 1 issue and they were in different tabs )
-
Good idea, I have nothing against modal prompts. Also some comments/reviews in About UserScript Tab is good info for future users. (this feature is often is used in Film\Books\Games websites)
*1) Another thing about Issues, let's look at idea that closed issues are dissappearing.
So when someone has the same problem he can't find previous, because Author already answered how to fix it for another user, and that user closed the issue.
I suggest adding "All" option to "open/closed" in the right block, so people would see all issues that were present? and only then they could select open only if they need only open issues...
I'm more inclined to consider #356 to extend the existing Issues structure and seems more inline with what you are asking. Creating a subclass of issues can be handled cleaner this route and offers the same functionality as most SCMs which is what OUJS is. That's great that other sites want to make things overly complex by sub-categorizing RFEs vs Bug reports vs Comments however I think it would be better to let #356 handle this and should let the end user handle their own classifications instead of us... just like GH does.
As far as the filter goes for Issues ... I agree with an All option for easier traversing however that may affect the search as well which we have a few issues that need to be addressed.
OK, if I understood you correctly, you are more inclined to add labels to issues, that's perfectly reasonable idea. You could even give a list of common labels/tags for users to use (for issues ex.: script-problem, compatibility-problem, feature-bug, feature-requests, feature-discussion etc.)
In my experience review's are a good idea too, a lot of users look forward for reviews good/bad before any installation.
Issue is a vague category that allows any type of user feedback. It is flexible but provides some semblance of structure. Issue labels are intended to be eventually implemented (I don't remember if that has its own GH issue). As for reviews, see https://github.com/OpenUserJs/OpenUserJS.org/issues/286#issuecomment-51375866 (Marti quoting me). I do like the idea of having a filter to display all issues, but that is a different feature request which deserves its own issue.
