InnerSourceCommons / InnerSourceCommons/innersource-working-group
Collection of InnerSource User Stories
@dellagustin-sap is already working on this.
Since Sep 8, 2025.
- Dominant language
- Ruby
- Stars
- 26
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Description
In software development, user stories are used to express usage scenarios that lead to requirements or feature requests. They are an instrument deeply connected to user experience and design.
This issue represents an idea to express such usage scenarios from the perspective of an interested party of a project/project deliverable, focusing on empowering the interested party to find their way, participate and contribute. We will call these InnerSource User Stories.
The expected benefit of this exercise is to facilitate the adoption of InnerSource practices, by presenting potential adopters with pre-defined stories they can use as base for their project, and also present them with known ways to fulfill the user story. The typical way to describe how to fulfill one or more user stories should be an InnerSource Pattern.
These user stories should also help in defining the concept of Contributor Journey Optimization ( #157 )
Examples:
| ID | User Story | Known Solution(s) |
|---|---|---|
| US-RS-FEEDBACK-1 | As an interested party, I want to provide feedback in a transparent and traceable manner, in order to continuously improve the project and have a better experience with it. | |
| US-RS-FEEDBACK-2 | As an interested party, I want to know where to find existing feedback given to the project, in order avoid providing repeated feedback, learn from it, and enrich it with my own experience or opinions. |
Related Challenges
- #157
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.
Assessment
This issue has not been assessed yet.