appwrite / rfc

Architectural and new features proposals and designs for Appwrite πŸ“–

Home Page:https://appwrite.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Appwrite RFC's

Architectural and new features proposals and designs for Appwrite.

This repository serves as a central hub to keep track of all major features that go into Appwrite and enforces Appwrite's principle of transparency.

We want to ensure that any major feature or architectural change is subjected to scrutiny by the community and the Appwrite team and each change has a good reason to exist and adds value to the project.

πŸš€ The RFC Process

  1. Clone the repository
  2. Create a copy of rfc-template.md under problem/rfc-<0000>-<your-awesome-idea>.md (replace <0000> by incrementing the previous rfc # in the repo).
  3. Fill up Step 1 and raise a PR for the community to review. This will help us understand if the feature/change is worth pursuing.
  4. You will receive feedback on your proposal and once all the comments are addressed, your PR will be marked as Ready for Design Proposal or Changes Proposed or Rejected.
  5. Once marked with Ready for Design Proposal, fill up Step 2 of the RFC and move the file over to design/rfc-<your-awesome-idea>.md and update the PR.
  6. After another round of reviews, your PR will be marked as Accepted or Changes Requested.
  7. If Accepted, Congratulations!! You can go ahead with the implementation of your great new idea!

Throughout this process, you are obliged to comply with our Code of Conduct to ensure that we are building a safe and healthy community.

🀘 Support

At any point, if you are stuck, feel free to hop on our Discord server to ask questions or seek mentorship! Happy Coding!

About

Architectural and new features proposals and designs for Appwrite πŸ“–

https://appwrite.io

License:BSD 3-Clause "New" or "Revised" License