Allow repo to be used by multiple communities

[spier]

This repo was first just used by a single local community (the one in Japan).[^1]

Now we are trying to figure out how it could be used by multiple communities, so that it becomes easier for the different communities to learn from each other.

Some context from the organizer of the Japanese Community:

At first, I was going to use the jp-roadmap repository to host discussions of the Japanese community here. However, I changed our direction and renamed it because I thought it would be useful for the non-Japan community to be able to officially host their activities and deliverables here. So I want this community-toolkit repo to be widely used by non-Japanese users :grinning:

When I started the Japanese community, I didn’t know where to find resources that could be used by the community, and we didn’t know what to translate. I hope this is a good starting point. It would be easy to see what other communities are doing

[^1]: The repo was even called jp-roadmap before and then renamed to community-toolkit.

[yuhattor]

Thank you! Since this is still something I'm experimenting with, I have not yet decided on the following two points

• How to share Google Docs or pptx format files. I think one of the challenges of InnerSource is non-code/non-GitHub contributions. I would like to see non-code contributions made visible and hosted around GitHub. This is an important issue, as Slack has made it difficult to access past resources, conversations, and materials since the 3-month rule was applied. I think part of this problem will be covered by awesome-innersource, but I would like to see something that allows each community to re-use past material in an editable form.

• contents governance To avoid chaos, we would like to create a structure that prevents pdfs and large images from being uploaded. We want to make it easy to find the really important stuff and make sure that expired or highly important stuff gets sorted out.