This is an automated email from the ASF dual-hosted git repository.
poorejc pushed a commit to branch FLAGON-344
in repository https://gitbox.apache.org/repos/asf/incubator-flagon.git
The following commit(s) were added to refs/heads/FLAGON-344 by this push:
new 1906b1e [FLAGON-353] updated contribution.md to reflect name change
to Flagon
1906b1e is described below
commit 1906b1e1912dadfa210b6702e5b73de542131182
Author: poorejc <[email protected]>
AuthorDate: Sun Apr 7 22:18:16 2019 -0400
[FLAGON-353] updated contribution.md to reflect name change to Flagon
---
site/_docs/contributing.md | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/site/_docs/contributing.md b/site/_docs/contributing.md
index 581565b..6bed431 100644
--- a/site/_docs/contributing.md
+++ b/site/_docs/contributing.md
@@ -1,10 +1,10 @@
---
title: Contributing
-component: senssoft
+component: flagon
permalink: /docs/contributing/
---
-First, thank you for contributing to Apache SensSoft!
+First, thank you for contributing to Apache Flagon!
There are certain procedures that must be followed for all contributions.
These procedures are necessary to allow us to allocate resources for reviewing
and testing your contribution, as well as to communicate effectively with you
during the review process.
@@ -14,14 +14,16 @@ To report a bug or other issue, simply create an issue in
JIRA, as described in
#### 1. Create an issue in JIRA
- All changes to Apache SensSoft must have a corresponding issue in
[JIRA](https://issues.apache.org/jira/browse/SENSSOFT) so the change can be
properly tracked. If you do not already have an account on JIRA, you will need
to create one before creating your new issue.
+ All changes to Apache Flagon must have a corresponding issue in
[JIRA](https://issues.apache.org/jira/browse/FLAGON) so the change can be
properly tracked. If you do not already have an account on JIRA, you will need
to create one before creating your new issue.
#### 2. Make and test your changes locally
- The Apache SensSoft source code is maintained in [several git
repositories](https://git-wip-us.apache.org/repos/asf?s=senssoft) hosted by
Apache. These repositories are mirrored and more easily available [on
GitHub](https://github.com/apache?q=senssoft). To make your changes, fork the
appropriate GitHub repository and make commits to a topic branch in your fork.
Commits should be made in logical units and must reference the JIRA issue
number:
+ The Apache Flagon source code is maintained in [several git
repositories](https://gitbox.apache.org/repos/asf?s=flagon) hosted by Apache.
These repositories are mirrored and more easily available [on
GitHub](https://github.com/apache?q=flagon). To make your changes, fork the
appropriate GitHub repository and make commits to a topic branch in your fork.
Commits should be made in logical units and must reference the JIRA issue
number:
```shell
- git commit -m "#SENSSOFT-123: High-level message describing the changes."
+ git commit -S -m "[FLAGON-123] High-level message describing the changes."
```
+ Note that your commits should be verifiable; each commit should be verified
with a PGP certificate. The easiest way to do this is to create a PGP signature
with [GnuPG](https://www.gnupg.org/), register it with you GitHub account and
[configure git](https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work) to
use this signature when committing.
+
Avoid commits which cover multiple, distinct goals that could (and should)
be handled separately. If you do not already have an account on JIRA, you will
need to create one to claim an issue, discuss development, or report results.
#### 3. Submit your changes via a pull request on GitHub
