In T10584#164866, @eadler wrote:

In T10584#164865, @avivey wrote:

GitHub actually encourages reviewers to "Add commits to PRs"; It's a little hard to un-teach once it gets hold.

one of the many reasons that the github pull request model is broken as designed :\

In T9908#147085, @epriestley wrote:

To clarify, it's critical to you that newbies not be able to, e.g., change the priorities of tasks they filed by making Conduit API calls?

In T9908#147036, @epriestley wrote:

Maniphest currently has field-level edit permissions (e.g., "Can Edit Task Status", "Can Assign Tasks"). My belief is that these are essentially always used to hide fields in order to simplify interfaces, not as real policy controls to prevent changes, per se. I would like to remove them entirely: I think they add a lot of complexity and are very difficult to explain to the user, particularly on the email and Herald flows. Broadly, I don't want to move toward a future where every field in every application has a per-field edit policy.

/me patiently awaits @20after4's response, after being directed to this ticket from Wikimedia's Phabricator instance

I tried answering @epriestley Q134, but got an error (which I failed to copy) and then another error "#1062: Duplicate entry '0-PHID-USER-4188de7cae592cf1bce4' for key 'key_oneanswerperquestion'". So...I'll put my answer here

I think that if Phabricator is going to insist on its own markup language, then y'all should play to win, and not limp in with a "me too" format. Evan's writeup in this task is compelling, but being buried in Phabricator in a four digit ticket number is not really playing to win. @aaron11496 has some promising looking work on a Remarkup conversion plugin for pandoc, but it's clearly only a start.