If there is a particular bug you are interested in fixing, then let us know on the mailing list. We can give you suggestions on how to proceed, and we can let you know if anyone else is currently working on that bug.
There is a weekly open conference call for contributors to Sequoyah Project, feel free to contact members of Sequoyah team to get the details.
If you find a bug, log it. If you find a bug that you think is a duplicate, is not a bug, etc. feel free to comment saying so.
You can also:
Whether you're wanting to fix a typo in javadoc or to implement the next big bang feature for Sequoyah you'll need to know a few things before you contribute code.
All checkin comments should be formatted like this:
 fixing ugly images
 apply patch from Ewa Matejska for remotecdt-over-dstore
We do not want to be too restrictive right now - especially do not rewrite existing code just to make it conform to some naming convention. Most of the Sequoyah code seems to follow proper coding style already. In the end, well want to produce code and APIs of Eclipse Quality. Therefore, we better strive for quality early. Which means, try to follow common accepted guidelines for writing new codeSome useful references are:
Some best practices are:
To contribute a patch, first be sure you have the latest version of the code from our repository at SVN. Implement your modifications and save the file(s). Right-click on the package you are editing, go to Team -> Create Patch and follow the wizard. Then, attach this file to the bug. Finally, commment in the bug entry what are your modifications.
We try to be prompt and responsive on the mailing list but there's always room for improvement. If you know the answer to a query feel free to respond.
The wiki is open and can be edited by all. If you find a typo, a broken link, or anything that you view as a small issue feel free to fix it. If wanting to contribute a significant amount of information or create a new article we request that you log a bug so that we're aware of what you're contributing. This is so that we can ensure consistency structurally and in the message conveyed.
As part of the DSDP Restructuring, process, Sequoyah has moved to Tools project. The following items have been affected and updated: SVN repository, Bugzilla, IPLogs and web resources in general (download pages, web site, wiki page, blog). Those changes shouldn't affect Sequoyah users in any way different than reconfiguring SVN access and using different download pages.
Sequoyah 1.0.2 is now oficially available for download here. Please, check it out and feel free to leave us a message on our mailing list! :)
Sequoyah 1.0.1 is now oficially available for download here. Please, check it out and feel free to leave us a message on our mailing list! :)
We have just added a guide to help users setup their development environment correctly.
Check out our latest post
on Sequoyah Project Blog!
Soon we'll share more of our thoughts and experiences!
We have a proposal for extending Localization framework in order
to support other resources, such as image, sound and video.
You can find more information about it here.