| | 1 | = rasdaman Project Governance = |
| | 2 | |
| | 3 | == Project Steering Committee == |
| | 4 | |
| | 5 | The ''rasdaman community'' open-source project (in short: rasdaman) is governed by its Project Steering Committee (PSC). |
| | 6 | |
| | 7 | The PSC is overseeing and leading strategic development of rasdaman with the goal of ensuring that rasdaman keeps prospering. |
| | 8 | To this end, the PSC has the following main responsibilities based on several [wiki:#instruments instruments]: |
| | 9 | * manage commit rights to the rasdaman code base with the goal of keeping code quality and ensuring implementations of the strategic directions. |
| | 10 | * establish the short-term and long-term goals for the further development of rasdaman. |
| | 11 | * pursue an active outreach policy towards user groups, policy and standards makers, and any other relevant groups with the goal of (i) maintaining the technological lead of rasdaman in the field of Array Databases, (ii) maintaining its impact on relevant standards, such as OGC and ISO coverage standards, and (iii) maximize uptake of rasdaman in all user communities that can benefit from Array Databases. |
| | 12 | |
| | 13 | The PSC discusses issues openly, documents decisions made and provides minutes on publicly available media (mail logs, wiki pages, IRC logs, or whatever is deemed appropriate). |
| | 14 | In all issues, the PSC strives to achieve unanimous consent based on a free, independent exchange of facts and opinions. |
| | 15 | Should such consent exceptionally not be reached then Peter Baumann has a casting vote. |
| | 16 | |
| | 17 | Further rules the PSC will give itself on demand, driven by practical needs as issues arise. |
| | 18 | |
| | 19 | The PSC seeks to have a balanced representation of developers and users from the various domains. |
| | 20 | Peter Baumann, as the creator and Principal Architect of rasdaman, is a standing member in the PSC. |
| | 21 | Currently, the PSC consists of: |
| | 22 | * Peter Baumann, Jacobs University |
| | 23 | * Dimitar Misev, Jacobs University |
| | 24 | * Stephan Meissl, EOX IT Services GmbH |
| | 25 | |
| | 26 | == Instruments == |
| | 27 | |
| | 28 | The following instruments are being used, under the governance of the PSC, to run the rasdaman project: |
| | 29 | |
| | 30 | * The [http:/rasdaman.org rasdaman project website] is the single authoritative project information turnpike. Based on [http://trac.edgewall.org/ trac], it contains a wiki, a git repository for code maintenance, and some more modules. |
| | 31 | |
| | 32 | * The [http://rasdaman.org/patchmanager Patch Manager], integrated in the rasdaman trac, accepts code contributions, ensures rasdaman license rights, and maintains a history of code submissions. |
| | 33 | |
| | 34 | Developers submit their code exclusively through the Patch Manager. |
| | 35 | Patches are accepted by the Patch Manager only if the submitter agrees to the [http://rasdaman.org/wiki/ContributorAgreement rasdaman Contributor Agreement], thereby guaranteeing that the rasdaman code base follows a uniform IPR structure. |
| | 36 | (The originally first contributor of the full rasdaman code version and creator of the open-source project, [http://www.rasdaman.com rasdaman GmbH], has signed the Contributor Agreement as well.) |
| | 37 | |
| | 38 | All code contributions have to be formatted as [http://git-scm.com/ git] patches against the [http://rasdaman.org/browser rasdaman repository]. |
| | 39 | Patches are accepted by members of the PSC who all have commit rights. |
| | 40 | Incoming patches are inspected in due course after submission and checked for overall quality, adherence to the [http://rasdaman.org/wiki/CodeGuide rasdaman Code Guide], and mathinc gwith the overall strategic goals of the project. In case of deviations, committers can, at their discretion, accept the patch, accept it and invite the submitter to provide a follow-up patch for correction of minor issues, or - in case of major deviations - reject the patch and invite the submitter to provide a suitably revised patch. |
| | 41 | Patches submitted cannot be modified - every change to the rasdaman code base requires a specific patch with its own agreement to the rasdaman Contributor Agreement. |
| | 42 | |
| | 43 | This workflow is enforced by the [http://rasdaman.org/browser/patch_manager Patch Manager code]. |
| | 44 | |
| | 45 | * Nightly builds add to Quality Assurance; their [http://rasdaman.org/build current status] is publicy available on the project trac. |
