Get Involved

Morphis is always looking for new people to help out. We're looking for leaders, developers, and technical writers to contribute time and effort to the Morphis project. By creating a development community we ensure Morphis:

• can reach every mobile device
• is extensible and scalable
• is a quality product
• meets the needs of everyone

If you're interested in the Morphis, the first thing you should do is to join the morphis-interest mailing list. This will keep you in tune with new features, support issues, and provide you a channel to ask questions to the Morphis community. The morphis-interest list is the right place to pose ideas, suggestions or improvements.

If you have a question which requires individual attention, or if you would like to play a particular role in Morphis development, please email info@morphis.org.

If you've found a bug, you can use our bug submission form, or send an email to bugs@morphis.org.

How you can help

Specifically, Morphis is looking for help in the following areas:

• Device Registry (device.xml) updating: We've already collected information on many different wireless devices. However, there are devices we are missing, and properties that are not correct. By updating the device registry, and submitting your changes to support@morphis.org, you'll provide a benefit to every Morphis wireless application.
  
  
• Device stylesheets: With new device, come new browsers (and, browser bugs). As wireless developers know, every device has its own features, and its own problems. Morphis uses XSL stylesheets to translate WAX into device-specific markup languages. If you're testing with a device that does not work properly with the provided stylesheets, create your own! And, consider contributing your new stylesheets so all other community members may benefit.
  
  
• New translation filters: If you've done something cool or useful with Morphis translation, consider contributing your Java code!
  
  
• Extending the WAX language and features: A powerful way of extending Morphis WAX is to create new WAX tags.
  
  
• Fixing bugs: If you've found a problem with Morphis, feel free to fix it and submit the patch! An online bug tracking system is on the way.
  
  
• Improving performance: Obviously, and improvement in performance would be appreciated.

CVS Access

For information on retrieving the most recent version of source code via CVS, please check out these instructions.

Submitting Changes

We are in the process of setting up an online CVS repository.

Until that time, you may submit your features, bug fixes and new code to support@morphis.org. Along with any code, you will need to include your name, address and phone number in case we need to contact you. Your personal information will be kept private and undisclosed, as per our privacy policy.

We expect to have more community information, and organized project plans and teams as the Morphis project evolves.

Coding Styles and Guidelines

In order to develop a quality product, Morphis requires that developers follow certain rules:

• JavaDoc style comments: If you're writing a new attribute or method, you must provide a verbose description of its functionality. In addition, if you come across methods that are not documented, please set an example and document it.
  
  
• Coding style: For the most part, all code is written to Sun's Code Conventions for the Java Programming language as defined at http://java.sun.com/docs/codeconv/ .
  
  
• Whitespace issues: In order to be consistent, all code should be indented in 4 space increments. Since many editors display tabs in different ways, please do not indent using the tab character.