davidmiller / proposed-apperta-repo-management

Proposal for a policy for management of non-Apperta repositories which respects autonomy of project originators while strongly protecting Apperta's community investment.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Proposed Apperta Repository Management

Proposal for a policy for management of non-Apperta repositories which respects autonomy of project originators while strongly protecting Apperta's community investment.

Request For Comment

  • 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.

THEREFORE:

  • 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 fork the repository to the Apperta Foundation GitHub organisation.

  • Originators SHOULD have demonstrably open source code using a public source code management tool (such as GitHub) and this should be up to date with the latest development tip. Further, originators should demonstrate a willingness to accept contributions from the community such as Issues and Pull Requests.

  • Live, public internet-facing demonstration instances of the supported apps SHOULD be maintained by the originators, under subdomains of the apperta.org top level domain if appropriate.

  • 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.

  • Originators 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.

  • All Apperta-supported projects SHOULD have a clear copyright notice* stating the copyright owner, and an equally clear OSI-approved open source license.

  • In exceptional circumstances, variations to this policy may be discussed and agreed by the Apperta Board, for individual projects.

Definitions

  • 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"

Resources

Copyright 2018 Marcus Baw License CC-BY-SA-NC

About

Proposal for a policy for management of non-Apperta repositories which respects autonomy of project originators while strongly protecting Apperta's community investment.