[bisq-network/bisq-docs] Add proposals.adoc (#40)

[mrosseel]

mrosseel commented on this pull request.



> + . Discuss your idea with other contributors to see if a proposal is worth submitting at all;
+ . Search through existing proposals (both https://github.com/bisq-network/proposals/issues?utf8=%E2%9C%93&q=is%3Aissue+[open and closed]) to see whether something similar has already been proposed;
+ . Notice which among those proposals have been accepted and rejected, and why;
+ . Read this document to fully understand the proposal process and guidelines.
+
+=== Step 1. Submit
+
+Create a new GitHub issue in the `bisq-network/proposals` repository containing the text of your proposal, written and formatted per the guidelines below.
+
+A maintainer will quickly review your proposal and will either (a) assign it to you to indicate your ownership and responsibility over it, or (b) close it and label it as `was:incorrect` if it does not follow the guidelines below.
+
+=== Step 2. Review
+
+Once a proposal is submitted, a two-week review period follows. During this period, interested reviewers should read, discuss and ultimately react to the proposal as follows:
+
+ - 👍: I agree with the proposal and want to see it enacted

![screen shot 2018-04-23 at 15 03 28](https://user-images.githubusercontent.com/1465310/39128242-96b34f7e-4707-11e8-9f44-5228bf3aa246.png)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-docs/pull/40#discussion_r183386159
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180423/8fb0f5e5/attachment-0002.html>