The document discusses how the Eclipse Foundation can help research projects with open source collaboration. It notes that the Eclipse Foundation accepts project invitations to support members, gain new members and technologies, and diversify revenues. Over three years, challenges around open source like licensing and community building are addressed. Examples show how the Eclipse Foundation helped one project succeed with open source and another fail due to late contributions and political issues. The takeaways are to use open source for sustainability, build projects incrementally, and view open source as a journey between research and industry.
Steps To Getting Up And Running Quickly With MyTimeClock Employee Scheduling ...
Publishing Research with Open Source
1. 1 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
Publishing
your research results
with an open source foundation
Philippe Krief, PhD
Research Relations Director
Eclipse Foundation
2. 2 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
2
Dear Eclipse Foundation,
We would like you to join this project
to help us with the following points:
● Sustainability
● Community Building
● Dissemination
Sincerely,
an Eclipse Member
Why the Eclipse Foundation is invited?
3. 3 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
3
Why DID we accept invitations?
✓ To support our members
✓ To gain new members
✓ To retain existing members
✓ To gain new technologies
✓ To improve existing Eclipse technologies
✓ To diversify our revenues
4. 4 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
4
Why DO we accept invitations?
✓ To support our members
✓ To gain new members
✓ To retain existing members
✓ To gain new technologies
✓ To improve existing Eclipse technologies
✓ To diversify our revenues
✓ To promote Eclipse projects and members
✓ To evangelize on Open-Source & OSS Best Practices
✓ To enrich existing Eclipse ecosystems and working-groups
5. 5 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
5
IoT
IoT/
CPS
I4.0
I4.0 I4.0
Tools
Tools
Cloud
Auto
motive
Auto
motive
Embe
dded
IoT/
CPS
IoT
Privacy
Robo
tics
Our
Research
Project
Portfolio
6. 6 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
6
Research Project proposal invitations
7. COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
7
Challenges & Proposed Solutions
8. 8 COPYRIGHT (C) 2021 ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
Year 1
● I don’t want to open my source
● You don’t make money with OS
● Code coming from 5-75 partners
● Open and Close source code
● Own development tools
● Own/No development process
● Open-source is awesome & easy
● Open-source is an hippie stuff
● What is the difference between GPL
and Apache licenses?
● Open development
● Common development platform
● Open-source best practices
● OSS Education
● What is open-source
● What are the different OS licenses
Photo by Belinda Fewings on Unsplash
● Open-source business models
● Open-source success stories
COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
The partners bring their project vision and code
Challenges Solutions
9. 9 COPYRIGHT (C) 2021 ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
● Copyrights are missing
● Who owns this code?
● License selection is missing
● Third-party dependency IP issues
● No time to communicate
● No time to disseminate
● No time to document
● Why do you need a community
● How do you build an ecosystem
● Invite to create demos
● Invite to Eclipse events
● In-house development then publish
● No CI/CD
● Open-source best practices
● “Drive with open eyes”
● Preliminary IP reviews
● OS licenses compliance management
Year 2
The consortium develops its first prototype
COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
Challenges Solutions
10. 10 COPYRIGHT (C) 2021 ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
The consortium publishes its results
Photo by Nicolas Hoizey on Unsplash
● I want to build an ecosystem
● Do I need to become an Eclipse member
● Role of a Project or Working Group
● Create or join a project or WG
● No time to open-source
● No time to meet developers
● No time to document
● Run for a new proposal
● I don’t want to open my source
● I want to open-source my part
● Organise specific webinars
● Invite the project to Eclipse events
● Help in creating short videos on demos
● Help creating a Getting Started
● Support follow-up proposals
● Support Golden Nuggets
● Run after Early Adopters
Year 3
COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
Challenges Solutions
11. COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
11
Examples...
12. 12 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
12
A success story: Eclipse KUKSA
Open Source Connected Car Platform
✓ Open-source activity strongly supported by the coordinator (BOSCH)
✓ Eclipse project proposal submitted during the kick-off meeting
✓ Several partners had a good experience in Eclipse Development process
✓ License selected and specified in the project proposal
✓ Met open-source communities from Y1
✓ Organised meetups, Hackathons, and presentation from Y2
✓ Documentation, demos with a rover available very early
✓ Early-adopters
✓ Key partners are still involved in the code
13. 13 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
13
It’s OK to fail
> 3 different coordinators in 3 years
> Planned to open-source
the whole project
> Initial contribution submitted too late
> Political issues
(one tech partner left the project)
> None of the partners (but Eclipse)
wanted to stay in the project
> ...
14. COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
14
Takeaways...
15. 15 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
15
Use Open Source
for the sustainability
of your Research Projects
Photo by Vytas on Unsplash
COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
Build a platform incrementally
16. 16 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
16
Open Source is a journey,
not a destination
Photo by Dino Reichmuth on Unsplash
COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
17. 17 COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
17
as a catalyst
for Open-Source collaboration
between research and industry
Photo taken at 2018 ASCE (Credit: Graham Carlow)
COPYRIGHT (C) 2021, ECLIPSE FOUNDATION | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)