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 "Blaze" by CarlTrieloff
Date Thu, 27 Jul 2006 20:06:13 GMT
Dear Wiki user,

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

The following page has been changed by CarlTrieloff:
http://wiki.apache.org/incubator/Blaze

------------------------------------------------------------------------------
- = (Blaze Proposal) =
+ = Glasgow Proposal - renamed from Blaze) =
  
  == RATIONALE ==
- Blaze provides multiple language implementations of the Advanced Messaged Queuing Protocol
(AMQP) specification and related technologies including PGM, transaction management, queuing,
distribution, security, management and heterogeneous multi-platform support for messaging
(links to these specifications are in the "Initial Source" section of this proposal.) 
+ Glasgow provides multiple language implementations of the Advanced Messaged Queuing Protocol
(AMQP) specification and related technologies including PGM, transaction management, queuing,
distribution, security, management and heterogeneous multi-platform support for messaging
(links to these specifications are in the "Initial Source" section of this proposal.) 
- Blaze’s overall goal is to create an open and interoperable implementation for messaging
which implements the emerging AMQP specification, in keeping with the philosophy of the Foundation.
This implementation will provide a messaging solution that will be language and platform agnostic
by using a well defined wire specification. Providing both libraries for the framing and protocol
in addition to brokers in both Java and C/C++ allows for integration with Apache and non-Apache
projects in a manner that facilitates heterogeneous deployment with full interoperability
for SOA & distributed systems.
+ Glasgow’s overall goal is to create an open and interoperable implementation for messaging
which implements the emerging AMQP specification, in keeping with the philosophy of the Foundation.
This implementation will provide a messaging solution that will be language and platform agnostic
by using a well defined wire specification. Providing both libraries for the framing and protocol
in addition to brokers in both Java and C/C++ allows for integration with Apache and non-Apache
projects in a manner that facilitates heterogeneous deployment with full interoperability
for SOA & distributed systems.
  The seed code for the project will consist of in-progress C/C++ and Java implementations
of the AMQP specification that we intend to continue development on in conjunction with other
Apache communities. More information on the scope of the seed code can be found in subsequent
sections of this proposal. 
  
  == CRITERIA ==
  === Meritocracy: ===
- The Blaze committers recognize the desirability and necessity of running this project as
a full meritocracy; indeed, the scope of the project's technical aspects are so varied that
we find it hard to envision success any other way. One of the most important lessons that
can be derived from the historic evolution of middleware is that specifications architected
in isolation from real usable code that has been developed to solve tangible, real world problems
or amongst a narrowly restricted list of contributors often do not see widespread adoption.
Our goal in crafting this implementation and providing our learning to the specification team
is to develop the best possible language agnostic advanced message queuing platform.  We understand
that in order to do so, we will need to engage all interested  members of the community and
operate to the standard of meritocracy that characterizes successful Apache projects. 
+ The Glasgow committers recognize the desirability and necessity of running this project
as a full meritocracy; indeed, the scope of the project's technical aspects are so varied
that we find it hard to envision success any other way. One of the most important lessons
that can be derived from the historic evolution of middleware is that specifications architected
in isolation from real usable code that has been developed to solve tangible, real world problems
or amongst a narrowly restricted list of contributors often do not see widespread adoption.
Our goal in crafting this implementation and providing our learning to the specification team
is to develop the best possible language agnostic advanced message queuing platform.  We understand
that in order to do so, we will need to engage all interested  members of the community and
operate to the standard of meritocracy that characterizes successful Apache projects. 
  
  === Community: ===
- The project’s primary objective is to build a vibrant community of users and active contributors.
 Although Blaze is not based on an existing open source community, many of the initial contributors
have experience participating in and building other open source communities.  Several of the
contributors have previously participated in Apache communities. We understand that Apache’s
community governance protocols are a unique contributor to the success of Apache’s project
communities and we are eager to learn from our Incubator mentors so that we can evolve Blaze
into a healthy and sustainable community.  
+ The project’s primary objective is to build a vibrant community of users and active contributors.
 Although Glasgow is not based on an existing open source community, many of the initial contributors
have experience participating in and building other open source communities.  Several of the
contributors have previously participated in Apache communities. We understand that Apache’s
community governance protocols are a unique contributor to the success of Apache’s project
communities and we are eager to learn from our Incubator mentors so that we can evolve Glasgow
into a healthy and sustainable community.  
  === Core Developers: ===
  Most of the initial committers are members of Red Hat, IONA, and JP Morgan Chase’s (JPMC)
development teams. Additional developers will be added through the Apache community process.

  === Alignment: ===
  An initial implementation has been written in Java and C++, which will be refactored into
this project to form the initial code base.  We have had a few exploratory conversations about
integration with individuals of other communties such as Apache Geronimo, Tuscany,  ActiveMQ,
Fedora and ObjectWeb's Celtix and hope to work towards future collaboration with these communities.
Our current implementation makes extensive use of projects from the Apache Jakata Commons,
Mina and other Apache infrastructure projects. A compatibility binding for JMS also exists.
It is however important to note that this is NOT a JMS project and aims to solve a different
problem space, providing language and platform independent and interoperable messaging, driven
by a protocol specification which may ultimately be commoditized in hardware.
  
  The scope of the project is broader than just Java and C++ as the project will also look
at providing bindings in other languages such as PHP and Python.Additionally, bindings have
already been created for test automation.
- As Blaze’s broad goal is to create a standardized, widely available, and  interoperable
messaging solution based on the AMQP protocol, there are numerous potential collaboration
opportunities with many other Apache projects including: 
+ As Glasgow’s broad goal is to create a standardized, widely available, and  interoperable
messaging solution based on the AMQP protocol, there are numerous potential collaboration
opportunities with many other Apache projects including: 
   * Transport support for Geronimo 
   * Interoperability integration with ActiveMQ(JMS)
   * Integration with Axis for SOAP messaging over an asynchronous transport  
@@ -41, +41 @@

  
  == SCOPE OF SUBPROJECTS ==
  The initial contributors envision an active community of related projects sharing a common
of commodity and interoperable middleware but targeting specific technical areas: 
- Blaze will be seeded with several projects based on donated material (see the next section):

+ Glasgow will be seeded with several projects based on donated material (see the next section):

   * a Java implementation of the wire level framing
   * a C++ implementation of the wire level framing
   * a Java implementation of a broker
@@ -57, +57 @@

   * support for broadcast and relay from PGM <--> AMQP
   * integration with payload marshilling toolkits
   * Declarative policy based API's
- These initial projects are intended merely as starting points and should not be taken as
bounding the scope of the Blaze project as a whole. Some other potential projects may include:

+ These initial projects are intended merely as starting points and should not be taken as
bounding the scope of the Glasgow project as a whole. Some other potential projects may include:

   * Integration with rich middleware frameworks (such as Celtix or ServiceMix). 
   * Support and integration of Security. 
   * Management tools. 
@@ -75, +75 @@

  The initial contributors have been developing Java and C++ code bases (licensed under the
Apache License 2.0) which implement aspects of these specifications, and intend to donate
it to Apache. The current working svn is available at:
  https://etp.108.redhat.com/source/browse/etp/trunk/blaze
  
- Although the Blaze project expects to bootstrap using these materials and in the case of
specifications, to provide feedback that will be incorporated into their ongoing development,
we expect and encourage the open source community to take the project in new directions not
envisioned by them to create a world class implementation of the AMQP specification and related
technologies. 
+ Although the Glasgow project expects to bootstrap using these materials and in the case
of specifications, to provide feedback that will be incorporated into their ongoing development,
we expect and encourage the open source community to take the project in new directions not
envisioned by them to create a world class implementation of the AMQP specification and related
technologies. 
  
  == Interactions with the specifications ==
  The specification is being developed by group of companies, under a contract that requires
the resulting work to be published to a standards body. This model has been chosen to assure
that anyone that contributes to the specification grants a copyright and patient license to
all contributions made to the specification on every publication (draft or final). This ensures
that the specification will always be open and implementable by anyone without royalties or
commercial limitations. We feel that this is a very strong model for keeping this work entirely
open and will fit well with the Apache project enabling innovations to pass in both directions
across the extended community.
  
- Dealing with feedback from the Blaze project to specifications
+ Dealing with feedback from the Glasgow project to specifications
- It is key that the best implementation and specifications be created based on technical
merit and practicalities for adoption by both the parties developing the specification and
the committers within the Apache community. Given this, one of the important aspects is how
issues discovered during the development of this implementation are incorporated back into
the specifications.  The following feedback loop exists to ensure that any specification input
incuding the Blaze community can have their feedback incorporated into the specifications.
+ It is key that the best implementation and specifications be created based on technical
merit and practicalities for adoption by both the parties developing the specification and
the committers within the Apache community. Given this, one of the important aspects is how
issues discovered during the development of this implementation are incorporated back into
the specifications.  The following feedback loop exists to ensure that any specification input
incuding the Glasgow community can have their feedback incorporated into the specifications.
  === MECHANISMS FOR FEEDBACK ===
  a.) In the same way anyone can issue a JIRA on any Apache project having signed the Apache
CLA, anyone can issue a “JIRA” to the specification working group through the RLA (Reviewer
License Agreement). This agreement provides a license to that IP so that the specification
team can incorporate it and the specifaction as they like and the specifications can remain
entirely open and royalty free.
  b.) In the same spirit of Apache, if an individual has shown understanding of the project
and substantive contribution to the specification, a vote based on technical merit and understanding
of the goals of the work can be initiated to have that parties Employer join the specification
working group. On such acceptance the employer is required to sign an agreement to make sure
that employer also grants the ongoing and consistent licenses to the work as posted in specifications.
@@ -90, +90 @@

  
  == ASF resources to be created ==
  mailing list(s)
-  * blaze-dev
+  * glasgow-dev
-  * blaze-commits
+  * glasgow-commits
  Subversion repository
-  * https://svn.apache.org/repos/asf/incubator/blaze 
+  * https://svn.apache.org/repos/asf/incubator/glasgow 
  Jira
-  * Blaze (BLAZE) 
+  * Glasgow (GLASGOW) 
  
  === INITIAL COMMITTERS ===
   * Mark Atwell (JPMC)
@@ -118, +118 @@

   * Gordon Sim (Red Hat)
   * James Strachan (LogicBlaze)
   * Manik Surtani (Red Hat)
+  * Paul Taylor (IONA)
   * Carl Trieloff (Red Hat)
   * Kim van der Riet (Red Hat)
   * Sergey Yedrikov (IONA)
   * Chamikara Jayalath (WSO2)
  
  === APACHE SPONSOR ===
- The Blaze team will make the submission to the incubator as the sponsor for incubation.
+ The Glasgow team will make the submission to the incubator as the sponsor for incubation.
+ 
  Champion
   * Cliff Schmidt (consultant to Red Hat)
  Mentors:

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


Mime
View raw message