[wp-trac] [WordPress Trac] #12423: Include default code editor

WordPress Trac noreply at wordpress.org
Thu Mar 23 13:22:54 UTC 2017


#12423: Include default code editor
-----------------------------+----------------------------
 Reporter:  scribu           |       Owner:  afercia
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  4.8
Component:  Editor           |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:  accessibility
-----------------------------+----------------------------

Comment (by afercia):

 Replying to [comment:114 jnylen0]:
 > My other questions from comment:109 still stand, then:
 > What was the discussion that led to this guideline?
 You should ask the 6 project leads :) or some of the most experienced
 contributors. Those principles are there way before I started contributing
 so I wasn't there when they were decided.

 > Has it been followed for other features?
 Since I'm contributing to the project, I've often seen new feature
 proposals being not accepted based on that principle and then considered
 "plugin territory".

 > It would be an interesting exercise to look through major features
 merged in the past ~2 years and try to determine (1) whether such data was
 collected beforehand
 Rarely, and that's one of my points: at least some of the most important
 decisions should be based on data

 > and (2) whether 80% of people actually use the feature
 This should apply to all new features and require some form of data
 collecting. I think there's an ongoing discussion on this topic. Re: the
 Editor, I think the ongoing survey http://wordpressdotorg.polldaddy.com/s
 /editor-survey will reserve some surprises about which are the editor
 features users really care about :)

--
Ticket URL: <https://core.trac.wordpress.org/ticket/12423#comment:115>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list