Many developers are required to work on a proprietary company project, but they must also maintain active in the Open Source community. "We need new features, and to release our product next month, but you also need to make sure you maintain contributing" said the manager. This is a hard feat to accomplish, which many struggle with.
With the evolution of services, companies must determine what goes in OpenSource and what to keep proprietary. Compaines do not wish to contribute their Intellectual Property, but still want to make an impact on the OpenStack community. This also becomes a struggle. What can and can't we contribute, and will our companies IP ever be allowed into an OpenStack project?
This panel will cover experiences on the above topics from various different OpenStack contributors, who do not fully work on OpenSource.
Attendess should expect to learn:
- What can and can’t be contributed to the OpenSource community. There are items which remain intellectual property, however there is a process of contributing Intellectual Property which varies by company.
- Various tips and tricks to the OpenStack Community.
- How to maintain active in an OpenStack project while spending the time on proprietary projects.
