Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Pattern idea: Requiring InnerSource before Open Source #285

Open
spier opened this issue Jan 31, 2021 · 12 comments · May be fixed by #776
Open

Pattern idea: Requiring InnerSource before Open Source #285

spier opened this issue Jan 31, 2021 · 12 comments · May be fixed by #776
Labels
📖 Type - Content Work Working on contents is the main focus of this issue / PR 💡 Early Idea

Comments

@spier
Copy link
Member

spier commented Jan 31, 2021 •
edited
Loading

Going straight from closed-source to Open Source is not always possible, and it can also be a hard transition for the maintaining team as the required processes are very different.

To address that, somebody floated the idea that one could be requiring InnerSource before Open Source, sort of like an incubation phase inside of the company to see if a project has the potential to become Open Source. The InnerSource Incubation Phase would also allow the maintainers of the project to practice all the things required when a project starts to receive contributions from outside of the core team, including improving documentation and review processes accordingly. For the time being let's call this InnerSource Incubation.

There might be another branch of this idea, where Open Source isn't possible for some reason e.g. any intellectual property that the company doesn't feel comfortable sharing in the open. In that case InnerSource could be an attractive alternative to Open Source because through InnerSource the maintainers still get some of the benefits of exposing their project to a wider audience. For the time being let's call this InnerSource as next best alternative.

Focusing on the InnerSource Incubation for now, some specific ideas that would make such a pattern really interesting and valuable for readers:

  • how is the InnerSource Incubation phase is explained to the maintainers of a given project?
  • interview the maintainers of a project that have done through the InnerSource Incubation and have eventually released their project as Open Source. Ask them what the experience was like especially what of the incubation phase was most useful for them to prepare for Open Source
  • how long should the incubation phase be?
  • who would facilitate the incubation phase? Is that drive by the OSPO of the company? (assuming there is one)
@spier spier added 💡 Early Idea 📖 Type - Content Work Working on contents is the main focus of this issue / PR labels Jan 31, 2021
@spier
Copy link
Member Author

spier commented Jan 31, 2021

One other possible tag line that may spark additional thoughts about this:
"InnerSource as a stepping stone to Open Source"

@spier
Copy link
Member Author

spier commented Oct 8, 2022

There are some interesting aspects mentioned in this ISC Community Call:

InnerSource to Open Source - taking the next step

@spier
Copy link
Member Author

spier commented Oct 8, 2022

@mishari would it be possible to get the slides from your ISC community call "InnerSource to Open Source". I might try to incorporate some of the text or visuals into this pattern idea here.

@mcobby
Copy link

mcobby commented Oct 9, 2022

Hi @spier - PDF of the slides is in Slack https://innersourcecommons.slack.com/archives/C04PXKRN4/p1665315070585709?thread_ts=1663659054.262749&cid=C04PXKRN4.
Are you also wanting an editable version?

@spier
Copy link
Member Author

spier commented Oct 12, 2022

Thanks @mcobby.
As the messages in Slack will disappear after some time, would you be fine to attach the PDF to this issue here as well?

I don't think I need an editable version for now.

@rrrutledge rrrutledge moved this to Challenge in ISPO Working Group Dec 20, 2024
@yenk
Copy link

yenk commented Jan 27, 2025

@spier - can you verify if it's already in the pattern doc? Move to external column post verification.

@spier
Copy link
Member Author

spier commented Jan 27, 2025 •
edited
Loading

@yenk your question is whether we already have a pattern for this, right?

No, this is just an idea so far. We don't have a pattern for it yet. But of course if somebody in the ISPO WG wants to write a pattern about this, that would be awesome!

Aside:
Other readers of this repo here might not know which "external column" you are referring to. I believe it is a column on this board of the ISPO working group right?

@spier
Copy link
Member Author

spier commented Feb 23, 2025

@yenk did the last comment answer your question? Is this topic something that you are interested in working on?

@spier
Copy link
Member Author

spier commented Feb 23, 2025

Hi @spier - PDF of the slides is in Slack https://innersourcecommons.slack.com/archives/C04PXKRN4/p1665315070585709?thread_ts=1663659054.262749&cid=C04PXKRN4. Are you also wanting an editable version?

@mcobby I forgot that Slack history is purged at some point. Sorry about that :(

Would you mind attaching the PDF the slides for this community call here?
InnerSource to Open Source

You can can do that by writing a new comment here and then just drag&drop the PDF in the comment box. Thank you so much!

@spier spier linked a pull request Feb 23, 2025 that will close this issue
Open
5 tasks
@yenk
Copy link

yenk commented Feb 25, 2025

@yenk did the last comment answer your question? Is this topic something that you are interested in working on?

Thanks for checking on this one @spier. I can pick it up if you can please direct me to the right place, that'll be super helpful! Thanks!

@spier
Copy link
Member Author

spier commented Feb 25, 2025 •
edited
Loading

@yenk is your own organization/company applying this pattern (or some form of it)? In that case the easiest way would be to start with a brief description of how you are using this approach, and the experiences that you have made with it.

There is also a first draft of this pattern in #776. If you like, you can also review that PR and leave your suggestions there.

@jeffabailey
Copy link
Contributor

@yenk are you open to joining a working session to create a v1 of this pattern?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
📖 Type - Content Work Working on contents is the main focus of this issue / PR 💡 Early Idea
Projects
ISPO Working Group
Status: Challenge
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Pattern Draft] Require InnerSource before Open Source InnerSourceCommons/InnerSourcePatterns
4 participants
@spier @jeffabailey @yenk @mcobby