[wp-meta] [Making WordPress.org] #5118: Introduce dev-note field to Trac

[Making WordPress.org]

#5118: Introduce dev-note field to Trac
----------------------------------------------------+---------------------
 Reporter:  garrett-eclipse                         |       Owner:  (none)
     Type:  enhancement                             |      Status:  new
 Priority:  normal                                  |   Milestone:
Component:  Trac                                    |  Resolution:
 Keywords:  has-patch has-screenshots dev-feedback  |
----------------------------------------------------+---------------------

Comment (by desrosj):

 While I do like the the idea of making the process of writing, collecting,
 and publishing dev notes easier, I am not sure this is the best way to
 accomplish that.

 IMO, this field will be reinventing the wheel. Google Docs is really the
 best way to collaborate on a document such as a post like this. There are
 revisions, comments, suggested changes, etc., and all of this works really
 well. It also creates a lot more noise within update emails. Not everyone
 that was interested in contributing to the ticket will be interested in
 contributing to the dev note.

 What if, instead of a full fledged WYSIWYG field, we just add a simple
 text field for a URL to the draft dev note on Google Docs? It solves many
 of the points brought up. It makes the process more public and
 transparent, it's easy to know who and where the draft is, who had
 participated and contributed, etc. The draft can be created and linked to
 at any point (so the primary contributor could draft it while fresh in
 their mind). It also allows contributors to follow along if they wish by
 starring the document on Google Drive.

 When the dev note is finally published, the link to the draft document can
 be replaced with the final Make/Core blog post.

 For clarity, the field should be accompanied by a description linking to
 the [https://make.wordpress.org/core/handbook/best-practices/post-comment-
 guidelines/ Post & Comment Guidelines page] in the Core handbook.

 Alternatively, if we want to avoid embracing Google Docs as an external
 means to collaborate on these posts, we could encourage using draft posts
 on Make Core for creating and refining the post. Though I don't think I
 like that because a) it requires a public preview (which expires after a
 given time frame), and b) may cause confusion if someone shares a public
 preview link and someone is not aware that the post has not officially
 been published.

 If we choose to add a URL field, we could create a report that lists all
 `needs-dev-note` tickets showing information like component, owner, and
 URL to the draft, etc. This could maybe help replace the spreadsheets that
 have been used recently.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5118#comment:12>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org