Merge pull request #69 from hgraph-os/merging-in-hgraph-react-repo

Merging in hgraph react repo

Author: ericbenwa

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at hgraph@goinvo.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTE.md

@@ -0,0 +1,53 @@
+# Contribute
+
+We welcome contributions in the form of [issues](https://github.com/hgraph-os/hGraph/issues/) or [pull requests](https://github.com/hgraph-os/hGraph/pulls). We recommend starting with an [issue](https://github.com/hgraph-os/hGraph/issues/new) to have a conversation before changing any files.
+
+## Code of Conduct
+Help us keep hGraph open and inclusive. Please read and follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Topics for Contributing
+For designers and engineers:
+* What's version 2 of hGraph?
+* Repo evolves from a demo into a production-ready component others can integrate with minimal effort
+* CSS refinement of hGraph (making it beautiful)
+* JS help to make hGraph an easy to use, plug n’ play JS library for visualizing data
+* Scales beautifully for both desktop and mobile
+* Provide multi-level view and connection of health data
+[Determinants of Health](https://www.goinvo.com/vision/determinants-of-health/) (ex. Holistic view of all data, missing data)
+* hGraph main, high-level view
+* hGraph secondary detailed view
+* Design the population hGraph for your neighborhood, city, clinic, nation.
+
+For clinicians and researchers:
+* Make a [hScore](https://github.com/hgraph-os/hScore). Evolve the scoring algorithm.
+* What are the top metrics to show (at the "global" hGraph level)? What are the correct groupings and sub metric groupings?
+* What are the chronic disease patterns (the outlines on hGraph) and how do we arrange the metrics to better see those conditions?
+* What are we missing from the everyday diagnostic tool clinicians use? How do we improve hGraph to rock your in-patient encounter experience? Population diagnostic experience?
+
+## Ways to Contribute
+
+### Report issues
+- Ensure the issue was not already reported by searching on GitHub under [Issues](https://github.com/hgraph-os/hGraph/issues/).
+- If you're unable to find an open issue addressing the problem, open a [new issue](https://github.com/hgraph-os/hGraph/issues/new) and label it 'bug'. Be sure to include a title and clear description, as much relevant information as possible, and a text sample or an executable test case demonstrating the expected behavior that is not occurring.
+
+### Suggest new features
+- Suggest your change as a [new issue](https://github.com/hgraph-os/hGraph/issues/new) and label it 'feature request' before writing any text.
+- The team will review your new feature and respond within 24 business hours.
+
+### Edit text or documentation
+- No pull request is too small: fix typos, add comments, clean up inconsistent whitespace.
+- Ensure the pull request description clearly describes the problem and solution. Include the relevant issue number if applicable.
+- The team will review your pull request and respond within 24 business hours.
+
+## Editing
+### Instructions
+First, make sure you're logged in with your Github account. When you have a change you wish to make, simply find the version of the document that you wish to change. Open it and press the Edit button.
+
+On the edit page, you'll be presented with a version of the document. Edit the text you wish to change. When you are done editing, there will be a section at the bottom of the page to save your work. Under "Commit summary", enter a brief description of the change(s) you're making. In the "Extended description" field, explain what the changes are and why they're needed. Select the "Create a new branch for this commit..." option. When you're done, commit your changes.
+
+At this point, you'll be presented with a form to submit a pull request. The bottom section of the page will show all of the changes you've made to the document, and all you should need to do is press the "Send Pull Request" button.
+
+Once you've submitted a pull request, the hGraph team can review the work under the Pull Requests tab on the right-hand side, and a contributor to the repo can merge your changes.
+
+### Markdown
+These files are written in the Markdown syntax. You can reference this [guide](https://www.markdownguide.org/basic-syntax/) for formatting (ex. Bold, Footnotes, Lists, Links).