khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-04 10:46:21 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1852 from ahstro/fix/gender

Browse Source 
Use more inclusive pronouns
This commit is contained in:
Jan-Christoph Borchardt
2020-03-26 23:39:59 +01:00
committed by GitHub
parent 6657d331c3 139f1876eb
commit c5b521f50d
9 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
developer_manual/app/flow.rst
View File

@@ -4,6 +4,6 @@ Nextcloud Flow
Nextcloud Flow is the workflow engine of Nextcloud. It offers flexible, user-defined event-based task automation. Apps can register events or triggers which can start a flow, as well as actions which get executed once a trigger is hit and the constraints are satisfied.
At 36c3 blizzz gave a talk explaining Flow and `how to write actions and triggers. <https://mirror.eu.oneandone.net/projects/media.ccc.de/congress/2019/h264-sd/36c3-oio-174-eng-Building_Nextcloud_Flow_sd.mp4>`_ You can `find the slides of his talk here. <https://nextcloud.com/wp-content/themes/next/assets/files/Building_nextcloud_flow.pdf>`_
At 36c3 blizzz gave a talk explaining Flow and `how to write actions and triggers. <https://mirror.eu.oneandone.net/projects/media.ccc.de/congress/2019/h264-sd/36c3-oio-174-eng-Building_Nextcloud_Flow_sd.mp4>`_ You can `find the slides of their talk here. <https://nextcloud.com/wp-content/themes/next/assets/files/Building_nextcloud_flow.pdf>`_
Contributions to this documentation are, as always, very welcome!

2
developer_manual/app/publishing.rst
View File

@@ -68,7 +68,7 @@ Respect the users
* Apps must respect user privacy. IF user data is sent anywhere, this must be clearly explained and be kept to a minimum for the functioning of an app. Use proper security measures when needed.
* 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.
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, they might find themselves blocked from submitting applications.
Moving your repo to the Nextcloud organization
----------------------------------------------

4
developer_manual/bugtracker/codereviews.rst
View File

@@ -23,7 +23,7 @@ reviewed!
How will it work?
-----------------
#. A developer will submit his changes on GitHub via a pull request (PR).
#. A developer will submit their changes on GitHub via a pull request (PR).
`GitHub:help - using pull requests <https://help.GitHub.com/articles/using-pull-requests>`_
#. Within the pull request the developer could already name other developers (using
@GitHubusername) and ask them for review.
@@ -32,7 +32,7 @@ How will it work?
PR author had indicated.
#. Other developers (either named or at free will) have a look at the changes
and are welcome to write comments within the comment field.
#. In case the reviewer is okay with the changes and thinks all his comments and
#. In case the reviewer is okay with the changes and thinks all their comments and
suggestions have been taken into account a :+1 on the comment will signal a positive
review.
#. Before a pull request will be merged into master or the corresponding

4
developer_manual/bugtracker/kanban.rst
View File

@@ -77,7 +77,7 @@ Why do we have it?
What does a developer think?
"Nice! I can safely implement it that way because more than one person has put
his brain to the task of coming up with a good solution. Here! Me! I’ll do
their brain to the task of coming up with a good solution. Here! Me! I’ll do
it!"
When can I pull?
@@ -144,7 +144,7 @@ Reviewing
Why do we have it?
With the Gherkin Scenario from the Concept Phase reviewers have a checklist to
test if a Bug has been solved and if an Enhancement works as expected. **The
most eager reviewer we have is Drone**. When it comes to testing he soldiers
most eager reviewer we have is Drone**. When it comes to testing they soldier
on going through the different combinations of platform, Web server and
database.

2
developer_manual/general/security.rst
View File

@@ -216,7 +216,7 @@ Always store user data or configuration files in safe locations, e.g. **nextclou
Cross site request forgery
--------------------------
Using `CSRF <http://en.wikipedia.org/wiki/Cross-site_request_forgery>`_ one can trick a user into executing a request that he did not want to make. Thus every POST and GET request needs to be protected against it. The only places where no CSRF checks are needed are in the main template, which is rendering the application, or in externally callable interfaces.
Using `CSRF <http://en.wikipedia.org/wiki/Cross-site_request_forgery>`_ one can trick a user into executing a request that they did not want to make. Thus every POST and GET request needs to be protected against it. The only places where no CSRF checks are needed are in the main template, which is rendering the application, or in externally callable interfaces.
.. note:: Submitting a form is also a POST/GET request!