[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3706: Create documentation for requesting design review

[Tahoe-LAFS]

#3706: Create documentation for requesting design review
---------------------+----------------------------------------
 Reporter:  maylee   |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  Contributor Experience
Component:  unknown  |        Version:  n/a
 Keywords:           |  Launchpad Bug:
---------------------+----------------------------------------
 From: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Patches

 Original text:

 `To request a design review, just explain your design (with or without a
 patch) and ask for feedback. Completion of a design review will normally
 not directly result in a patch being committed. The main goal of a design
 review is to give the person working on the ticket confidence that there
 are no show-stopping issues with the approach they are taking, and to get
 feedback on smaller issues that are useful to take into account before
 doing further work on a patch.`

 Example replacement text:

 `If you have a design that you would like feedback on, open a PR and
 explain your design, attaching files as needed. Request a review from
 Tahoe Committers. The goal of a design review is to ensure there are no
 show-stopping issues before beginning work and to address things that
 should be taken into account (e.g., how to break the work up into multiple
 tickets or PRs).`

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3706>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage