Suggestion: label/template and maintainers

[junaruga]

I have a suggestion to make the operation effective in this repository.

Challenge and motivation.

The current challenge is the maintainer is mainly only @sodabrew . He tends to be busy. So, I think we can create an better situation to make other people help for each other.

My idea is to manage the issues and PRs by the GitHub labels, then add the maintainers for the specific labels.

How?

Issues

For the issues, in my impression, there are many installation related tickets such as the issue "gem install mysql2 does not work on my OS". I think we can put the label "installation" for the issues. And maybe we can put the label automatically for the new opened issue by creating the new issue template and guide users.

So, the label can be like this. For the names of the os: debian-based and os: rpm-based, I referred the wiki page. Or the labels using linux distribution names can be also candidate such as os: debian, os: ubuntu, os: fedora, os: centos, os: suse.

• installation
  • os: linux
    • os: debian-based
    • os: rpm-based
    • os: debian
    • os: ubuntu
    • os: fedora
    • os: centos
    • os: suse
  • os: macos
  • os: windows

Each person can focus their comfortable label's issue. We can add someone to a specific label's maintainer if someone is happy for that.

Pull-requests

For the pull-requests, I think we can create backport or backport: 0.4.x, backport: 0.3.x, backport: 0.2.x labels. I can see that some people want to see the bug fixing version on the minor version branches will be released. We might be able to use the pull-request template to put the proper label automatically.

Here is an example.

• master branch: @sodabrew
• backport: someone
  • backport: 0.4.x 0.4.x branch: someone
  • backport: 0.3.x 0.3.x branch: someone
  • backport: 0.2.x 0.2.x branch: someone

Opinions?

So, what do you think? Positive or negative?

I think this makes the repository's operation effective. My image for the operation is inspired from the Ruby project (maintainer assignment and backport) and the Podman project. (the operation by using labels).

[sodabrew]

I do appreciate the interest, but I have serious concerns about backporting. The use cases of people asking for backports seems to be: "I have a very old Rails application that I will not update, but also I'm updating to the very latest MySQL database."

[junaruga]

I do appreciate the interest,

@sodabrew My intent for this ticket is I think we can create the environment where you can focus to important things such as fixing bugs on master branch more comfortably in this repository. If we are surrounded by the information or we take a shower of information, we consume the energy of the will.

but I have serious concerns about backporting. The use cases of people asking for backports seems to be: "I have a very old Rails application that I will not update, but also I'm updating to the very latest MySQL database."

In my use case, currently I only use the latest version of mysql2. And if you have the concerns about the backportng use cases, I think we can document it on this repo's PR template (or/and somewhere) to avoid additional backporting PRs, and we can also close the current backporting PRs.

[junaruga]

Are your concerns that you have to spend time for the backporting and for the releasing right? Could you explain more about why people who have the situation you mentioned could be your concerns?