glideapps / glideapps/glide-data-grid

Additional Maintainers Sought

Open
#815 7 comments 9 reactions 0 assignees View on GitHub
help wanted
Dominant language
TypeScript
Stars
5.3k
Forks
428
PR merge metrics
No merged PRs in 30d

Description

![An animated gif from Wolf of Wallstreet featuring the popular meme of a person saying "I'm not leaving"](https://github.com/glideapps/glide-data-grid/assets/30443/c39109f7-151f-4a36-bb66-36a7ff568bd1)

Just want to be clear about that.

Anyway yeah, I could use help. There is a lot to do with this project and I want it to grow and be even better. So... I would love to bring on some more maintainers.

Here is what I propose:

# The GDG Maintainer Program

Do you love fast as all heck data grids too? Great. We (really more of a royal we) are starting a 3 phase program to admit new maintainers:

### Phase 1: Make at least 2 open-source code contributions

Past contributions count of course. Your contributions must either fix a bug in the core library or add a new feature. This shows some degree of familiarity with the project.

### Phase 2: Documentation improvements

Several of the docs are out of date and need work. We need better release notes, up to date docs on new features and settings, ya know, grunt work. You can't spell "maintainer" without "free labor" I always say. This also shows willingness to work on the less than glorious parts of the project.

### Phase 3: Co-PR review and issue management

You will review PR's submitted by me or other project contributors. We will work together to find a happy and healthy understanding of the goals and methods of this project. Prospective maintainers will also help to manage issues at this phase.

Once we have worked together long enough, I would like to promote at least one person to a core role. All new maintainers, at least for the time being will be at my sole discretion.

Some things to know:

- If you're a butthead or find yourself regularly accused of being a butthead, please stay away.
- While I do intend to slowly hand over a greater degree of freedom to new maintainers, it will be a slow process. I don't want to let this project suffer mission creep and eventual death due to that.
- If you want to help in a more limited capacity that is something of a hybrid between community contributor and maintainer let me know. I very much do need help here.

Also, the vaporwave website lives forever, sorry not sorry.

Let me know what you think! Consider this a PR to the project governance moving from a divine right dictatorship to an eventual divine right oligarchy.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.