[wp-trac] [WordPress Trac] #35417: Audit "blog" usage in inline docs

[WordPress Trac]

#35417: Audit "blog" usage in inline docs
--------------------------------+------------------------------
 Reporter:  ericlewis           |       Owner:
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  4.5
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  dev-feedback        |     Focuses:  docs, multisite
--------------------------------+------------------------------
Changes (by ericlewis):

 * keywords:  has-patch => dev-feedback


Comment:

 I've removed the `good-first-bug` because I think some hard decisions need
 to be made with some of what's left.

 Should we call
 [https://github.com/WordPress/WordPress/blob/22467e840fd4ad9d41357a705078955a2d70112d
 /wp-includes/wp-db.php#L243 $wpdb->blogid Site ID]?
 [https://github.com/WordPress/WordPress/blob/22467e840fd4ad9d41357a705078955a2d70112d
 /wp-includes/wp-db.php#L417 Multisite "sites" table]?
 [https://github.com/WordPress/WordPress/blob/22467e840fd4ad9d41357a705078955a2d70112d
 /wp-includes/wp-db.php#L935 site prefix]?

 Similarly in the caching API, e.g.
 [https://github.com/WordPress/WordPress/blob/22467e840fd4ad9d41357a705078955a2d70112d
 /wp-includes/cache.php#L205 referring to "blog cache groups"]. Should
 these be site cache groups?

 I ask because some of these terms are so ingrained in our nomenclature.
 I'm leaning towards changing all of them, which will hopefully change the
 vocabulary we use. e.g. I think "site prefix" is a more usable term than
 "blog prefix."

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