Title: Apache Synapse

| This is the status page. Synapse has now graduated!!!! |

The Synapse project graduated on 2007-01-02

http://ws.apache.org/synapse/

  • 2005-08-22 Project announced publicly.

  • 2005-08-13 Project proposed and accepted for incubation in Apache.

  • 2005-12-12 Paul Fremantle presented on Apache Synapse at ApacheCon US 2005

  • 2006-01-23 Milestone 1 M1 released

  • 2006-05-09 Eran Chinthaka presented at JAX 2006 on Synapse

  • 2006-05-17 Glen Daniels presented at JavaOne on Synapse

  • 2006-05-25 Preparing M2 milestone release

  • 2006-06-05 M2 Milestone released

  • 2006-10-11 Presented Synapse at ApacheCon Austin

  • 2006-10-23 Created a Synapse Blog

  • 2006-12-14 Synapse 0.90 released

  • 2006-12-20 Three new committers proposed and voted on

  • 2007-01-02 Synapse passes graduation!!!!

The Synapse project is creating a robust, lightweight and highly scalable XML and Web Service mediation framework based on open standards and specifications.

To participate in the Synapse podling, you should join the mailing list. Just send an empty message to synapse-dev-subscribe@ws.apache.org .

The initial goal of the project while in incubation is to build a viable developer community and create a useful codebase. In particular, it is a stated aim of this project to re-use and integrate with other components from the Apache Web Services project such as Axis2, Axiom, Sandesha, Rampart, etc.

  • The Apache WS project will own the Synapse subproject, and the subproject will follow the Apache WS PMC's direction. All committers on this subproject will be committers on Apache WS and vice-versa.

Detailed References:

itemtypereference
Status filewwwhttp://incubator.apache.org/projects/synapse.html
Websitewwwhttp://incubator.apache.org/synapse/
Mailing listdevsynapse-dev@ws.apache.org
Mailing listuserssynapse-user@ws.apache.org
Source codeSVN/repos/asf/incubator/synapse/code/trunk/
MentorGlen DanielsGlen Daniels (CLA on file)
MentordimsDavanum Srinivas (CLA on file)
MentorsanjivaSanjiva Weerawarana (CLA on file)
Committerspzf@apache.orgPaul Fremantle (CLA on file)
Committersasankha@apache.orgAsankha Perera (CLA on file)
Committersajith@apache.orgAjith Ranabahu (CLA on file)
Committerssaminda@apache.orgSaminda Abeyruwan (CLA on file)
Committershari@infravio.comD. Hariharasudhan (CLA on file)
Committersvikas@infravio.comP. Vikas Roonwal (CLA on file)
Committersgdaniels@apache.orgGlen Daniels (CLA on file)
Committersant@apache.orgAnt Elder (CLA on file)
CommittersjaliyaJaliya Ekanayake (CLA on file)
Committersdeepal@apache.orgDeepal Jayasinghe (CLA on file)
Committerschinthaka@apache.orgChinthaka (CLA on file)
Committersruwan@apache.orgRuwan Linton (CLA on file)

Completed tasks are shown by the completion date (YYYY-MM-dd).

Project Setup

Identify the codebase

dateitem
DONEIf applicable, make sure that any associated name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product.
NAIf request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names.
DONEIf request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
N/AIf request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.

Copyright

dateitem
DONECheck and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
DONECheck and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Verify distribution rights

dateitem
DONECheck that all active committers have a signed CLA on record.
DONERemind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is is required to authorize their contributions under their individual CLA.
DONECheck and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
DONECheck and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Establish a list of active committers !

statusitem
DONECheck that all active committers have submitted a contributors agreement.
DONEAdd all active committers in the STATUS file.
DONEAsk root for the creation of committers' accounts

Collaborative Development

  • Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
    Yes

  • Are there three or more independent committers? (The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.)
    Yes, we have active committers and contributors from four companies plus two or more universities

  • Are project decisions being made in public by the committers?
    Yes

  • Are the decision-making guidelines published and agreed to by all of the committers?
    Yes

Infrastructure !

statusitem
DONEAsk infrastructure to create source repository modules and grant the committers karma.
DONEAsk infrastructure to set up and archive Mailing lists.
DONEDecide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira).
DONEMigrate the project to our infrastructure.

Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.

Licensing awareness

  • DONE - Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?

Project Goals during Incubation

Build independent development community

  • 131 subscribers to dev list

  • 48 subscribers to user list

  • Added two committers during incubation (asankha, ruwan)

Produce a release

  • (2006-01-23) M1 release - voted, tagged, signed

  • (2006-06-05) M2 release - voted, tagged, signed

  • (2006-12-14) 0.90 release - voted, tagged, signed

Exit

Things to check for before voting the project out.

Organizational acceptance of responsibility for the project

  • Has the receiving PMC voted to accept it? **Yes - thread starts here **

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks? **YES! 2007-01-02 Graduation vote passes - result here **