Proposal for jUDDI, A Web Services Subproject (via Incubator)
http://juddi.org
7 Feburary 2003, Davanum Srinivas (dims@yahoo.com), Steve Viens (sviens@comcast.net)
(0) rationale
jUDDI (pronounced "Judy"), currently hosted at SourceForge (http://sourceforge.net/projects/juddi/), is a java-based implementation of a Universal Description Discovery and Integration (UDDI) registry.
jUDDI has been an open-source project on SourceForge since September 2000 and has recently adopted Apache meritocracy rules to govern the project. Beginning with version 0.6.0, the license for jUDDI has been changed from GPL to BSD.
(0.1) criteria
Community: A growing community of developers from higher education and some genearally interested in Web Services have been working with jUDDI and/or deploying UDDI registries. A few well-known software companies have also been working with jUDDI over the past six months.
Core Developers: Primary author is Steve Viens
Alignment: Uses Axis, Log4j and Commons Logging and generally looks to Apache projects before turning elsewhere due to compatability of licensing terms and code quality and support. jUDDI is typically deployed as a J2EE Web Application and most development and testing occurs under Tomcat servlet container.
Scope: jUDDI currently implements version 2.0 of the UDDI specification but will continue to closly track the progress of the UDDI Technical Committee at OASIS (http://www.oasis-open.org/committees/uddi-spec/) and implement new features and changes as they are included in the specification.
(0.2) warning signs
Orphaned Products:
Inexperience:
Homogeneous Developers:
Reliance on Salaried Developers:
No ties to other Apache Products: As stated above, jUDDI uses Axis, Log4j and Commons Logging, and generally looks to Apache projects before turning elsewhere due to compatability of licensing terms and code quality and support. jUDDI is typically deployed as a J2EE Web Application and most development and testing occurs under Tomcat servlet container.
(1) scope of the subproject
As stated above, jUDDI currently implements version 2.0 of the UDDI specification but will continue to closly track the progress of the UDDI Technical Committee at OASIS (http://www.oasis-open.org/committees/uddi-spec/) and implement new features and changes as they are included in the specification.
(2) identify the initial source from which the subproject is to be populated
http://juddi.org
(3) identify the ASF resources to be created
(3.1) mailing list(s)
juddi-dev
(3.2) CVS repositories
ws-juddi (proposed)
(3.3) Bugzilla
(4) identify the initial set of committers
{{{ Steve Viens (steve@viens.net)
Anou Manavalan (anou_mana@hotmail.com) Andy Cutright (andy.cutright@borland.com) Davanum Srinivas (dims@yahoo.com) Anil Saldhana (anilsaldhana@yahoo.com) }}}
(5) identify apache sponsoring individual
Davanum Srinivas (dims@yahoo.com)