Process to participate in ProjectIdeas

This page describes the process to participate in GlassFish Project Ideas.

The projects are arranged in groups (shown in the first column) for convenience. Click on the project name to see more details about the project. Each project is submitted by a GlassFish community member. Some of the projects have a mentor assigned to them. The mentor is an expert in that area and will guide you through out the project. It is highly recommended to pick a project with an assigned mentor. Some projects also provide the amount of effort involved.
Sun Contributor Agreement - Each person willing to contribute to the project must sign SCA. Please contact [Jagadesh Munta] or [Judy Tang] for getting the process started. One SCA is valid for all Sun-sponsored projects.

After mentor/mentee relationship is established and SCAs are signed ...

1. Bootstrap - Mentor & Mentee(s) "meet" over the phone/email/IM/webex/whatever_is_convenient. The expected outcome of this activity is:
   1. Mentor creates a new project page linked from the ProjectIdeas wiki. This new page will be the homepage for that project and needs to be updated bi-weekly. It should should have:
      1. Team members name, email id and IM (optional)
      2. Design docs
      3. Workspace information
      4. Pointer to latest binary build & docs
   2. Mentor marks the project taken by specifying "Started" in "Status" column. Other statuses are
      1. "In Progress" - after the initial design is completed
      2. "Review" - after all the design/coding/testing/docs efforts are completed and final review is going
      3. "Finished" - after mentor has signed off the project
   3. Mentee(s) need to write a one-pager (may extend to 2 pages) describing their understanding of the project, design, expected outcome and schedule. The schedule should highlight milestone builds with feature sets and their timeline.
   4. Exit criteria - A clearly defined exit criteria needs to be defined. This will allow everybody to agree to a common goal before the project can be concluded.
   5. Mentor/Mentee(s) agree upon a project name - Trying to find out if it needs to be legally approved.
2. Code Contribution - Each mentee in the project need to have a java.net id (from Register page). A new directory, with the agreed upon project name, is created in "https://spotlight.java.net/svn/spotlight/trunk" (see more below). All the code is contributed to that directory on a continuous basis. Use of Maven is highly recommended.
   1. 3rd party tools - The projects can use any 3rd-party tools. If the code is consumed in any of the GlassFish related projects then an inbound-OSR needs to be filed.
   2. Please commit code only to your project.
   3. The code may be hosted on a different repository such as jax-ws-commons.java.net or a different java.net project. The reason for choosing the different location needs to be clearly mentioned on the project page.
3. Recommended Artifacts
   1. Docs - Documentation is a very important aspect of the project. This is not restricted to adding javadocs and in-line comments but also preparing more detailed docs that describe how to get started, pre-requisites, environment, limitations, etc. It is required for each project to have documentation consistent with the binaries at each milestone.
   2. Tests - Each functionality in the project needs to have fully automated test(s).
   3. Samples - For external users, there should be samples (with READMEs) on how to get started with the project.
   4. Blogs - Highly recommended to get a blogging account on weblogs.java.net/blog
4. Communication - Usage of users@glassfish.java.net alias is recommended for all technical discussion. It is highly recommended to use the project name in the email subject for a clear identification.