You can contribute by many ways to EDAS2, you don’t need and special skills: just the wish to participate in the project. One of the best way to participate is to post (and respond to posts) on the Forum

This seems evident, but using and installing EDAS2 is an important contribution for EDAS2 developers.

With the bug reports you submit, we can make of EDAS2 a more reliable software. Submit a bug

We will look to incorporate the following patches and functions provided by the community:

• Patches and additions support core functionality needed by a broad audience
• Submissions are approved by the core developers
• Submissions are provided by approved project committers

Please follow the code contribution process outlined below. Suggestions to improve the process are welcomed.

EDAS2 needs documentation. Installation, using, tips… Please use the wiki.

You can also support development of EDAS2 by sponsoring the development of additional functionality. In some cases this functionality or customization may be specific to the needs of an individual group, or may be helpful to all users. To help the project grow, we ask that commissioned work be made available to all at the discretion of the community.

• A list of proposed changes to any aspect of the system as differs from the latest release on the Sourceforge site. These include screen changes, function changes, database changes, or value changes. Each change should be accompanied by a brief explanation of the change and the reasoning for it.

• Intended implementation time line
• Any other documentation that can be provided such as use cases and design information

• Specialized capabilities and functions should be implemented as optional modules to the base project
• EDAS2 core developers will contact individual external developers if any changes are approved and give them credentials to transmit changes

• Only files that have been changed, but must also consider changes to the database (through alter scripts), as well as control, label and value changes. The project prefers to receive patches when possible. The following links provide more information about creating patch sets.

• http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.user/tasks/tasks-68c.htm
• http://docs.moodle.org/en/Development:How_to_create_a_patch
• http://javacvs.netbeans.org/doc/jihlava/functional-spec.html

• All code changes must be clearly designated with comments, and include the name and organization of the developer who made them
• Use cases or descriptions of the changes
• Test cases or descriptions the proper, intended functionality of the change that can be used to evaluate that they have been implemented properly.

Download this page in Open Office format