From a961e67ead3d0c6d9bd9a16fad8095c8eb511425 Mon Sep 17 00:00:00 2001 From: Jos Poortvliet Date: Mon, 1 Apr 2019 19:43:17 +0200 Subject: [PATCH 1/4] add section on moving into our repo --- developer_manual/app/publishing.rst | 30 +++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/developer_manual/app/publishing.rst b/developer_manual/app/publishing.rst index fe7f64f88..2d8acf4d5 100644 --- a/developer_manual/app/publishing.rst +++ b/developer_manual/app/publishing.rst @@ -69,3 +69,33 @@ Respect the users * App authors must provide means to contact them, be it through a bug tracker, forum or mail. Apps which break the guidelines will lose their 'approved' or 'official' state; and might be blocked from the app store altogether. This also has repercussions for the author, especially in case of security concerns, he/she might find themselves blocked from submitting applications. + +Putting your repo in the Nextcloud Project +------------------------------------------ +We're always delighted to hear app develpers are interested in moving their app into the Nextcloud Project in `github.com/nextcloud `_! There are benefits for users and developers in being there. However, it comes with some requirements as well. + +Benefits +^^^^^^^^ + +* You can use the tools and bots we have set up, including translations and such +* Everybody in the Nextcloud project can more easily contribute +* Your visibility to app developers increases +* Users can expect apps in our project to be better maintained + +Requirements +^^^^^^^^^^^^ +To deliver on the promises above, we have two simple rules. + +* You participate in our `collaborative development model <../general/code-of-conduct.html>`_ +* When you are no longer active, our admins can decide to hand over maintainership to another contributor + +We want to make sure that when you find other things in life which are more urgent or otherwise are unable to help your project anymore, it does not become 'dead code' as long as there are people who want to keep it alive. + +Please note that the role of a maintainer is not to be the most active or prolific contributor to a project! Worlds' `most famous maintainer of an open source project `_ has not appeared in the top-100 of contributors by lines of code for decades, yet he runs the largest single software development project in the history of mankind. Being friendly, welcoming and responsive are what it takes to be a successful maintainer. Not being the most brilliant developer ever, or spending nights and weekends coding! + +The goal of these rules is simple: help your project be more successful. We also suggest you watch this talk by `Jan about building a great community. `_ + +How to move +^^^^^^^^^^^ + +To move into our github repo, just ask any of our contributors, `especially those who are admin. `_ They will be happy to help! From 8e0008f848d074f3f883be19a9d2aac6b50fb5f3 Mon Sep 17 00:00:00 2001 From: Jos Poortvliet Date: Mon, 1 Apr 2019 19:46:57 +0200 Subject: [PATCH 2/4] note it is about users Signed-off-by: Jos Poortvliet --- developer_manual/app/publishing.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer_manual/app/publishing.rst b/developer_manual/app/publishing.rst index 2d8acf4d5..831608c0b 100644 --- a/developer_manual/app/publishing.rst +++ b/developer_manual/app/publishing.rst @@ -89,7 +89,7 @@ To deliver on the promises above, we have two simple rules. * You participate in our `collaborative development model <../general/code-of-conduct.html>`_ * When you are no longer active, our admins can decide to hand over maintainership to another contributor -We want to make sure that when you find other things in life which are more urgent or otherwise are unable to help your project anymore, it does not become 'dead code' as long as there are people who want to keep it alive. +We want to make sure that when you find other things in life which are more urgent or otherwise are unable to help your project anymore, it does not become 'dead code' as long as there are people who want to keep it alive. This is not fair to users, who would be forced to remove the app and install another. Please note that the role of a maintainer is not to be the most active or prolific contributor to a project! Worlds' `most famous maintainer of an open source project `_ has not appeared in the top-100 of contributors by lines of code for decades, yet he runs the largest single software development project in the history of mankind. Being friendly, welcoming and responsive are what it takes to be a successful maintainer. Not being the most brilliant developer ever, or spending nights and weekends coding! From 4c9eecfda7e74c1cf9ac477f435a0f7267e28f18 Mon Sep 17 00:00:00 2001 From: Jan-Christoph Borchardt Date: Mon, 1 Apr 2019 20:39:43 +0200 Subject: [PATCH 3/4] Apply suggestions from code review Wording fixes --- developer_manual/app/publishing.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/developer_manual/app/publishing.rst b/developer_manual/app/publishing.rst index 831608c0b..deaba158e 100644 --- a/developer_manual/app/publishing.rst +++ b/developer_manual/app/publishing.rst @@ -70,15 +70,15 @@ Respect the users Apps which break the guidelines will lose their 'approved' or 'official' state; and might be blocked from the app store altogether. This also has repercussions for the author, especially in case of security concerns, he/she might find themselves blocked from submitting applications. -Putting your repo in the Nextcloud Project +Moving your repo to the Nextcloud organization ------------------------------------------ -We're always delighted to hear app develpers are interested in moving their app into the Nextcloud Project in `github.com/nextcloud `_! There are benefits for users and developers in being there. However, it comes with some requirements as well. +We're always delighted to hear app developers are interested in moving their app to the Nextcloud organization at `github.com/nextcloud `_! There are benefits for users and developers in being there. However, it comes with some requirements as well. Benefits ^^^^^^^^ * You can use the tools and bots we have set up, including translations and such -* Everybody in the Nextcloud project can more easily contribute +* Everybody in the Nextcloud organization can contribute more easily * Your visibility to app developers increases * Users can expect apps in our project to be better maintained @@ -86,7 +86,7 @@ Requirements ^^^^^^^^^^^^ To deliver on the promises above, we have two simple rules. -* You participate in our `collaborative development model <../general/code-of-conduct.html>`_ +* You work and communicate according to the values of our `Code of Conduct <../general/code-of-conduct.html>`_ * When you are no longer active, our admins can decide to hand over maintainership to another contributor We want to make sure that when you find other things in life which are more urgent or otherwise are unable to help your project anymore, it does not become 'dead code' as long as there are people who want to keep it alive. This is not fair to users, who would be forced to remove the app and install another. @@ -98,4 +98,4 @@ The goal of these rules is simple: help your project be more successful. We also How to move ^^^^^^^^^^^ -To move into our github repo, just ask any of our contributors, `especially those who are admin. `_ They will be happy to help! +To move your repository to our Github organization, just ask any of our contributors, `especially those who are admin. `_ They will be happy to help! From 1f1925ee624292df64d9bf48a8a6ad75a6c191d2 Mon Sep 17 00:00:00 2001 From: Jan-Christoph Borchardt Date: Mon, 1 Apr 2019 20:40:33 +0200 Subject: [PATCH 4/4] Remove specific unnecessary reference --- developer_manual/app/publishing.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer_manual/app/publishing.rst b/developer_manual/app/publishing.rst index deaba158e..756d1ae37 100644 --- a/developer_manual/app/publishing.rst +++ b/developer_manual/app/publishing.rst @@ -91,7 +91,7 @@ To deliver on the promises above, we have two simple rules. We want to make sure that when you find other things in life which are more urgent or otherwise are unable to help your project anymore, it does not become 'dead code' as long as there are people who want to keep it alive. This is not fair to users, who would be forced to remove the app and install another. -Please note that the role of a maintainer is not to be the most active or prolific contributor to a project! Worlds' `most famous maintainer of an open source project `_ has not appeared in the top-100 of contributors by lines of code for decades, yet he runs the largest single software development project in the history of mankind. Being friendly, welcoming and responsive are what it takes to be a successful maintainer. Not being the most brilliant developer ever, or spending nights and weekends coding! +Please note that the role of a maintainer is not to be the most active or prolific contributor to a project! Being friendly, welcoming and responsive are what it takes to be a successful maintainer. Not being the most brilliant developer ever, or spending nights and weekends coding! The goal of these rules is simple: help your project be more successful. We also suggest you watch this talk by `Jan about building a great community. `_