[wp-meta] [Making WordPress.org] #3317: Add new `coding-standards` focus to core Trac

[Making WordPress.org]

#3317: Add new `coding-standards` focus to core Trac
--------------------+------------------
 Reporter:  netweb  |       Owner:
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+------------------

Comment (by netweb):

 Replying to [comment:2 jrf]:
 > As suggested
 [https://wordpress.slack.com/archives/C18723MQ8/p1512808420000020?thread_ts=1512768357.000481&cid=C18723MQ8
 slightly further on in the Slack thread], maybe this now focus label
 should be called "technical-debt" instead to also cover missing unit
 tests, missing documentation, outdated dependencies etc.

 There are already existing Trac workflows to cover these:

 * "missing documentation" has the `docs` focus ->
 https://core.trac.wordpress.org/query?status=!closed&focuses=~docs
 * "outdated dependencies" has the `Build/ Test Tools` component ->
 https://core.trac.wordpress.org/query?status=!closed&component=Build%2FTest+Tools
 * "missing unit tests" is covered by either the component that it relates
 to or if more general then also the "Build/ Test Tools" component


 Due to the level of "technical debt" WordPress carris I don't think the
 introduction of a core focus of that name should be introduced. It implies
 that a new core focus on reducing "technical debt" has been introduced and
 sanctioned when this is not the actual case. I think we are all for
 reducing WordPress' technical debt, but there will be, for at least for
 the mid-term significant technical debt remain in WordPress so that
 WordPress just works for the majority of users.

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