pi/babyphone
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Change project name to "Child Monitor"

Browse Source
This commit is contained in:
edr
2020-04-22 22:52:08 +02:00
parent 10f2d0a253
commit d0ed6c1bba
29 changed files with 159 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
CONTRIBUTING.md
View File

@@ -1,9 +1,9 @@
How to Submit Patches to the Protect Baby Monitor Project
How to Submit Patches to the Child Monitor Project
===============================================================================
https://github.com/brarcher/budget-watch
https://github.com/enguerrand/child-monitor
This document is intended to act as a guide to help you contribute to the
Protect Baby Monitor project. It is not perfect, and there will always be exceptions
Child Monitor project. It is not perfect, and there will always be exceptions
to the rules described here, but by following the instructions below you
should have a much easier time getting your work merged with the upstream
project.
@@ -28,13 +28,6 @@ and FindBugs, run using:
The final check is by testing the application on a live device and verifying
the basic functionality works as expected.
## Make Sure Your Code is Tested
The Protect Baby Monitor code uses a fair number of unit tests to verify that
the basic functionality is working. Submissions which add functionality
or significantly change the existing code should include additional tests
to verify the proper operation of the proposed changes.
## Explain Your Work
At the top of every patch you should include a description of the problem you
@@ -85,7 +78,7 @@ your real name, saying:
## Submit Patch(es) for Review
Finally, you will need to submit your patches so that they can be reviewed
and potentially merged into the main Protect Baby Monitor repository. The preferred
way to do this is to submit a Pull Request to the Protect Baby Monitor project.
and potentially merged into the main Child Monitor repository. The preferred
way to do this is to submit a Pull Request to the Child Monitor project.
Changes need to apply cleanly onto the master branch and pass all
unit tests and produce no errors during static analysis.