In order to prevent what happened last time, I'm going to edit this document piecemeal so you can choose which PRs to accept and which to reject.
* Partitioned run on sentences
* Cleaned up wording.
* Newline at end of sentences.
Removed some unnecessary parentheses around entire sentences and completely relevant clauses. Also expanded the Using PGP with Email section to provide more detail.
Also made newlines at the end of sentences as per the doc guidelines.
This proposed file changes probably includes some content changes, but ones I hope you'll immediately agree with because the result is a more accurate article.
Among other things,
* Removed unnecessarily prudent logical connection phrases like "thus," and just replaced them with "because" and "as a result" where I could.
* Moved some sentences or clarifications to their proper sections, e.g. moved the "Despite this rule, some acronyms..." line to the Avoid Acronyms section.
* Removed some sentences (like "Additionally, security focused software has the responsibility of providing safety to the user and their data") that, while true, without proper context did not seem relevant to the article.
* Removed some phrases that repeated known contextual information like "of usability and experience" in "if you are interested in furthering your understanding of usability and experience" or "which are shown to a user" in "notifications which are shown to a user".
* Introduced some clauses or phrases that clarified information, like adding "of those mentioned" to "All three desktop environments have their own human interface guidelines,"
* Merged the Avoid Repetitive Tasks and Minimize Repetitive Steps sections.
* Rewrote some sentences that were incomplete or didn't make sense into what I assumed the writer intended to say.
* Inserted possessive's' when they were necessary, and turned bigger sentences into smaller ones using possessives when I could ("notification messages presented to user" --> "user's notification messages")
* Grammar edits
* Compartmentalized run-on sentences.
This was a pretty big edit, so you'll probably disagree with some of the changes. Just explain what you want to be re-done or where my edits changes an important meaning/formed an inaccuracy and I will make another commit.
I did not modify any of the content itself; just presented it more clearly by:
- Modifying unnecessarily wordy phrases
- Fixing grammatical mistakes
- Partitioning run-on sentences
- Reduced Word Re-use
- Removed unnecessary commas
- Formatted each individual typographic convention consistently
- Made misc. changes to improve clarity and make the text more evocative
I did not modify any of the content itself; just presented it more clearly by:
- Modifying unnecessarily wordy phrases
- Fixing grammatical mistakes
- Partitioning run-on sentences
- Reduced Word Re-use
- Made misc. changes to improve clarity and make the text more evocative
* Organize sections logically according to each step in the bug
reporting process
* Explain how bugs can be reported in different venues
* Explain how to report bugs in qubes-issues (will replace
CONTRIBUTING.MD)
* Link to Contributing page
* Generally improve wording and formatting
* List all of the main ways in which people can contribute
* Provide helpful links for each of those ways
* Explain how to contribute code
* Provide helpful links to source code, how to send patches, reporting
bugs, etc.
* Improve wording and formatting in general
* Distinguish security issues from bugs and add link to information
on reporting security issues
* Add link to Mailing Lists page in place of direct link to Google
Groups web interface
* Add common redirects
