Return-Path: X-Original-To: apmail-accumulo-commits-archive@www.apache.org Delivered-To: apmail-accumulo-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 365DC180D4 for ; Fri, 22 Apr 2016 03:15:44 +0000 (UTC) Received: (qmail 83465 invoked by uid 500); 22 Apr 2016 03:15:44 -0000 Delivered-To: apmail-accumulo-commits-archive@accumulo.apache.org Received: (qmail 83336 invoked by uid 500); 22 Apr 2016 03:15:44 -0000 Mailing-List: contact commits-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list commits@accumulo.apache.org Received: (qmail 82543 invoked by uid 99); 22 Apr 2016 03:15:43 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Apr 2016 03:15:43 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0CC69E0BAC; Fri, 22 Apr 2016 03:15:43 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: ctubbsii@apache.org To: commits@accumulo.apache.org Date: Fri, 22 Apr 2016 03:15:55 -0000 Message-Id: <4190ae0310564177960c587b645c9181@git.apache.org> In-Reply-To: <5892900940b8477ab652cdc03d5e257f@git.apache.org> References: <5892900940b8477ab652cdc03d5e257f@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [14/29] accumulo git commit: Clean up links on website http://git-wip-us.apache.org/repos/asf/accumulo/blob/3e80cf03/get_involved.html ---------------------------------------------------------------------- diff --git a/get_involved.html b/get_involved.html index fd96ea9..e7c72f8 100644 --- a/get_involved.html +++ b/get_involved.html @@ -66,7 +66,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) { - +

@@ -186,7 +186,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) {

Apache Accumulo Professionals

apache / accumulo #accumulo @ freenode -

Apache Accumulo Blog +

Apache Accumulo Blog

@@ -227,18 +227,18 @@ 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”. 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 Meetups

Your first engagement with the project should be to subscribe to our -mailing lists. You can also look for Accumulo Meetups in your area. +mailing lists. You can also look for Accumulo Meetups in your area. Apache Accumulo developers and community members hang out in the #accumulo channel on irc.freenode.net.

Developer’s Guide

See the developer’s guide for recommended practices in interacting with our source code. +

See the developer’s guide for recommended practices in interacting with our source code. Take a look at Accumulo’s Ohloh page for an analysis of the code base.

Community Interaction

@@ -261,7 +261,7 @@ Most of the time we work with the consensus building techniques documented below

Lazy Consensus

Lazy consensus is the first, and possibly the most important, consensus building +

Lazy consensus 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.

@@ -270,31 +270,31 @@ 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 amongst the community.

+building consensus amongst the community.

Once there is a consensus people can proceed with the work under the lazy +

Once there is a consensus people can proceed with the work under the lazy consensus model.

Voting

Occasionally a “feel” for consensus is not enough. Sometimes we need to -have a measurable consensus. For example, when voting in new committers or +have a measurable consensus. For example, when voting in new committers or to approve a release.

- +

Copyright © 2011-2016 The Apache Software Foundation, Licensed under - the Apache License, Version 2.0. + the Apache License, Version 2.0. Apache Accumulo, Accumulo, Apache, the Apache feather logo, and the Apache Accumulo - project logo are trademarks of the Apache Software Foundation.
- Site created with Bootstrap including icons from GLYPHICONS and Font Awesome. + project logo are trademarks of the Apache Software Foundation.
+ Site created with Bootstrap including icons from GLYPHICONS and Font Awesome.

http://git-wip-us.apache.org/repos/asf/accumulo/blob/3e80cf03/git.html ---------------------------------------------------------------------- diff --git a/git.html b/git.html index d5ead06..bcdee7f 100644 --- a/git.html +++ b/git.html @@ -66,7 +66,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) { - +

@@ -186,7 +186,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) {

Apache Accumulo Professionals

apache / accumulo #accumulo @ freenode -

Apache Accumulo Blog +

Apache Accumulo Blog

@@ -200,7 +200,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) {

Git

Git is an open source, distributed version control system +

Git is an open source, distributed version control system which has become very popular in large, complicated software projects due to its efficient handling of multiple, simultaneously and independently developed branches of source code.\

@@ -336,7 +336,7 @@ in the commit message:

ACCUMULO-2428 throw exception when rename fails after compaction

Consider following the git log message format described in - Zach Holman’s talk + Zach Holman’s talk (specifically slides 78-98, beginning at 15:20 into the video). Essentially, leave a short descriptive message in the first line, skip a line, and write more detailed stuff there, if you need to. For example:

@@ -397,7 +397,7 @@ for large features, release candidates or whatever else is deemed useful.

It is always the responsibility of committers to determine that a patch is intended and able to be contributed. From the -new committer’s guide: +new committer’s guide: “Please take care to ensure that patches are original works which have been clearly contributed to the ASF in public. In the case of any doubt (or when a contribution with a more complex history is presented) please consult your @@ -405,7 +405,7 @@ project PMC before committing it.”

Extra diligence may be necessary when code is contributed via a pull request. Committers should verify that the contributor intended to submit the code as a -Contribution under the Apache License. +Contribution under the Apache License. When pulling the code, committers should also verify that the commits pulled match the list of commits sent to the Accumulo dev list in the pull request.

@@ -477,7 +477,7 @@ from, the steps are even easier:

If the branch doesn’t fast-forward merge, you likely want to inform the contributor to update their branch to avoid the conflict resolution and merge -commit. See the Git +commit. See the Git manual for more information on merging. When merging a pull-request, it’s best to not include a signoff on the commit(s) as it changes the final commit ID in the @@ -607,8 +607,8 @@ API.

x.y (where the changes for z' are commits since x.y.z. The steps to take are as follows:

Prepare the release candidate. Release -Guide, Maven +
Prepare the release candidate. Release +Guide, Maven Instructions
Create a branch for the release candidate from the x.y branch, named something like x.y.z'-RCN.

ASF Github

Apache hosted

Mailing lists

It should be noted in the INFRA request that commit messages should be sent to commits@accumulo.apache.org. The subject -can be decided on using the provided +can be decided on using the provided variables.

Examples

- +

http://git-wip-us.apache.org/repos/asf/accumulo/blob/3e80cf03/glossary.html ---------------------------------------------------------------------- diff --git a/glossary.html b/glossary.html index b860b8c..6658c47 100644 --- a/glossary.html +++ b/glossary.html @@ -66,7 +66,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) { - +

- +

http://git-wip-us.apache.org/repos/asf/accumulo/blob/3e80cf03/governance/consensusBuilding.html ---------------------------------------------------------------------- diff --git a/governance/consensusBuilding.html b/governance/consensusBuilding.html index 0088447..8e428b8 100644 --- a/governance/consensusBuilding.html +++ b/governance/consensusBuilding.html @@ -66,7 +66,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) { - +

- +

http://git-wip-us.apache.org/repos/asf/accumulo/blob/3e80cf03/governance/lazyConsensus.html ---------------------------------------------------------------------- diff --git a/governance/lazyConsensus.html b/governance/lazyConsensus.html index 91fae7a..f7cb295 100644 --- a/governance/lazyConsensus.html +++ b/governance/lazyConsensus.html @@ -66,7 +66,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) { - +

@@ -186,7 +186,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) {

Apache Accumulo Professionals

apache / accumulo #accumulo @ freenode -

Apache Accumulo Blog +

Apache Accumulo Blog

@@ -242,7 +242,7 @@ it accounts for different timezones and non-apache commitments.

In this approach the original proposal is not insisting that there is a discussion around their proposal, nor are they requesting that the community explicitly supports their actions. However, this differs from assuming lazy consensus -since it allows space and time to express support or objections and corrections to +since it allows space and time to express support or objections and corrections to the proposal before work begins.

@@ -256,16 +256,16 @@ can take some time to get used to.

- +

http://git-wip-us.apache.org/repos/asf/accumulo/blob/3e80cf03/governance/releasing.html ---------------------------------------------------------------------- diff --git a/governance/releasing.html b/governance/releasing.html index 97a91f6..c36f6d2 100644 --- a/governance/releasing.html +++ b/governance/releasing.html @@ -66,7 +66,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) { - +

@@ -186,7 +186,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) {

Apache Accumulo Professionals

apache / accumulo #accumulo @ freenode -

Apache Accumulo Blog +

Apache Accumulo Blog

@@ -202,7 +202,7 @@ if (ga.hasOwnProperty('loaded') && ga.loaded === true) {

Versioning

Accumulo has adopted Semantic Versioning and follows their rules and guidelines.

Testing

@@ -260,7 +260,7 @@ release, the release should be vetoed via the normal voting process. New major r - Have its version set to note it is RC1. - Be fully built, including a tar.gz of the entire project as well as the documentation.

PGP Signatures of the tarball must be signed to a separate file and made available to the public, along with the tarball and MD5 and SHA512 checksums. The Apache Nexus server fills this role for us via the maven-release-plugin.
PGP Signatures of the tarball must be signed to a separate file and made available to the public, along with the tarball and MD5 and SHA512 checksums. The Apache Nexus server fills this role for us via the maven-release-plugin.
A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release; at least 3 +1 votes from PMC members are required. All checksums and signatures need to be verified before any voter can +1 it. Voting shall last 72 hours.
- Voters SHOULD include with their vote details on the tests from the testing section they have successfully run. If given, said details for each test MUST include: the number of worker nodes in the cluster, the operating system and version, the Hadoop version, and the Zookeeper version. For testing done on a version other than the release candidate that is deemed relevant, include the commit hash. All such gathered testing information will be included in the release notes.

- +

Mailing lists and Meetups

Developer’s Guide

Community Interaction

Lazy Consensus

Voting

Git

Mailing lists

Examples

Silence is consent

Versioning

Testing