changed readme and contributing markdowns with respect to joss guidelines, added code o conduct for the same reason

Author: Vlasovets

CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at [email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -2,7 +2,27 @@
 
 ## Bug reports and feature requests
 
-In case you have questions, possible bugs or feature requests, please open an issue on Github. 
+In case you have questions, possible bugs or feature requests, please, open an [issue](https://github.com/fabian-sp/GGLasso/issues) on Github. 
+
+Pull requests will be evaluated against a checklist:
+
+1.  __Motivation__. Your pull request should clearly and concisely motivate the need for change. Please, describe the problem your PR addresses and show how your pull request solves it as concisely as possible.
+
+Also, include this motivation in `NEWS` so that when a new release of
+`gglasso` comes out it is easy for users to see what has changed. Add your
+item at the top of the file and use markdown for formatting. The
+news item should end with `(@yourGithubUsername, #the_issue_number)`.
+
+2.  __Only related changes__. Before you submit your pull request, please, check to make sure that you have NOT accidentally included any unrelated changes. These make it harder to see exactly what was changed, and to evaluate any unexpected side effects.
+
+Each PR corresponds to a git branch, so if you expect to submit multiple changes
+make sure to create multiple branches. If you have multiple changes that depend
+on each other, start with the first one and do not submit any others until the
+first one has been processed.
+
+3. __Use `gglasso` coding style__. We tried to adhere as closely as possible to the [PEP8](https://www.python.org/dev/peps/pep-0008/) guidelines, please, do so as well. Maintaining a consistent style across the whole code base makes it much easier to jump into the code. If you are modifying existing `gglasso` code that does not follow the style guide, a separate pull request to fix the style would be greatly appreciated.
+
+4. If you add new parameters or a new function, you will also need to document them.
 
 ## Contributing code
 
@@ -14,6 +34,11 @@ The procedure for contributing code is the following:
 4. Run `pytest gglasso/tests` to see whether all tests are successfull. If you add new functionalities, add unit tests for these.
 5. Open a pull request for your feature branch on Github.
 
-Also have a look at [this guide on forking in Github](https://guides.github.com/activities/forking/).
+Also, have a look at [this guide on forking in Github](https://guides.github.com/activities/forking/).
+
+Useful information on how to write bug reports and the principles of contributing to open-source code projects are described on [the scikit-learn webpage](https://scikit-learn.org/stable/developers/contributing.html).
+
+
+## Fixing typos
+You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the source file.
 
-Useful information on how to write bug reports and the principles of contributing to open-source code projects are described on [the scikit-learn webpage](https://scikit-learn.org/stable/developers/contributing.html).

README.md

@@ -61,6 +61,15 @@ We implement the PPDNA Algorithm like proposed in [4]. To use this, import `warm
 4) ADMM method for Group Graphical Lasso where the features/variables are non-conforming<br>
 Method for problems where not all variables exist in all instances/datasets.  To use this, import `ext_ADMM_MGL` from `gglasso/solver/ext_admm_solver`.<br>
 
+## Community Guidelines
+
+1)  Contributions and suggestions to the software are always welcome.
+    Please, consult our [contribution guidelines](CONTRIBUTING.md) prior
+    to submitting a pull request.
+2)  Report issues or problems with the software using github’s [issue
+    tracker](https://github.com/fabian-sp/GGLasso/issues).
+3)  Contributors must adhere to the [Code of
+    Conduct](CODE_OF_CONDUCT.md).
 
 
 ## References