ruby / ruby/gem_rbs_collection

Maintainer for Rails gems wanted

Open
#558 11 comments 10 reactions 1 assignee View on GitHub

@pocke is already working on this.

Since May 20, 2024.

Dominant language
Ruby
Stars
303
Forks
136
Avg merge
5h 15m
Merged PRs (30d)
6

Description

As I mentioned in my talk at RubyKaigi 2024, we need "Gem Reviewers" for Rails gems, such as activesupport, activerecord, and so on.
https://speakerdeck.com/pocke/community-driven-rbs-repository

This issue describes what is expected of the maintainers in detail.

We are looking for two roles: core maintainer and ordinary gem reviewer.

Core maintainers

Core maintainers work on the ecosystem of RBS and Rails.

We expect them to design, develop, and maintain the ecosystem.
For example:

  • Review pull requests in this repository for rails gems
    • You become a gem reviewer of these (all?) gems.
  • Maintenance rbs_rails gem
    • Implement new features
    • Design the structure
  • Collabolation between rbs_rails gem, RBS definitions in ruby/gem_rbs_collection, and RBS feature / language spec.

In other words, they will do everything related to RBS and Rails.

I expect one or two developers will become this role.

Requirements
  • Periodic meeting with me (and other members)
  • Understand RBS basics
    • Do not need to understand RBS completely. I'll teach RBS
  • Understand Rails deeply

Ordinary gem reviewers

Ordinary gem reviewers review pull requests for Rails gems in this repository.
They cooperate with the core maintainers.
Woking other repositories is optional.

They should become a gem reviewer for one or more Rails-related gems.

We do not limit the number of developers.

How to become core maintainers/gem reviewers

First, comment on this issue and describe which role you are interested in.

We'll discuss how to work as a maintainer or gem reviewer on this issue. After that, I'll promote them.

@pocke's work in the future

I've spent much time on the RBS and Rails ecosystem. I'll continue to work on this area, but I plan to hand over the maintainer role to a successor(s).
I'll support the successor, especially at the beginning of their work. I'll continue to work on the RBS, of course.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.