This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/master by this push:
new 0f82111 Updated Contributor Listing policy per
https://s.apache.org/1oYF CTR
0f82111 is described below
commit 0f82111ecd1a1c966760c9009d486eae4adc8a3e
Author: Stephen Mallette <[email protected]>
AuthorDate: Wed Dec 19 08:40:32 2018 -0500
Updated Contributor Listing policy per https://s.apache.org/1oYF CTR
---
docs/site/home/index.html | 7 ++--
docs/src/dev/developer/administration.asciidoc | 44 ++++++++++++++++++++++++++
docs/src/dev/developer/for-committers.asciidoc | 2 +-
3 files changed, 49 insertions(+), 4 deletions(-)
diff --git a/docs/site/home/index.html b/docs/site/home/index.html
index c630f8f..a18843b 100644
--- a/docs/site/home/index.html
+++ b/docs/site/home/index.html
@@ -295,9 +295,10 @@ limitations under the License.
<li><a href="http://tomsawyer.com/products/perspectives/";>Tom
Sawyer Perspectives</a> - Advanced graphics-based software for building
enterprise-class data relationship visualization and analysis applications.</li>
</ul>
<a name="committers"></a>
- <h3 id="committers">Apache TinkerPop Committers</h3>
- <img src="img/tinkerpop-logo-small.png" style="float:right"
/>TinkerPop seeks committers dedicated to the art of graph computing. TinkerPop
committers bring solid theoretical,
- development, testing, documentation, etc. skills to the group.
Committers contribute to TinkerPop beyond the ever-changing requirements of
their day-to-day jobs and maintain
+ <a name="contributors"></a>
+ <h3 id="contributors">Apache TinkerPop Contributors</h3>
+ <img src="img/tinkerpop-logo-small.png" style="float:right"
/>TinkerPop seeks contributors dedicated to the art of graph computing.
TinkerPop contributors bring solid theoretical,
+ development, testing, documentation, etc. skills to the group. These
individuals contribute to TinkerPop beyond the ever-changing requirements of
their day-to-day jobs and maintain
responsibility for their contributions through time.
<p/>
<ul>
diff --git a/docs/src/dev/developer/administration.asciidoc
b/docs/src/dev/developer/administration.asciidoc
index 95ca454..29bf6e1 100644
--- a/docs/src/dev/developer/administration.asciidoc
+++ b/docs/src/dev/developer/administration.asciidoc
@@ -184,3 +184,47 @@ committed to the appropriate meeting agenda in SVN at:
[source,text]
https://svn.apache.org/repos/private/foundation/board
+[[contributor-listing]]
+== Contributor Listing
+
+Contributions can come in <<many forms,Contributing Section>> and extend well
beyond code contributions. TinkerPop
+strives to ensure that contributions are honestly and accurately recognized
for the benefit of the individuals who
+help make TinkerPop possible.
+
+One of the ways in which this recognition is supported is by way of the
+link:http://tinkerpop.apache.org/#contributors[Contributor Listing] on the
TinkerPop home page, which list those who
+have contributed to the project in some way. It lists both committers and PMC
members and provides a short "bio"
+(i.e. a description of their contributions) as well as an indication of
whether they are currently participating in
+the project or not, i.e. active or inactive. The bios have a slightly
different form depending on that status:
+
+* An _active_ bio should be reflective of current contributions, roughly
representing the past six months and the
+following six months of the update.
+* An _inactive_ bio for those not currently contributing to the project,
should reflect the full scope of all
+contributions made by that individual during their active periods.
+
+IMPORTANT: Irrespective of being active or inactive, the contributor's name
and tenure accomplishments remain present
+on the front page of the web site. Being "inactive" does *not* affect the
contributors status as an Apache committer or
+PMC member - that remains unchanged. Should a contributor become "inactive" at
some point, there is no special process
+to become "active" again - they simply update their bio to do so.
+
+Committers and PMC members can keep this information up to date themselves as
they have direct access to the Git
+repository. Reminders to update this information will be sent every six
months, beginning with a general email to
+the dev list followed by direct emails to individuals who might have missed
the reminder. Those who do not update
+their bios or do not reply to the email will be assumed "inactive" for purpose
of the listing.
+
+The following is a template for the "Bio Update" email:
+
+[source,text]
+----
+Subject: Apache TinkerPop Bio Update
+
+To Committers/PMC Members,
+
+As an Apache TinkerPop committer and/or PMC member, your name is listed on the
TinkerPop home page in the Contributor List[1] with your "bio". If you are
active on the project, your "bio" reflects what you have been working on and
what you expect to be working on with respect to TinkerPop for recent times
(i.e. for the previous six months and the following six months). If you are
currently inactive on the project, your "bio" reflects the full scope of all
your contributions throughout yo [...]
+
+Please take a moment to update your bio directly in Git[2] or, if you would
prefer, please reply to this email with your bio update and it will be added
for you. If no changes are required, please reply to this email to confirm that
this is the case.
+
+[1] http://tinkerpop.apache.org/#contributors
+[2] http://tinkerpop.apache.org/docs/current/dev/developer/#contributor-listing
+[3] https://github.com/apache/tinkerpop/blob/master/docs/site/home/index.html
+----
\ No newline at end of file
diff --git a/docs/src/dev/developer/for-committers.asciidoc
b/docs/src/dev/developer/for-committers.asciidoc
index 62b4791..a7a41a6 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -66,7 +66,7 @@ TinkerPop has several release branches:
* `tp31` - 3.1.x (no longer maintained)
* `tp32` - 3.2.x (major bug fixes only)
* `tp33` - 3.3.x (current development)
-* `master` - 3.4.x (future development)
+* `master` - 3.4.x (current development)
Changes to `tp32` should merge to `tp33` and then `tp33` to `master`. Please
read more about this process in the
<<pull-requests, Pull Requests>> section.
