add code of conduct and contributing guide

.github/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 lcsb-r3 .at. uni.lu. 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

.github/CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing to COBREXA.jl
+
+:+1::tada: Thanks for taking the time to contribute to [COBREXA.jl](https://github.com/LCSB-BioCore/COBREXA.jl)! :tada::+1:
+
+## How can I contribute?
+
+A complete technical guide on how to get started contributing is given [here](https://lcsb-biocore.github.io/COBREXA.jl/stable/howToContribute/).
+
+## How to report a bug or suggest an enhancement
+
+Please use the [GitHub issue tracker](https://github.com/LCSB-BioCore/COBREXA.jl/issues) to report any problems with the software, and discuss any potential questions about COBREXA use.
+
+Before creating bug reports, please check [the open
+issues](https://github.com/LCSB-BioCore/COBREXA.jl/issues) as you might find
+out that you don't need to create one. When you are creating a bug report,
+please include as many details as possible. Fill out the required template, the
+information it asks for helps us resolve issues faster.
+
+> If you find a Closed issue that seems like it is the same thing that
+  you're experiencing, open a new issue and include a link to the original issue
+  in the body of your new one.
+
+If reporting issues, please do not forget to include a description of conditions under which the issue occurs; preferably a code snippet that can be run separately (sometimes termed "minimal crashing example").
+
+## How to submit a pull request (PR)?
+
+Please follow these steps to have your contribution considered by the maintainers:
+
+1. Follow all instructions in the template
+2. Submit your pull request
+3. After you submit your pull request, verify that all status checks are passing
+
+After you submitted a pull request, a label might be assigned that allows us
+to track and manage issues and pull requests.