Archived

Overview

Projects and Working Groups that are no longer active, or falter for other reasons, may be archived by the PMC of the hosting Program.  In this state, issues may not be triaged in a timely fashion (or at all), and almost certainly won't be addressed.  The project team or working group participants may also have disbanded.

Triggers

Projects and Working Groups that have become inactive become eligible for archiving, where "inactivity" is defined as having had no activity (released / publications, commits, PRs, mailing list traffic, wiki updates, documentation updates, issue updates, etc.) in the last 180 days (6 months).

The PMC shall notify the Project lead or Working Group chair at least 14 days in advance that they are at risk of archiving, which provides ample time for the team to reassess objectives, team commitment and structure, and provides a buffer for dialogue with the PMC.  If the Project team or Working Group agrees that archiving is the appropriate course of action, or the project team or Working Group is unresponsive, the PMC will make a formal decision to archive it.

Objectives

Archived projects and working groups have no objectives - they are simply retained as-is, in whatever state they were in at the time of archival.

The PMC will, however, continue to gauge community interest in reviving the project or working group, and will actively support such activities.

Requirements

Badge

Foundation-hosted projects are expected to provide a clear indication to visitors that they have been archived.  Although Working Groups typically don't use badges, they are also welcome to use it, if desired.

To this end, the project team or (if the team is unresponsive or has disbanded) PMC will add this badge at the top of the project's root-level README.md file, using the following Markdown:

[![FINOS - Archived](https://cdn.jsdelivr.net/gh/finos/contrib-toolbox@master/images/badge-archived.svg)](https://finosfoundation.atlassian.net/wiki/display/FINOS/Archived)

This will appear as follows:

and when clicked will navigate to this page.

Releases

Archived projects and working groups cannot publish anything, of any kind.  If an archived project or working group intends to make publish new or updated artifacts, it must be revived first by going through the contribution process again and being reinstated as an incubating or active project.

The Foundation encourages community members to volunteer to revive any archived project, whether they originally contributed it or not. Reviving an existing code base is preferable to creating a competing alternative of the same functionality from scratch.

Notes for Evaluators

If you're evaluating Foundation-hosted projects or working groups and see the archived badge shown above, here are some of the things you should expect should you choose to download and use the software:

  • The artifacts (software, standards, etc.) produced by this activity are no longer maintained.  You cannot expect that any issues you raise, or contributions you make, will be triaged, let alone addressed.
  • The project may not have ever been released, and therefore may never have achieved significant levels of functionality or quality.
  • The project or working group may not have a team any more.  Some projects and working groups are archived precisely because the team disbanded and no replacements were forthcoming from the community.

If you see an archived project that looks useful to you, we strongly encourage you to form a new project team and take the project over.