In-Reply-To: <26f702516ef6467d90fec2392e20f654@git.apache.org> References: <26f702516ef6467d90fec2392e20f654@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [06/11] accumulo-website git commit: Jekyll build from master:a71056c archived-at: Wed, 14 Dec 2016 14:34:12 -0000 http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/governance/consensusBuilding.html ---------------------------------------------------------------------- diff --git a/governance/consensusBuilding.html b/governance/consensusBuilding.html index cb0408f..da45a65 100644 --- a/governance/consensusBuilding.html +++ b/governance/consensusBuilding.html @@ -1,212 +1,10 @@ - - - + - - - - - - - -Consensus Building - - - - - - - - - - - - -

- - -

- -

Consensus Building

- -

In some cases there is no obvious path to take, or you might be a new community, -or a new member of an existing community. In these cases people will often -need to build consensus by making proposals and eliciting responses.

- -

We want to avoid unnecessary discussion and the creation of significant -amounts of unnecessary mail that everyone in the community needs to read. -That is not to say that we want to avoid constructive discussion. This is -the lifeblood of a successful project. However, many ASF projects adopt a -shorthand notation for showing support, or otherwise, for a proposal.

- -

Expressing support (or otherwise)

- -

The notation used is “+1”, “-1” and “0”. It’s also common to see “+0” and “-0”.

- -

So, what do these notations mean?

- -

+1 means “I agree with this and will help make it happen”
+0 means “I agree with this but probably won’t make it happen, so my -opinion is not that important”
-0 means “I don’t agree with this, but I’m offering no alternative so -my opinion is not that important”
-1 means “I don’t agree and I am offering an alternative that I am able -to help implement”

- -

Many people will use fractions to indicate the strength of their feelings, - e.g. “+0.5”. Some will even indicate this is a “no brainer” with something -like “+1000”.

- -

The important thing is that this is not an exact science. It’s just a shorthand -way of communicating strength of feeling.

- -

Consensus Building is Not Voting

- -

The confusing thing about this notation is that it is the same notation -used in a formal vote. Knowing when something is a vote and when it is a -preference is important. It’s easy to tell though, if the subject does not have -“[Vote]” at the start then it’s just an opinion. We try not to call votes, -consensus building is much more inclusive.

- -

The reasons for this notation being common is -that when someone wants to summarise a discussion thread they can mentally -add up the strength of feeling of the community and decide if there is consensus -or not.

- -

Once there is a clear consensus members of the community can proceed with -the work under the lazy consensus model.

- - -

- - - - - -

- +Redirecting… + + +

Redirecting…

+Click here if you are not redirected. + http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/governance/index.html ---------------------------------------------------------------------- diff --git a/governance/index.html b/governance/index.html deleted file mode 100644 index 4d3a055..0000000 --- a/governance/index.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - - - - - - - - -Project Governance - - - - - - - - - - - - -

- - -

- -

Project Governance

- -

- - - - - -

- - http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/governance/lazyConsensus.html ---------------------------------------------------------------------- diff --git a/governance/lazyConsensus.html b/governance/lazyConsensus.html index 283f91b..7ac2d44 100644 --- a/governance/lazyConsensus.html +++ b/governance/lazyConsensus.html @@ -1,215 +1,10 @@ - - - + - - - - - - - -Lazy Consensus - - - - - - - - - - - - -

- - -

- -

Lazy Consensus

- -

The concept of “Lazy Consensus” is very important in our project. Lazy -Consensus means that when you are convinced that you know what the community -would like to see happen you can simply assume that you already have consensus -and get on with the work. You don’t have to insist people discuss and/or -approve your plan, and you certainly don’t need to call a vote to get approval. -You just assume you have the community’s support unless someone says otherwise.

- -

We have a time machine (Subversion), this means that as long as you commit -(or submit patches) early and often the community has plenty of opportunity -to indicate disapproval. If you believe the community will support your action -you can operate on lazy consensus as long as you are prepared to roll back -any work should a valid objection is raised.

- -

Avoiding Unnecessary Discussion

- -

The key thing about lazy consensus is that it’s easier for people to agree, -by doing nothing, than it is to object, which requires an -alternative to be proposed. This has two effects, firstly people are less -likely to object for the sake of it and secondly it cuts down on the amount -of unnecessary mail traffic and discussion.

- -

Lazy consensus means we can avoid waiting for a community based decision -before proceeding. However, it does require everyone who cares for the health -of the project to watch what is happening, as it is happening. Objecting too -far down the road will cause upset, but objecting (or asking for clarification -of intent) early is likely to be greeted with relief that someone is watching -and cares.

- -

Stating Lazy Consensus

- -

Sometimes a member of the community will believe a specific action is the correct -one for the community but are not sure enough to proceed with the work under the -lazy consensus model. In these circumstances they can state Lazy Consensus is in -operation.

- -

What this means is that they make a proposal and state that they will start -implementing it in 72 hours unless someone objects. 72 hours is chosen because -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 -the proposal before work begins.

- - - -

People may choose to indicate their support for the actions taken with a +1 -mail - quick and easy to read and reassuring for the implementer. However, -remember, in a lazy consensus world silence is the equivalent to support. This -can take some time to get used to.

- - -

- - - - - -

- +Redirecting… + + +

Redirecting…

+Click here if you are not redirected. + http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/governance/releasing.html ---------------------------------------------------------------------- diff --git a/governance/releasing.html b/governance/releasing.html index c849b94..8ebc7ad 100644 --- a/governance/releasing.html +++ b/governance/releasing.html @@ -1,235 +1,10 @@ - - - + - - - - - - - -Release Guide - - - - - - - - - - - - -

- - -

- -

Release Guide

- -

Versioning

- -

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

- -

Testing

- -

Testing for an Accumulo release includes a few steps that a developer may take without a Hadoop cluster and several that require a working cluster. For minor releases, -the tests which run on a Hadoop cluster are recommended to be completed but are not required. Running even a reduced set of tests against real hardware is always encouraged -even if the full test suite (in breadth of nodes or duration) is not executed. If PMC members do not believe adequate testing was performed for the sake of making the proposed -release, the release should be vetoed via the normal voting process. New major releases are expected to run a full test suite.

- -

Stand alone

The following steps can be taken without having an underlying cluster. They SHOULD be handled with each Hadoop profile available for a given release version. To activate an alternative profile specify e.g. “-Dhadoop.profile=2” for the Hadoop 2 profile on the Maven commandline. Some older versions of Accumulo referred to Hadoop profiles diferently; see the README that came with said versions for details on building against different Hadoop versions.

- -

All JUnit tests must pass. This should be a requirement of any patch so it should never be an issue of the codebase. - - Use “mvn package” to run against the default profile of a particular release - - Use “mvn -Dhadoop.profile=2 package” to test against the Hadoop 2 profile on e.g. 1.4 or 1.5 - - Use “mvn -Dhadoop.profile=1 package” to test against the Hadoop 1 profile on e.g. 1.6 or later -
- Analyze output of static analysis tools like Findbugs and PMD.
- For versions 1.6 and later, all functional tests must pass via the Maven failsafe plugin. -
  - Use “mvn verify” to run against the default profile of a particular release
  - Use “mvn -Dhadoop.profile=1 verify” to run the functional tests against the Hadoop 1 profile
  -
-

- -

Cluster based

The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper. The cluster MAY have any number of worker nodes; it can even be a single node in pseudo-distributed mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base will be exercised. For the purposes of release testing, you should note the number of nodes and versions used. See the Releasing section for more details.

- -

For versions prior to 1.6, all functional tests must complete successfully. - - See $ACCUMULO_HOME/test/system/auto/README for details on running the functional tests. -
- Two 24-hour periods of the LongClean module of the RandomWalk test need to be run successfully. One of them must use agitation and the other should not. -
  - See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean module.
  -
- Two 24-hour periods of the continuous ingest test must be validated successfully. One test period must use agitation and the other should not. -
  - See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying the continuous ingest test.
  -
- Two 72-hour periods of continuous ingest must run. One test period must use agitation and the other should not. No validation is necessary but the cluster should be checked to ensure it is still functional.
-

- -

Releasing

- -

Tag the tested branch. It should: - - 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.
- 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.
  -
- Upon successful vote, the new releases can be retagged to remove the RC status and released on the Accumulo webpage.
- If at any time the tag needs to be remade due to any sort of error, it should be incremented to the next release candidate number.
-

- - -

- - - - - -

- +Redirecting… + + +

Redirecting…

+Click here if you are not redirected. + http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/governance/voting.html ---------------------------------------------------------------------- diff --git a/governance/voting.html b/governance/voting.html index 4f99f6d..ac2cbd7 100644 --- a/governance/voting.html +++ b/governance/voting.html @@ -1,252 +1,10 @@ - - - + - - - - - - - -Voting - - - - - - - - - - - - -

- - -

- -

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 to approve a -release.

- -

Preparing for a Vote

- -

Before calling a vote it is important to ensure that the community is given time to -discuss the upcoming vote. This will be done by posting an email to the list -indicating the intention to call a vote and the options available. By the time a -vote is called there should already be consensus in the community. The vote -itself is, normally, a formality.

- -

Calling a Vote

- -

Once it is time to call the vote a mail is posted with a subject starting with -“[VOTE]”. This enables the community members to ensure they do not miss an important -vote thread. It also indicates that this is not consensus building but a formal -vote. The initiator is responsible for the vote. That means also to count the votes -and present the results. Everyone has 1 vote.

- -

Casting Your Vote

- -

The notation used in voting is:

- -

+1 (means I vote positive) - You can say why you vote positive but it’s not a must-have.

- -

0 (means I have no strong opinion, aka abstention)

- -

-1 (means I vote negative because of the following reason) - Yes, you must support your objection and provide an alternative course of action - that you are willing and able to implement (where appropriate).

- -

Example for a vote mail:

- -

Address: private@
-Subject: [VOTE] John Doe should become a regular committer
-
-Text:
-"I would like to propose to vote in John Doe as committer. John has showed in
-the last months that he has the skills and oversight for improving things (think
-about the last UI change of the "Find" dialog)."
-
-+1 (means I vote for John)
- 0 (means I'm not for John but also not against to vote him in)
--1 (means I'm not for John because of the following reason(s):
-
-Voting time frame is finished 72 hours from now until June 30, 12:00 PM UTC.
-

- -

Example for a reply mail:

- -

Text:
-+1
-
-I like his work and want him to stay and to go on with his good improvements.
-

- -

Example for a result mail:

- -

Subject: [VOTE][RESULTS] John Doe should become a regular committer
-
-Text:
-Vote started Thu, Jun 27, 2011 at 12:00 PM UTC, voting is now closed.
-
-Voting results:
-
---- Numbers ---
-
-+1: 6
- 0: 0
--1: 0
-
---- Details ---
-
-+1 John
-+1 Jane
-+1 David
-+1 Dolores
-+1 Carl
-+1 Chris
-

- -

See here for more information
-See here for more mail templates

- - -

- - - - - -

- +Redirecting… + + +

Redirecting…

+Click here if you are not redirected. + http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/index.html ---------------------------------------------------------------------- diff --git a/index.html b/index.html index a08b35f..5a33f31 100644 --- a/index.html +++ b/index.html @@ -97,8 +97,8 @@

Javadocs (1.8)

Examples (1.8)

Features

Papers & Presentations

Glossary

External Docs

Mailing Lists

- -

All Accumulo mailing lists are in the accumulo.apache.org domain. Please note -that search providers linked on this page are not part of the official Apache -mailing list archives.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Name	Description	Read	Follow	Post
user	General user questions, help, and announcements	Archive	Subscribe Unsubscribe	Post
dev	Contributor discussions and development activity	Archive	Subscribe Unsubscribe	Post
commits	Code changes	Archive	Subscribe Unsubscribe
notifications	Automated notifications (JIRA, etc.)	Archive	Subscribe Unsubscribe

- - -

- - - - - -

- - http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/fd45f7a2/mailing_list/index.html ---------------------------------------------------------------------- diff --git a/mailing_list/index.html b/mailing_list/index.html new file mode 100644 index 0000000..6a95be1 --- /dev/null +++ b/mailing_list/index.html @@ -0,0 +1,208 @@ + + + + + + + + + + + + +Mailing Lists + + + + + + + + + + + + +

+ + +

+ +

Mailing Lists

+ +

All Accumulo mailing lists are in the accumulo.apache.org domain. Please note +that search providers linked on this page are not part of the official Apache +mailing list archives.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Name	Description	Read	Follow	Post
user	General user questions, help, and announcements	Archive	Subscribe Unsubscribe	Post
dev	Contributor discussions and development activity	Archive	Subscribe Unsubscribe	Post
commits	Code changes	Archive	Subscribe Unsubscribe
notifications	Automated notifications (JIRA, etc.)	Archive	Subscribe Unsubscribe

+ + +

+ + + + + +

+ +

Consensus Building

Expressing support (or otherwise)

Consensus Building is Not Voting

Redirecting…

Project Governance

Lazy Consensus

Avoiding Unnecessary Discussion

Stating Lazy Consensus

Silence is consent

Redirecting…

Release Guide

Versioning

Testing

Stand alone

Cluster based

Releasing

Redirecting…

Voting

Preparing for a Vote

Calling a Vote

Casting Your Vote

Example for a vote mail:

Example for a reply mail:

Example for a result mail:

Redirecting…

Mailing Lists

Mailing Lists