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 739C4200D3D for ; Mon, 13 Nov 2017 19:54:16 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 71F4A160BF3; Mon, 13 Nov 2017 18:54:16 +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 B94C3160BF0 for ; Mon, 13 Nov 2017 19:54:15 +0100 (CET) Received: (qmail 8080 invoked by uid 500); 13 Nov 2017 18:54:15 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 8069 invoked by uid 99); 13 Nov 2017 18:54:14 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2017 18:54:14 +0000 From: GitBox To: notifications@accumulo.apache.org Subject: [GitHub] mikewalch commented on a change in pull request #37: Accumulo 4714 Create landing page for new developers Message-ID: <151059925435.18464.18100608131402737092.gitbox@gitbox.apache.org> archived-at: Mon, 13 Nov 2017 18:54:16 -0000 mikewalch commented on a change in pull request #37: Accumulo 4714 Create landing page for new developers URL: https://github.com/apache/accumulo-website/pull/37#discussion_r150631263 ########## File path: pages/how-to-contribute.md ########## @@ -0,0 +1,149 @@ +--- +title: How To Contribute +permalink: /how-to-contribute/ +redirect_from: /contributor/ +--- + +Contributions are welcome to all Apache Accumulo repositories. While most contributions are code, +there are other ways to contribute to Accumulo: + +* answer questions on mailing lists +* review pull requests +* verify and test new releases +* update the Accumulo website and documentation + +Contributions are reviewed (via GitHub pull requests) by +the community before being merged by a committer. + +This document provides basic instructions for contributing to Accumulo. If you are looking for more information, check out the more comprehensive [contributor guide](/contributors-guide/). + +## Issues + +Any contribution should have a corresponding issue. Accumulo uses [JIRA] for issue tracking. Before creating an issue, +you will need to create an [Apache JIRA account][jira-signup]. If you need help finding an issue to work on, check out +the [open issues labeled for newbies][newbie-issues] or [contact us][contact]. + +## Repositories + +Contributions can be made to the following repositories. While the general contribution workflow is +described below, repositories have special instructions in their `CONTRIBUTING.md` file which can be +viewed by clicking on the `C` in the Links column below. + +| Repository | Links | Description +| ------------------------------- | -------- | ----------- +| [Accumulo][a] | [C][ac] | Core Project +| [Accumulo Website][w] | [C][wc] | Source for this website +| [Accumulo Examples][e] | [C][ec] | Accumulo example code +| [Accumulo Testing][t] | [C][tc] | Accumulo test suites such as continuous ingest and random walk +| [Accumulo Docker][d] | [C][dc] | Source for Accumulo Docker image +| [Accumulo Wikisearch][s] | [C][sc] | Accumulo example application that indexes and queries Wikipedia data + +## Contribution workflow + +1. Create an [Apache JIRA account][jira-signup] (for issue tracking) and [GitHub account][github-join] (for pull requests). +1. Find an [issue][newbie-issues] to work on or create one that describes the work that you want to do. +1. [Fork] and [clone] the GitHub repository that you want to contribute to. +1. Create a branch in the local clone of your fork. +``` + git checkout -b accumulo-4321 +``` +1. Do work and commit to your branch. You can reference [this link][messages] for a guide on +to write good commit log messages in git. +1. Ensure you works satisfies the guidelines laid out in the `CONTRIBUTING.md` file. +1. If needed, squash to the minimum number of commits. For help on squashing commits, see this tutorial or StackOverflow answer. Review comment: This was my mistake. Below should fix it. ``` [tutorial][squash-tutorial] or [StackOverflow answer][squash-stack]. ``` ``` [squash-tutorial]: http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html [squash-stack]: https://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services