[wp-meta] [Making WordPress.org] #287: Core Trac "focuses"

Making WordPress.org noreply at wordpress.org
Tue Jan 21 06:51:36 UTC 2014


#287: Core Trac "focuses"
---------------------+------------------
  Reporter:  nacin   |      Owner:
      Type:  defect  |     Status:  new
  Priority:  normal  |  Component:  Trac
Resolution:          |   Keywords:
---------------------+------------------

Comment (by nacin):

 I looked through everything in the performance component and had no issue
 immediately identifying the component each ticket should be moved to.

 I had more trouble with multisite. What do you have in mind? While the new
 Bootstrap/Load component can handle so much of ms-settings et al, many of
 these tickets have to do with inherently multisite concepts. The network
 admin is a good example of something that sould probably keep its
 component. A new Login/Registration component would cover a lot of others.
 What about tickets citing My Sites or get_blog_details() or
 switch_to_blog() etc? So My Sites could be snuck into Network Admin, but
 would we need a new "Networks/Sites" component to handle the rest?

 FWIW, I'm happy to just work with you to convert everything over. If we
 end up needing to roll it back, that's easy.

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


More information about the wp-meta mailing list