accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwa...@apache.org
Subject [accumulo-website] branch master updated: Remove broken link on get_involved.md page (#31)
Date Wed, 01 Nov 2017 21:38:35 GMT
This is an automated email from the ASF dual-hosted git repository.

mwalch pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 19d5482  Remove broken link on get_involved.md page (#31)
19d5482 is described below

commit 19d54825dfedb631ee197f4fffed086b4c15cca3
Author: Mark Owens <jmarkowe@gmail.com>
AuthorDate: Wed Nov 1 17:38:34 2017 -0400

    Remove broken link on get_involved.md page (#31)
    
    The link, "building open source communities", under the Community Interaction section
is broken. I cannot access www.betaversion.org at all. Rather than updating the broken link
with a confusing and basically unhelpful pdf link, the Community Interaction sub-section was
completely removed.
---
 pages/get_involved.md | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/pages/get_involved.md b/pages/get_involved.md
index 7ebd426..94d1b8f 100644
--- a/pages/get_involved.md
+++ b/pages/get_involved.md
@@ -47,10 +47,6 @@ Take a look at [Accumulo's Ohloh page][5] for an analysis of the code base.
 * [Accumulo Users Group - DC VA MD](https://www.meetup.com/Accumulo-Users-DC/)
 * Look for [Accumulo Meetups in your area](https://www.meetup.com/find/?keywords=accumulo)
 
-## Community Interaction
-
-Learn about [building open source communities][6].
-
 ## Decision Making
 
 The most important thing about engaging with any Apache project is that everyone
@@ -67,7 +63,7 @@ Most of the time we work with the consensus building techniques documented
below
 
 ### Lazy Consensus
 
-[Lazy consensus][7] is the first, and possibly the most important, consensus building 
+[Lazy consensus][6] is the first, and possibly the most important, consensus building 
 tool we have. Essentially, lazy consensus means that you don't need to get explicit
 approval to proceed, but you need to be prepared to listen if someone objects.
 
@@ -76,15 +72,15 @@ approval to proceed, but you need to be prepared to listen if someone
objects.
 Sometimes, lazy consensus is not appropriate. In such cases, it is necessary to
 make a proposal to the mailing list and discuss options. There are mechanisms
 for quickly showing your support or otherwise for a proposal and 
-[building consensus][8] amongst the community.
+[building consensus][7] amongst the community.
 
 Once there is a consensus, people can proceed with the work under the [lazy 
-consensus][9] model.
+consensus][8] model.
 
 ### Voting
 
 Occasionally a "feel" for consensus is not enough. Sometimes we need to 
-have a measurable consensus. For example, when [voting][10] in new committers or 
+have a measurable consensus. For example, when [voting][9] in new committers or 
 to approve a release. 
 
 [1]: https://s.apache.org/newbie_accumulo_tickets
@@ -92,8 +88,8 @@ to approve a release.
 [3]: https://www.meetup.com/find/?keywords=accumulo
 [4]: {{ site.baseurl }}/contributor/
 [5]: https://www.ohloh.net/p/accumulo
-[6]: http://www.betaversion.org/~stefano/papers/ac2006.2.pdf
-[7]: {{ site.baseurl }}/contributor/lazyConsensus
-[8]: {{ site.baseurl }}/contributor/consensusBuilding
-[9]: {{ site.baseurl }}/contributor/lazyConsensus
-[10]: {{ site.baseurl }}/contributor/voting
+[6]: {{ site.baseurl }}/contributor/lazyConsensus
+[7]: {{ site.baseurl }}/contributor/consensusBuilding
+[8]: {{ site.baseurl }}/contributor/lazyConsensus
+[9]: {{ site.baseurl }}/contributor/voting
+

-- 
To stop receiving notification emails like this one, please contact
['"commits@accumulo.apache.org" <commits@accumulo.apache.org>'].

Mime
View raw message