We have more than 300,000 downloads of JVCL from our Website. If everyone would volunteer only for one hour a week, we would have almost 300,000 hours a week, or an equivalent of 7500 full-time people working on this project. And with this we could have tremendous results. Think about it - only 1 hour a week. 


Here's some ways you can contribute:

Writing help

Providing help for the components in the library is one of the most important tasks for us. If you want to participate in writing help, please go to the JEDI Online Help website and start editing the items in that system. Your work will make it into the system after review. This is the easiest way to contribute as it only requires an Internet browser and connection. Spending a few minutes documenting components you use everyday and know well is one the best way to show us your appreciation.
Should you want direct access to the files, you should contact the help coordinator for further instructions.

Donating components

The JEDI VCL is built upon donations made by the community. If you have components that you would like to submit to JVCL then we would love to receive them. There are few rules that need to be followed when donating code. They are primarily needed to protect ourselves and to make the inclusion of your code as efficient and smooth as possible:


Writing demos

We are always looking for more demos that shows off the components in JVCL. Writing a demo is also a great way to get to know a component. If you have demos you would like to donate, submit them through the bug tracker. Please select Category "03 Donations", and attach a zip file with your code. If you write a lot of demos, you might get developer access to CVS, so you can upload your demos directly.

Fixing bugs

The JVCL is large and there is bound to be bugs in some of the components some of the time. If you want to help out fixing bugs, log in to our bug tracker and take a look at the reported bugs. If you fix a bug, you can attach it to the bug report along with a description. If you fix a lot of bugs, you might get developer access to CVS so you can make updates to the source directly.


Writing test

We need help in writing test code for the components in JVCL. We use dunit to write the tests. To find out what tests are already available, see the tests/DUnit folder in GIT or contact one of the admins.



If you speak another language than english, you can contribute by translating the texts in JVCL into other language(s) you know.


Translating JVCL is a matter of creating a copy of the jvcl.po file in the \locale folder of the JVCL installation and translate it using poEdit ( Once you are done, you can upload the translated po file to either our bug tracker or to the jedi.binaries newsgroup and a JVCL developer will take care of adding it to CVS.



If you have other skills or ideas on how to improve JVCL, please contact us and we will try to help you make it happen.