incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From svi...@apache.org
Subject cvs commit: incubator/site/projects juddi.cwiki
Date Mon, 22 Dec 2003 22:17:22 GMT
sviens      2003/12/22 14:17:22

  Modified:    site/projects juddi.cwiki
  Log:
  More status updates.
  
  Revision  Changes    Path
  1.9       +65 -30    incubator/site/projects/juddi.cwiki
  
  Index: juddi.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/juddi.cwiki,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- juddi.cwiki	22 Dec 2003 21:11:44 -0000	1.8
  +++ juddi.cwiki	22 Dec 2003 22:17:22 -0000	1.9
  @@ -5,7 +5,7 @@
   
   !!!Project Website
   
  -The website for the jUDDI project is: http://ws.apache.org/juddi/.
  +The website for the jUDDI project is: [http://ws.apache.org/juddi/].
   
   The previous jUDDI website address now forwards all traffic to the new website.
   
  @@ -13,9 +13,7 @@
   
   !!!Identify the project to be incubated
   
  -*Make sure that the requested project 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.
  +*Make sure that the requested project 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.
   
   On 22-Dec-2003 we used the free online search form available at www.nameprotect.com. No
trademark conflicts were found for the name "jUDDI' in the US or Canada. The domain name 'juddi.org'
is owned by a jUDDI committer (Steve Viens).
   
  @@ -23,20 +21,19 @@
   
   *If request from an existing Apache project to adopt an external package, then ask the
Apache project for the cvs module and mail address names.
   
  -A cvs module is in place and the jUDDI source has been imported. Source 
  -can be viewed via ViewCVS at the following URL: 
  +A cvs module is in place and the jUDDI source has been imported. Source can be viewed via
ViewCVS at the following URL: 
   
   __DONE__
   
   juddi-user and juddi-dev mailing lists have been created and are being archived at the
following locations:
     
  -  juddi-dev@ws.apache.org
  -  http://nagoya.apache.org/eyebrowse/SummarizeList?listId=179
  -  http://marc.theaimsgroup.com/?l=juddi-dev
  +  *juddi-dev@ws.apache.org*
  +  [http://nagoya.apache.org/eyebrowse/SummarizeList?listId=179]
  +  [http://marc.theaimsgroup.com/?l=juddi-dev]
     
  -  juddi-user@ws.apache.org
  -  http://nagoya.apache.org/eyebrowse/SummarizeList?listId=197
  -  http://marc.theaimsgroup.com/?l=juddi-user
  +  *juddi-user@ws.apache.org*
  +  [http://nagoya.apache.org/eyebrowse/SummarizeList?listId=197]
  +  [http://marc.theaimsgroup.com/?l=juddi-user]
   
   Also, all past messages for these list have been imported into the archives that are available
at MARC.
   
  @@ -64,9 +61,7 @@
   
   !!!Copyright
   
  -*Have 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.
  +*Have 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.
   
   *Have the files been updated to reflect the new ASF copyright?
   
  @@ -74,9 +69,7 @@
   
   Verify distribution rights:
   
  -*For all code included with the distribution that is not under the
  -     Apache license, do we have the right to combine with Apache-licensed
  -     code and redistribute?
  +*For all code included with the distribution that is not under the Apache license, do we
have the right to combine with Apache-licensed code and redistribute?
   
   The distribution includes the jUDDI jar file and the following files: 
   
  @@ -96,52 +89,94 @@
   
   Proper license files are also included. The build process depends on uddi4j.jar, which
is not included in the distribution, for license issues. 
   
  -__DONE__
  +__TO-DO__
   
   *Is all source code distributed by the project 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?
   
  +__TO-DO__
  +
   !!!Establish a list of active committers
   
   *Are all active committers in the STATUS file?
   
   *Do they have accounts on cvs.apache.org?
   
  +Currently waiting for notification that one committer's CLA has been recieved and filed.
All others have accounts and can access cvs.
  +
  +__TO-DO__
  +
   *Have they submitted a contributors agreement?
   
  +Currently waiting for notification that one committer's CLA has been recieved and filed.
All others have accounts and can access cvs.
  +
  +__TO-DO__
  +
   !!!Infrastructure
   
   *CVS modules created and committers added to avail file?
   
  +__DONE__
  +
   *Mailing lists set up and archived?
   
  +__DONE__
  +
   *Problem tracking system (Bugzilla)?
   
  +To-Do (waiting for Jira installation to be completed). Until then bugs continue to be tracked
on SourceForge.net
  +
  +[http://sourceforge.net/tracker/?group_id=42875&atid=434422]
  +
  +__TO-DO__
  +
   *Has the project migrated to our infrastructure?
   
  -!!!Collaborative Development
  +__DONE__
  +
  +*Have all of the active long-term volunteers been identified and acknowledged as committers
on the project?
  +
  +There are four jUDDI committers:
   
  -*Have all of the active long-term volunteers been identified
  -     and acknowledged as committers on the project?
  +  1 Steve Viens
  +  1 Anou Manavalan
  +  1 Andy Cutright
  +  1 Anil Saldhana
  +
  +All four individuals are acknowledged jUDDI committers.  We're currently waiting for notification
that Anil's CLA has been recieved and filed.
  +  
  +__DONE__
   
   *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.)
  +All four initial jUDDI committers are independent committers.
  +
  +__DONE__
   
   *Are project decisions being made in public by the committers?
   
  -*Are the decision-making guidelines published and agreed to by
  -     all of the committers?
  +Yes.
  +
  +__DONE__
  +
  +*Are the decision-making guidelines published and agreed to by all of the committers?
  +
  +Yes.
  +
  +__DONE__
   
   !!!Organizational acceptance of responsibility for the project
   
   *If graduating to an existing PMC, has the PMC voted to accept it?
   
  +The Web Services PMC has voted to Incubate jUDDI. If jUDDI successfully makes it through
Incubation it will become part of the Web Services Project.
  +
  +__DONE__
  +
   *If graduating to a new PMC, has the board voted to accept it?
   
  +__NOT APPLICABLE__
  +
  +
   !!!Incubator sign-off
   
  -*Has the Incubator decided that the project has accomplished all
  -     of the above tasks?
  +*Has the Incubator decided that the project has accomplished all of the above tasks?
  
  
  

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


Mime
View raw message