Serna Free is an Open Source XML editor now

Serna Open Source Contribution FAQ

Q: How I can access repository with Serna Free source code?

The source code of Serna Free XML editor is hosted on bitbucket.org project hosting service. You will need Mercurial DCVS to work with Serna Free source code repository.

Official project page:

To clone the repository, use the following command (assuming you have Mercurial installed): 
hg clone http://bitbucket.org/syntext/serna-free

To build Serna Free from scratch you will also need several third-party packages, which you can download from http://downloads.syntext.com/serna-free-3rd.

After that, follow the instructions of the INSTALL file located in the trunk directory.

Q: Can anyone contribute to Serna?

A: Yes, anyone can contribute to Serna.

Q: How I can contribute to Serna?

A: The easiest way to do so is to clone Serna repository on BitBucket and commit all changes to there. When you finish your development, send us repository merge request.

Alternatively, make your modifications and send us patch by e-mail to serna-patches@syntext.com.

Note that prior to sending us your patches you must accept Syntext Contributor Agreement. If you do not accept Contributor Agreement, we will not be able to include your contributions to Serna.

Q: What are the guidelines for contribution?

A: You must follow the coding conventions (Syntext C++ Coding Conventions, Syntext Python Coding Conventions). Also we recommend that you document any new functions/classes, make sure that your changes work on all Serna platforms, check that no unit tests regress with your changes, write new unit tests as needed. Discuss your work with other developers.

Q: How will Syntext developers decide which contributions are accepted?

A: All contributions must meet the basic technical requirements, adhere to guidelines and pass a legal code check. Serna is used across many industries and platforms, so your change should add value and not degrade experience for existing users.

Q: How long we can expect to wait for a decision on the submitted changes?

A: We are trying to do our best review and reply to contributions as quickly as possible. However, we cannot promise a fixed turnaround time.