From 4d5b3620617b331f0a24ebd22e633fb5a52d3501 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cornelius=20K=C3=B6lbel?= Date: Wed, 21 Aug 2019 15:01:41 +0200 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 19 +++++++------------ 1 file changed, 7 insertions(+), 12 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8e22d935f5..91f8c0de13 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,7 +9,7 @@ be really easy. You are using privacyIDEA in your network? Tell about it! Write a blog post, tell your friends or simply twitter about it. -This will make privacyIDEA wider known and attract new contributors. +This will make privacyIDEA wider known and attract new users and contributors. ## Talk to us @@ -30,22 +30,17 @@ So you can make privacyIDEA better and earn karma points by sharing your experience and helping other, younger users. By doing so the developers have more time to develop and -improving your beloved project and hopefully allowing -the developers to earn some money to make a living. +improving your beloved project. So **you are "the community"**, go and help others! https://community.privacyidea.org -## Money +## Professional services -This is an important part to contribute to privacyIDEA. -To allow developers to work full time on privacyIDEA they -have to make money. - -One possibility to do this and also get rid of the NO-WARRANTY -label is to get privacyIDEA Enterprise Edition including a -Service Level Agreement or corresponding consultancy. +If you want to get rid of the NO-WARRANTY +label take a look at privacyIDEA Enterprise Edition including a +Service Level Agreement or get professional consultancy: - consultancy https://netknights.it/en/leistungen/one-time-services/ @@ -223,4 +218,4 @@ If the reviewer approves a pull request, and if no other reviews have been reque ##### Multiple Reviewers -The developer may also request reviews from multiple team members. This makes sense if the PR spans across multiple architectural layers (e.g. backend *and* frontend), or if the developer wants both a functional (does the PR fix the bug?) and technical review (is the code okay?). If a developer requests multiple reviews, the PR description should explicitly state if *all* reviews should be positive, or if *one* positive review is sufficient. \ No newline at end of file +The developer may also request reviews from multiple team members. This makes sense if the PR spans across multiple architectural layers (e.g. backend *and* frontend), or if the developer wants both a functional (does the PR fix the bug?) and technical review (is the code okay?). If a developer requests multiple reviews, the PR description should explicitly state if *all* reviews should be positive, or if *one* positive review is sufficient.