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

Is there list of official maintainers? #1069

Closed
mrwweb opened this issue Jan 4, 2017 · 10 comments
Closed

Is there list of official maintainers? #1069

mrwweb opened this issue Jan 4, 2017 · 10 comments

Comments

@mrwweb
Copy link
Contributor

mrwweb commented Jan 4, 2017

In trying to appeal a closed issue, I realized I have no idea who the official maintainers of _s are and what the policy is for closing tickets. Could this information get added to CONTRIBUTING.md?

@samikeijonen
Copy link
Contributor

That's a good point. It would be nice to know for transparency and all.

@bahiirwa
Copy link
Contributor

bahiirwa commented Jan 5, 2017 via email

@mrwweb
Copy link
Contributor Author

mrwweb commented Jan 13, 2017

Hoping to get some activity here. Tagging people I've seen close issues or commit PRs (I know this list is way incomplete): @karmatosed @davidakennedy @kovshenin @sixhours @laurelfulford @alaczek

@bahiirwa
Copy link
Contributor

@mrwweb Check out https://github.com/bahiirwa/_s/blob/master/CONTRIBUTING.md. You could build on that.

@mrwweb
Copy link
Contributor Author

mrwweb commented Jan 17, 2017

@bahiirwa Where'd you get that list from?

@bahiirwa
Copy link
Contributor

I did some snooping on guys who merged and closed issues in the past. Not conclusive/exhaustive I must say.

@mrwweb
Copy link
Contributor Author

mrwweb commented Feb 6, 2017

With the core focus on the Customizer and Editor, _s will likely need to make some changes pretty quickly as new features that impact theming near public release. Getting processes for reviewing issues/PRs/etc in order now, makes a whole lot of sense.

My interest in contributing to _s is seriously flagging due to this uncertainty, and that makes me really sad. I'm extremely hesitant to invest time in coding and thinking that right now seems unlikely to result in a reasonably-responsive and transparent review.


Also, just sharing this relevant article from @samikeijonen:

  • Issues and pull requests should be reviewed and discussed more frequently. I don’t even know who have access the repo, and that’s one of the problems. Transparency is always good.
  • There should be several people who takes the main lead reviewing and discussing issues and PRs.
  • Main lead could rotate in month period. And main lead would check the repo every week, or every other week.
  • Checking the repo could mean active discussion, testing the PRs, closing the issues, calling for help and second opinions and so on.

@davidakennedy
Copy link
Contributor

We’re busy working on some improvements to Underscores, as well as Components. Development should pick up again soon. Things have ebbed and flowed thanks to other priorities.

As far as a list of maintainers, Underscores is and has always been maintained by the Theme Team at Automattic. Hope that helps!

@mrwweb
Copy link
Contributor Author

mrwweb commented Feb 8, 2017

Thanks for the clarification, @davidakennedy. Much appreciated.

I'd like to note that "Theme Team" does not appear anywhere in the repo and there's clearly confusion around this if both I and @samikeijonen didn't know this. This really needs to be in CONTRIBUTING.md, README.md, or both.

And while we're here, any chance I can get #1019 unclosed and given further review by the Automattic Theme Team. There's an extensive explanation for why it was closed without given proper consideration on the ticket.

@bahiirwa
Copy link
Contributor

Reopening this is effective. Issue keeps on cropping. #1109 #1084

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants