| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
parent directory.. | ||||
Whenever changes to the InnerSource Patterns GitHub repository are made, a new version of the InnerSource Patterns book is published at patterns.innersourcecommons.org.
The latest version of the book is available for readers at patterns.innersourcecommons.org.
We also have a Staging version, used by the editors/producers of the book for testing purposes. If you want to make structural changes to the book, please contact us via a GitHub issue first.
The book contains patterns of maturity Structured (Level 2) or Validated (Level 3).
Initial (Level 1) patterns are not published in the book. Those are still subject to a lot of change, and have likely not even proven to work yet. For more on these maturity levels see the Contributor Handbook.
We use the gitbook.com service to host our book.
The /book folder contains generator scripts and extra content required to create the gitbook.
The book is generated in multiple languages.
The descriptions above are for the English book. You find the English content in /book/en.
For other languages the content is mirrored and translated to folders like /book/<YOUR_LANGUAGE>1.
For more on the translation process see these translation instructions.
The book is generated in multiple languages.
gitbook takes care of the markdown to HTML rendering for us. To do so, we need to provide a full list of all patterns that should be dipslayed in the book.
As the list of patterns grows over time, we generate the list automatically using /book/scripts/generate_toc.rb. The script is triggered by the .github/workflows/book.yml workflow, which contains a hard-coded list of all languages for which we need to generate toc.md files.
If a new language is added, you need to modify this line in .github/workflows/book.yml and add the 2-letter language code of the language that you are adding.
These patterns are already publicly available in the InnerSource Patterns GitHub repo. So why publish such a book at all?
There are a couple of good reasons to publish the InnerSource patterns as a gitbook:
Replace <YOUR_LANGUAGE> with the 2-letter ISO 639-1 language code for your language. ↩ ↩2
| Back | FazBrowse Home | New Git URL |