The ScopeSET Support and Community Portal
View all tags
Tags:    No tags associated yet.

Contributing code:

Any contributions are highly appreciated. If you find something on the roadmap or the open enhancement requests we would appreciate if you could create a specific community change ticket and link it to the originating ECR or roadmap ticket. The same principle applies to any bug-fixes and of course we also appreciate any changes which are not yet logged on the roadmap or elsewhere.

Of course, you can also let us know about any ideas, suggestions etc. on the OpenAmeos Forums

All code changes you contribute can then be committed using the CCT ID (see below).

OpenAmeos Issue Trackers:

  • Roadmap - high level feature plans
  • Link not available [ScopeSET change request] tracker (ECRs) - usually submitted by maintenance customers
  • Community change tickets (CCTs) (please register to create tickets) - anything the community plans to do

Getting the code:

The OpenAmeos source code can either be downloaded as ZIP, or be checked out from the SVN repository

Building the code:

Coding styles:

  • TBD

Change process:

After every binary distribution release, ScopeSET synchronizes any changes for that release (taken from the Link not available [ECR Tracker] into the public SVN repository. Public changes are optionally synchronized back into the repository for binary distributions.

Committing code:

In order to commit code, please contact ScopeSET for write access to the repository. Any commit needs to have a corresponding community change ticket, the commit comments need to look like this:

By committing code to the SVN repository, you implicitly assert, that the intellectual property right on that code is your own and that you are transferring that IP to the project.