-
Notifications
You must be signed in to change notification settings - Fork 0
Add arch diag #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
refining story and context
alex-jw-brooks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general this looks great! Some small thoughts, but all very minor. Great work @Ssukriti!
| ## Problem | ||
|
|
||
| As the number of new feature contributions to a mature InnerSource repository rapidly increases, it adds more burden on code reviews and maintenance. How do we allow for faster release of new features, encouraging innovation and experimentation; while also keeping the repository well maintained? | ||
| As the number of contributions to a mature InnerSource repository rapidly increase, it adds more burden on code reviews and maintenance. How do we allow for faster release of new features, encouraging innovation and experimentation; while also keeping the repository well maintained? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Should be rapidly increases
| - Everlasting backlog of pull requests that need to be reviewed. | ||
| - Job dissatisfaction: Majority of maintainers' time spent in community support leaves no room for innovation. | ||
| - Perceived lack of accomplishment: Only a fraction of the new capabilities added gain adoption by users. | ||
| - Perceived lack of accomplishment: There are more features being contributed than gaining adoption by users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence feels a bit indirect to me - how do you feel about Not all contributed features have adequate user demand and consequent adoption?
| ## Patlet | ||
|
|
||
| An InnerSource project is receiving too many contributions, making maintenance difficult and resulting in a large code review backlog or premature rejection of new feature contributions. By offering an extension mechanism outside of the core project, the maintainers enable scaling of project capabilities with minimal cost and maintenance overhead. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Putting it here because I can't add it on the picture directly - do you know how diagrams are embedded into the book in general? Mostly wondering if this should be directly embedded in the text, with the caption in text as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great question, I actually followed one of the other structured patterns. I am not sure how it goes inside the book, but I assume they have some publication process and read from assets/images
Co-authored-by: Sebastian Spier <[email protected]>
No description provided.