Finding the Balance between Open Source and Proprietary Work
Many challenges exist in open source involvement, ranging from company deadlines to intellectual property limitations. Tips like setting up an IRC bouncer and maintaining regular contributions can help navigate these obstacles. Contributors share their experiences in finding the balance between open source and proprietary work.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Finding the balance between Open Source and Proprietary Work Dave McCowan Doug Mendizabal Fernando Diaz
Introduction Dave McCowan(dave-mccowan): Cisco Douglas Mendizabal(redrobot) Fernando Diaz(diazjf): IBM
Challenges There are many challenges to maintaining involvement in Open Source. Many OpenStack contributors are struggling with contributing for a variety of reasons: Deadlines on company product work Stable OpenStack versions in production; /master for upstream work Change of job description or mission Competing priorities between company and community
Intellectual Property Many companies have an Intellectual Property agreement that limits what can be contributed. Some examples of what can t be contributed are as following: Company IP Patentable Process Work which conflicts a business goal (Contributing to a Competing Product)
Helpful Tips Setup an IRC bouncer to always be logged and maintain active during daytime hours. Continue Contributing at the very least monthly by picking up small bugs and/or documentation. Attend Meetings regularly (If not possible, keep up to date with meeting history) Build Relationships with Active Developers.
