Closed tristaZero closed 4 years ago
tristaZero
commented
4 years ago To solve item 1st and 3rd, you can search key word issues, wiki commits for double-check.
For your convenience, to copy and paste the content below to a new file is my advice. ⬇️
tristaZero
commented
4 years ago <?xml version="1.0" encoding="UTF-8"?>
<document>
<properties>
<title>Apache ShardingSphere Project Incubation Status </title>
<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
</properties>
<body>
<section id="ShardingSphere+Project+Incubation+Status">
<title>Apache ShardingSphere 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>Sharding-Sphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration. </p>
</section>
<section id="News">
<title>News</title>
<ul>
<li>2020-01-13 ShardingSphere 4.0.0 released</li>
<li>2020-01-08 New committer: Jiang Xiaofeng</li>
<li>2019-12-12 New committer: Dong ZongLei</li>
<li>2019-12-06 New committer: Ouyang Wen</li>
<li>2019-11-26 ShardingSphere 4.0.0-RC3 released</li>
<li>2019-11-13 New committer: Yan Zhiyi</li>
<li>2019-10-22 New committer: Li Ya</li>
<li>2019-09-24 New committer: Wang Qi</li>
<li>2019-09-20 New committer: Wang Guangyuan</li>
<li>2019-09-17 New committer: Sun Haisheng</li>
<li>2019-09-12 New committer: Zhao Yanan</li>
<li>2019-09-04 ShardingSphere officially docker repositories have transfered to Apache Docker Hub organization</li>
<li>2019-08-23 ShardingSphere 4.0.0-RC2 released</li>
<li>2019-04-21 ShardingSphere 4.0.0-RC1 released</li>
<li>2019-02-02 New PPMC: Yang Yi</li>
<li>2019-02-02 New PPMC: Du Hongjun</li>
<li>2019-01-19 ShardingSphere website on ASF</li>
<li>2018-11-10 Project enters incubation</li>
</ul>
</section>
<section id="Project+info">
<title>Project info</title>
<ul>
<li>ShardingSphere Website - https://shardingsphere.incubator.apache.org</li>
</ul>
<ul>
<li>
<a href="https://shardingsphere.incubator.apache.org/community/">Community Pages</a>
</li>
</ul>
<ul>
<li>
<a href="https://shardingsphere.apache.org/document/current/">Current Documentation</a>
</li>
</ul>
<ul>
<li>
<a href="https://shardingsphere.apache.org/document/current/en/downloads/">Releases</a>
</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 id="www">
<a href="https://shardingsphere.incubator.apache.org/">https://shardingsphere.incubator.apache.org/</a>
</td>
</tr>
<tr>
<td>.</td>
<td>wiki</td>
<a href="https://cwiki.apache.org/confluence/display/SHARDINGSPHERE">https://cwiki.apache.org/confluence/display/SHARDINGSPHERE</a>
</tr>
<tr>
<td>Mailing list</td>
<td>dev</td>
<td id="mail-dev">
<code>dev</code>
<code>@</code>
<code>shardingsphere.incubator.apache.org</code>
</td>
</tr>
<tr>
<td>.</td>
<td>private</td>
<td id="mail-private">
<code>private</code>
<code>@</code>
<code>shardingsphere.incubator.apache.org</code></td>
</tr>
<tr>
<td>.</td>
<td>commits</td>
<td id="mail-commits">
<code>commits</code>
<code>@</code>
<code>shardingsphere.incubator.apache.org</code></td>
</tr>
<tr>
<td>.</td>
<td>notifications</td>
<td id="mail-notifications">
<code>notifications</code>
<code>@</code>
<code>shardingsphere.incubator.apache.org</code></td>
</tr>
<tr>
<td>Bug tracking</td>
<td>.</td>
<td id="tracker">
https://github.com/apache/incubator-shardingsphere/issues
</td>
</tr>
<tr>
<td>Source code</td>
<td>.</td>
<td>.</td>
</tr>
<tr>
<td>.</td>
<td>incubator-shardingsphere</td>
<td>https://github.com/apache/incubator-shardingsphere.git</td>
</tr>
<tr>
<td>.</td>
<td>incubator-shardingsphere-example</td>
<td>https://github.com/apache/incubator-shardingsphere-example.git</td>
</tr>
<tr>
<td>.</td>
<td>incubator-shardingsphere-doc</td>
<td>https://github.com/apache/incubator-shardingsphere-doc.git</td>
</tr>
<tr>
<td>Roster</td>
<td>Whimsy</td>
<td><a href='https://whimsy.apache.org/roster/ppmc/shardingsphere'>ShardingSphere Roster</a></td>
</tr>
<tr>
<td>Mentors</td>
<td/>
<td>see <a href='https://whimsy.apache.org/roster/ppmc/shardingsphere#mentors'>ShardingSphere Roster Mentors</a></td>
</tr>
<tr>
<td>PMC and Committers</td>
<td/>
<td>see <a href='https://whimsy.apache.org/roster/ppmc/shardingsphere#ppmc'>ShardingSphere Roster PMC + Committers</a></td>
</tr>
</table>
</section>
<section id="Incubation+status+reports">
<title>Incubation status reports</title>
<ul>
<li><a href='https://whimsy.apache.org/board/minutes/shardingsphere.html'>ShardingSphere Board Reports</a></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 (2018-11-10).</em>
</p>
<section id="Identify+the+project+to+be+incubated">
<title>Identify the project to be incubated</title>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>2018-11-10</td>
<td>Make sure that the requested project name does not already exist. <a href="http://www.apache.org/foundation/marks/naming.html">Please follow
the guide to ensure a suitable project/product name.</a></td>
</tr>
<tr>
<td>N/A</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>N/A</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>2018-11-10</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="Infrastructure">
<title>Infrastructure</title>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>2018-11-18</td>
<td>Request DNS (first step after creating podling status page)</td>
</tr>
<tr>
<td>2018-11-18</td>
<td>Request <a href='https://whimsy4.apache.org/officers/mlreq/incubator'>Mailing Lists</a></td>
</tr>
<tr>
<td>2019-01-16</td>
<td>Request <a href='https://reporeq.apache.org/'>git repositories</a></td>
</tr>
<tr>
<td>N/A</td>
<td>Ask infrastructure to create source repository modules
and grant the committers karma (if using SVN)</td>
<!-- Use https://infrahelp.apache.org/ -->
</tr>
<tr>
<td>N/A</td>
<td>Ask infrastructure to set up issue tracker (<a href='https://selfserve.apache.org/jira.html'>JIRA</a>, Bugzilla).</td>
</tr>
<tr>
<td>2019-06-03</td>
<td>Ask infrastructure to set up wiki (<a href='https://selfserve.apache.org/confluence.html'>Confluence</a>).</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Migrate the project to our infrastructure.</td>
</tr>
</table>
</section>
<section id="Interim+responsibility">
<title>Mentor-related responsibility/oversight</title>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>N/A</td>
<td>Subscribe all Mentors on the pmc and general lists.</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Give all Mentors access to the incubator Git repository.
(to be done by the Incubator PMC chair or an Incubator PMC
Member wih karma for the authorizations file)</td>
</tr>
<tr>
<td>....-..-..</td>
<td>Tell Mentors to track progress in the file '<a href="https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/shardingsphere.xml">incubator/contents/projects/shardingsphere.xml</a>'</td>
</tr>
</table>
</section>
<section id="Copyright">
<title>Copyright</title>
<table>
<tr>
<th>date</th>
<th>item</th>
</tr>
<tr>
<td>2019-01-16</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>2019-01-16</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>2019-04-21</td>
<td>Check and make sure that for all code included with the distribution
that is not under the Apache license, we have the right to combine
with Apache-licensed code and redistribute.
</td>
</tr>
<tr>
<td>2019-04-21</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>2019-09-18</td>
<td>Check that all active committers have submitted a contributors
agreement.</td>
<!-- check http://people.apache.org/committer-index.html -->
</tr>
<tr>
<td>2019-09-18</td>
<td>Add all active committers in the relevant section above.</td>
</tr>
<tr>
<td>2019-09-18</td>
<td>Ask root for the creation of committers' accounts in
LDAP.</td>
<!-- this may happen automatically as their ICLAs are filed.
If you are using git source control, ensure that all
committers are members of the 'incubator' group. -->
</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>YES</li>
<li>If graduating to a new PMC, has the board voted to accept it?</li>
<li>YES</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>We have to add the following links to our website to solve sub-issues from 4th to 9th.
http://www.apache.org/ http://www.apache.org/events/current-event http://www.apache.org/licenses/ http://www.apache.org/foundation/thanks.html http://www.apache.org/security/ http://www.apache.org/foundation/sponsorship.html
tristaZero
commented
4 years ago To fix sub-issues 10th to 12th, the copyright, trademarks and disclaimer are required. Please refer to my proposal here.
Copyright © 2018-2020, Apache ShardingSphere, ShardingSphere, Apache, the Apache feather logo, and the Apache ShardingSphere project logo are either registered trademarks or trademarks of The Apache Software Foundation in the United States and other countries.
Apache ShardingSphere is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of The Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.For the last one, i am not sure, here is one hint. https://incubator.apache.org/clutch/shardingsphere.html
tristaZero
commented
4 years ago The 16th item is
The 17th one is
When the user clicks Community button, the drop-down list will show three items,
Developer item directs the user to https://shardingsphere.apache.org/community/enWiki item directs the user to https://cwiki.apache.org/confluence/display/SHARDINGSPHEREIssue Tracker directs the user to https://github.com/apache/incubator-shardingsphere/issuestristaZero
commented
4 years ago All done. Congrats!
Those items are blockers for our graduation, please refer to shardingsphere to learn more.
Project xml
Missing links
Missing descriptions on website
Release distributions
Deployment
Missing linksandMissing descriptions on websiteto website