Leo Simons wrote:

> As long as you make sure that the questions are more obvious from the docs
> afterwards, don't apologize :-)

>>*) IP clearance checklist - I need to make a copy of that in SVN here,
>>/incubator/site-author/ip-clearance.  I'll try and get that done over
>>the weekend.

Ok, I added /incubator/site-author/ip-clearance/ofbiz.xml - although I
only cut the lines to be cut and changed the title.  More later...

> Its not just the ip clearance that's needed. There's the concept of an
> incubator status file (see below).

I added that too, thanks to Jacopo Cappellato, who did the initial
version of it.

>>*) iCLA's - the OFBiz guys are working on it.  This needs to happen
>>before they get accounts, and conversely, they get accounts once this
>>happens, right?

> if the right emails are sent as documented on /dev/, yup.

Which /dev/ are you referring to?

>>*) Cleaning up the code - they're in the process of cleaning up the
>>code, getting rid of LGPL dependencies.  This needs to happen prior to
>>the code touching our subversion repositories, correct?

> No. It needs to happen prior to making any kind of release, and no LGPL
> code or binaries should touch our SVN. But working on removing such a
> dependency while within the incubator is okay.

Ok - I get the impression that they've got a good handle on this, and
may be able to do the initial import with no dependancies.

>>*) JIRA - they have a JIRA instance of their own, which should be
>>migrated to the ASF.  I don't know anything about admin'ing JIRA, so I
>>believe this step will require collaboration between David Jones and
>>someone on the infrastructure team.  Should I/we go ahead and open an
>>issue on our side for JIRA migration?  Does this step have dependencies,
>>or can it start to happen when people are ready to do the work?

> Yes, go ahead. I think this is quite a tricky thing to do. Jeff Turner is
> the guy from the infra team to talk to.

Ok.  So, if David Jones is reading this, that would be jefft followed by
apache.org, right?

>>*) Mailing lists - an issue needs to be opened for the infrastructure
>>team to create them, and then collaborate on moving over the existing
>>subscriber list.  Same question on dependencies as above.
>
> No particular dependencies. Provide the subscriber list as a file with
> email addresses seperated by newlines and add it to the jira issue, and
> its easy for the apmail people to add all those people in one swoop.
> Once that is done you can send an email to the new mailing list and all
> those people will know they're on a new list.

> Handling external mailing list archives (eg marc, mail-archives, gmane)
> might be a little work and depends on how those archives are set up to
> interact with the ASF stuff; I think some of them have 'special' support.

I'll let the OFBiz guys take it from here on this issue...

>>Anything else?
> 
> 
> The first step before doing any of the above is to get an incubation
> status file filled out and up on
> 
>   http://incubator.apache.org/projects/index.html
> 
> Eg, start off with
> 
>   
> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/incubation-status-template.xml

Thanks to Jacopo, we have an initial cut at that, but neither he nor I
has the tools to turn it into HTML (and I need to get some sleep tonight).

If anyone else on the OFBiz team wants to have a crack at it, it's
attached to this email (I'm not sure you can access the incubator repo
anonymously?).

-- 
David N. Welton
- http://www.dedasys.com/davidw/

Linux, Open Source Consulting
- http://www.dedasys.com/
<?xml version="1.0" encoding="UTF-8"?>
<document>
  <properties>
    <!--<meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
    <!--<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->

    <title>OFBiz Incubation Status</title>
    <link href="http://purl.org/DC/elements/1.0/"; rel="schema.DC"/>
  </properties>
  <body>
    <section id="OFBiz+Project+Incubation+Status">
      <title>OFBiz Project Incubation Status</title>
      <p>This page tracks the project status, incubator-wise. For more general project status, look on the project website.</p>
    </section>
    <section id="Description">
      <title>Description</title>
      <p>
	The Open For Business Project (OFBiz) is an open source
	enterprise automation software project. By open source
	enterprise automation we mean: Open Source ERP, Open Source
	CRM, Open Source E-Business / E-Commerce, Open Source SCM,
	Open Source MRP, Open Source CMMS/EAM, and so on. It is one of
	the few apps of this type to be developed by a community,
	rather than one corporation.
      </p>
    </section>
    <section id="News">
      <title>News</title>
      <ul>
        <li>2006-01-31 Project accepted by the Incubator PMC</li>
        <li>2006-01-10 Project proposed to the Incubator PMC</li>
      </ul>
    </section>
    <section id="Project+info">
      <title>Project info</title>
      <ul>
        <li>link to the main website</li>
      </ul>
      <ul>
        <li>link to the page(s) that tell how to participate (Website,Mailing lists,Bug tracking,Source code)</li>
      </ul>
      <ul>
        <li>link to the project status file (Committers,non-incubation action items,project resources, etc)</li>
      </ul>
      <p>If the project website and code repository are not yet setup, use the following table:</p>
      <table>
        <tr>
          <th>item</th>
          <th>type</th>
          <th>reference</th>
        </tr>
        <tr>
          <td>Website</td>
          <td>www</td>
          <td>
            <a href="http://www.ofbiz.org";>http://www.ofbiz.org</a> or <a href="http://incubator.apache.org/ofbiz/";>http://incubator.apache.org/ofbiz/</a>
          </td>
        </tr>
        <tr>
          <td>.</td>
          <td>wiki</td>
          <td>.</td>
        </tr>
        <tr>
          <td>Mailing list</td>
          <td>dev</td>
          <td>[EMAIL PROTECTED]</td>
        </tr>
        <tr>
          <td>.</td>
          <td>cvs</td>
          <td>incubator-cvs@apache.org</td>
        </tr>
        <tr>
          <td>Bug tracking</td>
          <td>.</td>
          <td>.</td>
        </tr>
        <tr>
          <td>Source code</td>
          <td>SVN</td>
          <td>incubator-X</td>
        </tr>
        <tr>
          <td>Mentors</td>
          <td>davidw</td>
          <td>David N. Welton</td>
        </tr>
        <tr>
          <td>.</td>
          <td>yoavs</td>
          <td>Yoav Shapira</td>
        </tr>
        <tr>
          <td>.</td>
          <td>farra</td>
          <td>J Aaron Farr</td>
        </tr>
        <tr>
          <td>Committers</td>
          <td>.</td>
          <td>David E. Jones</td>
        </tr>
        <tr>
          <td>.</td>
          <td>.</td>
          <td>Andy Zeneski</td>
        </tr>
        <tr>
          <td>.</td>
          <td>.</td>
          <td>Si Chen</td>
        </tr>
        <tr>
          <td>.</td>
          <td>.</td>
          <td>Al Byers</td>
        </tr>
        <tr>
          <td>.</td>
          <td>.</td>
          <td>Jacopo Cappellato</td>
        </tr>
        <tr>
          <td>.</td>
          <td>.</td>
          <td>Hans Bakker</td>
        </tr>
      </table>
    </section>
    <section id="Incubation+status+reports">
      <title>Incubation status reports</title>
      <ul>
        <li>none yet</li>
      </ul>
    </section>
    <section id="Incubation+work+items">
      <title>Incubation work items</title>
      <section id="Project+Setup">
        <title>Project Setup</title>
        <p>This is the first phase on incubation, needed to start the project at Apache.</p>
        <p>
          <em>Item assignment is shown by the Apache id.</em>
          <em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
        </p>
        <section id="Identify+the+project+to+be+incubated%26%23xD%3B">
          <title>Identify the project to be incubated&amp;#xD;</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>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.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>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.</td>
            </tr>
          </table>
        </section>
        <section id="Interim+responsibility">
          <title>Interim responsibility</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Identify all the Mentors for the incubation, by asking all that can be Mentors.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Subscribe all Mentors on the pmc and general lists.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Give all Mentors access to all incubator CVS modules. (to be done by PMC chair)</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'</td>
            </tr>
          </table>
        </section>
        <section id="Copyright">
          <title>Copyright</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>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.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.</td>
            </tr>
          </table>
        </section>
        <section id="Verify+distribution+rights">
          <title>Verify distribution rights</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>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.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>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.</td>
            </tr>
          </table>
        </section>
        <section id="Establish+a+list+of+active+committers">
          <title>Establish a list of active committers</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Check that all active committers have submitted a contributors agreement.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Add all active committers in the STATUS file.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Ask root for the creation of committers' accounts on people.apache.org.</td>
            </tr>
          </table>
        </section>
        <section id="Infrastructure">
          <title>Infrastructure</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Ask infrastructure to create source repository modules and grant the committers karma.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Ask infrastructure to set up and archive Mailing lists.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira).</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Migrate the project to our infrastructure.</td>
            </tr>
          </table>
        </section>
        <section id="Project+specific">
          <title>Project specific</title>
          <p>
            <em>Add project specific tasks here.</em>
          </p>
        </section>
      </section>
      <section id="Incubation">
        <title>Incubation</title>
        <p>These action items have to be checked for during the whole incubation process.</p>
        <p>
          <em>These items are not to be signed as done during incubation, as they may change during incubation.</em>
          <em>They are to be looked into and described in the status reports and completed in the request for incubation signoff.</em>
        </p>
        <section id="Collaborative+Development">
          <title>Collaborative Development</title>
          <ul>
            <li>Have all of the active long-term volunteers been identified and acknowledged as committers on the project?</li>
            <li>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.)</li>
            <li>Are project decisions being made in public by the committers?</li>
            <li>Are the decision-making guidelines published and agreed to by all of the committers?</li>
          </ul>
        </section>
        <section id="Licensing+awareness">
          <title>Licensing awareness</title>
          <ul>
            <li>Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?</li>
          </ul>
        </section>
        <section id="Project+Specific">
          <title>Project Specific</title>
          <p>
            <em>Add project specific tasks here.</em>
          </p>
        </section>
      </section>
      <section id="Exit">
        <title>Exit</title>
        <p>
          <em>Things to check for before voting the project out.</em>
        </p>
        <section id="Organizational+acceptance+of+responsibility+for+the+project">
          <title>Organizational acceptance of responsibility for the project</title>
          <ul>
            <li>If graduating to an existing PMC, has the PMC voted to accept it?</li>
            <li>If graduating to a new PMC, has the board voted to accept it?</li>
          </ul>
        </section>
        <section id="Incubator+sign-off">
          <title>Incubator sign-off</title>
          <ul>
            <li>Has the Incubator decided that the project has accomplished all of the above tasks?</li>
          </ul>
        </section>
      </section>
    </section>
  </body>
</document>




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

Reply via email to