Apperta believes that making things open makes them better.
All Apperta supported projects are encouraged to work in the open and share what they're doing whenever they can.
This document is a proposal, and Apperta actively seeks feedback on it via Github Issues and Pull Requests to this repository.
Apperta supports many open source projects which it does not itself maintain.
This document outlines the expectations Apperta has of such projects, and how Apperta will behave with respect to those projects.
The goal of this policy is to respect the autonomy and independence of project originators as much as possible while strongly protecting Apperta's community investment.
In the common case, movement of a GitHub repository involves considerable work, none of which improves the quality of the code, the features of the project, and much of which can actually cause harm to the project.
Furthermore Apperta is in general unlikely to be the sole investor in most open source projects it supports over their lifetime. This would in fact be unsustainable and a risk to the projects and the broader ecosystem. Therefore Apperta EXPECTS source code to be managed by whichever person or institution is the maintainer of the proejct.
-
Repositories SHOULD remain in the GitHub Organisation of the originator, UNLESS the Apperta Technical Subcomittee deem that there is a significant risk of loss of the community's asset through a future closure of the source code, in which case the Apperta Foundation will ask that the repository be managed by the Apperta Foundation under their GitHub organisation.
-
Projects SHOULD have demonstrably open source code using a public source code management tool (such as GitHub)
-
Source code SHOULD be up to date with the latest development tip.
-
Projects SHOULD demonstrate a willingness to accept contributions from the community such as Issues and Pull Requests. Where Pull Requests or similar are not merged, the project should explain the reason for this decision in a reasonably timely manner.
-
Where appropriate, live, public internet-facing demonstration instances of the supported apps SHOULD be maintained by the originators.
-
Projects SHOULD display the 'Supported By Apperta' badge on the repositories which have been supported by Apperta, and may demonstrate attribution in other ways if they so wish.
-
Repositories SHOULD have a clear copyright notice* stating the copyright owner, and an equally clear OSI-approved open source license.
-
Apperta WILL maintain a simple list or directory of such supported apps and components; their respective subdomain URLs; and appropriate documentation so as to make a demonstration interaction possible.
-
Apperta MAY download code snapshots from the originators' repository at the point of completion of a project or at any other time, in order to protect their investment in development of projects.
-
Apperta MAY fork a code repository from the originators' repository at the point of completion of a project or at any other time, in order to protect their investment in development of projects.
-
Depending on the specifics of the project, Apperta MAY ask that live public internet-facing demonstration instances use an Apperta subdomain that Apperta will provide and configure. If this incurs a cost it WILL be covered by Apperta.
In exceptional circumstances, variations to this policy may be discussed and agreed by the Apperta Board, for individual projects.
- Apperta = "The Apperta Foundation CIC"
- Originators = "The individual, gorup of individuals, organisation, company, or other institution from which the original open source project was created"
- Exemplar text for repositories regarding reasonable expectations of the community for project and product support: https://github.com/ethercis/ethercis#productproject-support
- OSEHRA paper on licensing terms for open source healthcare applications https://www.osehra.org/sites/default/files/osehra_licensing_terms_v.1.0.pdf
Copyright 2018 Marcus Baw License CC-BY-SA-NC