Initial company profile and contribution rules

Signed-off-by: jdsika <[email protected]>

CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+# 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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+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.1]: https://www.contributor-covenant.org/version/2/1/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

@@ -0,0 +1,72 @@
+# Contributing to StakeNow projects
+
+## Developer Certification of Origin (DCO)
+
+To make a good faith effort to ensure licensing criteria are met, StakeNow projects require the Developer Certificate of Origin (DCO) process to be followed.
+The DCO is an attestation attached to every contribution made by every developer.
+In the commit message of the contribution, (described more fully later in this document), the developer simply adds a Signed-off-by statement and thereby agrees to the DCO.
+When a developer submits a patch, it is a commitment that the contributor has the right to submit the patch per the license.
+The DCO agreement is shown below and online at [developercertificate.org](https://developercertificate.org/).
+
+```
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the
+    best of my knowledge, is covered under an appropriate open
+    source license and I have the right under that license to
+    submit that work with modifications, whether created in whole
+    or in part by me, under the same open source license (unless
+    I am permitted to submit under a different license), as
+    Indicated in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including
+    all personal information I submit with it, including my
+    sign-off) is maintained indefinitely and may be redistributed
+    consistent with this project or the open source license(s)
+    involved.'
+```
+
+## DCO Sign-Off methods
+
+The DCO requires a sign-off message in the following format appear on each commit in the pull request:
+
+`Signed-off-by: Firstname Lastname <[email protected]>`
+
+The DCO text can either be manually added to your commit body, or you can add either `-s` or `--signoff` to your usual Git commit commands.
+If you forget to add the sign-off you can also amend a previous commit with the sign-off by running git commit `--amend -s`.
+You can add sign-offs to multiple commits (including commits originally authored by others, if you are authorized to do so) using `git rebase --signoff`.
+If you’ve pushed your changes to GitHub already you’ll need to force push your branch after this with `git push --force-with-lease`.
+If you want to be reminded to add the sign-off for commits in your repository, you can add the following commit-message git hook to your repository:
+
+
+```bash
+#!/bin/sh
+#
+# Check for DCO/Signed-off-by in message
+#
+
+if ! grep -q "^Signed-off-by: " "$1"
+then
+  echo "Aborting commit: Commit message is not signed off" >&2
+  exit 1
+fi
+```
+
+Placing this script into a file called `.git/hooks/commit-msg` and making it executable (e.g. using `chmod a+x .git/hooks/commit-msg` on unixoid operating systems) will prevent commits without a sign-off.
+
+## Commit signature verification
+
+The project requires a verification of the commit signature using GPG-sign commits with `-S [<keyid>]`. The `keyid` argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. `--no-gpg-sign` is useful to countermand both `commit.gpgSign` configuration variable, and earlier `--gpg-sign`.
+
+You can read all about setting it up in the [official GitHub documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification).

README.md

@@ -1,2 +1,15 @@
-# .github
-StakeNow company profile & open source contribution rules.
+# StakeNow
+
+## Public organization profile
+The profile information is described in [profile/README.md](profile/README.md) and displayed on the organization main page. Read the corresponding GitHub [documentation](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile) for more information on organization profiles.
+
+## Code of Conduct
+As a community we need to define how we want to interact with each other respectfully and make sure that we create an inclusive environment that encourages contributions. For this reason StakeNow has a clear [Code of Conduct](/CODE_OF_CONDUCT.md) that applies to everyone. Read [here](https://opensource.guide/code-of-conduct/) why we need a code of conduct. A modified version of [this](https://www.contributor-covenant.org/) document is currently in use.
+
+## Contributing
+Thanks for your interest in contributing! There are many ways to contribute to StakeNow projects. Get started [here](/CONTRIBUTING.md).
+
+## Licensing
+The open-source material to be contributed must be licensed under a common open-source license as listed on [opensource.org](https://opensource.org/) and is documented in the LICENSE file.
+
+The license tells you what rights you have as a developer, provided by the copyright holder. It is important that the contributor fully understands the licensing rights and agrees to them. Sometimes the copyright holder isn’t the contributor, such as when the contributor is doing work on behalf of a company.

profile/README.md

@@ -0,0 +1,45 @@
+![tp header](/doc/img/StakeNow_fi.png)
+
+[![](https://img.shields.io/twitter/follow/StakeNow?label=Follow&style=social)](https://twitter.com/StakeNow)
+
+# StakeNow.fi
+
+This GitHub organization is maintained by the [vDL Digital Ventures GmbH](https://vdl.digital/) - a Venture Studio based in Aschheim, Germany.
+
+We operate the largest Tezos [validator](https://tzkt.io/tz1g8vkmcde6sWKaG2NN9WKzCkDM6Rziq194/schedule) in Germany since the beginning of the Tezos beta network and develop [StakeNow.fi](https://stakenow.fi/) giving you a 360° view of your investments and letting you manage your Tezos assets in one place.
+
+![tp header](/doc/img/StakeNow_fi_NFTs.png)
+
+As a Venture Studio our main focus of activities is the development of professional services and software to interact securely and effortlessly with public blockchains. We support decentralization and thus the stability of distributed systems by promoting adaptation among private individuals and companies. We invest in key technologies and products complementing each other to ensure the interaction of a successful ecosystem while we connect stakeholders around the globe.
+
+We support strong Open Source communities and welcome your contribution to projects, If you are interested read more detailed information [here](/README.md).
+
+## Open Source projects
+
+### Sign In With Tezos (SIWT)
+
+Initiated: 2022-04-13
+
+SIWT is an open-source library that supports the development of your decentralized application first of all by proving the ownership of the private key to the address the user signs in with. This allows you to add permissions to use an API/backend based on a diverse set of access-control mechanisms, like owning a specific NFT or an address being part of a white/black list. After winning the [Tezos x Encode hackathon](https://medium.com/encode-club/encode-x-tezos-hackathon-finale-prizewinners-and-summary-ba5c9cda677c) and due to the positive feedback from the Tezos community, we decided to spend additional efforts to take our Proof-of-Concept to an easy-to-integrate library with an extended feature set with the help of the [Tezos Foundation](https://tezos.foundation/). We invite you to use SIWT in your dApp and contact us in our [Discord](https://discord.com/invite/6J3bjhkpxm?utm_source=StakeNow+Discord&utm_medium=Twitter&utm_campaign=StakeNow.Fi+Launch) if you have any questions!
+
+#### Links:
+- [Repository](https://github.com/StakeNow/SIWT)
+- [Demo Website](https://siwt.xyz/)
+- [Documentation](https://docs.siwt.xyz/)
+
+### Tezos Reward Distributor (TRD)
+
+Initiated: 2018-10-13
+
+TRD is a software for distributing staking rewards of Tezos validators (bakers) occurred through the [Tezos Liquid Proof of Stake](https://tezos.com/governance/) consensus mechanism. It is not a script but a full scale application which can continuously run in the background as a Linux service. It can track cycles and make payments. However, it does not have to be used as a service, but it can also be used interactively. Read about it [here](https://tezos-reward-distributor-organization.github.io/tezos-reward-distributor/).
+
+#### Maintainer:
+- [Carlo van Driesten](https://github.com/jdsika) (vDL Digital Ventures GmbH)
+- [Nicolas Ochem](https://github.com/nicolasochem) (MIDL.dev)
+- [Matthew Boehm](https://github.com/utdrmac) (Freelancer)
+- [Viktor Kreschenski](https://github.com/vkresch) (kreschenski.com)
+
+
+#### Links:
+- [TRD StakeNow Fork](https://github.com/StakeNow/tezos-reward-distributor/tree/master)
+- [TRD Public Organization](https://github.com/tezos-reward-distributor-organization)