FAQ#465
Merged
tsadler1988 merged 17 commits intomasterfrom Aug 2, 2022
Merged
Conversation
Contributor
Looks good to me. |
rrrutledge
reviewed
Feb 1, 2022
Co-authored-by: rrrutledge <rrrutledge@users.noreply.github.com>
Collaborator
Author
|
Thanks @rrrutledge added your proposed questions, split the 'overhead' question in 2, and added my thoughts to the answers threads. |
tsadler1988
commented
Jul 2, 2022
rrrutledge
reviewed
Jul 6, 2022
Contributor
rrrutledge
left a comment
rrrutledge
left a comment
There was a problem hiding this comment.
Thanks for this work, Tom!
Co-authored-by: rrrutledge <rrrutledge@users.noreply.github.com>
…SourceLearningPath into common-concerns
rrrutledge
requested changes
Jul 15, 2022
Contributor
rrrutledge
left a comment
rrrutledge
left a comment
There was a problem hiding this comment.
Just one formatting change, and then this looks good.
Co-authored-by: rrrutledge <rrrutledge@users.noreply.github.com>
rrrutledge
reviewed
Jul 19, 2022
|
|
||
| You can mitigate this by setting expectation, potentialy via SLAs. If contributors expect PR reviews within an hour, maybe you will be stuck reviewing PRs all the time, but if you set an SLA of 1 day or 1 week, this won't be the case. | ||
|
|
||
| === How do we convince management this is a good idea? |
Contributor
There was a problem hiding this comment.
From Chan:
Two recommendations:
Add link: https://innersourcecommons.org/stories/
If your organization's OSPO manages innersource projects, reach out to them for support.
Contributor
|
Looks great, @tsadler1988 ❗️ |
|
Cool! Thank you, both. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft Pull Request for adding an FAQ of common concerns per #455.Is this a good format for a first iteration?How are these questions and what other questions should we have?How do we want to answer these questions? I'm happy to add answers from my point of view as a starting point, but a variety of opinions and experience would be bestThis is now ready for review!