Home
This project is for fun and for learning. If you're not having fun or not learning, please let others know so we can achieve these 2 primary goals! Since we all know each other IRL, we don't have a Code of Conduct; Goal 0 is not to need one.
We are using kan-ban with quasi-weekly Refinement meetings for project management (typically Wed. at 6:30pm, on Discord). We use a Trello board to track work. We have plans to do periodic Retrospective meetings to refine our process, scheduling TBD.
Work is divided into Cards (aka "tickets" by those of us poisoned by Jira usage), and accomplished in terse-but-descriptively-named branches, and merged into main after at least one Approval[Elaboration needed] on a PR. Cards can be added by any member with access to the board. Cards should include specifications and acceptance criteria[Elaboration required]. Cards are ideally discussed in a Refinement meeting before being picked up, though this is not required.
To work on a card, add your name as a Member on the Trello card, and place it in To Do or In Progress column depending on whether you have started it. Create a PR for it whenever you want some feedback; create it as a Draft PR or use the "do not merge" label if it is not yet ready. Use the just-dev-things Discord channel to solicit reviews, opinions, or memes. If you are comfortable with the PR being merged, use the Auto-merge feature so that it will be merged as soon as the PR is approved. Unless there is a good reason to preserve intermediate commits, all PRs should be squashed on merging.
Potential changes to the code base which are not specific to a particular feature are best discussed using the Issues page so that the discussion is close the code-base, and can be referenced in subsequent Cards or PRs. Issues can be raised by any member with access and should be closed once they are addressed. There is no process around closing Issues, it's on the honor system.