-
Notifications
You must be signed in to change notification settings - Fork 3
ACS Community Organization
The ALMA Common Software (ACS) is a control framework that provides general purpose distributed system functionality. It was developed starting in early 2000s for the Atacama Large Millimeter/Sub-millimeter Array (ALMA) radio astronomy observatory. It has also been released under the GNU Lesser General Public License (LGPL), allowing other projects to use it and people from other multiple institutions to collaborate in and contribute to its development. This repository maintains the open-source version for the broader ACS Community. The community wiki provides relevant documentation and references to shared resources, while this page defines the general organization of the community.
The "ACS Community" (or "Community" from here onwards) is defined as the group of ACS users and voluntary Community Branch developers. A list of projects currently using ACS is maintained [here](Community Users).
The community maintains this Community Repository, containing all LGPL released modules of the ACS framework. Patches coming from both ALMA and the broader community are regularly integrated to the Community Repository, according to the procedures described below.
Following the git philosophy each community member is welcome to fork the repository and make changes as desired for their individual applications, while considering sending general purpose patches back to the Community Repository. This repository contains a working version with tested and peer-reviewed changes that should serve as the reference for the whole community.
Initially the Community will be led by an ACB composed by the following persons:
TBD: Initial ACB composition.
The role of the ACB is to develop the initial ACS Community policies and procedures and to ensure it grows as an all-inclusive fruitful and useful collaboration for its members. The ACB will be active from July 2014 until June 2016, time at which an election process to replace the Board members should be in place.
TBD: Election process.
- GitHub
- Wiki
- Issue Tracking
- Build and test server
- [Binary repository](Official Binaries) (TBD)
Community members may report bugs or request features through the issue tracker. As well, any community member may pick up a ticket and initiate its discussion and implementation. All changes should be considered for integration into the Community Repository.
Bug fixes and new features can be added by anyone in the community in their repository fork. The following procedure explains how to integrate patches back to the main repository.
Every patch integration request must consist of a git-formatted patch file attached to the corresponding issue ticket, which should contain at least:
- Patch title (One-line summary)
- Motivation (Why is this change needed?)
- Implementation description (What was changed and what is its impact?)
Once attached, the ticket should be assigned to the control committee (see below).
Every patch submission integration request will be peer-reviewed and tested prior to its commit to the Community Repository. Every patch must comply with ACS coding standards and be testable through an existing or new Unit Test.
TBD: code formatting standard and minimal testing rules.
A community designated committee (CCB) is in charge of receiving new patches, reviewing and approving them for integration into the Community Repository.
As of July 2014, Jorge Avarias is the head of the CCB.
TBD: CCB composition and election mechanism
ALMA has an incremental release process by which a new ACS release is available every 2 to 3 months. New ACS releases are made available on a public ALMA repository. It is the responsibility of the Community Repository maintainers to pull any changes from the ALMA repository.
A community designated person is in charge of pulling new releases from the ALMA Repository into the Community Repository, prior consultation with the integration committee.
As of July 2014, Joe Schwarz has assumed this role.
TBD: Election process.