InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
InnerSource @ Panasonic
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
In this article Panasonic shares a story of applying InnerSource, to bring the development cultures of two different units more closely together.
Following Panasonic Connect’s acquisition of Blue Yonder, significant difference in development cultures between the two companies brought a “sense of danger.” To overcome the differences, they decided to pursue a cloud-native development culture. As a platform and tool for change, Panasonic Connect adopted Microsoft Azure and GitHub. This article describes how Panasonic Connect has worked on the transformation of its development culture.
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
The issue provides only a Microsoft article about Panasonic Connect’s InnerSource adoption and names no file, test, or entry point. Read the linked article and inspect the repository’s existing patterns to determine whether a documented change is intended; completion criteria are not specified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100