See the full deck from the Foundation's webinar on its refined project life cycle with Peter Monks, VP of technology

1. Project Life Cycle Webinar
2017-03-02
Peter Monks
VP of Technology, Symphony Software Foundation
@pmonksssf peter@symphony.foundation

2. 1.What and why?
2.Our project life cycle
3.Project portfolio states
4.Q&A
Agenda

12. From Jim Zemlin’s keynote at the Linux Foundation’s 2017 Open Leadership Summit

14. Apache Top Level Projects
(plus many more)

16. Incubation allows the project team to form, figure out their collaborative processes, and improve
the quality of the code towards activation.
Consumers have a clear sign that the project is under construction, so the project team can
focus on innovation, unburdened by support requests, backwards compatibility concerns, etc.

17. Active projects have a roadmap informed by feedback from the project's users, and are actively
executing against it. This is where projects are expected to spend the bulk of their time.
Consumers have a clear sign that active projects are production-ready.

18. Long term maintenance is available to projects that are neither active, nor ready for archiving.
This includes projects that are mature and stable but no longer actively enhanced, as well as
examples and sample code.
Consumers have a clear sign that LTM projects are not actively developed.

19. Archived projects are moribund - they are no longer maintained.
Consumers have a clear sign that archived projects have been abandoned.

21. Contribution is the initial transition into the Foundation.
Minimal requirements, mostly legal:
● Code, and any works it derives from, must be compatible with Apache License v2.0
● Contributor has a Contributor License Agreement in place with the Foundation
● Contribution is aligned with the mission of the Foundation

22. Activation has substantial security, quality, and viability requirements. Project must provide
evidence that the software is “production grade”.

23. No specific criteria for moving into Long Term Maintenance, beyond a low level of activity. May be
requested by a project team at will.

24. Archiving is generally initiated by the ESCo, due to inactivity.

28. As at March 1st, 2017

29. 1. Simple 4 stage lifecycle
with
1. Clear transitions gated by well defined criteria
➔ Balance between bureaucracy and chaos

31. https://symphonyoss.atlassian.net/wiki/display/FM/Project+Lifecycle
or
https://tinyurl.com/jd7fb3j

32. Thanks!
Peter Monks
VP of Technology, Symphony Software Foundation
@pmonksssf peter@symphony.foundation