This is an automated email from the ASF dual-hosted git repository.
eya pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-age-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a5711b1 Update index.html (#40)
a5711b1 is described below
commit a5711b17810636d17f8bbbb4398dadf51701ea84
Author: Andrew Ko <[email protected]>
AuthorDate: Fri Apr 22 11:31:01 2022 +0900
Update index.html (#40)
---
index.html | 76 +++++++++++++++++++++++++++++++++-----------------------------
1 file changed, 41 insertions(+), 35 deletions(-)
diff --git a/index.html b/index.html
index 796ac70..13634a5 100644
--- a/index.html
+++ b/index.html
@@ -1398,6 +1398,12 @@ Committers should support the development and
advancement of AGE in different ar
<td> [email protected]
</td>
</tr>
+
+ <tr>
+ <td>David Shin </td>
+ <td> [email protected]
+ </td>
+ </tr>
</tbody>
</table>
@@ -1638,177 +1644,177 @@ The ASF Security Team maintains a page with the
description of how vulnerabiliti
<tr>
<td style="width:15%;"><b>Category</b></td>
<td style="width:40%;"><b>Description</b></td>
- <td style="background-color:yellowgreen;width:45%;"><b>AGE
self asssessment</b></td>
+ <td style="width:45%;"><b>Self Asssessment</b></td>
</tr>
<tr>
<td style="width:15%;">Code CD10</td>
<td style="width:40%;">The project produces Open Source
software for distribution to the public, at no charge.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
project source code is licensed under the Apache License, version 2.0.</td>
+ <td style="width:45%;">YES. The project source code is
licensed under the Apache License, version 2.0.</td>
</tr>
<tr>
<td style="width:15%;">Code CD20</td>
<td style="width:40%;">Anyone can easily discover and access
the project's code.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Linked from the website, available via git.apache.org and GitHub at
https://github.com/apache/incubator-age</td>
+ <td style="width:45%;">YES. Linked from the website,
available via git.apache.org and GitHub at
https://github.com/apache/incubator-age</td>
</tr>
<tr>
<td style="width:15%;">Code CD30</td>
<td style="width:40%;">Anyone using standard,
widely-available tools, can build the code in a reproducible way.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Anyone with a standard OS can build the AGE extension from the code at the
GitHub repo.</td>
+ <td style="width:45%;">YES. Anyone with a standard OS can
build the AGE extension from the code at the GitHub repo.</td>
</tr>
<tr>
<td style="width:15%;">Code CD40</td>
<td style="width:40%;">The full history of the project's
code is available via a source code control system, in a way that allows anyone
to recreate any released version.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Releases are cut from Main repository at
https://github.com/apache/incubator-age All releases are tagged.</td>
+ <td style="width:45%;">YES. Releases are cut from Main
repository at https://github.com/apache/incubator-age All releases are
tagged.</td>
</tr>
<tr>
<td style="width:15%;">Code CD50</td>
<td style="width:40%;">The source code control system
establishes the provenance of each line of code in a reliable way, based on
strong authentication of the committer. When third parties contribute code,
commit messages provide reliable information about the code provenance.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
project GitHub repository, managed by Apache Infra, ensures provenance of each
line of code to a committer. Third party contributions are accepted in
accordance with the Contribution Guide only.</td>
+ <td style="width:45%;">YES. The project GitHub repository,
managed by Apache Infra, ensures provenance of each line of code to a
committer. Third party contributions are accepted in accordance with the
Contribution Guide only.</td>
</tr>
<tr>
<td style="width:15%;">Licenses and Copyright LC10</td>
<td style="width:40%;">The Apache License, version 2.0,
covers the released code.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Source distributions clearly state license. Convenience binaries clearly state
license.</td>
+ <td style="width:45%;">YES. Source distributions clearly
state license. Convenience binaries clearly state license.</td>
</tr>
<tr>
<td style="width:15%;">Licenses and Copyright LC20</td>
<td style="width:40%;">Libraries that are mandatory
dependencies of the project's code do not create more restrictions than the
Apache License does.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
list of mandatory dependencies have been reviewed to contain approved licenses
only.</td>
+ <td style="width:45%;">YES. The list of mandatory
dependencies have been reviewed to contain approved licenses only.</td>
</tr>
<tr>
<td style="width:15%;">Licenses and Copyright LC30</td>
<td style="width:40%;">The libraries mentioned in LC20 are
available as Open Source software.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. All
mandatory dependencies are available as open source software.</td>
+ <td style="width:45%;">YES. All mandatory dependencies are
available as open source software.</td>
</tr>
<tr>
<td style="width:15%;">Licenses and Copyright LC40</td>
<td style="width:40%;">Committers are bound by an Individual
Contributor Agreement (the "Apache iCLA") that defines which code they may
commit and how they need to identify code that is not their own.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
project uses a repository managed by Apache Infra -- write access requires an
Apache account, which requires an ICLA on file.</td>
+ <td style="width:45%;">YES. The project uses a repository
managed by Apache Infra -- write access requires an Apache account, which
requires an ICLA on file.</td>
</tr>
<tr>
<td style="width:15%;">Licenses and Copyright LC50</td>
<td style="width:40%;">The project clearly defines and
documents the copyright ownership of everything that the project produces.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. All
files in the source repository have appropriate headers (see below).Even
further, Software Grant Agreements for the initial donations and Corporate CLAs
have been filed.</td>
+ <td style="width:45%;">YES. All files in the source
repository have appropriate headers (see below).Even further, Software Grant
Agreements for the initial donations and Corporate CLAs have been filed.</td>
</tr>
<tr>
<td style="width:15%;">Releases RE10</td>
<td style="width:40%;">Releases consist of source code,
distributed using standard and open archive formats that are expected to stay
readable in the long term.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Source releases are distributed via dist.apache.org and linked from the
website.</td>
+ <td style="width:45%;">YES. Source releases are distributed
via dist.apache.org and linked from the website.</td>
</tr>
<tr>
<td style="width:15%;">Releases RE20</td>
<td style="width:40%;">The project's PMC (Project Management
Committee, see CS10) approves each software release in order to make the
release an act of the Foundation.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. All
incubating releases have been unanimously approved by the AGE community and the
Incubator, all with at least 3 (P)PMC votes.</td>
+ <td style="width:45%;">YES. All incubating releases have
been unanimously approved by the AGE community and the Incubator, all with at
least 3 (P)PMC votes.</td>
</tr>
<tr>
<td style="width:15%;">Releases RE30</td>
<td style="width:40%;">Releases are signed and/or
distributed along with digests that anyone can reliably use to validate the
downloaded archives.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. All
releases are signed, and the KEYS file is provided on dist.apache.org.</td>
+ <td style="width:45%;">YES. All releases are signed, and the
KEYS file is provided on dist.apache.org.</td>
</tr>
<tr>
<td style="width:15%;">Releases RE40</td>
<td style="width:40%;">The project can distribute
convenience binaries alongside source code, but they are not Apache Releases,
they are provided with no guarantee.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Docker images are available at the <a target="_blank"
href="https://hub.docker.com/r/apache/age";>AGE Docker Hub</a> under the Apache
Software Foundation account.</td>
+ <td style="width:45%;">YES. Docker images are available at
the <a target="_blank" href="https://hub.docker.com/r/apache/age";>AGE Docker
Hub</a> under the Apache Software Foundation account.</td>
</tr>
<tr>
<td style="width:15%;">Releases RE50</td>
<td style="width:40%;">The project documents a repeatable
release process so that someone new to the project can independently generate
the complete set of artifacts required for a release.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Release guide is available describing the entire process on the AGE website at
the <a target="_blank" href="https://age.apache.org/?l=releaseprocess";>Release
Process</a> page. The AGE releases have been performed by multiple release
managers.</td>
+ <td style="width:45%;">YES. Release guide is available
describing the entire process on the AGE website at the <a target="_blank"
href="https://age.apache.org/?l=releaseprocess";>Release Process</a> page. The
AGE releases have been performed by multiple release managers.</td>
</tr>
<tr>
<td style="width:15%;">Quality QU10</td>
<td style="width:40%;">The project is open and honest about
the quality of its code. Various levels of quality and maturity for various
modules are natural and acceptable as long as they are clearly
communicated.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE project records bugs in the Apache’s JIRA issue tracker.</td>
+ <td style="width:45%;">YES. The AGE project records bugs in
the Apache’s JIRA issue tracker.</td>
</tr>
<tr>
<td style="width:15%;">Quality QU20</td>
<td style="width:40%;">The project puts a very high priority
on producing secure software.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Security issues are treated with the highest priority and any potential
security issue is managed and reported per the Apache Way.</td>
+ <td style="width:45%;">YES. Security issues are treated with
the highest priority and any potential security issue is managed and reported
per the Apache Way.</td>
</tr>
<tr>
<td style="width:15%;">Quality QU30</td>
<td style="width:40%;">The project provides a
well-documented, secure and private channel to report security issues, along
with a documented way of responding to them.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
Apache <a target="_blank" href="https://age.apache.org/?l=agesecurity";>AGE
Security</a> page describes how to report security issues and also informs how
to deal with security issuses in accordance with the Apache Way.</td>
+ <td style="width:45%;">YES. The Apache <a target="_blank"
href="https://age.apache.org/?l=agesecurity";>AGE Security</a> page describes
how to report security issues and also informs how to deal with security
issuses in accordance with the Apache Way.</td>
</tr>
<tr>
<td style="width:15%;">Quality QU40</td>
<td style="width:40%;">The project puts a high priority on
backwards compatibility and aims to document any incompatible changes and
provide tools and documentation to help users transition to new features.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Each release contains a release notes and is announced on the AGE website at
the <a target="_blank" href="https://age.apache.org/?l=roadmap";>Roadmap</a>
page with the details of the features added or improved. The project aims to
make no backward incompatible changes within a given major version.</td>
+ <td style="width:45%;">YES. Each release contains a release
notes and is announced on the AGE website at the <a target="_blank"
href="https://age.apache.org/?l=roadmap";>Roadmap</a> page with the details of
the features added or improved. The project aims to make no backward
incompatible changes within a given major version.</td>
</tr>
<tr>
<td style="width:15%;">Quality QU50</td>
<td style="width:40%;">The project strives to respond to
documented bug reports in a timely manner.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE project community has responded to every bug reported in a timely manner.
</td>
+ <td style="width:45%;">YES. The AGE project community has
responded to every bug reported in a timely manner. </td>
</tr>
<tr>
<td style="width:15%;">Community CO10</td>
<td style="width:40%;">The project has a well-known homepage
that points to all the information required to operate according to this
maturity model.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE website contains every key information about the AGE project including the
description of the project, technical details, online user guide and how to
contribute and release the software. </td>
+ <td style="width:45%;">YES. The AGE website contains every
key information about the AGE project including the description of the project,
technical details, online user guide and how to contribute and release the
software. </td>
</tr>
<tr>
<td style="width:15%;">Community CO20</td>
<td style="width:40%;">The community welcomes contributions
from anyone who acts in good faith and in a respectful manner, and who adds
value to the project.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
It’s part of the contribution guide and the current committers are really keen
to welcome contributions.</td>
+ <td style="width:45%;">YES. It’s part of the contribution
guide and the current committers are really keen to welcome contributions.</td>
</tr>
<tr>
<td style="width:15%;">Community CO30</td>
<td style="width:40%;">Contributions include source code,
documentation, constructive bug reports, constructive discussions, marketing
and generally anything that adds value to the project.</td>
- <td style="background-color:yellowgreen;width:45%;">The AGE
project values and accepts both source code and non-source code
contributions.</td>
+ <td style="width:45%;">The AGE project values and accepts
both source code and non-source code contributions.</td>
</tr>
<tr>
<td style="width:15%;">Community CO40</td>
<td style="width:40%;">The community strives to be
meritocratic and gives more rights and responsibilities to contributors who,
over time, add value to the project.</td>
- <td style="background-color:yellowgreen;width:45%;">YES.
Based on meritocracy, the AGE community has elected 9 new committers and has
elevated 4 committers to PPMC during incubation. </td>
+ <td style="width:45%;">YES. Based on meritocracy, the AGE
community has elected 9 new committers and has elevated 4 committers to PPMC
during incubation. </td>
</tr>
<tr>
<td style="width:15%;">Community CO50</td>
<td style="width:40%;">The project documents how
contributors can earn more rights such as commit access or decision power, and
applies these principles consistently.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
process to become a committer is documented on the AGE website at the <a
target="_blank" href="https://age.apache.org/?l=committerres";>Committer
Requirements</a> page.</td>
+ <td style="width:45%;">YES. The process to become a
committer is documented on the AGE website at the <a target="_blank"
href="https://age.apache.org/?l=committerres";>Committer Requirements</a>
page.</td>
</tr>
<tr>
<td style="width:15%;">Community CO60</td>
<td style="width:40%;">The community operates based on
consensus of its members (see CS10) who have decision power. Dictators,
benevolent or not, are not welcome in Apache projects.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
project works to build consensus. All votes have been unanimous todate.</td>
+ <td style="width:45%;">YES. The project works to build
consensus. All votes have been unanimous todate.</td>
</tr>
<tr>
<td style="width:15%;">Community CO70</td>
<td style="width:40%;">The project strives to answer user
questions in a timely manner.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE project typically provides detailed answers to user questions in a timely
manner via dev@ mailing list and users@ mailing list.</td>
+ <td style="width:45%;">YES. The AGE project typically
provides detailed answers to user questions in a timely manner via dev@ mailing
list and users@ mailing list.</td>
</tr>
<tr>
<td style="width:15%;">Community consensus CS10</td>
<td style="width:40%;">The project maintains a public list
of its contributors who have decision power. The project's PMC (Project
Management Committee) consists of those contributors.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE website contains a list of the committers and the PPMC members.</td>
+ <td style="width:45%;">YES. The AGE website contains a list
of the committers and the PPMC members.</td>
</tr>
<tr>
<td style="width:15%;">Community consensus CS20</td>
<td style="width:40%;">Decisions require a consensus among
PMC members and are documented on the project's main communications channel.
The PMC takes community opinions into account, but the PMC has the final
word.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE project has been making all important decisions on the Apache AGE project
mailing lists.</td>
+ <td style="width:45%;">YES. The AGE project has been making
all important decisions on the Apache AGE project mailing lists.</td>
</tr>
<tr>
<td style="width:15%;">Community consensus CS30</td>
<td style="width:40%;">The project uses documented voting
rules to build consensus when discussion is not sufficient.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
project uses the standard ASF voting rules. Voting rules are clearly stated
before the voting starts for each individual vote.</td>
+ <td style="width:45%;">YES. The project uses the standard
ASF voting rules. Voting rules are clearly stated before the voting starts for
each individual vote.</td>
</tr>
<tr>
<td style="width:15%;">Community consensus CS40</td>
<td style="width:40%;">In Apache projects, vetoes are only
valid for code commits. The person exercising the veto must justify it with a
technical explanation, as per the Apache voting rules defined in CS30.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
project hasn't used a veto at any point and relies on robust code reviews.</td>
+ <td style="width:45%;">YES. The project hasn't used a veto
at any point and relies on robust code reviews.</td>
</tr>
<tr>
<td style="width:15%;">Community consensus CS50</td>
<td style="width:40%;">All "important" discussions happen
asynchronously in written form on the project's main communications channel.
Offline, face-to-face or private discussions 11 that affect the project are
also documented on that channel.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE project has been making all important decisions on the AGE project's
official Apache mailing lists. Some discussions may occasionally happen at the
AGE project's GitHub repository and they become registered also on the AGE
project's developer mailing list.</td>
+ <td style="width:45%;">YES. The AGE project has been making
all important decisions on the AGE project's official Apache mailing lists.
Some discussions may occasionally happen at the AGE project's GitHub repository
and they become registered also on the AGE project's developer mailing
list.</td>
</tr>
<tr>
<td style="width:15%;">Independence IN10</td>
<td style="width:40%;">The project is independent from any
corporate or organizational influence.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
AGE project's PPMC members and committer are from 8 different companies.</td>
+ <td style="width:45%;">YES. The AGE project's PPMC members
and committer are from 8 different companies.</td>
</tr>
<tr>
<td style="width:15%;">Independence IN20</td>
<td style="width:40%;">Contributors act as themselves, not
as representatives of a corporation or organization.</td>
- <td style="background-color:yellowgreen;width:45%;">YES. The
contributors act on their own initiative without representing a corporation or
organization.</td>
+ <td style="width:45%;">YES. The contributors act on their
own initiative without representing a corporation or organization.</td>
</tr>
