Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Consider a call for maintainers #2567

Closed
mrlife opened this issue Jan 23, 2021 · 8 comments
Closed

Consider a call for maintainers #2567

mrlife opened this issue Jan 23, 2021 · 8 comments

Comments

@mrlife
Copy link

mrlife commented Jan 23, 2021

Open source software is a boon for software developers around the world. It also takes a lot of effort to maintain a repository. Please consider recruiting some maintainers to help keep the ball rolling.

e.g. selectize/selectize.js#752

cc @caseyjhol @brockholzer

@NicolasCARPi
Copy link
Collaborator

@caseyjhol I would be willing to help with issue triage (and closing the old ones) and pr review.

@caseyjhol
Copy link
Member

@NicolasCARPi That's great - thank you! That's definitely what I need the most help with currently. Here is a pre-written message you can use on bug reports that are missing requirements. I'll try to get you access to close/label tickets soon. In the meantime you can just tag me in a comment if you think it should be closed.

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case (you can use our preconfigured Plunker), and report back with:

  • your link
  • Bootstrap version
  • bootstrap-select version
  • specific browser and OS details.

If you're not using the latest version of bootstrap-select, please try that as well.

@NicolasCARPi
Copy link
Collaborator

@caseyjhol I'm glad you accept my proposition. I think I'll start by modifying the issue template to include the required details so at least new issues have that, it seems to be a generic template as of now. I'll then gradually go over the existing issues with the close hammer at hand.

I think for a repo of this size we can aim for 100 open issues and 10 open PR. PR should be merged or closed after 30 days max ideally.

Cheers,
~Nico

@caseyjhol
Copy link
Member

@NicolasCARPi The bug issue template is customized for bootstrap-select currently, but many people choose to ignore it anyway. It could definitely be improved, though. I think perhaps short and sweet would be better to ensure people actually read through it.

@caseyjhol
Copy link
Member

@NicolasCARPi Also, before merging in any PRs you think look good, please flag me first so I can review. Thanks!

@NicolasCARPi
Copy link
Collaborator

NicolasCARPi commented May 29, 2021

Well, this is weird, I got the invitation email, get on the invitation page, click Accept, first I get an error that my browser did something wrong, second time I get a 404, and now it tells me Invitation is invalid.... ¯_(ツ)_/¯

I'll try later...

edit: opened a support ticket for it. Maybe I'll need to decline and you'll need to invite again.

@NicolasCARPi
Copy link
Collaborator

@caseyjhol I have declined the invitation (as it is not working), could you kindly make a new one (so I stop pinging you and can actually close stuff myself)?

Cheers,
~Nico

@NicolasCARPi
Copy link
Collaborator

@caseyjhol Thanks for the invitation, this time it worked. But it seems it is only "view" rights, which doesn't mean a lot for a public repository. The idea was that I would have rights to label and close issues, so I can be an effective help, do you think you can extend rights like so?

@snapappointments snapappointments locked and limited conversation to collaborators May 30, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants