Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

Add curated list of material on more detailed aspects of collaboration happening around InnerSource #39

Open
lenucksi opened this issue May 11, 2019 · 1 comment
Assignees

Comments

@lenucksi
Copy link
Member

lenucksi commented May 11, 2019

Rationale

It is impressive to see the amount of people looking for material to bring people up to speed with regard to general collaborative working approaches of InnerSource (and actually also OSS) who have not been exposed to them. This applies on various levels, an example being "How do I do a PR across repos, why do I do this instead of just getting full permissions any whatever repo and creating a branch with my work trying to get that merged" (in the popular case of Git and code).

Proposed approach

I think it would be worthwhile to curate a list of links on details such as Git(hub|lab) workflows that could be relevant after a person has watched some of the learning path material or generally got more involved with InnerSource.

We could add such a list to the resources section.

@lenucksi lenucksi self-assigned this May 16, 2019
@dicortazar
Copy link
Member

@lenucksi this is a great idea.
So far there's a list of existing materials in the 'resources' tab at innersourcecommons.org.
In addition to the existing materials and your proposal, I'd like to see at some point some kind of structured guides as in the case of the TODO Group (focused on Open Source Offices).

Then, going to your comments. I'd say that the point about the InnerSource Commons is to start defining good practices from several points of view (cultural approach, process, tools, etc). The one you refer to is to the basics of using certain infrastructures. We can include this into the tooling section. And perhaps have a more generic approach about using the several options in the market through pointers to the documentation to each of them.

Said all of this: I see as interesting to think first about we'd like to structure this info, and then start working on those pointers. This will help to ask for help in the community to other pointers.

Does it make sense to you @lenucksi ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants