incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject RaveProposal reverted to revision 6 on Incubator Wiki
Date Mon, 18 Apr 2011 20:34:30 GMT
Dear wiki user,

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

The page RaveProposal has been reverted to revision 6 by RossGardler.
The comment on this change is: Oooops - pasted into the wrong page, revert to correct content.


- = Airavata Proposal for Apache Incubator =
+ = Apache Rave Proposal =
+ == Status ==
+ The Rave Proposal has been [[|accepted]]
+ See you soon at (Rave site not created yet)
  == Abstract ==
+ Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an out-of-the-box as
well as an extendible lightweight Java platform to host, serve and aggregate (Open)Social
Gadgets and services through a highly customizable and Web 2.0 friendly front-end.
+ Rave is targeted as engine for internet and intranet portals and as building block to provide
context-aware personalization and collaboration features for multi-site/multi-channel (mobile)
oriented and content driven websites and (social) network oriented services and platforms.
+ For the [[|OpenSocial]] container and services the (Java) [[|Apache
Shindig]] will be integrated. At a later stage further generalization is envisioned to also
transparently support [[|W3C Widgets]] using [[|Apache
- Airavata is a software toolkit currently used to build science
- gateways but that has a much wider potential use. It provides features
- to compose, manage, execute, and monitor large scale applications and
- workflows on computational resources ranging from local clusters to
- national grids and computing clouds. Users can use Airavata back end
- services and build gadgets to deploy in open social containers such as
- Apache Rave and modify them to suite their needs. Airavata builds on
- general concepts of service oriented computing, distributed messaging,
- and workflow composition and orchestration.
  == Proposal ==
+ The reason for starting Rave is to bring together and combine several existing projects
and teams currently working towards more or less the same or overlapping goals but each in
their own small(er) target audience and community.
- Airavata will provide web interfaces and scalable Service Oriented
- Architecture based backend services to build or enhance Science
- Gateway (see 
- and similar environments. Airavata will specifically focus on:
-   1. sophisticated server-side tools for registering and managing large scale applications
on computational resources.
-   2. graphical user interfaces to construct, execute, control, manage and reuse of scientific
-   3. interfacing and interoperability with with various external (third party) data and
provenance management tools.
+ The goal for Rave is to become a lightweight and open-standards based extendible platform
for using, integrating and hosting !OpenSocial and W3C Widget related features, technologies
and services.
+ It will also provide strong context-aware personalization, collaboration and content integration
capabilities and a high quality out-of-the-box installation as well as be easy to integrate
in other platforms and solutions.
+ The initial features for Rave will at least be based on the current capabilities from the
contributing external projects, for which they will provide the necessary code contributions.
+ However, the code base for Rave will be built anew with strong focus on generalization,
customization and extendibility to support the intended multi-purpose adoption and integration.
+ The contributing external projects will start using and switch to the new Rave based solution
as soon as the initial features become available to ensure the continued participation and
interest from their side as well as their own communities.
+ ==== The intended initial features include: ====
+ '''Core Features'''
+  1. Advanced !OpenSocial compliance and optional features support
+  1. !OpenSocial persistence and SPI (Service Provider Interface) implementation
+  1. Self-service application administration including security, gadget management and page
+  1. User and group management with full privacy model
+  1. Gadget repository with life-cycle management (install/update/remove) and extended meta
data (categories, comments, ratings, etc.)
+  1. Dynamic and highly customizable front-end engine (skins, pages, tabs, layouts, navigation)
+  1. Full OAuth support
+  1. Support for security restrictions on both Gadgets and page/tag/layout customizations
+  1. Set of common and general purpose Gadgets to be usable out-of-the-box
+  1. Support for inter-gadget messaging with examples
+ '''Extensible Features'''
+  1. Pluggable persistence
+  1. Pluggable security model with example modules for authentication and authorization
+  1. Support for !OpenSocial extensions not (yet) defined in the specification
+  1. Support for other (non-standard, yet) pluggable container services and extensions
+ Beyond these initial features the vision and scope for Rave goes much further and includes
integrating and providing other highly desired/needed features like:
+  * native W3C Widgets support through [[|Apache Wookie]]
+  * pluggable and extendible content integration and management services
+  * space extensions and management features, like
+  * context aware features and extensions integration for personalized and social network
and (mobile) device oriented sites and channels
+  * enhanced client-side widget messaging, coordination and co-location support like using
[[|OpenAjax]] Hub and Registry
+  * space, page and Gadget based linking, navigation, coordination and collaboration
+  * inline widget rendering, like
+  * [[|Activity Streams]] support
+  * integration with other social networks like with [[|W3C
Federated Social Web Incubator Group]], [[|OneSocialWeb]] and [[|OStatus]]
+  * integration with [[|Apache Wave]]
+  * runtime services monitoring, reporting and configuration/life-cycle management support
  == Background ==
- Working in close quarters with Apache Axis2 committers and inspired by
- the true open source community driven software development of ASF,
- Suresh Marru and Marlon Pierce have been pioneering the idea of a
- Science Gateways software-based Apache project since late 2008. Many
- Apache members have fostered these ideas and guided them to arrive at
- this proposal.
+ The plan for starting a project like Apache Rave was initially proposed at an [[|ApacheCON
meetup]] November 2010 in Atlanta and [[
|in more detail]] at the first [[|European
OpenSocial Event]] December 2010 in Utrecht (The Netherlands).
+ This resulted in participants from [[|Pervasive Technology Institute
Indiana University]], [[|The MITRE Corporation]], [[|SURFnet
SURFConext]], [[|OSS Watch]], [[|Hippo]]
and other individuals to come together and discuss the possibilities to collaborate and work
together on this joined effort, resulting in this proposal for the Apache Rave project.
- Currently the software is a actively used in various science
- gateways. But the tools are general purpose and build upon widely used
- Apache tools like Axis2, ODE engine. The core team is motivated to
- expand the community and build a community welcoming both synergistic
- software components and also new usage scenarios.
- It is perhaps worth noting that one of the three seed projects that
- make up the Apache Rave (Incubating) project is also the product of
- this same team and is derived from the same Science Gateways
- community.
  == Rationale ==
+ The reason for the Apache Rave proposal is that there is a clear need for a more lightweight
collaborative and social network oriented integration and services platform, portal if you
like, which is easier to use, extend and manage than the more heavy weight J2EE / Portal /
Portlet standards based solutions.
+ The !OpenSocial, WC3 Widgets and similar related standards are much more "network" and collaboration
oriented and lighter weight in their definition, implementation and integration requirements,
and are moving much more rapidly and agile forward.
+ Several open-source projects already have stepped into this arena, converting over or starting
from scratch, to create new and lightweight solutions based on these emerging standards.
- The nature of computational problems has evolved from simple desktop
- calculations to complex, multidisciplinary activities that require the
- monitoring and analysis of remote data streams, database and web
- search and large ensembles of simulations. In the academic domain
- Science Gateways have emerged to address these needs and have built
- software platforms that provide a community of users with the ability
- to easily solve computational problems within a specific domain. The
- tools developed to support these gateways are potentially of value to
- any organisation needing to perform complex computations. Gateways
- provide a convenient interface to the underlying infrastrucure without
- the need for a deep understanding of the intricacies that
- infrastructure.
- We summarize the rationale for choosing The Apache Software Foundation
- (ASF) below. This is what we hope to gain from participating in the
- ASF.
+ In most cases these new implementations are still at the early stages, and much of the basic
work is duplicated as is the effort to build up communities and attract developers.
+ The Apache Rave contributing projects are all building on the same concepts (!OpenSocial),
have the same or very similar functional needs with regards to Gadget handling, service handling,
back-end integration, front-end rendering, code maintenance, etc.
+ The rationale for Apache Rave is to combine these efforts and work and collaborate together
on a common base solution and to get out of each own "silo".
+ This joined effort than can benefit everyone, both on technical implementation and feature
realization and provide a much wider and stronger community perspective.
-   1. '''Broader impact''': our science gateway tool set is based on Service Oriented Architecture
principles, and it has always been our goal to align our software with broader trends in the
development of software for distributed systems.  Participating in the ASF provides a concrete
way to implement this idea.  In particular, we have done extensive work on the workflow systems,
messaging, and application management as Web services from the perspective of computational
science use cases (i.e., high failure rates, very long running jobs, dynamic service creation,
workflows not expressible as directed acyclic graphs, etc). These requirements and our work
to implement them have already had direct impact on the Apache Axis 2 and Apache ODE projects.
As an Apache project, it is hoped that our community will have an enhanced opportunity for
collaboration and complementary development with Apache Hadoop (for scientific application
management), Apache QPID (for messaging), Apache Rave (incubator - Open Social Container)
and others.  It is our goal to expand our software’s usage beyond just science gateways
to the broader enterprise community.
-   2. '''Sustainability''': Science gateway software development (and cyberinfrastructure
software generally) is primarily funded in the US by the National Science Foundation (NSF),
so the long term sustainability of software across funding cycles is a longstanding problem.
 The NSF is attempting to solve this problem, and its vision for sustainable software is described
 here: Participating in the ASF is our
project’s vision for reaching software sustainability that underpins the NSF CF21 vision.
 As a successful ASF project (after incubation), we will have created a community led, rather
than funding led, environment for the development of our sotware. This community, through
our community engagement work and adoption of meritocratic principles, will expand beyond
our current core team and existing project collaborations.  This will greatly increase the
chances that our software will continue to grow and improve beyond the participation of any
-   3. '''Maturity''': much of the software included in this proposal was developed initially
by graduate students as part of their Ph. D. work.  The Open Grid Computing Environment has
devoted significant effort (through salaried staff and volunteers from collaborating institutions)
to convert these research projects into mature, reliable, well-written, packaged components.
 The code is currently hosted at SourceForge, but we recognize the need to go beyond just
the SourceForge support tools to participate in a real community of software engineering experts.
It is our desire, through the Apache Incubator, to take our software engineering efforts to
a higher level by learning from the substantial experience of appropraite Apache Committers.
Apache mentors will provide initial guidance, as will  the attraction of additional committers
from the relevant Apache projects.
+ The initiating projects and individuals on this joined effort have their existing code based
licensed under the ASL 2.0, or will do so as part of this project. Participants include long
time users, committers and members of the Apache Software Foundation. That, and the strong
alignment with existing Apache projects like Shindig and Wookie, and the strong belief in
the Apache "way" with focus on collaboration and community, makes starting the Rave project
at Apache the logical thing to do.
+ The external projects providing the initial code contributions all fully support the goal
to come up with a '''new''' base solution to replace their own project base line solution.
+ Apache Rave will not be started from one of these initial code contributions directly, but
be build from scratch where selected features and implementations might be cherry picked from
the code contributions where applicable.
+ Each of the code contribution projects are willing to give up their current implementation
and replace that with the new solution from Apache Rave, even if no part of their existing
implementation details would "survive".
+ == Current Status ==
+ === Community ===
+ This project will form a new community, made up initially of the contributors  listed below.
However, from our experience at the !ApacheCon, we believe that  this project will quickly
draw interest and its community will broaden easily.  The proposers have worked well together
so far, in producing this  proposal and clarifying design approaches, and are keen to continue
this  in a more open venue.
+ === Code ===
+ Three initial codebases that implement parts of the scope of this project have been offered
to this project. All are, or will be, Apache licensed, and grants can be provided. All three
of these codebases will be imported into Apache SVN, each into separate sandboxes.
+ A followup codebase donation is planned, providing a context aware mapping engine and content
integration features, under the same conditions as for the initial codebases.
  == Initial Goals ==
+ The initial goal will be to produce a single usable codebase from the three imported codebases,
and to get this to a suitable state where contributing parties can use it within their own
-   * Implement a standalone version of the code base with a simple hello world service, workflow
and gadget(s) to access the examples.
-   * Migration of documentation and design knowledge from existing SF project
-   * Re-architect Grid based security (GSI) dependencies and adopt more general purpose security
-   * Make sure Cloud (including hadoop) support is more first class. 
-   * Aim to have the first Apache release within the first 6 months
-   * Verify with Apache Legal that some of the more esoteric licences in our dependencies
are acceptable, or replace them as appropriate
- == Current Status ==
+ This will be done by starting with a fresh, clean repository and then, on a feature-by-feature
basis, cherry-picking the best code for that feature from the three codebases.
- The proposed tools are currently hosted on SourceForge at
- (source at
- and are
- described at
- == Meritocracy ==
- A significant portion of initial committers are already ASF Committers/Members,
- and the entire team is well experienced with open source software
- development. The existing code base has resulted from
- multi-institutional collaborative projects. The developers are well
- aware of the Apache way and will honor the meritocracy policy of ASF
- foundation.  
- == Community ==
- To date our focus has been serving our immediate partners needs rather
- than looking outwards in order to build a broader community with
- diverse needs. Whilst the core team area likely to remain focussed on
- the Science Gateways communities we are keen to welcome community
- members from other disciplines.
- == Core Developers ==
- Our core developers consist of participants from academic,
- not-for-profit and for-profit organisations. Many are already well
- versed in The Apache Way.
- Amongst our initial team we have one or more committers on the
- following Apache top level projects; axis, geronimo, synapse, ws,
- ws-pmc, ws-woden as well as Apache Rave (Incubating).
- == Alignment
- Airavata software is built upon Apache Projects like Axis2, ODE,
- Rampart, Tomcat and Maven. We will try to closely align the project
- with ODE to ensure BPEL workflow compatibility. We will align with
- metadata management projects like Apache OODT. Web interfaces within
- the Airavata software will be synergistically developed with Apache
- Rave.
  == Known Risks ==
- === Orphaned products ===
- We acknowledge the need to seek project contributions outside the current
- developers. The core team actively travels and conducts workshops and
- tutorials at relevant academic conferences like Supercomputing, TeraGrid,
- Collaborative Technologies Systems and SciDAC. Previous experiences
- have showed that these tutorials and outreach efforts will bring in
- community participation. The general strategy will be to encourage
- users to be active in the community and develop patches and
- contribute. Also, the core developers use the Airavata software in
- multiple projects with a life span ranging from 2 to 10 years, so the
- risk of orphaned products is very minimal.
+ Any project joining the Incubator is going to have risks - aspects to it that could lead
the project to fail. In this section, the risks that have been noted for the Rave project
are discussed.
- Furthermore, by opening our doors to non-academic organisations
- already adopting large scale computation related projects in the ASF
- we hope to be able to build community beyond the proposing teams
- Science Gateway interests.
- === Inexperience with Open Source ===
- The core team is very familiar with open source practices. The
- developers include existing Apache members who have long term experience with
- the Apache Way. The OGCE project has been an active
- open source project in SourceForge since November 2006. We welcome the
- new directions and are well prepared to follow the Apache way.
- === Homogenous Developers ===
- We have a semi-distributed development environment distributed among
- Indiana University and Lanka Software Foundation. We fully expect
- contributions from the partnering science gateways adding to the
- heterogeneous development.
+ === Three Code Bases ===
+ Working with three initial code bases will be a challenge. However, we are hoping that it
will be less of a challenge than starting with none!
+ All parties contributing code have agreed that they are prepared to participate in this
project even if none of their contributed code is incorporated in the final product, recognising
that for each feature, it will be necessary to pick the best code for the job, rather than
the code that one participant is most attached to.
+ === Speed of Development ===
+ Initially at least, this project is dependent upon contributions made on company time. For
this approach to succeed, the project must deliver a workable system in a timeframe acceptable
to those companies. The initial parties have the intention of releasing a first version within
6 months after starting the Incubator. Failure to do so could prevent the project reaching
critical mass, and could prevent the project from being in a position to attract new developers.
+ === Inexperience with Community Development ===
+ None of the participants have worked together before this project was conceived. Some participants
have released open source code, but not done development 'in the open'.
+ There will clearly be some learning in how to participate together in this project, in a
meritocratic way, as a newly formed community. However, we do have in our mix folks that are
experienced in open source development, including existing Apache committers and Apache members,
as a consequence of which we believe we have enough experience to work with the challenges
of forming a new community.
  === Reliance on Salaried Developers ===
- The core developers are self motivated on the project and also are
- funded through various federal, state and endowment research
- grants. Participation in these research efforts based on Airavata
- software is mostly voluntary and above and beyond the requirements of
- the salaried jobs.
+ At present, the vast majority of contributors will be doing so as a part of their day jobs.
Therefore, as already alluded to, there is a risk that the project won't gain enough traction
to be of use to their employers. However, given the centrality of these codebases to the participating
companies, it is clearly in their best interests to transition to an openly developed alternative.
- The Open Gateway Computing project, from which the initial code
- donation is sourced, is funded for the next 3 years and is mandated by
- the funding guidelines to open source software development -
- We
- believe in the Airavata software capabilities and its vital role in
- providing sustainable middleware for Science Gateways. Nevertheless,
- the core team will actively build upon Airavata software and foster
- developer community outside the current core.
- === Relationships with Other Apache Products ===
- See “Alignment” above.  Airavata is based on the concepts of Service
- Oriented Architecture and all services run within Tomcat
- container. The web services are based on Axis2. The orchestration of
- the scientific workflows uses Orchestration Director Engine. The
- software is built using Apache Maven.
- === An Excessive Fascination with the Apache Brand ===
- The Apache brand would certainly help promote the software suite, but
- gaining the brand is not the motivation for this project. Airavata is
- being proposed to Apache because of the belief in Apache’s meritocracy
- model for mentored, community-driven, open source software is the best
- way to develop sustainable software. See “Rational” above. Most
- importantly, The Apache Software Foundation will help us create an
- institution-neutral contribution venue and will help us build a
- long-standing community around Airavata to sustain and improve it
- beyond the span of specific, targeted research grants.
+ === Other Risks ===
+ Of the other risks commonly raised regarding incubator proposals, none seem particularly
pertinent to this project.
+ The project is no less likely to be orphaned than any other new podling. Given the multi-company
support it has easily gained, it would seem to be quite the opposite.
+ Given the range of organisations putting themselves behind this proposal, there is no obvious
risk of over-dependence on one contributing organisation.
+ The participants are attracted to Apache due to its governance model, and proximity to similar
projects, e.g. Apache Shindig. This affinity is clearly shown by the fact that the original
group who formed this proposal met at !ApacheCon.
  == Documentation ==
- Existing documentation is available from the OGCE wiki,
- In addition,
- there is abundance of presentation and self guided video tutorial
- material. Effort will be put in to collect all this information into
- meaningful documentation on the Apache websites.
+ Details for the initial contributed code can be seen here:
+  * MITRE: [[|OpenSocial Enterprise Container]]
+  * SURFnet: [[|SURFConext Portal]]; [[|SURFconext
technical design]]
+  * [[|OGCE]] [[|OGCE
Gadget Container]]
+ Because this project will create new code, we will not have any documentation on first starting.
It is likely however that partial documentation can be reused from either codebases.
  == Initial Source ==
- The initial source of the project is in SourceForge. The source is
- available for anonymous check out from svn at
+ The initial source will be made up of three contributions, namely:
+  * [[|MITRE OpenSocial Enterprise Container - Source]]
+  * SURFnet SURFconext Portal - This source will be brought into the Incubator as SURFnets
+  * OGCE: Gadget Container code is part of the [[|OGCE
SourceForge Site]]. See [[|the portal
download page]] for SVN instructions.
  == Source and Intellectual Property Submission Plan ==
- Indiana University is the current holder of Intellectual Property
- rights for the software. The university has approved the code donation
- and signed trustees approval, Corporate Contributor Licence Agreement
- and Software Grant Agreement have been emailed to ASF secretary and
- received acknowledgement.
- Specifically Indiana University will donate 4 components into Airavata project. 
+ ==== Hippo ====
-   1. XBaya Scientific Workflow Suite - includes a GUI for workflow composition and monitoring.
The composed workflow can be exported to various workflow languages like BPEL, SCUFL, Condor
DAG, Jython and Java. The defacto workflow enacting engine used is Apache ODE. 
-   2. GFac - an application wrapper service that can be used to wrap command line-driven
science applications and make them into robust, network- accessible services. This component
is build on Axis2 web service stack. 
-   3. XRegistry - a registry service for storing deployment information about wrapped application
services and constructed workflows.
-   4. WS-Messenger - a “publish-subscribe” based message broker implemented on
top of Apache Axis2 web services stack. It implements the WS-Eventing and WS-Notifications
specifications and incorporates a message box component that facilities communications with
clients behind firewalls and overcomes network glitches.  
- == External Dependencies ==
+ The code to be offered by Hippo is already open source and Apache Licensed.
- Following the guideline -, the following are the
dependent software and all of them are in binary format in java archive (jar files).
+ ==== The MITRE Corporation ====
-    * CDDL license  - Javax activation, JSR311, Portlet-API, Servlet-API
-    * Apache V2: cog-jglobus, globus, caster, gridsphere, Woodstox, xmpp, xsul, sigiri, atomixmiser,
-    * BSD: puretls, 
-    * MIT: bcporv, hsqldb, dom4j, slf4j 
-    * PSFL: Jython
-    * GPL 2.0: mysql-connector-java
-    * Other: 
-      * cryptix32, cryptix-asn1 (
-      * backport (public domain)
-      * jaxen (
- Licence incompatibilities (GPL) will be resolved during incubation.
+ The code offered by The MITRE Corporation is already open source and Apache Licensed.
+ ==== SURFnet SURFConext Portal ====
+ This source will be brought into the Incubator as SURFnets contribution; initial project
members have already been given access for evaluation purposes.
+ ==== Open Gateway Computing Environments ====
+ The OGCE will contribute its Gadget Container code, which is Apache licensed and available
from !SourceForge, with current dependencies and their licenses described below.
+ Other OGCE software efforts are not covered by this incubator proposal and are not included
in the code contribution.
+ == Dependencies on other Apache Projects ==
+  * Apache Shindig
+  * Apache Tomcat
+  * Apache Tiles
+  * Apache !HttpComponents
+  * Apache Commons
+  * Apache Log4J
+  * Apache Maven
+  * Apache Ant
  == Cryptography ==
+ There is no cryptography in the code at this time.
+ OGCE has requirements to support security for Computational Grids and Clouds. Although the
code will not have any cryptographic implementations, in the future there will be dependencies
on external cryptographic libraries. Before committing any cryptographic dependencies, the
process listed at will be followed.
- The software does not implement any cryptographic algorithms. However,
- to perform secured messaging and data movement and SSL communications,
- the software depends upon third party security libraries. These
- external libraries depend in turn on Java Security, Puretls, Cryptix
- and Bounce Castle libraries. Apache Cryptographic steps will be
- followed to register the use of these libraries.
  == Required Resources ==
  === Mailing lists ===
-   1. airavata-dev
-   2. airavata-commits
-   3. airavata-private
+  * rave-dev
+  * rave-commits
+  * rave-private (moderated subscriptions)
  === Subversion Directory ===
+  *
  === Issue Tracking ===
- We intend to make use of Jira for issue tracking. Proposed key: AIRAVATA
+ We intend to make use of Jira for issue tracking.
+ Proposed JIRA key: JIRA-RAVE
  === Other Resources ===
- We intend to manage our website using the Apache CMS.
+ None right now.
  == Initial Committers ==
  Names of initial committers with affiliation and current ASF status:
+  * Ate Douma (Hippo), Apache Member, id: ate
+  * Unico Hommes (Hippo), Apache Committer, id: unico
+  * Ard Schrijvers (Hippo), Apache Committer, id: ard
+  * Woonsan Ko (Hippo), Apache Committer, id: woonsan
+  * Matt Franklin (MITRE, osec)
+  * Jesse Ciancetta (MITRE, osec)
+  * Tony Carlucci (MITRE, osec)
+  * Ross Gardler (OSS Watch), Apache Member, id: rgardler
+  * Sander van der Waal (OSS Watch)
+  * Scott Wilson (University of Bolton), Apache Committer, id: scottbw
+  * Hadrian Zbarcea (independent), Apache Member, id: hadrian
+  * Marlon Pierce (Pervasive Technology Institute Indiana University, OGCE)
+  * Raminderjeet Singh (Pervasive Technology Institute Indiana University, OGCE)
+  * Zhenhua Guo (Pervasive Technology Institute Indiana University, OGCE)
+  * Suresh Marru&nbsp;(Pervasive Technology Institute Indiana University, OGCE)
+  * Niels van Dijk (SURFNET, SURFConext)
+  * Maarten Kremers (SURFNET, SURFConext)
+  * Bas Zoetekouw (SURFNET, SURFConext)
+  * Joost van Dijk (SURFNET, SURFConext)
+  * Okke Harsta (Zilverline, SURFConext)
- || '''Name'''           || '''Email'''            || '''Affiliation'''         || '''ICLA'''
|| '''ASF Status''' || '''Apache Id''' ||
- || Suresh Marru         ||  || Indiana University        || On File
|| Apache Commiter || smarru    ||
- || Marlon Pierce        || || Indiana University        || On File
|| Apache Commiter || mpierce   ||
- || Srinath Perera       ||    || Lanka Software Foundation || On File
|| Apache Member   || hemapani  ||
- || Aleksander Slominski || aslom at    || IBM                       || On File
|| Apache Member   || aslom     ||
- || Raminderjeet Singh   ||    || Indiana University        || On File
|| Apache Commiter || raminder  ||
- || Archit Kulshrestha   ||   || Indiana University        || On File
|| N/A             || N/A       ||
- || Chathura Herath      ||    || Indiana University        || On File
|| Apache Commiter || chathura  ||
- || Eran Chinthaka       ||   || Indiana University        || On File
|| Apache Member   || chinthaka ||
- || Thilina Gunaratne    ||     || Indiana University        || On File
|| Apache Commiter || thilina   ||
- || Wathsala Vithanage   || || Lanka Software Foundation || On File
|| N/A             || N/A       ||
+ == Sponsors ==
- All the parties are affiliated with companies and organizations that
- are familiar with the development of open source. We expect that the
- amount of volunteer work will increase, and more developers will come
- on board.
- == Champion ==
+ === Champion ===
- Ross Gardler, Apache Software Foundation
+  * Ate Douma
- == Nominated Mentors ==
+ === Nominated Mentors ===
-   * Ross Gardler, Member, Apache Software Foundation
-   * Alek Slominski, Member, Apache Software Foundation
-   * Ate Douma, Member, Apache Software Foundation
-   * Sanjiva Weerawarna, Member, Apache Software Foundation
-   * Paul Fremantle, Member, Apache Software Foundation
+  * Ate Douma
+  * Sylvain Wallez
+  * Upayavira
+  * Ross Gardler
+  * Hadrian Zbarcea
- == Sponsoring Entity ==
+ === Sponsoring Entity ===
- Apache Incubator Project.
+  * Apache Incubator Project
+ == Appendix A: External Dependencies ==
+ Here's the list of identified external dependencies for each of the initial code contributions:
+ ==== MITRE OpenSocial Enterprise Container ====
+  * ''Build Time/Test Dependencies''
+  '''Apache Licensed'''
+   * Jakarta ORO
+   * Apache log4j
+   * cglib
+   * !EasyMock
+   * Google Guice
+   * h2datasource (MITRE Developed)
+   * Objenesis
+   * Spring Framework Test
+   * servlet-api
+  '''BSD Licensed'''
+   * YUI Compressor
+   * YUI Compressor Ant Task
+   * JUnit
+  '''MPL && EPL Licensed'''
+   * H2 Database Engine
+  '''Other Licenses'''
+   * ASM:
+   * Cobertura:
+  * ''Runtime Dependencies''
+  '''Apache Licensed'''
+   * Apache Commons
+   * Apache Taglibs
+   * Google Collections
+   * Jackson
+   * Apache log4j
+   * Shindig
+   * Spring Framework
+   * Spring Security
+   * Apache Tiles
+   * Google Guice
+   * h2datasource (MITRE Developed)
+  '''MPL && EPL Licensed'''
+   * H2 Database Engine
+  '''EPL Licensed'''
+   * !EclipseLink
+   * javax.persistence API
+   * AspectJ
+  '''BSD-style Licensed'''
+   * !FreeMarker:
+  '''CDDL Licensed'''
+   * JSTL
+   * !JavaMail
+  '''MIT Licensed'''
+   * SLF4J
+  '''Other Licenses'''
+   * AOP Alliance:
+ ==== SURFnet SURFConext portal ====
+ ''Dependencies and licenses of all dependencies of the COIN portal (excluded the shindig
+  '''Apache Software License, Version 1.1'''
+   * cglib:cglib-nodep:jar:2.2:compile
+  '''Apache Software License, Version 2.0'''
+   * org.codehaus.jackson:jackson-mapper-lgpl:jar:1.5.5:compile
+   * org.springframework:spring-core:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-orm:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-jdbc:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-context:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
+   * commons-dbcp:commons-dbcp:jar:1.2.2:compile
+   * commons-pool:commons-pool:jar:1.3:compile
+   * commons-codec:commons-codec:jar:1.4:compile
+   * org.springframework:spring-webmvc:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-context-support:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
+   * org.springframework:spring-web:jar:3.0.3.RELEASE:compile
+   * commons-collections:commons-collections:jar:3.1:compile
+   * org.codehaus.jackson:jackson-mapper-asl:jar:1.5.3:compile
+   * org.codehaus.jackson:jackson-core-asl:jar:1.5.3:compile
+   * org.apache.httpcomponents:httpclient:jar:4.1-alpha2:compile
+   * org.apache.httpcomponents:httpcore:jar:4.1-beta1:compile
+   * commons-logging:commons-logging:jar:1.1.1:compile
+   * org.easymock:easymock:jar:2.5.2:compile
+   * org.objenesis:objenesis:jar:1.0:compile
+   * org.apache.commons:commons-io:jar:1.3.2:compile
+   * javax.validation:validation-api:jar:1.0.0.GA:compile
+   * org.hibernate:hibernate-validator:jar:4.0.2.GA:compile
+   *
+  '''GNU Lesser General Public License'''
+   * c3p0:c3p0:jar:
+  '''Dual license of the MPL and the LGPL'''
+   * javassist:javassist:jar:3.8.0.GA:compile
+  '''BSD License'''
+   * org.hsqldb:hsqldb:jar:
+  '''GPL-2.0'''
+   * mysql:mysql-connector-java:jar:5.1.10:compile
+  '''Public Domain'''
+   * aopalliance:aopalliance:jar:1.0:compile
+  '''LPGL v2.1'''
+   * org.hibernate:hibernate-core:jar:3.3.2.GA:compile
+   * org.hibernate:hibernate-annotations:jar:3.4.0.GA:compile
+   * org.hibernate:ejb3-persistence:jar:1.0.2.GA:compile
+   * org.hibernate:hibernate-commons-annotations:jar:3.1.0.GA:compile
+  '''BSD license'''
+   * antlr:antlr:jar:2.7.6:compile
+   * dom4j:dom4j:jar:1.6.1:compile
+   * org.hamcrest:hamcrest-core:jar:1.1:compile
+   * javax.transaction:jta:jar:1.1:compile
+   * javax.mail:mail:jar:1.4.3:compile
+   * javax.activation:activation:jar:1.1:compile
+   * javax.servlet:jstl:jar:1.2:compile
+   * javax.xml.bind:jaxb-api:jar:2.1:compile
+   * com.sun.xml.bind:jaxb-impl:jar:2.1.3:compile
+  '''MIT license'''
+   * org.slf4j:slf4j-api:jar:1.5.8:compile
+   * org.slf4j:slf4j-log4j12:jar:1.5.8:compile log4j:log4j:jar:1.2.14:compile
+   * org.mockito:mockito-core:jar:1.8.5:compile
+ ==== OGCE Gadget Container ====
+  '''Apache Software License, Version 2.0'''
+   * OpenAJAX
+   * Commons-codec
+   * Commons-logging
+   * Commons-fileupload
+   * Commons-collections
+   * Commons-digester
+   * Commons-el
+   * Commons-lang
+   * Tomcat Catalina
+   * Google-collections
+   * Xalan
+   * Xerces dom3-xml-apis and dom3-xercesImpl
+   * Tomcat annotations-api
+   * commons-beanutils
+   * commons-io
+   * openid4java
+   * axiom-api
+   * openxri-client, openxri-syntax
+   * jug
+   * stax-api
+   * Guice
+   * cilogon-portal-servlet (also have BSD & NCSA Licenses)
+  '''MIT'''
+   * Facebook Java API
+   * slf4j (3 jars: simple, api, and jdk14)
+   * xmlsec
+  '''BSD'''
+   * Dom4j
+   * Antlr
+  '''CDDL'''
+   * JSTL
+  '''GPL V3'''
+   * EXT-JS v2.2
+  '''GPL v2'''
+   * Trimpath v1.0.38
+   * Rhino JS 1.7R1 (Also has MPL1.1 license)
+   * Sun Jersey (Also has CDDI license)
+   * mysql-connector-jar
+  '''LGPL'''
+   * Hibernate
+   * !C3P0
+   * JBoss Javassist (Also has MPL License)
+   * htmlparser (also has CPL License)
+  '''Common Public License, v1'''
+   * Junit, junit-addons
+  '''Sun Binary'''
+   * Servlet API
+   * activation
+  '''EPL'''
+   * higgins-configuration-api
+   * higgins-sts-api
+   * higgins-sts-common
+   * higgins-sts-server-token-handler
+   * higgins-sts-spi
+  '''Other'''
+   * Google !FriendConnect:
+   * TMT JS:
+   * JSON:
+   * H2:
+   * icu4j:

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

View raw message