Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add links to upcoming blog post on communicating OSS #50

Merged
merged 1 commit into from
Jul 18, 2023
Merged

Add links to upcoming blog post on communicating OSS #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions principles.qmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ Useful software development is unlikely to be achieved by developers alone: rath
::: {.callout-tip title="Read more about this principle in application"}

- [What should the first 100 lines of code written during an epidemic look like?](https://epiverse-trace.github.io/posts/100days-workshop/)
- [Communicating development stages of open-source software](https://epiverse-trace.github.io/posts/comm-software-devel/)

:::

Expand All @@ -48,6 +49,12 @@ The main objective of our collaboration framework will be to optimize interactio

To maximize agility, we recommend also adopting the lean principle in which the amount of work in progress (WIP) at any time is minimized. In other words, it is more efficient to work on a few MVPs and deliver value quickly, rather than working on many MVPs at the same time, resulting in a lot of WIP and low completion rates. We recommend using Kanban boards to keep track of progress, and as a tool for identifying long-lasting WIP, likely indicative of blockage or issues which need addressing. These boards should be fully public to encourage and facilitate external visibility and contributions.

::: {.callout-tip title="Read more about this principle in application"}

- [Communicating development stages of open-source software](https://epiverse-trace.github.io/posts/comm-software-devel/)

:::

## Decentralizing code ownership

The sustainability of open source software (OSS) projects increases with the number of developers who understand the code base enough to make contributions. While there is always a need for a single official maintainer, we will aim at decentralizing code ownership as much as possible, using a series of practices:
Expand Down
Loading