Requirements and Resources
To start committing code and create modules you need to first create a login with JavaForge and then request to join this project.
You need to be familiar with Java and the NetBeans API in order to develop modules.
Currently, our commons are based on NetBeans 6.0 Release Candidate 1.
You also need to install Subversion to be able to check in and out code from the PE commons repository located at svn.javaforge.com/svn/studiosl/trunk/commons
Being an example worth a thousand words, click here to jump right in and start coding a module!
A real set of modules have been already developed for Stanford University's GPRS simulator. Please click You must login to see this link. Register now, if you have no user account yet..
How to write code for Commons
Having knowledge in a few key areas regarding coding for PE Commons will be extremely helpful in getting your code committed to the SVN repository for this project. Please take time to read the following information.
Testing a bug patch submission or new feature are the areas in greatest need of your help.
Getting the source. Creating modules and new features.
Testing of a module or new feature. Committing code to the PE Commons Project.
How source code is organized. Tools required. Where to
start. Developer branches.
Information on testing code for the PE Commons
project can be found in the Bug Guidelines.
Developer branches and branch merging
Creating and handling branches
(for developers with granted workspace).
The PE Commons Coding Guidelines attempts to
explain the use, basic styles and formatting of code used in PE Commons.
A list of roles in the PE Commons Community.
Get the source
If you already have commit access and know all there is to know
about getting started on the PE Commons project, then get
How to get in touch with PE Commons Developers
Developers serious in coding PE Commons can
be found participating in the mailing lists.
skype- Discuss new PE Commons features.
source to keep others informed of news-worthy information such as
Developer projects and thoughts.
Get the latest code
If you are wanting to help test or develop
for PE Commons, you will want to use SVN to get the most
up-to-date source code.
Search for a bug before posting it. It may already
exist in the bug tracker.
Report a bug
Before you post a bug, please take the time to read the
Our bug tracking system used to report bugs and track changes.
Participation in the lists is recommended for anyone
with a serious interest in implementing or coding PE Commons.
Various messages are sent each day.
PE Commons IRC channel - An
excellent place for developers to meet to discuss new PE Commons features. Join #PE_Commons, port 6667 at
Version control is used to obtain, manage and maintain PE Commons releases in development.
The Wiki code documentation is the built-in code and main developer documentation for PE Commons.
Developers who are interested in creating their own branded application, or in extending the existing interface, should read the
NetBeans Developer's Guide.
Visit JavaForge public SVN repositories for community-run PE Commons related projects.
PE Side projects are a list of identified issues within the code base that need attention, and offer a nice starting point to begin development for PE Commons.