El poder de la comunidad - Development en proyectos open-source: Caso OpenStack

Charla sobre proyectos open-source, haciendo especial enfásis en los procesos seguidos por proyecto OpenStack.
7mo Meetup de ArqConf

Transcript

1. EL PODER DE LA COMUNIDAD DEVELOPMENT EN PROYECTOS OPEN-SOURCE: CASO OPENSTACK 7MO MEETUP ARQCONF - 14/09/2016
2. VICTORIA MARTINEZ DE LA CRUZ MAY-AUG 2016 OUTREACHY INTERN EN OPENSTACK CO-FOUNDER DE LINUXCHIXAR SOFIA ENRIQUEZ SOFTWARE ENGINEER EN RED HAT
3. LINUXCHIX ARGENTINA 20 miembros activos Reuniones (todos los meses) Charlas, talleres, difusión FLISOL 2016 Nerdear.la PyConAR 2016 ​ ​ ​ ​ ​ ​ ​ @linuxchixar #linuxchixar at irc.freenode.org
4. FREE AND OPEN SOURCE SOFTWARE MÁS QUE SOFTWARE, UNA CULTURA/IDEOLOGÍA
6. FOSS COMMUNITIES EMPRESAS CONTRIBUYENTES VOLUNTARIOS ORGANIZACIONES
7. FOSS FOUNDATIONS
8. OPENSTACK Created by a large growing community 40,497 people 596 supporting companies 179 countries 20M++ LOC Most recent ("Mitaka") release stats: 2,336 developers 345 different organizations More than 20,000 patches
9. OPENSTACK MAIN ACTORS
10. OPENSTACK SUMMIT
11. Decides on issues affecting multiple programs Forms an ultimate appeals board for technical decisions Has oversight over the OpenStack project entirely. TECHNICAL COMMITTEE OPENSTACK GOVERNANCE Providing technical leadership over all the OpenStack projects Openness, Transparency, Commonality, Integration, Quality
12. Oversight of the Foundation and its budget, strategy and goals according to the mission and responsibilities. Provides strategic and financial oversight of Foundation resources and staff. BOARD OF DIRECTORS OPENSTACK GOVERNANCE
13. Consolidate user requirements and present these to the management board and technical committee Provide guidance for the development teams where user feedback is requested Track OpenStack deployments and usage, helping to share user stories and experiences Work with the user groups worldwide to keep the OpenStack community vibrant and informed USER COMMITTEE OPENSTACK GOVERNANCE
14. PROJECT TEAMS OPENSTACK GOVERNANCE Teams using tools (code repository, bug tracker, CI, wiki) and coordinated processes to produce a number of deliverables, in order to achieve a clearly stated objective. PTL Core members
15. OPENSTACK RELEASE SCHEDULE
16. CONTRIBUTION WORKFLOW 1. JOIN OUR COMMUNICATION FORUMS Project description in wiki pages Developer docs in http://docs.openstack.org 2. LOOK FOR A PROJECT IRC Freenode network (#openstack-cinder, #openstack-dev, #openstack-opw) Mailing lists (openstack, openstack-dev, ...) Join the OpenStack Foundation (as a Foundation member) Sign ICLA Create Launchpad account 3. ACCOUNT SETUP
17. CONTRIBUTION WORKFLOW 4. DevStack setup (*) 5. Hack! 6. Commit Spin up a VM with Fedora 22/Centos 7/Ubuntu 16.04LTS Get the code & deploy git clone https://git.openstack.org/openstack-dev/devstack cd devstack ./stack Repos are located by default under /opt/stack Run test suite before submitting for review :) Check out commit msgs guidelines https://wiki.openstack.org/wiki/GitCommitMessages (*) Check if desired component is by default in DevStack
18. CONTRIBUTION WORKFLOW cinder Upstream code Local environment cinder cinder/BUG-NUMBER Gerrit Core reviews: 2 +2 Jenkins:+1 Zuul / Jenkins (automated testing) Zuul / Jenkins (automated testing) check queue git branch BUG-NUMBER Fix changes; unit tests; git commit git review git commit --amend gate queue git clone / git remote update cinder/BUG-NUMBER
20. Q&A ¡GRACIAS! @VKMC @ENRIQUETASO