incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "ChaupalProposal" by JeromeVerstrynge
Date Mon, 08 Nov 2010 15:04:30 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: Chaupal page creation.


  ## page was copied from AbderaProposal
  ## page was renamed from AriProposal
- = Abdera, an Atom Implementation Proposal =
+ = Chaupal, a P2P framework =
+ 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. Rationale ==
+ == 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.
- The fundamental goal of the project is to provide a high-quality and functionally-complete
implementation of the Atom Syndication Format (RFC4287) and the Atom Publishing Protocol specifications
published by the IETF Atompub working group.
+ == 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.
- (the ancient city of Abdera, Thrace was the birthplace of the Greek Philosopher Democritus,
one of the [[|co-originators of "atomism"]])
+ Since 2009, the JXTA community has taken over and has released version JXTA/JXSE 2.6 in
July 2010. A complete knowledge transfer has been performed with a former leader from Sun
Microsystems. The community has enough material to perform a new 2.7 release.
- == 0.1 Criteria ==
+ We can be reached via our dev mailing list (see
- === Meritocracy: ===
+ == 2. Rationale ==
+ The JXTA community needs to find a new supportive environment to develop this project. We
have voted overwhelmingly for ASF. There is currently no P2P projects at ASF. We believe this
technology has a future and that ASF is a proper environment to nurture its development.
- Apache was chosen for an incubator for the guidance the community can provide.
+ == 3. Initial Goals ==
+ - Release version 2.7 from before moving to ASF
+ - Comply with ASF requirements before releasing 2.8 (or 3.0) from ASF
- === Community: ===
+ - Review and update code examples 
+ - Improve our OSGi interface
+ - Implement NAT traversal
+ - Explore and implement binary transfer protocol
+ - Review and improve the JXTA protocols (followed by implementation)
+ - Extending test coverage core code.
+ - Re-engineer core code for better scaling and usage of resources
- The contributed work was inspired by open source development and by the need to have functionally
complete implementations of the Atom specifications available for developers to use.  To be
successful, the project needs to build a strong and diverse community to validate its mission
and carry it forward. Further, the project needs to be guided by the same general principles
of open and transparent development that has helped to shape the standards upon which the
project is based.
+ == 4. Current Status ==
+ Around 20 different individuals have contributed to the 2.6 release with patches, testing,
and documentation. The technology is used live by a couple of companies. As mentioned above,
we have enough material to perform a new release.
- === Core Developers: ===
+ The community has complained about the quality of for a long time. About a year
ago, we decided to initiate a move to Kenai. We had to put this on hold since the future of
Kenai became uncertain following the Sun acquisition by Oracle. If our project is accepted
by ASF, we will freeze that migration completely.
- The initial committers for the project are employees of the donating company. Two of the
developers have worked on open source projects before and have experience with and a deep
understanding of open source principles.
+ === 4.1 Meritocracy ===
+ The JXTA project was governed by a board of directors, but they did not organize elections
in 2010. Since its inception, the community has operated according to the spirit of Open Source.
Patches, release scopes and suggestions are reviewed and discussed by the community. Votes
are performed when necessary. We believe we are compatible with the Apache spirit.
- === Alignment: ===
+ === 4.2 Community ===
+ The community was originally centered around Sun Microsystems, but many outside contributors
have participated to the development of the technology right from the start. The firsts books
where written by third parties. Since 2009, all the contributions to the project come from
external parties.
- The initial code has been implemented in Java and is based primarily on the same Apache
Axiom / StAX XML parsing API that underpins the Apache Axis2 project.  As such, the implementations
draws heavily on the work of other existing Apache projects and will continue to do so. 
+ === 4.3 Core Developers ===
+ 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.
- == 0.2 Warning signs ==
+ === 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.

- === Orphaned products: ===
+ 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.
- The initial committers are users of this toolkit and have a long-term interest in use and
maintenance of the code.
+ We welcome contributions from other P2P frameworks too.
- === Inexperience with open source: ===
+ == 5. Known Risks ==
- Several of the commiters are very experienced in Open Source environment. All efforts have
and will be made to ensure that the work done and momentum will be in strict adherence to
open source guidelines.
+ === 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.
- === Homogenous developers: ===
+ The community is small, but has proven its dedication with release 2.6 and upcomming release
2.7. We believe moving under ASF will only strengthen our community.
- As noted above, the initial list of developers consists of paid employees of the donating
company.  However, efforts will be made to actively expand the team of developers committing
to the project.
+ === 5.2 Inexperience with Open Source ===
+ The risk is null, since the project has been operating under open source principles right
from the start.
- The current list of committers bring with them a broad range of experiences with open source,
standards, emerging technologies, and product development.
+ === 5.3 Homogenous Developers ===
+ The risk is small to null, since the set of contributors has never been as diverse as it
is right now.
- === Reliance on salaried developers: ===
+ === 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). 
- The initial set of committers are salaried developers. Through the incubation process, more
diversity will hopefully be achieved in many aspects, including reliance on salaried developers.
+ === 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.
- === No ties to other Apache products: ===
+ === 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 or Kenai.
- The initial codebase relies heavily on existing Apache technologies and will continue to
do so.
+ == 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
- === A fascination with the Apache brand: ===
+ 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.
- The committers are intent on developing a strong open source community. We believe that
the Apache Software Foundation's emphasis on community development makes it the most suitable
+ A book called 'Practical JXTA' has been published in 2008. The second edition came out this
simmer (2010).
- == 1. Scope of the subprojects ==
+ == 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 (REM: it has not been completely migrated to Kenai yet).
+ DawningStreams, Inc. is willing to give its codes examples to ASF under Apache License 2.0.
They are not part of the JXTA repository.
- The initial scope of the project will be the development of a functionally-complete Java-language
implementation of the Atom Syndication Format and Atom Publishing Protocol specifications,
along with a selection of extensions and utility functions.  It is expected, however, that
C/C++ and possibly other language implementations will be explored in the future.  
- The Atom Syndication Format implementation will include a high-performance parser and serializer
for Atom documents, a set of API's for working with the Atom data model, support for a variety
of extensions to the Atom format, and support for various advanced features such as XPath,
XML Digital Signatures, Feed paging, etc.
- The Atom Publishing Protocol implementation will include both client and server implementations
designed with the dual purpose of demonstrating the proper function of the protocol and providing
the tools necessary to build and deploy Atom Publishing-based applications.
- == 2. Initial source ==
+ == 8. Source and Intellectual Property Submission Plan ==
+ Oracle is not willing to transfer the 'JXTA' trademark. Hence, we have voted for a new name:
- The initial source for the project was originally written to address the needs of the donating
company's own internal Atom development activities.  A snapshot of the initial source is available
+ There are some potential issues with existing patents. We have sent an email to
to discuss these.
- == 2.1 External Dependencies of the project ==
+ Our Oracle representative said he is looking into moving existing code from Apache license
1.0 to 2.0.
+ == 9. External Dependencies ==
+ 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.
- The current implemenation depends on the following components:
-  * Apache Axiom 1.0
-  * StAX XML API's
-  * The Woodstox XML Parser
-  * Java Activation Framework (JAF) and JavaMail API
-  * Jaxen (optional for XPath support)
-  * Junit (for unit testing)
-  * Apache Ant (for the build)
- == 3. Identify the ASF resources to be created ==
+ == 10. Cryptography ==
+ Release 2.7 will see the implementation of an operation membership and cryptography system.

- == 3.1 mailing list(s) ==
+ == 11. Required Resources ==
+ Subversion repository
+ Issue Tracker (Jira)
+ Website location
+ Wiki
+ Mailing lists
+ Forum (new)
-  * abdera-ppmc (moderated subscriptions)
-  * abdera-dev 
-  * abdera-commits
-  * abdera-user
+ == 12. Initial Committers ==
+ Simon Temple (Amalto)
+ John Boyle (OneDrum)
+ Jérôme Verstrynge (DawningStreams)
+ Nick a.k.a. buzzlightyear (independant)
- == 3.2 Subversion repository ==
+ == 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".
-  *
- == 3.3 Bugzilla ==
-  * Abdera
- == 4. Identify the initial set of committers: ==
-  * James M Snell (IBM)
-  * Sam Ruby (IBM)
-  * Robert Yates (IBM)
-  * Yoav Shapira (Independent)
-  * Elias Torres (IBM)
- == 5. Identify Apache sponsoring individual ==
- We request that the Apache Incubator PMC sponsor the Abdera Atom implementation as an incubating
- Champion: Sam Ruby
- Mentors:
-  * Garrett Rooney
-  * Paul Querna

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message