accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] mikewalch closed pull request #31: Update broken link on get_involved.md page
Date Thu, 01 Jan 1970 00:00:00 GMT
mikewalch closed pull request #31: Update broken link on get_involved.md page
URL: https://github.com/apache/accumulo-website/pull/31
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

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
+


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message