Issues and coordination¶
Development is coordinated using a JIRA issue tracker which has separate projects for EntryStore and EntryStore.js.
Source code is managed by and committed to Git repositories on Bitbucket.
EntryStore and the client library EntryStore.js are tested using JUnit and Nodeunit, respectively.
Both projects are continuously built and tested using Bitbucket Pipelines.
The EntryStore tests currently cover the modules entrystore-core-impl and entrystore-rest, with work in progress on other modules.
The goal is to gradually improve test coverage of EntryStore and all of its modules. This is an ongoing and time-consuming process, therefore no complete test coverage is currently available.
The tests in EntryStore.js cover internal functionality and most importantly the whole REST API.
The Nodeunit tests in EntryStore.js can also be seen as complementary integration tests for the EntryStore REST module.
MetaSolutions desires that all contributors of ideas, code, or documentation to their Open Source projects complete, sign, and submit (via email or postal mail) an Individual Contributor License Agreement (ICLA). The purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to MetaSolutions' Open Source projects and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed ICLA is required to be on file before an individual is given commit rights to a MetaSolutions project.
For a corporation that has assigned employees to work on a MetaSolutions Open Source project, a Corporate CLA (CCLA) is available for contributing intellectual property via the corporation, that may have been assigned as part of an employment agreement. Note that a Corporate CLA does not remove the need for every developer to sign their own CLA as an individual, to cover any of their contributions which are not owned by the corporation signing the CCLA.
The ICLA is not tied to any employer you may have, so it is recommended to use one's personal email address in the contact details, rather than an @work address.
Your Full name will be published unless you provide an alternative Public name. For example if your full name is Andrew Bernard Charles Dickens, but you wish to be known as Andrew Dickens, please enter the latter as your Public name.
The email address and other contact details are not published.