Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E2584200BEC for ; Wed, 14 Dec 2016 15:34:11 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E0DCA160B2E; Wed, 14 Dec 2016 14:34:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C9B5F160B19 for ; Wed, 14 Dec 2016 15:34:09 +0100 (CET) Received: (qmail 61949 invoked by uid 500); 14 Dec 2016 14:34:09 -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 61927 invoked by uid 99); 14 Dec 2016 14:34:09 -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; Wed, 14 Dec 2016 14:34:09 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id DA00BE9411; Wed, 14 Dec 2016 14:34:08 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: mwalch@apache.org To: commits@accumulo.apache.org Date: Wed, 14 Dec 2016 14:34:09 -0000 Message-Id: In-Reply-To: <26f702516ef6467d90fec2392e20f654@git.apache.org> References: <26f702516ef6467d90fec2392e20f654@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [02/11] accumulo-website git commit: Several updates to website archived-at: Wed, 14 Dec 2016 14:34:12 -0000 http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/governance/bylaws.md ---------------------------------------------------------------------- diff --git a/governance/bylaws.md b/governance/bylaws.md deleted file mode 100644 index 04707c0..0000000 --- a/governance/bylaws.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -title: Bylaws -redirect_from: /bylaws ---- - -This is version 3 of the bylaws. Community work actively continues on the bylaws, and so key segments of them are subject to change. - -# Introduction - -This document defines the bylaws under which the Apache Accumulo project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc. - -Accumulo is a project of the [Apache Software Foundation][foundation]. The foundation holds the copyright on Apache code including the code in the Accumulo codebase. The [foundation FAQ][foundation-faq] explains the operation and background of the foundation. - -Accumulo is typical of Apache projects in that it operates under a set of principles, known collectively as the Apache Way. If you are new to Apache development, please refer to the [Incubator project][incubator] for more information on how Apache projects operate. Terms used at the ASF are defined in the [ASF glossary][glossary]. - -# Roles and Responsibilities - -Apache projects define a set of roles with associated rights and responsibilities. These roles govern what tasks an individual may perform within the project. The roles are defined in the following sections. - -## Users - -The most important participants in the project are people who use our software. The majority of our contributors start out as users and guide their development efforts from the user's perspective. - -Users contribute to the Apache projects by providing feedback to contributors in the form of bug reports and feature suggestions. As well, users participate in the Apache community by helping other users on mailing lists and user support forums. - -## Contributors - -All of the volunteers who are contributing time, code, documentation, or resources to the Accumulo project are considered contributors. A contributor that makes sustained, welcome contributions to the project may be invited to become a committer, though the exact timing of such invitations depends on many factors. - -## Committers - -The project's committers are responsible for the project's technical management. Committers have write access to the project's code repositories and may cast binding votes on any technical discussion regarding Accumulo. Committer access is by invitation only and must be approved by consensus approval of the active PMC members. Upon acceptance of the invitation to become a committer, it is the accepting member’s responsibility to update their status on the Accumulo web page accordingly. - -A committer is considered emeritus, meaning inactive, by their own declaration or by not reviewing patches or committing patches to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update their status on the web page accordingly. - -An emeritus committer’s commit access may be disabled as part of routine security. Access shall not be removed without notifying the committer, and access shall be maintained if the committer wishes to leave it active. A committer’s commit access shall be reactivated upon the committer’s request to the PMC. - -All Apache committers are required to have a signed [Contributor License Agreement][icla] (CLA) on file with the Apache Software Foundation. Under the terms of the CLA that all committers must sign, a committer's primary responsibility is to ensure that all code committed to Apache Accumulo is licensed appropriately and meets those criteria set forth in the CLA (including both original works and patches committed on behalf of other contributors). There is a [Committer FAQ][committer-faq] which provides more details on the requirements for committers. - -It is the custom of the Accumulo project to also invite each committer to become a member of the Accumulo PMC. - -## Project Management Committee - -The role of the PMC, from a Foundation perspective, is [oversight][pmc-howto]. The main -role of the PMC is not code and not coding, but to ensure that all legal -issues are addressed, that procedure is followed, and that each and every -release is the product of the community as a whole. That is key to our -litigation protection mechanisms. - -Secondly, the role of the PMC is to further the long-term development and -health of the community as a whole, and to ensure that balanced and wide -scale peer review and collaboration does happen. Within the ASF, we worry -about any community which centers around a few individuals who are working -virtually uncontested. We believe that this is detrimental to quality, -stability, and robustness of both code and long term social structures. - -The responsibilities of the PMC include: - -* Deciding what is distributed as products of the Apache Accumulo project. -* Maintaining the project's shared resources, including the code repository, mailing lists, and websites. -* Protecting and ensuring proper use of Apache trademarks by the project and by other parties. -* Speaking on behalf of the project. -* Nominating new PMC members and committers. -* Maintaining these bylaws and other guidelines of the project. - -In particular, PMC members must understand both our project's criteria and ASF criteria for voting on a [release][release-management]. -See the [PMC Guide][pmc-guide] for more information on PMC responsibilities. - -Membership of the PMC is by invitation only and must be approved by a consensus approval of active PMC members. Upon acceptance of the invitation to become a PMC member, it is the accepting member’s responsibility to update their status on the Accumulo web page accordingly. - -A PMC member is considered emeritus, meaning inactive, by their own declaration or by not contributing in any form to the project for over six months. Emeritus members will be recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members retain all voting and commit rights associated with their former designation and can move themselves out of emeritus status by sending an announcement of their return to the developer mailing list. It will be the returning member's responsibility to update their status on the web page accordingly. - -The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (Vice President, Apache Accumulo) and has primary responsibility to the board for the management of the projects within the scope of the Accumulo PMC. The chair reports to the board quarterly on developments within the Accumulo project. - -When the current chair of the PMC resigns, the PMC votes to recommend a new chair using consensus approval, but the decision must be ratified by the Apache board. - -## Release Manager - -The [ASF release process][release-pub] defines the [release manager][release-manager] as an individual responsible for shepherding a new project release. Any committer may serve as a release manager. The release manager for a release is chosen as part of the release plan. - -At a minimum, a release manager is responsible for packaging a release candidate for a vote and signing and publishing an approved release candidate. An Accumulo release manager is also expected to: - -* guide whether changes after feature freeze or code freeze should be included in the release -* ensure that required release testing is being conducted -* track whether the release is on target for its expected release date -* adjust release plan dates to reflect the latest estimates -* determine if a re-plan may be needed and, if so, call a vote -* call votes on release candidates - -[Release guidelines][release-guidelines] and [details on the mechanics of creating an Accumulo release][release-mechanics] are available on the Accumulo project site. - -# Decision Making - -Within the Accumulo project, different types of decisions require different forms of approval. For example, the previous section describes several decisions which require 'consensus approval'. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval. - -## Voting - -Decisions regarding the project are made by votes on the primary project development mailing list: dev@accumulo.apache.org. Where necessary, PMC voting may take place on the private Accumulo PMC mailing list: private@accumulo.apache.org. Votes are clearly indicated by a subject line starting with [VOTE]. A vote message may only pertain to a single item’s approval; multiple items should be separated into multiple messages. Voting is carried out by replying to the vote mail. A vote may take on one of four forms, defined below. - -{: .table } -| Vote | Meaning | -|------|---------| -| +1 | *Yes*, *Agree*, or *The action should be performed*. In general, this vote also indicates a willingness on the behalf of the voter to *make it happen*. | -| +0 | This vote indicates a willingness for the action under consideration to go ahead. The voter, however, will not be able to help. | -| -0 | This vote indicates that the voter does not, in general, agree with the proposed action but is not concerned enough to prevent the action going ahead. | -| -1 | *No*, *Disagree*, or *The action should not be performed*. On issues where consensus is required, this vote counts as a veto. All vetoes must contain an explanation of why the veto is appropriate. Vetoes with no explanation are void. It may also be appropriate for a -1 vote to include an alternative course of action. | - -All participants in the Accumulo project are encouraged to vote. For technical decisions, only the votes of active committers are binding. Non-binding votes are still useful for those with binding votes to understand the perception of an action across the wider Accumulo community. For PMC decisions, only the votes of active PMC members are binding. - -See the [voting page][voting] for more details on the mechanics of voting. - -## Commit Then Review (CTR) - -Voting can also be applied to changes to the Accumulo codebase. Under the Commit Then Review policy, committers can make changes to the codebase without seeking approval beforehand, and the changes are assumed to be approved unless an objection is raised. Only if an objection is raised must a vote take place on the code change. - -For some code changes, committers may wish to get feedback from the community before making the change. It is acceptable for a committer to seek approval before making a change if they so desire. - -## Approvals - -These are the types of approvals that can be sought. Different actions require different types of approvals. - -{: .table } -| Approval Type | Definition | -|-----------------------------------|--------------------------------------------------------------------------------------------------| -| Consensus Approval | A consensus approval vote passes with 3 binding +1 votes and no binding vetoes. | -| Majority Approval | A majority approval vote passes with 3 binding +1 votes and more binding +1 votes than -1 votes. | -| Lazy Approval (or Lazy Consensus) | An action with lazy approval is implicitly allowed unless a -1 vote is received, at which time, depending on the type of action, either majority approval or consensus approval must be obtained. Lazy Approval can be either *stated* or *assumed*, as detailed on the [lazy consensus page][lazy]. | - -## Vetoes - -A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto, but merely that the veto is valid. - -If you disagree with a valid veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, the action that has been vetoed must be reversed in a timely manner. - -## Actions - -This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action. It also specifies the minimum length of time that a vote must remain open, measured in days. In general, votes should not be called at times when it is known that interested members of the project will be unavailable. - -For Code Change actions, a committer may choose to employ assumed or stated Lazy Approval under the [CTR][ctr] policy. Assumed Lazy Approval has no minimum length of time before the change can be made. - -{: .table } -| Action | Description | Approval | Binding Votes | Min. Length (days) | -|---------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------|--------------------| -| Code Change | A change made to a codebase of the project. This includes source code, documentation, website content, etc. | Lazy approval, moving to consensus approval upon veto | Active committers | 1 | -| Release Plan | Defines the timetable and actions for an upcoming release. The plan also nominates a Release Manager. | Lazy approval, moving to majority approval upon veto | Active committers | 3 | -| Release Plan Cancellation | Cancels an active release plan, due to a need to re-plan (e.g., discovery of a major issue). | Majority approval | Active committers | 3 | -| Product Release | Accepts or rejects a release candidate as an official release of the project. | Majority approval | Active PMC members | 3 | -| Adoption of New Codebase | When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue. This also covers the creation of new sub-projects within the project. | Consensus approval | Active PMC members | 7 | -| New Committer | When a new committer is proposed for the project. | Consensus approval | Active PMC members | 3 | -| New PMC Member | When a committer is proposed for the PMC. | Consensus approval | Active PMC members | 3 | -| New PMC Chair | When a new PMC chair is chosen to succeed an outgoing chair. | Consensus approval | Active PMC members | 3 | -| Modifying Bylaws | Modifying this document. | Consensus approval | Active PMC members | 7 | - -No other voting actions are defined; all other actions should presume Lazy Approval (defaulting to Consensus Approval upon veto). If an action is voted on multiple times, or if a different approval type is desired, these bylaws should be amended to include the action. - -For the purposes of the "Adoption of New Codebase" action, the Accumulo codebase is defined as the Accumulo site content, primary project code, and all contributed code ("contribs") as they exist in their respective repositories. Adoption of a new codebase generally refers to the creation of a new contrib repository, but could cover, for example, a rework of the project site, or merging a contrib project into the primary codebase. - -Voting actions for the removal of a committer or PMC member are intentionally not defined. According to ASF rules, [committer status never expires][committer-terms] and [PMC members can only be removed with approval from the ASF Board][pmc-removal]. - -# Release Plans - -The approval of a release plan begins the process of creating a new project release. The process ends when a release candidate is approved. - -An Accumulo release plan consists of at least the following: - -* a version number -* a feature freeze date -* a code freeze date -* a release date -* the choice of a release manager - -After feature freeze, new features should not be accepted for the release. After code freeze, only critical fixes should be accepted for the release. The release manager guides the decision on accepting changes. - -All dates in a plan are estimates, as unforeseen issues may require delays. The release manager may adjust dates as needed. In serious circumstances, the release manager may opt to call a re-plan vote. - -[foundation]: https://www.apache.org/foundation -[foundation-faq]: https://www.apache.org/foundation/faq -[incubator]: https://incubator.apache.org -[glossary]: https://www.apache.org/foundation/glossary -[icla]: https://www.apache.org/licenses/icla.txt -[committer-faq]: https://www.apache.org/dev/committers -[pmc-howto]: https://www.apache.org/foundation/how-it-works.html#pmc -[release-management]: https://www.apache.org/dev/release#management -[pmc-guide]: https://www.apache.org/dev/pmc -[release-pub]: https://www.apache.org/dev/release-publishing -[release-manager]: https://www.apache.org/dev/release-publishing#release_manager -[release-guidelines]: governance/releasing -[release-mechanics]: releasing -[voting]: governance/voting -[ctr]: #commit-then-review-ctr -[committer-terms]: https://www.apache.org/dev/committers#committer-set-term -[pmc-removal]: https://www.apache.org/dev/pmc#pmc-removal -[lazy]: governance/lazyConsensus http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/governance/consensusBuilding.md ---------------------------------------------------------------------- diff --git a/governance/consensusBuilding.md b/governance/consensusBuilding.md deleted file mode 100644 index 799c1e0..0000000 --- a/governance/consensusBuilding.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: 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][1] model. - -[1]: {{ site.baseurl }}/governance/lazyConsensus http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/governance/index.md ---------------------------------------------------------------------- diff --git a/governance/index.md b/governance/index.md deleted file mode 100644 index 10d47d7..0000000 --- a/governance/index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Project Governance ---- - -* [Bylaws](/governance/bylaws) -* [Consensus Building](/governance/consensusBuilding) -* [Lazy Consensus](/governance/lazyConsensus) -* [Releasing](/governance/releasing) -* [Voting](/governance/voting) http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/governance/lazyConsensus.md ---------------------------------------------------------------------- diff --git a/governance/lazyConsensus.md b/governance/lazyConsensus.md deleted file mode 100644 index 02af8c9..0000000 --- a/governance/lazyConsensus.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: 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][1] and corrections to -the proposal before work begins. - -## Silence is consent - -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. - -[1]: {{ site.baseurl }}/governance/consensusBuilding http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/governance/releasing.md ---------------------------------------------------------------------- diff --git a/governance/releasing.md b/governance/releasing.md deleted file mode 100644 index 75462fe..0000000 --- a/governance/releasing.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Release Guide ---- - -## Versioning - -Accumulo has adopted [Semantic Versioning][1] 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. - - 1. 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. - - 1. 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 - - 1. 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][nexus] 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. - -[1]: {{ site.baseurl }}/versioning -[nexus]: https://repository.apache.org http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/governance/voting.md ---------------------------------------------------------------------- diff --git a/governance/voting.md b/governance/voting.md deleted file mode 100644 index 998205b..0000000 --- a/governance/voting.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -title: 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][1]. 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][2]
-[See here for more mail templates][3] - - -[1]: consensusBuilding -[2]: https://www.apache.org/foundation/voting -[3]: https://community.apache.org/newcommitter http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/mailing_list.md ---------------------------------------------------------------------- diff --git a/mailing_list.md b/mailing_list.md deleted file mode 100644 index adf4300..0000000 --- a/mailing_list.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: 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][lists]. - -{: .table } -| Name | Description | Read | Follow | Post | -|-------------------|--------------------------------------------------|------|--------|------| -| **user** | General user questions, help, and announcements | [ Archive][U_A] | [ Subscribe][U_SU] [ Unsubscribe][U_UN] | [ Post][U_P] | -| **dev** | Contributor discussions and development activity | [ Archive][D_A] | [ Subscribe][D_SU] [ Unsubscribe][D_UN] | [ Post][D_P] | -| **commits** | Code changes | [ Archive][C_A] | [ Subscribe][C_SU] [ Unsubscribe][C_UN] | | -| **notifications** | Automated notifications (JIRA, etc.) | [ Archive][N_A] | [ Subscribe][N_SU] [ Unsubscribe][N_UN] | | - -[U_A]: https://lists.apache.org/list.html?user@accumulo.apache.org -{: .btn .btn-primary .btn-xs } -[U_SU]: mailto:user-subscribe@accumulo.apache.org -{: .btn .btn-success .btn-xs } -[U_UN]: mailto:user-unsubscribe@accumulo.apache.org -{: .btn .btn-danger .btn-xs } -[U_P]: mailto:user@accumulo.apache.org -{: .btn .btn-warning .btn-xs } - -[D_A]: https://lists.apache.org/list.html?dev@accumulo.apache.org -{: .btn .btn-primary .btn-xs } -[D_SU]: mailto:dev-subscribe@accumulo.apache.org -{: .btn .btn-success .btn-xs } -[D_UN]: mailto:dev-unsubscribe@accumulo.apache.org -{: .btn .btn-danger .btn-xs } -[D_P]: mailto:dev@accumulo.apache.org -{: .btn .btn-warning .btn-xs } - -[C_A]: https://lists.apache.org/list.html?commits@accumulo.apache.org -{: .btn .btn-primary .btn-xs } -[C_SU]: mailto:commits-subscribe@accumulo.apache.org -{: .btn .btn-success .btn-xs } -[C_UN]: mailto:commits-unsubscribe@accumulo.apache.org -{: .btn .btn-danger .btn-xs } - -[N_A]: https://lists.apache.org/list.html?notifications@accumulo.apache.org -{: .btn .btn-primary .btn-xs } -[N_SU]: mailto:notifications-subscribe@accumulo.apache.org -{: .btn .btn-success .btn-xs } -[N_UN]: mailto:notifications-unsubscribe@accumulo.apache.org -{: .btn .btn-danger .btn-xs } - -[lists]: https://lists.apache.org http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/news.md ---------------------------------------------------------------------- diff --git a/news.md b/news.md deleted file mode 100644 index cc6aa35..0000000 --- a/news.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: News Archive -redirect_from: /blog/ ---- - -
-{% for post in site.posts %} - {% assign post_year = post.date | date: "%Y" %} - {% assign newer_post_year = post.next.date | date: "%Y" %} - {% if post_year != newer_post_year %} -
-

{{ post_year }}

- {% endif %} -
-
{{ post.date | date: "%b %d" }}
-
{{ post.title }}
-
-{% endfor %} -
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/external-docs.md ---------------------------------------------------------------------- diff --git a/pages/external-docs.md b/pages/external-docs.md new file mode 100644 index 0000000..8f891df --- /dev/null +++ b/pages/external-docs.md @@ -0,0 +1,110 @@ +--- +title: External Documentation +permalink: /external-docs/ +redirect_from: /papers +--- + +This page contains links to external documentation that may be useful to Accumulo users. + +## Papers and Presentations + +{: #citationtable .table .table-bordered .table-striped style="width:100%;" } +| Title | Links | Category | Venue | Peer-Reviewed | Awards | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|--------------|----------------------------------------------------------------|---------------|---------------------| +| Prout, Andrew, et al. "Enabling On-Demand Database Computing with MIT SuperCloud Database Management System." IEEE HPEC 2015. | [paper][p01] | Architecture | IEEE HPEC 2015 | Yes | | +| Hubbell, Matthew, et al. "Big Data Strategies for Data Center Infrastructure Management Using a 3D Gaming Platform." IEEE HPEC 2015. | [paper][p02] | Use Cases | IEEE HPEC 2015 | Yes | | +| Gadepally, Vijay, et al. "Computing on Masked Data to improve the Security of Big Data." IEEE HST 2015. | [paper][p03] | Use Cases | IEEE HST 2015 | Yes | | +| Kepner, Jeremy, et al. "Associative Arrays: Unified Mathematics for Spreadsheets, Databases, Matrices, and Graphs." New England Database Summit 2015. | [paper][p04] | Use Cases | New England Database Summit 2015 | Yes | | +| Achieving 100,000,000 database inserts per second using Accumulo and D4M - Kepner et al IEEE HPEC 2014 | [paper][p05] | Performance | IEEE HPEC 2014 | Yes | | +| Evaluating Accumulo Performance for a Scalable Cyber Data Processing Pipeline - Sawyer et al IEEE HPEC 2014 | [paper][p06] | Performance | IEEE HPEC 2014 | Yes | | +| Understanding Query Performance in Accumulo - Sawyer et al IEEE HPEC 2013 | [paper][p07] | Performance | IEEE HPEC 2013 | Yes | | +| Benchmarking Apache Accumulo BigData Distributed Table Store Using Its Continuous Test Suite - Sen et al 2013 IEEE International Congress on Big Data. | [paper][p08] | Performance | IEEE International Congress on Big Data 2013 | Yes | | +| Benchmarking the Apache Accumulo Distributed Key-Value Store - Sen et al 2014 Updated version of the IEEE paper, including edits for clarity and additional results from benchmarking on Amazon EC2. | [paper][p09] | Performance | Online | No | | +| Computing on Masked Data: a High Performance Method for Improving Big Data Veracity - Kepner et al IEEE HPEC 2014 | [paper][p10] | Security | IEEE HPEC 2014 | Yes | | +| D4M 2.0 Schema: A General Purpose High Performance Schema for the Accumulo Database - Kepner et al IEEE HPEC 2013 | [paper][p11] [slides][s11] | Architecture | IEEE HPEC 2013 | Yes | | +| Genetic Sequence Matching Using D4M Big Data Approaches - Dodson et al IEEE HPEC 2014 | | Use Cases | IEEE HPEC 2014 | Yes | Best Paper Finalist | +| Big Data Dimensional Analysis - Gadepally et al IEEE HPEC 2014 | | Use Cases | IEEE HPEC 2014 | Yes | | +| LLSuperCloud: Sharing HPC systems for diverse rapid prototyping - Reuther et al IEEE HPEC 2013 | [paper][p12] [slides][s12] | Architecture | IEEE HPEC 2013 | Yes | | +| Spatio-temporal indexing in non-relational distributed databases - Fox et al 2013 IEEE International Congress on Big Data | [paper][p13] | Use Cases | IEEE International Congress on Big Data 2013 | Yes | | +| Typograph: Multiscale spatial exploration of text documents - Endert, Alex, et al 2013 IEEE International Congress on Big Data | [paper][p14] | Use Cases | IEEE International Congress on Big Data 2013 | Yes | | +| UxV Data to the Cloud via Widgets - Charles et al 18th International Command & Control Research & Technology Symposium 2013 | [paper][p15] | Use Cases | Command & Control Research & Technology Symposium 2013 | Yes | | +| Driving Big Data With Big Compute - Byun et al IEEE HPEC 2012 | [paper][p16] [slides][s16] | Architecture | IEEE HPEC 2012 | Yes | | +| Large Scale Network Situational Awareness Via 3D Gaming Technology - Hubbell et al IEEE HPEC 2012 | [paper][p17] [slides][s17] | Use Cases | IEEE HPEC 2012 | Yes | | +| Rya: a scalable RDF triple store for the clouds - Punnoose et al 1st International Workshop on Cloud Intelligence, ACM, 2012 | [paper][p18] | Architecture | ACM International Workshop on Cloud Intelligence 2012 | Yes | | +| Dynamic distributed dimensional data model (D4M) database and computation system - Kepner et al ICASSP 2012 | [paper][p19] [slides][s19] | Architecture | ICASSP 2012 | Yes | | +| An NSA Big Graph experiment (Technical Report NSA-RD-2013-056002v1) | [slides][s20] | Performance | Technical Report | No | | +| Patil, Swapnil, et al. "YCSB++: benchmarking and performance debugging advanced features in scalable table stores." Proceedings of the 2nd ACM Symposium on Cloud Computing. ACM, 2011. | [paper][p21] [slides][s21] | Performance | ACM Symposium on Cloud Computing 2011 | Yes | | +| Turner, Keith "Apache Accumulo 1.4 & 1.5 Features." February, 2012 | [slides][s22] | Architecture | Meetup | No | | +| Fuchs, Adam "Accumulo: Extensions to Google's Bigtable Design." March, 2012 | [slides][s23] | Architecture | Meetup | No | | +| Miner, Donald "An Introduction to Apache Accumulo - how it works, why it exists, and how it is used." August, 2014 | [slides][s24] | Architecture | Online | No | | + + + +## Slides from Conferences and Meetups + + - [Accumulo Summit Slides](https://www.slideshare.net/AccumuloSummit) + - Strata + Hadoop World Meetup 24 Oct 2012 + - [Accumulo standalone AMI](https://aws.amazon.com/amis/accumulo-standalone-20121019) + - [Large-scale web analytics with Accumulo (and Nutch/Gora, Pig, and Storm)](https://www.slideshare.net/jasontrost/accumulo-at-endgame) + - [Compaction and Splitting in Accumulo](https://www.slideshare.net/hortonworks/compaction-and-splitting-in-apache-accumulo) + +## Blog Posts and Writeups + + - [Codebits Blogs](http://affy.blogspot.com/search?q=accumulo&by-date=true) + - [Implement Word Count in Accumulo](http://affy.blogspot.com/2012/04/implement-word-count-in-accumulo.html) + - [Using Accumulo To Calculate Seven Day Rolling Average](http://affy.blogspot.com/2012/04/using-accumulo-to-calculate-seven-day.html) + - [covert.io blogs](http://www.covert.io/) + - [Accumulo, Nutch, and Gora](http://www.covert.io/post/18414889381/accumulo-nutch-and-gora) + - [Accumulo and Pig](http://www.covert.io/post/18605091231/accumulo-and-pig) + - [Accumulo on MapR](https://www.mapr.com/blog/accumulo-on-mapr) [More Accumulo on MapR](http://blog.stavi.sh/instructions-for-running-accumulo-on-mapr-m5) + - [Accumulo on Ubuntu VirtualBox](https://gist.github.com/1535657) + - [Accumulo on EC2](http://www.accumulodata.com/ec2.html) + +## Books + + - [Apache Accumulo for Developers (Packt Publishing)](https://www.packtpub.com/apache-accumulo-for-developers/book) + - [Accumulo: Application Development, Table Design, and Best Practices (O'Reilly Media)](https://shop.oreilly.com/product/0636920032304.do) + +## Reference + + - [Log-Structured Merge Tree](https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.44.2782&rep=rep1&type=pdf) + - [BigTable](https://research.google.com/archive/bigtable.html) + - [GFS](https://research.google.com/archive/gfs.html) + - [Chubby](https://research.google.com/archive/chubby.html) + - [Dapper](https://research.google.com/pubs/pub36356.html) + - [Bloom Filter](https://en.wikipedia.org/wiki/Bloom_filter) + +[p01]: https://arxiv.org/abs/1506.08506 +[p02]: https://arxiv.org/abs/1506.08505 +[p03]: https://arxiv.org/abs/1504.01287 +[p04]: https://arxiv.org/abs/1501.05709 +[p05]: https://arxiv.org/abs/1406.4923 +[p06]: https://arxiv.org/abs/1407.5661 +[p07]: http://ieee-hpec.org/2013/index_htm_files/28-2868615.pdf +[p08]: https://sqrrl.com/media/Accumulo-Benchmark-10312013-1.pdf +[p09]: accumulo-benchmarking-2.1.pdf +[p10]: https://arxiv.org/abs/1406.5751 +[p11]: http://ieee-hpec.org/2013/index_htm_files/11-Kepner-D4Mschema-IEEE-HPEC.pdf +[s11]: http://ieee-hpec.org/2013/index_htm_files/11_130716-D4Mschema.pdf +[p12]: http://ieee-hpec.org/2013/index_htm_files/26-HPEC13_LLSuperCloud_Reuther_final.pdf +[s12]: http://ieee-hpec.org/2013/index_htm_files/HPEC+2013+Reuther+SuperCloud+final.pdf +[p13]: http://geomesa.github.io/assets/outreach/SpatioTemporalIndexing_IEEEcopyright.pdf +[p14]: https://people.cs.vt.edu/aendert/Alex_Endert/Research_files/Typograph.pdf +[p15]: http://www.dodccrp.org/events/18th_iccrts_2013/post_conference/papers/051.pdf +[p16]: http://www.mit.edu/~kepner/pubs/ByunKepner_2012_BigData_Paper.pdf +[s16]: http://ieee-hpec.org/2012/index_htm_files/42_ID18.pptx +[p17]: http://ieee-hpec.org/2012/index_htm_files/HPEC12_Hubbell.pdf +[s17]: http://ieee-hpec.org/2012/index_htm_files/31_ID20.pptx +[p18]: https://sqrrl.com/media/Rya_CloudI20121.pdf +[p19]: http://www.mit.edu/~kepner/pubs/Kepner_2012_D4M_Paper.pdf +[s19]: http://www.mit.edu/~kepner/pubs/Kepner_2012_D4M_Slides.pdf +[s20]: http://www.pdl.cmu.edu/SDI/2013/slides/big_graph_nsa_rd_2013_56002v1.pdf +[p21]: http://www.pdl.cmu.edu/PDL-FTP/Storage/socc2011.pdf +[s21]: http://www.cercs.gatech.edu/opencirrus/OCsummit11/presentations/patil.pdf +[s22]: https://home.apache.org/~kturner/accumulo14_15.pdf +[s23]: https://home.apache.org/~afuchs/slides/morgan_state_talk.pdf +[s24]: https://www.slideshare.net/DonaldMiner/an-introduction-to-accumulo http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/get_involved.md ---------------------------------------------------------------------- diff --git a/pages/get_involved.md b/pages/get_involved.md new file mode 100644 index 0000000..e8df1e8 --- /dev/null +++ b/pages/get_involved.md @@ -0,0 +1,99 @@ +--- +title: Get Involved +permalink: /get_involved/ +--- + +You don't need to be a software developer to contribute to +Apache Accumulo. To be successful this project +requires a huge range of different skills, levels of involvement and degrees of +technical expertise. So, if you want to get involved in Apache Accumulo, there +is almost certainly a role for you. + +We are looking for people to: + + - provide feedback + - write or update documentation + - help new users + - recommend the project to others + - test the code and report bugs + - fix bugs + - give us feedback on required features + - write and update the software + - create artwork + - translate to different languages + - anything you can see that needs doing + +All of these contributions help to keep a project active and strengthen +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. + +## 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 +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. + +## 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) + +## Community Interaction + +Learn about [building open source communities][6]. + +## Decision Making + +The most important thing about engaging with any Apache project is that everyone +is equal. All people with an opinion are entitled to express that opinion and, where +appropriate, have it considered by the community. + +To some the idea of having to establish consensus in a large and distributed team +sounds inefficient and frustrating. Don't despair though, The Apache Way has a +set of simple processes to ensure things proceed at a good pace. + +In ASF projects we don't like to vote. We reserve that for the few things that need +official approval for legal or process reasons (e.g. a release or a new committer). +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 +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. + +### Consensus Building + +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. + +Once there is a consensus people can proceed with the work under the [lazy +consensus][9] 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 +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]: 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 http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/mailing_list.md ---------------------------------------------------------------------- diff --git a/pages/mailing_list.md b/pages/mailing_list.md new file mode 100644 index 0000000..256d332 --- /dev/null +++ b/pages/mailing_list.md @@ -0,0 +1,50 @@ +--- +title: Mailing Lists +permalink: /mailing_list/ +--- + +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][lists]. + +{: .table } +| Name | Description | Read | Follow | Post | +|-------------------|--------------------------------------------------|------|--------|------| +| **user** | General user questions, help, and announcements | [ Archive][U_A] | [ Subscribe][U_SU] [ Unsubscribe][U_UN] | [ Post][U_P] | +| **dev** | Contributor discussions and development activity | [ Archive][D_A] | [ Subscribe][D_SU] [ Unsubscribe][D_UN] | [ Post][D_P] | +| **commits** | Code changes | [ Archive][C_A] | [ Subscribe][C_SU] [ Unsubscribe][C_UN] | | +| **notifications** | Automated notifications (JIRA, etc.) | [ Archive][N_A] | [ Subscribe][N_SU] [ Unsubscribe][N_UN] | | + +[U_A]: https://lists.apache.org/list.html?user@accumulo.apache.org +{: .btn .btn-primary .btn-xs } +[U_SU]: mailto:user-subscribe@accumulo.apache.org +{: .btn .btn-success .btn-xs } +[U_UN]: mailto:user-unsubscribe@accumulo.apache.org +{: .btn .btn-danger .btn-xs } +[U_P]: mailto:user@accumulo.apache.org +{: .btn .btn-warning .btn-xs } + +[D_A]: https://lists.apache.org/list.html?dev@accumulo.apache.org +{: .btn .btn-primary .btn-xs } +[D_SU]: mailto:dev-subscribe@accumulo.apache.org +{: .btn .btn-success .btn-xs } +[D_UN]: mailto:dev-unsubscribe@accumulo.apache.org +{: .btn .btn-danger .btn-xs } +[D_P]: mailto:dev@accumulo.apache.org +{: .btn .btn-warning .btn-xs } + +[C_A]: https://lists.apache.org/list.html?commits@accumulo.apache.org +{: .btn .btn-primary .btn-xs } +[C_SU]: mailto:commits-subscribe@accumulo.apache.org +{: .btn .btn-success .btn-xs } +[C_UN]: mailto:commits-unsubscribe@accumulo.apache.org +{: .btn .btn-danger .btn-xs } + +[N_A]: https://lists.apache.org/list.html?notifications@accumulo.apache.org +{: .btn .btn-primary .btn-xs } +[N_SU]: mailto:notifications-subscribe@accumulo.apache.org +{: .btn .btn-success .btn-xs } +[N_UN]: mailto:notifications-unsubscribe@accumulo.apache.org +{: .btn .btn-danger .btn-xs } + +[lists]: https://lists.apache.org http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/news.md ---------------------------------------------------------------------- diff --git a/pages/news.md b/pages/news.md new file mode 100644 index 0000000..52a2d6a --- /dev/null +++ b/pages/news.md @@ -0,0 +1,20 @@ +--- +title: News Archive +permalink: /news/ +redirect_from: /blog/ +--- + +
+{% for post in site.posts %} + {% assign post_year = post.date | date: "%Y" %} + {% assign newer_post_year = post.next.date | date: "%Y" %} + {% if post_year != newer_post_year %} +
+

{{ post_year }}

+ {% endif %} +
+
{{ post.date | date: "%b %d" }}
+
{{ post.title }}
+
+{% endfor %} +
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/people.md ---------------------------------------------------------------------- diff --git a/pages/people.md b/pages/people.md new file mode 100644 index 0000000..4eeeac5 --- /dev/null +++ b/pages/people.md @@ -0,0 +1,182 @@ +--- +title: People +skiph1fortitle: true +permalink: /people/ +--- + +## PMC and Committers + +{: .table .table-striped} +| username | name | organization | timezone | +|---------------|-------------------|----------------------------------------|----------| +| acordova | Aaron Cordova | [Koverse][KOVERSE] | | +| afuchs | Adam Fuchs | [sqrrl][SQRRL] | [ET][ET] | +| bhavanki | Bill Havanki | [Cloudera][CLOUDERA] | [ET][ET] | +| billie | Billie Rinaldi | [Hortonworks][HORTONWORKS] | [ET][ET] | +| bimargulies | Benson Margulies | [Basis Technology Corp.][BASISTECH] | [ET][ET] | +| brianloss | Brian Loss | [Praxis Engineering][PRAXIS] | [ET][ET] | +| busbey | Sean Busbey | [Cloudera][CLOUDERA] | [CT][CT] | +| cawaring | Chris Waring | | | +| cjnolet | Corey J. Nolet | [Tetra Concepts LLC][TETRA] | [ET][ET] | +| ctubbsii | Christopher Tubbs | [NSA][NSA] | [ET][ET] | +| dhutchis | Dylan Hutchison | [University of Washington][UW] | [PT][PT] | +| dlmarion | Dave Marion | [Objective Solutions, Inc.][OBJECTIVE] | [ET][ET] | +| drew | Drew Farris | [Booz Allen Hamilton][BOOZ] | [ET][ET] | +| ecn | Eric Newton | [SW Complete Inc.][SWC] | [ET][ET] | +| elserj | Josh Elser | [Hortonworks][HORTONWORKS] | [ET][ET] | +| etcoleman | Ed Coleman | | [ET][ET] | +| jtrost | Jason Trost | [Endgame][ENDGAME] | | +| kturner | Keith Turner | [Peterson Technologies][PETERSON] | [ET][ET] | +| mdrob | Mike Drob | [Cloudera][CLOUDERA] | [ET][ET] | +| medined | David Medinets | | | +| mjwall | Michael Wall | [Objective Solutions, Inc.][OBJECTIVE] | [ET][ET] | +| mmiller | Michael Miller | [Centroid, LLC][CENTROID] | [ET][ET] | +| mwalch | Mike Walch | [Peterson Technologies][PETERSON] | [ET][ET] | +| phrocker | Marc Parisi | [WaveStrike LLC][WAVE] | [ET][ET] | +| rweeks | Russ Weeks | [PHEMI][PHEMI] | [PT][PT] | +| shickey | Sean Hickey | | [PT][PT] | +| ujustgotbilld | William Slacum | [Miner & Kasch][MINERKASCH] | [ET][ET] | +| vikrams | Vikram Srivastava | [Cloudera][CLOUDERA] | [PT][PT] | +| vines | John Vines | [sqrrl][SQRRL] | [ET][ET] | + +## Contributors + +{: .table .table-striped} +| username | name | organization | timezone | +|-------------|---------------------|-------------------------------------------------------------------|-----------------------| +| | Aaron Glahe | [Data Tactics][DATATACT] | [ET][ET] | +| | Adam J Shook | [Datacatessen][DATACATESS] | [ET][ET] | +| | Al Krinker | | [ET][ET] | +| | Alex Moundalexis | [Cloudera][CLOUDERA] | [ET][ET] | +| | Andrew George Wells | [ClearEdgeIT][CLEAREDGE] | [ET][ET] | +| | Arshak Navruzyan | [Argyle Data][ARGYLE] | | +| | Ben Manes | | [PT][PT] | +| | Bob Thorman | [AT&T][ATT] | | +| | Chris Bennight | | | +| | Chris McCubbin | [sqrrl][SQRRL] | [ET][ET] | +| | Christian Rohling | [Endgame][ENDGAME] | [ET][ET] | +| | Damon Brown | [Tetra Concepts LLC][TETRA] | [ET][ET] | +| | Dave Wang | [Cloudera][CLOUDERA] | [PT][PT] | +| | David M. Lyle | | | +| | David Protzman | | | +| | Dennis Patrone | [The Johns Hopkins University Applied Physics Laboratory][JHUAPL] | [ET][ET] | +| dimaspivak | Dima Spivak | [Cloudera][CLOUDERA] | | +| | Ed Kohlwey | [Booz Allen Hamilton][BOOZ] | | +| edwardyoon | Edward Yoon | | | +| | Eugene Cheipesh | | | +| | Gary Singh | [Sabre Engineering][SABRE] | [ET][ET] | +| | Hayden Marchant | | | +| | Hung Pham | [Cloudera][CLOUDERA] | [ET][ET] | +| | Ivan Bella | [Objective Solutions, Inc.][OBJECTIVE] | [ET][ET] | +| | Jacob Meisler | [Booz Allen Hamilton][BOOZ] | [ET][ET] | +| | James Fiori | [Flywheel Data][FLYWHEEL] | [ET][ET] | +| jaredwinick | Jared Winick | [Koverse][KOVERSE] | [MT][MT] | +| | Jason Then | | | +| | Jay Shipper | | | +| jfield | Jeff Field | [Cloudera][CLOUDERA] | [ET][ET] | +| | Jeffrey S. Schwartz | | | +| | Jenna Huston | | [ET][ET] | +| | Jerry He | [IBM][IBM] | [PT][PT] | +| | Jesse Yates | | | +| | Jessica Seastrom | [Cloudera][CLOUDERA] | [ET][ET] | +| | Jim Klucar | [Splyt][SPLYT] | [ET][ET] | +| | Joe Skora | | | +| | John McNamee | | | +| | John Stoneham | | [ET][ET] | +| jmhsieh | Jonathan M. Hsieh | [Cloudera][CLOUDERA] | [PT][PT] | +| | Jonathan Park | [sqrrl][SQRRL] | [ET][ET] | +| | Kevin Faro | [Tetra Concepts LLC][TETRA] | [ET][ET] | +| | Laura Peaslee | [Objective Solutions, Inc.][OBJECTIVE] | [ET][ET] | +| | Luis Tavarez | | [ET][ET] | +| | Luke Brassard | [sqrrl][SQRRL] | [ET][ET] | +| | Mario Pastorelli | [Teralytics AG][TERALYTICS] | [CEST][CEST] | +| | Matt Dailey | | | +| | Matthew Kirkley | | | +| | Max Jordan | | | +| | Michael Allen | [sqrrl][SQRRL] | [ET][ET] | +| | Michael Berman | [sqrrl][SQRRL] | [ET][ET] | +| | Miguel Pereira | [SRA International, Inc][SRA] | [ET][ET] | +| | Mike Fagan | [Arcus Research][ARCUS] | [MT][MT] | +| | Morgan Haskel | | | +| | Nguessan Kouame | | | +| | Oren Falkowitz | [sqrrl][SQRRL] | [ET][ET] | +| | Phil Eberhardt | [sqrrl][SQRRL] | [ET][ET] | +| | Philip Young | | | +| | Pushpinder Heer | [Applied Technical Systems][ATSID] | [PT][PT] | +| | Ravi Mutyala | [Hortonworks][HORTONWORKS] | [CT][CT] | +| | Ryan Fishel | [Cloudera][CLOUDERA] | | +| | Ryan Leary | | | +| | Sapah Shah | | | +| | Scott Kuehn | | | +| | Shawn Walker | | | +| stevel | Steve Loughran | [Hortonworks][HORTONWORKS] | [GMT][GMT]/[BST][BST] | +| supun | Supun Kamburugamuva | | | +| | Takahiko Saito | [Hortonworks][HORTONWORKS] | [PT][PT] | +| | Ted Malaska | [Cloudera][CLOUDERA] | | +| tedyu | Ted Yu | [Hortonworks][HORTONWORKS] | [PT][PT] | +| | Tim Halloran | | | +| | Tim Reardon | | | +| | Travis Pinney | | | +| | Trent Nadeau | [Anthem Engineering LLC][ANTHEMENG] | [ET][ET] | +| | Tristen Georgiou | [PHEMI][PHEMI] | [PT][PT] | +| | Vicky Kak | | | +| | Vincent Russell | | | +| | Volth | | | +| | Wil Selwood | [Satellite Applications Catapult][SACAT] | [GMT][GMT]/[BST][BST] | + +## Organizations + +First off, thanks to our parent organization, the [Apache Software Foundation][ASF] and [all who sponsor][ASF_SPONSORS] them. + +Additionally, we would like to thank the following organizations for resources that they provide: + + - ej-technologies for allowing us to use their [Java profiler][JPROFILER] + - YourKit for allowing us use of their [Java Profiler][YOURKIT] + - Coverity for running [static analysis][COVERITY] + +[ANTHEMENG]: http://www.anthemengineering.com +[ARCUS]: http://www.arcus-research.com +[ARGYLE]: http://www.argyledata.com +[ATSID]: http://www.atsid.com +[ATT]: http://www.att.com +[BASISTECH]: http://www.basistech.com +[BOOZ]: http://www.boozallen.com +[CENTROID]: http://www.centroid-llc.com/ +[CLEAREDGE]: http://clearedgeit.com +[CLOUDERA]: http://www.cloudera.com +[DATATACT]: http://www.data-tactics.com +[DATACATESS]: https://datacatessen.com/ +[ENDGAME]: http://www.endgame.com +[FLYWHEEL]: http://flywheeldata.com +[HORTONWORKS]: http://hortonworks.com +[IBM]: http://www.ibm.com +[JHUAPL]: http://www.jhuapl.edu +[KOVERSE]: http://www.koverse.com +[MINERKASCH]: http://minerkasch.com +[NSA]: http://www.nsa.gov +[OBJECTIVE]: http://www.objectivesolutions.com +[PETERSON]: http://www.ptech-llc.com +[PHEMI]: http://www.phemi.com +[PRAXIS]: http://www.praxiseng.com +[SABRE]: http://www.sabre-eng.com +[SACAT]: https://sa.catapult.org.uk +[SPLYT]: http://www.splyt.com +[SQRRL]: http://sqrrl.com +[SRA]: http://sra.com +[SWC]: http://swcomplete.com +[TERALYTICS]: http://www.teralytics.net/ +[TETRA]: http://www.tetraconcepts.com +[UW]: http://www.uw.edu +[WAVE]: http://www.wavestrike.com/ +[BST]: http://www.timeanddate.com/time/zones/bst +[CT]: http://www.timeanddate.com/time/zones/ct +[ET]: http://www.timeanddate.com/time/zones/et +[GMT]: http://www.timeanddate.com/time/zones/gmt +[MT]: http://www.timeanddate.com/time/zones/mt +[PT]: http://www.timeanddate.com/time/zones/pt +[CEST]: http://www.timeanddate.com/time/zones/cest +[ASF]: https://www.apache.org +[ASF_SPONSORS]: https://www.apache.org/foundation/sponsorship +[JPROFILER]: https://www.ej-technologies.com/products/jprofiler/overview.html +[YOURKIT]: https://www.yourkit.com/java/profiler/features/ +[COVERITY]: https://scan.coverity.com/projects/accumulo http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/related-projects.md ---------------------------------------------------------------------- diff --git a/pages/related-projects.md b/pages/related-projects.md new file mode 100644 index 0000000..2f592d1 --- /dev/null +++ b/pages/related-projects.md @@ -0,0 +1,92 @@ +--- +title: Related Projects +permalink: /related-projects/ +redirect_from: /projects +--- + +The Apache Accumulo community is happy to promote and encourage use of Accumulo in ways that are novel and reusable +by other users within the community. As such, we're happy to curate a list of projects related to Accumulo to give +them visibility to a larger audience. To have you project listed here, send a request to the +[developer's mailing list](mailto:dev@accumulo.apache.org) + +## Open source projects using Accumulo + +#### Apache Fluo + +[Fluo](https://fluo.apache.org) builds on Accumulo and enables low latency, continuous incremental processing of big data. + +#### Apache Gora + +[Gora](https://gora.apache.org/) open source framework provides an in-memory data model and persistence for big data. Accumulo's continuous ingest test suite was adapted to Gora and called [Goraci](http://gora.apache.org/current/index.html#goraci-integration-testsing-suite). + +#### Apache Hive + +[Hive](https://hive.apache.org/) data warehouse software facilitates reading, writing, and managing large datasets residing in distributed storage using SQL. +Hive has the ability to read and write data in Accumulo using the [AccumuloStorageHandler](https://cwiki.apache.org/confluence/display/Hive/AccumuloIntegration). + +#### Apache Pig + +[Pig](http://pig.apache.org/) is a platform for analyzing large data sets that consists of a high-level language for expressing data analysis programs, coupled with infrastructure for evaluating these programs. Pig has the ability to read and write data in Accumulo using [AccumuloStorage](http://pig.apache.org/docs/r0.16.0/func.html#AccumuloStorage). + +#### Apache Rya + +[Rya](http://rya.apache.org/) is a scalable RDF triple store built on top of a columnar index store. + +#### Geomesa + +[Geomesa](http://www.geomesa.org/) is an open-source, distributed, spatio-temporal database built on a number of distributed cloud data storage systems, including Accumulo, HBase, Cassandra, and Kafka. + +#### Geowave + +[Geowave](https://ngageoint.github.io/geowave/) is a library for storage, index, and search of multi-dimensional data on top of a sorted key-value datastore. + +#### Graphulo + +Graphulo is a Java library for Apache Accumulo which delivers server-side sparse matrix math primitives that +enable higher-level graph algorithms and analytics. [Code](https://github.com/Accla/graphulo). + +#### Presto + +[Presto](https://prestodb.io/) is an open source distributed SQL query engine for running interactive analytic queries against data sources of all sizes, ranging from gigabytes to petabytes. Through the use of the new Accumulo connector for Presto, users are able to execute traditional SQL queries against new and existing tables in Accumulo. For more information, see the [Accumulo Connector](https://prestodb.io/docs/current/connector/accumulo.html) documentation. + +#### Timely + +[Timely](https://nationalsecurityagency.github.io/timely/) : A secure time series database based on Accumulo and Grafana. + +#### Uno and Muchos + +[Uno](https://github.com/astralway/uno) and [Muchos](https://github.com/astralway/muchos) provide automation for quickly setting up Accumulo instances for testing. These project were created to enable Fluo testing, but can be used to setup just Accumulo. + +## User-Created Applications + +#### Trendulo + +[Trendulo](http://trendulo.com/) is Twitter trend analysis using Apache Accumulo. The [source code](https://github.com/jaredwinick/Trendulo) is publicly available. + +#### Wikisearch + +The [Wikisearch project]({{ site.baseurl }}/example/wikisearch) is a rough example of generalized secondary indexing, both ingest +and search, built on top of Apache Accumulo. This write contains more information on the project as well as some +general performance numbers of the project. + +#### Node.js, RabbitMQ, and Accumulo + +A [simple example](https://github.com/joshelser/node-accumulo) using Node.js to interact with Accumulo using RabbitMQ . + +#### ProxyInstance + +ProxyInstance is a Java Instance implementation of the Accumulo Instance interface that communicates with +an Accumulo cluster via Accumulo's Apache Thrift proxy server. [Documentation](https://jhuapl.github.io/accumulo-proxy-instance/proxy_instance_user_manual) and +[code](https://github.com/JHUAPL/accumulo-proxy-instance) are available. + +#### AccumuloGraph + +ProxyInstance is an implementation of the TinkerPop Blueprints 2.6 API using +Apache Accumulo as the backend. +[Documentation](https://jhuapl.github.io/AccumuloGraph/) and +[code](https://github.com/JHUAPL/AccumuloGraph) are available. + +## Github + +[Github](https://github.com/search?q=accumulo&type=Repositories) also contains many projects that use/reference Accumulo +in some way, shape or form. http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/pages/release.md ---------------------------------------------------------------------- diff --git a/pages/release.md b/pages/release.md index f8c92ae..6c8dda6 100644 --- a/pages/release.md +++ b/pages/release.md @@ -1,9 +1,9 @@ --- title: Release Archive -permalink: "/release/" +permalink: /release/ redirect_from: - - "/release_notes/" - - "/release_notes.html" + - /release_notes/ + - /release_notes.html ---
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/a71056ca/papers.md ---------------------------------------------------------------------- diff --git a/papers.md b/papers.md deleted file mode 100644 index b51569f..0000000 --- a/papers.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Related Links -redirect_to: "{{ site.baseurl }}/papers/" ---- - -This page redirects to canonical location for papers