If you are not a committer and you have found a problem in or have an idea for an improvement for the Endefr project, you can create an issue in the issue tracking system.

To ensure that the issue is processed as quickly as possible, follow these steps:

All communication about the issue has to be done by using comments. This ensures that everybody can easily track the history of the issue.

Monitor the issue after you have submitted it. People (not only committers) might ask for clarification. Responding to their questions quickly ensures your issue is processed as fast as possible.


All your contributions must be licensed under the Apache License, Version 2.0.


When you make changes to the project (either directly as a committer or by submitting a patch) you retain the copyright of those changes.

Some files of the project (currently only Java source files) contain a copyright statement. If you change one of those files add your full name to the list of copyright holders. Also change the years of the copyright statement if needed.

Becoming a committer

If you contribute a number of significant patches of good quality you are eligible for becoming a committer. A committer (after getting your consent) or you yourself can propose that you should become a committer. The committer proposal has to be posted on the development mailing list. If none of the current committers have a good reason why you should not be a committer you will be added to the project.

Contact information

Committers have to let the project lead know as much contact information as possible. This is necessary for negotiating a commit silence, and for private committer meetings about sensitive issues.

Below are a couple of contact information items a developer could provide:

The project lead will collect all contact information. If (part of) your contact information changes you have to let the project lead know about it. The project lead will make sure that the other team members have the latest information.

The project page of Endefr at