Anyone can help! You don't need open-source experience, and you don't need to be neurodivergent (ND) to help the cause. If you ARE ND yourself, you can also join ND In Tech yourself.
- Clone: Clone the project locally. Don't make a fork.
- Ticket: Choose a ticket from the "To Do" column of our issue board that you think you can complete in under a week.
- Assign: Set to yourself.
- Move ticket: Drag ticket to the "In Progress" column.
- Create branch: Name the local branch with the issue number plus 1-3 words summarizing of ticket, such as
6-favicon
or18-day-night-toggle
. - Start: Try your best to get it started.
- Pull request: Create a PR into
main
. It doesn't need to be complete yet; you can create one as soon as you start working on the ticket & keep pushing onto it. - PR template: Fill in auto-generated template that will pop up. If it's still in progress, just note such in the description, and ignore everything below the "Type of change" section.
- Request review: When it's ready for code review or you have a question, assign it to an owner, with any questions right in the PR's "Conversation" tab.
- Receive review: Owners will do a review of code or questions.
- Merging: When it's good to go, an owner will merge the ticket into
main
. - Thank you! We appreciate you contributing as a volunteer to this open-source, social-good project.
Anyone can move a ticket from "To Do" > "In Progress" > "Code Review" as they work, but we currently only allow only owners to move specifically from "Planning" > "To Do".
Anyone can help with PR code reviews, but please don't merge into main
.
Right now, we only allow only owners to merge PRs into main
.
This site is currently made with JavaScript, HTML, & CSS.
We use GitHub Project Issues (linked here).
We have in-progress wireframe brainstorming happening on Penpot. If you'd like an invite to our team there, please reach out.
The owners of the repo are @hayleyw7 & @royemosby.
Our general code of conduct applies here.
We try to keep specific discourse and questions in tickets, PRs, and the GitHub Discussions tab.
Yes, please. We're open to all minds & labor offered.
Absolutely! Once you've had a PR merged into main
, it's great open-source & volunteer experience to put on your resume and post about on your LinkedIn.
The website is open-source and licensed under an MIT License.