 |
Our commitment is to provide the infrastructure and people involvement for promoting community development. This infrastructure enables Jcorporate and a community of companies, developers, and members from other open source projects, to openly and collaboratively develop. This exciting model enables synergy, where the creation of dynamic ideas is greater than what could be achieved individually. Send contributions to contribute@jcorporate.com or post on the forums. |
Jcorporate is committed to providing free access to all interested participants. All of our code is distributed under the Apache Style Software License or GPL license, both OSI-approved licenses. The projects' user and developer forums are all open to the public and contributors are welcomed with open arms.
There is no cost required to contribute code to the projects. However, there is usually a time committment that is required in order to contribute to a project. For some, time is cheaper than money. For others, money is cheaper than time (lucky you). We realize that, and want to promote contributions from everyone - no matter the form.
Open Source projects like Expresso are successful because of people like you. We invite you to participate as much or as little as you choose. Everyone’s input matters, and we encourage you to participate in any way that you can. A community approach to building software products has a number of benefits:
As many of you are involved in developing custom solutions it is desireable to contribute code back to the projects so that it becomes part of the standard release. Collaboration is intended to further propel innovation of the platform. Come and help steer Expresso’s destiny. Start by:
To be a contributor simply contribute some code or documentation via contribute@jcorporate.com which is then checked into CVS. Certainly feel free to post your ideas to the forums or listserv where it encourages collaboration on the ideas. Once you are a contributor you can enter tasks directly into the Task List where you have the benefit of receiving email notifications anytime these tasks status is changed - so that you can more easily track their progress.
Anyone may participate to the development process. We encourage your writing, discussing, proposing from ideas to code to implementation. We look forward to people willing to test the various pieces of software, in various environments, and to track, reproduce, isolate, and fix problems reported by the user community. We consider the reporting of problems to our tracking systems to be a valuable contribution as well. The more you contribute the more recognition you receive from the community. You can get involved by:
Another way to support the open source projects through:
Email sales@jcorporate.com if you have any questions about the above.
Participation in production of the actual code base for Expresso is what takes Expresso to new levels. The nature of users using Expresso results in new contributions in the real world in various environments results in problems reported and code contributed by the user community.
| The developers have put an immense amount of work into these projects and in the true spirit of open source, they very much appreciate your enhancements to the community in exchange for using the software. You can also support the open source development and our full time developer resources by purchasing Premium Support or sponsoring development. | Send contributions to contribute@jcorporate.com or post to the forums. |
Copyright of contributed code is nonexclusive both copyrighted by its author and copyrighted by Jcorporate Ltd. separately, meaning each party has "All rights reserved." Authors of significant contributions must have a signed copy of the Contributor License Agreement on file at Jcorporate.
If you have cvs write access (CVS info) as a Major Contributor the following is the peer review process for commits. The process is as such:
Just because you aren’t contributing code or fixes to Expresso, doesn’t mean that you aren’t a valuable resource. A great way to help move Expresso forward is by giving feedback on your experiences using Expresso. This takes the form of reporting bugs, making feature requests, giving general product feedback, and contributing your usage stories so others know how Expresso is being implemented to build solutions.
You can contribute as both a novice programmer or skilled developer.
We welcome both students and commercial developers. There are
many tasks which may be performed by a novice programmer. Use
the software and review its visual appeal and error messages. Document
the issues and make a list of what could be made to look better or
reworded to make more sense. Consider possible ways to remedy the issues
and attempt to fix them. Although you may not be able to solve all
the issues you documented, you can post a patch along with a listing
of the issues resolved and a list of issues which remain to be solved.
Adding additional error output and debugging code can be of great use to a
project. Such additions don't tend to take a lot of time. These are useful
as good software provides consistent, easy-to-read messages which are both
of practical benefit to the end-user and useful to the developer during the
troubleshooting process. Submit changes in the form of a patch as we would
be very grateful to receive them.
A most fundamental job a novice may perform is to test and review or audit the released software and documentation. It is most helpful to the project to have a third party reviewing work, especially early releases. Reporting the results of such tests and submitting changes to documentation according can help ensure a higher quality release.
Another level of support you can lend to a project relates to documentation.
And documentation can lag in the develop process. We would especially
like to ask developers contributing code to assist in the documentation of
it since they are intimately involved in its creation - makes for better
documentation.
It is good practice to submit updates to documentation when you find mistakes,
bad grammar, or old information (broken URLs, incorrect company contact information,
etc.). It is also a good time to review the documentation thoroughly when
you are reading it.
|
|
Home | Products | Services | Partners | Customers | About Us | Login | Forums | Contact Us |
Copyright © 2001-2005 Jcorporate
Ltd. All rights reserved. Copyright Privacy
Last Modified:
19-Jun-2005
