book vs working group repo schism?
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 55
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
I am finding myself confused when just looking at the readme what this repo is for. I think that it has grown to become two separate things: 1) the guide, and 2) a repo for the working group's issues.
I think the SMBD needs a very clean, minimal repo to maximize conversion from confused newcomer into monthly attendee. Can we split these out into two repos?
It would also be nice to have separate issue trackers for each 1 & 2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the README and reviewing how the guide and working-group issues are currently presented in this repository. Define the boundaries of the two proposed repositories and their separate issue trackers; done means the split plan is agreed and both newcomer paths are clearly separated.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100