PLEASE READ: Important information about the consolidation of the JXTA.org site

[Bernard Traversat]

Hi,

As some of you may have noticed we currently have two hosting sites
for the JXTA community:
   - www.jxta.org
   - www.jxta.dev.java.net

For historical reason, as the first project hosted on Collab.net,
the jxta.org website has been managed as a separated hosted
instance than the Java.net site. A couple of years ago to respond to
community demands to host projects that use a different
OSS license than the JXTA license (jxta.org can only host
projects that use the JXTA license), we created a JXTA community
umbrella project under Java.net (jxta.dev.java.net) to host these projects.

In order to reduce project management, overhead and inconsistency
between the two sites, we have just started the process of consolidating
all the JXTA projects to the jxta.dev.java.net umbrella project. When
done we will create a redirect from jxta.org to jxta.dev.java.net, so
people can access the combined site via the common jxta.org URL, as
well as an individual redirect for each *.jxta.org project to their new
location *.jxta.dev.java.net.

We see a number of compelling reasons to combine these two sites:

- The Java.net site provides a broader OSS community environment
and will bring the JXTA community closer to all the Java.net communities
increasing potential community cross-pollination between projects. We
are already seeing a few great cross-community development (the JXTA
SIP-communicator provider, the Glassfish Shoal project to name a few),
and are looking to foster even further community collaborations by
bringing all these communities under one roof and one set of common tools.

- As mentioned previously, the java.net site provides a wider set of
licenses to host projects. While we are still advising people to host
their projects under the JXTA license, the java.net site will provide
community members with the choice to select the most appropriate license
for their project.

- Having two hosting sites mean that we have to manage two
separate project databases and web sites. Many of our users have
different userID on java.net and jxta.org making life difficult and in
some cases create confusions. We want jxta.org users to use the java.net
site, but they may have a different user ID than their current jxta.org
user ID. Combining the two sites will address this issue. In addition,
we are already using java.net for the jxta wiki since jxta.org doesn't
have wikis and the requirement for two accounts has been cited as a
blocker to people contributing to the wiki.

- jxta.org being a smaller site than the main Java.net site is lacking a
number of new capabilities that are already deployed or planned to be
deployed for the main Java.net site. Having jxta.org under java.net will
allow us to leverage all the support provided for all the java.net
communities.

- Finally, this site consolidation is providing the opportunity to clean
up project database and site information. Many of you have complained in
the past that core platform projects (JXTA-SE, JXTA-ME, etc) contain a
large amount of old, irrelevant or stale information that are often
confusing and misleading for new developers and users. We are looking as
part of this consolidation to clean up the core platform and related
projects, updating project information and removing old and misleading
information.

We have worked with the java.net hosting site folks to ensure that
the combined jxta.org site under jxta.dev.java.net will receive the
same level of functionality, performance and support than community
members have experienced under the current jxta.org site.


WHEN THIS CONSOLIDATION WILL BE COMPLETED ?

We expect the consolidation to be completed by end of June. Our intent
is to perform this consolidation as quickly as can in order to avoid
potential confusion on which site users should use. As we deactivate
the jxta.org site, we will redirect all the project URLs *.jxta.org to
their new jxta.dev.java.net location.

We will keep you inform about our progress as we are consolidating the
two sites. For the time being continue to access JXTA projects as you
have done it until hearing further notice.

CURRENT STATUS:

We have started the process of migrating the core projects under the
jxta.dev.java.net site:
   - Platform (Jxta SE)
   - Jxme (JXTA ME)
   - JXTA-c
   - Spec
   - Shell
   - Guide
   - CMS
   - MyJxta2
   - bench

We have reviewed all projects on jxta.org and generated a tentative
list of projects that will be moved to jxta.dev.java.net.
Our decision was based on current and past project activities as well as
relevance of the code present. Please, review carefully the proposed
list on the attached document, and let us know as soon as possible if
you are depending on any projects that is not in the planned list.

We are in process of notifying all project owners to help migrate their
projects.

AS A PROJECT OWNER, WHAT DO I NEED TO DO?

If your project is on jxta.dev.java.net you are done! If your project
is hosted on jxta.org and your project is in the planned migration list,
in the next few days we will contact every project owner individually to
work with them on the logistics and the process to migrate their
projects to the jxta.dev.java.net site. In the mean time if you have any
questions feel free to contact us.

AS A PROJECT COMMITTER, OBSERVER or USER, WHAT DO I NEED TO DO?

As this point you have nothing to do! Continue to access the jxta.org or
jxta.dev.java.net as you are currently doing it. When projects are
officially migrated on jxta.dev.java.net, we will inform you. You will
need then to re-subscribe to the project, re-apply for your project
role, and re-subscribe to project mailing-lists. Unfortunately due to
legal reasons we will not be able to move your project subscription from
one site to the others. This is also giving us the opportunity to clean
the project membership for members that are no more active and provide a
better accounting of active users.

We appreciate your help and support during this consolidation process.

The Sun JXTA Engineering Team



---------------------------------------------------------------------
To unsubscribe, e-mail: announce-unsubscribe@...
For additional commands, e-mail: announce-help@...