as patches) either within the body of the message or provide a URL for
retrieval.
-To join the mailing lists, see our link:mail.html[Mailing List] page.
+To join the mailing lists, see our xref:mail.adoc[Mailing List] page.
The Project's list fall into the categories below.
=== Product Support
-If you have questions or comments about the software or documentation on this site, please subscribe to the appropriate mailing list listed link:mail.html[here].
+If you have questions or comments about the software or documentation on this site, please subscribe to the appropriate mailing list listed xref:mail.adoc[here].
=== Security Issues
=== The DB Project
If after reviewing the material on http://db.apache.org/[this site], you have
-questions regarding DB or the link:management.html[Project Management Committee],
-you may post them to the link:mail.html[General mailing list].
+questions regarding DB or the xref:management.adoc[Project Management Committee],
+you may post them to the xref:mail.adoc[General mailing list].
**Proposing a New Subproject**
-See our link:newproject.html[DB Subproject Proposals] page.
+See our xref:newproject.adoc[DB Subproject Proposals] page.
=== The DB Website(s)
== Decision Making
-All link:roles.html[Contributors] are encouraged to participate in
+All xref:roles.adoc[Contributors] are encouraged to participate in
decisions, but the decision itself is made by those that have
-link:roles.html[Committer] status in the Project. In other words, the
+xref:roles.adoc[Committer] status in the Project. In other words, the
Project is a *Minimum Threshold Meritocracy*.
Any subscriber to the list may vote on any issue or action item.
resolved by voting, and the procedures to follow for proposing and making
changes to the codebase of the Project.
- * link:roles.html[Roles and Responsibilities]
+ * xref:roles.adoc[Roles and Responsibilities]
Defines the recognized roles in the project.
- * link:communication.html[Communication]
+ * xref:communication.adoc[Communication]
Defines how users and developers communicate.
- * link:decisions.html[Decision Making]
+ * xref:decisions.adoc[Decision Making]
Defines how action items are proposed and voted on.
- * link:source.html[Organization of Source Repositories]
+ * xref:source.adoc[Organization of Source Repositories]
Defines how the Project's source code is organized and developed.
- * link:management.html[Project Management]
+ * xref:management.adoc[Project Management]
Defines the roles and responsibilities of the Project Management Committee (PMC).
- * link:newproject.html[New Subproject Proposals]
+ * xref:newproject.adoc[New Subproject Proposals]
Defines the methodology for proposing new top level DB Subprojects.
This is a living document. Changes can be made by the Project Management
Committee. Suggestions for changes should be discussed on the
-general at db.apache.org link:mail.html[mailing list].
+general at db.apache.org xref:mail.adoc[mailing list].
For more about the Apache DB Project, see
- * link:guidelines.html[DB Project Guidelines]
- * link:newproject.html[DB Subproject Proposals]
- * link:contact.html[Contacting Us]
+ * xref:guidelines.adoc[DB Project Guidelines]
+ * xref:newproject.adoc[DB Subproject Proposals]
+ * xref:contact.adoc[Contacting Us]
For more about the Apache Software Foundation, visit the Foundation's Web site
This is the project general mailing list.
This is where ideas, suggestions, and comments are exchanged that deal with the overall DB project.
Matters that affect the project as a whole are decided here.
-If you are interested in adding a new project to DB, please see link:newproject.html[this page].
+If you are interested in adding a new project to DB, please see xref:newproject.adoc[this page].
=== Derby Mailing Lists
DB that, in the opinion of the PMC as determined by a vote, displays the
capability and desire to help guide the DB project. The PMC will nominate a
chairperson from amongst their ranks for presentation to the Board. The list
-of current members can be found in our link:whoweare.html[Project Credits].
+of current members can be found in our xref:whoweare.adoc[Project Credits].
=== Roles
member may be removed from the PMC by a 3/4 vote of the PMC.
In order to be elected to the PMC, a person must have served as a
-link:roles.html[Committer] and be nominated by a PMC Member. The nominee must
+xref:roles.adoc[Committer] and be nominated by a PMC Member. The nominee must
receive 3/4 positive vote with a minimum of 3 positive votes. Abstaining PMC
voters do not affect the result.
**Meritocracy**.
Before submitting a proposal, be sure to study the guidelines that
-link:guidelines.html[govern DB subprojects]. These guidelines explain our system
+xref:guidelines.adoc[govern DB subprojects]. These guidelines explain our system
of Meritocracy, which is the core of the DB Project. If the product
developers do not wish to adopt this system, then they should **not** donate
their code to the Project, and should look elsewhere for hosting.
at least one of the developers making the proposal to already be active in a
DB subproject or other open source initiative.
-At DB, the core developers of a product (the link:roles.html[Committers]) manage
+At DB, the core developers of a product (the xref:roles.adoc[Committers]) manage
the codebases and make the day-to-day development decisions. We are only
interested in products that can guided by their own development communities.
DB provides the infrastructure, and some essential guidelines, but the
we must believe that a product will attract volunteers to extend and maintain
it over the long term. A product like this, arriving with no volunteer
developers or open source community, does not further
-link:index.html#DB_Mission[DB's mission], and would not be accepted.
+xref:index.adoc#DB_Mission[DB's mission], and would not be accepted.
We generally recommend that an orphaned product start with an independent
host, and consider making a proposal after it has started to build a
=== Who Decides
Final acceptance is based the rules defined in the
-link:management.html[Project Management Committee Bylaws] which state that
+xref:management.adoc[Project Management Committee Bylaws] which state that
"Creation of a new subproject requires approval by 3/4 vote of the PMC." The
proposal for a new subproject must submitted to the DB General
-link:mail.html[mailing list], where the PMC conducts business. All discussion
+xref:mail.adoc[mailing list], where the PMC conducts business. All discussion
regarding the proposal will occur the General list, including the final vote.
it on the project's Developer mailing list.
A list of some of our current Committers can be found in our
-link:whoweare.html[Project Credits].
+xref:whoweare.adoc[Project Credits].
=== Management Committee (PMC)
individual may then be approved with a 3/4 majority of the PMC.
To view the Project Management Committee bylaws, click
-link:management.html[here].
+xref:management.adoc[here].
A list of our current PMC Members can be found in our
-link:whoweare.html[Project Credits].
+xref:whoweare.adoc[Project Credits].
== Sitemap
- * link:index.html[Welcome]
- * link:communication.html[Communication]
- * link:contact.html[Contact us!]
- * link:decisions.html[Decision Making]
- * link:guidelines.html[Project Guidelines]
- * link:mail.html[Mailing Lists]
- * link:management.html[PMC Bylaws]
- * link:newproject.html[Subproject Proposals]
- * link:roles.html[Roles and Responsibilities]
- * link:source-repos.html[Source Repositories]
- * link:source.html[Organization of Source Repositories]
- * link:whoweare.html[Who We Are]
+ * xref:index.adoc[Welcome]
+ * xref:communication.adoc[Communication]
+ * xref:contact.adoc[Contact us!]
+ * xref:decisions.adoc[Decision Making]
+ * xref:guidelines.adoc[Project Guidelines]
+ * xref:mail.adoc[Mailing Lists]
+ * xref:management.adoc[PMC Bylaws]
+ * xref:newproject.adoc[Subproject Proposals]
+ * xref:roles.adoc[Roles and Responsibilities]
+ * xref:source-repos.adoc[Source Repositories]
+ * xref:source.adoc[Organization of Source Repositories]
+ * xref:whoweare.adoc[Who We Are]
The DB Project operates on a meritocracy: the more you do, the more responsibility you will
obtain. This page lists all of the people who have gone the extra mile and are Committers or
members of the Project Management Committee. If you would like to get involved, the first
-step is to join the link:mail.html[mailing lists].
+step is to join the xref:mail.adoc[mailing lists].
We ask that you please do not send us emails privately asking for support. We are non-paid
volunteers who help out with the project and we do not necessarily have the time or energy
-to help people on an individual basis. Instead, we have setup link:mail.html[mailing lists] which often
+to help people on an individual basis. Instead, we have setup xref:mail.adoc[mailing lists] which often
contain hundreds of individuals who will help answer detailed requests for help. The benefit
of using mailing lists over private communication is that it is a shared resource where
others can also learn from common mistakes and as a community we all grow together.
projects / db-site.git / commitdiff
