@Patrick and I had an idea to organize proposals/specifications to help the community propose, improve and follow some "ideas/standards". The [[ https://github.com/Whonix/proposals | proposals repo ]] is currently hosting these documents and we should write a spec to explain to other people how this works and how they can be composed.
Here is the initial draft I have in mind:
XXX Add a better introduction than the one above ^
# S# Quicksteps:
1. Create a task  describing the idea you have for a rule or
standard you think other people might find useful (if you already
have written a draft, add it to the ticket too)
2. Discuss with others and collect feedback
3. Once you have enough information to compose the document, create a text
file with the following headers:
# <Name of the proposal> (Proposal <Number assigned to the ticket you created>)
- Ticket: https://phabricator.whonix.org/T<Number>
- File: https://github.com/Whonix/proposals/blob/master/<Number>-<name-of-the-proposal>.txt
- Authors: XXX Should we use the usernames from Phabricator?
- Assignees: <Name of who is currently working in the proposal>
- [Supersedes:] <Number of the proposal/spec to be superseded, if applies>
- [Priority:] XXX How does Whonix currently handle this?
- [Impact:] XXX How does Whonix currently handle this?
- Status: Work in progress | Needs review | Accepted (XXX What else?)
4. Add a description section:
<CActual contents of the proposal>
<You may prefix certain parts of the document with "XXX" which is
unfinished or you need help with>
<(XXX Use markdown?)>
<(XXX Limit lines to 70 characters?)>
5. If needed, add a "TODO" section:
<If there isTasks which still work to do,must be done>
6. listAdd the feedback paragraph and the tasks>references:
<References 0 and 1 are a bit redundant but are useful because we
remove the headers section at the top when posting to other
places that are not familiar to this workflow>
Feedback on the ticket  and pull requests on the repository 
[N]: <Other references>
47. You may want to take a look at the proposals repo  for ideas on
how current proposals were written
58. Name this file in the format: `<Number>-<name-of-the-proposal>.txt`
69. Send a Pull Request (PR) with the file to the proposals repo  or
ask someone to do that for you if not familiar with git/GitHub
710. Update the ticket with the link once the PR is merged (you may
want to replace the draft in the ticket with the link so that you
do not have to update both places)
811. Feel free to continue discussing the proposal in the initial ticket
ticket you opened and update the GitHub PR or create new ones to improve
I noticed the Phabricator UI calls these "tasks". Do you call them tasks or tickets?
Do you think the "TODO" section should be at the end of the document or right after the headers?
What do you think?