nicolaken    2003/12/04 06:21:50

  Modified:    site/projects index.xml
               site     site.xml
  Added:       site/projects ruper.cwiki
  Log:
  Adding Ruper to the Incubating projects.
  
  NOTE: on "namesprotect" I did not find any Ruper, but there were
  lots of Rupert.
  
  Revision  Changes    Path
  1.19      +10 -1     incubator/site/projects/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/index.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- index.xml 19 Nov 2003 16:24:17 -0000      1.18
  +++ index.xml 4 Dec 2003 14:21:50 -0000       1.19
  @@ -90,12 +90,21 @@
              <td>2003-09</td>
            </tr>  
             <tr>
  -           <td><link href="site:projects/directory">Apache 
Directory</link></td>
  +           <td><link href="site:projects/directory">Directory</link></td>
              <td>Directory projects.</td> 
              <td>Incubator PMC</td>       
              <td>Noel J. Bergman, Nicola Ken Barozzi</td>
              <td>2003-10-23</td>
            </tr>   
  +          <tr>
  +           <td><link href="site:projects/ruper">Ruper</link></td>
  +           <td>Integrated tools for automating downloading, publishing
  +               and managing software artifacts, along with tools for 
  +               manipulating their metadata.</td> 
  +           <td>Incubator PMC</td>       
  +           <td>Nicola Ken Barozzi</td>
  +           <td>2003-12-04</td>
  +         </tr>  
          </table>
       </section>   
       <section>
  
  
  
  1.1                  incubator/site/projects/ruper.cwiki
  
  Index: ruper.cwiki
  ===================================================================
  !!! Ruper Project Incubation Status
  
  This page tracks the project status, incubator-wise.
  For more general project status, look on the project website.
  
  !!! Description
  
  The Ruper Project deals with integrated tools for automating downloading 
  (with security checks), publishing (new artifacts) and managing the contents 
  of the apache repository. 
  
  It also focuses on additional tools for manipulating metadata of the 
artifacts.
  
  !!! News
  
  * none yet
  
  !!! Project info
  
  || item              || type     || reference                 
  |  Website           | www       | .
  |  .                 | wiki      | .
  |  Mailing list      | dev       | .
  |  .                 | cvs       | .
  |  Bug tracking      | .         | .
  |  Source code       | CVS       | .
  |  Mentors           | nicolaken | Nicola Ken Barozzi
  |  Committers        | .         | .
  |  Extra             | proposal  | 
[http://nagoya.apache.org/wiki/apachewiki.cgi?RepoProposal]
    
  
  !!! Incubation status reports
  
  * none yet
  
  !!! Incubation work items
  
  !! Project Setup
  
  This is the first phase on incubation, needed to start the project at Apache.
  
  '' Item assignment is shown by the Apache id.''
  '' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
  
  ! Identify the project to be incubated
  || date || item
  | 2003-12-04 | 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.
  | 2003-12-04 | If 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.
  
  ! Interim responsibility
  
  || date || item
  | 2003-12-04 | Identify all the Mentors for the incubation, by asking all 
that can be Mentors. 
  | 2003-12-04 | Subscribe all Mentors on the pmc and general lists. 
  | 2003-12-04 | Give all Mentors access to all incubator CVS modules. (to be 
done by PMC chair)  
  | 2003-12-04 | Tell Mentors to track progress in the file 
'incubator/projects/{project.name}.cwiki' 
  
  ! Copyright
  
  || date || item
  | ....-..-.. | Check 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. 
  | ....-..-.. | Check and make sure that the files that have been donated have 
been updated to reflect the new ASF copyright. 
  
  ! Verify distribution rights
  
  || date || item
  | ....-..-.. | Check and make sure that for all code included with the 
distribution that is not under the Apache license, e have the right to combine 
with Apache-licensed code and redistribute. 
  | ....-..-.. | Check and make sure that all source code distributed 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 !
  
  || date || item
  | ....-..-.. | Check that all active committers have submitted a contributors 
agreement. 
  | ....-..-.. | Add all active committers in the STATUS file. 
  | ....-..-.. | Ask root for the creation of committers' accounts on 
cvs.apache.org. 
  
  ! Infrastructure !
  
  || date || item
  | ....-..-.. | Ask infrastructure to create source repository modules and add 
thecommitters to the avail file. 
  | ....-..-.. | Ask infrastructure to set up and archive Mailing lists. 
  | ....-..-.. | Decide about and then ask infrastructure to setup an 
issuetracking system (Bugzilla, Scarab, Jira). 
  | ....-..-.. | Migrate the project to our infrastructure. 
  
  ! Project specific 
  
  ''Add project specific tasks here.''
  
  !! Incubation 
  
  These action items have to be checked for during the whole incubation process.
  
  '' These items are not to be signed as done during incubation, as they may 
change during incubation.  ''
  '' They are to be looked into and described in the status reports and 
completed in the request for incubation signoff.  ''
  
  ! Collaborative Development 
  
  * Have all of the active long-term volunteers been identified and 
acknowledged as committers on the project?
  * 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.)
  * Are project decisions being made in public by the committers?
  * Are the decision-making guidelines published and agreed to by all of the 
committers?
  
  ! Licensing awareness 
  
  * Are all licensing, trademark, credit issues being taken care of and 
acknowleged by all committers?
  
  ! Project Specific 
  
  ''Add project specific tasks here.''
  
  !! Exit 
  
  ''Things to check for before voting the project out.''
  
  ! Organizational acceptance of responsibility for the project 
  
  * If graduating to an existing PMC, has the PMC voted to accept it?
  * If graduating to a new PMC, has the board voted to accept it?
  
  ! Incubator sign-off 
  
  * Has the Incubator decided that the project has accomplished all of the 
above tasks?
  
  
  
  1.19      +1 -0      incubator/site/site.xml
  
  Index: site.xml
  ===================================================================
  RCS file: /home/cvs/incubator/site/site.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- site.xml  4 Dec 2003 13:27:21 -0000       1.18
  +++ site.xml  4 Dec 2003 14:21:50 -0000       1.19
  @@ -29,6 +29,7 @@
       <wsrp4j label="Wsrp4j" href="wsrp4j.html"/>   
       <xmlbeans label="XmlBeans" href="xmlbeans.html"/>   
       <directory label="Directory" href="directory.html"/>   
  +    <ruper label="Ruper" href="ruper.html"/>   
     </projects>
       
     <learn label="Learn" tab="learn" href="learn/">
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to