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

[core] Organizing Issues #4911

Closed
12 of 13 tasks
mpontikes opened this issue Aug 5, 2016 · 5 comments
Closed
12 of 13 tasks

[core] Organizing Issues #4911

mpontikes opened this issue Aug 5, 2016 · 5 comments
Labels
core Infrastructure work going on behind the scenes

Comments

@mpontikes
Copy link

mpontikes commented Aug 5, 2016

Problem description

So many of the issues are untagged, and it might be overwhelming for new collaborators to see that we have 450-ish issues. The thing is, we don't actually have 450-ish issues. Many of the issues are just discussions, questions, or feature requests. It might be a good idea to tag the issues that we currently have so that both old and new collaborators can see what's really happening in the issues tab. I went through these 450-ish issues and wrote what tag I think they should be under, tell me what you guys think. I also found some issues I thought looked like they could be closed. Thanks!

@rafaelsales
Copy link

I'm trying to follow up on #4753 as I can, and I'd like to pursue that. I could even implement it if someone from the team says "ok, go ahead"

@oliviertassinari
Copy link
Member

oliviertassinari commented Sep 17, 2016

So many of the issues are untagged

@mpontikes That's true. I do agree that it's can feel intimidating for a new contributor to see all those issue 530+ now as we are speaking.
We definitely need to be more organize. Thanks for doing this first iteration.

Github have just added a new Projects section. I think that we could take advantage of this new feature.
I have started creating one project per component. E.g. with the Snackbar.
Why using this per component approach?
Because our components are quite independent.
We work on one component at the time.
It's quite useful to have a full overview about one component (before starting / when) working on it.

@callemall/material-ui If you guys like this proof of concept we can go further.

@oliviertassinari oliviertassinari changed the title Organizing Issues [core] Organizing Issues Sep 17, 2016
@ashl1
Copy link

ashl1 commented Oct 5, 2016

image
And now the issues looks like:
image

Not labeled issues are rapidly growing...

@oliviertassinari
Could Callemall give me write access for this repo for triaging bugs (label them, close as dups, check is them really happens). You can add me as outside collaborator. And of course, you can check my history activities in audit log
My email: [email protected]
I'll try to check new issues at least once a week and up to each working day.

@oliviertassinari
Copy link
Member

oliviertassinari commented Oct 5, 2016

@ashl1 Thanks for your interest in helping us. Are you on gitter.im so we can chat about it :)?

@oliviertassinari
Copy link
Member

We have tagged all the linked issues. I'm closing this one.

@ashl1 How did you generate that chart? I would love to see how that looks like 7 months later.

@oliviertassinari oliviertassinari added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Dec 21, 2022
@zannager zannager added core Infrastructure work going on behind the scenes and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Infrastructure work going on behind the scenes
Projects
None yet
Development

No branches or pull requests

5 participants