Mailing-List: contact commits-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Date: Wed, 01 Nov 2017 21:52:50 +0000
To: "commits@accumulo.apache.org" <commits@accumulo.apache.org>
Subject: [accumulo-website] branch master updated: Switch from numbers to
 ids for links
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Message-ID: <150957317064.27530.9121801002460284765@gitbox.apache.org>
From: mwalch@apache.org
Auto-Submitted: auto-generated
archived-at: Wed, 01 Nov 2017 21:53:01 -0000

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 d8338cc  Switch from numbers to ids for links
d8338cc is described below

commit d8338cc96c5a0eec50d3895cbef719d15fc5c8d9
Author: Mike Walch <mwalch@apache.org>
AuthorDate: Wed Nov 1 17:52:21 2017 -0400

    Switch from numbers to ids for links
---
 pages/get_involved.md | 41 +++++++++++++++++++++--------------------
 1 file changed, 21 insertions(+), 20 deletions(-)

diff --git a/pages/get_involved.md b/pages/get_involved.md
index 94d1b8f..96415ef 100644
--- a/pages/get_involved.md
+++ b/pages/get_involved.md
@@ -28,24 +28,24 @@ the community. The project team and the broader community will
 therefore welcome and encourage participation, and attempt to make it 
 as easy as possible for people to get involved.
 
-Want to get started now? Check out [open issues labeled for "newbies"][1]. If you need help, use the mailing list information below to reach out. If the issue you choose deals with code, you should read the developer's guide section.
+Want to get started now? Check out [open issues labeled for "newbies"][newbie]. If you need help, use the mailing list information below to reach out. If the issue you choose deals with code, you should read the developer's guide section.
 
 ## Mailing lists and chat
 
 Your first engagement with the project should be to subscribe to our
-[mailing lists][2].  Apache Accumulo developers and community members
+[mailing lists][mlist].  Apache Accumulo developers and community members
 hang out in the #accumulo channel on irc.freenode.net.
 
 ## Contributor Guide
 
-See the [contributor guide][4] for recommended practices in interacting with our source code.
-Take a look at [Accumulo's Ohloh page][5] for an analysis of the code base.
+See the [contributor guide][contrib] for recommended practices in interacting with our source code.
+Take a look at [Accumulo's OpenHub page][openhub] for an analysis of the code base.
 
 ## Conferences and Meetups
 
-* [Accumulo Summit](http://accumulosummit.com)
-* [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)
+* [Accumulo Summit][summit]
+* [Accumulo Users Group - DC VA MD][meetup-dc]
+* Look for [Accumulo Meetups in your area][meetup]
 
 ## Decision Making
 
@@ -63,7 +63,7 @@ Most of the time we work with the consensus building techniques documented below
 
 ### Lazy Consensus
 
-[Lazy consensus][6] is the first, and possibly the most important, consensus building 
+[Lazy consensus][lazy] 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.
 
@@ -72,24 +72,25 @@ 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][7] amongst the community.
+[building consensus][consensus] amongst the community.
 
 Once there is a consensus, people can proceed with the work under the [lazy 
-consensus][8] model.
+consensus][lazy] model.
 
 ### Voting
 
 Occasionally a "feel" for consensus is not enough. Sometimes we need to 
-have a measurable consensus. For example, when [voting][9] in new committers or 
+have a measurable consensus. For example, when [voting] in new committers or
 to approve a release. 
 
-[1]: https://s.apache.org/newbie_accumulo_tickets
-[2]: {{ site.baseurl }}/mailing_list
-[3]: https://www.meetup.com/find/?keywords=accumulo
-[4]: {{ site.baseurl }}/contributor/
-[5]: https://www.ohloh.net/p/accumulo
-[6]: {{ site.baseurl }}/contributor/lazyConsensus
-[7]: {{ site.baseurl }}/contributor/consensusBuilding
-[8]: {{ site.baseurl }}/contributor/lazyConsensus
-[9]: {{ site.baseurl }}/contributor/voting
+[newbie]: https://s.apache.org/newbie_accumulo_tickets
+[mlist]: {{ site.baseurl }}/mailing_list
+[summit]: http://accumulosummit.com
+[meetup-dc]: https://www.meetup.com/Accumulo-Users-DC/
+[meetup]: https://www.meetup.com/find/?keywords=accumulo
+[contrib]: {{ site.baseurl }}/contributor/
+[openhub]: https://www.openhub.net/p/accumulo
+[lazy]: {{ site.baseurl }}/contributor/lazyConsensus
+[consensus]: {{ site.baseurl }}/contributor/consensusBuilding
+[voting]: {{ site.baseurl }}/contributor/voting
 

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