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 "IvrWorxProposal" by borisu
Date Mon, 08 Feb 2010 10:19:02 GMT
Dear Wiki user,

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

The "IvrWorxProposal" page has been changed by borisu.
http://wiki.apache.org/incubator/IvrWorxProposal?action=diff&rev1=2&rev2=3

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

  
  == Abstract ==
  
- Apache Ace is a software distribution framework based on OSGi that allows you to manage
and distribute artifacts, like e.g. software components.
+ IvrWorx is a :-
+ 
+ 1. fiber based messaging framework based 
+ 
+ 2. lightweight SIP IVR application built on top of it.
+ 
+ IvrWorx strives to provide framework for easy creation of any message based application
by reducing asynchrnous programming. 
+ IVR application and integration effort.
  
  == Proposal ==
  
- Apache Ace is a software distribution framework that allows you to centrally manage and
distribute software components, configuration data and other artifacts to target systems.
It is built using OSGi and can be deployed in different topologies. The target systems are
usually also OSGi based, but don't have to be.
+ IvrWorx strives to provide framework for easy creation of any message based application
by reducing asynchronous programming effort. As an example lightweight SIP Ivr application
is provided to demosntrated pluggabilty od different protocols feature under one synchronous
API.
  
  == Background ==
  
+ Telephony application is essentially high
- When assembling software out of reusable components, the task of deploying software onto
an ever increasing number of targets is not trivial to solve. This becomes even harder when
these targets require different components based on who's using them.
- 
- A key technology in the Java space for developing component based applications is OSGi.
The OSGi speciļ¬cation, which has been around since 1999 and by now has matured into the
de facto module system for Java, allows you to write components that can interact through
services and that allows components to be updated individually, without disturbing the rest
of the components.
- 
- Although the OSGi speciļ¬cation describes how software distribution should be done, it
does not actually prescribe any protocols or implementations. Apache Ace implements a software
distribution system based on, but not limited to OSGi. It is setup so it can deal with different
target types, using different protocols. Also, it can handle an extensible number of artifact
types (bundles, configurations, resources, ...).
  
  == Rationale ==
  
@@ -33, +36 @@

  
  == Current Status ==
  
- The current codebase is developed and tested in various configurations. It was developed
at luminis over the last couple of years using Scrum, so we have internally demonstrated we
can release often and produce working code using a transparent process. Documentation for
the project is now available on an internal wiki, which can be donated and converted to the
Apache Ace website. We did not yet use mailing lists as the primary colaborative process,
as the whole team met face to face on a daily basis.
+ The current codebase is developed and tested. It was developed at luminis over the last
couple of years using Scrum, so we have internally demonstrated we can release often and produce
working code using a transparent process. Documentation for the project is now available on
an internal wiki, which can be donated and converted to the Apache Ace website. We did not
yet use mailing lists as the primary colaborative process, as the whole team met face to face
on a daily basis.
  
  == Meritocracy ==
  
- Some of the core developers are already committers and PMC members at Apache, so they understand
what it means to have a process based on meritocracy.
+ N/A
  
  == Community ==
  
@@ -45, +48 @@

  
  == Core Developers ==
  
- The core development team is a mix of people that work for luminis and have been involved
in the project up til now and new committers, some of which have previous experience at Apache.
+ Currently ivrworx is being developed by single developer. We certainly hope to extend the
team to more developers.
  
  == Alignment ==
  
@@ -63, +66 @@

  
  == Source and Intellectual Property Submission Plan ==
  
- The current codebase is owned by luminis, and will be donated together with its documentation.
We will get the paperwork out of the way as soon as possible. There should already be a CCLA
on file for luminis and the people that are already involved with Apache obviously have ICLAs
on file.
+ The current codebase is owned by Boris Ouretskey under GPLV3 license, and will be donated
together with its documentation. We will get the paperwork out of the way as soon as possible.
There should already be a CCLA on file for luminis and the people that are already involved
with Apache obviously have ICLAs on file.
  
  == External Dependencies ==
  
  There are quite a few open source libraries already used. The libraries, their sources and
licenses are listed here:
  
+ IvrWorx is strongly dependent on  which powers all message based framework. 
- Apache Felix, ASL:
-  * framework
-  * shell
-  * shell-tui
-  * obr
-  * http.jetty
-  * config admin
-  * event admin
-  * deployment admin
-  * dependency manager
-  * prefs
-  * upnp.basedriver
-  * org.osgi.foundation
-  * core
-  * compendium
-  * javax.servlet
  
+ Strong core dependency on 
- Apache Ant, ASL:
-  * ant.jar
-  * ant-contrib.jar
  
+  * KentCSP++
- Apache Velocity, ASL:
-  * velocity
  
+ Weak dependency on 
- KXML2 (http://kxml.sourceforge.net/kxml2/), BSD license:
-  * kxml2 (hmm, what was that issue we had with that in felix)
  
- Knopflerfish (http://knopflerfish.org/), BSD style license:
-  - log_all.jar, useradmin_all.jar
+  * lua
+  * json spirit
  
+ Pluggable dependency on 
- Luminis Open Source Server (https://opensource.luminis.net/), BSD license:
-  * net.luminis.build.plugin.jar
  
- XStream (http://xstream.codehaus.org/), BSD license:
-  * various xstream jars
- 
+  * medisatreamer2
+  * resiprocate
+  * live555
+  * unimrcp
  == Required Resources ==
  
+ N/A
- Mailing lists:
-  * ace-private
-  * ace-dev
-  * ace-commits
-  * ace-user (only after leaving the incubator)
- 
- Subversion:
-  * https://svn.apache.org/repos/asf/incubator/ace
- 
- Issue Tracking:
-  * JIRA: Apache Ace (ACE)
- 
- Wiki:
-  * Confluence: Apache Ace (ACE)
  
  == Initial Committers ==
  
- These existing Apache committers have either worked on the initial codebase (Christian,
Karl and Marcel) or expressed an interest in extending the project:
+ These existing Apache committers have either worked on the initial codebase or expressed
an interest in extending the project:
  
+  * Boris Ouretskey
-  * Marcel Offermans
-  * Karl Pauls
-  * Christian van Spaandonk
-  * Clement Escoffier
-  * Felix Meschberger
-  * Carsten Ziegeler
  
  == Community Members ==
  
+ N/A
- The following people have already expressed their interest in actively participating in
this project:
- 
-  * Bram de Kruijff
-  * Toni Menzel
-  * Alin Dreghiciu
-  * Dennis Geurts
  
  == Affiliations ==
  
- For the record, Marcel Offermans, Christian van Spaandonk and Dennis Geurts work at luminis
and might get paid to do certain work on Apache Ace.
+ For the record, Boris Ouretskey is working for Cosmocom - call center on demand provider.
  
  == Sponsors ==
  
- We have approached both the champion and an initial list of mentors that have agreed to
mentor this project.
+ Champion:
  
+ N/A
- Champion:
-  * Karl Pauls
  
  Mentors:
+ 
+ N/A
-  * Carsten Ziegeler
-  * Niclas Hedhman
-  * Bertrand Delacretaz
  
  Sponsor:
-  * Apache Incubator
  
+ N/A
+ 

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


Mime
View raw message