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.

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

Airbus pattern use #622

Merged
merged 3 commits into from Nov 24, 2023
Merged

Conversation

sicot-f
Copy link
Contributor

@sicot-f sicot-f commented Nov 24, 2023

We are adding Airbus' use of Innersource patterns into various known instances.

@spier spier added the 🐅 patterns-in-the-wild InnerSource patterns that were spotted in the wild. We can extract Known Instances and new patterns. label Nov 24, 2023
Copy link
Member

@spier spier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for sharing these experiences with us @sicot-f !

I left one question in this review that could help us make the content even better.
Otherwise this already looks great.

@@ -66,6 +66,8 @@ The mentioned collaboration challenges include:

It is worth mentioning that so far the software shared under this InnerSource license is mostly tooling, infrastructure, and tools lower in the stack.

Airbus created ad hoc InnerSource licenses to enable InnerSource way of working within a large part of the group.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by "ad hoc" in this context?
Do you have a template that people should use to create their own licenses? Or do you prescribe a single one? Or something else? :)

Also can you share if you modelled your licenses after any open source license that is out there, and why?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By "ad hoc" I mean we created them from scratch (not based on open-source licenses) for the sole sake of Airbus InnerSource program. Our IP team was used to commercial licenses while developers were more familiar with open-source ones. We iterated many times to find common grounds and also comply with the transfer pricing directive. I'll see with my colleagues if I can share more. Keep you posted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be awesome!

@spier
Copy link
Member

spier commented Nov 24, 2023

@sicot-f given the feedback you shared I am already going ahead and merging what we have here.

If you have more info that you want to share publicly, please open a new PR.

Who knows, maybe you can even share key parts of your license as part of the InnerSource License pattern, just like DB Systel did. Of course that is more effort, in terms of getting approval etc.

@spier spier merged commit 201704f into InnerSourceCommons:main Nov 24, 2023
9 checks passed
@spier
Copy link
Member

spier commented Nov 24, 2023

This is now live, and you can find all patterns containing "Airbus" like this:
https://patterns.innersourcecommons.org/p/innersource-license?q=airbus

Thank you again for your contribution @sicot-f !

rmarting pushed a commit to rmarting/InnerSourcePatterns that referenced this pull request Feb 29, 2024
Add Airbus as a "known instance" to multiple patterns
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐅 patterns-in-the-wild InnerSource patterns that were spotted in the wild. We can extract Known Instances and new patterns.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pattern in the wild: Airbus + Citi as Known Instances of InnerSource License
2 participants