[issue-241] Update community standards

CODEOWNERS

@@ -0,0 +1 @@
+@jmesnil @yersan

CODE_OF_CONDUCT.md

@@ -0,0 +1,39 @@
+## WildFly Operator Community Code of Conduct v1.0
+
+### Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering
+an open and welcoming community, we pledge to respect all people who contribute
+through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for
+everyone, regardless of level of experience, gender, gender identity and expression,
+sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
+religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+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. By adopting this Code of Conduct, project maintainers
+commit themselves to fairly and consistently applying these principles to every aspect
+of managing this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
+contacting a Jeff Mesnil <[email protected]>
+
+
+This Code of Conduct is adapted from the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) which is
+adapted from the Contributor Covenant (http://contributor-covenant.org), version 1.2.0, available at http://contributor-covenant.org/version/1/2/0/

CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing To WildFly Operator
+
+Firstly, anyone is more than welcome to contribute to WildFly Operator, so big thanks for considering it. You can contribute by reporting and fixing bugs, improving the documentation or requesting and implementing new features.  
+
+You only must follow the guidelines described on this document.
+
+## Code of Conduct
+
+We are serious about making this a welcoming, happy project. We will not tolerate discrimination,
+aggressive or insulting behaviour.
+
+To this end, the project and everyone participating in it is bound by the [Code of
+Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report
+unacceptable behaviour to any of the project admins.
+
+## Bugs
+
+If you find a bug, please [open an issue](https://github.com/wildfly/wildfly-operator/issues)! Do try
+to include all the details needed to recreate your problem. This is likely to include:
+
+- The version of the WildFly Operator
+- The exact platform and version of the platform that you're running on
+- The steps taken to cause the bug
+
+## Building Features and Documentation
+
+If you're looking for something to work on, take look at the issue tracker, in particular any items
+labelled [good first issue](https://github.com/wildfly/wildfly-operator/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).
+Please leave a comment on the issue to mention that you have started work, in order to avoid
+multiple people working on the same issue.
+
+If you have an idea for a feature - whether you have time to work on it - please also open an
+issue describing your feature and label it "enhancement". We can then discuss it as a community and
+see what can be done. Please be aware that some features may not align with the project goals and
+might therefore be closed. In particular, please don't start work on a new feature without
+discussing it first to avoid wasting effort. We do commit to listening to all proposals and will do
+our best to work something out!
+
+## Pull Request Process
+
+On opening a PR, a GitHub action will execute the test suite against the new code. All code is
+required to pass the tests, and new code must be accompanied by new tests. 
+
+All PRs have to be reviewed and signed off by another developer before being merged to the main
+branch. This review will likely ask for some changes to the code - please don't be alarmed or upset
+at this; it is expected that all PRs will need tweaks and a normal part of the process.
+
+Be aware that all WildFly Operator code is released under the [Apache 2.0 licence](LICENSE).
+
+## Development environment setup
+
+The WildFly Operator [README](README.adoc) contains a section that describes how you can work with the WildFly Operator from the developer point of view.
+Take a look at the [Developer Instructions](https://github.com/wildfly/wildfly-operator/blob/main/README.adoc#developer-instructions) section to learn how you can use the WildFly Operator on your local environment for development purposes.
+
+## Thanks
+
+This guideline has been elaborated following these resources:
+[Java Operator SDK](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/CONTRIBUTING.md)

SECURITY.md

@@ -0,0 +1,10 @@
+# Security Policy
+
+## Security Contacts and Procedures
+
+The WildFly Operator community takes security very seriously, and we aim to take immediate action to address serious security-related problems that involve our products or services.
+
+Please report any suspected security vulnerability in this project to Red Hat Product Security at [email protected]. You can use our GPG key to communicate with us securely.
+
+To report an issue in any Red Hat branded website or online service, please contact Red Hat Information Security at [email protected].
+https://access.redhat.com/security/team/contact