The Pharo consortium was created in 2012 to sustain development of the Pharo programming language and community. It has grown to include 25 industrial and 13 academic partners who help fund Pharo engineers. The consortium is transitioning to be managed by the Inria Foundation, a non-profit, which will provide more stability and governance improvements while continuing to grow the consortium and support more Pharo engineers.

1. Pharo consortium:
Getting pro to deliver
more
Clément Béra & Esteban Lorenzano

3. Evolution
Achievements
Transition to Inria Foundation

4. Evolution
Achievements
Transition to Inria Foundation

5. Consortium goals
• Sustain Pharo
• Structure the community
• Companies can get an impact
• Individuals can get an impact too!

6. Historical perspective
• 2009 to 2012: Discussion with companies using
Pharo and Inria to design the first consortium
• December 2012: Pharo consortium creation
• 2013: First consortium members

7. More and more members
Consortium website includes
the amount of money received every year
& how the money is spent

8. Income = Engineers
• 2012 - 2015:
• Esteban Lorenzano
• Guillermo Polito to develop Garage
• 2016:
• Esteban Lorenzano
• Nicolas Passerini to build Iceberg
• Esteban Maringolo to port Glorp
• Mariano Marinez-Peck to develop OSSubprocess
• 2017:
• Esteban Lorenzano
• 2018:
• Clement Bera
• Esteban Lorenzano

9. Investments
• 10 years of engineering time by Inria in Pharo
• Money invested by RMoD
• Join!

10. Consortium FAQ
• Pharo will stay free!
• No negative impact: just a better Pharo
• Companies participate to the consortium
• Individuals participate to the association

11. Consortium members
• Up until now managed by Inria
• Companies, institutions, user groups
• Privileged access to the core development team
• Influence priorities of the next development
• Engineering support time
• Job posts
• Training/Conference special price

12. Current members
• 25 industrial partners
• 13 academic partners
• New members are under signature

16. Evolution
Achievements
Transition to Inria Foundation

17. Disclaimer: This is just a glimpse ;)

18. Pharo 2.0
• Revamp the release cycle
• No more 1.* (no natural backward-compatibility)
• Time boxed and not Feature boxed
• RPackage
• Announcements

19. Pharo 3.0
• VM: iOS
• Pharo using StackVM
• Many plugins and workarounds
• Platform deliverables
• Zeroconf
• CommandLine

20. Pharo 4.0
• OSWindow
• DarkTheme
• Libraries as part of the standard Pharo VM
• External libraries: Voyage 1.0, Marina
• Platform distributions

21. Pharo 5.0
• Migration to Spur
• UnifiedFFI to replace NB
• FastTable
• Garage (JDBC for Pharo). G. Polito
• GLORP new port and documentation. E. Maringolo
• OSSubprocess. M. Martinez-Peck
• Voyage-Mongo with replica set. M. Dias
• Voyage-Unqlite

22. Pharo 6.0
• Supporting Pharo 64bits (macOS and linux)
• Iceberg
• Unification with the OpenSmalltalk initiative
• Transparent UnifiedFFI (32 and 64 bits)
• Work on SmalltalkCI (Travis and appveyor)

23. Pharo 7.0
• New development process (based on git and
iceberg)
• Migration to GitHub
• Pharo 64bits on Windows
• Preview of Sista
• more to come

24. Evolution
Achievements
Transition to Inria Foundation

25. Inria Foundation
• Created March 2017
• Non profit organisation
• Host “Software Heritage” project
• Specialised in Consortium creation, management
and hosting for software linked to Inria

26. Software Heritage
• Supported by Unesco
• Collect, organise, preserve, and make easily
accessible the source code of publicly available
softwares

27. Other consortiums
• Sofa: Simulation Open Framework Architecture
• Mainly for medical simulation
• Coq: Formal proof management system
• Certification of properties of programming
languages
• Formalisation of mathematics

28. More for Pharo
• Visibility
• Solidity
• Legal Department
• Tax reduction for donation (US and FR)

29. Governance improvements
• More influence and visibility for each member
• Still two committees
Steering comittee Technical comittee

30. Governance improvements
• More influence and visibility for each member
• Still two committees
Steering comittee Technical comittee
Consortium members

31. Governance improvements
• More influence and visibility for each member
• Still two committees
Steering comittee Technical comittee
Consortium members
3 chosen by consortium
members
1 among consortium
engineers
3 among RMoD team

32. Governance improvements
• More influence and visibility for each member
• Still two committees
Consortium members
Steering comittee Technical comittee
3 chosen by consortium
members
1 among consortium
engineers
3 among RMoD team
Build
roadmap
Approves
roadmap
& expenses
(vote)

33. Technical committee
• Evaluates requests for changes or features
• Builds a roadmap
• Oversees the development and release of Pharo

34. Steering committee
• Reviews the state of Pharo ecosystem and community
• Recommends actions to develop Pharo
• Reviews the financial situation (Approve expenses)
• Approves the technical committee road map or
recommend changes (Vote)
• Sets work priorities for consortium engineers

35. Platinum members
• New consortium tier in 2017
• 8,000 and over
• 10 days of engineering time on YOUR system
• More impact on the Pharo road map

36. Donation
• 2018 and over
• Donations from France and US will have tax
deductions
• Donation means no services

37. Getting more engineers
• Foundation helps getting a second engineer
• Investment, etc.
• Aims to hire more engineers

38. Services
• In addition to membership
• Support for past Pharo version, other platforms
• Help/Talk on development practice, continuous
integration or specific libraries / frameworks
• Help to migrate to the latest Pharo version
• Custom development (Libraries, etc.)

39. Support for past version
• Included
• Support for Stable (Pharo 6.1)
• Support for Development (Pharo 7.0 Alpha)
• Additional
• Support for previous version (Pharo 4, 5, …)

40. Help/Talk
• Development practice & continuous integration
• Set-up the infrastructure
• Specific frameworks & libraries

41. Migration to the latest Pharo

42. Custom development
• MIT libraries
• French company
• 50k in 2017 for first version of CORBA support
• Dutch company
• 15k/year for Sista integration
• Others…

43. Large projects
• Large migration
• Large custom development
• Greater than 30 days of work
• Most probably we will work with other Pharo
consultants/companies

44. Feedback
• Discussion with the consortium members during
the Pharo days
• After ESUG we will send a survey
• Get feedback on the transition
• Get feedback on consortium members need
• Transition 1st of January

45. • Consortium keeps growing
• Transition to Inria Foundation
• Towards 2 engineers