Git-Mirrors/Qubes-Community-Content
1
0
Fork 0
mirror of https://github.com/Qubes-Community/Contents.git synced 2024-12-22 21:59:26 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update no-git-submissions.md

Browse Source
This commit is contained in:
Ivan 2018-03-14 15:42:15 +00:00 committed by GitHub
parent 618a164dcb
commit 1b6d9bc6b8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/no-git-submissions.md
View File

@ -1,9 +1,9 @@
#### Contributing without knowing git #### Contributing without knowing git
A shortcoming of the official [qubes-doc](https://www.qubes-os.org/doc/) is that basic git knowledge is [required](https://www.qubes-os.org/doc/doc-guidelines/) to contribute: concepts like forking a repository or understanding pull requests have to be mastered, as well as synchronizing a forked repository with upstream for subsequent contributions. A shortcoming of the official [qubes-doc](https://www.qubes-os.org/doc/) is that basic git knowledge is [required](https://www.qubes-os.org/doc/doc-guidelines/) to contribute: while git command line isn't necessary, concepts like forking a repository or understanding pull requests have to be mastered, as well as synchronizing a forked repository with the official repository for subsequent contributions.
Qubes users who don't want to learn git for a reason or another, or who don't feel confident submitting a pull request (PR), can simply create an issue in this github community page ("Issues" tab above) with any content they deem fit: documentation (new or improvements), suggestions, fixes, one-liners, ... Qubes users who don't want to learn git for a reason or another or who don't feel confident submitting a pull request (PR) can simply create an issue in this github community page ("Issues" tab above), with any content they see fit: addition or improvements to documentation, suggestions, tips, typo fixes, one-liners, ...
Once the issue's content is discussed in the issue's thread and is in shape for a PR submission (whether to this project's unoffical documentation or to Qubes' official repository), a community member will either create a git pull request on your behalf and will take care of anything "git", or guide you in creating your own PR. Note however that in the former case attribution/credit cannot be assigned to you, it is a technical shortcoming of having a pull request created and submitted on your behalf. After (optional) discussion in the issue's thread and if the content is deemed fit for submission (whether to this project's unoffical documentation or to Qubes' official qubes-doc repository) a community member may either create a git pull request on your behalf and take care of anything "git", or if you'd like to, he could guide you in creating your own PR. Note however that in the former case attribution/credit cannot be assigned to you - it is a technical shortcoming of having a pull request created and submitted on your behalf.
It would of course ease the burden on community members if returning contributors learn the few basic git steps required to submit pull requests themselves, but this is of course not a requirement. It would of course ease the burden on community members if returning contributors learn the few basic git steps required to submit pull requests themselves, but this is of course not a requirement.