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
Categories #317
Comments
@eddieajau had some proposal here #257 |
+1 I think it's a starting point. |
Again we are facing here the limitation of GitHub. How do we map categories? As the labels as Andrew suggested or we do not need to map them at all? |
I agree with Andrew's gist here |
@allenzhao during his GSoC project should provide the Categories. He will be ready to code in one week, so we need to establish the interim guidelines for how labels can be used in Github to supplement our categorization of issues. Here are some questions that we should discuss:
The Categories are the vital part of a new tracker so I call up to all JBS members - please share your ideas. Thank you! |
Can anyone repost andrews gist? I can't seem to view it? I think categories needs to be dynamic because if Joomla wants to focus on something in particular then we want to be able to add new categories (e.g. if we want have a postgres cleanup we can add a postgres category and encourage people to test in there). I think probably only the Leadership should have permissions to manage the categories themselves though and then obviously JBS people to add a category label to an issue I think we have a good set of categories on the tracker though at least to start with. components, code quality, libraries seems like the main 3. I think the only way to map them is via more labels |
@wilsonge Sorry but I didn't save that gist, maybe we need @eddieajau to repost it;) |
Thanks @b2z Here my ideas
They should be dynamic as @wilsonge noted but as start here a quick list:
Add and remove it globally --> only commiters / github maintainers / leadership members
As label (as we have it for "Needs JC" or "Have JC" ) @note i can't and have not read the gist @eddieajau |
Could the categories only be managed in JIssues and not mapped to GitHub at all? |
Actually I think @Bakual makes a very good point there. I don't think that's essential information for github |
I want to hear issue starter @brianteeman :) And one more question - issue can be assigned to multiple categories? |
For the initial implementation, I'd keep the categories local to the application. We still need to define a workflow where a user who doesn't have the rights on GitHub would be able to change something like labels via the bot accounts. Assigning something to multiple categories; I don't see why not. |
Possible via a group with selected JBS members or all JBS members?
hmm i think yes. e.g.
.... |
Thank you all. Now we have everything we need to do the coding! |
So please let me make a small conclusion here:
|
Sounds good to me :) |
|
I think the one who opens an issue should be allowed to choose a category and maybe (not necessary) also edit later on in his own issue. JBS group should be able to edit the category on each issue. I think the filtering is probably the most important thing :) |
I am currently playing with implementing labels and I am facing similar UI disasters 😉 I think for the item view we should go with something like we already have for labels. For the edit/add views I think we should look for something "collapsible". Think about having hundreds of categories... What GitHub has for selecting labels, milestones etc. in the edit and list views looks pretty cool. I think it's a bootstrap modal window with some logic for searching etc. - You have been proven to have decent JavaScript knowledge, maybe you can come up with something? The GitHub thingy looks like this: Alternatively, this here seems to have the options we might require: http://silviomoreto.github.io/bootstrap-select/ How does that sound? |
Oh and YES - I think we should provide colors :) |
I found this: http://davidstutz.github.io/bootstrap-multiselect/ |
I guess I need some idea here, |
I don't think so. Filtering by one category at a time should be enough. |
👍 |
Now it's on the live site;) Thanks to @mbabker for deploy so fast after the merge;)
And if there's any bug, report I will try to fix it;) Hope there isn't any after me and @b2z testing again and again;) Thanks for all the help along the way of implementing this and I'm really thrilled to see all this working;) |
👏 |
Now someone needs to think up colours for the list mentioned here 😄 |
Excellent work @allenzhao !! |
Awesome work man! Thankyou so much! |
I thought that we had colors covered already? Closing this 😉 |
Thanks @allenzhao good work! |
Where is it? Since we are now officially on the new tracker it would be nice to add categories. We have a list and we need only colors now ;) And we should keep in mind what is proposed in #432 |
Still not sure what's missing, I believe that we have the "feature implemented". If you mean "setting up the categories" for the project as in this list, and assigning the "correct" color to every category, this would be the job of a user belonging to a group with "manage" permissions. Do you think we should do anything here code wise? maybe creating some default categories when adding a new project, or "hard coding" the category list for the Joomla! projects we have in our install.sql file? |
I am talking about setting up categories, yes ;) Best regards, ----- Reply message ----- Where is it? Still not sure what-s missing. We have the "feature implemented". f you mean setting up the categories for the project as in the list, and assigning the "correct" color to every category, this would be the job of a user belonging to a group with "manage" permissions. Do you think we should do anything here code wise? maybe creating some default categories when adding a new project, or "hard coding" the category list for the Joomla! projects we have in our install.sql file? — |
Ah, OK ;) I think maybe a color selector would be a nice addition (like the one they have on GitHub) |
I'm really missing to tag, sort and filter issues by category
The text was updated successfully, but these errors were encountered: