The document discusses the author's experiences with open source software and free/liberal licensing over his career. It provides an overview of his early encounters with FOSS projects, describes some of the companies and technologies he has worked with that utilize open source, and encourages readers to get involved in their own way through activities like coding, testing, documenting or community participation. The author advocates that open source helps with time to market, cost of development and building ecosystems.

1. An Open Source Story
By Johan Thelin // Hacktober 2018

2. Computers

4. First Encounters with FOSS
• Internet
• DJGPP – compiler
• Allegro – game lib
• RedHat 5 – boxed Linux
• Chalmers
• Tru64 and Sun machines – real UNIX
• SDL, KDE, Qt

5. FOSS? FLOSS?
• Free software
• Open source software
• Libre software
• FLOSS! Free, Libre, Open Source Software
• Free as in beer! Free as in freedom!
• Not only software these days – open hardware, creative commons, etc

6. Working
• Coding away (and some driving)
• Volvo (automatic transmissions – bare metal C)
• Followed by some Qt
• Qt in boats
• Qt in trains
• Qt in power meters
• Qt in alarm panels
• Qt in other boats
• Qt in Education

7. Partnering up
• Joining Pelagicore
• Experience Change!
• Qt in cars
• Open Source in cars
• Qt Automotive Suite + PELUX
• foss-gbg

8. Mid-life Crisis? Co-founder
• We are the builders!
• When starting a business you need to be quick!
• Time to market
• Cost of development
• MVP
• Ecosystem
• Open Source helps!

9. Recap
time
FOSS
?

10. What is Open Source
• Free distribution
• Source code
• Derived works
• Integrity of The Author’s Source Code
• No Discrimination Against Persons or Groups
• No Discrimination Against Fields of Endevour
• Distribution of License
• License Must Not Be Specific to a Product
• License Must Not Restrict Other Software
• License Must Be Technology Neutral

11. Copyright and Copyleft
Non-permissive and Permissive
Strong and Weak

12. Community Work
• foss-sthlm
• foss-gbg
• foss-north
• gbgcpp – a part of swedencpp
• :oppenkod

13. But what do I actually DO?
• Automotive
• Making and defending technical choices
• Driving standards
• Politics
• Licenses
• Advisory
• What is out there?
• What does this all mean?
• How can we use this?
• How do we work with this, properly?
• QML Book
• Writing about Qt/QML
• Completely open project

14. http://qmlbook.org

15. https://wiki.qt.io/QML_Book_Project

16. https://github.com/qmlbook/qmlbook/pulls

18. What can you DO?
• Coding
• Testing

19. What can you DO?
• Coding
• Testing
• Designing
• Drawing

20. What can you DO?
• Coding
• Testing
• Designing
• Drawing
• Documenting
• Promoting

21. What can you DO?
• Coding
• Testing
• Designing
• Drawing
• Documenting
• Promoting
• All skills are valuable!

22. Tools of the Trade
• Git
• Issue trackers – JIRA, bugzilla, trello
• E-mail
• IRC / discourse / slack / etc

23. Where do I start?
• Make stuff! Create! Explore!
CC BY 2.0 https://flic.kr/p/kUN41 by RatRanch

24. Where do I start?
• Make stuff! Create! Explore!
• Junior jobs
• https://www.gnome.org/get-involved/
• https://community.kde.org/Get_Involved
• Follow the blogs (or planets)
• planetkde, planetqt, planetgnome, planetfedora, etc
• https://andrewcrouthamel.wordpress.com/2018/10/03/making-plasma-
superb-in-hidpi/

25. Exercise – Fix a typo!
• I’m not a good teacher
• My spelling is bad
• I’m not a native English speaker
• I am human
• Caveat – github is not git!
• Caveat – we have a CLA (because
we still believe that we might see
this text on dead trees)
qmlbook.org

26. Exercise – Fix a typo!
1. Create a github account

27. Exercise – Fix a typo!
1. Create a github account
2. Fork qmlbook/qmlbook

28. Exercise – Fix a typo!
1. Create a github account
2. Fork qmlbook/qmlbook
3. In your fork, fix something!
1. git clone
2. git add
3. git commit
4. git push
https://try.github.io/

29. Exercise – Fix a typo!
1. Create a github account
2. Fork qmlbook/qmlbook
3. In your fork, fix something!
1. git clone
2. git add
3. git commit
4. git push
4. Create a pull request

30. Exercise – Fix a typo!
1. Create a github account
2. Fork qmlbook/qmlbook
3. In your fork, fix something!
1. git clone
2. git add
3. git commit
4. git push
4. Create a pull request
5. Discuss, fix and get merged!

31. Thank you!

32. Resources
• Open Source Initiative, OSI - https://opensource.org/
• Permissive vs Strong copyleft - https://opensource.com/resources/what-is-copyleft
• Qt Automotive Suite - https://www.qt.io/qt-automotive-suite/
• PELUX - http://pelux.io/
• foss-sthlm - https://www.foss-sthlm.se/
• foss-gbg - http://foss-gbg.se/
• foss-north - http://foss-north.se/2018/
• Getting started with git - https://try.github.io/
• QML Book (sources) - https://github.com/qmlbook/qmlbook
• QML Book - http://qmlbook.org