You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@age.apache.org by ey...@apache.org on 2022/04/21 02:20:53 UTC
[incubator-age-website] branch asf-site updated: Updated some info on matrix, pg support and a menu name (#38)
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 99edb4b Updated some info on matrix, pg support and a menu name (#38)
99edb4b is described below
commit 99edb4b53198cb41d54d17904f8640291291724f
Author: Andrew Ko <76...@users.noreply.github.com>
AuthorDate: Thu Apr 21 11:20:49 2022 +0900
Updated some info on matrix, pg support and a menu name (#38)
* Update index.html
* Update index.html
* Update index.html
* Update index.html
---
index.html | 47 ++++++++++++++++++++++++-----------------------
1 file changed, 24 insertions(+), 23 deletions(-)
diff --git a/index.html b/index.html
index eda523c..4d2e30c 100644
--- a/index.html
+++ b/index.html
@@ -34,12 +34,12 @@
<!-- FAQs <br /> -->
<span id="sidebar-license" class="sidebar-item"> <a class="sidebar-link" href="#" onclick="handleClick(this)">License</a></span> <br />
<!-- Downloads <br /> -->
- <span id="sidebar-roadmap" class="sidebar-item"> <a class="sidebar-link" href="#sidebar-roadmap" onclick="handleClick(this)">Roadmap</a></span> <br />
+ <span id="sidebar-roadmap" class="sidebar-item"> <a class="sidebar-link" href="#" onclick="handleClick(this)">Roadmap</a></span> <br />
</p>
<p class="sidebar--section">
<span class="emph">DOCUMENTATION</span> <br />
- <a target="_blank" class="sidebar-link external-link" href="docs/master/index.html">Documentation</a> <br />
+ <a target="_blank" class="sidebar-link external-link" href="docs/master/index.html">Online User Guide</a> <br />
</p>
@@ -119,7 +119,7 @@
<div class="heading"><h2>Features</h2></div>
<ul>
- <li>AGE is currently being developed for the PostgreSQL 11 release and will support PostgreSQL 12, 13 and 14 in Q1 2022 and all the future releases of PostgreSQL. </li>
+ <li>AGE is currently being developed for the PostgreSQL 11 release and will support PostgreSQL 12, 13 and 14 in Q2 2022 and all the future releases of PostgreSQL. </li>
<li>AGE supports the openCypher graph query language and label hierarchy.</li>
<li>AGE enables querying multiple graphs at the same time. This will allow a user to query two or more graphs at once with cypher, decide how to merge them and get the desired query outputs.</li>
<li>AGE will be enhanced with an aim to support all of the key features of AgensGraph (PostgreSQL fork extended with graph DB functionality). </li>
@@ -318,6 +318,7 @@
</tr>
</tbody>
</table>
+ <br>
<table>
<tbody>
<tr>
@@ -1672,12 +1673,12 @@ The ASF Security Team maintains a page with the description of how vulnerabiliti
<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. See below.</td>
+ <td style="background-color:yellowgreen;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. See below.</td>
+ <td style="background-color:yellowgreen;width:45%;">YES. All mandatory dependencies are available as open source software.</td>
</tr>
<tr>
<td style="width:15%;">Licenses and Copyright LC40</td>
@@ -1707,42 +1708,42 @@ The ASF Security Team maintains a page with the description of how vulnerabiliti
<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. AGE provides docker files for convenience with the installation and drivers for users to connect to the project.</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>
</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. The AGE releases have been performed by different people.</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>
</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 project records all bugs in the Apache’s JIRA issue tracker.</td>
+ <td style="background-color:yellowgreen;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, according to the CVE/Security Advisory procedure. We lean on the data redundancy, authentication and security features provided by postgres.</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>
</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. Website provides AGE security page: https://age.apache.org</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>
</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 “What’s new” on the website containing the release notes (extracted for Jira). The project aims to make no backward incompatible changes within a given major version.</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>
</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 project has resolved >150 issues during incubation.</td>
+ <td style="background-color:yellowgreen;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 project website has a description of the project with technical details, and how to contribute. Several issues ahve been flagged as "good first issue" also available at https://github.com/apache/incubator-age/contribute</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>
</tr>
<tr>
<td style="width:15%;">Community CO20</td>
@@ -1752,37 +1753,37 @@ The ASF Security Team maintains a page with the description of how vulnerabiliti
<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%;">YES. The contribution guide refers to non source code contribution, like documentation.</td>
+ <td style="background-color:yellowgreen;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. The community has elected 4 new committers during incubation, based on meritocracy.</td>
+ <td style="background-color:yellowgreen;width:45%;">YES. Based on meritocracy, the AGE community has elected 8 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 criteria is documented in the contribution guide.</td>
+ <td style="background-color:yellowgreen;width:45%;">YES. The process to become a committer is documented on the AGE website at the <span id="inline_committerres"> <a href="#" onclick="handleClick(this)">Committer Requirements</a></span> 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="background-color:yellowgreen;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 project typically provides detailed answers to user questions within a few hours via dev@ mailing list and users@ mailing list.</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>
</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 website contains the list of committers and PPMC members.</td>
+ <td style="background-color:yellowgreen;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 project has been making important decisions on the project mailing lists. Vast majority of, if not all, decisions have had a consensus without any PPMC action needed. We are working on making it better.</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>
</tr>
<tr>
<td style="width:15%;">Community consensus CS30</td>
@@ -1797,17 +1798,17 @@ The ASF Security Team maintains a page with the description of how vulnerabiliti
<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 project has been making important decisions on the project mailing lists. Minor decisions may occasionally happen during code reviews, which are also asynchronous and in written form. We're working to improve in this area.</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>
</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. While one particular organisation is keenly interested in the development of AGE the community is autonomous in product design and development</td>
+ <td style="background-color:yellowgreen;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 committers and contributors act on their own initiative without representing a corporation or organization. Many contributors are employees of a single company who has interest in the success of AGE but there are many entirely independent contributors.</td>
+ <td style="background-color:yellowgreen;width:45%;">YES. The contributors act on their own initiative without representing a corporation or organization.</td>
</tr>