jassmith
commented
1 year ago (boring version to make sure we I am being inclusive in case my sense of humor doesn't work for you)
The Glide Data Grid (GDG) team is expanding and we are looking for new maintainers to join our project. We are introducing the GDG Maintainer Program, a structured approach to bring passionate individuals on board.
The GDG Maintainer Program
This program is a way to gradually integrate new maintainers into the project. It consists of three phases:
Phase 1: Code Contributions
To start, potential maintainers should make at least two open-source contributions to the project. These contributions can be either bug fixes or new features. This is to demonstrate familiarity with the core library.
Phase 2: Documentation Updates
The second phase involves updating and improving the project documentation. This includes revising outdated sections, enhancing release notes, and detailing new features and settings. This phase is critical as it requires attention to detail and a commitment to maintaining the project’s standards.
Phase 3: Collaborative Review and Issue Management
In this phase, candidates will collaborate on reviewing pull requests (PRs) and managing issues. This process is vital for understanding the project's goals and methodologies. It's a step towards a more significant role within the project.
Upon successful completion of these phases, we aim to promote at least one individual to a core maintainer role. The selection of new maintainers is at the discretion of the existing team.
Important Considerations
- We are looking for individuals who are respectful and collaborative. Disruptive behavior is not conducive to the health of the project.
- The transition to granting more autonomy to new maintainers will be gradual, ensuring the project's vision and integrity remain intact.
- If you're interested in contributing but not ready for a full maintainer role, we welcome hybrid contributions between community contributor and maintainer.
The project's unique website design will remain as is for the foreseeable future.
We are open to feedback and ideas about this new governance approach. We aim to transition from a single-person-led project to a more collaborative team structure.
artimath
BrianHung
lukasmasuch
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:
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.