Open actuallyyun opened 1 year ago
https://docs.openbeta.io/how-to-contribute/overview#software-development
One additional GitHub instruction we may want to add (especially for folks new to GitHub) is: they should create a new branch when working on a task or issue instead of submit a PR directly from their develop
branch (The latter will cause merge headaches for the contributor if there's a conflict).
Maybe we can add a link or two to GitHub tutorial (article or youtube).
How to send Auth0 API keys to new contributors (ideally automate the process)
Current we have two items of the general onboarding checklist
General Checklist CHECKLIST FOR EVERYONE Sign up for Discord Sign up for GitHub
I think we should also add:
Organization Workflow
Our workflow involves both unsynchronized communications through GitHub issues, pull requests (PRs), and a Discord channel, as well as regular synchronized meetings. Here's an overview of our organization workflow:
Unsynchronized Communication
GitHub Issues:
Pull Requests (PRs):
Discord Channel:
Synchronized Meetings
We meet bi-weekly to synchronize efforts and provide updates on the project's progress. Check out the current project we are working on and join the meeting if you are interested.
Approval Process