InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern idea: (Project) Adopters pattern
Open
Nobody has claimed this yet.
:bulb: Early Idea
1-initial
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
Suggested by @spier as a reaction to https://github.com/SAP/project-portal-for-innersource/pull/38 .
Issue has yet to be defined, but in summary, the idea of recording users/adopters of an InnerSource project should become a pattern.
References
- Related threads on ISC Slack
- Call to action to register adopters on the SAP/project-portal-for-innersource - https://innersourcecommons.slack.com/archives/C04PXKRN4/p1660307419013239
- Discussion where this pattern was suggested by @spier : https://innersourcecommons.slack.com/archives/C2EFRTS6A/p1660307566174429
- Adopters at the SAP/project-portal-for-innersource
- ADOPTERS.md - used a permalink to avoid broken version, so be sure to look for newer versions
- Reference PR - https://github.com/SAP/project-portal-for-innersource/pull/38
Related issues
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 reviewing the current ADOPTERS.md in SAP/project-portal-for-innersource, its reference PR #38, and related issue #418. Review the linked Slack discussions for context, then define the scope and guidance for an Adopters pattern. Done means the idea has become a documented, agreed pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100