The Consortium will deal with any major issues, but will not not fund any development.
It will be up to individual developers, working either for free or funded by a third
party (eg. The Steering Group) to undertake any development work and systems testing.
John van Breda is the lead developer and will ensure that changes and coding meets
the required standard and he will also need to be satisfied that the changes have
been adequately tested. The final checking, compilation of the code and the work
to incorporate any change into an R6 build will be undertaken by the Consortium,
where it may be subject to additional testing. Developers will need to fund this
work and are advised to obtain agreement from the Consortium (contact Mike Weideli)
before starting a project. They should provide an outline of what they are proposing
and the time scales. Providing the Consortium approves the change the developer will
be advised of the Consortium costs involved. The Consortium will make sure that no
two developers are working on the same area of code. Code must not be added the
the Develop Branch in the repository without Consortium approval. The Recorder 6
source code is open source, so developers may make their own changes and submit them
for consideration, however, it is strongly recommended that the Consortium is consulted
The Consortium currently has an agreement with the Recorder 6 Steering Group not
to make any major changes in functionality without first consulting with the Steering
Group as a representative of the users.
The acceptance of a change or the funding of a change should not be taken to imply
any control over the final product.