1.
4 libertés

2.
4 libertés
• utiliser
• étudier
• modifier
• distribuer

3.
#AOSWay
@alexismonville
@ayeba
Alexis Monville

4.
Alexis Monville
#AOSWay
@alexismonville
@ayeba
@enovance

5.
#mixit14
#AOSWay
@alexismonville
@ayeba
@enovance

6.
Culture
#agile #opensource
inspect and adapt
release early release often
transparency
build with stake holders
small teams
autonomy
users are co-developers
collaboration
communication
customer satisfaction
continuous delivery
short iterations
trust
technical excellence
sustainable pace
self organizing
simplicity
outside in inside out
version control
feedbacks
continuous improvement
responding to change
working software
source code published
available to the public
respect

7.
The OpenStack Open Source Cloud Mission:
to produce the ubiquitous Open Source Cloud Computing
platform that will meet the needs of public and private
clouds regardless of size, by being simple to implement and
massively scalable.

8.
Computing Networking Storing

9.
Cloud Operating System

10.
Who?

11.
Who?

12.
and a lot more...

13.
15834+ people
136+ Countries
850+ Companies
$10+ million funding

14.
analytics?

15.
ohloh.net

16.
Accueil

17.
What Does
Openness
Mean?

18.
feedback

19.
How to
contribute?

20.
Principes

21.
Principes

22.
Outils

23.
Outils
• mailing lists
• IRC
• Ask
• Wiki
• Launchpad
• …

24.
Release
Cycle

25.
Release Cycle
• Cycle de 6 mois avec des jalons
intermédiaires
• 4 phases principales
• Planning
• Implementation
• Pre-Release
• Release

26.
Austin

27.
Bexar

28.
Cactus

29.
Diablo

30.
Essex

31.
Folsom

32.
Grizzly

33.
Havana

34.
Icehouse

35.
Juno

36.
Release Cycle
F G H
planning
Openstack
Design
Summit
G-1 G-2 G-3
RC planning
H-1 H-2 H-3
RC
Openstack
Design
Summit
6 mois 6 mois

37.
Rythme
3 months
6 months
2 weeks
second

38.
Planning

39.
Planning
• 4 weeks to:
• Design
• Discuss
• Target

40.
Blueprints

41.
Blueprints

42.
Bugs

43.
Project Technical Leads
• Project Technical Leads (PTL)
• A PTL is the elected technical leader of a given
OpenStack core project.
• At the end of the planning stage the PTLs triage
the submitted blueprints and sets Priority for
them.
• The blueprints with a priority above Low will be
tracked by Release Management throughout the
cycle.

44.
Product Owner
• 1 product owner par équipe de
développement produit
• les fonctionnalités des produits eNovance
en connexion avec les fonctionnalités des
logiciels libres les constituants

45.
Meetings
• Réunion quotidienne, planning, revue,
rétro :
• video conférence
• utilisation d’outil en ligne

46.
Summit

47.
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com

48.
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com

49.
OpenStack Summit April 2013 - Portland, Oregon. Licensed under Creative Commons Attribution - ShareAlike - photographer Aaron Hockley - hockleyphoto.com

50.
Summit
• Every 6 months the
Design Summit gather
users and developers
• The Summit closes the
Planning phase

51.
Distribué

52.
1200+
developers

53.
Implémentation

54.
Qualité

55.
2 +2, 0 -2

56.
Apprentissage

57.
Core Devs
• You need 2 +2 from Core Developers
• Core Developers are co-opted among the
contributors

58.
Tests

59.
Versions

60.
branch model

61.
Livrer en continu
• Le déploiement et la mise à jour des
produits sont testés en continu sur une
architecture de référence

62.
En conclusion…
Communication
Feedback
Respect
…

63.
• Créer les conditions de la collaboration
• temps passé ensemble
• outillage de communication confortable
• vision produit traduit dans les outils du projet
• pratique d’ingénierie : tests, intégration
continue, automatisation
• apprentissage du feedback

64.
Alexis Monville
#AOSWay
@alexismonville
@ayeba
@enovance

65.
The
Agileand
Open
SourceWay

66.
Merci !