InnerSource Readiness Standard

[rrrutledge]

How do I know when something is "InnerSource Ready"?
How can I clearly explain that to others?
How can I have a machine understand that?

[spier]

There is a mention of so-called InnerSource-readiness in this pattern that you might find relevant:
Good First Project and especially see their reference implementation.

[rrrutledge]

Fitness tracker? Nice!

[indie-rok]

I did this check list for on my training sessions:

https://docs.google.com/document/d/1Z2yMirjwZSGWvSS3-5m2Xrlh4ZpZq7HqhND5SFlewIE/

[rrrutledge]

Thanks for sharing, @indie-rok !

[spier]

I did this check list for on my training sessions:

https://docs.google.com/document/d/1Z2yMirjwZSGWvSS3-5m2Xrlh4ZpZq7HqhND5SFlewIE/

@indie-rok great list, thanks for sharing. I am leaving some comments/questions below.

Find who is my closest Trusted Committer

This is interesting. I wonder why the "closest" Trusted Committer is so important?
Also how does that look in a real life scenario? Do you list the location or timezone of the TCs, or how to people determine who their "closest" TC is?

Have a public road map visible

This could be related to the Issue Tracker Use Cases pattern.

README.md / CONTRIBUTING.md answers the following questions

Would you like to add any of those points to this existing pattern?
https://patterns.innersourcecommons.org/p/base-documentation

3 doc types

What do you mean by this?

Link to existing docs on different products.

What are "different products" in this context? Do you mean mean Wiki / Backstage / or other tools?

One general question:
I saw that you have copied the patterns to your own repository. Was wondering if you need that to keep any customized information their, or what the copy is used for? Just curious to learn how people are using the patterns.

[jimjag]

An innersource readiness checklist can be found here.

[rrrutledge]

Thank you, @jimjag ❗️ I am excited to collect all of these examples and want to get a way to list them out in an easy-to-find place so that they can be shared.

[spier]

Great stuff @jimjag.
Left some comments on your doc.

[rrrutledge]

Hi, @jimjag ❗ Thank you for this sharing! Do you want to respond to @spier comments and then put the document in the ISPO GDrive (linked in our CONTRIBUTING.md)?

[jimjag]

Will do

[rrrutledge]

Thanks, @jimjag ❗

[rrrutledge]

@jimjag link to the doc and move this ticket to "done"

[rrrutledge]

Hi Jim! Remember to do this when you have a moment. Thank you!

[dellagustin-sap]

This issue should be merged with #73 .

[rrrutledge]

They are all cross-linked, so closing this issue.