Also see our user generated FAQ on the wiki.
1. What is java.net?
java.net is a premier web-based, open community created to facilitate Java™ technology collaboration in applied areas of technology and industry solutions. java.net is a central gathering place for Java technology enthusiasts and existing communities across industries, platforms, and interest groups.
2. What is the goal of java.net?
The goal is to expand the Java™ technology portfolio of applications, tools, and services by promoting conversation and collaboration around development of practical applications across industry groups.
3. What will developers find on java.net?
On java.net, developers can find and post material related to their specialized needs. Through a variety of collaborative tools such as wikis, weblogs, discussion forums, mail lists, and RSS newsfeeds, as well as traditional open source tools like CVS, java.net allows developers to come to one place to find out the latest news and opinions, have conversations with other developers who share specific interests, and ultimately engage in efficient development efforts using Java™ technology.
4. Is java.net a Sun web site?
java.net was launched by Sun and will be championed and financially sponsored by Sun; the majority of the content will come from companies and individuals outside of Sun.
5. How will Sun benefit from java.net?
A thriving java.net community benefits all active participants, including Sun. By participating in java.net communities, Sun can create better products, establish new business relationships and partnerships, and engage more closely with developers who are committed to using Java™ technology in innovative and creative ways.
6. How is O'Reilly Media involved in java.net?
In order to ensure the Java™ technology community is broadly represented, Sun has arranged for renowned publisher O'Reilly Media (www.oreilly.com) to be the feature editor for java.net. O'Reilly will solicit and manage the news features and highlighted webloggers that are presented on the opening pages of java.net.
7. How is CollabNet involved in java.net?
CollabNet provides collaborative hosting infrastructure using its SourceCast software for the java.net project space.
8. What are the specific technologies used to provide the collaborative environment on java.net?
At the foundation of java.net is an infrastructure and philosophy that supports open communication and development among peers. It includes project-support tools such as mailing lists, identities and personalities, reputation, weblogs, and wikis. It provides the tools an open source development project needs to be successful; a CVS source tree, bug-tracking system, forums, mail lists. It also provides tools for gathering information on what's happening in the industry through RSS newsfeeds.
9. How can I get involved with java.net?
There are many ways to participate. Go to Get Involved for details on participation options.
Collaboration at java.net
1. What are weblogs and blogs?
The terms weblog and blog are used interchangeably. A weblog is a type of online diary or journal run by special software that is updated often. It points to articles elsewhere on the web (often with comments) and to on-site articles.
Weblogs enable people without much web experience to create, format, and post diary-like entries with ease. In a community, bloggers often refer and link to other bloggers, with interesting and often unanticipated outcomes.
You can sample existing Blog/Weblog sites at:
- http://www.artima.com/weblogs/index.jsp - about Jini™ Network Technology
- http://weblog.siliconvalley.com - by a journalist
- http://www.javablogs.com - about Java™ technology
- http://www.rebeccablood.net - by the author of a book about weblogs
2. What are wikis?
A wiki is a collaborative hypertext document created by a software application that enables web documents to be authored collectively using a simple markup scheme and without the content being reviewed before its acceptance.
You can browse a sample wiki site by its inventor, Ward Cunningham, at: http://c2.com/cgi/WIKI?WelcomeVisitors
3. What are RSS newsfeeds?
RSS (an acronym for Rich Site Summary or Really Simple Syndication) is an XML format for syndicating web content. Using RSS news feeds, your site and java.net can publish targeted content on each other's sites. This means that your existing open source project--even when it becomes a federated project of java.net--can retain its own identity, culture, and infrastructure. Whether federated or hosted on java.net, you will have full access to other members, and cross-pollination is encouraged. To add your news feed to our list of Java-related RSS feeds, refer to http://today.java.net/pub/q/rsschannels.
4. What is CVS?
CVS is short for Concurrent Versions System, an open source, network-transparent program that allows developers to keep track of different development versions of source code. CVS does not maintain multiple versions of source code files but rather keeps a single copy and the records of all of the changes that are made. When a developer wants a particular development version of a file, CVS will reconstruct that version based on its records.
The CVS service used on java.net is based on CollabNet's SourceCast software. It is designed to help you set up your project and assign contributors to different roles; some might have full access to uploading and downloading code, others might just be able to download code.
5. What are mail lists and discussion groups?
Mail lists and discussion groups are what places like Yahoo! Groups provide. A mail list can serve a lively collection of people--or a small community--who share common interests. When paired with a drop box, such a community can share artifacts and even work on them--a small, ad hoc open-artifact community. The java.net mailing list and discussion groups are based on CollabNet's SourceCast software tools.
6. What is IssueZilla?
All development projects must somehow handle the recording and disposition of bugs and feature requests. BugZilla was written originally for the Mozilla[TM] project and is widely used throughout the world of open source. IssueZilla is a modified BugZilla that has additional tools to help route all types of issues, not just bugs and features, through a process from discovery to resolution. For more about IssueZilla, go to http://www.openoffice.org/project_issues.html
java.net compared to related developer web sites
1. Does java.net relate to the Java Community Process[sm]?
No. The Java Community Process[sm] (JCP[sm]) program is the formalized, community-based process for evolving and maintaining Java™ technology. Java technology is the only successful binary standard, and the JCP Program defines that standard in the Java[x] namespace. It charters the evolution and development of all Java specifications and APIs. For more information, see http://jcp.org
java.net is a resource for developers and others using the Java platform to develop innovative applications and to make their work environment more productive. It provides a catalog of tools and applications that facilitate development using Java technologies and encourages groups with common interests to meet and work together.
2. Will some Java[tm] Specification Requests be hosted as java.net projects?
java.net can support Java™ Specification Requests ("JSR™") projects. It is up to the JSR expert lead and the Java Community Process[sm] to decide on a case-by-case basis if this forum is appropriate.
3. How is java.net different from Java.sun.com and the Java Developer Connection[sm]?
The Java Developer Connection[sm] ("JDC[sm]" ) and Java.sun.com are web sites that represent the voice of Sun and provide materials related to commercial products developed by Sun. Developers go to Java.sun.com to download products and to access Sun support. These sites are traditional information portals that focus on Sun's implementation of Java™ technology.
java.net is the place where the entire community has a voice. Although information on Java technology from many sources is available on the site, the emphasis is on application and value-added resource development through collaboration.
Participation in java.net
1. Who can participate in java.net?
Any person, group, or company can get involved in java.net as long as they agree with the Guiding Principles of the site.
2. How can I participate in java.net?
There are many different ways to get involved in java.net:
- Join a mail list
- Contribute to a wiki
- Join a project
- Link your web site
- Federate your web site
- Request a project
3. Are there any registration requirements for participation in java.net?
You can browse the top-level editorial features, newsfeeds, wikis, and weblogs without registration. If you're interested in contributing to a wiki or commenting on a weblog, you must register at a minimum anonymously. We encourage you to register and use your username as wikis and weblogs are more effective when consistent identity can be followed. Finally, if you wish to start a project, join a project, or join a mail list, you will be asked to register your email address and a unique nickname and to agree to the Terms of Participation for java.net. The Terms of Participation outline an expected code of conduct for the site and address copyright and license concerns for contributions. More information on the Terms of Participation is availabe in the FAQ under licensing.
4. Can I post anonymously on java.net?
Yes. Comments that contribute to real reputation are probably more valuable than random comments, but you may comment on an existing wiki , blog, or article without registration. When you submit a comment, you must still acknowledge the Terms of Participation and check the "Anonymous Coward" box. Your comment will have "Anonymous Coward" posted as the nickname. You must provide a valid registration to author a blog, start a wiki, submit an article, propose or lead or contribute to a project, report a bug, or arrange to link or federate your web site.
5. What are the benefits of participating in java.net?
Participants benefit by joining with and having access to other members of the community with similar interests. At java.net, they have a centralized meeting place to go for help with their projects. They can leverage the rich set of collaborative tools available for their use.
java.net can save the effort and expense of starting a unique, stand-alone web site and allows new projects to instantly be part of the larger community focused on Java[tm] technology. Existing web sites can link or federateto java.net and still take advantage of the additional collaborative tools.
6. If we join java.net, will we be able to better influence the future of Java[tm] technology?
The Java Community Process[sm] (JCP[sm]) program is the appropriate place to contribute to the evolution of binary standards for Java[tm] technology. java.net is intended as a space to collaborate while applying Java technology, but in some cases work on java.net may lead to proposal of a Java Specification Request. java.net was envisioned as a suitable place for experimentation, and also as a framework for leading an accepted Java Specification Request.
7. Can all companies and organizations participate in java.net?
Yes. All companies and their employees interested in Java[tm] technology are encouraged to participate in java.net, as long as they adhere to the Guiding Principles of the site.
How Do I...?
1. Browse top-level editorial features, newsfeeds, and weblogs?
Anyone can browse the top-level editorial features, newsfeeds, and weblogs on java.net without registration requirements.
2. Join a mail list?
Mail lists are connected to individual projects, although each community has a low-traffic announce list that covers all announcements for that community.
To join a mail list simply go to the federated or hosted project in which you are interested in receiving information, and subscribe to their mailing list. You can see all projects in the Directory.
3. Start a mail list?
To start a mail list you must propose it to the appropriate project membership and project lead. It's always a good idea to ask the community whether it would participate in a new list.
4. Contribute to a wiki?
To contribute to a wiki simply go to a federated or a hosted project that has a wiki and select the wiki link form that home page. You can see all projects in the Directory.
5. View and comment on a weblog?
To view and comment on a blog go to the blog list page (link to blog list page) and select the blog for which you would like to contribute and comment.
6. Recommend your existing weblog for aggregation?
To recommend that we add your weblog to our aggregation list (or that we consider highlighting it), send an email to the Content Editor. We reserve the right to refuse any such request but generally, if the content is good, we will be very glad to add your link.
7. Contribute an article?
For step-by-step instructions, go to Get Involved.
8. Contribute a Java[tm] technology tool?
You must submit it as part of the JavaJar project. Before transferring your executable file, you must provide a binary license (or use the generic one provided), and agree to the Terms of Participation.
10. Join an existing project?
Visit the java.net Directory. Select a project from the list. Each project home page outlines the activities available for the project, with instructions on how to join.
11. Start a new project?
To start a new project, first browse the java.net Directory to make sure a similar project does not already exist. Before undertaking this task, please evaluate your commitment, considering the time and energy it takes to manage a successful project. Creating a Successful Project is a document that will help you evaluate the undertaking. If you are prepared to start a new project, then go to Request a Project for step-by-step instructions.
12. Host a project on java.net?
For step-by-step instructions, go to Request a Project
13. Link to java.net web site?
For step-by-step instructions, go to Link your web site.
14. Federate with java.net web site?
For step-by-step instructions, go to Federate your web site.
1. What does federating mean?
"To federate" means, "To cause to join into a league, federal union, or similar association." (American Heritage Dictionary).
On java.net, federated sites will typically be sites that are already mature. They have an existing, stable community and are self supporting. For a variety of reasons, these groups may wish to maintain their own established infrastructure and to tie into some of the enriched features that java.net offers.
2. Why should I federate?
By federating your site you will be able to provide your current users with the enriched web services available on java.net. Conversely, your site will become known to and available to many potential new members. Some of the additional benefits of federating are:
- You will have the opportunity to be a leader in a particular area that is important to you.
- Your weblog and wiki contributions will be cross referenced among others on the site.
- The java.net search engine will find your contributions more readily and more often.
- Your news releases may be highlighted in the java.net RSS newsfeeds.
3. Are there different levels of federating to choose from?
No. In fact, the term "federated" is a loosely defined term that assumes some proactive level of commitment to the java.net community beyond a simple link. At this time there are no hard requirements as to what that might be, but in open source generally your reputation is built by active and constructive participation.
4. Can we participate in java.net without federating?
If you do not have an existing web site to federate, you can still be part of java.net. You can join a mail list (link to get involved page); start a project; join an existing project; contribute to a wiki; comment on a blog or contribute an article; or simply browse the site and leverage some of the content to address your own needs.
6. If we federate, do we need to change our license?
Generally, no. If you are federating an existing site to java.net, you will probably not have to change your software license. This is a difference between federation and migration to hosting directly on the java.net infrastructure.
7. If we federate, do we need to change our governance?
Generally, no. You will not have to change your existing site governance when you federate to java.net as long as your site is open to all java.net members and supports the Guiding Principles of java.net.
Projects at java.net
1. What types of projects are likely to get started on java.net?
Current projects at java.net have evolved from an interest of one person, and/or a collective interest, or a need among a group of people. Some of these groups already exist and have been looking for a venue to engage with others. We have engaged in enthusiastic conversations with:
- Standards groups that want to collaborate on applications using Java[tm] technologies, but which have no expertise in site or collaborative code management.
- Industry-specific application engineers who are looking for a place to reach out to other engineers developing and supporting similar systems.
- Universities around the world with technologists who want to collaborate on research and need a home.
- Educators who wish to collaborate on developing new courses on Java technologies.
- Companies that want to expose some ideas to developers during their exploration stages.
- ISPs and support engineers who have small utilities and tools they are willing to share.
- Java User Groups that want to share their meeting topics and lectures.
- Small companies and individuals who are cooking up ideas and looking for a forum of developers.
- Existing communities and web sites focused on Java technology that want to leverage the information shared on and around java.net.
2. I have an idea for a new interest group. How do I engage the java.net community?
First, we recommend you review wikis and weblogs on the site for conversations that might be related, and scan project homes and their sub-projects for similar efforts. If you believe an interest group exists related to Java[tm] technology and there is no suitable venue for members to communicate and/or develop code together, you can solicit people with similar interests with a blog, mail list, or an entry to the incubator.
3. Can I customize my project home page?
There are some opportunities to customize the look of your project home page. For more details, go to Request a project.
4. Is java.net for open source projects only?
Today, open source projects are the only projects java.net supports.
5. How do I migrate my existing project to java.net?
For step-by-step instructions, go to "get involved".
1. What software licenses are offered on java.net?
When you request to start a project, you will be asked to indicate the license you wish to use. Please visit the License List for a complete listing of licenses that java.net offers. Here are details about a few of them:
a. Open Source License:
java.net and the CollabNet SourceCast software can support the use of any Open Source Initiative (OSI) approved license for projects developing source code. java.net is pre-configured to support the BSD, Apache, SISSL, GPL, LGPL, and MPL licenses.
b. Sun Community Source License ("SCSL")
In addition, java.net supports projects using source code provided under the Java[tm] source code SCSL. The SCSL makes source code available to a community of registered users who agree to abide by restrictions on use of the code outside of the community. Projects under SCSL will not allow content browsing by unregistered users.
c. Binary Licenses
One of the projects on java.net is a Java[tm] JavaJar[tm], where you can post binary utilities for other developers to try.
d. Document Licenses
If your project does not include source code, but does include generating a significant document, such as a manual, a teaching course, or a research article, you may want to choose a document license that outlines copyright rights. java.net supports these licenses:
If you are new to open source and/or Java[tm] source code licensing, there are many, many articles and overviews describing the different licenses and strategies. Here is a brief list of some of these resources. Choosing a license is a complex process. Be sure to read the full text of any license you are considering before making your choice.
The JRL is a new license that was created specifically for universities and researchers who want to use Java[tm] technologies as subject matter for learning and research. it was written to simplify and relax the terms of the existing "research" section of the current SCSL.
This license is designed for the research community. This includes schools and universities as well as companies that are interested in investigating new products and services using Java technologies. This research license is only for initial research and development projects. If you decide to use your project internally for a productive use, and/or distribute your product to others, you must sign a commercial agreement and meet the Java compatibility requirements.
The JRL is intended for all Java platforms, profiles, and standard extensions currently covered under Java SCSL licenses (e.g. J2SE, J2EE, and J2ME).
2. What are the distribution and compatibility requirements for JRL?
There are no Java compatibility requirements for JRL. The license encourages innovation and experimentation using the Java technology core. It is expected that research implementations will not be compatible with the Reference Implementation from Sun.
Work done on JRL-licensed code can be published in the usually accepted academic manner as long as appropriate references to the Java Research License are mentioned, and the correct copyright information is included. Binaries can also be distributed for research purposes under a license of your choice that complies with the terms of the JRL (e.g. includes copyright notices and references the JRL). Code modifications can also be shared with other researchers, provided that the other researchers have accepted the JRL.
For more details on JRL, please refer to the JRL FAQ java.net/jrl.csp
3. How will the java.net community be governed?
java.net governance will evolve as the site and its participants become more engaged. As a start, Sun Microsystems has written a set of Guiding Principles. Individuals and communities should join java.net only if they agree with, and adhere to these principles. The java.net Community Manager will have day-to-day management and governance responsibilities