InnerSource in Action - Boosting Pattern usage + contributions

Open
#152 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
content

Research direction

Start with the InnerSource in Action page linked in the issue and inspect how organization tiles are represented. Review the contribution examples and the patterns.innersourcecommons.org and GitHub search links to determine what can reliably identify an organization's pattern contributions. Done means contributor organizations are visibly distinguished on the page, with links to relevant patterns only if a precise approach is agreed.

Written by the indexing model from the issue text.

Description

website

If an org has contributed to our patterns, we could highlight that on the InnerSource in Action page, effectively showing some extra appreciation of their work.

See mock below.

idea-showcasing-patterns

Purpose:

  • when a new org adds themselves to our in Action page, they would notice that their org tile on that page looks different from some others (e.g. other orgs have "more stuff" to display on their tile)
  • readers can more easily discover that an org has contributed to our patterns
Aside

Contributions of orgs to our patterns come in different forms, so it doesn't necessarily have to be a lot of work e.g.

  • adding themselves as an adopter of a given pattern (a Known Instance)
  • improving existing patterns
  • writing entirely new patters
Bonus feature:

We could try to add a link to the patterns that a given org has contributed to.
I don't know how to do that in a sensible way yet.

Both of the approaches above are not very precise in finding the patterns that a given org has contributed to, but it is better than nothing.

Dominant language
No language data
Stars
9
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InnerSourceCommons/InnerSourceMarketing

All issues in InnerSourceCommons/InnerSourceMarketing

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.