[bisq-network/projects] Establish critical bugs board and process (#16)

[Chris Beams]

> @cbeams Do you want to close this issue after your wiki edits?
>> yes, will do

Actually, this project shouldn't be considered complete until the board and process are linked to from the places that (especially new) developers would look to as a reference on our development process. I've added checkboxes in the description to this effect. I would be fine if these links are surgically added in a rough / quick way. We should more fully revise and unify the resources mentioned there, but that's a separate effort.

As an aside, this is a good example of end-to-end thinking when it comes to projects / what it means to really deliver something. We created the board, documented the process and announced it to `@bisq-network/dev` and `@bisq-network/support`, but without the links mentioned above, it's likely that future developers won't know about the board/process unless someone mentions it to them.

-- 
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/projects/issues/16#issuecomment-589585185
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200221/3d3a5dbb/attachment.html>