incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "ChaupalProposal" by JeromeVerstrynge
Date Tue, 25 Jan 2011 21:36:11 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "ChaupalProposal" page has been changed by JeromeVerstrynge.
The comment on this change is: Status Update.
http://wiki.apache.org/incubator/ChaupalProposal?action=diff&rev1=22&rev2=23

--------------------------------------------------

  Chaupal is an Hindi word. It means a common meeting place in a village owned by the whole
community. This truly reflects the P2P philosophy.
  
  == 0. Proposal ==
- Chaupal is to provide implementations of a P2P framework in several programming languages.
It is a continuation of the JXTA P2P project. We are looking forward at reviewing and improving
the existing JXTA protocols.
+ Chaupal is to provide implementations of a P2P framework in several programming languages.
It is a continuation of the JXTA P2P project. We are looking forward at reviewing and improving
the existing JXTA protocol.
+ 
+ Update:
+ 
+ As of January 25th, 2011, we are still waiting for an answer from Oracle regarding intellectual
property. Some members of the community have decided to create a separate project called Chaupal
on Google Code (see http://code.google.com/p/chaupal/). Its purpose is to develop and implement
a new set of P2P protocols independently of the JXTA protocols. These aim at solving structural
designs and conceptual flaws in the current JXTA protocols, including providing solutions
to issues not covered by JXTA. It is not a re-implementation of the JXTA protocols, nor an
attempt to remain compatible with these. This new Chaupal project is developed under the Apache
License 2.0.
  
  == 1. Background ==
  The JXTA project was initiated by Sun Microsystems in 2001, but since the end of 2007, Sun
has has progressively reduced its commitment to zero. Recently, Oracle has officially announced
its complete withdrawal from the project.
@@ -23, +27 @@

  
  - Comply with ASF requirements before releasing 2.8 (or 3.0) from ASF
  
- - Review and update code examples 
+ - Review and update code examples
  
  - Improve our OSGi interface
  
@@ -52, +56 @@

  The core developers belong to different companies and organizations. Some have been active
for several years. Some are contributing to other open source projects too. Some members of
the community focus only on testing released versions. It is a mixed crowd.
  
  === 4.4 Alignment ===
- The initial intention of the JXTA project was to define a P2P framework independently of
any programming language. There are currently two main implementations: Java and C. The JXME
implementation has not received much attention from the community and is more or less abandonned.

+ The initial intention of the JXTA project was to define a P2P framework independently of
any programming language. There are currently two main implementations: Java and C. The JXME
implementation has not received much attention from the community and is more or less abandonned.
  
  We are aligned with keeping any future version of the JXTA protocols independant from any
programming language. The purpose is to facilitate the communication between peers operating
under different environments.
  
  We welcome contributions from other P2P frameworks too.
  
  == 5. Known Risks ==
- 
  === 5.1 Orphaned products ===
  The JXTA C implementation has been used by Boeing for several years. The Java implementation
has been used by small companies. Oracle announced that won't be using JXTA in GlashFish anymore.
  
@@ -72, +75 @@

  The risk is small to null, since the set of contributors has never been as diverse as it
is right now.
  
  === 5.4 Reliance on Salaried Developers ===
- Medium. The community is a made of a set of salaried and free contributors, from different
entities (private) and companies (public). 
+ Medium. The community is a made of a set of salaried and free contributors, from different
entities (private) and companies (public).
  
  === 5.5 Relationships with Other Apache Products ===
  We are not in conflict with other Apache products. In fact, we have taken the decision to
avoid re-inventing the wheel and use existing open source libraries wherever possible. We
welcome discussions with other Apache projects.
  
  === 5.6 A Excessive Fascination with the Apache Brand ===
- We don't believe ASF will be our savior (lol). We have already proven we could deliver without
the brand. We are looking for a better environment than Java.net or Kenai.
+ We have already proven we could deliver without the brand. We are looking for a better environment
than Java.net or Kenai.
  
  == 6. Documentation ==
  As part of the 2.6 release, a huge effort has been performed to transfer knowledge from
Sun Microsystemm to the community. The corresponding programmer's guide contains a chapter
called 'Under the hood' which describes most of the complex mechanics of the code (see http://jxse.kenai.com).
  
  A lot of information is available via Google from our posts in the forum. Our mailing list
are registered and the email contents are available too.
  
- A book called 'Practical JXTA' has been published in 2008. The second edition came out this
simmer (2010).
+ A book called 'Practical JXTA' has been published in 2008. The second edition came out in
summer 2010.
  
  == 7. Initial Source ==
  Initial source can be obtained from copying the current our subversion repository. We could
upload it in an Apache subversion repository and discontinue our contributions to our current
repository on Java.net (REM: it has not been completely migrated to Kenai yet).
@@ -107, +110 @@

  During release 2.6, we mavenized the project. We are currently releasing our artifacts from
an open source repository offered by Sonatype. We aim at being available from the central
repository, but could not achieve this because of an open source dependency that was not available
from central repository itself yet.
  
  == 10. Cryptography ==
- Release 2.7 will see the implementation of an operation membership and cryptography system.

+ Release 2.7 will see the implementation of an operation membership and cryptography system.
  
  == 11. Required Resources ==
+ Subversion repository Issue Tracker (Jira) Website location Wiki Mailing lists Forum (new)
- Subversion repository
- Issue Tracker (Jira)
- Website location
- Wiki
- Mailing lists
- Forum (new)
  
  == 12. Initial Committers ==
+ Simon Temple (Amalto) John Boyle (OneDrum) Jérôme Verstrynge (DawningStreams) Nick a.k.a.
buzzlightyear (independant)
- Simon Temple (Amalto)
- John Boyle (OneDrum)
- Jérôme Verstrynge (DawningStreams)
- Nick a.k.a. buzzlightyear (independant)
  
  == 13. Sponsors ==
  We don't have a sponsor yet. On the Apache Incubator list, Jochen Wiedmann said "I'm not
qualified as a mentor, but I'm in for #3, which should help to get a sufficient number".

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message