open at start guidance - Githubissues

datasciencecampus / coding-in-the-open

A compendium of open-source guidance which aims to share the benefits, risks and a summarised strategy for open-source coding.

MIT License

8 stars 0 forks source link

Closed r-leyshon closed 1 year ago

r-leyshon commented 1 year ago

Including considerations from setting up transport network performance repository. Including:

Access to external collaborators (codebase & kanbans)
Ways of working:
- open issues
- closed notes in draft
- closed conversation repo
- opening issues from repo versus opening from kanban
Minimal project governance prior to open src dev
Gaining agreement with project lead

r-leyshon commented 1 year ago

More notes:

Don't document GitHub UI in much detail - they change their UI a lot and the docs wont age well. Possibly raise this in the contributing guide too.
Document the aspects of the project that could be classified as anything above official so that your team has a clear indication of what information should not be staged within the open code repository.