Importance of the contribution for an open source

1. This Document is Confidential

2. Importance of the contribution
for an Open Source
Ilya Antipenko
Software Engineer at Oro Inc.
iantypenko@oroinc.com
https://github.com/aivus

3. What is the Open Source?
WIKIPEDIA:
Open-source software (OSS) is computer software with its source code made available
with a license in which the copyright holder provides the rights to study, change,
and distribute the software to anyone and for any purpose
OSI Logo, License Creative Commons Attribution-Share Alike 2.5 Generic, source: https://commons.wikimedia.org/wiki/File:Osi_standard_logo.png

4. Why do people prefer using Open Source
Software?
● Control
● Security
● Stability

5. Open Source Definition
1. Free Redistribution
2. Source Code
3. Derived Works
4. Integrity of The Author's Source Code
5. No Discrimination Against Persons or Groups
6. No Discrimination Against Fields of Endeavor
7. Distribution of License
8. License Must Not Be Specific to a Product
9. License Must Not Restrict Other Software
10.License Must Be Technology-Neutral

6. Licenses
● Around 80 according to
https://opensource.org/licenses/alphabetical
● Most popular:
○ Apache License 2.0
○ BSD 2/3
○ (L)GPL
○ MIT
● Want to choose your license? Go https://choosealicense.com/

7. Typical Open Source project structure
(GitHub)
● Owner
● Maintainers and Collaborators
● Contributors
● Community Members

8. Symfony Core Team structure
1. Project Leader
2. Mergers
3. Deciders

9. Symfony PR voting policy
1. -1 votes must always be justified by technical and objective
reasons;
2. +1 votes do not require justification, unless there is at least
one -1 vote;
3. Core members can change their votes as many times as they
desire during the course of a pull request discussion;
4. Core members are not allowed to vote on their own pull
requests.

10. Symfony PR merging policy
A pull request can be merged if:
1. It is a minor change [1];
2. Enough time was given for peer reviews (at least 2 days for
"regular" pull requests, and 4 days for pull requests with "a
significant impact");
3. At least the component's Merger or two other Core members
voted +1 and no Core member voted -1.

11. Contributing (Issues)
● Check CONTRIBUTING file before create issue
● Check existing issues
● Be clear
● Link to demos
● Include system details
● Paste error output

12. Contributing (PRs)
● Check CONTRIBUTING file before create PR
● Fork the repository
● Create a branch
● Be clear
● It’s best to test
● Contribute in the style of the project
● Include screenshots (demo)
● Check BC (choose correct branch)
P.S. Keep in mind that the PR could be closed. Don’t worry, it may
not be what the project maintainer had in mind, or they were already
working on it.

13. CONTRIBUTOR LICENSE AGREEMENT
(CLA)
● CLA is Intellectual Property Assignment Agreement in Open
Source world

14. Why should I contribute to OpenSource?
1. Open Source is everywhere (mobile devices, car’s MCU, etc).
You can fix/improve anything you want
1. Really great experience
2. Improving quality of code
3. You can show you code to potential employer
4. BADGES!!!

15. What can I get more?
1. Swag (ex.
https://hacktoberfest.digitalocean.com/)
2. Tickets to events
3. For students: $5000 (Google Summer of Code)
Hacktober fest photo source: https://twicopy.org/TuckerSiemens/

16. Why is it important for us?
1. We are OSS users and providers.
We want to have great tools and provide great product.
1. Feature requests
2. Quick feedback for new features
3. Bug fixing

17. Questions?

18. This Document is Confidential