Tuesday, 18 April 2017

Reducing scope of OSGeo-Live for next 11.0 release

For our next OSGeo-Live release, 11.0, we propose to reduce the number of packages included, and only support a 64 bit distribution, (32 bit will be built but not tested or officially supported).
Factors leading to this suggestion include:
  1. Some projects have dwindling communities and momentum.
  2. Increased OSGeo-Live scope has increased our core maintenance and testing.
  3. Reduced engagement from projects (partly due to less core time spent reaching out to projects)
  4. Missing our first release milestone in 9 years.
From our options of reduce quality, become more efficient, increase volunteer engagement, find a sponsor to support core activities, and reduce scope, reducing scope is our most viable and acceptable option. Other ideas are welcomed.

Questions we will ask in assessing which projects to keep include:
  1. Is there an ACTIVE OSGeo-Live liaison person/people for the project? See "Contact" column in our Package List.
  2. Has the Project Overview and Quickstart been reviewed and are they current and complete?
  3. Do OpenHub metrics reflect an active and healthy community: 
  4. Is the project being updated on OSGeo-Live with each release?
Key Milestones
  • 5-Jun-2017 OSGeo-Live Feature Freeze (final application versions installed)
  • 19-Jun-2017 OSGeo-Live delivered to UAT (final application versions installed - Beta stage)
  • 24-Jul-2017 OSGeo-Live Final ISO
  • 14-Aug-2017 FOSS4G 2017 Boston


Brad Hards said...

Remember that openhub does a really poor job of some version control systems. For example, you'd probably conclude from https://www.openhub.net/p/spatialite that the project is dead. It just doesn't know the sqlite based VCS that is used - Fossil.

Cameron Shorter said...

Brad, you are right that OpenHub has many limitations. However I'm yet to see another tool which does a better job of efficiently harvesting accessible, quality project metrics. I believe the best we can do at the moment is to encourage projects to keep source metrics up to date, and note the limitations of such metrics.