From noreply at wordpress.org  Sat Jun  1 01:58:56 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Jun 2019 01:58:56 -0000
Subject: [wp-meta] [Making WordPress.org] #4485: Glossary not showing
 for WPTV
In-Reply-To: <051.60dd4f3f95ce6a4be6c6d08039225926@wordpress.org>
References: <051.60dd4f3f95ce6a4be6c6d08039225926@wordpress.org>
Message-ID: <066.6ed4e4790a698153fe0d625514fdf0e2@wordpress.org>

#4485: Glossary not showing for WPTV
--------------------------------------+---------------------
 Reporter:  casiepa                   |       Owner:  (none)
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Activated the plugin.

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

From noreply at wordpress.org  Sat Jun  1 04:53:05 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Jun 2019 04:53:05 -0000
Subject: [wp-meta] [Making WordPress.org] #4479: Updating WordPress page
 - links without href attribute
In-Reply-To: <051.b7ee242d3c6cc76a72b42dafd63a2bb6@wordpress.org>
References: <051.b7ee242d3c6cc76a72b42dafd63a2bb6@wordpress.org>
Message-ID: <066.c7616f8c3da724e80277aa24e240f6af@wordpress.org>

#4479: Updating WordPress page - links without href attribute
---------------------+---------------------
 Reporter:  Rahmohn  |       Owner:  (none)
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  HelpHub  |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------
Changes (by coffee2code):

 * status:  new => closed
 * resolution:   => fixed


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

From noreply at wordpress.org  Sat Jun  1 07:11:12 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Jun 2019 07:11:12 -0000
Subject: [wp-meta] [Making WordPress.org] #4489: Tabs for content page read
 <title>content title &#8211; company title</title>
Message-ID: <053.f3c6a27ea3a982af647f8cfe30769635@wordpress.org>

#4489: Tabs for content page read <title>content title &#8211; company
title</title>
-----------------------+--------------------
 Reporter:  susanfla2  |      Owner:  (none)
     Type:  defect     |     Status:  new
 Priority:  normal     |  Milestone:
Component:  General    |   Keywords:
-----------------------+--------------------
 I want to change the tabs on my content pages to read my company name and
 not a blog title - company name.  I have fixed this for the login pages
 and the admin globally.  But, what is the php file that I need to fix for
 the content page tabs?  By tabs I mean the ones you see in the browser.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4489>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun  1 07:13:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Jun 2019 07:13:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4489: Tabs for content page
 read <title>content title &#8211; company title</title>
In-Reply-To: <053.f3c6a27ea3a982af647f8cfe30769635@wordpress.org>
References: <053.f3c6a27ea3a982af647f8cfe30769635@wordpress.org>
Message-ID: <068.8c5f1cf21ca5753f4a64e1d72ce801da@wordpress.org>

#4489: Tabs for content page read <title>content title &#8211; company
title</title>
-----------------------+----------------------
 Reporter:  susanfla2  |       Owner:  (none)
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:  invalid
 Keywords:             |
-----------------------+----------------------
Changes (by Otto42):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Hello, this is the meta trac, where we trac bugs and problems and changes
 to the WordPress.org websites and associated properties. It is not a
 support forum.

 If you need assistance, then please post on the WordPress support forums
 here: https://wordpress.org/support/

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

From noreply at wordpress.org  Sat Jun  1 16:26:23 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Jun 2019 16:26:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3954: Support Forums: Add
 counters to moderation links
In-Reply-To: <058.4e92f9a36b37dbfdb70bb520a6b83468@wordpress.org>
References: <058.4e92f9a36b37dbfdb70bb520a6b83468@wordpress.org>
Message-ID: <073.1ca257cc7f28dc49c019d142231177c2@wordpress.org>

#3954: Support Forums: Add counters to moderation links
----------------------------+-----------------------------
 Reporter:  SergeyBiryukov  |       Owner:  SergeyBiryukov
     Type:  enhancement     |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => accepted


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

From noreply at wordpress.org  Sat Jun  1 20:06:31 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Jun 2019 20:06:31 -0000
Subject: [wp-meta] [Making WordPress.org] #4487: Set the codex to
 readonly
In-Reply-To: <051.3cea0a15d04c8a963647fe1d9be86eac@wordpress.org>
References: <051.3cea0a15d04c8a963647fe1d9be86eac@wordpress.org>
Message-ID: <066.798beb028e160d90ab147b397056ffb3@wordpress.org>

#4487: Set the codex to readonly
---------------------+---------------------
 Reporter:  Clorith  |       Owner:  (none)
     Type:  task     |      Status:  new
 Priority:  normal   |   Milestone:
Component:  HelpHub  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by Clorith):

 There is already a rollout plan at
 https://make.wordpress.org/polyglots/2019/02/25/helphub-localisation-plan/
 and given it's been 3 months, it would probably be good to get some input
 on the progression there (cc @kenshino).

 I definitely get your point about locale-specific pages, I have done some
 quick checking, and in the past 90 days, the outtake is (in no particular
 order):

 - A few people using the `Talk` feature to try and get support and/or
 backlinks
 - HelpHub redirects added
 - Edits to English articles by various individuals, these should all be on
 HelpHub by now and means someone should probably double-check the content
 now?
 - Edits to function references (which are all on DevHub and have been for
 some time)
 - Edits to .org specific references (API descriptions, perhaps these
 should get an official space on DevHub?)
 - Various kinds of spam edits or page/profile creations
 - One rosetta page created, not counting the `Talk` feature

 I do, however, agree we should get #2575 sorted, as a requirement for the
 migration to move forward, we should probably bump the importance of that.

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

From noreply at wordpress.org  Mon Jun  3 01:09:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 01:09:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4447: Create an easier way to
 trac contributions across GitHub and Trac
In-Reply-To: <051.ee9b37492321f4e8e2ffcedf018f5536@wordpress.org>
References: <051.ee9b37492321f4e8e2ffcedf018f5536@wordpress.org>
Message-ID: <066.056467c2289dcf66175437a6318e7aed@wordpress.org>

#4447: Create an easier way to trac contributions across GitHub and Trac
-------------------------+---------------------
 Reporter:  desrosj      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by dd32):

 Replying to [comment:10 desrosj]:
 > Are we concerned at all with verification of ownership? For example,
 nothing stops me from using @aduth's GitHub username on my .org profile.
 >
 > Maybe there could be a verification step where an email is sent to the
 user's GitHub email for confirmation.

 The "simple" solution for that is using something like "Link my Github
 account" instead of a plain-text field, we'd then do an OAuth flow to
 [https://developer.github.com/apps/building-oauth-apps/understanding-
 scopes-for-oauth-apps/ allow access] for either `user:email` or `[no
 scope]` (allows access to public data only). That would then be able to
 provide an authenticated `dd32 on WordPress is Github:dd32` scenario which
 can then populate that profile field.

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

From noreply at wordpress.org  Mon Jun  3 02:50:55 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 02:50:55 +0000 (UTC)
Subject: [wp-meta] [8904]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/libs/site-search/jetpack-search.php:
 Plugin Directory: Search: Use `wp_json_encode()` to handle non-UTF8 queries
 better.
Message-ID: <20190603025055.216FD1B0052B@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/e0b796c5/attachment.html>

From noreply at wordpress.org  Mon Jun  3 03:21:31 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 03:21:31 +0000 (UTC)
Subject: [wp-meta] [8905]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/trac-notifications/trac-components.php:
 Trac Notifications: Handle API failures in the
 https://make.wordpress.org/core/components/ UI.
Message-ID: <20190603032131.1DAF71B0052B@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/d165c83e/attachment.html>

From noreply at wordpress.org  Mon Jun  3 12:33:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 12:33:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4490: Twitter: use video
 thumbnail as picture
Message-ID: <051.9c1b7c1147eb1db0ff74bd34b0a3fa28@wordpress.org>

#4490: Twitter: use video thumbnail as picture
--------------------------+--------------------
 Reporter:  casiepa       |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+--------------------
 When a video is published, a tweet is sent from
 https://twitter.com/WordPressTV
 The current picture used by the tweet is just a black box.
 It would be nicer to use the Video Thumbnail as image for twitter.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4490>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 14:33:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 14:33:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4491: Archive page shows 2
 columns instead of 3 at certain media queries
Message-ID: <054.eebc6b0b5da5a73f5283f8b17c1f7366@wordpress.org>

#4491: Archive page shows 2 columns instead of 3 at certain media queries
------------------------+-----------------------------------------
 Reporter:  milana_cap  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  HelpHub     |   Keywords:  needs-patch has-screenshots
------------------------+-----------------------------------------
 CSS used for these columns should be changed to something more reliable
 and up to date. This is what we have now:


 {{{
 @media (min-width: 48em)
 .three-up .archive-block, .three-up > div {
     display: inline-block;
     vertical-align: top;
     width: 30%;
     margin-right: 4.5%;
     font-size: 0.8rem;
 }

 .three-up .archive-block:nth-child(3n), .three-up > div:nth-child(3n) {
     margin-right: 0;
 }
 }}}

 Using either Flexbox or CSS Grid would make columns behave better.

 One of effected pages: https://wordpress.org/support/category/getting-
 started/

 Screenshot:

 [[Image(https://user-
 images.githubusercontent.com/7957680/41554497-a217d596-72fa-
 11e8-9c20-2500a7d880c8.jpg)]]

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4491>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 14:36:38 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 14:36:38 +0000 (UTC)
Subject: [wp-meta] [8906]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-participation-notifier/wordcamp-participation-notifier.php:
 WordCamp: Rename methods to reduce ambiguity.
Message-ID: <20190603143638.78D841B004E3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/91bd1951/attachment.html>

From noreply at wordpress.org  Mon Jun  3 14:36:46 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 14:36:46 +0000 (UTC)
Subject: [wp-meta] [8907]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-participation-notifier/wordcamp-participation-notifier.php:
 WC: Refactor participant notifier to fix design flaw.
Message-ID: <20190603143646.969CF1B004E3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/13ac244f/attachment-0001.html>

From noreply at wordpress.org  Mon Jun  3 14:36:53 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 14:36:53 +0000 (UTC)
Subject: [wp-meta] [8908]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-participation-notifier/wordcamp-participation-notifier.php:
 WC Participant Notifier: Code review fixes.
Message-ID: <20190603143653.45BC31B004E3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/aeeeeeac/attachment.html>

From noreply at wordpress.org  Mon Jun  3 14:37:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 14:37:38 -0000
Subject: [wp-meta] [Making WordPress.org] #4492: Homepage: Forums text needs
 to match size of other sections
Message-ID: <054.f636f02ff2be08e5531c5a5453471787@wordpress.org>

#4492: Homepage: Forums text needs to match size of other sections
------------------------+-----------------------------------------
 Reporter:  milana_cap  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  HelpHub     |   Keywords:  needs-patch has-screenshots
------------------------+-----------------------------------------
 The "Support Forums" module displays larger text than the other modules.
 They should match in size with one another.

 Forums:
 [[Image(https://user-images.githubusercontent.com/617986/41545510
 -32d1024a-72d0-11e8-8f63-b0c6a8b15e84.png)]]

 Other:
 [[Image(https://user-
 images.githubusercontent.com/617986/41545518-37fed5d0-72d0-11e8-8623-f5fe0ccf9993.png)]]

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4492>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 14:44:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 14:44:00 -0000
Subject: [wp-meta] [Making WordPress.org] #703: Keep track of which
 WordCamps each profile has spoken at and organized
In-Reply-To: <051.eb7c52567af1470eb803871969600e12@wordpress.org>
References: <051.eb7c52567af1470eb803871969600e12@wordpress.org>
Message-ID: <066.83752d96923ab14b1024eeb72e873759@wordpress.org>

#703: Keep track of which WordCamps each profile has spoken at and organized
-------------------------------------+---------------------
 Reporter:  iandunn                  |       Owner:  (none)
     Type:  defect                   |      Status:  closed
 Priority:  high                     |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  fixed
 Keywords:                           |
-------------------------------------+---------------------
Changes (by vedjain):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 Fixed in r8907

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

From noreply at wordpress.org  Mon Jun  3 14:44:44 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 14:44:44 -0000
Subject: [wp-meta] [Making WordPress.org] #4493: Homepage: Height adjustment
Message-ID: <054.2e6aa0ed3a8f591b69e47081d6190d0c@wordpress.org>

#4493: Homepage: Height adjustment
------------------------+-----------------------------------------
 Reporter:  milana_cap  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  HelpHub     |   Keywords:  needs-patch has-screenshots
------------------------+-----------------------------------------
 The vertical rhythm needs to be consistent on the homepage. If the height
 of these two spaces could match, that would be great!

 [[Image(https://user-images.githubusercontent.com/617986/41545330-cd9d1cc4
 -72cf-11e8-8aef-150a8f7a5a12.png)]]

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4493>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 15:34:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 15:34:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3309: Feed shows posts while
 in 'Coming soon' mode
In-Reply-To: <051.515e92b4391417a92148e667bb1c137b@wordpress.org>
References: <051.515e92b4391417a92148e667bb1c137b@wordpress.org>
Message-ID: <066.fdae279d8199d0254718afb7e90ad589@wordpress.org>

#3309: Feed shows posts while in 'Coming soon' mode
-------------------------------------+-----------------------
 Reporter:  casiepa                  |       Owner:  (none)
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+-----------------------
Changes (by casiepa):

 * owner:  casiepa => (none)


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

From noreply at wordpress.org  Mon Jun  3 15:48:42 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 15:48:42 -0000
Subject: [wp-meta] [Making WordPress.org] #4494: Posts published on a
 "Coming Soon" mode WordCamp site appear on profile stream
Message-ID: <047.6bd599c1def856486af039d8d652b67a@wordpress.org>

#4494: Posts published on a "Coming Soon" mode WordCamp site appear on profile
stream
-------------------------------------+-------------------------
 Reporter:  Nao                      |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  needs-patch
-------------------------------------+-------------------------
 While your WordCamp site is "Coming Soon" mode, published posts on the
 site still show up under the author's profile page (e.g. see
 https://profiles.wordpress.org/mimitips/ ).

 Steps to reproduce:

 1. Set a WordCamp site to "Coming Soon" mode
 2. Publish a new post
 3. Check your WordPress.org profile activity stream

 Could be related: #3309

 If this is not something we are going to fix, we should at least say (in
 the WordCamp organizer handbook) that posts published during Coming Soon
 mode will be visible in feeds.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4494>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 15:55:23 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 15:55:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3309: Feed shows posts while
 in 'Coming soon' mode
In-Reply-To: <051.515e92b4391417a92148e667bb1c137b@wordpress.org>
References: <051.515e92b4391417a92148e667bb1c137b@wordpress.org>
Message-ID: <066.a206ba6929448ff251900c0202e3132c@wordpress.org>

#3309: Feed shows posts while in 'Coming soon' mode
-------------------------------------+-----------------------
 Reporter:  casiepa                  |       Owner:  (none)
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+-----------------------

Comment (by casiepa):

 Maybe related: https://meta.trac.wordpress.org/ticket/4494

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

From noreply at wordpress.org  Mon Jun  3 16:01:20 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:01:20 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility of
 the Trac ticket Keywords and Focuses
Message-ID: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------+-----------------------------
 Reporter:  afercia  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  Trac     |   Keywords:  has-screenshots
---------------------+-----------------------------
 I'd like to propose a few improvements for the Keywords and Focuses user
 interface within the ticket properties section. Here's how they currently
 look like:

 [[Image(http://cldup.com/6p5TmD7gXw.png)]]

 Color contrast (personally, I struggle to see the focuses buttons text),
 and many other things can be improved, for example:

 - the "manual" link is barely visible
 - it can't be operated with a keyboard
 - it should be a button
 - accessibility of the "X" buttons to remove keywords: they're just empty
 links
 - keyboard interaction with the custom keywords input field can be
 improved
 - focuses buttons color contrast can be improved
 - focuses buttons should be buttons
 - their "pressed" state should be communicated semantically


 Patch incoming. Please consider I don't have a running local environment
 for testing. I've managed to build a SVN diff and would greatly appreciate
 some testing. Any feedback is welcome.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4495>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 16:21:44 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:21:44 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.b025ccbfcef1a44441c431ae86219988@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
-----------------------------+---------------------
 Reporter:  afercia          |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+---------------------
Changes (by afercia):

 * Attachment "4495.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4495>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 16:26:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:26:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.4b68ebcfb95f42ec447ada2ade47da2b@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+---------------------
 Reporter:  afercia                    |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by afercia):

 * keywords:  has-screenshots => has-screenshots has-patch


Comment:

 Trying to recap what [attachment:"4495.diff"] does:

 "Manual" button:
 - changes the link to a button element
 - adds an aria-label "Manual keyword" to clarify its purpose
 - adds an aria-expanded attribute to make screen readers users understand
 something in the page opened
 - styles a bit the button and improves color contrast

 Remove keywords "X" buttons:
 - changes the empty links to buttons with meaningful aria-labels
 - handles focus to avoid focus losses when removing the keywords

 Custom keywords input field:
 - adds an aria-label to label the field
 - handles keyboard interaction when pressing Enter and Escape: both Enter
 and Escape populate the keywords and hide the field
 - attaches the field `change` event on initialization: previously it was
 attached each time the "manual" button was clicked

 Focuses:
 - makes this section look the same on the new ticket and on the ticket
 pages: previously they looked different (see attached screenshots)
 - wraps the buttons in a fieldset element with a legend "Focuses:"
 - makes the buttons real `<button>` elements
 - adds an aria-pressed attribute to communicate the buttons state
 - styles the buttons to improve color contrast and provide better hover /
 focus styles

 General:
 - cleans up a bit the CSS

 Note: I'm assuming there's no need for proper l10n like in core, as Trac
 is always in English.

 /Cc @SergeyBiryukov

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

From noreply at wordpress.org  Mon Jun  3 16:26:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:26:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.1dd64052feaaf4210cae04ee12fd6dad@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+---------------------
 Reporter:  afercia                    |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by afercia):

 * Attachment "01 new ticket before.png" added.

 New ticket before

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4495>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 16:26:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:26:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.c61f5401d743d74600a8752e8f866ec2@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+---------------------
 Reporter:  afercia                    |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by afercia):

 * Attachment "02 new ticket after.png" added.

 New ticket after

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4495>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 16:27:14 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:27:14 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.39a55e578b0eff2a68b3f4b04876035c@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+---------------------
 Reporter:  afercia                    |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by afercia):

 * Attachment "03 ticket before.png" added.

 Ticket page before

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4495>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 16:27:27 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:27:27 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.56105cef9d7f1c23a357bef3f5e4702d@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+---------------------
 Reporter:  afercia                    |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by afercia):

 * Attachment "04 ticket after.png" added.

 Ticket page after

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4495>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 16:41:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:41:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3329: Add filter to
 translate.wp.org on Plugins/Themes listing to order by last activity date
In-Reply-To: <059.57bc08053e33543b795da75376b64737@wordpress.org>
References: <059.57bc08053e33543b795da75376b64737@wordpress.org>
Message-ID: <074.ec50f75eb19ac9fb4d84e8f43be54515@wordpress.org>

#3329: Add filter to translate.wp.org on Plugins/Themes listing to order by last
activity date
--------------------------------------+---------------------
 Reporter:  garrett-eclipse           |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by maximejobin):

 I totally agree with this feature. When I find out translations made for a
 plugin/theme made 8 months ago and nothing was accepted, it feels like we
 lost an opportunity to have a contributor that will continue to translate.

 If I spent time on something that would go unnoticed for 8 months, I would
 probably not translate anything else.

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

From noreply at wordpress.org  Mon Jun  3 16:45:31 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:45:31 -0000
Subject: [wp-meta] [Making WordPress.org] #2320: Global stats for
 GlotPress to identify possible future GTE
In-Reply-To: <052.130c2ddcdc33c84d06ef71fa74c0500d@wordpress.org>
References: <052.130c2ddcdc33c84d06ef71fa74c0500d@wordpress.org>
Message-ID: <067.4d458d99af8107252cde7f28dbd2a049@wordpress.org>

#2320: Global stats for GlotPress to identify possible future GTE
--------------------------------------+-------------------------
 Reporter:  xavivars                  |       Owner:  tellyworth
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion has-patch     |
--------------------------------------+-------------------------

Comment (by maximejobin):

 I really like that feature. More than that, it could also add gamification
 to the process and make translations and approval like a game.

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

From noreply at wordpress.org  Mon Jun  3 16:58:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 16:58:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4496: Make "Save" and "Approve"
 the same
Message-ID: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>

#4496: Make "Save" and "Approve" the same
--------------------------------------+--------------------
 Reporter:  maximejobin               |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 I'm a LTE. I spend most of my time accepting and editing translations made
 by others.

 If I see a string and want it as is, I must "Accept".
 If I edit a string, I must "Save".

 Otherwise, it displays an error message.

 I think that no matter if I click on "Accept" or "Save", the wanted
 behaviour should be automatically detected.

 This is simple, not confusing and would save me (and probably others) a
 lot of time.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4496>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun  3 17:15:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 17:15:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4496: Make "Save" and
 "Approve" the same
In-Reply-To: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
References: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
Message-ID: <070.81835a3270a13bab0b563dc3f6257e44@wordpress.org>

#4496: Make "Save" and "Approve" the same
--------------------------------------+---------------------
 Reporter:  maximejobin               |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by tobifjellner):

 This request is about things inside GlotPress and would therefore be
 better posted at https://github.com/GlotPress/GlotPress-WP/issues/new
 Actually, similar functionality is already available if you are able to
 use the browser extension GlotDict https://github.com/Mte90/GlotDict

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

From noreply at wordpress.org  Mon Jun  3 17:33:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 17:33:24 -0000
Subject: [wp-meta] [Making WordPress.org] #4496: Make "Save" and
 "Approve" the same
In-Reply-To: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
References: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
Message-ID: <070.44378c8545a37df7b1c7bb9038702857@wordpress.org>

#4496: Make "Save" and "Approve" the same
--------------------------------------+---------------------
 Reporter:  maximejobin               |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by maximejobin):

 I wasn't sure if this was the right place. You can close this as I will
 post it at the right place. Thank you!

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

From noreply at wordpress.org  Mon Jun  3 17:48:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 17:48:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4496: Make "Save" and
 "Approve" the same
In-Reply-To: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
References: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
Message-ID: <070.1ec728284a1adff804e7c7c81252d28b@wordpress.org>

#4496: Make "Save" and "Approve" the same
--------------------------------------+--------------------------------
 Reporter:  maximejobin               |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  reported-upstream
 Keywords:                            |
--------------------------------------+--------------------------------
Changes (by tobifjellner):

 * status:  new => closed
 * resolution:   => reported-upstream


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

From noreply at wordpress.org  Mon Jun  3 20:33:30 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 20:33:30 +0000 (UTC)
Subject: [wp-meta] [8909]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Grant
 announce privilege to justinahinon and marybaum for #core (as WP 5.2.2
 co-leads), per audrasjb.
Message-ID: <20190603203330.525671B004E3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/3f6893b0/attachment.html>

From noreply at wordpress.org  Mon Jun  3 20:46:23 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 20:46:23 +0000 (UTC)
Subject: [wp-meta] [8910]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer:
 Developer: Add ability for second-level handbook sidebar menu items with
 sub-items to be collapsible/expandable.
Message-ID: <20190603204623.18CF81B004E3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/6779f8f3/attachment-0001.html>

From noreply at wordpress.org  Mon Jun  3 20:46:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 20:46:24 -0000
Subject: [wp-meta] [Making WordPress.org] #4476: Make Handbook sidebar
 menu collapsible
In-Reply-To: <051.a49bff5260acb809a3d340fbe2c220df@wordpress.org>
References: <051.a49bff5260acb809a3d340fbe2c220df@wordpress.org>
Message-ID: <066.9ecef81c45d0ac16eb2375a84a9deed2@wordpress.org>

#4476: Make Handbook sidebar menu collapsible
-------------------------+--------------------------
 Reporter:  welcher      |       Owner:  coffee2code
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:  fixed
 Keywords:  has-patch    |
-------------------------+--------------------------
Changes (by coffee2code):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8910" 8910]:
 {{{
 #!CommitTicketReference repository="" revision="8910"
 Developer: Add ability for second-level handbook sidebar menu items with
 sub-items to be collapsible/expandable.

 Nested menu items are all initially collapsed.

 Props welcher.
 Fixes #4476.
 }}}

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

From noreply at wordpress.org  Mon Jun  3 20:52:11 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 20:52:11 +0000 (UTC)
Subject: [wp-meta] [8911]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc/parser.php:
 Developer: Prevent files in `wp-includes/random_compat/` from getting
 parsed.
Message-ID: <20190603205211.8CC741B004E3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/9d898ac7/attachment.html>

From noreply at wordpress.org  Mon Jun  3 20:59:55 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Jun 2019 20:59:55 +0000 (UTC)
Subject: [wp-meta] [8912]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/functions.php:
 Developer: Bump CSS and JS version for cache bust.
Message-ID: <20190603205955.D63751B004ED@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190603/6a990458/attachment.html>

From noreply at wordpress.org  Mon Jun  3 21:04:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 21:04:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4476: Make Handbook sidebar
 menu collapsible
In-Reply-To: <051.a49bff5260acb809a3d340fbe2c220df@wordpress.org>
References: <051.a49bff5260acb809a3d340fbe2c220df@wordpress.org>
Message-ID: <066.2078c3a3bb769d8250e1b22ff0c3ad45@wordpress.org>

#4476: Make Handbook sidebar menu collapsible
-------------------------+--------------------------
 Reporter:  welcher      |       Owner:  coffee2code
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:  fixed
 Keywords:  has-patch    |
-------------------------+--------------------------

Comment (by coffee2code):

 @welcher: Thanks for the patch!

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

From noreply at wordpress.org  Mon Jun  3 21:04:29 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 21:04:29 -0000
Subject: [wp-meta] [Making WordPress.org] #4488: Metabox Doc in showing
 <br> tag.
In-Reply-To: <056.12f6a0ebc6c331400d24094662b129a3@wordpress.org>
References: <056.12f6a0ebc6c331400d24094662b129a3@wordpress.org>
Message-ID: <071.183c1f1d930b2cbf3111e1d02a2fd381@wordpress.org>

#4488: Metabox Doc in showing <br> tag.
--------------------------+---------------------
 Reporter:  hardipparmar  |       Owner:  (none)
     Type:  defect        |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Handbooks     |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by coffee2code):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fix
 [https://github.com/WordPress/gutenberg/commit/42afdbf879d8e2a7de4b158d053d3449e2d68b3b
 committed in GitHub] by @mkaz.

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

From noreply at wordpress.org  Mon Jun  3 21:50:30 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 21:50:30 -0000
Subject: [wp-meta] [Making WordPress.org] #4469: Plugin information API:
 Prioritize 100% matched slug in search
In-Reply-To: <056.0958277a52370c6dc6e18b523bb9bd4a@wordpress.org>
References: <056.0958277a52370c6dc6e18b523bb9bd4a@wordpress.org>
Message-ID: <071.57009388873a9117b7d2f829e29722f0@wordpress.org>

#4469: Plugin information API: Prioritize 100% matched slug in search
--------------------------+-------------------------
 Reporter:  tobifjellner  |       Owner:  tellyworth
     Type:  enhancement   |      Status:  reviewing
 Priority:  normal        |   Milestone:
Component:  API           |  Resolution:
 Keywords:                |
--------------------------+-------------------------

Comment (by coffee2code):

 Replying to [ticket:4469 tobifjellner]:
 > Next: if, after deleting any trailing spaces, there are no spaces in the
 search argument, then check if there's any valid plugin with exactly this
 slug, then include this plugin as match number 1.

 My take is that searching for a slug-like term without a hyphen (e.g.
 "seo") should not feature a plugin with a matching slug since it isn't
 clear if user is searching on a generic term or a plugin by slug. However,
 a slug-like term with a hyphen (e.g. "best-seo") ''should'' feature a
 plugin that 100% matches the slug (and is definitely a different search
 than "best seo").

 A search for a fully-qualified Plugin Directory URL (as also proposed in
 the ticket) should definitely feature the associated plugin, assuming we
 want to support specifying a Plugin Directory URL.

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

From noreply at wordpress.org  Mon Jun  3 22:50:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Jun 2019 22:50:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.9a2834269f476573e105c99f1eb50c16@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+-----------------------------
 Reporter:  afercia                    |       Owner:  SergeyBiryukov
     Type:  defect                     |      Status:  reviewing
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => reviewing


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

From noreply at wordpress.org  Tue Jun  4 02:01:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 02:01:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4469: Plugin information API:
 Prioritize 100% matched slug in search
In-Reply-To: <056.0958277a52370c6dc6e18b523bb9bd4a@wordpress.org>
References: <056.0958277a52370c6dc6e18b523bb9bd4a@wordpress.org>
Message-ID: <071.2bed594153e23938e2cec3ac60c041b7@wordpress.org>

#4469: Plugin information API: Prioritize 100% matched slug in search
--------------------------+-------------------------
 Reporter:  tobifjellner  |       Owner:  tellyworth
     Type:  enhancement   |      Status:  reviewing
 Priority:  normal        |   Milestone:
Component:  API           |  Resolution:
 Keywords:                |
--------------------------+-------------------------

Comment (by dd32):

 Replying to [comment:5 coffee2code]:
 > My take is that searching for a slug-like term without a hyphen (e.g.
 "seo") should not feature a plugin with a matching slug since it isn't
 clear if user is searching on a generic term or a plugin by slug. However,
 a slug-like term with a hyphen (e.g. "best-seo") ''should'' feature a
 plugin that 100% matches the slug (and is definitely a different search
 than "best seo").

 My take is a little different - I think we should let the search engine
 handle it.
 It already has a slug-match boost which pushes plugins much higher in the
 ranking, but it doesn't always put it into first position as other plugins
 still match the term better based on the other ranking factors.
 For most plugins it seems that slug boost already works, one example of a
 plugin where it doesn't is `debug-bar-console` which is half way down
 page2, because it's really not the best plugin to match it (based on last-
 updated, reviews, support, etc. and far more plugins better matching
 "debug bar console")

 After [8902] searching for the exact URL results in it searching for
 'plugin-slug' which at least in the case of health check now results in it
 being in the first position:
 https://wordpress.org/plugins/search/https://wordpress.org/plugins/health-
 check/

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

From noreply at wordpress.org  Tue Jun  4 05:56:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 05:56:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4469: Plugin information API:
 Prioritize 100% matched slug in search
In-Reply-To: <056.0958277a52370c6dc6e18b523bb9bd4a@wordpress.org>
References: <056.0958277a52370c6dc6e18b523bb9bd4a@wordpress.org>
Message-ID: <071.101835191693907ab42a21a0d7c0e88b@wordpress.org>

#4469: Plugin information API: Prioritize 100% matched slug in search
--------------------------+-------------------------
 Reporter:  tobifjellner  |       Owner:  tellyworth
     Type:  enhancement   |      Status:  reviewing
 Priority:  normal        |   Milestone:
Component:  API           |  Resolution:
 Keywords:                |
--------------------------+-------------------------

Comment (by tobifjellner):

 Could a search term that begins with a forward slash {{{/}}} be treated as
 a slug search that should yield only one single result?

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

From noreply at wordpress.org  Tue Jun  4 05:58:21 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 05:58:21 -0000
Subject: [wp-meta] [Making WordPress.org] #3990: Creating an easier way
 to navigate to the Gutenberg handbook
In-Reply-To: <052.52e97b611b9c2f60cfd3b61a42c51e70@wordpress.org>
References: <052.52e97b611b9c2f60cfd3b61a42c51e70@wordpress.org>
Message-ID: <067.073c604d945af1d2ba0c0bd27b0d4330@wordpress.org>

#3990: Creating an easier way to navigate to the Gutenberg handbook
----------------------+---------------------
 Reporter:  boemedia  |       Owner:  (none)
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:  fixed
 Keywords:            |
----------------------+---------------------
Changes (by coffee2code):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Thanks for the suggestion!

 The Gutenberg Handbook referenced in the ticket has since been reorganized
 and relocated to !DevHub at https://developer.wordpress.org/block-editor/,
 a link to which features prominently on the !DevHub home page at
 https://developer.wordpress.org/.

 The Try Gutenberg site itself (https://wordpress.org/gutenberg/) has a few
 inline links on the page that point to pages of the new block editor
 handbook.

 The "Get Involved" page is a listing of contributor teams in the WordPress
 ecosystem. As the block editor falls within the purview of the existing
 core and design teams, those team pages would be more appropriate for
 adding links to resources for block editor-specific contributors.

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

From noreply at wordpress.org  Tue Jun  4 07:02:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 07:02:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3718: Theme Directory: Allow
 minimum WP and PHP version requirement
In-Reply-To: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
References: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
Message-ID: <067.a002e3c7e7544426f3635756e8e28fe9@wordpress.org>

#3718: Theme Directory: Allow minimum WP and PHP version requirement
----------------------------------+-----------------------
 Reporter:  flixos90              |       Owner:  dd32
     Type:  task                  |      Status:  accepted
 Priority:  normal                |   Milestone:
Component:  Theme Directory       |  Resolution:
 Keywords:  has-patch servehappy  |
----------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"8913" 8913]:
 {{{
 #!CommitTicketReference repository="" revision="8913"
 Theme Directory: Add the `requires` and `requires_php` to the Theme
 objects.

 Missed in [8895].
 Props flixos90 for initial work, dd32.
 See #3718.
 }}}

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

From noreply at wordpress.org  Tue Jun  4 07:02:56 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Jun 2019 07:02:56 +0000 (UTC)
Subject: [wp-meta] [8913]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/theme-directory:
 Theme Directory: Add the `requires` and `requires_php` to the Theme
 objects.
Message-ID: <20190604070256.7A3F01B00412@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190604/d8db15ee/attachment-0001.html>

From noreply at wordpress.org  Tue Jun  4 07:04:13 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Jun 2019 07:04:13 +0000 (UTC)
Subject: [wp-meta] [8914]
 sites/trunk/api.wordpress.org/public_html/themes/info: Theme Directory:
 API: Define a constant statically to avoid edgecases.
Message-ID: <20190604070413.54A851B00412@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190604/50cae49a/attachment.html>

From noreply at wordpress.org  Tue Jun  4 07:04:15 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 07:04:15 -0000
Subject: [wp-meta] [Making WordPress.org] #3718: Theme Directory: Allow
 minimum WP and PHP version requirement
In-Reply-To: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
References: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
Message-ID: <067.13bab73c1ce3fb005ad8b7e97a934b8c@wordpress.org>

#3718: Theme Directory: Allow minimum WP and PHP version requirement
----------------------------------+-----------------------
 Reporter:  flixos90              |       Owner:  dd32
     Type:  task                  |      Status:  accepted
 Priority:  normal                |   Milestone:
Component:  Theme Directory       |  Resolution:
 Keywords:  has-patch servehappy  |
----------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"8914" 8914]:
 {{{
 #!CommitTicketReference repository="" revision="8914"
 Theme Directory: API: Define a constant statically to avoid edgecases.

 See #3718.
 }}}

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

From noreply at wordpress.org  Tue Jun  4 07:05:21 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Jun 2019 07:05:21 +0000 (UTC)
Subject: [wp-meta] [8915]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/theme-directory/themes-api.php:
 Theme Directory: API: Change the cache format for
 api.wordpress.org/themes/update-check/.
Message-ID: <20190604070521.8505A1B00412@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190604/8494208b/attachment.html>

From noreply at wordpress.org  Tue Jun  4 07:05:23 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 07:05:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3718: Theme Directory: Allow
 minimum WP and PHP version requirement
In-Reply-To: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
References: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
Message-ID: <067.a481ce7ba1a4a21defa383d857857d22@wordpress.org>

#3718: Theme Directory: Allow minimum WP and PHP version requirement
----------------------------------+-----------------------
 Reporter:  flixos90              |       Owner:  dd32
     Type:  task                  |      Status:  accepted
 Priority:  normal                |   Milestone:
Component:  Theme Directory       |  Resolution:
 Keywords:  has-patch servehappy  |
----------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"8915" 8915]:
 {{{
 #!CommitTicketReference repository="" revision="8915"
 Theme Directory: API: Change the cache format for api.wordpress.org/themes
 /update-check/.

 See #3718.
 }}}

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

From noreply at wordpress.org  Tue Jun  4 07:24:48 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 07:24:48 -0000
Subject: [wp-meta] [Making WordPress.org] #3718: Theme Directory: Allow
 minimum WP and PHP version requirement
In-Reply-To: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
References: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
Message-ID: <067.d27fd1684245d5c93c0a32ed06d78000@wordpress.org>

#3718: Theme Directory: Allow minimum WP and PHP version requirement
----------------------------------+-----------------------
 Reporter:  flixos90              |       Owner:  dd32
     Type:  task                  |      Status:  accepted
 Priority:  normal                |   Milestone:
Component:  Theme Directory       |  Resolution:
 Keywords:  has-patch servehappy  |
----------------------------------+-----------------------

Comment (by dd32):

 This should now be rolled out.

 As it turned out, I missed committing some of the code last week, but it's
 fixed now.

 The API's (info, and update-checks) should now also be returning the data.
 eg:
 https://api.wordpress.org/themes/info/1.2/?action=theme_information&request[slug]=doody

 I've not backfilled the data for older themes, but I'm going to call this
 fixed for now, given the speed at which most themes get updated.

 If going back and importing data for all themes is needed, let me know and
 I'll make it happen.

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

From noreply at wordpress.org  Tue Jun  4 08:11:42 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 08:11:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3990: Creating an easier way
 to navigate to the Gutenberg handbook
In-Reply-To: <052.52e97b611b9c2f60cfd3b61a42c51e70@wordpress.org>
References: <052.52e97b611b9c2f60cfd3b61a42c51e70@wordpress.org>
Message-ID: <067.4d36c702f58035b77a4b62b67f8ea6bc@wordpress.org>

#3990: Creating an easier way to navigate to the Gutenberg handbook
----------------------+---------------------
 Reporter:  boemedia  |       Owner:  (none)
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:  fixed
 Keywords:            |
----------------------+---------------------

Comment (by boemedia):

 Hi @coffee2code,

 Thanks for responding. I hear you when you say Gutenberg spans multiple
 teams and is therefore hard to give it's own space.

 I think links on https://wordpress.org/gutenberg/ should work too, but
 that brings me to the next 'problem': how to discover that page from
 wordpress.org home if you don't know it exists?

 So my main question is: someone coming to wordpress.org and wanting to
 find out more about Gutenberg. What would be the easiest and quickest way
 to get there?

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

From noreply at wordpress.org  Tue Jun  4 10:59:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 10:59:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4496: Make "Save" and
 "Approve" the same
In-Reply-To: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
References: <055.749c1684d7c79853f3bcbdbffc87e123@wordpress.org>
Message-ID: <070.334295f60763464f9f8f9018857c68f2@wordpress.org>

#4496: Make "Save" and "Approve" the same
--------------------------------------+--------------------------------
 Reporter:  maximejobin               |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  reported-upstream
 Keywords:                            |
--------------------------------------+--------------------------------

Comment (by Mte90):

 As replied on https://github.com/GlotPress/GlotPress-WP/issues/1014
 LTE/GTE roles doesn't exists on GlotPress but only on translate.wp.org
 because the platform extended GP.
 So the right place to ask is this ticket system/project :-)

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

From noreply at wordpress.org  Tue Jun  4 16:28:34 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 16:28:34 -0000
Subject: [wp-meta] [Making WordPress.org] #4497: Translate link only shows
 up after plugin is translated
Message-ID: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>

#4497: Translate link only shows up after plugin is translated
------------------------------+--------------------
 Reporter:  iandunn           |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 New plugins in the repository don't have the `Languages: See all n` link
 in the sidebar, because `class-meta.php` has that wrapped in a `if (
 $available_languages )` condition.

 The unintended side-effect of that is that users have no way to know that
 they can translate the plugin, or where to go to do it.

 If no translations exist, the link should still be shown, to encourage
 users to translate. Instead of, `See all n`, it could say something like
 `Needs translation` or something.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4497>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun  4 16:28:57 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 16:28:57 -0000
Subject: [wp-meta] [Making WordPress.org] #4497: Translate link only
 shows up after plugin is translated
In-Reply-To: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
References: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
Message-ID: <066.99fff03374db815cba2ced097b60429d@wordpress.org>

#4497: Translate link only shows up after plugin is translated
------------------------------+---------------------
 Reporter:  iandunn           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  good-first-bug    |
------------------------------+---------------------
Changes (by iandunn):

 * keywords:   => good-first-bug


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

From noreply at wordpress.org  Tue Jun  4 16:42:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 16:42:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4497: Translate link only
 shows up after plugin is translated
In-Reply-To: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
References: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
Message-ID: <066.4828d916b5cf94f4a7eac0f5cd87f229@wordpress.org>

#4497: Translate link only shows up after plugin is translated
------------------------------+---------------------
 Reporter:  iandunn           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  good-first-bug    |
------------------------------+---------------------
Changes (by ocean90):

 * Attachment "call-to-translate.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4497>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun  4 16:43:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 16:43:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4497: Translate link only
 shows up after plugin is translated
In-Reply-To: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
References: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
Message-ID: <066.dff5c687c21079200e6c1b49f7414757@wordpress.org>

#4497: Translate link only shows up after plugin is translated
------------------------------+---------------------
 Reporter:  iandunn           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  good-first-bug    |
------------------------------+---------------------
Changes (by ocean90):

 * Attachment "call-to-translate-2.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4497>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun  4 16:43:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 16:43:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4497: Translate link only
 shows up after plugin is translated
In-Reply-To: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
References: <051.cbfea6e919064c31151ebf066eb56998@wordpress.org>
Message-ID: <066.3e90486d4faf42a4c1a3d1c4e72b33ad@wordpress.org>

#4497: Translate link only shows up after plugin is translated
-------------------------------+---------------------
 Reporter:  iandunn            |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:
Component:  Plugin Directory   |  Resolution:
 Keywords:  close 2nd-opinion  |
-------------------------------+---------------------
Changes (by ocean90):

 * keywords:  good-first-bug => close 2nd-opinion
 * type:  defect => enhancement


Comment:

 This is intentionally because the actual call to action for this is the
 banner (see attached screenshots) on the plugin page.

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

From noreply at wordpress.org  Tue Jun  4 22:20:10 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Jun 2019 22:20:10 +0000 (UTC)
Subject: [wp-meta] [8916] sites/trunk/wordpress.org/public_html/style: wp4:
 Fix display of old-style page titles (as seen in Showcase) at narrow
 viewports.
Message-ID: <20190604222010.44B3B1B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190604/31bc0889/attachment-0001.html>

From noreply at wordpress.org  Tue Jun  4 22:20:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Jun 2019 22:20:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4362: Title bug on /showcase/
In-Reply-To: <056.f459a6a9bf05263c4801f251c2fba4d6@wordpress.org>
References: <056.f459a6a9bf05263c4801f251c2fba4d6@wordpress.org>
Message-ID: <071.81ce47bbdaa685b88fe575be64490fdf@wordpress.org>

#4362: Title bug on /showcase/
--------------------------+---------------------
 Reporter:  themeeverest  |       Owner:  ck3lee
     Type:  defect        |      Status:  closed
 Priority:  low           |   Milestone:
Component:  General       |  Resolution:  fixed
 Keywords:  has-patch     |
--------------------------+---------------------
Changes (by coffee2code):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8916" 8916]:
 {{{
 #!CommitTicketReference repository="" revision="8916"
 wp4: Fix display of old-style page titles (as seen in Showcase) at narrow
 viewports.

 Props ck3lee, themeeverest.
 Fixes #4362.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 04:03:08 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 04:03:08 +0000 (UTC)
Subject: [wp-meta] [8917]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/shortcodes/class-reviews.php:
 Plugin Directory: Always link to the 'pretty permalink' of reviews,
 now that the caches will have cleared.
Message-ID: <20190605040308.2F43E1B0059F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/9ea1a1e6/attachment.html>

From noreply at wordpress.org  Wed Jun  5 04:03:09 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 04:03:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4286: Plugin review URLs
 reference the raw 'p' value
In-Reply-To: <058.07f3962962c77a2d548d81cc0a7ffb7b@wordpress.org>
References: <058.07f3962962c77a2d548d81cc0a7ffb7b@wordpress.org>
Message-ID: <073.7821aa4b3d20cab786a6a89b843de94a@wordpress.org>

#4286: Plugin review URLs reference the raw 'p' value
------------------------------+---------------------
 Reporter:  jonoaldersonwp    |       Owner:  dd32
     Type:  defect            |      Status:  closed
 Priority:  lowest            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  seo               |
------------------------------+---------------------

Comment (by dd32):

 In [changeset:"8917" 8917]:
 {{{
 #!CommitTicketReference repository="" revision="8917"
 Plugin Directory: Always link to the 'pretty permalink' of reviews, now
 that the caches will have cleared.

 Amends [8474].
 See #4286.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 04:34:53 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 04:34:53 +0000 (UTC)
Subject: [wp-meta] [8918]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory:
 Plugin Directory: Jobs: Update the Tested-up-to version in the API
 update-check endpoints when the plugin directory automatically bumps the
 tested-up-to value for plugins.
Message-ID: <20190605043453.1584A1B0059F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/2ee1be1a/attachment-0001.html>

From noreply at wordpress.org  Wed Jun  5 04:34:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 04:34:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4468: Plugin Update Check API
 returns tested field without patch version
In-Reply-To: <050.30e29ecd97612d3aa44d24d35b73fddb@wordpress.org>
References: <050.30e29ecd97612d3aa44d24d35b73fddb@wordpress.org>
Message-ID: <065.0e035d52c98b476d93ac90d4dccbb855@wordpress.org>

#4468: Plugin Update Check API returns tested field without patch version
------------------------------+---------------------
 Reporter:  abrain            |       Owner:  dd32
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8918" 8918]:
 {{{
 #!CommitTicketReference repository="" revision="8918"
 Plugin Directory: Jobs: Update the Tested-up-to version in the API update-
 check endpoints when the plugin directory automatically bumps the tested-
 up-to value for plugins.

 This also runs the 'Meta Sync' cron task whenever a new WordPress release
 is made, to help speed up the rate at which Plugins show the latest
 version in their 'tested' fields.

 Fixes #4468.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 04:52:17 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 04:52:17 +0000 (UTC)
Subject: [wp-meta] [8919]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/libs/site-search/jetpack-search.php:
 Plugin Directory: Search: Remove debug and add specific errors in the case
 of a non-200 response.
Message-ID: <20190605045217.915971B0059F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/37089900/attachment.html>

From noreply at wordpress.org  Wed Jun  5 05:21:37 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 05:21:37 +0000 (UTC)
Subject: [wp-meta] [8920]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/functions.php:
 Theme Directory: Add canonical redirects for upper-case requests for Themes
 or section filters to their lower-case variant.
Message-ID: <20190605052137.49A8C1B0059F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/75e16b16/attachment.html>

From noreply at wordpress.org  Wed Jun  5 05:21:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 05:21:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4364: Mixed case URLs in the
 theme directory break the display
In-Reply-To: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
References: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
Message-ID: <073.fed1792d8ecb3e07e163fe4ceb565e1b@wordpress.org>

#4364: Mixed case URLs in the theme directory break the display
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:  seo analytics    |
-----------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8920" 8920]:
 {{{
 #!CommitTicketReference repository="" revision="8920"
 Theme Directory: Add canonical redirects for upper-case requests for
 Themes or section filters to their lower-case variant. The JS is case-
 sensitive.

 Fixes #4364.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 05:24:31 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 05:24:31 +0000 (UTC)
Subject: [wp-meta] [8921]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/functions.php:
 Theme Directory: Tighten a regular expression.
Message-ID: <20190605052431.644F61B0059F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/c87e5eb2/attachment.html>

From noreply at wordpress.org  Wed Jun  5 05:24:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 05:24:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4364: Mixed case URLs in the
 theme directory break the display
In-Reply-To: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
References: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
Message-ID: <073.14400060180cba84b2626637af1f7324@wordpress.org>

#4364: Mixed case URLs in the theme directory break the display
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:  seo analytics    |
-----------------------------+---------------------

Comment (by dd32):

 In [changeset:"8921" 8921]:
 {{{
 #!CommitTicketReference repository="" revision="8921"
 Theme Directory: Tighten a regular expression.

 Amends [8920].
 See #4364.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 06:59:37 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 06:59:37 +0000 (UTC)
Subject: [wp-meta] [8922]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-meeting-posttype/wporg-meeting-posttype.php:
 Make/Meetings: add a shortcode for displaying the next meeting time for a
 team.
Message-ID: <20190605065937.B04E61B00477@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/1d45a8bf/attachment.html>

From noreply at wordpress.org  Wed Jun  5 06:59:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 06:59:39 -0000
Subject: [wp-meta] [Making WordPress.org] #3078: Meetings: Use a single
 place to store meeting times info
In-Reply-To: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
References: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
Message-ID: <073.bf41114196e4fcc4c624086910a80165@wordpress.org>

#3078: Meetings: Use a single place to store meeting times info
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  has-patch                 |
--------------------------------------+---------------------

Comment (by tellyworth):

 In [changeset:"8922" 8922]:
 {{{
 #!CommitTicketReference repository="" revision="8922"
 Make/Meetings: add a shortcode for displaying the next meeting time for a
 team.

 This uses the meetings from the CPT on the Meetings tab, and will enable
 us to deprecate the redundant Weekly Meeting meta in the Sites CPT.

 Props ck3lee.
 See #3078.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 07:10:22 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 07:10:22 +0000 (UTC)
Subject: [wp-meta] [8923]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-makehome:
 Make home theme: show next meeting time in user's TZ.
Message-ID: <20190605071022.6E8D61B00477@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/53da09ac/attachment.html>

From noreply at wordpress.org  Wed Jun  5 07:10:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 07:10:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3078: Meetings: Use a single
 place to store meeting times info
In-Reply-To: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
References: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
Message-ID: <073.7b1f523e8b5c6475e9326bdb00fdb231@wordpress.org>

#3078: Meetings: Use a single place to store meeting times info
--------------------------------------+-------------------------
 Reporter:  SergeyBiryukov            |       Owner:  tellyworth
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:  has-patch                 |
--------------------------------------+-------------------------
Changes (by tellyworth):

 * owner:  (none) => tellyworth
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8923" 8923]:
 {{{
 #!CommitTicketReference repository="" revision="8923"
 Make home theme: show next meeting time in user's TZ.

 This uses the shortcode from [8922] to display the next meeting for each
 team, with a link to find additional meetings, rather than a single
 "Weekly" meeting per team. JS is used to convert the time into the user's
 local time zone. It also links to a filtered list of meetings per team.

 Props ck3lee.
 Fixes #3078.
 }}}

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

From noreply at wordpress.org  Wed Jun  5 07:22:58 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 07:22:58 +0000 (UTC)
Subject: [wp-meta] [8924]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-makehome/functions.php:
 Make home theme: bump cache for [8923]
Message-ID: <20190605072258.CD2391B00477@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/37c4b735/attachment.html>

From wp-meta at lists.wordpress.org  Wed Jun  5 13:15:25 2019
From: wp-meta at lists.wordpress.org (Mas Clientes)
Date: 5 Jun 2019 08:15:25 -0500
Subject: [wp-meta] Directorio Empresarial 2019.
Message-ID: <20190605081525.746A27D640DA5397@lists.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/1989d52e/attachment-0001.html>

From noreply at wordpress.org  Wed Jun  5 21:28:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 21:28:16 -0000
Subject: [wp-meta] [Making WordPress.org] #2575: Codex: #dotorgredirect
 does not redirect to Rosetta sites (was: Codex: #dotorgredirect does not
 redirect to forums)
In-Reply-To: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
References: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
Message-ID: <073.36baef6ff624bf587fa9bda564a5e6a7@wordpress.org>

#2575: Codex: #dotorgredirect does not redirect to Rosetta sites
----------------------------+-----------------------
 Reporter:  SergeyBiryukov  |       Owner:  Otto42
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:
Component:  Codex           |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

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

From noreply at wordpress.org  Wed Jun  5 21:29:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 21:29:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2575: Codex: #dotorgredirect
 does not redirect to Rosetta sites
In-Reply-To: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
References: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
Message-ID: <073.f048c8c7eae85e1d693dce46e5c90b6f@wordpress.org>

#2575: Codex: #dotorgredirect does not redirect to Rosetta sites
----------------------------+-----------------------
 Reporter:  SergeyBiryukov  |       Owner:  Otto42
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:
Component:  Codex           |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by SergeyBiryukov):

 Related: #4487

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

From noreply at wordpress.org  Wed Jun  5 21:35:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Jun 2019 21:35:33 -0000
Subject: [wp-meta] [Making WordPress.org] #2575: Codex: #dotorgredirect
 does not redirect to Rosetta sites
In-Reply-To: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
References: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
Message-ID: <073.91358c200290654382c434a5fadefcfd@wordpress.org>

#2575: Codex: #dotorgredirect does not redirect to Rosetta sites
----------------------------+-----------------------
 Reporter:  SergeyBiryukov  |       Owner:  Otto42
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:
Component:  Codex           |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by Otto42):

 Okay, I added wordpress.org in deploy:8223 but forgot about
 *.wordpress.org. I'll make that change shortly too.

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

From noreply at wordpress.org  Wed Jun  5 23:58:33 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Jun 2019 23:58:33 +0000 (UTC)
Subject: [wp-meta] [8925]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/views/wordcamp/metabox-original-application.php:
 WordCamp post type: Fix horizontal scrolling of application data
Message-ID: <20190605235833.9CB751B004DF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190605/9eea6c5a/attachment.html>

From noreply at wordpress.org  Thu Jun  6 12:26:02 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Jun 2019 12:26:02 +0000 (UTC)
Subject: [wp-meta] [8926]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/wcpt-wordcamp/wordcamp-admin.php:
 WordCamp: Add checkbox to track WordCamp running money through WPCS PBC.
Message-ID: <20190606122602.70AE01B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190606/0ef99c7d/attachment.html>

From noreply at wordpress.org  Thu Jun  6 12:26:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Jun 2019 12:26:04 -0000
Subject: [wp-meta] [Making WordPress.org] #3909: Add a new checkbox to
 the CPT "wordcamp" to mark when a WordCamp is not running all the money
 through WPCS PBC.
In-Reply-To: <057.166b4fbec4cf9255f099599136ebbf95@wordpress.org>
References: <057.166b4fbec4cf9255f099599136ebbf95@wordpress.org>
Message-ID: <072.db786b940592b977051e8eef017c38d3@wordpress.org>

#3909: Add a new checkbox to the CPT "wordcamp" to mark when a WordCamp is not
running all the money through WPCS PBC.
----------------------------------------+----------------------
 Reporter:  _DorsVenabili               |       Owner:  vedjain
     Type:  enhancement                 |      Status:  closed
 Priority:  high                        |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:  fixed
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+----------------------
Changes (by vedjain):

 * owner:  (none) => vedjain
 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8926" 8926]:
 {{{
 #!CommitTicketReference repository="" revision="8926"
 WordCamp: Add checkbox to track WordCamp running money through WPCS PBC.

 We can use this new field to ask WordCamps who are not running money
 through WC Central to send us transparency report at the end of event.

 Also have some indentation changes.

 Fixes #3909
 }}}

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

From noreply at wordpress.org  Thu Jun  6 12:26:14 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Jun 2019 12:26:14 +0000 (UTC)
Subject: [wp-meta] [8927]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-reports/assets/css/wordcamp-details.css:
 WordCamp report: Style fix for checkbox to have normal width.
Message-ID: <20190606122614.1B26E1B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190606/7da7af77/attachment.html>

From noreply at wordpress.org  Thu Jun  6 15:11:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Jun 2019 15:11:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2575: Codex: #dotorgredirect
 does not redirect to Rosetta sites
In-Reply-To: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
References: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
Message-ID: <073.cd3e7845a036ebb294f2dca8f910e9f4@wordpress.org>

#2575: Codex: #dotorgredirect does not redirect to Rosetta sites
----------------------------+-----------------------
 Reporter:  SergeyBiryukov  |       Owner:  Otto42
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:
Component:  Codex           |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by Otto42):

 Change made to deploy revision 8740. It will accept wordpress.org and
 *.wordpress.org. It was also send 301's for the redirects instead of
 302's.

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

From noreply at wordpress.org  Thu Jun  6 15:50:34 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Jun 2019 15:50:34 +0000 (UTC)
Subject: [wp-meta] [8928]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 Support Theme: Add trailling slash to links to user profiles.
Message-ID: <20190606155034.0BE141B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190606/24dd9cdf/attachment-0001.html>

From noreply at wordpress.org  Thu Jun  6 15:53:27 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Jun 2019 15:53:27 +0000 (UTC)
Subject: [wp-meta] [8929]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/plugins/jobswp/jobswp-template.php:
 Jobs: Properly escape output of URL.
Message-ID: <20190606155327.EBC2C1B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190606/5544772c/attachment.html>

From noreply at wordpress.org  Thu Jun  6 15:53:29 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Jun 2019 15:53:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3826: Wrong data validation
 added for esc_url_raw in WordPress Jobs Plugin
In-Reply-To: <052.bd623bc25f5daf0d75a452c335b3ad7a@wordpress.org>
References: <052.bd623bc25f5daf0d75a452c335b3ad7a@wordpress.org>
Message-ID: <067.771e40afc204e451bc17fa61978d5f1b@wordpress.org>

#3826: Wrong data validation added for esc_url_raw in WordPress Jobs Plugin
---------------------------------------+--------------------------
 Reporter:  mukesh27                   |       Owner:  coffee2code
     Type:  defect                     |      Status:  closed
 Priority:  low                        |   Milestone:
Component:  Jobs (jobs.wordpress.net)  |  Resolution:  fixed
 Keywords:  has-patch dev-feedback     |
---------------------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8929" 8929]:
 {{{
 #!CommitTicketReference repository="" revision="8929"
 Jobs: Properly escape output of URL.

 Props mukesh27.
 Fixes #3826.
 }}}

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

From noreply at wordpress.org  Thu Jun  6 18:25:13 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Jun 2019 18:25:13 +0000 (UTC)
Subject: [wp-meta] [8930]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Grant
 announce privilege to timothybjacobs for #core-restapi, per desrosj.
Message-ID: <20190606182513.B3B8A1B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190606/78870fdd/attachment.html>

From noreply at wordpress.org  Thu Jun  6 18:58:21 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Jun 2019 18:58:21 +0000 (UTC)
Subject: [wp-meta] [8931] sites/trunk/browsehappy.com/public_html: Browse
 Happy: Automatically wrap site name in header for languages that translate
 into long words.
Message-ID: <20190606185821.6F16C1B0043E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190606/6a4357f4/attachment-0001.html>

From noreply at wordpress.org  Fri Jun  7 02:03:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 02:03:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4498: Page order not working on
 Rosetta /team/handbook/
Message-ID: <047.53cc5d98eb2cec0348f64bd027d26ffc@wordpress.org>

#4498: Page order not working on Rosetta /team/handbook/
-----------------------+-------------------------
 Reporter:  Nao        |      Owner:  (none)
     Type:  defect     |     Status:  new
 Priority:  normal     |  Milestone:
Component:  Handbooks  |   Keywords:  needs-patch
-----------------------+-------------------------
 Related: #1919

 We've had @SergeyBiryukov enable handbook feature under our Rosetta team
 P2 (https://ja.wordpress.org/team/handbook/).
 Things are working great so far except we can't get the menu to follow the
 page order.

 **Steps for reproducing the issue**

 1. Enable handbook on a Rosetta site at locale.wordpress.org/team/handbook
 2. Create 2 or more handbook pages
 3. Set page orders under the "Page Attribute" meta box - the page orders
 are ignored.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4498>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun  7 02:12:41 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 02:12:41 -0000
Subject: [wp-meta] [Making WordPress.org] #2575: Codex: #dotorgredirect
 does not redirect to Rosetta sites
In-Reply-To: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
References: <058.651cb7005507497f6057ef4acbc7714c@wordpress.org>
Message-ID: <073.5af8830f6419494351b009379a33933a@wordpress.org>

#2575: Codex: #dotorgredirect does not redirect to Rosetta sites
----------------------------+-----------------------
 Reporter:  SergeyBiryukov  |       Owner:  Otto42
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:
Component:  Codex           |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by SergeyBiryukov):

 Replying to [comment:13 Otto42]:
 > Change made to deploy revision 8740. It will accept wordpress.org and
 *.wordpress.org.

 Thanks! Is it deployed yet? Still getting "Invalid Redirect" for this:
 {{{
 {{#dotorgredirect:https://ru.wordpress.org/support/forum-rules/}}
 }}}

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

From noreply at wordpress.org  Fri Jun  7 04:11:56 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 04:11:56 -0000
Subject: [wp-meta] [Making WordPress.org] #4499: Prevent tall screenshots
 overflowing container
Message-ID: <048.dbb628eb3d29e7fb5a5bd8cd5cc06b90@wordpress.org>

#4499: Prevent tall screenshots overflowing container
-----------------------------+--------------------
 Reporter:  dd32             |      Owner:  (none)
     Type:  defect           |     Status:  new
 Priority:  normal           |  Milestone:
Component:  Theme Directory  |   Keywords:
-----------------------------+--------------------
 Sometimes theme authors accidentally add screenshots which are too tall
 for the theme directory, see the below slack conversation for an example,
 we should limit the height of screenshots.

 https://wordpress.slack.com/archives/C02RP4Y3K/p1559876587250600

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4499>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun  7 04:12:27 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Jun 2019 04:12:27 +0000 (UTC)
Subject: [wp-meta] [8932]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/css:
 Theme Directory: Styles: Prevent tall screenshots overflowing the
 container.
Message-ID: <20190607041227.D891D1B00542@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190607/3ccad4ba/attachment-0001.html>

From noreply at wordpress.org  Fri Jun  7 04:12:29 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 04:12:29 -0000
Subject: [wp-meta] [Making WordPress.org] #4499: Prevent tall
 screenshots overflowing container
In-Reply-To: <048.dbb628eb3d29e7fb5a5bd8cd5cc06b90@wordpress.org>
References: <048.dbb628eb3d29e7fb5a5bd8cd5cc06b90@wordpress.org>
Message-ID: <063.1b55079484ce7bc87b0889519cae731b@wordpress.org>

#4499: Prevent tall screenshots overflowing container
-----------------------------+---------------------
 Reporter:  dd32             |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:                   |
-----------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8932" 8932]:
 {{{
 #!CommitTicketReference repository="" revision="8932"
 Theme Directory: Styles: Prevent tall screenshots overflowing the
 container.

 Fixes #4499.
 }}}

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

From noreply at wordpress.org  Fri Jun  7 04:26:01 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Jun 2019 04:26:01 +0000 (UTC)
Subject: [wp-meta] [8933]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/functions.php:
 Theme Directory: Cache bump after r8932.
Message-ID: <20190607042601.D0E491B00542@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190607/961038ed/attachment.html>

From noreply at wordpress.org  Fri Jun  7 04:26:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 04:26:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4499: Prevent tall
 screenshots overflowing container
In-Reply-To: <048.dbb628eb3d29e7fb5a5bd8cd5cc06b90@wordpress.org>
References: <048.dbb628eb3d29e7fb5a5bd8cd5cc06b90@wordpress.org>
Message-ID: <063.80cadee49a844fb14c53ac4d3ed92595@wordpress.org>

#4499: Prevent tall screenshots overflowing container
-----------------------------+---------------------
 Reporter:  dd32             |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:                   |
-----------------------------+---------------------

Comment (by dd32):

 In [changeset:"8933" 8933]:
 {{{
 #!CommitTicketReference repository="" revision="8933"
 Theme Directory: Cache bump after r8932.

 See #4499.
 }}}

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

From noreply at wordpress.org  Fri Jun  7 04:30:35 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Jun 2019 04:30:35 +0000 (UTC)
Subject: [wp-meta] [8934]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/functions.php:
 Theme Directory: Make the canonical redirects for uppercase urls a little
 less strict.
Message-ID: <20190607043035.4C5871B00542@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190607/99657e6e/attachment.html>

From noreply at wordpress.org  Fri Jun  7 04:30:37 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 04:30:37 -0000
Subject: [wp-meta] [Making WordPress.org] #4364: Mixed case URLs in the
 theme directory break the display
In-Reply-To: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
References: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
Message-ID: <073.c06f39bb8bffe2f3ce6ceb52f744ba64@wordpress.org>

#4364: Mixed case URLs in the theme directory break the display
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:  seo analytics    |
-----------------------------+---------------------

Comment (by dd32):

 In [changeset:"8934" 8934]:
 {{{
 #!CommitTicketReference repository="" revision="8934"
 Theme Directory: Make the canonical redirects for uppercase urls a little
 less strict.

 This uses path comparisons instead to reduce the complexity.

 See #4364.
 }}}

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

From noreply at wordpress.org  Fri Jun  7 04:40:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 04:40:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4498: Page order not working
 on Rosetta /team/handbook/
In-Reply-To: <047.53cc5d98eb2cec0348f64bd027d26ffc@wordpress.org>
References: <047.53cc5d98eb2cec0348f64bd027d26ffc@wordpress.org>
Message-ID: <062.92207e29ea3b2f938f10a9980fc4c9af@wordpress.org>

#4498: Page order not working on Rosetta /team/handbook/
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+---------------------
Changes (by coffee2code):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 The Handbook Sidebar widget was configured to order the pages by "Page
 title" (ページタイトル). I switched it to "Page order" (ページ順序) and
 everything appears to be ordered as expected.

 Unrelated, but I noticed the handbook appears to have a fairly empty index
 page (https://ja.wordpress.org/team/handbook/). There is a Meetup
 Organizer Handbook (https://ja.wordpress.org/team/handbook/meetup-
 organizer-hanbook/). Would that page make better sense as the index page,
 or will the team handbook have topics other than things for meetup
 organizers?

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

From noreply at wordpress.org  Fri Jun  7 06:54:20 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Jun 2019 06:54:20 +0000 (UTC)
Subject: [wp-meta] [8935]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/functions.php:
 Theme Directory: Fix a typo that didn't make it to the previous commit.
Message-ID: <20190607065420.2A1A51B00477@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190607/accbdaf1/attachment.html>

From noreply at wordpress.org  Fri Jun  7 06:54:21 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 06:54:21 -0000
Subject: [wp-meta] [Making WordPress.org] #4364: Mixed case URLs in the
 theme directory break the display
In-Reply-To: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
References: <058.c535f796fb13944c7760f0ad22da5605@wordpress.org>
Message-ID: <073.78f6546acd07fbc8a7abc5decff8abf5@wordpress.org>

#4364: Mixed case URLs in the theme directory break the display
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  closed
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:  seo analytics    |
-----------------------------+---------------------

Comment (by dd32):

 In [changeset:"8935" 8935]:
 {{{
 #!CommitTicketReference repository="" revision="8935"
 Theme Directory: Fix a typo that didn't make it to the previous commit.

 Ammends [8934].
 See #4364.
 }}}

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

From noreply at wordpress.org  Fri Jun  7 07:05:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 07:05:06 -0000
Subject: [wp-meta] [Making WordPress.org] #3718: Theme Directory: Allow
 minimum WP and PHP version requirement
In-Reply-To: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
References: <052.f813ca3953a53ea16939c46b5f3c65df@wordpress.org>
Message-ID: <067.e576e7622fe5cf64c3f26e9faaf363b4@wordpress.org>

#3718: Theme Directory: Allow minimum WP and PHP version requirement
----------------------------------+---------------------
 Reporter:  flixos90              |       Owner:  dd32
     Type:  task                  |      Status:  closed
 Priority:  normal                |   Milestone:
Component:  Theme Directory       |  Resolution:  fixed
 Keywords:  has-patch servehappy  |
----------------------------------+---------------------
Changes (by dd32):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 Data for older themes is being imported.

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

From noreply at wordpress.org  Fri Jun  7 08:47:57 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 08:47:57 -0000
Subject: [wp-meta] [Making WordPress.org] #4498: Page order not working
 on Rosetta /team/handbook/
In-Reply-To: <047.53cc5d98eb2cec0348f64bd027d26ffc@wordpress.org>
References: <047.53cc5d98eb2cec0348f64bd027d26ffc@wordpress.org>
Message-ID: <062.0e8cd4bf2d63d6e2c4a7acaa0078d0da@wordpress.org>

#4498: Page order not working on Rosetta /team/handbook/
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+---------------------

Comment (by Nao):

 Awesome, thanks for a quick fix!

 We plan on translating multiple handbooks - so an index page like this
 https://make.wordpress.org/community/handbook/ would be more appropriate.

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

From noreply at wordpress.org  Fri Jun  7 08:50:17 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 08:50:17 -0000
Subject: [wp-meta] [Making WordPress.org] #1919: Allow locales to create
 localised handbooks on Rosetta sites
In-Reply-To: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
References: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
Message-ID: <066.07820264e7a405bc63d82a63e629ca27@wordpress.org>

#1919: Allow locales to create localised handbooks on Rosetta sites
-------------------------------------------+---------------------
 Reporter:  casiepa                        |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  low                            |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:                                 |
-------------------------------------------+---------------------

Comment (by Nao):

 In #4498 @coffee2code helped us configure the menu order (the config is
 under Customizer > Widget). FYI, @CoachBirgit and others who will be
 getting their handbook enabled.

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

From noreply at wordpress.org  Fri Jun  7 09:03:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 09:03:54 -0000
Subject: [wp-meta] [Making WordPress.org] #1919: Allow locales to create
 localised handbooks on Rosetta sites
In-Reply-To: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
References: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
Message-ID: <066.e429e7e86f6996bcc20f174d12eb4f49@wordpress.org>

#1919: Allow locales to create localised handbooks on Rosetta sites
-------------------------------------------+---------------------
 Reporter:  casiepa                        |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  low                            |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:                                 |
-------------------------------------------+---------------------

Comment (by CoachBirgit):

 Replying to [comment:16 Nao]:
 > In #4498 @coffee2code helped us configure the menu order (the config is
 under Customizer > Widget). FYI, @CoachBirgit and others who will be
 getting their handbook enabled.

 That's awesome! Thank you all very much for your contribution to the local
 contributor handbooks.

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

From noreply at wordpress.org  Fri Jun  7 17:33:11 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Jun 2019 17:33:11 +0000 (UTC)
Subject: [wp-meta] [8936]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/load-other-mu-plugins.php:
 WordCamp: Enabled blocks for WC Boston, Taipei and Sevilla.
Message-ID: <20190607173311.BE41A1B00477@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190607/dfb14c69/attachment.html>

From noreply at wordpress.org  Fri Jun  7 17:38:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 17:38:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4500: Add responsive embed
 support to WordCamp sites
Message-ID: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>

#4500: Add responsive embed support to WordCamp sites
-------------------------------------+--------------------
 Reporter:  melchoyce                |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 The theme needs to support it: https://developer.wordpress.org/block-
 editor/developers/themes/theme-support/#responsive-embedded-content

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4500>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun  7 17:50:15 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Jun 2019 17:50:15 -0000
Subject: [wp-meta] [Making WordPress.org] #4501: Allow authors to cross-post
 to all Make blogs
Message-ID: <051.778cd2ea274b60ee2d3bf14cd73523ce@wordpress.org>

#4501: Allow authors to cross-post to all Make blogs
--------------------------------------+--------------------
 Reporter:  iandunn                   |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+--------------------
 If a person has a `Contributor` (or higher) role on ''any'' Make site, I
 think they should have the ability to cross-post to any other Make site.

 Otherwise people have to be manually added to each individual site, which
 is tedious and adds an unnecessary barrier to communicating.

 (For contributors, their post would still need to be approved by an Editor
 before the cross posting would happen, of course)

 One way to do this would be to programatically add all users to all sites,
 but there's probably a more elegant way to do it with `map_meta_cap` or
 `has_cap`. It would need to make sure that all of the sites appear in the
 list that o2 shows when you type `+`.

 Sites that are marked as `private`, `archived`, and `deactivated` should
 be excluded from this functionality. Users should '''not''' be given
 access to browse wp-admin of the other sites, etc. It should only allow
 them to cross-post.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4501>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun  8 08:51:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 08:51:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4502: Slack username seems no
 longer unique
Message-ID: <051.7e7c478f492e2cee608817f9065f4a65@wordpress.org>

#4502: Slack username seems no longer unique
-------------------------+--------------------
 Reporter:  casiepa      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Profiles     |   Keywords:
-------------------------+--------------------
 Starting from a profile like https://profiles.wordpress.org/imatoni/ it
 indicates that the user is '@Phil on Slack'. But on Slack there are
 currently 4 different @Phil.

 Starting a DM with each of them will indicate 'This is the very beginning
 of your direct message history with @Phil'

 I suppose this is due to Slack now using 'member IDs' like UCGDDDSBA or
 U5C0WNDJM.

 Proposals:
 1) add the member ID next to the slack alias.
 2) add the direct DM link (https://wordpress.slack.com/messages/UCGDDDSBA/
 or https://wordpress.slack.com/messages/U5C0WNDJM)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4502>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun  8 08:51:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 08:51:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4502: Slack username seems no
 longer unique
In-Reply-To: <051.7e7c478f492e2cee608817f9065f4a65@wordpress.org>
References: <051.7e7c478f492e2cee608817f9065f4a65@wordpress.org>
Message-ID: <066.8d46bfec857d2250ad22a907656fcd77@wordpress.org>

#4502: Slack username seems no longer unique
-------------------------+---------------------
 Reporter:  casiepa      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Profiles     |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by casiepa):

 * Attachment "Slack.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4502>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun  8 12:56:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 12:56:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4503: Incoherent final slash added
Message-ID: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>

#4503: Incoherent final slash added
----------------------+--------------------
 Reporter:  casiepa   |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:
Component:  Profiles  |   Keywords:
----------------------+--------------------
 Using link https://profiles.wordpress.org/casiepa I do not put a final
 slash, but the slash gets added.
 Using link https://profiles.wordpress.org/casiepA I do not put a final
 slash and no slash gets added.

 Both links however get me to the correct profile.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4503>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun  8 13:29:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 13:29:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4503: Incorrect
 capitalization of nicename not corrected in user profile links (was:
 Incoherent final slash added)
In-Reply-To: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>
References: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>
Message-ID: <066.d85cace0e372c5aace6e4489efec33f6@wordpress.org>

#4503: Incorrect capitalization of nicename not corrected in user profile links
----------------------+---------------------
 Reporter:  casiepa   |       Owner:  (none)
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:
 Keywords:            |
----------------------+---------------------

Comment (by Otto42):

 The final slash is supposed to be there. The problem is that the nicename
 is not corrected to the correct case and thus redirecting you to the
 correct URL.

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

From noreply at wordpress.org  Sat Jun  8 13:34:48 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 13:34:48 -0000
Subject: [wp-meta] [Making WordPress.org] #4502: Slack username seems no
 longer unique
In-Reply-To: <051.7e7c478f492e2cee608817f9065f4a65@wordpress.org>
References: <051.7e7c478f492e2cee608817f9065f4a65@wordpress.org>
Message-ID: <066.8740a9f4016fb6bbdbcaee755df0b399@wordpress.org>

#4502: Slack username seems no longer unique
-------------------------+----------------------
 Reporter:  casiepa      |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Profiles     |  Resolution:  invalid
 Keywords:               |
-------------------------+----------------------
Changes (by Otto42):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Slack eliminated unique usernames a couple years ago.

 https://api.slack.com/changelog/2017-09-the-one-about-usernames

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

From noreply at wordpress.org  Sat Jun  8 17:16:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 17:16:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4504: Security docs in Plugins
 hanbook for developing in block editor context
Message-ID: <052.7055d69637afb44065058170c7b9f063@wordpress.org>

#4504: Security docs in Plugins hanbook for developing in block editor context
----------------------+--------------------
 Reporter:  manooweb  |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:
Component:  General   |   Keywords:
----------------------+--------------------
 Hello,

 As we discussed during a #core-editor meeting on wednesday 5th June
 https://wordpress.slack.com/archives/C02QB2JS7/p1559741727071700

 it seems there is no guidelines about what a developer need to pay
 attention when he codes in javascript and espacially React technologies
 like that exists with PHP in the plugins handbook here
 https://developer.wordpress.org/plugins/security/

 For example when we start and are new on these technologies we can ask
 ourselves some questions

 - Do I need to use JSX instead of createElement because JSX is safe?

 See https://reactjs.org/docs/react-without-jsx.html
 and https://reactjs.org/docs/introducing-jsx.html#jsx-prevents-injection-
 attacks

 Is it the same because Babel compiles JSX down to React.createElement()
 calls?

 - What about the use of dangerouslySetInnerHtml? The block editor use it
 internally. What
   should we pay attention to when we need to use it?

 https://reactjs.org/docs/dom-elements.html#dangerouslysetinnerhtml

 - What should we never do?


 Because we don't really know where to open the issue I'm going to also
 open it on the Gutenberg repository on Github

 Regards

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4504>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun  8 17:21:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 17:21:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4504: Security docs in
 Plugins hanbook for developing in block editor context
In-Reply-To: <052.7055d69637afb44065058170c7b9f063@wordpress.org>
References: <052.7055d69637afb44065058170c7b9f063@wordpress.org>
Message-ID: <067.37cf033eedb5adb139c5e0f1b7403bdb@wordpress.org>

#4504: Security docs in Plugins hanbook for developing in block editor context
---------------------------+---------------------
 Reporter:  manooweb       |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:                 |
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * component:  General => Developer Hub


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

From noreply at wordpress.org  Sat Jun  8 18:05:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Jun 2019 18:05:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3773: Request from Marketing
 Team to Implement Navigation Change at make.wordpress.org
In-Reply-To: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
References: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
Message-ID: <074.3d80ba4545aec76b6e51dda69abe3927@wordpress.org>

#3773: Request from Marketing Team to Implement Navigation Change at
make.wordpress.org
-------------------------------------------------+-------------------------
 Reporter:  westcountymedia                      |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  high                                 |   Milestone:
Component:  Make (Get Involved) / P2             |  Resolution:
 Keywords:  ui-feedback ux-feedback 2nd-opinion  |
  needs-design                                   |
-------------------------------------------------+-------------------------

Comment (by karmatosed):

 @westcountymedia thanks for working on this what about these as options to
 focus the links:

 Meetup Groups (https://www.meetup.com/pro/wordpress/)
 WordCamps (https://central.wordcamp.org/)
 Team Meetings (https://make.wordpress.org/meetings/)
 Team Updates (https://make.wordpress.org/updates/)

 For now, I think not having the contribution day link probably is a good
 balance.

 @hedgefield are you still able to create a mockup? That would be great.

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

From noreply at wordpress.org  Sun Jun  9 07:03:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Jun 2019 07:03:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4503: Incorrect
 capitalization of nicename not corrected in user profile links
In-Reply-To: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>
References: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>
Message-ID: <066.4980a2ff709b4afbe1b0f8c26e10c326@wordpress.org>

#4503: Incorrect capitalization of nicename not corrected in user profile links
----------------------+--------------------------
 Reporter:  casiepa   |       Owner:  coffee2code
     Type:  defect    |      Status:  accepted
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:
 Keywords:            |
----------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => accepted


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

From noreply at wordpress.org  Sun Jun  9 14:19:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Jun 2019 14:19:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4491: Archive page shows 2
 columns instead of 3 at certain media queries
In-Reply-To: <054.eebc6b0b5da5a73f5283f8b17c1f7366@wordpress.org>
References: <054.eebc6b0b5da5a73f5283f8b17c1f7366@wordpress.org>
Message-ID: <069.fea3c847a27585c9dc1200b86489b39f@wordpress.org>

#4491: Archive page shows 2 columns instead of 3 at certain media queries
-----------------------------------------+---------------------
 Reporter:  milana_cap                   |       Owner:  (none)
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  HelpHub                      |  Resolution:
 Keywords:  needs-patch has-screenshots  |
-----------------------------------------+---------------------
Changes (by milana_cap):

 * Attachment "4491.patch" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4491>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jun  9 14:19:32 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Jun 2019 14:19:32 -0000
Subject: [wp-meta] [Making WordPress.org] #4491: Archive page shows 2
 columns instead of 3 at certain media queries
In-Reply-To: <054.eebc6b0b5da5a73f5283f8b17c1f7366@wordpress.org>
References: <054.eebc6b0b5da5a73f5283f8b17c1f7366@wordpress.org>
Message-ID: <069.3eecf717fc40f5a546e5fed2b5c1b4a9@wordpress.org>

#4491: Archive page shows 2 columns instead of 3 at certain media queries
---------------------------------------+---------------------
 Reporter:  milana_cap                 |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  HelpHub                    |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+---------------------
Changes (by milana_cap):

 * keywords:  needs-patch has-screenshots => has-screenshots has-patch


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

From noreply at wordpress.org  Sun Jun  9 14:29:20 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Jun 2019 14:29:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3854: Multiple Attendees
 Lists Shortcodes Breaks the Page
In-Reply-To: <054.6e402b613a442a8bcd5cb87addad4948@wordpress.org>
References: <054.6e402b613a442a8bcd5cb87addad4948@wordpress.org>
Message-ID: <069.c49f4f73b307e8d198740c2da36b17ad@wordpress.org>

#3854: Multiple Attendees Lists Shortcodes Breaks the Page
---------------------------------------+-----------------------
 Reporter:  milana_cap                 |       Owner:  (none)
     Type:  defect                     |      Status:  assigned
 Priority:  normal                     |   Milestone:
Component:  WordCamp Site & Plugins    |  Resolution:
 Keywords:  has-screenshots has-patch  |
---------------------------------------+-----------------------
Changes (by milana_cap):

 * keywords:  needs-patch has-screenshots => has-screenshots has-patch


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

From noreply at wordpress.org  Sun Jun  9 16:05:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Jun 2019 16:05:24 -0000
Subject: [wp-meta] [Making WordPress.org] #4505: Add at page consistency
 next and previous strings buttons
Message-ID: <053.ed3ca263ef894e5a16ff47a4928eb2f6@wordpress.org>

#4505: Add at page consistency next and previous strings buttons
--------------------------------------+--------------------
 Reporter:  websaitua                 |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:  Q1
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 Hi, Glotpress.
 Please add at page https://translate.wordpress.org/consistency/ buttons
 next and previous strings buttons. Like this page
 https://translate.wordpress.org/projects/wp-
 plugins/kirki/dev/uk/default/?filters%5Btranslated%5D=yes&filters%5Bstatus%5D=waiting&page=3
 when click at Details.
 In glotpress thya calling "Open previous editor" and "Open next editor".
 Thanks

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4505>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 10 01:48:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 01:48:59 -0000
Subject: [wp-meta] [Making WordPress.org] #3717: Include post date in
 the Reviews tab
In-Reply-To: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
References: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
Message-ID: <071.0b341c3da0418b7586b9112d6771f698@wordpress.org>

#3717: Include post date in the Reviews tab
------------------------------+-----------------------
 Reporter:  philclothier      |       Owner:  ck3lee
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  ui-feedback       |
------------------------------+-----------------------
Changes (by ck3lee):

 * Attachment "WordPress 2019-06-10 13-37-35.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3717>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 10 01:50:08 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 01:50:08 -0000
Subject: [wp-meta] [Making WordPress.org] #3717: Include post date in
 the Reviews tab
In-Reply-To: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
References: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
Message-ID: <071.730c3a73ef8fc8eb4c101a6fd51ea00e@wordpress.org>

#3717: Include post date in the Reviews tab
------------------------------+-----------------------
 Reporter:  philclothier      |       Owner:  ck3lee
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  ui-feedback       |
------------------------------+-----------------------
Changes (by ck3lee):

 * Attachment "3717.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3717>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 10 02:01:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 02:01:59 -0000
Subject: [wp-meta] [Making WordPress.org] #3717: Include post date in
 the Reviews tab
In-Reply-To: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
References: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
Message-ID: <071.482f68dbfbc2d5c32eaf64ed40398351@wordpress.org>

#3717: Include post date in the Reviews tab
-----------------------------------+-----------------------
 Reporter:  philclothier           |       Owner:  ck3lee
     Type:  enhancement            |      Status:  assigned
 Priority:  normal                 |   Milestone:
Component:  Plugin Directory       |  Resolution:
 Keywords:  ui-feedback has-patch  |
-----------------------------------+-----------------------
Changes (by ck3lee):

 * keywords:  ui-feedback => ui-feedback has-patch


Comment:

 attachment:3717.diff and screenshot are based on @mapk's latest design.
 Hope this works. Yeah, having the dates for each review definitely helps
 here.

 @SergeyBiryukov, please review when you have a chance. Thank you.

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

From noreply at wordpress.org  Mon Jun 10 07:12:40 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 07:12:40 -0000
Subject: [wp-meta] [Making WordPress.org] #3717: Include post date in
 the Reviews tab
In-Reply-To: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
References: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
Message-ID: <071.ce08992d74ffa83a56566b6d70eebe34@wordpress.org>

#3717: Include post date in the Reviews tab
-----------------------------------+-----------------------
 Reporter:  philclothier           |       Owner:  ck3lee
     Type:  enhancement            |      Status:  assigned
 Priority:  normal                 |   Milestone:
Component:  Plugin Directory       |  Resolution:
 Keywords:  ui-feedback has-patch  |
-----------------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:13 ck3lee]:
 > attachment:3717.diff and screenshot are based on @mapk's latest design.
 Hope this works. Yeah, having the dates for each review definitely helps
 here.
 >
 > @SergeyBiryukov, please review when you have a chance. Thank you.

 I like where this has gone, the only thing I've picked up on is that
 `date_i18n()` should be used in place of `gmdate()` so we've got localised
 months on international sites.
 IIRC changing the markup here doesn't affect the markup delivered through
 the API to WordPress plugin info iframes, but that should be checked prior
 to committing this.

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

From noreply at wordpress.org  Mon Jun 10 14:43:53 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 14:43:53 -0000
Subject: [wp-meta] [Making WordPress.org] #4267: Version article title
 should look different than rest of the headings
In-Reply-To: <053.8da77a746ac94216f60abec6424c3d36@wordpress.org>
References: <053.8da77a746ac94216f60abec6424c3d36@wordpress.org>
Message-ID: <068.73bef3a55d9dcb3d1c29a796e5c51ba2@wordpress.org>

#4267: Version article title should look different than rest of the headings
-----------------------+---------------------
 Reporter:  kartiks16  |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  HelpHub    |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------

Comment (by Kenshino):

 @coffee2code - can this be merged? It's a minor css change

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

From noreply at wordpress.org  Mon Jun 10 14:45:11 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Jun 2019 14:45:11 +0000 (UTC)
Subject: [wp-meta] [8937]
 sites/trunk/wordpress.org/public_html/wp-content/plugins: Translate: Send
 approved translations to translation memory.
Message-ID: <20190610144511.299A01B004DF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190610/8310717b/attachment-0001.html>

From noreply at wordpress.org  Mon Jun 10 14:45:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 14:45:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4430: Provide suggestions for
 translations
In-Reply-To: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
References: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
Message-ID: <066.3633fbea8c273dc9b1c74a42add64210@wordpress.org>

#4430: Provide suggestions for translations
--------------------------------------+-----------------------
 Reporter:  ocean90                   |       Owner:  ocean90
     Type:  task                      |      Status:  assigned
 Priority:  high                      |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by ocean90):

 In [changeset:"8937" 8937]:
 {{{
 #!CommitTicketReference repository="" revision="8937"
 Translate: Send approved translations to translation memory.

 Props yoavf, ocean90.
 See #4430.
 }}}

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

From noreply at wordpress.org  Mon Jun 10 21:41:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 21:41:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4500: Add responsive embed
 support to WordCamp sites
In-Reply-To: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
References: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
Message-ID: <068.fee4bb53333af929d084ed3f536b0b28@wordpress.org>

#4500: Add responsive embed support to WordCamp sites
-------------------------------------+---------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------
Changes (by ryelle):

 * Attachment "4500.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4500>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 10 21:43:13 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Jun 2019 21:43:13 +0000 (UTC)
Subject: [wp-meta] [8938]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress/bbPress: Include bbPress Trac body class in subnav styling.
Message-ID: <20190610214313.6C36D1B004DF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190610/f660b151/attachment.html>

From noreply at wordpress.org  Mon Jun 10 21:43:35 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Jun 2019 21:43:35 +0000 (UTC)
Subject: [wp-meta] [8939] sites/trunk/trac.wordpress.org/templates:
 BuddyPress/bbPress: bump CSS version in Trac headers.
Message-ID: <20190610214335.C5D5C1B004DF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190610/4e16a9e7/attachment.html>

From noreply at wordpress.org  Mon Jun 10 21:44:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 21:44:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4500: Add responsive embed
 support to WordCamp sites
In-Reply-To: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
References: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
Message-ID: <068.b8492b3e4a65c2887d3252618ddf17ec@wordpress.org>

#4500: Add responsive embed support to WordCamp sites
-------------------------------------+---------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+---------------------
Changes (by ryelle):

 * keywords:   => has-patch


Comment:

 [attachment:"4500.diff"] adds the theme support to CampSite, which fixes
 the issue we were having on WCUS with making a VideoPress embed wide-width
 with the "align wide" option.

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

From noreply at wordpress.org  Mon Jun 10 23:02:12 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 23:02:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3717: Include post date in
 the Reviews tab
In-Reply-To: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
References: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
Message-ID: <071.99d8f150aa5ab6f89f1e91315ac8129b@wordpress.org>

#3717: Include post date in the Reviews tab
-----------------------------------+-----------------------
 Reporter:  philclothier           |       Owner:  ck3lee
     Type:  enhancement            |      Status:  assigned
 Priority:  normal                 |   Milestone:
Component:  Plugin Directory       |  Resolution:
 Keywords:  ui-feedback has-patch  |
-----------------------------------+-----------------------
Changes (by ck3lee):

 * Attachment "3717.1.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3717>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 10 23:04:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Jun 2019 23:04:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3717: Include post date in
 the Reviews tab
In-Reply-To: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
References: <056.9e63a9983223d026f36bcd9414825ada@wordpress.org>
Message-ID: <071.f6f7d775f5d4107fb513ea77243b866a@wordpress.org>

#3717: Include post date in the Reviews tab
-----------------------------------+-----------------------
 Reporter:  philclothier           |       Owner:  ck3lee
     Type:  enhancement            |      Status:  assigned
 Priority:  normal                 |   Milestone:
Component:  Plugin Directory       |  Resolution:
 Keywords:  ui-feedback has-patch  |
-----------------------------------+-----------------------

Comment (by ck3lee):

 Thank you for your feedback, @dd32.

 Uploaded attachment:3717.1.diff with `date_i18n()`.
 Please review. I hope this works.

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

From noreply at wordpress.org  Tue Jun 11 00:39:57 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 00:39:57 -0000
Subject: [wp-meta] [Making WordPress.org] #262: Automate WordCamp
 Gravatar Badge Creation
In-Reply-To: <051.401611a60373917b67de1429781f2ed0@wordpress.org>
References: <051.401611a60373917b67de1429781f2ed0@wordpress.org>
Message-ID: <066.3118f86a992993a594d51f78ca22729b@wordpress.org>

#262: Automate WordCamp Gravatar Badge Creation
----------------------------------------+-----------------------
 Reporter:  iandunn                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  assigned
 Priority:  high                        |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------

Comment (by tinkerbelly):

 This is great feedback, thank you! Rather than working line-by-line, I'm
 going to try to point-form some responses here so as not to get too wall-
 of-texty:

 - I've added (Admin flag) in parentheses beside the header—that way, users
 will know where these are coming from, and can link back to the page, but
 the header still makes sense.

 - Definitely typed "Generate Tickets" all over for no good reason other
 than not being 100% attention-paying-y. Fixed now! Side note, is there a
 better term than "generate"? It feels so .... clinical. Would "Building"
 or "making" work better in some places, to be a bit friendlier? Or maybe,
 if we were to go with "Generating badge data", would "Exporting badge
 data" or "building badge data" or similar work better?

 - Let's use a modal as well as giving the option to come back later—this
 allows for more user flexibility and the modal makes it feel a lot more
 like something is happening, where before the flow sort of came to a dead
 end. If you'd like to prioritise one over the other, the modal approach is
 probably the most expected and immediate flow, so let's start there.

 - If we're going to allow for users to return back and download the
 generated badge data, we probably want to add a section for that to the
 generate badges landing page, so it's easy to find in a centralised place.
 I can mock this up as well... and maybe we can streamline the page a bit
 while we're at it?

 - In terms of a notification: I think it would make sense to a) send an
 email and b) send a Dashboard/wp-admin Notice to let them know their badge
 data is available for download. Would there b a way to avoid triggering
 these notices if the data has already been downloaded though? That would
 be super groovy.

 - Let's definitely provide this in a wireframe and a prototype. I've
 started pieceing it together a bit in Figma here:
 https://www.figma.com/proto/Hs5WJesPPvr4yFVCIcEefwxm/InDesign-Badge-Data-
 Generation?node-id=39%3A16&viewport=221%2C721%2C0.5&scaling=scale-down

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

From noreply at wordpress.org  Tue Jun 11 00:43:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 00:43:58 -0000
Subject: [wp-meta] [Making WordPress.org] #262: Automate WordCamp
 Gravatar Badge Creation
In-Reply-To: <051.401611a60373917b67de1429781f2ed0@wordpress.org>
References: <051.401611a60373917b67de1429781f2ed0@wordpress.org>
Message-ID: <066.84d68f776d66a7aacd6d1f488fd19e79@wordpress.org>

#262: Automate WordCamp Gravatar Badge Creation
----------------------------------------+-----------------------
 Reporter:  iandunn                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  assigned
 Priority:  high                        |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------
Changes (by tinkerbelly):

 * Attachment "2019-06-10 20.25.43.gif" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/262>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 11 05:49:15 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 05:49:15 -0000
Subject: [wp-meta] [Making WordPress.org] #4267: Version article title
 should look different than rest of the headings
In-Reply-To: <053.8da77a746ac94216f60abec6424c3d36@wordpress.org>
References: <053.8da77a746ac94216f60abec6424c3d36@wordpress.org>
Message-ID: <068.9e4cd40939cb0f059502816346cfe3f0@wordpress.org>

#4267: Version article title should look different than rest of the headings
-----------------------+--------------------------
 Reporter:  kartiks16  |       Owner:  coffee2code
     Type:  defect     |      Status:  accepted
 Priority:  normal     |   Milestone:
Component:  HelpHub    |  Resolution:
 Keywords:  has-patch  |
-----------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => accepted


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

From noreply at wordpress.org  Tue Jun 11 14:00:08 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 14:00:08 -0000
Subject: [wp-meta] [Making WordPress.org] #4445: Rosetta: redirects for
 fi.wordpress.org
In-Reply-To: <050.dadd163c636380b1236761e381bf9488@wordpress.org>
References: <050.dadd163c636380b1236761e381bf9488@wordpress.org>
Message-ID: <065.499ed771b7f34a0caf92d37355396e3e@wordpress.org>

#4445: Rosetta: redirects for fi.wordpress.org
-------------------------------------------+----------------------
 Reporter:  sippis                         |       Owner:  (none)
     Type:  defect                         |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  wontfix
 Keywords:                                 |
-------------------------------------------+----------------------
Changes (by sippis):

 * status:  new => closed
 * resolution:   => wontfix


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

From noreply at wordpress.org  Tue Jun 11 14:16:15 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 14:16:15 -0000
Subject: [wp-meta] [Making WordPress.org] #4506: i18n: Create list with
 CL-PTE's and their respective projects
Message-ID: <056.0c852f5540d41ccb48a6a098cc0e473a@wordpress.org>

#4506: i18n: Create list with CL-PTE's and their respective projects
--------------------------------------+--------------------
 Reporter:  tobifjellner              |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 The number of CL-PTE's (Cross Locale Project Translation Editor) is
 growing.
 For contributors involved in the translation of WordPress, it becomes
 increasingly important to have a convenient way to find all CLPTE's and
 their respective projects, somewhere on
 https://make.wordpress.org/polyglots/ just like we already have
 https://make.wordpress.org/polyglots/teams/ and its sub-pages to easily
 find the translation teams for the various locales

 Please develop a page that will list the CL-PTE's with Gravata, Username
 (linked to profile), Nice Name, and with a (linked) list of all their
 respective assigned translation projects.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4506>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 11 16:12:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 16:12:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4507: Glossary tooltips break
 HTML markup (take 2)
Message-ID: <058.a001e3bab727502e4bd908103d404b46@wordpress.org>

#4507: Glossary tooltips break HTML markup (take 2)
--------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov            |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:  has-screenshots
--------------------------------------+-----------------------------
 Previously: #4473

 On https://make.wordpress.org/polyglots/2019/06/02/pte-request-for-
 kirki/#comment-283767, there's this part of a sentence:
 > `[username] can not be the translation editor for the […] language`

 The new glossary tooltips interfere with the page, causing invalid markup
 and display issues:
 {{{
 … can not be the <span tabindex="0" class="glossary-item-
 container">translation editor<span class="glossary-item-hidden-
 content"><span class="glossary-item-header">Translation Editor</span>
 <span class="glossary-item-description">Translation editors can approve
 translations for projects. The GTE (General Translation Editor) and LM
 (Locale Manager) roles can add new users with the "Project Translation
 Editor" role that can approve translations for specific projects.</p>
 <p>There are two different Translation Editor roles, see:</p>
 <p>     <a href="#general-translation-editor">General Translation
 Editor</a><br />
         <a href="#project-translation-editor">Project Translation
 Editor</a><br />
 <br /><a href="https://make.wordpress.org/polyglots/wp-
 admin/post.php?post=5951&amp;action=edit">Edit
 Entry</a></span></span></span> for the <a
 href="https://make.wordpress.org/polyglots/teams/?locale=uk"
 class="tag"><span class="tag-prefix">#</span>uk</a> Ukrainian language.
 }}}

 Two issues here:
 * `<p>` inside `<span>` is invalid.
 * Extra text is displayed on the page, instead of being in a tooltip.

 See the screenshot. Tested in the latest Google Chrome and Microsoft Edge
 on Windows 10.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4507>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 11 16:12:31 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 16:12:31 -0000
Subject: [wp-meta] [Making WordPress.org] #4507: Glossary tooltips break
 HTML markup (take 2)
In-Reply-To: <058.a001e3bab727502e4bd908103d404b46@wordpress.org>
References: <058.a001e3bab727502e4bd908103d404b46@wordpress.org>
Message-ID: <073.a69307004d51ff4e4525d40ce3fe9230@wordpress.org>

#4507: Glossary tooltips break HTML markup (take 2)
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  has-screenshots           |
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "4507.PNG" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4507>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 11 16:13:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 16:13:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4473: Glossary tooltips break
 HTML markup
In-Reply-To: <058.5fc2ad6fa7245353693994aa89b6d473@wordpress.org>
References: <058.5fc2ad6fa7245353693994aa89b6d473@wordpress.org>
Message-ID: <073.f6a5bd3cf5c41a0aff3b3b63a39ffdf8@wordpress.org>

#4473: Glossary tooltips break HTML markup
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:  has-screenshots           |
--------------------------------------+---------------------

Comment (by SergeyBiryukov):

 Follow-up: #4507

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

From noreply at wordpress.org  Tue Jun 11 19:30:19 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 19:30:19 -0000
Subject: [wp-meta] [Making WordPress.org] #4445: Rosetta: redirects for
 fi.wordpress.org
In-Reply-To: <050.dadd163c636380b1236761e381bf9488@wordpress.org>
References: <050.dadd163c636380b1236761e381bf9488@wordpress.org>
Message-ID: <065.ed7591a2773a61746b15ed06787fe539@wordpress.org>

#4445: Rosetta: redirects for fi.wordpress.org
-------------------------------------------+------------------------
 Reporter:  sippis                         |       Owner:  (none)
     Type:  defect                         |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  duplicate
 Keywords:                                 |
-------------------------------------------+------------------------
Changes (by SergeyBiryukov):

 * resolution:  wontfix => duplicate


Comment:

 Duplicate of #4399.

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

From noreply at wordpress.org  Tue Jun 11 20:51:49 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Jun 2019 20:51:49 +0000 (UTC)
Subject: [wp-meta] [8940]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support:
 Support Theme: Increase font size for `h1` to differentiate it from `h2` on
 HelpHub pages.
Message-ID: <20190611205149.241A91B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190611/6420323d/attachment-0001.html>

From noreply at wordpress.org  Tue Jun 11 20:51:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 20:51:50 -0000
Subject: [wp-meta] [Making WordPress.org] #4267: Version article title
 should look different than rest of the headings
In-Reply-To: <053.8da77a746ac94216f60abec6424c3d36@wordpress.org>
References: <053.8da77a746ac94216f60abec6424c3d36@wordpress.org>
Message-ID: <068.a710916a7f26e1191fbc9b92abf49881@wordpress.org>

#4267: Version article title should look different than rest of the headings
-----------------------+--------------------------
 Reporter:  kartiks16  |       Owner:  coffee2code
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  HelpHub    |  Resolution:  fixed
 Keywords:  has-patch  |
-----------------------+--------------------------
Changes (by coffee2code):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8940" 8940]:
 {{{
 #!CommitTicketReference repository="" revision="8940"
 Support Theme: Increase font size for `h1` to differentiate it from `h2`
 on HelpHub pages.

 Props milana_cap, kartiks16.
 Fixes #4267.
 }}}

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

From noreply at wordpress.org  Tue Jun 11 20:52:54 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Jun 2019 20:52:54 +0000 (UTC)
Subject: [wp-meta] [8941]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/handbook/inc/navigation.php:
 Handbook plugin: Fix navigation links for menu-based handbooks.
Message-ID: <20190611205254.9807C1B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190611/c5a56b5c/attachment.html>

From noreply at wordpress.org  Tue Jun 11 21:01:36 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Jun 2019 21:01:36 +0000 (UTC)
Subject: [wp-meta] [8942]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/handbook/inc/widgets.php:
 Handbook plugin: Change default sortby for Handbook Pages widget from
 'post_title' to 'menu_order'.
Message-ID: <20190611210136.AFDFF1B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190611/e1b22465/attachment.html>

From noreply at wordpress.org  Tue Jun 11 21:21:57 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Jun 2019 21:21:57 +0000 (UTC)
Subject: [wp-meta] [8943]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 Support Theme: Bump CSS version for cache bust.
Message-ID: <20190611212157.EE3901B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190611/b9825cc3/attachment-0001.html>

From noreply at wordpress.org  Tue Jun 11 21:23:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 21:23:38 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make "make
 glossary" less obtrusive
Message-ID: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+--------------------
 Reporter:  tobifjellner              |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+--------------------
 The new https://wordpress.org/plugins/wporg-glossary/ is a good idea.
 However, if a page on make has many matches against the glossary, it may
 become hard to handle the page: whenever you move the pointer over the
 page you almost always happen to pass over some explained term (that you
 almost always know very well...) and ... poff a popup blows up and you
 have to wait a bit before you can continue what you were doing.

 Suggestion: Make the popups trigger on click and not on hover.

 I've suggested the same in https://wordpress.org/support/topic/could-it-
 be-a-bit-less-obtrusive/ I just don't know where is the best place for
 this.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4508>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 11 21:26:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Jun 2019 21:26:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make
 "make glossary" less obtrusive
In-Reply-To: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
References: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
Message-ID: <071.b9b46f58b2a4f932019610d06a3f1642@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by garrett-eclipse):

 Thought: If hover is too fast and click isn't desired there's always
 hover-intent.

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

From noreply at wordpress.org  Wed Jun 12 01:27:40 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Jun 2019 01:27:40 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make
 "make glossary" less obtrusive
In-Reply-To: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
References: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
Message-ID: <071.b7d3bb10b1670a82d7d62930e61d0efb@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+---------------------
Changes (by dd32):

 * keywords:   => needs-patch


Comment:

 We had considered using click, in combination with a few other things for
 accessibility, but ultimately had ruled out using click for a few
 different reasons that I'm not going to go into right now.

 Using hoverintent style approach however makes a lot of sense here, and
 will mostly avoid unintentional expansions.

 If there's any pages which are showing the glossary definitions
 particularly badly, I'd appreciate it being linked here for reference so
 it can be taken into account.  Some glossary items have been removed if
 they're not as useful as could be.

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

From noreply at wordpress.org  Wed Jun 12 04:21:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Jun 2019 04:21:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make
 "make glossary" less obtrusive
In-Reply-To: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
References: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
Message-ID: <071.600202bf7a3131b21cd728c49552364d@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+---------------------

Comment (by tobifjellner):

 > If there's any pages which are showing the glossary definitions
 particularly badly,
 > I'd appreciate it being linked here for reference so it can be taken
 into account.
 > Some glossary items have been removed if they're not as useful as could
 be.
 @dd32 The pre-existing Polyglots glossary has some quite long
 "explanations", if several of them happen to match a in page, then there
 may be several dangerous spots in a post, where I need to, say, mark some
 checkboxes... See, for instance,
 https://make.wordpress.org/polyglots/2019/06/11/clpte-request-woobewoo-
 plugins/

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

From noreply at wordpress.org  Wed Jun 12 04:44:41 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Jun 2019 04:44:41 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make
 "make glossary" less obtrusive
In-Reply-To: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
References: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
Message-ID: <071.34a3e7a3cf70bcdd040cd2a9de7685ea@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+---------------------

Comment (by garrett-eclipse):

 One other thing to note with the post @tobifjellner pointed out, along
 with the quick to popup it takes a long time to go away so you either need
 to click away or wait to read the content that gets hidden behind the
 post. When a user desires to read the content they usually stay on the
 word or in the tooltip so leaving the hover area might be improved by
 dismissing a little faster.

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

From noreply at wordpress.org  Wed Jun 12 13:55:42 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Jun 2019 13:55:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3773: Request from Marketing
 Team to Implement Navigation Change at make.wordpress.org
In-Reply-To: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
References: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
Message-ID: <074.85466e9a479b1fa48a4122bb0819dff2@wordpress.org>

#3773: Request from Marketing Team to Implement Navigation Change at
make.wordpress.org
-------------------------------------------------+-------------------------
 Reporter:  westcountymedia                      |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  high                                 |   Milestone:
Component:  Make (Get Involved) / P2             |  Resolution:
 Keywords:  ui-feedback ux-feedback 2nd-opinion  |
  needs-design                                   |
-------------------------------------------------+-------------------------
Changes (by hedgefield):

 * Attachment "Screen Shot 2019-06-12 at 15.53.17.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3773>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 12 13:56:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Jun 2019 13:56:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3773: Request from Marketing
 Team to Implement Navigation Change at make.wordpress.org
In-Reply-To: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
References: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
Message-ID: <074.e019b9e57318d5af41c4892f8376c095@wordpress.org>

#3773: Request from Marketing Team to Implement Navigation Change at
make.wordpress.org
-------------------------------------------------+---------------------
 Reporter:  westcountymedia                      |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  high                                 |   Milestone:
Component:  Make (Get Involved) / P2             |  Resolution:
 Keywords:  ui-feedback ux-feedback 2nd-opinion  |
-------------------------------------------------+---------------------
Changes (by hedgefield):

 * keywords:  ui-feedback ux-feedback 2nd-opinion needs-design => ui-
     feedback ux-feedback 2nd-opinion


Comment:

 Gotcha, I attached a quick edit to show what this would look like (man,
 still confused by how Trac handles attachments ha). I added some example
 copy for the content boxes.

 p.s. The masonry grid on the Make page isn't as easy to manipulate as
 you'd think, so apologies for the incorrect icons.

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

From noreply at wordpress.org  Wed Jun 12 21:49:07 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Jun 2019 21:49:07 +0000 (UTC)
Subject: [wp-meta] [8944]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/: Plugins: Add
 `pwa` feature plugin for offline schedule beta test.
Message-ID: <20190612214907.3EC251B0042E@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190612/be8f5d58/attachment.html>

From noreply at wordpress.org  Thu Jun 13 05:51:21 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 05:51:21 +0000 (UTC)
Subject: [wp-meta] [8945]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-make-sites-cpt/make_sites_cpt.php:
 Make sites CPT: allow fetching list of Make sites via API
Message-ID: <20190613055121.552BE1B004DF@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/e8e3a7e2/attachment.html>

From noreply at wordpress.org  Thu Jun 13 05:53:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 05:53:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4509: Long name gets unreadable
Message-ID: <053.3783758a921f8279d3e07df075577543@wordpress.org>

#4509: Long name gets unreadable
--------------------------------------+--------------------
 Reporter:  Presskopp                 |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 Look at https://translate.wordpress.org/locale/de/default/wp-
 plugins/jetpack/

 and you'll see that the long contributor name will be hidden behind the
 "Editor" role.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4509>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 13 05:53:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 05:53:24 -0000
Subject: [wp-meta] [Making WordPress.org] #4509: Long name gets
 unreadable
In-Reply-To: <053.3783758a921f8279d3e07df075577543@wordpress.org>
References: <053.3783758a921f8279d3e07df075577543@wordpress.org>
Message-ID: <068.5dfe9cdc4f6e2ae18e2d60b81d745714@wordpress.org>

#4509: Long name gets unreadable
--------------------------------------+---------------------
 Reporter:  Presskopp                 |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by Presskopp):

 * Attachment "long_title_bug.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4509>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 13 08:46:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 08:46:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4506: i18n: Create list with
 CL-PTE's and their respective projects
In-Reply-To: <056.0c852f5540d41ccb48a6a098cc0e473a@wordpress.org>
References: <056.0c852f5540d41ccb48a6a098cc0e473a@wordpress.org>
Message-ID: <071.272e1f08b4226acec52feacfcf635663@wordpress.org>

#4506: i18n: Create list with CL-PTE's and their respective projects
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by Nao):

 Yes, it's important for GTEs to be able to access CLPTEs' info and their
 assigned project.

 While I agree with @tobifjellner's idea for having a separate page to list
 CLPTEs, I think it should be very simple (just their display
 name/Gravatar/Slack/link to profile).

 In addition, I'd like to see:

 1) **Filter**: On https://translate.wordpress.org/locale/XX/, add a filter
 "CLPTE assigned" to list all projects with a CLPTE.
 2) **New Profile Tab**: On https://profiles.wordpress.org/USERNAME/ , add
 a tab that says "Translations" under Activity/Plugins/Themes, above
 Favorites. With this, GTEs and PTEs should also have their assigned
 projects/locale listed here.

 With 1, GTEs can check the progress of each project with a familiar
 screen.
 2 is also beneficial for all *TEs. They can easily access & display their
 contribution status.

 I know I'm requesting 3 things instead of one but the new profile tab is
 needed not only for CLPTE.

 (Translator specific profile page could be an alternative to 2, if having
 such page on translate.wordpress.org makes more sense than
 profiles.wordpress.org)

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

From noreply at wordpress.org  Thu Jun 13 09:57:50 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 09:57:50 +0000 (UTC)
Subject: [wp-meta] [8946]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/class-plugin-directory.php:
 Plugin dir: add Block browse option.
Message-ID: <20190613095750.EE33C1B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/8ca4c149/attachment.html>

From noreply at wordpress.org  Thu Jun 13 15:50:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 15:50:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4509: Long name gets
 unreadable
In-Reply-To: <053.3783758a921f8279d3e07df075577543@wordpress.org>
References: <053.3783758a921f8279d3e07df075577543@wordpress.org>
Message-ID: <068.ca88ecc4b146eccbe7eb47f116489d13@wordpress.org>

#4509: Long name gets unreadable
--------------------------------------+---------------------
 Reporter:  Presskopp                 |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by Presskopp):

 Possible patch:


 {{{
 img.avatar, .contributor-name span {
     float: left;
 }
 }}}

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

From noreply at wordpress.org  Thu Jun 13 15:53:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 15:53:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4509: Long name gets
 unreadable
In-Reply-To: <053.3783758a921f8279d3e07df075577543@wordpress.org>
References: <053.3783758a921f8279d3e07df075577543@wordpress.org>
Message-ID: <068.712485991bb4a65b032745b3fa8b53a6@wordpress.org>

#4509: Long name gets unreadable
--------------------------------------+---------------------
 Reporter:  Presskopp                 |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by Presskopp):

 * Attachment "with_patch.jpg" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4509>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 13 15:53:41 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 15:53:41 -0000
Subject: [wp-meta] [Making WordPress.org] #4509: Long name gets
 unreadable
In-Reply-To: <053.3783758a921f8279d3e07df075577543@wordpress.org>
References: <053.3783758a921f8279d3e07df075577543@wordpress.org>
Message-ID: <068.e208287c0cf7c11869e6ea4032091f4c@wordpress.org>

#4509: Long name gets unreadable
--------------------------------------+---------------------
 Reporter:  Presskopp                 |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  has-screenshots           |
--------------------------------------+---------------------
Changes (by Presskopp):

 * keywords:   => has-screenshots


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

From noreply at wordpress.org  Thu Jun 13 18:21:57 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 18:21:57 -0000
Subject: [wp-meta] [Making WordPress.org] #4510: Announce rights in @wceu
Message-ID: <051.eb5cf88b922419521fc67a5c61ef784f@wordpress.org>

#4510: Announce rights in @wceu
-------------------------+--------------------
 Reporter:  casiepa      |      Owner:  (none)
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Slack & IRC  |   Keywords:
-------------------------+--------------------
 Could someone please grant me announce rights in slack #wceu? I'm
 organizer.
 w.org @casiepa
 slack @Pascal

 Thanks!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4510>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 13 20:47:00 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 20:47:00 +0000 (UTC)
Subject: [wp-meta] [8947]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Grant
 announce privilege to casiepa for #wceu.
Message-ID: <20190613204700.2A6CE1B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/eccf9dbc/attachment.html>

From noreply at wordpress.org  Thu Jun 13 20:47:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Jun 2019 20:47:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4510: Announce rights in @wceu
In-Reply-To: <051.eb5cf88b922419521fc67a5c61ef784f@wordpress.org>
References: <051.eb5cf88b922419521fc67a5c61ef784f@wordpress.org>
Message-ID: <066.5a67668ee390bb843a3a6e2252828937@wordpress.org>

#4510: Announce rights in @wceu
-------------------------+--------------------------
 Reporter:  casiepa      |       Owner:  coffee2code
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:               |
-------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8947" 8947]:
 {{{
 #!CommitTicketReference repository="" revision="8947"
 Slack: Grant announce privilege to casiepa for #wceu.

 Fixes #4510.
 }}}

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

From noreply at wordpress.org  Thu Jun 13 20:55:13 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 20:55:13 +0000 (UTC)
Subject: [wp-meta] [8948]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Use correct
 w.org login for TimothyBlynJacobs.
Message-ID: <20190613205513.558401B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/cfbc0a06/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 13 20:58:37 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 20:58:37 +0000 (UTC)
Subject: [wp-meta] [8949]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Make note of
 casiepa's Slack username.
Message-ID: <20190613205837.20B191B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/12e9245b/attachment.html>

From noreply at wordpress.org  Thu Jun 13 22:31:41 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 22:31:41 +0000 (UTC)
Subject: [wp-meta] [8950]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/content-home.php:
 Jobs: Sort front page listing by job categories according to recency of
 their most recently posted jobs.
Message-ID: <20190613223141.81D431B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/06c7af2b/attachment.html>

From noreply at wordpress.org  Thu Jun 13 22:32:34 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Jun 2019 22:32:34 +0000 (UTC)
Subject: [wp-meta] [8951]
 sites/trunk/jobs.wordpress.net/public_html/wp-content/themes/jobswp/style.css:
 Jobs: Add icon for new 'Contributor' position type.
Message-ID: <20190613223234.58AD41B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190613/53e7ce8f/attachment.html>

From noreply at wordpress.org  Fri Jun 14 05:59:45 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Jun 2019 05:59:45 +0000 (UTC)
Subject: [wp-meta] [8952]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-meeting-posttype/wporg-meeting-posttype.php:
 Make/meetings: adapt the meeting_time shortcode so it can be used on all
 Make sites.
Message-ID: <20190614055945.8DCE01B00558@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190614/d8776b34/attachment-0001.html>

From noreply at wordpress.org  Fri Jun 14 05:59:47 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Jun 2019 05:59:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3078: Meetings: Use a single
 place to store meeting times info
In-Reply-To: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
References: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
Message-ID: <073.0367fb2d9c50788c574227237db37cb7@wordpress.org>

#3078: Meetings: Use a single place to store meeting times info
--------------------------------------+-------------------------
 Reporter:  SergeyBiryukov            |       Owner:  tellyworth
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:  has-patch                 |
--------------------------------------+-------------------------

Comment (by tellyworth):

 In [changeset:"8952" 8952]:
 {{{
 #!CommitTicketReference repository="" revision="8952"
 Make/meetings: adapt the meeting_time shortcode so it can be used on all
 Make sites.

 Adds several parameters so it can be used in a sidebar. For example, to
 list all meetings for the Meta team:

 [meeting_time team="meta" before="" more=0 limit=-1 /]

 See #3078
 }}}

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

From noreply at wordpress.org  Fri Jun 14 06:09:56 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Jun 2019 06:09:56 +0000 (UTC)
Subject: [wp-meta] [8953]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-meeting-posttype/wporg-meeting-posttype.php:
 Make/meetings: fix post count for 'more' param in [8952]
Message-ID: <20190614060956.B86ED1B004F3@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190614/4b735876/attachment.html>

From noreply at wordpress.org  Fri Jun 14 06:09:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Jun 2019 06:09:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3078: Meetings: Use a single
 place to store meeting times info
In-Reply-To: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
References: <058.1f577249f3fe12c5316b965581063554@wordpress.org>
Message-ID: <073.eca459dd3b3f4a56f2342dcd9c77c4e7@wordpress.org>

#3078: Meetings: Use a single place to store meeting times info
--------------------------------------+-------------------------
 Reporter:  SergeyBiryukov            |       Owner:  tellyworth
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:  has-patch                 |
--------------------------------------+-------------------------

Comment (by tellyworth):

 In [changeset:"8953" 8953]:
 {{{
 #!CommitTicketReference repository="" revision="8953"
 Make/meetings: fix post count for 'more' param in [8952]

 See #3078
 }}}

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

From noreply at wordpress.org  Fri Jun 14 16:32:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Jun 2019 16:32:04 -0000
Subject: [wp-meta] [Making WordPress.org] #262: Automate WordCamp
 Gravatar Badge Creation
In-Reply-To: <051.401611a60373917b67de1429781f2ed0@wordpress.org>
References: <051.401611a60373917b67de1429781f2ed0@wordpress.org>
Message-ID: <066.d714aac0a397b6e74f2ac50856a4a38d@wordpress.org>

#262: Automate WordCamp Gravatar Badge Creation
----------------------------------------+-----------------------
 Reporter:  iandunn                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  assigned
 Priority:  high                        |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------

Comment (by iandunn):

 * I agree that "building" and "making" are more friendly than
 "generating". "Generating" sounds more "correct" to me, but that's
 probably just because I'm an engineer. "Exporting" sounds "correct" to me
 too, but probably isn't as friendly as "building" and "making". I agree
 that, for something like this, it makes sense to go with something more
 user-friendly. "Building badge data" has a nice alliterative ring to it :)
 It'd be fun if there were a good synonym for "data" that starts with a
 "b", but I can't find one :(

 * Adding a note to the badges landing page sounds good to me. For the
 InDesign page, I was thinking that, when they come back, if the data is
 still being built, the modal would pop up with the progress bar, just like
 it would as if they'd never left the page. Then, once it's finished, the
 spinner goes away and the download link is shown. So, they get a
 consistent interface/flow regardless of whether or not they stay on the
 page the whole time. That's just my first thought, though, I'm open to any
 other ideas you have!
  * The modal should be dismissible, though, so that they can restart the
 process if it gets stuck or something.

 * Streamlining the landing page sounds great!

 * The email notification should be fine. The wp-admin notice is doable,
 but might take a bit more time than we want to invest v1, since we'd have
 to add code to track if they've downloaded it or not.

 * Those Figma wireframes look great!

 * I'm guessing we'll want a spinner rather than a progress bar, since
 determining how far along in the process the script is will probably be
 too much of a time investment for v1. It'd be good to have some text
 letting the user know that the process could take up to 10 minutes,
 though.

 * I really like the friendliness of the "in progress" text, but the
 pedantic/literalist in me is a little offput by the promise that the data
 will be ready when they return, since it can take 5-10 minutes, and they
 might return before that. Maybe something like,
  [[br]][[br]]
  > Your badge data is being compiled. This can take up to 10 minutes, so
 feel free to navigate elsewhere while you wait, and you'll receive an
 email when it's finished.
  [[br]]
  That's just a rough draft, though, and I'm definitely open to other
 ideas.

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

From noreply at wordpress.org  Fri Jun 14 17:57:29 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Jun 2019 17:57:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3318: Change two sentences on
 wordpress.org/
In-Reply-To: <055.f2c1a95096fcf6cd25a30678968add81@wordpress.org>
References: <055.f2c1a95096fcf6cd25a30678968add81@wordpress.org>
Message-ID: <070.efd3bbe5ce39870075c772f267a8c11d@wordpress.org>

#3318: Change two sentences on wordpress.org/
-----------------------------------------+-----------------------
 Reporter:  IkusiMakusi                  |       Owner:  (none)
     Type:  enhancement                  |      Status:  reopened
 Priority:  normal                       |   Milestone:
Component:  General                      |  Resolution:
 Keywords:  has-patch reporter-feedback  |
-----------------------------------------+-----------------------

Comment (by IkusiMakusi):

 @tellyworth I'm sorry, but there isn't any confusion to be clarified. I
 explained which English text to change and why. I also proposed and
 alternative text (in English, of course).
  1. Why the actual text shouldn't be changed at all?
  2. What's wrong with the alternative text?

 From my point of view, the actual text can be enhanced because enacts
 values not shared by all of us. I think the text I proposed it does and it
 looks good! Adding a note for translators doesn't fix this issue, because
 my petition is about the original English text.

 Someone could try to justify why saying "Feel like a rock star" is better
 than saying "It's really easy!" and why saying "impress your friends" is
 better than saying "It's really easy!". Nobody did, so I think we should
 make the little change I proposed and close this issue. I know my petition
 is not usual, but I see it as just an enhancement.

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

From noreply at wordpress.org  Fri Jun 14 21:32:08 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Jun 2019 21:32:08 +0000 (UTC)
Subject: [wp-meta] [8954]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/: WordCamp: Add
 bd-payments-camptix plugin external at tag 1.2
Message-ID: <20190614213208.9BD731B00221@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190614/db020e90/attachment.html>

From noreply at wordpress.org  Sat Jun 15 08:55:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Jun 2019 08:55:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4511: Translation is duplicated
 in the tooltip
Message-ID: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>

#4511: Translation is duplicated in the tooltip
--------------------------------------+-----------------------------
 Reporter:  ivan192                   |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:  has-screenshots
--------------------------------------+-----------------------------
 If the term from the glossary is used string in one string, then when you
 hover the cursor on this term, the translation is duplicated in the
 tooltip.
 For example: https://translate.wordpress.org/projects/wp-
 plugins/basepress/dev/ru/default/?filters%5Boriginal_id%5D=7905313
 [[Image(https://i.paste.pics/cb4151ec037026a199afebf45fbc0964.png)]]

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4511>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun 15 09:01:43 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Jun 2019 09:01:43 -0000
Subject: [wp-meta] [Making WordPress.org] #4511: Translation is
 duplicated in the tooltip
In-Reply-To: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>
References: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>
Message-ID: <066.9b39bc20676d9915d622484928f7f09a@wordpress.org>

#4511: Translation is duplicated in the tooltip
--------------------------------------+---------------------
 Reporter:  ivan192                   |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  has-screenshots           |
--------------------------------------+---------------------

Comment (by ivan192):

 Sorry.
 If the term from the glossary is used **twice** in one string, then when
 you hover the cursor on this term, the translation is duplicated in the
 tooltip.

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

From noreply at wordpress.org  Mon Jun 17 17:35:12 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Jun 2019 17:35:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3791: Consider bumping
 pre-commit checker on plugins to PHP 7.1
In-Reply-To: <051.a649e8525280ac88e3ba1f38f27d5c23@wordpress.org>
References: <051.a649e8525280ac88e3ba1f38f27d5c23@wordpress.org>
Message-ID: <066.f6c2b714f8c46a7c0d0388bac94468c0@wordpress.org>

#3791: Consider bumping pre-commit checker on plugins to PHP 7.1
------------------------------+---------------------
 Reporter:  Ipstenu           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  pending-systems   |
------------------------------+---------------------

Comment (by Ipstenu):

 Is there anyone we can poke about this? It's getting progressively worse
 and more and more libraries people use are PHP 7.1+

 Plus now that we block new submissions until people have used their
 already approved plugins, we get developers stuck :( The only work-around
 I can do for them is close the plugin and let them continue on, but it's a
 terrible experience.

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

From noreply at wordpress.org  Mon Jun 17 19:44:21 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 17 Jun 2019 19:44:21 +0000 (UTC)
Subject: [wp-meta] [8955]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/: WordCamp: Bump
 Akismet plugin external to 4.1.2 tag
Message-ID: <20190617194421.7AFDF1B004A1@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190617/805ca0b8/attachment.html>

From noreply at wordpress.org  Mon Jun 17 22:40:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Jun 2019 22:40:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4512: Profiles: Round Gravatars
Message-ID: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>

#4512: Profiles: Round Gravatars
-------------------------+--------------------
 Reporter:  melchoyce    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Profiles     |   Keywords:
-------------------------+--------------------
 They look better 🤷‍♀️

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4512>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 17 22:40:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Jun 2019 22:40:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4512: Profiles: Round
 Gravatars
In-Reply-To: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>
References: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>
Message-ID: <068.a99af15dab38783fb46a9d9b9a537fd3@wordpress.org>

#4512: Profiles: Round Gravatars
-------------------------+---------------------
 Reporter:  melchoyce    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Profiles     |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by melchoyce):

 * Attachment "Screen Shot 2019-06-17 at 6.40.07 PM.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4512>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 17 22:40:42 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 17 Jun 2019 22:40:42 +0000 (UTC)
Subject: [wp-meta] [8956]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/: WordCamp: Bump
 Jetpack plugin external to 7.4.1 tag
Message-ID: <20190617224042.499081B004A1@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190617/fe237546/attachment.html>

From noreply at wordpress.org  Mon Jun 17 23:27:32 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 17 Jun 2019 23:27:32 +0000 (UTC)
Subject: [wp-meta] [8957]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/: WordCamp: Bump
 Gutenberg plugin external to 5.9.2 tag
Message-ID: <20190617232732.91C371B004A1@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190617/8b1fdda3/attachment-0001.html>

From noreply at wordpress.org  Mon Jun 17 23:46:14 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Jun 2019 23:46:14 -0000
Subject: [wp-meta] [Making WordPress.org] #4512: Profiles: Round
 Gravatars
In-Reply-To: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>
References: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>
Message-ID: <068.96337250464e86d86c18b5af6a559709@wordpress.org>

#4512: Profiles: Round Gravatars
-------------------------+--------------------------
 Reporter:  melchoyce    |       Owner:  coffee2code
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:
Component:  Profiles     |  Resolution:
 Keywords:               |
-------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => accepted


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

From noreply at wordpress.org  Mon Jun 17 23:51:46 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Jun 2019 23:51:46 -0000
Subject: [wp-meta] [Making WordPress.org] #4512: Profiles: Round
 Gravatars
In-Reply-To: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>
References: <053.656f974b19f1a0bf504c07d55796c0bc@wordpress.org>
Message-ID: <068.49bca91666ff293e4e26f8c888d5a6ac@wordpress.org>

#4512: Profiles: Round Gravatars
-------------------------+--------------------------
 Reporter:  melchoyce    |       Owner:  coffee2code
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Profiles     |  Resolution:  fixed
 Keywords:               |
-------------------------+--------------------------
Changes (by coffee2code):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 Agreed!

 Implemented in [dotorg-15148].

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

From noreply at wordpress.org  Tue Jun 18 00:41:37 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 00:41:37 -0000
Subject: [wp-meta] [Making WordPress.org] #4513: Profiles header takes two
 lines instead of one
Message-ID: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>

#4513: Profiles header takes two lines instead of one
----------------------------+-----------------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Profiles        |   Keywords:  has-screenshots
----------------------------+-----------------------------
 Since [8916], Profiles header has extra whitespace and takes two lines
 instead of one, which is inconsistent with similar headers in other
 WordPress.org sections.

 Previously, "Logged in as ..." and "Log Out" links were on the same line
 with the heading.

 See the screenshot.

 Caused by removing `float: left` from `#headline h2` in [8916].

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4513>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 18 00:41:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 00:41:50 -0000
Subject: [wp-meta] [Making WordPress.org] #4513: Profiles header takes
 two lines instead of one
In-Reply-To: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>
References: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>
Message-ID: <073.3f676d9357929a11c7ef4e9949a15c09@wordpress.org>

#4513: Profiles header takes two lines instead of one
-----------------------------+---------------------
 Reporter:  SergeyBiryukov   |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Profiles         |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "4513.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4513>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 18 01:24:35 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 01:24:35 -0000
Subject: [wp-meta] [Making WordPress.org] #4511: Translation is
 duplicated in the tooltip
In-Reply-To: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>
References: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>
Message-ID: <066.ba06e41aec058533b823650b6c19b8eb@wordpress.org>

#4511: Translation is duplicated in the tooltip
--------------------------------------+---------------------
 Reporter:  ivan192                   |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  has-screenshots close     |
--------------------------------------+---------------------
Changes (by garrett-eclipse):

 * keywords:  has-screenshots => has-screenshots close


Comment:

 Hi @ivan192 I ran into this myself and opened an issue upstream via
 GlotPress - https://github.com/GlotPress/GlotPress-WP/issues/915

 This was fixed in GP but pending it's 3.0 version, marking for close but
 will leave a quick-fix link for the Meta team if they want to address
 prior to the upstream fix.
 GP Fix - https://github.com/GlotPress/GlotPress-
 WP/pull/917/commits/6bc5c1ed6d2dbbe87e894e4ba3e68f6f5945e289

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

From noreply at wordpress.org  Tue Jun 18 03:17:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 03:17:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4514: Add support for 'Requires
 at least' and 'Requires PHP' headers in the main plugin file
Message-ID: <058.38b2d86a08ac5ab7ccac44b6d2b1c93a@wordpress.org>

#4514: Add support for 'Requires at least' and 'Requires PHP' headers in the main
plugin file
------------------------------+--------------------
 Reporter:  SergeyBiryukov    |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 Background: #2952 added support for `Requires PHP` plugin header.

 At the time, it made sense to have it defined in the same place as
 `Requires at least`, which only exists in `readme.txt`.

 Per discussion with @Otto42 in #WP46938, a decision was made for WP core
 to read both `Requires at least` and `Requires PHP` headers from the
 plugin' main PHP file as well, and give precedence to those instead of the
 ones from the `readme.txt` file.

 For consistency, Plugin Directory should do the same.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4514>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 18 05:11:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 05:11:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4514: Add support for
 'Requires at least' and 'Requires PHP' headers in the main plugin file
In-Reply-To: <058.38b2d86a08ac5ab7ccac44b6d2b1c93a@wordpress.org>
References: <058.38b2d86a08ac5ab7ccac44b6d2b1c93a@wordpress.org>
Message-ID: <073.25c0581fcb9ce80bcc300fedbbcc5d72@wordpress.org>

#4514: Add support for 'Requires at least' and 'Requires PHP' headers in the main
plugin file
------------------------------+---------------------
 Reporter:  SergeyBiryukov    |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------
Description changed by SergeyBiryukov:

Old description:

> Background: #2952 added support for `Requires PHP` plugin header.
>
> At the time, it made sense to have it defined in the same place as
> `Requires at least`, which only exists in `readme.txt`.
>
> Per discussion with @Otto42 in #WP46938, a decision was made for WP core
> to read both `Requires at least` and `Requires PHP` headers from the
> plugin' main PHP file as well, and give precedence to those instead of
> the ones from the `readme.txt` file.
>
> For consistency, Plugin Directory should do the same.

New description:

 Background: #2952 added support for `Requires PHP` plugin header.

 At the time, it made sense to have it defined in the same place as
 `Requires at least`, which only exists in `readme.txt`.

 Per discussion with @Otto42 in #WP46938, a decision was made for WP core
 to read both `Requires at least` and `Requires PHP` headers from the
 plugin's main PHP file as well, and give precedence to those instead of
 the ones from the `readme.txt` file.

 For consistency, Plugin Directory should do the same.

--

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

From noreply at wordpress.org  Tue Jun 18 06:02:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 06:02:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4511: Translation is
 duplicated in the tooltip
In-Reply-To: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>
References: <051.1f01ca6bbc4c96d44c62de5830fb1935@wordpress.org>
Message-ID: <066.8f2a39cb4c55f07f3733d43c49b78694@wordpress.org>

#4511: Translation is duplicated in the tooltip
--------------------------------------+--------------------------------
 Reporter:  ivan192                   |       Owner:  (none)
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  reported-upstream
 Keywords:  has-screenshots           |
--------------------------------------+--------------------------------
Changes (by ocean90):

 * keywords:  has-screenshots close => has-screenshots
 * status:  new => closed
 * resolution:   => reported-upstream


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

From noreply at wordpress.org  Tue Jun 18 15:15:01 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Jun 2019 15:15:01 +0000 (UTC)
Subject: [wp-meta] [8958]
 sites/trunk/api.wordpress.org/public_html/core/credits/wp-52.php: Credits
 API: Update credits for WordPress 5.2.2.
Message-ID: <20190618151501.35EF01B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190618/ca5ca114/attachment.html>

From noreply at wordpress.org  Tue Jun 18 16:41:47 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 16:41:47 -0000
Subject: [wp-meta] [Making WordPress.org] #4515: Updating Trac ticket w/
 multi-byte characters get stripped.
Message-ID: <059.685bf8672d52f99c36a8d0c3b233df22@wordpress.org>

#4515: Updating Trac ticket w/ multi-byte characters get stripped.
-----------------------------+--------------------
 Reporter:  garrett-eclipse  |      Owner:  (none)
     Type:  defect           |     Status:  new
 Priority:  normal           |  Milestone:
Component:  Trac             |   Keywords:
-----------------------------+--------------------
 Hello,

 I found by adding a comment to
 [https://core.trac.wordpress.org/ticket/47547 core#47547] that it created
 an unintended Description change. Reviewing the
 [https://core.trac.wordpress.org/ticket/47547?action=diff&version=1 diff]
 it seems the multi-byte characters were stripped.

 On the core Trac I have permissions to modify ticket properties, I didn't
 touch the description field, but assume the cause is the description field
 found in the modify properties section doesn't support the emojis (multi-
 byte characters) like the textarea on 'Create new Ticket' does.

 Thank you

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4515>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 18 16:44:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 16:44:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4515: Updating Trac ticket w/
 multi-byte characters get stripped.
In-Reply-To: <059.685bf8672d52f99c36a8d0c3b233df22@wordpress.org>
References: <059.685bf8672d52f99c36a8d0c3b233df22@wordpress.org>
Message-ID: <074.953ea7be0fc1f99348db9f786a696e9a@wordpress.org>

#4515: Updating Trac ticket w/ multi-byte characters get stripped.
-----------------------------+------------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:  duplicate
 Keywords:                   |
-----------------------------+------------------------
Changes (by ocean90):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #3838.

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

From noreply at wordpress.org  Tue Jun 18 19:37:52 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Jun 2019 19:37:52 +0000 (UTC)
Subject: [wp-meta] [8959]
 sites/trunk/api.wordpress.org/public_html/core/credits/wp-52.php: Credits
 API: Update credits for WordPress 5.2.2.
Message-ID: <20190618193752.D48341B004A1@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190618/91e7e726/attachment.html>

From noreply at wordpress.org  Tue Jun 18 20:46:53 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Jun 2019 20:46:53 -0000
Subject: [wp-meta] [Making WordPress.org] #3631: Gravatars aren't
 lazy-loaded when multiple [camptix_attendees] shortcodes are used on the
 same page
In-Reply-To: <051.4dc68fe918f5a1988fea62f43901e758@wordpress.org>
References: <051.4dc68fe918f5a1988fea62f43901e758@wordpress.org>
Message-ID: <066.ed45d200fc1cf4bcd548abe41a93e104@wordpress.org>

#3631: Gravatars aren't lazy-loaded when multiple [camptix_attendees] shortcodes
are used on the same page
----------------------------------------+------------------------
 Reporter:  iandunn                     |       Owner:  (none)
     Type:  defect                      |      Status:  closed
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:  duplicate
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+------------------------
Changes (by coreymckrill):

 * status:  assigned => closed
 * resolution:   => duplicate


Comment:

 #3854 is newer and reports the same issue, but it already has a patch, so
 closing this one as the duplicate.

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

From noreply at wordpress.org  Tue Jun 18 21:36:46 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Jun 2019 21:36:46 +0000 (UTC)
Subject: [wp-meta] [8960]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Give announce
 to amykamala in #hosting-community, per jadonn.
Message-ID: <20190618213646.E29BB1B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190618/e742130f/attachment-0001.html>

From noreply at wordpress.org  Wed Jun 19 01:35:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 01:35:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4515: Updating Trac ticket w/
 multi-byte characters get stripped.
In-Reply-To: <059.685bf8672d52f99c36a8d0c3b233df22@wordpress.org>
References: <059.685bf8672d52f99c36a8d0c3b233df22@wordpress.org>
Message-ID: <074.f4a479da8a77946ecf63b2c2e315fa1a@wordpress.org>

#4515: Updating Trac ticket w/ multi-byte characters get stripped.
-----------------------------+------------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:  duplicate
 Keywords:                   |
-----------------------------+------------------------
Description changed by SergeyBiryukov:

Old description:

> Hello,
>
> I found by adding a comment to
> [https://core.trac.wordpress.org/ticket/47547 core#47547] that it created
> an unintended Description change. Reviewing the
> [https://core.trac.wordpress.org/ticket/47547?action=diff&version=1 diff]
> it seems the multi-byte characters were stripped.
>
> On the core Trac I have permissions to modify ticket properties, I didn't
> touch the description field, but assume the cause is the description
> field found in the modify properties section doesn't support the emojis
> (multi-byte characters) like the textarea on 'Create new Ticket' does.
>
> Thank you

New description:

 Hello,

 I found by adding a comment to #core47547 that it created an unintended
 Description change. Reviewing the
 [https://core.trac.wordpress.org/ticket/47547?action=diff&version=1 diff]
 it seems the multi-byte characters were stripped.

 On the core Trac I have permissions to modify ticket properties, I didn't
 touch the description field, but assume the cause is the description field
 found in the modify properties section doesn't support the emojis (multi-
 byte characters) like the textarea on 'Create new Ticket' does.

 Thank you

--

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

From noreply at wordpress.org  Wed Jun 19 05:04:11 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 05:04:11 +0000 (UTC)
Subject: [wp-meta] [8961]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer:
 Developer: Create Common APIs handbook.
Message-ID: <20190619050411.DC0C41B00594@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/678fa450/attachment.html>

From noreply at wordpress.org  Wed Jun 19 05:04:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 05:04:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4376: Centralized API handbook
In-Reply-To: <051.a9a8b13ace9672d314a033e9ddfb11e1@wordpress.org>
References: <051.a9a8b13ace9672d314a033e9ddfb11e1@wordpress.org>
Message-ID: <066.7227d547e8f4077c429a90d987ff0c56@wordpress.org>

#4376: Centralized API handbook
---------------------------+---------------------
 Reporter:  casiepa        |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  2nd-opinion    |
---------------------------+---------------------

Comment (by coffee2code):

 In [changeset:"8961" 8961]:
 {{{
 #!CommitTicketReference repository="" revision="8961"
 Developer: Create Common APIs handbook.

 Handbook is currently only accessible to logged-in users.

 See #4376.
 }}}

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

From noreply at wordpress.org  Wed Jun 19 05:10:57 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 05:10:57 +0000 (UTC)
Subject: [wp-meta] [8962]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc/template-tags.php:
 Developer: Customize section title for Common APIs handbook.
Message-ID: <20190619051057.2A0801B00594@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/d62caf39/attachment-0001.html>

From noreply at wordpress.org  Wed Jun 19 05:10:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 05:10:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4376: Centralized API handbook
In-Reply-To: <051.a9a8b13ace9672d314a033e9ddfb11e1@wordpress.org>
References: <051.a9a8b13ace9672d314a033e9ddfb11e1@wordpress.org>
Message-ID: <066.7b17e6bb2ef254988281754b8df74cf8@wordpress.org>

#4376: Centralized API handbook
---------------------------+---------------------
 Reporter:  casiepa        |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  2nd-opinion    |
---------------------------+---------------------

Comment (by coffee2code):

 In [changeset:"8962" 8962]:
 {{{
 #!CommitTicketReference repository="" revision="8962"
 Developer: Customize section title for Common APIs handbook.

 See #4376.
 }}}

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

From noreply at wordpress.org  Wed Jun 19 05:28:22 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 05:28:22 -0000
Subject: [wp-meta] [Making WordPress.org] #4376: Centralized API handbook
In-Reply-To: <051.a9a8b13ace9672d314a033e9ddfb11e1@wordpress.org>
References: <051.a9a8b13ace9672d314a033e9ddfb11e1@wordpress.org>
Message-ID: <066.25706c454f3e1f0068ce6584261c4de6@wordpress.org>

#4376: Centralized API handbook
---------------------------+--------------------------
 Reporter:  casiepa        |       Owner:  coffee2code
     Type:  enhancement    |      Status:  accepted
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:                 |
---------------------------+--------------------------
Changes (by coffee2code):

 * keywords:  2nd-opinion =>
 * owner:  (none) => coffee2code
 * status:  new => accepted


Comment:

 The Common APIs handbook has been created and accessible (only to logged-
 in users) via https://developer.wordpress.org/apis/.

 I've held off on adding a !DevHub front page block for it until later.
 Relatedly, the details for the block could stand to be agreed upon.
 Currently I have:

 * Dashicon: https://developer.wordpress.org/resource/dashicons/#admin-
 site-alt3
 * Block description (in the form of a question): "Interested in
 interacting with various APIs?"
 * Link text: "Utilize APIs"
 * Position: first block in second row (when each row displays 3 blocks)

 This ticket can be closed out once the handbook has been added to the
 !DevHub front page and made publicly accessible.

 @casiepa: You're already a handbook editor, but be sure to coordinate with
 the rest of the Docs team to confirm the structure and style of the
 handbook before getting too far with things.

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

From noreply at wordpress.org  Wed Jun 19 05:28:35 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 05:28:35 -0000
Subject: [wp-meta] [Making WordPress.org] #4513: Profiles header takes
 two lines instead of one
In-Reply-To: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>
References: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>
Message-ID: <073.6d4b3567040fbd1071eba1bc0312bbe9@wordpress.org>

#4513: Profiles header takes two lines instead of one
-----------------------------+--------------------------
 Reporter:  SergeyBiryukov   |       Owner:  coffee2code
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Profiles         |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => accepted


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

From noreply at wordpress.org  Wed Jun 19 05:29:08 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 05:29:08 -0000
Subject: [wp-meta] [Making WordPress.org] #4513: Profiles header takes
 two lines instead of one
In-Reply-To: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>
References: <058.61c7e56b9eec149033afd1cef30b635d@wordpress.org>
Message-ID: <073.67e0f476fe18c1a2248a345a9dc615a3@wordpress.org>

#4513: Profiles header takes two lines instead of one
-----------------------------+--------------------------
 Reporter:  SergeyBiryukov   |       Owner:  coffee2code
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Profiles         |  Resolution:  fixed
 Keywords:  has-screenshots  |
-----------------------------+--------------------------
Changes (by coffee2code):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 Fixed in [dotorg-15156].

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

From noreply at wordpress.org  Wed Jun 19 11:57:12 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 11:57:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3838: Editing Descriptions
 that contain emoji's strip the emoji
In-Reply-To: <059.bef77bea518e4f503775ad06809b5746@wordpress.org>
References: <059.bef77bea518e4f503775ad06809b5746@wordpress.org>
Message-ID: <074.d39bfddb5eab6c0b4a5b0df0959378ff@wordpress.org>

#3838: Editing Descriptions that contain emoji's strip the emoji
-----------------------------+---------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:
 Keywords:                   |
-----------------------------+---------------------

Comment (by dd32):

 Turns out that this isn't even a Trac bug, it's a combination Twemoji or
 WordPress Emoji issue.

 The tl;dr of it is, the
 [https://core.trac.wordpress.org/browser/trunk/src/js/_enqueues/wp/emoji.js?marks=160#L90
 WordPress Emoji MutationObserver] calls `twemoji.parse()` with a
 `textarea` node, which causes `twemoji.grabAllTextNodes()` to fetch all
 the subnodes of a `textarea` node, and not skip `textarea` as it "should".

 I'm debating on if it's a twemoji or WordPress Emoji bug (leaning towards
 the latter) as I think twemoji is doing exactly what is wanted, processing
 Emoji's within an element that's usually skipped but doing so because it's
 been told to process that exact node.
 On the other hand, maybe it's unexpected that passing a skipped node to
 `twemoji.parse()` should process it..

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

From noreply at wordpress.org  Wed Jun 19 14:38:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 14:38:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3838: Editing Descriptions
 that contain emoji's strip the emoji
In-Reply-To: <059.bef77bea518e4f503775ad06809b5746@wordpress.org>
References: <059.bef77bea518e4f503775ad06809b5746@wordpress.org>
Message-ID: <074.0b6808673df4bb7600e40f5c2b5b2da3@wordpress.org>

#3838: Editing Descriptions that contain emoji's strip the emoji
-----------------------------+-----------------------
 Reporter:  garrett-eclipse  |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:
 Keywords:                   |
-----------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


Comment:

 After chatting with Gary, I decided to just add the `wp-exclude-emoji`
 class to the textareas in Trac, I have a WIP patch for that.. but it needs
 some more testing

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

From noreply at wordpress.org  Wed Jun 19 18:55:07 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 18:55:07 +0000 (UTC)
Subject: [wp-meta] [8963]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: Service Worker
 Caching: Initial commit.
Message-ID: <20190619185507.266E11B0049F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/709d254d/attachment.html>

From noreply at wordpress.org  Wed Jun 19 18:55:14 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 18:55:14 +0000 (UTC)
Subject: [wp-meta] [8964]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: Day of Event
 Template: Initial commit.
Message-ID: <20190619185515.02E3F1B0049F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/5e6f8538/attachment-0001.html>

From noreply at wordpress.org  Wed Jun 19 19:05:07 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 19:05:07 -0000
Subject: [wp-meta] [Making WordPress.org] #4516: New & Updated in WordPress
 x.x URLS are all linking to the reference page
Message-ID: <049.87a41c05feedb68f1270abcc91ca50f9@wordpress.org>

#4516: New & Updated in WordPress x.x URLS are all linking to the reference page
---------------------------+-----------------------
 Reporter:  imath          |      Owner:  (none)
     Type:  defect         |     Status:  new
 Priority:  normal         |  Milestone:
Component:  Developer Hub  |   Keywords:  has-patch
---------------------------+-----------------------
 Hi,

 If you go to the Code Reference
 [https://developer.wordpress.org/reference/ landing page] and click on any
 of the links listed into the "New & Updated in WordPress x.x" box, you
 will simply refresh the page.

 I suggest the attached patch to fix the issue.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4516>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 19 19:05:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 19:05:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4516: New & Updated in
 WordPress x.x URLS are all linking to the reference page
In-Reply-To: <049.87a41c05feedb68f1270abcc91ca50f9@wordpress.org>
References: <049.87a41c05feedb68f1270abcc91ca50f9@wordpress.org>
Message-ID: <064.325ad4ad432a0c976984649fc0902598@wordpress.org>

#4516: New & Updated in WordPress x.x URLS are all linking to the reference page
---------------------------+---------------------
 Reporter:  imath          |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  has-patch      |
---------------------------+---------------------
Changes (by imath):

 * Attachment "4516.patch" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4516>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 19 19:14:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 19:14:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4517: Enqueueing chapter.js in
 wporg-developer theme so that child themes can enjoy it.
Message-ID: <049.9a3c24c1b308eeee23c1dd609a67cb35@wordpress.org>

#4517: Enqueueing chapter.js in wporg-developer theme so that child themes can
enjoy it.
---------------------------+-----------------------
 Reporter:  imath          |      Owner:  (none)
     Type:  defect         |     Status:  new
 Priority:  normal         |  Milestone:
Component:  Developer Hub  |   Keywords:  has-patch
---------------------------+-----------------------
 Hi,

 I'm building a child theme of wporg-developer and I currently have to
 dequeue `wporg-developer-chapters` to re-enqueue it using another handle
 and `get_template_directory_uri()` (instead of
 `get_stylesheet_directory_uri()` used in the `theme_scripts_styles()`
 function of the wporg-developer theme).

 Would it be possible to use `get_template_directory_uri()` directly in the
 wporg-developer theme? That would be really great.

 I'm attaching a patch with the suggested change.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4517>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 19 19:15:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 19:15:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4517: Enqueueing chapter.js
 in wporg-developer theme so that child themes can enjoy it.
In-Reply-To: <049.9a3c24c1b308eeee23c1dd609a67cb35@wordpress.org>
References: <049.9a3c24c1b308eeee23c1dd609a67cb35@wordpress.org>
Message-ID: <064.8f4e9fcc3f151959bfbcab909886f271@wordpress.org>

#4517: Enqueueing chapter.js in wporg-developer theme so that child themes can
enjoy it.
---------------------------+---------------------
 Reporter:  imath          |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  has-patch      |
---------------------------+---------------------
Changes (by imath):

 * Attachment "4517.patch" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4517>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 19 20:12:12 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 20:12:12 +0000 (UTC)
Subject: [wp-meta] [8965]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/page-reference-landing.php:
 Developer: Fix links for Code Reference resources listed in 'New &
 Updated'.
Message-ID: <20190619201212.DAFA81B0049F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/92c1b6be/attachment.html>

From noreply at wordpress.org  Wed Jun 19 20:12:14 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 20:12:14 -0000
Subject: [wp-meta] [Making WordPress.org] #4516: New & Updated in
 WordPress x.x URLS are all linking to the reference page
In-Reply-To: <049.87a41c05feedb68f1270abcc91ca50f9@wordpress.org>
References: <049.87a41c05feedb68f1270abcc91ca50f9@wordpress.org>
Message-ID: <064.435b9fcca537b4760b3402a60703a551@wordpress.org>

#4516: New & Updated in WordPress x.x URLS are all linking to the reference page
---------------------------+--------------------------
 Reporter:  imath          |       Owner:  coffee2code
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:  fixed
 Keywords:  has-patch      |
---------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8965" 8965]:
 {{{
 #!CommitTicketReference repository="" revision="8965"
 Developer: Fix links for Code Reference resources listed in 'New &
 Updated'.

 Props imath.
 Fixes #4516.
 }}}

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

From noreply at wordpress.org  Wed Jun 19 20:16:41 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 20:16:41 +0000 (UTC)
Subject: [wp-meta] [8966]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/functions.php:
 Developer: Use `get_template_directory_uri()` instead of
 `get_stylesheet_directory_uri()` when enqueuing js/chapters.js.
Message-ID: <20190619201641.586171B0049F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/6dbb062c/attachment-0001.html>

From noreply at wordpress.org  Wed Jun 19 20:16:43 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Jun 2019 20:16:43 -0000
Subject: [wp-meta] [Making WordPress.org] #4517: Enqueueing chapter.js
 in wporg-developer theme so that child themes can enjoy it.
In-Reply-To: <049.9a3c24c1b308eeee23c1dd609a67cb35@wordpress.org>
References: <049.9a3c24c1b308eeee23c1dd609a67cb35@wordpress.org>
Message-ID: <064.d8d823b8ac89822815c376ecfc9bd3bc@wordpress.org>

#4517: Enqueueing chapter.js in wporg-developer theme so that child themes can
enjoy it.
---------------------------+--------------------------
 Reporter:  imath          |       Owner:  coffee2code
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:  fixed
 Keywords:  has-patch      |
---------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8966" 8966]:
 {{{
 #!CommitTicketReference repository="" revision="8966"
 Developer: Use `get_template_directory_uri()` instead of
 `get_stylesheet_directory_uri()` when enqueuing js/chapters.js.

 Props imath.
 Fixes #4517.
 }}}

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

From noreply at wordpress.org  Wed Jun 19 23:44:50 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 23:44:50 +0000 (UTC)
Subject: [wp-meta] [8967]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/theme-templates/templates/day-of-event:
 Day of Event Template: Use timestamps for clarity.
Message-ID: <20190619234450.5D7051B0049F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/95946b8c/attachment-0001.html>

From noreply at wordpress.org  Wed Jun 19 23:45:42 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Jun 2019 23:45:42 +0000 (UTC)
Subject: [wp-meta] [8968]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/load-other-mu-plugins.php:
 Day of Event Template: Enable for `2019.europe`.
Message-ID: <20190619234542.A2A001B0049F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190619/7d75592b/attachment.html>

From noreply at wordpress.org  Thu Jun 20 07:34:09 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 07:34:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4430: Provide suggestions for
 translations
In-Reply-To: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
References: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
Message-ID: <066.9598cfb20cf46eaded224fb2a547615a@wordpress.org>

#4430: Provide suggestions for translations
--------------------------------------+-----------------------
 Reporter:  ocean90                   |       Owner:  ocean90
     Type:  task                      |      Status:  assigned
 Priority:  high                      |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by yoavf):

 For machine translation, I think we'd need API keys serverside - or an
 option to let users set their own API keys as an option. I'm not sure any
 of these options is suitable at this time, so maybe we can mark this as
 done? :)

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

From noreply at wordpress.org  Thu Jun 20 09:04:48 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:04:48 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
Message-ID: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>

#4518: Plan: translation discussions/feedback
-------------------------------------+-------------------------------------
 Reporter:  yoavf                    |      Owner:  (none)
     Type:  task                     |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  Translate Site &         |   Keywords:  needs-patch needs-
  Plugins                            |  design
-------------------------------------+-------------------------------------
 Based on discussions in WCEU 2019 contributor day, we'd like to allow
 translators and translation editors to communicate about specific strings
 and translations.

 Core GlotPress implemented a "Notes" feature, but as a native GP feature,
 it lacks any type of notification support or any of the basic features we
 associate with comments or discussion (threading, mentions, spam detection
 etc).

 Instead, we'd like to build a bridge between translate.wordpress.org and a
 per-locale specific translations forum.

 This will include:
  - On the GlotPress side, every original should have a link to a specific
 forum topic to discuss its translation to the locale. If the topic doesn't
 exist, it will link to a pre-populated form to create it. Otherwise, it
 will list the number of posts on that topic.
 - The topics will be created in a `translations` forum for each locale
 (i.e https://he.wordpress.org/support/forum/translation/).
 - The topics will link back to the original

 Bonus:
 - When rejecting a translation, the validator will be able to enter a
 comment about the rejection reason, which will be added to the topic as
 well.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4518>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 09:18:27 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:18:27 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
Message-ID: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+-------------------------
 Reporter:  Travel_girl       |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  needs-patch
------------------------------+-------------------------
 Currently the FAQ-Section in the plugin  directory are not accessible for
 various reasons.

 Problems

 1. Questions don't have a semantic structure. They are just links at the
 moment
 2. with a click on the link, nothing happens for screen reader users
 3. aria-expandet is on the wrong element and don't announce anything to a
 screen reader user


 Suggested solutions:

 1. questions should be semantic headlines (H3 as FAQ is H2)
 2. those headlines should include a button-element to expand the section.
 Because it causes an action, it should be a Button, not a link
 3. this button should have an aria-expanded true/false, so it gets
 announced to an screen reader users


 Please also have a look on the buttons

 Further ressources about accessible accordions:

 https://www.w3.org/TR/wai-aria-practices-1.1/#accordion
 https://inclusive-components.design/collapsible-sections/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4519>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 09:27:05 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:27:05 -0000
Subject: [wp-meta] [Making WordPress.org] #1456: WordPress.tv: Increase
 font sizes site-wide
In-Reply-To: <057.0059cf2adf9925a753f73d8dbfd4be76@wordpress.org>
References: <057.0059cf2adf9925a753f73d8dbfd4be76@wordpress.org>
Message-ID: <072.c389d8cebab48a93cf89c4cd12fe61b1@wordpress.org>

#1456: WordPress.tv: Increase font sizes site-wide
-----------------------------------------+---------------------
 Reporter:  davidjlaietta                |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  high                         |   Milestone:
Component:  WordPress.tv                 |  Resolution:
 Keywords:  needs-patch has-screenshots  |
-----------------------------------------+---------------------

Comment (by BrashRebel):

 If not the entire sidebar, at least the video description could be
 relocated from the sidebar to below the video. That is where the largest %
 of text is on the page and it typically fits poorly into its current
 space. If we move the description to under the video, the sidebar might
 otherwise be acceptable in its current state and the description's font
 size can be increased.

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

From noreply at wordpress.org  Thu Jun 20 09:27:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:27:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.db8e7cc1061e6a9a6be9df068aba6e7f@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by yoavf):

 Some tasks:

 Dev:
 - Script to create a forum called `translations` in each one of the
 rosetta sites. Some sites need bbPress setup first.
 - Form to post a new topic about a string (=original)
 - Functionality to fetch replies from a topic for display
 - Remove the "Notes" feature from core GlotPress.

 Design:
 - If the topic doesn't exist - link+form to create the topic (within GP
 UI)
 - It topic exist, list replies in the topic with helpful meta (author,
 date, etc)

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

From noreply at wordpress.org  Thu Jun 20 09:36:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:36:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.99e07e2db9e6ab048faa0b9805f386b4@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by yoavf):

 Additional tasks:
 - Add indication to a topic if an original status has been marked as
 `obsolete` in GlotPress (and remove if status is back to `active`)

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

From noreply at wordpress.org  Thu Jun 20 09:50:31 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:50:31 -0000
Subject: [wp-meta] [Making WordPress.org] #974: Make WordPress.tv theme
 responsive
In-Reply-To: <054.3f56752fb059e84796d7716779ffdb79@wordpress.org>
References: <054.3f56752fb059e84796d7716779ffdb79@wordpress.org>
Message-ID: <069.713711850a248e6533eb41c033333207@wordpress.org>

#974: Make WordPress.tv theme responsive
--------------------------------------------------+-----------------------
 Reporter:  BrashRebel                            |       Owner:  (none)
     Type:  enhancement                           |      Status:  assigned
 Priority:  normal                                |   Milestone:
Component:  WordPress.tv                          |  Resolution:
 Keywords:  good-first-bug has-patch ui-feedback  |
--------------------------------------------------+-----------------------

Comment (by BrashRebel):

 As far as I know, here's what else has been going on relative to this
 ticket:

 At some point, I believe in 2017, someone enabled the Jetpack mobile
 theme. Because of that, the urgency for this ticket's resolution went down
 a bit because that feature made the mobile theme load for small screens
 instead of the current theme.

 The latest patch, 974.3, I believe, is pretty complete and has not
 received feedback or been committed. I do believe it is a major
 improvement and worth committing.

 At this time, the Jetpack mobile theme is no longer enabled on
 WordPress.tv so the current non-responsive theme still loads for mobile.

 Also, @obenland I think the problem you reported 6 months ago may have
 been related to the Jetpack mobile theme and thus, no longer an issue.

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

From noreply at wordpress.org  Thu Jun 20 09:53:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 09:53:45 -0000
Subject: [wp-meta] [Making WordPress.org] #1434: Create terms list pages
In-Reply-To: <054.02d291c0ac7737fe4be60af3668313c7@wordpress.org>
References: <054.02d291c0ac7737fe4be60af3668313c7@wordpress.org>
Message-ID: <069.7e00966ffa9110a2c7978489be94ed96@wordpress.org>

#1434: Create terms list pages
--------------------------+---------------------
 Reporter:  BrashRebel    |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:  needs-design  |
--------------------------+---------------------
Changes (by BrashRebel):

 * keywords:   => needs-design


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

From noreply at wordpress.org  Thu Jun 20 10:05:35 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 10:05:35 -0000
Subject: [wp-meta] [Making WordPress.org] #3037: WordPress.tv: Show the
 views of the video
In-Reply-To: <049.a54f83f929f817a33348775440ec5fa8@wordpress.org>
References: <049.a54f83f929f817a33348775440ec5fa8@wordpress.org>
Message-ID: <064.6eacadec2f12727b79938d6fbcc8dac1@wordpress.org>

#3037: WordPress.tv: Show the views of the video
--------------------------+---------------------
 Reporter:  Mte90         |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:  needs-patch   |
--------------------------+---------------------
Changes (by BrashRebel):

 * keywords:   => needs-patch


Comment:

 Jerry's right, this looks completely possible and would be an exciting
 enhancement. Thanks for the suggestion @Mte90!

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

From noreply at wordpress.org  Thu Jun 20 10:06:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 10:06:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.b2f6a9c8c3e8d0190e2b0da9c58a924d@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by ottok):

 I suggest you start out with something much more simple. Instead of the
 modal thing we could start up with a dead simple list of supported PHP
 versions.

 There are two sources of information to consider here. First of all the
 current "PHP Version" line uses the "Requires PHP: N.N.N" from the plugin
 readme.txt. This should still be honored and used to set the minimum PHP
 version supported in a list fo supported PHP versions.

 The second source of information is the JSON report by WP Tide:

 {{{
 "compatible_versions":
 [
   "5.6",
   "7.0",
   "7.1",
   "7.2",
   "7.3"
 ],
 }}}

 From this list all values above the readme.txt stated minimum version
 should be used.

 My suggested UI is below. These examples are hopefully self-explanatory.

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

From noreply at wordpress.org  Thu Jun 20 10:06:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 10:06:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.8c76a17e77d1f236ac3db6cfcf795c67@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------
Changes (by ottok):

 * Attachment "compatible-with-up-to-latest.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4309>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 10:06:46 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 10:06:46 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.19822ebbebaf01a43b05eede9776c653@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------
Changes (by ottok):

 * Attachment "not-compatible-with-latest-warning.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4309>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 10:09:20 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 10:09:20 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.a70c57b521c3c8b7861475199f3e5166@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------
Changes (by ottok):

 * Attachment "compatible-with-up-to-latest.2.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4309>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 11:47:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 11:47:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.a8611637a8d3577e96584de631757644@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by ocean90):

 > The topics will be created in a `translations` forum for each locale

 At the moment only `ar.wordpress.org` and `he.wordpress.org` have a forum
 for `translation` (without `s`).

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

From noreply at wordpress.org  Thu Jun 20 11:57:32 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 11:57:32 +0000 (UTC)
Subject: [wp-meta] [8969]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-discussions:
 Translate: Add initial plugin for discussion implementation.
Message-ID: <20190620115732.8E7F51B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/32a99f74/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 20 11:57:34 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 11:57:34 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.5a302f39eae5a2d1aeb423f026fa8fad@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by ocean90):

 In [changeset:"8969" 8969]:
 {{{
 #!CommitTicketReference repository="" revision="8969"
 Translate: Add initial plugin for discussion implementation.

 See #4518.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 12:06:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:06:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------
Changes (by ottok):

 * Attachment "compatible-with-up-to-latest.png" removed.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4309>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 12:10:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:10:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4520: Rework Browse by WordCamp
 list in sidebar of event archives
Message-ID: <054.896c590f55433f766a8054b5bed42301@wordpress.org>

#4520: Rework Browse by WordCamp list in sidebar of event archives
--------------------------+--------------------
 Reporter:  BrashRebel    |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+--------------------
 Check out [an event archive page](https://wordpress.tv/event/wordcamp-
 europe-2018/) and scroll down. On the right sidebar there is a "Browse by
 WordCamp" heading followed by a list of all the terms in the events
 taxonomy. It's a really long list. There are 699 terms in that taxonomy
 right now and the list is always growing. We should find a new way for
 those events to be discovered.

 I propose we consider one of the following options:

 A. Remove the section entirely. It is not extremely important that we
 include other events in the sidebar of an event archive. They can be
 discovered other ways.
 B. Convert the list to a dropdown. It would still be a bit tedious to
 navigate but would be an improvement and would not take up so much space
 on the page. Plus it would be a pretty simple fix.
 C. Implement a search based dropdown. We'd probably need to load a jQuery
 library or something. I don't believe anything like it already exists on
 the site's frontend.
 D. Create a terms archive page for events, as described in [this
 ticket](https://meta.trac.wordpress.org/ticket/1434) and link to that page
 instead of listing the terms there.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4520>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 12:19:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:19:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.7213b41b8e94e3d1fd4e9819c4598508@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by dd32):

 How often is it likely that a plugin that was compatible with PHP 7.0 and
 7.2, but incompatible with PHP 7.1? Does displaying each version of PHP
 that's compatible useful to the average user or developer?

 Wouldn't we be better off sticking with minimum and potentially maximum
 supported versions of PHP?

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

From noreply at wordpress.org  Thu Jun 20 12:19:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:19:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4521: Broken link in the plugin
 handbook sidebar
Message-ID: <055.aa69d2ba3a9fdd7018283d0d35897d2b@wordpress.org>

#4521: Broken link in the plugin handbook sidebar
-------------------------+--------------------
 Reporter:  hofmannsven  |      Owner:  (none)
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Handbooks    |   Keywords:
-------------------------+--------------------
 In the plugin handbook, the menu item (Chapter: Securing Output) in the
 sidebar menu does not seem to exist:
 https://developer.wordpress.org/?post_type=plugin-handbook&p=11556

 Browse: Home / Plugin Handbook / Plugin Security / Securing Output

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4521>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 12:21:46 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:21:46 -0000
Subject: [wp-meta] [Making WordPress.org] #1770: Revamp handling for
 global admins in GlotPress
In-Reply-To: <051.e3ff58417abda70fcaf9e30f541f7a39@wordpress.org>
References: <051.e3ff58417abda70fcaf9e30f541f7a39@wordpress.org>
Message-ID: <066.5b7d264478f4c3c6ee3f82899ccb0931@wordpress.org>

#1770: Revamp handling for global admins in GlotPress
--------------------------------------+-------------------------
 Reporter:  ocean90                   |       Owner:  (none)
     Type:  task                      |      Status:  closed
 Priority:  high                      |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  maybelater
 Keywords:                            |
--------------------------------------+-------------------------
Changes (by ocean90):

 * status:  new => closed
 * resolution:   => maybelater


Comment:

 Closing as maybelater for now.

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

From noreply at wordpress.org  Thu Jun 20 12:22:21 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:22:21 -0000
Subject: [wp-meta] [Making WordPress.org] #4430: Provide suggestions for
 translations
In-Reply-To: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
References: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
Message-ID: <066.d30c7be77a31bad490d95af3e9235b24@wordpress.org>

#4430: Provide suggestions for translations
--------------------------------------+-----------------------
 Reporter:  ocean90                   |       Owner:  ocean90
     Type:  task                      |      Status:  assigned
 Priority:  high                      |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+-----------------------

Comment (by ocean90):

 Yep, let's close this for now and review machine translation again in the
 future.

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

From noreply at wordpress.org  Thu Jun 20 12:24:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:24:11 -0000
Subject: [wp-meta] [Making WordPress.org] #3713: GlotPress negative
 counts
In-Reply-To: <049.c9d2cd5c642a7a4e58b7248c5362eb40@wordpress.org>
References: <049.c9d2cd5c642a7a4e58b7248c5362eb40@wordpress.org>
Message-ID: <064.0b2c315365fe10cd82caa86b80bc61bb@wordpress.org>

#3713: GlotPress negative counts
--------------------------------------+-------------------------
 Reporter:  GaryJ                     |       Owner:  (none)
     Type:  defect                    |      Status:  closed
 Priority:  lowest                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  worksforme
 Keywords:                            |
--------------------------------------+-------------------------
Changes (by ocean90):

 * status:  reviewing => closed
 * resolution:   => worksforme


Comment:

 Based on any new reports I'm going to close this as ''worksforme''.

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

From noreply at wordpress.org  Thu Jun 20 12:30:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:30:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.bf3a94b5e0b2fb617426774af70dd727@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by BrashRebel):

 Could we make it consistent with the way the WordPress version
 compatibility is presented now?

 "PHP Version: 5.6 or higher"

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

From noreply at wordpress.org  Thu Jun 20 12:34:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:34:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
In-Reply-To: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
References: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
Message-ID: <070.e109bb03de3e699ecaf16ffec32967d6@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+---------------------
 Reporter:  Travel_girl       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by tellyworth):

 Big thanks for the specific solutions @Travel_girl !

 Regarding (1), the current implementation uses definition lists as its
 semantic markup. Would you suggest removing the dl/dd/dt markup entirely
 and replacing it with h3/p tags? If so, is there something we should do to
 indicate the relationship between the `h3` question and the `p` answer, or
 does the sequence imply enough semantic context?

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

From noreply at wordpress.org  Thu Jun 20 12:37:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:37:59 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make
 "make glossary" less obtrusive
In-Reply-To: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
References: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
Message-ID: <071.e7e83d0519100abe9cd09bda5926d5af@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+---------------------

Comment (by tellyworth):

 @talldanwp suggested https://github.com/tristen/hoverintent as a possible
 candidate for implementing this.

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

From noreply at wordpress.org  Thu Jun 20 12:40:22 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:40:22 -0000
Subject: [wp-meta] [Making WordPress.org] #4402: Slides URL field in
 submit video form is cutting the URL
In-Reply-To: <051.36f35b839da14b36dd37b555779eb4ce@wordpress.org>
References: <051.36f35b839da14b36dd37b555779eb4ce@wordpress.org>
Message-ID: <066.74495a8aca95c2e3c92c84e18e5b173d@wordpress.org>

#4402: Slides URL field in submit video form is cutting the URL
--------------------------+---------------------
 Reporter:  casiepa       |       Owner:  (none)
     Type:  defect        |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:                |
--------------------------+---------------------

Comment (by BrashRebel):

 @casiepa just wanted to get clarification on this ticket and go over
 options. When you say "cutting", are you experiencing the URL value
 actually being changed/truncated when saved or is it simply not visibly
 showing the entire URL when you insert it? And what would you suggest as a
 solution? I cannot envision a simple way to solve the problem without
 changing the layout of the form.

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

From noreply at wordpress.org  Thu Jun 20 12:54:04 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 12:54:04 +0000 (UTC)
Subject: [wp-meta] [8970] sites/trunk/common/includes/slack: Slack: Add the
 core-sitehealth channel, and add Clorith and miss_jwo as announcers.
Message-ID: <20190620125404.03D451B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/48ecafc6/attachment.html>

From noreply at wordpress.org  Thu Jun 20 12:59:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 12:59:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3240: Add speaker's social
 media handle to WordPress.tv video link
In-Reply-To: <053.afe05f5aef7fa1b09fa5867a73fc3c64@wordpress.org>
References: <053.afe05f5aef7fa1b09fa5867a73fc3c64@wordpress.org>
Message-ID: <068.85413e9934eb283f557c28ccaeb75142@wordpress.org>

#3240: Add speaker's social media handle to WordPress.tv video link
--------------------------+---------------------
 Reporter:  carmemias     |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:                |
--------------------------+---------------------

Comment (by BrashRebel):

 This is technically possible and requires three things:

 1. Use [this Publicize
 filter](https://developer.jetpack.com/hooks/wpas_default_message/) to
 customize the default share message so that it includes the speaker's
 Twitter handle.
 2. Add a new custom field to posts for saving the Twitter handle.
 3. Add a field to the video submission form to include it during initial
 submission.

 That's the most straightforward solution I can think of. There are two
 problems with it:

 1. The way I described it would not really support multiple
 speakers...although if it were just a text field we could provide
 instructions to separate handles with a space and it might work fine.
 2. We would only be collecting values going forward. Our 10k+ posts on the
 site now would not benefit.

 Anyway, it is possible and not particularly difficult. And it could be
 pretty handy too. Thanks for sharing the idea @carmemias !

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

From noreply at wordpress.org  Thu Jun 20 13:14:19 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 13:14:19 +0000 (UTC)
Subject: [wp-meta] [8971]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-customizations/templates/translation-row-editor.php:
 Translate: Add custom action to extend meta section.
Message-ID: <20190620131419.56B381B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/2bef5547/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 20 13:14:21 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 13:14:21 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.8ced177e0b74f8c705c34ceddcb381f0@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by ocean90):

 In [changeset:"8971" 8971]:
 {{{
 #!CommitTicketReference repository="" revision="8971"
 Translate: Add custom action to extend meta section.

 See #4518.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 13:15:18 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 13:15:18 -0000
Subject: [wp-meta] [Making WordPress.org] #4522: Glossary Landingpage
Message-ID: <053.8e02c9c5d6be17512d17e376987fe6f3@wordpress.org>

#4522: Glossary Landingpage
-------------------------+--------------------
 Reporter:  itsmarvin    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  low          |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 Hi there,
 I am attending my first [https://2019.europe.wordcamp.org/ WordCamp] and
 Contributor Day today and came up with the idea to use
 https://wordpress.org/glossary for some sort of landing page for all
 WordPress glossaries. What do you think of that?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4522>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 13:15:50 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 13:15:50 +0000 (UTC)
Subject: [wp-meta] [8972]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-discussions:
 Translate, Discussion: Retrieve REST API URL by locale.
Message-ID: <20190620131550.AB7991B002C6@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/b09d1a35/attachment.html>

From noreply at wordpress.org  Thu Jun 20 13:15:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 13:15:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.0d405265be5a00ef14a5cfb6938c6da8@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by ocean90):

 In [changeset:"8972" 8972]:
 {{{
 #!CommitTicketReference repository="" revision="8972"
 Translate, Discussion: Retrieve REST API URL by locale.

 See #4518.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 13:16:39 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 13:16:39 +0000 (UTC)
Subject: [wp-meta] [8973] sites/trunk/wordpress.org/public_html/style/trac:
 Trac: Improve accessibility of keywords and focuses on Trac ticket pages.
Message-ID: <20190620131639.87AF71B002C6@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/a4566b7a/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 20 13:16:41 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 13:16:41 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.1d706a8ec34c15dae61a6cf4c31f062e@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+-----------------------------
 Reporter:  afercia                    |       Owner:  SergeyBiryukov
     Type:  defect                     |      Status:  closed
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:  fixed
 Keywords:  has-screenshots has-patch  |
---------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8973" 8973]:
 {{{
 #!CommitTicketReference repository="" revision="8973"
 Trac: Improve accessibility of keywords and focuses on Trac ticket pages.

 Props afercia.
 Fixes #4495.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 13:18:37 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 13:18:37 +0000 (UTC)
Subject: [wp-meta] [8974]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump scripts
 version after [8973].
Message-ID: <20190620131838.013231B002C6@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/56687d17/attachment.html>

From noreply at wordpress.org  Thu Jun 20 13:18:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 13:18:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4495: Improve accessibility
 of the Trac ticket Keywords and Focuses
In-Reply-To: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
References: <051.17792ce3dd65a74cacad5d96ae8d2aaa@wordpress.org>
Message-ID: <066.cdbf87f87620fbeae7dcd43cc5bd0a9e@wordpress.org>

#4495: Improve accessibility of the Trac ticket Keywords and Focuses
---------------------------------------+-----------------------------
 Reporter:  afercia                    |       Owner:  SergeyBiryukov
     Type:  defect                     |      Status:  closed
 Priority:  normal                     |   Milestone:
Component:  Trac                       |  Resolution:  fixed
 Keywords:  has-screenshots has-patch  |
---------------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [changeset:"8974" 8974]:
 {{{
 #!CommitTicketReference repository="" revision="8974"
 Trac: Bump scripts version after [8973]. See #4495.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 13:56:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 13:56:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
In-Reply-To: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
References: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
Message-ID: <070.1b74ab8b7159fed8625be81d0ee49f4d@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+---------------------
 Reporter:  Travel_girl       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by tferry):

 @tellyworth I believe we'd need to include matching `id` and `aria-
 labelledby` attributes (respectively) in the case of changing to `<h3>`
 and `<p>` to maintain this semantic context.

 However, as far as I know the dl/dt/dd structure should be okay? The w3
 spec gives a question & answer structure as a use-case example for the dt
 element: https://www.w3.org/TR/html5/grouping-content.html#the-dt-element

 I'd suggest we simply add a wrapping `<h3>` inside the "question" <dt>
 element.

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

From noreply at wordpress.org  Thu Jun 20 14:08:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 14:08:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4522: Glossary Landingpage
In-Reply-To: <053.8e02c9c5d6be17512d17e376987fe6f3@wordpress.org>
References: <053.8e02c9c5d6be17512d17e376987fe6f3@wordpress.org>
Message-ID: <068.534dcd34dc20ff954563f84eeadc07bb@wordpress.org>

#4522: Glossary Landingpage
-------------------------------+---------------------
 Reporter:  itsmarvin          |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  low                |   Milestone:
Component:  General            |  Resolution:
 Keywords:  reporter-feedback  |
-------------------------------+---------------------
Changes (by tellyworth):

 * keywords:   => reporter-feedback


Comment:

 It's a good suggestion, thanks!

 We can sort of do this already. Not at the top-level
 `wordpress.org/glossary` url, but the Make sites that have set up a
 Handbook Glossary page do already have what I think you're asking for:

 https://make.wordpress.org/polyglots/handbook/glossary/

 It should be possible to set up one on the main Make site for the global
 glossary, but it looks like there's a theme layout issue on that site that
 needs to be fixed first.

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

From noreply at wordpress.org  Thu Jun 20 14:11:22 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 14:11:22 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
In-Reply-To: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
References: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
Message-ID: <070.b4a1f80597e4b02d0aa6bc554bd67cca@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+---------------------
 Reporter:  Travel_girl       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by obenland):

 @tellyworth I happened to talk to @Travel_girl in a WCEU hallway and she
 said we should keep the dl

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

From noreply at wordpress.org  Thu Jun 20 14:38:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 14:38:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.e4e960fc8323c8212e8944621ef39a72@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by JoshuaWold):

 Thank you @ottok for that wonderful mockup!

 I think the answer here comes down to what's actually needed for users. If
 there's situations where, as @dd32 mentioned, I could be compatible with
 7.0 and 7.2, but not 7.1, then we should go the way of the mockup @ottok
 suggested.

 Otherwise I agree with @BrashRebel that a simple statement works.

 @JeffPaul do you or Derek know the answer to this? :)

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

From noreply at wordpress.org  Thu Jun 20 14:56:25 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 14:56:25 +0000 (UTC)
Subject: [wp-meta] [8975]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/jobs:
 Plugin Directory: Add a job to import data from Tide into the plugin
 directory.
Message-ID: <20190620145625.0BD261B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/be96f465/attachment.html>

From noreply at wordpress.org  Thu Jun 20 14:56:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 14:56:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.905e18682906d35961b8f0bb2683f807@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by dd32):

 In [changeset:"8975" 8975]:
 {{{
 #!CommitTicketReference repository="" revision="8975"
 Plugin Directory: Add a job to import data from Tide into the plugin
 directory.

 This job isn't yet in use, and a follow up commit will enable it.

 See #4309.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 15:13:56 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 15:13:56 +0000 (UTC)
Subject: [wp-meta] [8976]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/cli/class-import.php:
 Plugin Directory: Import Tide data for plugins after commits.
Message-ID: <20190620151356.CEC041B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/63c74165/attachment.html>

From noreply at wordpress.org  Thu Jun 20 15:13:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 15:13:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.fa240c7233f9eb332eb02e1fc1e6cf74@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by dd32):

 In [changeset:"8976" 8976]:
 {{{
 #!CommitTicketReference repository="" revision="8976"
 Plugin Directory: Import Tide data for plugins after commits.

 See #4309.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 15:22:14 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 15:22:14 +0000 (UTC)
Subject: [wp-meta] [8977]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/jobs/class-tide-sync.php:
 Plugin Directory: Tide Sync: Handle the case of an empty tide summary
 report.
Message-ID: <20190620152214.2DB201B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/65a12591/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 20 15:22:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 15:22:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.600cef4a43a4a1ecce4e309459bfdc05@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by dd32):

 In [changeset:"8977" 8977]:
 {{{
 #!CommitTicketReference repository="" revision="8977"
 Plugin Directory: Tide Sync: Handle the case of an empty tide summary
 report.

 See #4309.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 15:35:14 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 15:35:14 +0000 (UTC)
Subject: [wp-meta] [8978]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/jobs/class-tide-sync.php:
 Plugin Directory: Tide Sync: Only support plugins who use versioned
 versions, ie.
Message-ID: <20190620153514.8C1921B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/dadfcf79/attachment.html>

From noreply at wordpress.org  Thu Jun 20 15:35:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 15:35:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.eabfac8a8b1859406451f8f7a0c48dc6@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by dd32):

 In [changeset:"8978" 8978]:
 {{{
 #!CommitTicketReference repository="" revision="8978"
 Plugin Directory: Tide Sync: Only support plugins who use versioned
 versions, ie. no `stable tag: trunk`.

 See #4309.
 }}}

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

From noreply at wordpress.org  Thu Jun 20 15:45:09 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 15:45:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.363de569d45753feb71c276f0d4612aa@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by ottok):

 Thanks @dd32 for working on this! Attaching mockups of the very simple UI
 version.

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

From noreply at wordpress.org  Thu Jun 20 15:45:30 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 15:45:30 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.80bd84e4f619dc72da51e52e0b7544fa@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------
Changes (by ottok):

 * Attachment "very-simple-not-compatible.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4309>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 15:45:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 15:45:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.9e7b70548f8002a4871d85c557ab6dba@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------
Changes (by ottok):

 * Attachment "very-simple-compatibile.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4309>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 16:56:31 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 16:56:31 -0000
Subject: [wp-meta] [Making WordPress.org] #4390: Hide duplicates on
 WordCamp attendees page
In-Reply-To: <055.54e74b07de4bd465c7213d9ade3f0e79@wordpress.org>
References: <055.54e74b07de4bd465c7213d9ade3f0e79@wordpress.org>
Message-ID: <070.2505405a9c267c4cce2b2bc2b1065213@wordpress.org>

#4390: Hide duplicates on WordCamp attendees page
-------------------------------------+---------------------
 Reporter:  hlashbrooke              |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by coreymckrill):

 @hlashbrooke the `camptix_attendees` shortcode takes a comma-separated
 list of ticket IDs as a parameter. Could this be fixed by only including
 the ID for the general admission ticket, and not the separate Contributor
 Day ticket? It looks like that might be what was done for 2019.europe.

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

From noreply at wordpress.org  Thu Jun 20 17:10:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 17:10:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.47b578c36808bcadedc0d8d484026d2a@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by JoshuaWold):

 These looks great. Thanks!

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

From noreply at wordpress.org  Thu Jun 20 17:37:37 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 17:37:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3713: GlotPress negative
 counts
In-Reply-To: <049.c9d2cd5c642a7a4e58b7248c5362eb40@wordpress.org>
References: <049.c9d2cd5c642a7a4e58b7248c5362eb40@wordpress.org>
Message-ID: <064.1286e6fe9453088695650e331681f46e@wordpress.org>

#3713: GlotPress negative counts
--------------------------------------+-------------------------
 Reporter:  GaryJ                     |       Owner:  (none)
     Type:  defect                    |      Status:  closed
 Priority:  lowest                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  worksforme
 Keywords:                            |
--------------------------------------+-------------------------

Comment (by garrett-eclipse):

 Sound good @ocean90 I just quickly ran through all the projects linked
 here that had the issue originally and can confirm there's none with a
 negative.

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

From noreply at wordpress.org  Thu Jun 20 18:23:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 18:23:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4500: Add responsive embed
 support to WordCamp sites
In-Reply-To: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
References: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
Message-ID: <068.8c95ec12d5df9f54c5a5331511c2f6af@wordpress.org>

#4500: Add responsive embed support to WordCamp sites
-------------------------------------+-----------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+-----------------------
Changes (by coreymckrill):

 * keywords:  has-patch => has-patch needs-testing
 * status:  new => assigned
 * type:  defect => enhancement


Comment:

 It seems unlikely, but we should test and make sure enabling this doesn't
 cause any side effects for other camps that are already using the theme
 and have embeds. If we can find any...

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

From noreply at wordpress.org  Thu Jun 20 18:29:42 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 18:29:42 -0000
Subject: [wp-meta] [Making WordPress.org] #4494: Posts published on a
 "Coming Soon" mode WordCamp site appear on profile stream
In-Reply-To: <047.6bd599c1def856486af039d8d652b67a@wordpress.org>
References: <047.6bd599c1def856486af039d8d652b67a@wordpress.org>
Message-ID: <062.6770ec3a050f529b459e889b6915c2c0@wordpress.org>

#4494: Posts published on a "Coming Soon" mode WordCamp site appear on profile
stream
-------------------------------------+-----------------------
 Reporter:  Nao                      |       Owner:  (none)
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion              |
-------------------------------------+-----------------------
Changes (by coreymckrill):

 * keywords:  needs-patch => 2nd-opinion
 * status:  new => assigned


Comment:

 I think preventing published posts from appearing in the profile stream
 while in Coming Soon mode could cause other issues and complications.
 Like, do we queue all published posts and then add them to the stream once
 Coming Soon is turned off? What if it is then turned back on?

 We could also decide to turn off that particular activity item altogether,
 and not have any published posts from WordCamp sites appear in the profile
 stream.

 As discussed in today's bug scrub, it seems like the best place to start
 is with @Nao 's suggestion to add a note about this to the handbook.

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

From noreply at wordpress.org  Thu Jun 20 18:34:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 18:34:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4426: WordCamp Planning
 Checklist: Add an "In Progress" status for tasks
In-Reply-To: <056.79ab979b361af036fac1d3715ab70847@wordpress.org>
References: <056.79ab979b361af036fac1d3715ab70847@wordpress.org>
Message-ID: <071.3194b3a3d1da13f20f755ca882f5d6d4@wordpress.org>

#4426: WordCamp Planning Checklist: Add an "In Progress" status for tasks
----------------------------------------+-----------------------
 Reporter:  coreymckrill                |       Owner:  (none)
     Type:  enhancement                 |      Status:  assigned
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------
Changes (by coreymckrill):

 * status:  new => assigned


Comment:

 I agree, a new default status of `Incomplete` would make sense. And
 perhaps change the label for the pending status to `In Progress` so that
 it's a bit more clear what it should be used for.

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

From noreply at wordpress.org  Thu Jun 20 18:35:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 18:35:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4523: HelpHub Plugin on pt_BR
 Rosetta Site
Message-ID: <054.16ce091555f0db01ae431a33fdfa27e6@wordpress.org>

#4523: HelpHub Plugin on pt_BR Rosetta Site
-------------------------+--------------------
 Reporter:  felipeelia   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  HelpHub      |   Keywords:
-------------------------+--------------------
 Hi! As per the procedure indicated in
 [https://make.wordpress.org/meta/2019/06/20/helphub-handbooks-
 localisation/ this post], the Brazilian Team would like to be part of this
 early stage of HelpHub & Handbooks Localisation. Can we please have the
 HelpHub plugin activated on our website? Thanks!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4523>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 20 18:43:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 18:43:50 -0000
Subject: [wp-meta] [Making WordPress.org] #4392: Add a way to declare a
 custom color palette in Gutenberg
In-Reply-To: <053.07e1a382acc09d2ed5973c74cb618945@wordpress.org>
References: <053.07e1a382acc09d2ed5973c74cb618945@wordpress.org>
Message-ID: <068.c79be3f689cf9d1cfd1127cc11874944@wordpress.org>

#4392: Add a way to declare a custom color palette in Gutenberg
--------------------------------------+-----------------------
 Reporter:  melchoyce                 |       Owner:  (none)
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:
Component:  WordCamp Site & Plugins   |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+-----------------------
Changes (by coreymckrill):

 * keywords:   => needs-patch needs-design
 * status:  new => assigned


Comment:

 In today's bug scrub, we discussed adding a WordCamp settings sidebar to
 the block editor UI where a custom color palette (and perhaps other things
 like in #4389) could be defined by the organizers. Similar to @ryelle's
 comment
 [https://wordpress.slack.com/archives/C08M59V3P/p1555611110080100?thread_ts=1555610462.064200&cid=C08M59V3P
 here].

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

From noreply at wordpress.org  Thu Jun 20 19:11:56 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 19:11:56 +0000 (UTC)
Subject: [wp-meta] [8979]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: Day Of Event
 Template: Revert to `On Now` and `Up Next` strings.
Message-ID: <20190620191156.26FC41B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/da5ab9c7/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 20 19:46:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Jun 2019 19:46:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3240: Add speaker's social
 media handle to WordPress.tv video link
In-Reply-To: <053.afe05f5aef7fa1b09fa5867a73fc3c64@wordpress.org>
References: <053.afe05f5aef7fa1b09fa5867a73fc3c64@wordpress.org>
Message-ID: <068.d97fddf0118bbd542f05b924ebbdb50b@wordpress.org>

#3240: Add speaker's social media handle to WordPress.tv video link
--------------------------+---------------------
 Reporter:  carmemias     |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:                |
--------------------------+---------------------

Comment (by carmemias):

 Thanks for looking into it @BrashRebel !

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

From noreply at wordpress.org  Thu Jun 20 20:24:09 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 20:24:09 +0000 (UTC)
Subject: [wp-meta] [8980]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: WordCamp
 Helpers: Rename to load earlier.
Message-ID: <20190620202409.0B4991B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/7a177d46/attachment-0001.html>

From noreply at wordpress.org  Thu Jun 20 20:24:14 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 20:24:14 +0000 (UTC)
Subject: [wp-meta] [8981]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: Offline
 Template: Initial commit.
Message-ID: <20190620202414.D16BF1B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/5660b68c/attachment.html>

From noreply at wordpress.org  Thu Jun 20 22:36:28 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Jun 2019 22:36:28 +0000 (UTC)
Subject: [wp-meta] [8982]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: Offline
 Template: Don't try to cache non-existant custom CSS URL.
Message-ID: <20190620223628.B34451B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190620/cfa5c6c8/attachment-0001.html>

From noreply at wordpress.org  Fri Jun 21 03:33:29 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 03:33:29 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.70c1a677b3952a3b7421b7e14a3c3f4a@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by afragen):

 Does this mockup mean the current `Requires PHP:` header is being replaced
 ?

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

From noreply at wordpress.org  Fri Jun 21 05:25:44 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Jun 2019 05:25:44 +0000 (UTC)
Subject: [wp-meta] [8983]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/theme-templates/templates/day-of-event/day-of-event.php:
 Day of Event Template: Add post content at bottom of template.
Message-ID: <20190621052544.A64131B0059A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190621/07f79c55/attachment.html>

From noreply at wordpress.org  Fri Jun 21 06:35:35 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Jun 2019 06:35:35 +0000 (UTC)
Subject: [wp-meta] [8984]
 sites/trunk/wordcamp.org/public_html/wp-content/themes/campsite-2017/functions.php:
 CampSite 2017: Add support for responsive embeds.
Message-ID: <20190621063535.94D381B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190621/3e72e86e/attachment.html>

From noreply at wordpress.org  Fri Jun 21 06:35:37 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 06:35:37 -0000
Subject: [wp-meta] [Making WordPress.org] #4500: Add responsive embed
 support to WordCamp sites
In-Reply-To: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
References: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
Message-ID: <068.e50e75ce120d6e3e5a5249b6387d313a@wordpress.org>

#4500: Add responsive embed support to WordCamp sites
-------------------------------------+----------------------
 Reporter:  melchoyce                |       Owner:  iandunn
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  fixed
 Keywords:  has-patch needs-testing  |
-------------------------------------+----------------------
Changes (by iandunn):

 * owner:  (none) => iandunn
 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8984" 8984]:
 {{{
 #!CommitTicketReference repository="" revision="8984"
 CampSite 2017: Add support for responsive embeds.

 Props ryelle.
 Fixes #4500.
 See
 https://wordpress.slack.com/archives/C08M59V3P/p1561098727119400?thread_ts=1561093493.110200&cid=C08M59V3P.
 }}}

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

From noreply at wordpress.org  Fri Jun 21 06:37:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 06:37:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4500: Add responsive embed
 support to WordCamp sites
In-Reply-To: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
References: <053.0e25ac701aaf8ae15094ff56fec6331a@wordpress.org>
Message-ID: <068.1e21c40f9dce91b8ebde642c920b49f9@wordpress.org>

#4500: Add responsive embed support to WordCamp sites
-------------------------------------+-----------------------
 Reporter:  melchoyce                |       Owner:  iandunn
     Type:  enhancement              |      Status:  reopened
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+-----------------------
Changes (by iandunn):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I committed [attachment:"4500.diff"] as last-minute support for WCEU, but
 meant to `See #4500` rather than `Fixes #4500` in the message.

 The patch works fine in my very limited testing, but re-opening because we
 still need to consider any back-compat implications, as mentioned above.

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

From noreply at wordpress.org  Fri Jun 21 07:26:03 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Jun 2019 07:26:03 +0000 (UTC)
Subject: [wp-meta] [8985]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main:
 Privacy: tentatively enable the export request page.
Message-ID: <20190621072603.A48841B0045D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190621/9c842bee/attachment-0001.html>

From noreply at wordpress.org  Fri Jun 21 07:59:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 07:59:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.b2520bcdabd21fb4faef41e549fcf9cc@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by dd32):

 Replying to [comment:13 afragen]:
 > Does this mockup mean the current `Requires PHP:` header is being
 replaced ?

 No, anything we do is in addition, or as q fallback for a plugin not
 specifying it.

 I don't think we'll be adding an upper boind of supported php either for
 the time being, due to difficulties in parsing that with confidence.

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

From noreply at wordpress.org  Fri Jun 21 08:05:12 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 08:05:12 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.a4dc9cee5d09adf4b1dc76d681e11a66@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by afragen):

 Should it say `Compatible PHP` as there will also be a `Requires PHP`? As
 ''requires'' is a minimum Tide data would be a bonus.

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

From noreply at wordpress.org  Fri Jun 21 08:18:56 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 08:18:56 -0000
Subject: [wp-meta] [Making WordPress.org] #4523: HelpHub Plugin on pt_BR
 Rosetta Site
In-Reply-To: <054.16ce091555f0db01ae431a33fdfa27e6@wordpress.org>
References: <054.16ce091555f0db01ae431a33fdfa27e6@wordpress.org>
Message-ID: <069.a54acc4f29b42a41c6dae648eb88dc6b@wordpress.org>

#4523: HelpHub Plugin on pt_BR Rosetta Site
------------------------+-----------------------
 Reporter:  felipeelia  |       Owner:  sergey
     Type:  task        |      Status:  assigned
 Priority:  normal      |   Milestone:
Component:  HelpHub     |  Resolution:
 Keywords:              |
------------------------+-----------------------
Changes (by netweb):

 * owner:  (none) => sergey
 * status:  new => assigned
 * type:  enhancement => task


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

From noreply at wordpress.org  Fri Jun 21 08:53:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Jun 2019 08:53:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4392: Add a way to declare a
 custom color palette in Gutenberg
In-Reply-To: <053.07e1a382acc09d2ed5973c74cb618945@wordpress.org>
References: <053.07e1a382acc09d2ed5973c74cb618945@wordpress.org>
Message-ID: <068.d66b17cf324ae5215729853d6958ec40@wordpress.org>

#4392: Add a way to declare a custom color palette in Gutenberg
--------------------------------------+-----------------------
 Reporter:  melchoyce                 |       Owner:  (none)
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:
Component:  WordCamp Site & Plugins   |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+-----------------------

Comment (by ryelle):

 I have a prototype for this, after WCEU I can clean it up. I tried the
 gutenberg sidebar way first, but unfortunately the way GB sets up the
 colors means that we can't seamlessly update without a page reload
 (because GB reads the colors from a variable set on the page) - you can
 see this almost working [https://github.com/ryelle/wc-custom-
 styles/tree/add/custom-colors on the prototype] (not a stable prototype,
 and if you download it you'll need to `npm install` and `npm run build` to
 test it), but the colors reset when you update/publish a post.

 The other direction I started going was the options page, so you set up
 your colors in a new page, then they're set as the editor colors when the
 editor initializes. [https://github.com/ryelle/wc-custom-styles/tree/try
 /custom-colors-screen There's an even less finished prototype here.]

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

From noreply at wordpress.org  Sat Jun 22 06:47:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 06:47:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4383: Plugin 'Reviews' tab
 should provide more information to logged-out users
In-Reply-To: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
References: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
Message-ID: <070.aaf27d50ef32e2713b53f7ee1e5c5aa5@wordpress.org>

#4383: Plugin 'Reviews' tab should provide more information to logged-out users
--------------------------------+-------------------------
 Reporter:  DannyCooper         |       Owner:  (none)
     Type:  defect              |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Plugin Directory    |  Resolution:  worksforme
 Keywords:  dev-feedback close  |
--------------------------------+-------------------------
Changes (by pratikgandhi):

 * keywords:   => dev-feedback close
 * status:  new => closed
 * resolution:   => worksforme


Comment:

 Hello @DannyCooper

 Thank you for the ticket.

 I just checked the plugin's review tab and I think it's now updated. I can
 see the reviews without login and with login in this tab easily. Hope it
 is visible to you as well.

 Thank you

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

From noreply at wordpress.org  Sat Jun 22 06:49:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 06:49:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4383: Plugin 'Reviews' tab
 should provide more information to logged-out users
In-Reply-To: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
References: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
Message-ID: <070.3ca45cc4e19b5ac71431af9facd26533@wordpress.org>

#4383: Plugin 'Reviews' tab should provide more information to logged-out users
--------------------------------+-----------------------
 Reporter:  DannyCooper         |       Owner:  (none)
     Type:  defect              |      Status:  reopened
 Priority:  normal              |   Milestone:
Component:  Plugin Directory    |  Resolution:
 Keywords:  dev-feedback close  |
--------------------------------+-----------------------
Changes (by DannyCooper):

 * status:  closed => reopened
 * resolution:  worksforme =>


Comment:

 Hi @pratikgandhi,

 This isnt fixed, please check a plugin that has no reviews when you are
 not logged in:

 https://wordpress.org/plugins/design-experiments/#reviews

 The tab is completely blank.

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

From noreply at wordpress.org  Sat Jun 22 06:57:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 06:57:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4383: Plugin 'Reviews' tab
 should provide more information to logged-out users
In-Reply-To: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
References: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
Message-ID: <070.ad34f16690593bf285dee93cb2466979@wordpress.org>

#4383: Plugin 'Reviews' tab should provide more information to logged-out users
------------------------------+-----------------------
 Reporter:  DannyCooper       |       Owner:  (none)
     Type:  defect            |      Status:  reopened
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+-----------------------
Changes (by pratikgandhi):

 * keywords:  dev-feedback close => needs-patch
 * priority:  normal => high


Comment:

 Hi @DannyCooper

 yes, There should be some message like 'This plugin has not been rated
 yet, **Add my review**'.

 Thanks

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

From noreply at wordpress.org  Sat Jun 22 07:22:16 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 22 Jun 2019 07:22:16 +0000 (UTC)
Subject: [wp-meta] [8986]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main:
 Privacy: link export page from privacy menu.
Message-ID: <20190622072216.93B3F1B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190622/2ec5069d/attachment.html>

From noreply at wordpress.org  Sat Jun 22 07:30:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 07:30:59 -0000
Subject: [wp-meta] [Making WordPress.org] #4345: Improve the display of
 block metadata in the plugin directory
In-Reply-To: <054.3d575332a1453e436aeb452eb1f32805@wordpress.org>
References: <054.3d575332a1453e436aeb452eb1f32805@wordpress.org>
Message-ID: <069.84f266ed400b864259498ec9bae880a8@wordpress.org>

#4345: Improve the display of block metadata in the plugin directory
------------------------------+---------------------
 Reporter:  tellyworth        |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-design      |
------------------------------+---------------------
Changes (by pratikgandhi):

 * Attachment "ticket-4345.png" added.

 Design for the Blocks section

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4345>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun 22 07:39:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 07:39:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4345: Improve the display of
 block metadata in the plugin directory
In-Reply-To: <054.3d575332a1453e436aeb452eb1f32805@wordpress.org>
References: <054.3d575332a1453e436aeb452eb1f32805@wordpress.org>
Message-ID: <069.b2b2e163e8a83e2d97e11a792b30b438@wordpress.org>

#4345: Improve the display of block metadata in the plugin directory
-------------------------------------------------+-------------------------
 Reporter:  tellyworth                           |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Plugin Directory                     |  Resolution:
 Keywords:  reporter-feedback 2nd-opinion has-   |
  screenshots                                    |
-------------------------------------------------+-------------------------
Changes (by pratikgandhi):

 * keywords:  needs-design => reporter-feedback 2nd-opinion has-screenshots


Comment:

 Hello @tellyworth

 How about this?
 [[Image(https://meta.trac.wordpress.org/raw-
 attachment/ticket/4345/ticket-4345.png)]]

 It can be done using the below code:
 {{{
 <ul>
     <li>
         <h6>atomic-blocks/ab-pricing</h6>
         <p>AB Pricing</p>
     </li>
     <li>
         <h6>atomic-blocks/newsletter</h6>
         <p>Email newsletter</p>
     </li>
     <li>
         <h6>atomic-blocks/ab-column</h6>
         <p>AB Advanced Column</p>
     </li>

     <li>
         <h6>atomic-blocks/ab-spacer</h6>
         <p>AB Spacer</p>
     </li>
     <li>
         <h6>atomic-blocks/ab-container</h6>
         <p>AB Container</p>
     </li>
     <li>
         <h6>atomic-blocks/ab-sharing</h6>
         <p>AB Sharing</p>
     </li>
 </ul>
 }}}

 Thanks

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

From noreply at wordpress.org  Sat Jun 22 09:02:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 09:02:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4430: Provide suggestions for
 translations
In-Reply-To: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
References: <051.93aecbbbee02f849a688e522974cb804@wordpress.org>
Message-ID: <066.4561f167fb3ba1afdc8af8d447acec40@wordpress.org>

#4430: Provide suggestions for translations
--------------------------------------+----------------------
 Reporter:  ocean90                   |       Owner:  ocean90
     Type:  task                      |      Status:  closed
 Priority:  high                      |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+----------------------
Changes (by ocean90):

 * status:  assigned => closed
 * resolution:   => fixed


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

From noreply at wordpress.org  Sat Jun 22 10:16:30 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 10:16:30 -0000
Subject: [wp-meta] [Making WordPress.org] #4383: Plugin 'Reviews' tab
 should provide more information to logged-out users
In-Reply-To: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
References: <055.ee390f1db13ce60f6c48f73a392b5115@wordpress.org>
Message-ID: <070.9413f8b292bbcead9755c89ae65b5ba7@wordpress.org>

#4383: Plugin 'Reviews' tab should provide more information to logged-out users
------------------------------+-----------------------
 Reporter:  DannyCooper       |       Owner:  (none)
     Type:  defect            |      Status:  reopened
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+-----------------------

Comment (by DannyCooper):

 I'm not familiar enough with the .org codebase to submit a patch, but I
 think something as simple as this would work:

 [[Image(https://i.imgur.com/rWlcnAR.png)]]

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

From noreply at wordpress.org  Sat Jun 22 10:33:28 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 22 Jun 2019 10:33:28 +0000 (UTC)
Subject: [wp-meta] [8987]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-discussions:
 Translate,
 Discussion: Start with basic UI elements for creating a new discussion and
 rejecting with feedback.
Message-ID: <20190622103328.B9C9A1B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190622/f43c8f2a/attachment-0001.html>

From noreply at wordpress.org  Sat Jun 22 10:33:30 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 10:33:30 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.d2806e8126647a27005548cbe61c78d9@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------

Comment (by ocean90):

 In [changeset:"8987" 8987]:
 {{{
 #!CommitTicketReference repository="" revision="8987"
 Translate, Discussion: Start with basic UI elements for creating a new
 discussion and rejecting with feedback.

 See #4518.
 }}}

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

From noreply at wordpress.org  Sat Jun 22 14:01:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 14:01:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4524: Gitlab support for remote
 css
Message-ID: <049.2a84ba5d9c25b7aa26d7cd1979ded571@wordpress.org>

#4524: Gitlab support for remote css
-------------------------------------+-------------------------
 Reporter:  tippl                    |      Owner:  (none)
     Type:  task                     |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  needs-patch
-------------------------------------+-------------------------
 Hi,
 I am creating our WordCamp website for Düsseldorf/Germany right now. For
 this I use the remote css feature.

 When I tried to add the style.css I learned that only a Github link is
 accepted. I would like to use Gitlab instead of Github.  What is the
 reason for this limitation?

 Best
 Manja

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4524>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun 22 14:31:48 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 14:31:48 -0000
Subject: [wp-meta] [Making WordPress.org] #4524: Gitlab support for
 remote css
In-Reply-To: <049.2a84ba5d9c25b7aa26d7cd1979ded571@wordpress.org>
References: <049.2a84ba5d9c25b7aa26d7cd1979ded571@wordpress.org>
Message-ID: <064.d3443a3b1839b8bde59e773cf0a1ae7d@wordpress.org>

#4524: Gitlab support for remote css
-------------------------------------+---------------------
 Reporter:  tippl                    |       Owner:  (none)
     Type:  task                     |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by vdwijngaert):

 Hey Manja,

 You are working locally, right? You can use the
 "wcrcss_trusted_remote_hostnames" filter to add gitlab.com to the list.
 This might get you started while waiting for this ticket to be resolved.

 {{{#!php
 <?php
 add_filter( 'wcrcss_trusted_remote_hostnames', function(
 $trusted_hostnames ) {
   $trusted_hostnames[] = 'gitlab.com';
   return $trusted_hostnames;
 } );
 }}}

 Best of luck with your WordCamp!

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

From noreply at wordpress.org  Sat Jun 22 14:59:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 14:59:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4506: i18n: Create list with
 CL-PTE's and their respective projects
In-Reply-To: <056.0c852f5540d41ccb48a6a098cc0e473a@wordpress.org>
References: <056.0c852f5540d41ccb48a6a098cc0e473a@wordpress.org>
Message-ID: <071.48d6042a50261f2c4642fa8475d48356@wordpress.org>

#4506: i18n: Create list with CL-PTE's and their respective projects
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by ocean90):

 @Nao Your comment sounds related to #1664.

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

From noreply at wordpress.org  Sat Jun 22 18:57:23 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 18:57:23 -0000
Subject: [wp-meta] [Making WordPress.org] #4525: Add insights to the plugin
 language packs page
Message-ID: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>

#4525: Add insights to the plugin language packs page
--------------------------------------+------------------------------------
 Reporter:  ramiy                     |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:  2nd-opinion needs-
                                      |  patch
--------------------------------------+------------------------------------
 This ticket is about the Plugin **language packs** page.

 https://wordpress.org/plugins/site-health-manager/ (Main plugin page)
 https://translate.wordpress.org/projects/wp-plugins/site-health-manager/
 https://translate.wordpress.org/projects/wp-plugins/site-health-
 manager/contributors/
 https://translate.wordpress.org/projects/wp-plugins/site-health-manager
 /language-packs/ (**This page**)

 ----

 The main plugin page displays the number of languages the plugin has ( on
 the sidebar - **[https://wordpress.org/plugins/site-health-manager/
 Languages: See all 9]** ).

 The problem is that the number of languages is not the same as the number
 of updated languages. It only represents the total language packs created.

 I would like to see in the plugin language packs page more data, not only
 a dumb list. I would like to see insights and maybe a graph like the one
 we currently have in the contributors page.

 Extra data to display:

 * Total number of language packs
 * Current plugin version
 * The number of packs for the current version
 * The number of packs for older version.
 * Pie Chart displaying languages packs by version.

 The chart can show plugin developers if the languages packs are mainly for
 obsolete versions or for the latest version. This single chart is much
 more useful than the list of languages.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4525>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sat Jun 22 23:46:34 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Jun 2019 23:46:34 -0000
Subject: [wp-meta] [Making WordPress.org] #4525: Add insights to the
 plugin language packs page
In-Reply-To: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
References: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
Message-ID: <064.4aeb3f06588ea4d801fa3668c40a5644@wordpress.org>

#4525: Add insights to the plugin language packs page
--------------------------------------+---------------------
 Reporter:  ramiy                     |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion needs-patch   |
--------------------------------------+---------------------

Comment (by tobifjellner):

 Almost only the plugin developer himself/herself may know how big
 differences there are in the strings between various versions.
 This can still be a good piece of information to add.

 But perhaps even better might be some graphics/diagram based on "How many
 percent of the strings in current stable version are translated in the
 latest available language pack". However – this metric can be demanding to
 create: If a plugin previously was translated to, say, 98% then a language
 pack got created, since the threshold of 95% was met. If later new strings
 were added, the translated percentage may have dropped to 50%. Even if
 someone after that again translated 40% and brought the translation to
 90%, the latest language pack still matches only 50% of the strings.

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

From noreply at wordpress.org  Sun Jun 23 00:45:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 00:45:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4525: Add insights to the
 plugin language packs page
In-Reply-To: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
References: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
Message-ID: <064.ea46875c534a1a71e54bd0c3967ff7c8@wordpress.org>

#4525: Add insights to the plugin language packs page
--------------------------------------+---------------------
 Reporter:  ramiy                     |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion needs-patch   |
--------------------------------------+---------------------
Changes (by ramiy):

 * Attachment "4525.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4525>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jun 23 08:30:44 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 08:30:44 -0000
Subject: [wp-meta] [Making WordPress.org] #4345: Improve the display of
 block metadata in the plugin directory
In-Reply-To: <054.3d575332a1453e436aeb452eb1f32805@wordpress.org>
References: <054.3d575332a1453e436aeb452eb1f32805@wordpress.org>
Message-ID: <069.67348f2ccf013fa649ba685c072eb7d7@wordpress.org>

#4345: Improve the display of block metadata in the plugin directory
-------------------------------------------------+-------------------------
 Reporter:  tellyworth                           |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Plugin Directory                     |  Resolution:
 Keywords:  reporter-feedback 2nd-opinion has-   |
  screenshots                                    |
-------------------------------------------------+-------------------------

Comment (by tellyworth):

 #4519 involves a somewhat similar semantic structure, so perhaps we should
 use the same markup.

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

From noreply at wordpress.org  Sun Jun 23 13:44:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 13:44:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4521: Broken link in the
 plugin handbook sidebar
In-Reply-To: <055.aa69d2ba3a9fdd7018283d0d35897d2b@wordpress.org>
References: <055.aa69d2ba3a9fdd7018283d0d35897d2b@wordpress.org>
Message-ID: <070.4311d0c8f5a168f72163fce317046aab@wordpress.org>

#4521: Broken link in the plugin handbook sidebar
-------------------------+---------------------
 Reporter:  hofmannsven  |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:  close        |
-------------------------+---------------------
Changes (by hofmannsven):

 * keywords:   => close


Comment:

 The link is working again.

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

From noreply at wordpress.org  Sun Jun 23 13:56:18 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 13:56:18 -0000
Subject: [wp-meta] [Making WordPress.org] #4526: undercore missing
Message-ID: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>

#4526: undercore missing
---------------------+--------------------
 Reporter:  arena    |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:
---------------------+--------------------
 https://make.wordpress.org/core/handbook/best-practices/coding-
 standards/php/#interpolation-for-naming-dynamic-hooks

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4526>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jun 23 13:56:44 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 13:56:44 -0000
Subject: [wp-meta] [Making WordPress.org] #4526: undercore missing
In-Reply-To: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>
References: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>
Message-ID: <064.9072161487d9cefab7e240890f8d68b0@wordpress.org>

#4526: undercore missing
---------------------+---------------------
 Reporter:  arena    |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------
Changes (by arena):

 * Attachment "##.JPG" added.

 underscore missing

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4526>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jun 23 19:07:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 19:07:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4309: Displaying PHP
 Compatibility results from Tide on wp.org
In-Reply-To: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
References: <054.f77b6553a767cae983e08247e72e77dc@wordpress.org>
Message-ID: <069.75f09ba4328a188088a568deb23e1e7b@wordpress.org>

#4309: Displaying PHP Compatibility results from Tide on wp.org
------------------------------+------------------------
 Reporter:  JoshuaWold        |       Owner:  ck3lee
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------

Comment (by BrashRebel):

 I just wanted to raise one other concern real quick: With this addition,
 "Tested up to:" could become a new point of confusion. We would have for
 example:

 ...
 - WordPress Version: 4.9 or higher
 - Tested up to: 5.2
 - PHP Version: 5.6 to 7.1

 The second item does not state what it pertains to. WordPress is implied
 currently but if we add another item to the list with an independent
 version number, we could introduce confusion. The matter is potentially
 exacerbated by the fact that numbers will commonly be similar since
 WordPress has now reached 5.x and so is much of the supported PHP.

 It might be wise to consider revising all three labels for clarity if we
 are going to introduce independent version numbers.

 Separate, less important question: Could we introduce capitalization
 consistency throughout all the labels?

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

From noreply at wordpress.org  Sun Jun 23 21:15:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 21:15:50 -0000
Subject: [wp-meta] [Making WordPress.org] #4525: Add insights to the
 plugin language packs page
In-Reply-To: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
References: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
Message-ID: <064.2699840c3d1058f5efb709ee32334de1@wordpress.org>

#4525: Add insights to the plugin language packs page
--------------------------------------+---------------------
 Reporter:  ramiy                     |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion needs-patch   |
--------------------------------------+---------------------
Changes (by ramiy):

 * Attachment "4525.patch" added.

 initial patch (not tested)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4525>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Jun 23 21:36:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Jun 2019 21:36:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4524: Gitlab support for
 remote css
In-Reply-To: <049.2a84ba5d9c25b7aa26d7cd1979ded571@wordpress.org>
References: <049.2a84ba5d9c25b7aa26d7cd1979ded571@wordpress.org>
Message-ID: <064.33d451527d2f0ea283efb2d2a2663dca@wordpress.org>

#4524: Gitlab support for remote css
----------------------------------------+-----------------------
 Reporter:  tippl                       |       Owner:  (none)
     Type:  task                        |      Status:  assigned
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------
Changes (by iandunn):

 * keywords:  needs-patch => needs-patch good-first-bug
 * status:  new => assigned


Comment:

 Remote CSS uses a safelist approach
 [https://github.com/WordPress/wordcamp.org/blob/8cc71f2a5c3037b55e0daebf57454645fb8fecaa/public_html
 /wp-content/plugins/wordcamp-remote-css/app/user-interface.php#L129-L139
 for security reasons], but it'd be great to add more popular platforms,
 and GitLab would be perfect.

 The only reason we haven't already is just that there's always more work
 to do than people to do it, but if anyone wants to contribute a patch
 that'd be great. You could look at
 [https://github.com/WordPress/wordcamp.org/blob/8cc71f2a5c3037b55e0daebf57454645fb8fecaa/public_html
 /wp-content/plugins/wordcamp-remote-css/platforms/github.php github.php]
 as an example.

 It'd be good to update the contextual help docs as well.

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

From noreply at wordpress.org  Mon Jun 24 16:50:27 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 16:50:27 -0000
Subject: [wp-meta] [Making WordPress.org] #4527: Add the Cookie Policy to
 the privacy menu items.
Message-ID: <059.fe6b918d5e96b60a7223eb3ce1f3c268@wordpress.org>

#4527: Add the Cookie Policy to the privacy menu items.
-----------------------------+--------------------
 Reporter:  garrett-eclipse  |      Owner:  (none)
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:
Component:  General          |   Keywords:
-----------------------------+--------------------
 Hello,

 Can we have the Cookie Policy added alongside the Privacy Policy, Data
 Export Request, and Data Erasure Request pages in the privacy menu.

 Thank you

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4527>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 24 16:50:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 16:50:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4527: Add the Cookie Policy
 to the privacy menu items.
In-Reply-To: <059.fe6b918d5e96b60a7223eb3ce1f3c268@wordpress.org>
References: <059.fe6b918d5e96b60a7223eb3ce1f3c268@wordpress.org>
Message-ID: <074.743083be32a6ea4b7dc4656e4e4d9faf@wordpress.org>

#4527: Add the Cookie Policy to the privacy menu items.
-----------------------------+---------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:
 Keywords:                   |
-----------------------------+---------------------
Changes (by garrett-eclipse):

 * Attachment "4527.diff" added.

 Patch to add the Cookie Policy link to the privacy menu items

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4527>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 24 17:02:32 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 17:02:32 -0000
Subject: [wp-meta] [Making WordPress.org] #4528: Provide Data Export Request
 link on the Privacy Policy 'Access to Data' section.
Message-ID: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>

#4528: Provide Data Export Request link on the Privacy Policy 'Access to Data'
section.
-----------------------------+--------------------
 Reporter:  garrett-eclipse  |      Owner:  (none)
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:
Component:  General          |   Keywords:
-----------------------------+--------------------
 Hello,

 Similar to how the Data Erasure Request was provided on the Privacy
 Policy;
 > If you would like to request deletion of your account and associated
 data, please follow these steps:
 >
 > 1. Visit https://wordpress.org/about/privacy/data-erasure-request/.
 > 2. Enter your email address.
 > 3. Click “Accept Declaration and Request Permanent Account Deletion”.
 > Note: If you have a WP.org account, it’s recommended you log in before
 submitting to associate your account with the request.

 Would like to have the Data Export Request included in the same way but
 under the Access to Data section.
 Link - https://wordpress.org/about/privacy/data-export-request/

 Thanks

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4528>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 24 17:03:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 17:03:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4528: Provide Data Export
 Request link on the Privacy Policy 'Access to Data' section.
In-Reply-To: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
References: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
Message-ID: <074.6a3dea9c0b8db3a4d6419136044507a0@wordpress.org>

#4528: Provide Data Export Request link on the Privacy Policy 'Access to Data'
section.
-----------------------------+---------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:
 Keywords:                   |
-----------------------------+---------------------
Changes (by garrett-eclipse):

 * Attachment "4528.diff" added.

 Patch to update Privacy Policy to include a link to the Data Export
 Request page.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4528>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 24 17:24:50 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 17:24:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3773: Request from Marketing
 Team to Implement Navigation Change at make.wordpress.org
In-Reply-To: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
References: <059.77c867355460bad97bd8a21d6c3d62bc@wordpress.org>
Message-ID: <074.442db45c7369e660735fc19d164a8dfd@wordpress.org>

#3773: Request from Marketing Team to Implement Navigation Change at
make.wordpress.org
-------------------------------------------------+---------------------
 Reporter:  westcountymedia                      |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  high                                 |   Milestone:
Component:  Make (Get Involved) / P2             |  Resolution:
 Keywords:  ui-feedback ux-feedback 2nd-opinion  |
-------------------------------------------------+---------------------

Comment (by westcountymedia):

 Replying to [comment:7 karmatosed]:
 > @westcountymedia thanks for working on this what about these as options
 to focus the links:
 >
 > Meetup Groups (https://www.meetup.com/pro/wordpress/)
 > WordCamps (https://central.wordcamp.org/)
 > Team Meetings (https://make.wordpress.org/meetings/)
 > Team Updates (https://make.wordpress.org/updates/)
 >
 > For now, I think not having the contribution day link probably is a good
 balance.
 >
 > @hedgefield are you still able to create a mockup? That would be great.

 I think adding these links to Meetups and WordCamps on this page would be
 a huge improvement and possibly encourage more people to get involved with
 WordPress locally.

 Not sure why posting link(s) to Contributor Day resources (eg.
 "Participate at a Contributor Day" / "Organize a Contributor Day") doesn't
 fit within "Get Involved" TBH. But I'm all for starting somewhere :)

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

From noreply at wordpress.org  Mon Jun 24 19:22:06 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 24 Jun 2019 19:22:06 +0000 (UTC)
Subject: [wp-meta] [8988]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: Service Worker
 Caching: Add notes for iteration.
Message-ID: <20190624192206.0BCAB1B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190624/67874c97/attachment-0001.html>

From noreply at wordpress.org  Mon Jun 24 19:22:11 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 24 Jun 2019 19:22:11 +0000 (UTC)
Subject: [wp-meta] [8989] sites/trunk/wordcamp.org/.docker: WordCamp Docker:
 Apply coding stanards.
Message-ID: <20190624192211.2553A1B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190624/1a48a307/attachment.html>

From noreply at wordpress.org  Mon Jun 24 19:46:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 19:46:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support Forum
 Replies
Message-ID: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+--------------------
 Reporter:  felipeloureirosantos  |      Owner:  (none)
     Type:  enhancement           |     Status:  new
 Priority:  normal                |  Milestone:
Component:  Support Forums        |   Keywords:
----------------------------------+--------------------
 I believe that we should make the support forums a happier and better
 place, so I just realized about something that could improve the
 communication.

 Most social medias (even Slack) have this feature: **reaction to
 replies**. It could make the support forums more informal and dynamic, so
 I really would like to proposal this feature.

 I don't think we should just allow all emojis. Maybe choose some of them
 (like these: https://snag.gy/Jp4aBK.jpg) or create some icons. We could
 just try it out using just the dashicons-heart, and then provide new
 reactions.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4529>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Mon Jun 24 23:01:14 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Jun 2019 23:01:14 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.3c3568689f4c25ed9283dbdde7b6107a@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+---------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:
 Keywords:                        |
----------------------------------+---------------------

Comment (by joyously):

 I am against this. The forums are for support, not emoting.

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

From noreply at wordpress.org  Mon Jun 24 23:55:24 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 24 Jun 2019 23:55:24 +0000 (UTC)
Subject: [wp-meta] [8990]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/camptix-tweaks.php:
 WordCamp: Add HubSpot to list of global sponsors in ticket email footers
Message-ID: <20190624235524.A54591B004A8@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190624/201f1a41/attachment.html>

From noreply at wordpress.org  Tue Jun 25 13:33:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 13:33:33 -0000
Subject: [wp-meta] [Making WordPress.org] #974: Make WordPress.tv theme
 responsive
In-Reply-To: <054.3f56752fb059e84796d7716779ffdb79@wordpress.org>
References: <054.3f56752fb059e84796d7716779ffdb79@wordpress.org>
Message-ID: <069.a21f929da0028686099c3519ff91d9ed@wordpress.org>

#974: Make WordPress.tv theme responsive
--------------------------------------------------+-----------------------
 Reporter:  BrashRebel                            |       Owner:  (none)
     Type:  enhancement                           |      Status:  assigned
 Priority:  normal                                |   Milestone:
Component:  WordPress.tv                          |  Resolution:
 Keywords:  good-first-bug has-patch ui-feedback  |
--------------------------------------------------+-----------------------

Comment (by casiepa):

 Related: https://meta.trac.wordpress.org/ticket/4304
 The theme suddenly got activated again.

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

From noreply at wordpress.org  Tue Jun 25 17:02:17 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 17:02:17 -0000
Subject: [wp-meta] [Making WordPress.org] #4508: Suggestion to make
 "make glossary" less obtrusive
In-Reply-To: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
References: <056.293d5974da9290869aa7a4a419163ff3@wordpress.org>
Message-ID: <071.ef24988bcd26312e7ce578f778f428b4@wordpress.org>

#4508: Suggestion to make "make glossary" less obtrusive
--------------------------------------+---------------------
 Reporter:  tobifjellner              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:6 tellyworth]:
 > @talldanwp suggested https://github.com/tristen/hoverintent as a
 possible candidate for implementing this.

 Since Make blogs appear to include jQuery, can't we just use core's
 bundled `hoverIntent.js`?

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

From noreply at wordpress.org  Tue Jun 25 17:17:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 17:17:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4530: Adding missing profile
 badges
Message-ID: <050.e99569106133ddd02d31257063a8f346@wordpress.org>

#4530: Adding missing profile badges
----------------------+--------------------
 Reporter:  stubgo    |      Owner:  (none)
     Type:  task      |     Status:  new
 Priority:  low       |  Milestone:
Component:  Profiles  |   Keywords:
----------------------+--------------------
 I'm migrating my .org account @stubgo to @miinasikk to match the rest of
 the profiles and WP Slack handle and avoid some confusion. Wondering if it
 would be possible to migrate my badges (Core Contributor, Tide
 Contributor, WordCamp Speaker, and Plugin Developer) from @stubgo to
 @miinasikk. Thanks!

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4530>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 25 20:29:18 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 20:29:18 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.0a1ca878de20664522ee26fe685b1c7c@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+---------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:
 Keywords:                        |
----------------------------------+---------------------

Comment (by sterndata):

 I second Joy's note.  Do not gamify the forums.

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

From noreply at wordpress.org  Tue Jun 25 20:47:09 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Jun 2019 20:47:09 +0000 (UTC)
Subject: [wp-meta] [8991] sites/trunk/wordcamp.org: WordCamp Docker: Setup
 fully-trusted SSL certs for testing service workers.
Message-ID: <20190625204709.993EE1B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190625/41e8b0c3/attachment-0001.html>

From noreply at wordpress.org  Tue Jun 25 20:47:14 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Jun 2019 20:47:14 +0000 (UTC)
Subject: [wp-meta] [8992] sites/trunk/wordcamp.org/.docker/wp-config.php:
 WordCamp Docker: Add missing constants to sample `wp-config`.
Message-ID: <20190625204714.2AFFE1B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190625/42307e81/attachment.html>

From noreply at wordpress.org  Tue Jun 25 20:47:18 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Jun 2019 20:47:18 +0000 (UTC)
Subject: [wp-meta] [8993] sites/trunk/wordcamp.org/docker-compose.yaml:
 WordCamp Docker: Update WP branch when booting container.
Message-ID: <20190625204718.396511B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190625/358ae66e/attachment-0001.html>

From noreply at wordpress.org  Tue Jun 25 20:47:24 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Jun 2019 20:47:24 +0000 (UTC)
Subject: [wp-meta] [8994] sites/trunk/wordcamp.org: WordCamp Docker: Update
 sample database.
Message-ID: <20190625204725.2B4C11B00425@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190625/70f4e293/attachment-0001.html>

From noreply at wordpress.org  Tue Jun 25 20:49:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 20:49:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.8129e0ba805362cf461c5cd6783e4ff1@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+---------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:
 Keywords:                        |
----------------------------------+---------------------

Comment (by felipeloureirosantos):

 I believe that as we are human begins, so emotions are a part of us and
 part of everything. Those small things help us to provide a better
 support. It could help users that are somehow nervous and make it more
 dynamic. But I understand your points of views.

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

From noreply at wordpress.org  Tue Jun 25 21:51:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 21:51:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4531: Delete WCEU Banner from
 wordpress.org homepage
Message-ID: <055.e6330e0ea9f1fb5c0b4ee45fd60be931@wordpress.org>

#4531: Delete WCEU Banner from  wordpress.org homepage
-------------------------+--------------------
 Reporter:  grafruessel  |      Owner:  (none)
     Type:  task         |     Status:  new
 Priority:  high         |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 Hi there,

 the webpage @ https://wordpress.org/ still has the WordCamp Europe 2019
 Banner on the frontpage. That needs to be removed.

 Thanks

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4531>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Tue Jun 25 22:38:37 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Jun 2019 22:38:37 -0000
Subject: [wp-meta] [Making WordPress.org] #4531: Delete WCEU Banner from
 wordpress.org homepage
In-Reply-To: <055.e6330e0ea9f1fb5c0b4ee45fd60be931@wordpress.org>
References: <055.e6330e0ea9f1fb5c0b4ee45fd60be931@wordpress.org>
Message-ID: <070.2e75fdf6a2c76b3358cff7f27cb9c631@wordpress.org>

#4531: Delete WCEU Banner from  wordpress.org homepage
-------------------------+-----------------------
 Reporter:  grafruessel  |       Owner:  Otto42
     Type:  task         |      Status:  accepted
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Changes (by Otto42):

 * owner:  (none) => Otto42
 * priority:  high => normal
 * status:  new => accepted


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

From noreply at wordpress.org  Wed Jun 26 06:41:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 06:41:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4532: Issue on the Website of
 WordCamp Karachi 2019
Message-ID: <055.03f5af326d7640790d60bbc1dcff97db@wordpress.org>

#4532: Issue on the Website of WordCamp Karachi 2019
-------------------------------------+--------------------
 Reporter:  harshbarach              |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  high                     |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 I have reviewed and found, there is **wrong sequence on the Schedule page
 of WordCamp Karachi 2019** https://2019.karachi.wordcamp.org/schedule/.

 **Current Behaviour:** There is 10.30 (Tea Break) located after 11.00
 (Panel Discussion [Speaker to be announced soon]) in the Schedule page of
 the WordCamp Karachi 2019 . **This is wrong sequence.**

 **Expected Behaviour:** According to time sequence 10.30 should come first
 then 11.00 should come. So, the Sequence should be 10.00 ([Speaker to be
 announced soon]) then 10.30 (Tea Break) and 11.00 (Panel Discussion
 [Speaker to be announced soon]).

 I think this typo should be sort out as soon as possible to provide proper
 information to user.

 Thank you.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4532>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 06:41:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 06:41:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4532: Issue on the Website of
 WordCamp Karachi 2019
In-Reply-To: <055.03f5af326d7640790d60bbc1dcff97db@wordpress.org>
References: <055.03f5af326d7640790d60bbc1dcff97db@wordpress.org>
Message-ID: <070.0a7ca4e49c39c989bcbc3a959bef96ed@wordpress.org>

#4532: Issue on the Website of WordCamp Karachi 2019
-------------------------------------+---------------------
 Reporter:  harshbarach              |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  high                     |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------
Changes (by harshbarach):

 * Attachment "karachi-wc.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4532>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 07:04:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 07:04:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4532: Issue on the Website of
 WordCamp Karachi 2019
In-Reply-To: <055.03f5af326d7640790d60bbc1dcff97db@wordpress.org>
References: <055.03f5af326d7640790d60bbc1dcff97db@wordpress.org>
Message-ID: <070.aa43629c32e6806394b951c8fdda397e@wordpress.org>

#4532: Issue on the Website of WordCamp Karachi 2019
-------------------------------------+----------------------
 Reporter:  harshbarach              |       Owner:  (none)
     Type:  defect                   |      Status:  closed
 Priority:  high                     |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  invalid
 Keywords:                           |
-------------------------------------+----------------------
Changes (by iandunn):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 It looks like they're manually constructing the table with the Table
 block, rather than using the automated `[schedule]` shortcode, so this is
 something for the organizers to address, rather than the Meta team.

 cc @fahaddsheikh

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

From noreply at wordpress.org  Wed Jun 26 09:30:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:30:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
Message-ID: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  high            |  Milestone:
Component:  General         |   Keywords:  seo
----------------------------+--------------------
 Dozens of our localised homepages link to invalid/broken/missing showcase
 pages.

 E.g., see the "WordPress Users" section in the bottom right of:
 - https://ido.wordpress.org/
 - https://gu.wordpress.org/
 - https://kal.wordpress.org/

 Noteably, from this small sample:
 - The Rolling Stones website is no longer powered by WP -
 https://wordpress.org/showcase/the-rolling-stones/
 - The CNN tag is empty - https://wordpress.org/showcase/tag/cnn/
 - The Motley Crue showcase page returns a 404 error -
 https://wordpress.org/showcase/motley-crue/

 This is more than a little embarrassing (and harmful from an SEO / quality
 perspective), and I think it calls for a degree of standardization of this
 component across localized homepages.

 Can we pick three prominent showcase entries, and update + manage these
 centrally?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4533>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 09:33:32 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:33:32 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
In-Reply-To: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
References: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
Message-ID: <073.d048fa3da8a47cab6c7c2139f406e324@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
-------------------------------------------+---------------------
 Reporter:  jonoaldersonwp                 |       Owner:  (none)
     Type:  defect                         |      Status:  new
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+---------------------
Changes (by jonoaldersonwp):

 * component:  General => International Sites (Rosetta)


Old description:

> Dozens of our localised homepages link to invalid/broken/missing showcase
> pages.
>
> E.g., see the "WordPress Users" section in the bottom right of:
> - https://ido.wordpress.org/
> - https://gu.wordpress.org/
> - https://kal.wordpress.org/
>
> Noteably, from this small sample:
> - The Rolling Stones website is no longer powered by WP -
> https://wordpress.org/showcase/the-rolling-stones/
> - The CNN tag is empty - https://wordpress.org/showcase/tag/cnn/
> - The Motley Crue showcase page returns a 404 error -
> https://wordpress.org/showcase/motley-crue/
>
> This is more than a little embarrassing (and harmful from an SEO /
> quality perspective), and I think it calls for a degree of
> standardization of this component across localized homepages.
>
> Can we pick three prominent showcase entries, and update + manage these
> centrally?

New description:

 Dozens of our localised homepages link to invalid/broken/missing showcase
 pages.

 E.g., see the "WordPress Users" section in the bottom right of:
 - https://ido.wordpress.org/
 - https://gu.wordpress.org/
 - https://kal.wordpress.org/

 Noteably, from this small sample:
 - The Rolling Stones website is no longer powered by WP -
 https://wordpress.org/showcase/the-rolling-stones/ (note that this one is
 also featured on the wordpress.org homepage)
 - The CNN tag is empty - https://wordpress.org/showcase/tag/cnn/
 - The Motley Crue showcase page returns a 404 error -
 https://wordpress.org/showcase/motley-crue/

 This is more than a little embarrassing (and harmful from an SEO / quality
 perspective), and I think it calls for a degree of standardization of this
 component across localized homepages.

 Can we pick three prominent showcase entries, and update + manage these
 centrally?

--

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

From noreply at wordpress.org  Wed Jun 26 09:35:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:35:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4534: The main/header menu on
 uz.wordpress.org features a broken link
Message-ID: <058.aebb4a536871e5d03d43331e6039c790@wordpress.org>

#4534: The main/header menu on uz.wordpress.org features a broken link
-------------------------------------------+--------------------
 Reporter:  jonoaldersonwp                 |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  lowest                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:  seo
-------------------------------------------+--------------------
 The `Biz haqimizda` link in the main nav on https://uz.wordpress.org pages
 should be removed, as it links to a missing page
 (https://uz.wordpress.org/?page_id=2)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4534>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 09:38:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:38:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4289: Delete placeholder pages
In-Reply-To: <058.ea8feffab078bd39b6b91ea5f5d70670@wordpress.org>
References: <058.ea8feffab078bd39b6b91ea5f5d70670@wordpress.org>
Message-ID: <073.e27888f2c644d5206e1f17eea1d8cee9@wordpress.org>

#4289: Delete placeholder pages
-------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  defries
     Type:  defect                         |      Status:  assigned
 Priority:  low                            |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+-----------------------
Changes (by jonoaldersonwp):

 * keywords:   => seo


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

From noreply at wordpress.org  Wed Jun 26 09:43:20 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:43:20 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
In-Reply-To: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
References: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
Message-ID: <073.e90e87ec1367984ca53111dc4741e884@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
-------------------------------------------+---------------------
 Reporter:  jonoaldersonwp                 |       Owner:  (none)
     Type:  defect                         |      Status:  new
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+---------------------

Comment (by fierevere):

 some locales still maintain a viable list of localized WordPress sites and
 therefore can offer a better showcase experience for local visitors.

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

From noreply at wordpress.org  Wed Jun 26 09:44:47 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:44:47 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
In-Reply-To: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
References: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
Message-ID: <073.54571532b7abfd1fe11e8210e2701334@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
-------------------------------------------+---------------------
 Reporter:  jonoaldersonwp                 |       Owner:  (none)
     Type:  defect                         |      Status:  new
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+---------------------

Comment (by jonoaldersonwp):

 Replying to [comment:2 fierevere]:
 > some locales still maintain a viable list of localized WordPress sites
 and therefore can offer a better showcase experience for local visitors.

 If they can guarantee that those links will remain valid and up to date,
 that's fine. But, I'm sure that's what they thought originally, and it
 clearly wasn't the case. Given how poorly loved and maintained many of
 these sites/pages are, I'd be keen to err on the side of caution.

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

From noreply at wordpress.org  Wed Jun 26 09:45:06 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Jun 2019 09:45:06 +0000 (UTC)
Subject: [wp-meta] [8995]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/front-page.php:
 WordPress.org Main Theme: Update fallback list for showcase entries.
Message-ID: <20190626094506.4D3051B0046D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190626/2feb50e8/attachment.html>

From noreply at wordpress.org  Wed Jun 26 09:45:08 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:45:08 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
In-Reply-To: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
References: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
Message-ID: <073.b3867cae3e2683c906830048ceeeeece@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
-------------------------------------------+----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  defect                         |      Status:  closed
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  fixed
 Keywords:  seo                            |
-------------------------------------------+----------------------
Changes (by ocean90):

 * owner:  (none) => ocean90
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8995" 8995]:
 {{{
 #!CommitTicketReference repository="" revision="8995"
 WordPress.org Main Theme: Update fallback list for showcase entries.

 Fixes #4533.
 }}}

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

From noreply at wordpress.org  Wed Jun 26 09:47:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:47:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4534: The main/header menu on
 uz.wordpress.org features a broken link
In-Reply-To: <058.aebb4a536871e5d03d43331e6039c790@wordpress.org>
References: <058.aebb4a536871e5d03d43331e6039c790@wordpress.org>
Message-ID: <073.4b9215f0c49e886b203138d86258abb7@wordpress.org>

#4534: The main/header menu on uz.wordpress.org features a broken link
-------------------------------------------+---------------------
 Reporter:  jonoaldersonwp                 |       Owner:  (none)
     Type:  defect                         |      Status:  closed
 Priority:  lowest                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  fixed
 Keywords:  seo                            |
-------------------------------------------+---------------------
Changes (by ocean90):

 * status:  new => closed
 * resolution:   => fixed


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

From noreply at wordpress.org  Wed Jun 26 09:50:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 09:50:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4535: Delete "Hello World" posts
 (and tidy up empty blogs)
Message-ID: <058.87dc495106ed159669fe26da9de54680@wordpress.org>

#4535: Delete "Hello World" posts (and tidy up empty blogs)
-------------------------------------------+--------------------
 Reporter:  jonoaldersonwp                 |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  high                           |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:  seo
-------------------------------------------+--------------------
 Various Rosetta sites have a blog with a "Hello World" post. These should
 be deleted.
 Because of the incorrect hreflang setup on these sites, these posts cause
 an absolute SEO nightmare as Google seeks out their (non-existent)
 siblings across the whole network.

 E.g.,
 https://tg.wordpress.org/2012/08/23/hello-world/
 https://tt.wordpress.org/2014/07/08/hello-world/
 https://fao.wordpress.org/2016/07/20/hello-world/
 https://dzo.wordpress.org/2015/02/24/hello-world/
 https://kab.wordpress.org/2015/02/24/hello-world/
 https://sa.wordpress.org/2011/07/26/hello-world/
 https://hau.wordpress.org/2016/07/15/hello-world/
 https://bre.wordpress.org/2015/07/17/hello-world/
 https://ak.wordpress.org/2016/03/05/hello-world/
 https://es-pr.wordpress.org/2016/03/05/hello-world/
 https://rup.wordpress.org/2016/03/05/hello-world/

 I don't have an easy way of finding them all from the outside-in - I'm
 hoping that these should be easy to round up?

 It's also worth considering that in many cases, these are the only blog
 posts on these blogs. E.g., https://dzo.wordpress.org/news/,
 https://bre.wordpress.org/news/

 When that's the case and we're removing them, can we also please:

 - Remove the entire blog
 - Remove menu links to the (removed) blog
 - 301 redirect requests to the blog root URL (e.g.,
 https://bre.wordpress.org/news/) to the local site root (e.g.,
 https://bre.wordpress.org/)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4535>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 10:03:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:03:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4535: Delete "Hello World"
 posts (and tidy up empty blogs)
In-Reply-To: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
References: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
Message-ID: <073.eb73f3186f8149850698f93727a84f00@wordpress.org>

#4535: Delete "Hello World" posts (and tidy up empty blogs)
-------------------------------------------+---------------------
 Reporter:  jonoaldersonwp                 |       Owner:  (none)
     Type:  defect                         |      Status:  new
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+---------------------

Comment (by casiepa):

 Hi @jonoaldersonwp, from my side (technically speaking) I could go in and
 delete the 'Hello World' pages and that won't break anything.
 But for your other requests this would mean that when the team of the
 locale starts to use it, we would need to undo these changes again, so I'm
 not in favor of that, but I let others respond to that part.

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

From noreply at wordpress.org  Wed Jun 26 10:09:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:09:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4535: Delete "Hello World"
 posts (and tidy up empty blogs)
In-Reply-To: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
References: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
Message-ID: <073.a0c9e5dc76a061a2538211c0596f24f1@wordpress.org>

#4535: Delete "Hello World" posts (and tidy up empty blogs)
-------------------------------------------+---------------------
 Reporter:  jonoaldersonwp                 |       Owner:  (none)
     Type:  defect                         |      Status:  new
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+---------------------

Comment (by jonoaldersonwp):

 Makes sense, although, they haven't used these at all (since 2011 in some
 cases), so I don't think that's a burning consideration.

 We also need a much better system/process in place before they do actively
 use them; there's a lot of poorly managed duplication of wordpress.org
 blog comment when/where they are infrequently used, and that causes a
 whole raft of other issues.

 More significantly, the technical approach to these is shot - the hreflang
 tags on https://nl.wordpress.org/2019/05/08/wordpress-5-2-is-vrijgegeven/,
 as just one isolated example, are actively damaging the whole ecosystem.

 I'm keen to err on the side of burning down as much of it we can, and
 making special cases for scenarios where it's needed and managed well...

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

From noreply at wordpress.org  Wed Jun 26 10:12:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:12:55 -0000
Subject: [wp-meta] [Making WordPress.org] #3423: Add new functionality
 for editor/locale requests
In-Reply-To: <052.2e4f3425f0456305278278f1c347b62e@wordpress.org>
References: <052.2e4f3425f0456305278278f1c347b62e@wordpress.org>
Message-ID: <067.7bea78c6f93915a4ec200d38a28ed2b6@wordpress.org>

#3423: Add new functionality for editor/locale requests
--------------------------------------+---------------------
 Reporter:  danieltj                  |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion               |
--------------------------------------+---------------------

Comment (by eclare):

 **New discussion on P2**: https://make.wordpress.org/polyglots/2019/06/26
 /proposal-for-handling-pte-requests/

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

From noreply at wordpress.org  Wed Jun 26 10:13:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:13:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4535: Delete "Hello World"
 posts (and tidy up empty blogs)
In-Reply-To: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
References: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
Message-ID: <073.f4dafd26ece4ed45e95ad739196568b8@wordpress.org>

#4535: Delete "Hello World" posts (and tidy up empty blogs)
-------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  enhancement                    |      Status:  accepted
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+-----------------------
Changes (by ocean90):

 * owner:  (none) => ocean90
 * priority:  high => normal
 * status:  new => accepted
 * type:  defect => enhancement


Comment:

 The `hreflang` tag should probably be removed for posts.

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

From noreply at wordpress.org  Wed Jun 26 10:33:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:33:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4535: Delete "Hello World"
 posts (and tidy up empty blogs)
In-Reply-To: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
References: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
Message-ID: <073.989722d1d3b4f9a8020d205a9dd7b7dc@wordpress.org>

#4535: Delete "Hello World" posts (and tidy up empty blogs)
-------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  enhancement                    |      Status:  accepted
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+-----------------------

Comment (by jonoaldersonwp):

 Ah, that's a good idea! Doing more harm than good with the current setup.
 Want a separate ticket?

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

From noreply at wordpress.org  Wed Jun 26 10:36:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:36:59 -0000
Subject: [wp-meta] [Making WordPress.org] #4536: Rosetta main nav menus
 frequently link to missing 'Support' page
Message-ID: <058.3d1049262de19f0ae77e2fa78551cc95@wordpress.org>

#4536: Rosetta main nav menus frequently link to missing 'Support' page
-------------------------------------------+--------------------
 Reporter:  jonoaldersonwp                 |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  low                            |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:  seo
-------------------------------------------+--------------------
 See the the following examples:
 - https://pcm.wordpress.org/plugins/browse/blocks/
 - https://fr-be.wordpress.org/plugins/
 - https://es-hn.wordpress.org/plugins/jetpack/

 In each case, the Support link in the main nav should be removed.

 It looks like this isn't always present on the homepage, so I suspect
 there's some hard-coded template logic on 'inner pages' (as per these
 examples), but, individual sites haven't created a Support page.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4536>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 10:50:41 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:50:41 -0000
Subject: [wp-meta] [Making WordPress.org] #4537: Misc Rosetta site nav menu
 broken links
Message-ID: <058.ca9d15d76ffd85c9e6ce0c2966ce56fe@wordpress.org>

#4537: Misc Rosetta site nav menu broken links
-------------------------------------------+--------------------
 Reporter:  jonoaldersonwp                 |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  lowest                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:  seo
-------------------------------------------+--------------------
 The following are examples of broken links in Rosetta site nav menus.
 These should be removed.

 - On https://af.wordpress.org/, 'Laai af', pointing to ?page_id=5
 - On https://hr.wordpress.org/, 'O WordPressu' , pointing to ?page_id=2
 - On https://sw.wordpress.org/, 'Download', pointing to ?page_id=70
 - On https://ka.wordpress.org/, 'ფორუმი', pointing to /forum

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4537>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 10:56:40 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 10:56:40 -0000
Subject: [wp-meta] [Making WordPress.org] #4538: The merchandise store
 subdomain is missing Google Tag Manager
Message-ID: <058.dc506b926b44afca04ed42619ed9858a@wordpress.org>

#4538: The merchandise store subdomain is missing Google Tag Manager
----------------------------+-----------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  high            |  Milestone:
Component:  General         |   Keywords:  analytics
----------------------------+-----------------------
 Add our Google Tag Manager code to all templates on
 mercantile.wordpress.org

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4538>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 11:03:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 11:03:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4539: Requests to trac raw .diff
 files should return an x-robots-tag HTTP header
Message-ID: <058.db674f78928bfee15f786792caab5ba4@wordpress.org>

#4539: Requests to trac raw .diff files should return an x-robots-tag HTTP header
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  Trac            |   Keywords:  seo
----------------------------+--------------------
 Requests to raw .diff files - such as https://core.trac.wordpress.org/raw-
 attachment/ticket/45495/45495.diff - should return an `x-robots-tag` HTTP
 header with a value of `noindex`.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4539>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 11:12:19 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 11:12:19 -0000
Subject: [wp-meta] [Making WordPress.org] #4540: Noindex search results
 pages in the block editor handbook
Message-ID: <058.0cd9f3827395176ad1ca4c48e7f403f6@wordpress.org>

#4540: Noindex search results pages in the block editor handbook
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  Developer Hub   |   Keywords:  seo
----------------------------+--------------------
 The Block Editor Handbook features a search function; e.g.,
 https://developer.wordpress.org/block-editor/?s=cats.

 Results pages should include a meta robots tag, with a `noindex` value.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4540>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 11:22:20 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 11:22:20 -0000
Subject: [wp-meta] [Making WordPress.org] #4541: Change the title formatting
 on Profile templates
Message-ID: <058.e64a1beeece9d98e2899e4d046edf0f7@wordpress.org>

#4541: Change the title formatting on Profile templates
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Profiles        |   Keywords:  seo
----------------------------+--------------------
 At the moment, the structure of the page title on Profile pages is:
 `WordPress > Profiles » {{NAME}}`

 E.g., on https://profiles.wordpress.org/youknowriad/, that results in
 `WordPress › Profiles » Riad Benguella`

 The format should be changed to:
 `{{NAME}} - {{SHORTNAME}} | WordPress.org`

 E.g., on https://profiles.wordpress.org/youknowriad/, that results in
 `Riad Benguella - @youknowriad | WordPress.org`

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4541>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 11:30:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 11:30:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4542: Contributor references in
 news/announcement posts should have a trailing slash
Message-ID: <058.9c4e11908e9e897a181a4718583413ba@wordpress.org>

#4542: Contributor references in news/announcement posts should have a trailing
slash
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  General         |   Keywords:  seo
----------------------------+--------------------
 When users are linked to / referenced in posts (e.g., in the "The Squad"
 section on https://wordpress.org/news/2019/05/jaco/), the links to their
 profile pages should append/include a trailing slash.

 This should be applied retrospectively to existing posts where possible.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4542>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:00:48 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:00:48 -0000
Subject: [wp-meta] [Making WordPress.org] #4543: Plugin tag pages with fewer
 than 3 members should be noindex'd
Message-ID: <058.4c84e2f7b8906742784a336f78f3c3f9@wordpress.org>

#4543: Plugin tag pages with fewer than 3 members should be noindex'd
------------------------------+--------------------
 Reporter:  jonoaldersonwp    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  low               |  Milestone:
Component:  Plugin Directory  |   Keywords:  seo
------------------------------+--------------------
 Plugin tag pages like https://wordpress.org/plugins/tags/3gp/, which
 contain fewer than three members, should output a meta robots tag with a
 value of 'noindex, follow'.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4543>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:03:49 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:03:49 -0000
Subject: [wp-meta] [Making WordPress.org] #4544: Plugin tags with only one
 member should not be linked to
Message-ID: <058.0568657e5b991b22ea8ba0997c667a79@wordpress.org>

#4544: Plugin tags with only one member should not be linked to
------------------------------+--------------------
 Reporter:  jonoaldersonwp    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  low               |  Milestone:
Component:  Plugin Directory  |   Keywords:  seo
------------------------------+--------------------
 Links to tag pages like https://wordpress.org/plugins/tags/office-for-
 lease/, which contain only one member, should not be output in scenarios
 where tags are listed (e.g., the 'tags' sidebar section on
 https://wordpress.org/plugins/opal-estate/).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4544>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:11:52 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:11:52 -0000
Subject: [wp-meta] [Making WordPress.org] #4545: Make 'homepages' and
 paginated states omit canonical URL tags
Message-ID: <058.afc217eb22716092708f2496f2f5359c@wordpress.org>

#4545: Make 'homepages' and paginated states omit canonical URL tags
--------------------------------------+---------------------------
 Reporter:  jonoaldersonwp            |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  high                      |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:  seo analytics
--------------------------------------+---------------------------
 The following templates are missing a canonical URL tag, which is causing
 serious issues with over-indexing.

 https://make.wordpress.org/mobile/
 https://make.wordpress.org/core/page/10/

 Please add a canonical URL tag to each 'make' homepage, and to paginated
 states of their homepage/feeds (which reference the current paginated
 state).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4545>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:14:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:14:38 -0000
Subject: [wp-meta] [Making WordPress.org] #4546: Invalid date format
 requests to News URLs should 301 redirect
Message-ID: <058.32b532a54906eb84b1588bef8ee0ba24@wordpress.org>

#4546: Invalid date format requests to News URLs should 301 redirect
----------------------------+---------------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  General         |   Keywords:  seo analytics
----------------------------+---------------------------
 Adding a '0' month into a date URL, such as
 https://wordpress.org/news/2008/10/0/ or
 https://wordpress.org/news/2008/0/page/2/ should remove it via a 301
 redirect (to https://wordpress.org/news/2008/10/ and
 https://wordpress.org/news/2008/page/2/ respectively).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4546>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:18:20 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:18:20 -0000
Subject: [wp-meta] [Making WordPress.org] #4546: Invalid date format
 requests to News URLs should 301 redirect
In-Reply-To: <058.32b532a54906eb84b1588bef8ee0ba24@wordpress.org>
References: <058.32b532a54906eb84b1588bef8ee0ba24@wordpress.org>
Message-ID: <073.944defa338e06635434e9355784b9e34@wordpress.org>

#4546: Invalid date format requests to News URLs should 301 redirect
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  General         |  Resolution:
 Keywords:  seo analytics   |
----------------------------+---------------------
Description changed by jonoaldersonwp:

Old description:

> Adding a '0' month into a date URL, such as
> https://wordpress.org/news/2008/10/0/ or
> https://wordpress.org/news/2008/0/page/2/ should remove it via a 301
> redirect (to https://wordpress.org/news/2008/10/ and
> https://wordpress.org/news/2008/page/2/ respectively).

New description:

 Adding a '0' value into the month or day parameter of a date URL, such as
 https://wordpress.org/news/2008/10/0/ or
 https://wordpress.org/news/2008/0/page/2/ should remove it via a 301
 redirect (to https://wordpress.org/news/2008/10/ and
 https://wordpress.org/news/2008/page/2/ respectively).

--

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

From noreply at wordpress.org  Wed Jun 26 12:20:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:20:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4547:
 https://wordpress.org/support/topic/0/ is a dead/empty template/page
Message-ID: <058.62098bc8432b17f91b1705d9514c2b43@wordpress.org>

#4547: https://wordpress.org/support/topic/0/ is a dead/empty template/page
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  Support Forums  |   Keywords:  seo
----------------------------+--------------------
 Requests to https://wordpress.org/support/topic/0/ should 301 to
 https://wordpress.org/support/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4547>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:22:34 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:22:34 -0000
Subject: [wp-meta] [Making WordPress.org] #4531: Delete WCEU Banner from
 wordpress.org homepage
In-Reply-To: <055.e6330e0ea9f1fb5c0b4ee45fd60be931@wordpress.org>
References: <055.e6330e0ea9f1fb5c0b4ee45fd60be931@wordpress.org>
Message-ID: <070.d23fe081a9f54be247ec1a312381d4e5@wordpress.org>

#4531: Delete WCEU Banner from  wordpress.org homepage
-------------------------+---------------------
 Reporter:  grafruessel  |       Owner:  Otto42
     Type:  task         |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------
Changes (by Otto42):

 * status:  accepted => closed
 * resolution:   => fixed


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

From noreply at wordpress.org  Wed Jun 26 12:31:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:31:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4548: Noindex empty support
 profile subpages
Message-ID: <058.35cade71149b17eda3e4efacb24c0d59@wordpress.org>

#4548: Noindex empty support profile subpages
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Profiles        |   Keywords:  seo
----------------------------+--------------------
 Profiles in the support section, such as
 https://wordpress.org/support/users/evalim/, feature multiple 'subpages'
 such as https://wordpress.org/support/users/evalim/reviews/ and
 https://wordpress.org/support/users/evalim/replied-to/.

 When these subpages have no content, they should output a meta robots tag
 with a value of 'noindex, follow'.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4548>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:49:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:49:59 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
Message-ID: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+--------------------
 Reporter:  jonoaldersonwp   |      Owner:  (none)
     Type:  defect           |     Status:  new
 Priority:  normal           |  Milestone:
Component:  Theme Directory  |   Keywords:  seo
-----------------------------+--------------------
 When theme author archives (such as
 https://wordpress.org/themes/author/dans7919/) contain fewer than three
 themes, they should output a meta robots tag with a value of 'noindex,
 follow'.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4549>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:53:24 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:53:24 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.e64b92ca825d26b5331e38caf7f72a87@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+---------------------

Comment (by DannyCooper):

 Just a point of note, some of the most popular theme developers have less
 than three live themes.

 OceanWP is the most obvious example -
 https://wordpress.org/themes/author/oceanwp/
 (creator of the most popular theme - excluding TwentyX themes)

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

From noreply at wordpress.org  Wed Jun 26 12:54:36 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:54:36 -0000
Subject: [wp-meta] [Making WordPress.org] #4550: Improve the page title and
 meta descriptions of theme author archives
Message-ID: <058.a662a7455c0a1e13393e1630a0b618e9@wordpress.org>

#4550: Improve the page title and meta descriptions of theme author archives
-----------------------------+--------------------
 Reporter:  jonoaldersonwp   |      Owner:  (none)
     Type:  defect           |     Status:  new
 Priority:  high             |  Milestone:
Component:  Theme Directory  |   Keywords:  seo
-----------------------------+--------------------
 Theme author archives (such as
 https://wordpress.org/themes/author/dans7919/) currently have a title
 structure of `{{AUTHORSLUG}} | WordPress.org`.

 This should be changed to `Themes by {{AUTHORSLUG}} | WordPress.org`.

 The meta description should be changed to "See all WordPress themes by
 {{AUTHORSLUG}}".

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4550>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 12:55:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:55:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.24d29f79f5d0e43ce74996ce22898084@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+---------------------

Comment (by jonoaldersonwp):

 That's fine - these pages are still low value, and shouldn't be entry
 points into the site in their current condition. They're also competing
 with / conflicting with the author profile, and the theme itself.

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

From noreply at wordpress.org  Wed Jun 26 12:57:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 12:57:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4550: Improve the page title
 and meta descriptions of theme author archives
In-Reply-To: <058.a662a7455c0a1e13393e1630a0b618e9@wordpress.org>
References: <058.a662a7455c0a1e13393e1630a0b618e9@wordpress.org>
Message-ID: <073.38965d507b6185288b716eb6f5aa456c@wordpress.org>

#4550: Improve the page title and meta descriptions of theme author archives
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+---------------------
Description changed by jonoaldersonwp:

Old description:

> Theme author archives (such as
> https://wordpress.org/themes/author/dans7919/) currently have a title
> structure of `{{AUTHORSLUG}} | WordPress.org`.
>
> This should be changed to `Themes by {{AUTHORSLUG}} | WordPress.org`.
>
> The meta description should be changed to "See all WordPress themes by
> {{AUTHORSLUG}}".

New description:

 Theme author archives (such as
 https://wordpress.org/themes/author/dans7919/) currently have a title
 structure of `{{AUTHOR}} | WordPress.org`.

 This should be changed to `Themes by {{AUTHOR}} | WordPress.org`.

 The meta description should be changed to "See all WordPress themes
 developed by {{AUTHOR}}".

 We should always use the 'clean' version of the author name, rather than
 the slug. E.g., for https://wordpress.org/themes/author/d5creation/,
 that's `D5 Creation`, rather than `d5creation`.

--

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

From noreply at wordpress.org  Wed Jun 26 13:01:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 13:01:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4551: Tweak theme templates when
 no author exists
Message-ID: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>

#4551: Tweak theme templates when no author exists
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  Theme Review    |   Keywords:  seo
----------------------------+--------------------
 When there's no author for a theme, such as on
 https://wordpress.org/themes/simple-round/, the template should be adapted
 to remove the byline. Also applies on
 https://wordpress.org/themes/author/dans7919/ and also on search results.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4551>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 13:04:37 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 13:04:37 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
In-Reply-To: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
References: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
Message-ID: <073.d75d5f7a4729cad2f49f0dd3d3a7dab9@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
-------------------------------------------+----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  defect                         |      Status:  closed
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  fixed
 Keywords:  seo                            |
-------------------------------------------+----------------------

Comment (by SergeyBiryukov):

 Replying to [comment:3 jonoaldersonwp]:
 > If they can guarantee that those links will remain valid and up to date,
 that's fine. But, I'm sure that's what they thought originally, and it
 clearly wasn't the case.

 FWIW, the links in question were a small portion of the global Showcase
 and were only displayed as a fallback if a locale didn't have their own
 list of notable sites.

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

From noreply at wordpress.org  Wed Jun 26 13:05:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 13:05:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4533: Update & standardize
 broken/missing showcase links on homepage templates
In-Reply-To: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
References: <058.502da6f3001c2545560c82c43cacc386@wordpress.org>
Message-ID: <073.7e0620f8bbf2c634f105e07585631f21@wordpress.org>

#4533: Update & standardize broken/missing showcase links on homepage templates
-------------------------------------------+----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  defect                         |      Status:  closed
 Priority:  high                           |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  fixed
 Keywords:  seo                            |
-------------------------------------------+----------------------

Comment (by jonoaldersonwp):

 Ah, interesting! :)

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

From noreply at wordpress.org  Wed Jun 26 13:26:18 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 13:26:18 -0000
Subject: [wp-meta] [Making WordPress.org] #4552: Pages on
 archive.wordpress.org are missing Tag Manager
Message-ID: <058.5f0a455b91582eac128577482e8ab87b@wordpress.org>

#4552: Pages on archive.wordpress.org are missing Tag Manager
----------------------------+-----------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  General         |   Keywords:  analytics
----------------------------+-----------------------
 Add our Tag Manager script to all pages/templates on
 https://archive.wordpress.org/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4552>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 13:27:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 13:27:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4553: 301 redirect
 https://archive.wordpress.org/ to https://archive.wordpress.org/interviews/
Message-ID: <058.92656d96b257d645ae512945f1218667@wordpress.org>

#4553: 301 redirect https://archive.wordpress.org/ to
https://archive.wordpress.org/interviews/
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  lowest          |  Milestone:
Component:  General         |   Keywords:  seo
----------------------------+--------------------
 There's a dead page at the root, and, the only content which exists is in
 /interviews/.
 We should 301 the homepage to /interviews/.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4553>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 14:22:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 14:22:04 -0000
Subject: [wp-meta] [Making WordPress.org] #2207: GTEs should be able to
 mark PTE requests as resolved
In-Reply-To: <058.1b658b356ed77ce737eee3f8849b362c@wordpress.org>
References: <058.1b658b356ed77ce737eee3f8849b362c@wordpress.org>
Message-ID: <073.613630ab0dcb301e95693c98c170848b@wordpress.org>

#2207: GTEs should be able to mark PTE requests as resolved
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by SergeyBiryukov):

 Related: #3423

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

From noreply at wordpress.org  Wed Jun 26 14:22:14 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 14:22:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2207: GTEs should be able to
 mark PTE requests as resolved
In-Reply-To: <058.1b658b356ed77ce737eee3f8849b362c@wordpress.org>
References: <058.1b658b356ed77ce737eee3f8849b362c@wordpress.org>
Message-ID: <073.9533f38f9b72ed58650e7d50ba85609a@wordpress.org>

#2207: GTEs should be able to mark PTE requests as resolved
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by SergeyBiryukov):

 Related: https://make.wordpress.org/polyglots/2019/06/26/proposal-for-
 handling-pte-requests/

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

From noreply at wordpress.org  Wed Jun 26 21:07:19 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 21:07:19 -0000
Subject: [wp-meta] [Making WordPress.org] #4554: Formatting on canned trac
 reports
Message-ID: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>

#4554: Formatting on canned trac reports
--------------------+--------------------
 Reporter:  pbiron  |      Owner:  (none)
     Type:  defect  |     Status:  new
 Priority:  normal  |  Milestone:
Component:  Trac    |   Keywords:
--------------------+--------------------
 The canned trac reports (e.g.,
 [https://core.trac.wordpress.org/tickets/major Next Major Release]) seem
 to not be formatting correctly.

 In particular, the `h2.report-results, div.paging, table.listing.tickets`
 go full page width, whereas everything above them in constrained to have
 `max-width: 940px; margin-left: auto; margin-right: auto`.

 I don't remember those things being that wide in the past...maybe they
 have been.

 However, even if those 3 selectors are added to the CSS rule on line 219
 of [https://s.w.org/style/trac/wp-trac.css?118], the table still blows
 beyond the `940px`.

 Even if the table is supposed to be full width, it actually breaks on
 mobile (see screenshots to be added shortly).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4554>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 21:07:40 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 21:07:40 -0000
Subject: [wp-meta] [Making WordPress.org] #4554: Formatting on canned
 trac reports
In-Reply-To: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
References: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
Message-ID: <065.96fbfd39ca2e313c1319968b6d7893c9@wordpress.org>

#4554: Formatting on canned trac reports
--------------------+---------------------
 Reporter:  pbiron  |       Owner:  (none)
     Type:  defect  |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------
Changes (by pbiron):

 * Attachment "trac-report.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4554>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 21:08:09 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 21:08:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4554: Formatting on canned
 trac reports
In-Reply-To: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
References: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
Message-ID: <065.751be219415ba4d28c7ce5f25f1132f2@wordpress.org>

#4554: Formatting on canned trac reports
--------------------+---------------------
 Reporter:  pbiron  |       Owner:  (none)
     Type:  defect  |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------
Changes (by pbiron):

 * Attachment "trac-report-mobile.png" added.

 this in Chrome's "mobile preview" in the inspector.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4554>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 22:09:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 22:09:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
Message-ID: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+--------------------
 Reporter:  Ipstenu           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 We need an admin-only tool that will allow us to mass-email plugins.

 One exists but currently can only be run by a server admin, which limits
 usability.

 1) Provide a list of plugins

 2) Provide an email subject and body with basic substitutions

 3) The tool would then email everyone with commit access and listed owner
 the message

 Substitutions needed:

 %USER_EMAIL%
 %USER_DISPLAY_NAME%
 %PLUGIN_URL%

 With Helpscout you can pre-fill everything BUT the body:
 https://docs.helpscout.com/article/119-pre-fill

 So it doesn't look like we can use that for our bulk-mail tool.

 If it's secure and has the capability to be given a usable UX, whatever
 tool is used on the back-end should be fine.

 Limiting the number of plugins mailed at a time is also fine. Handling
 more than 50 of those at a stretch is usually pretty annoying anyway :)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4555>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Wed Jun 26 22:45:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 22:45:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4526: undercore missing
In-Reply-To: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>
References: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>
Message-ID: <064.5ad95aef11e5327006ddaf8c9f04760e@wordpress.org>

#4526: undercore missing
-----------------------+---------------------
 Reporter:  arena      |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  Handbooks  |  Resolution:
 Keywords:             |
-----------------------+---------------------
Changes (by SergeyBiryukov):

 * component:  General => Handbooks


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

From noreply at wordpress.org  Wed Jun 26 23:11:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 23:11:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4526: undercore missing
In-Reply-To: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>
References: <049.4e2a71240fc089d56d691cf72c063120@wordpress.org>
Message-ID: <064.139acbea328f40f52beeabf8a09cc1b9@wordpress.org>

#4526: undercore missing
-----------------------+------------------------
 Reporter:  arena      |       Owner:  (none)
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  Handbooks  |  Resolution:  duplicate
 Keywords:             |
-----------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Hi @arena, welcome to WordPress Meta Trac!

 Thanks for the report, we're already tracking this issue in #4400.

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

From noreply at wordpress.org  Wed Jun 26 23:12:14 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 23:12:14 -0000
Subject: [wp-meta] [Making WordPress.org] #4400: Monaco font on the
 handbook on Chromium doesn't show underscores at 100% size
In-Reply-To: <054.0247a9a103cd67cff733c8f6baccec03@wordpress.org>
References: <054.0247a9a103cd67cff733c8f6baccec03@wordpress.org>
Message-ID: <069.5f96bd880a7e4bd573081967e4c46554@wordpress.org>

#4400: Monaco font on the handbook on Chromium doesn't show underscores at 100%
size
------------------------+---------------------
 Reporter:  santilinwp  |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Handbooks   |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by SergeyBiryukov):

 Previously: #1928, #2378.

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

From noreply at wordpress.org  Wed Jun 26 23:35:01 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Jun 2019 23:35:01 +0000 (UTC)
Subject: [wp-meta] [8996]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main:
 WordPress.org Main Theme: Add Cookie Policy page to the privacy menu items.
Message-ID: <20190626233501.E34171B0046D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190626/966d7f51/attachment.html>

From noreply at wordpress.org  Wed Jun 26 23:35:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 23:35:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4527: Add the Cookie Policy
 to the privacy menu items.
In-Reply-To: <059.fe6b918d5e96b60a7223eb3ce1f3c268@wordpress.org>
References: <059.fe6b918d5e96b60a7223eb3ce1f3c268@wordpress.org>
Message-ID: <074.45b834765cd8dbbbb6b24cb19fc1152a@wordpress.org>

#4527: Add the Cookie Policy to the privacy menu items.
-----------------------------+-----------------------------
 Reporter:  garrett-eclipse  |       Owner:  SergeyBiryukov
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  fixed
 Keywords:                   |
-----------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8996" 8996]:
 {{{
 #!CommitTicketReference repository="" revision="8996"
 WordPress.org Main Theme: Add Cookie Policy page to the privacy menu
 items.

 Props garrett-eclipse.
 Fixes #4527.
 }}}

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

From noreply at wordpress.org  Wed Jun 26 23:43:59 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Jun 2019 23:43:59 +0000 (UTC)
Subject: [wp-meta] [8997]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-privacy.php:
 WordPress.org Main Theme: Privacy: Link to Data Export Request page from
 Privacy Policy.
Message-ID: <20190626234359.7CF601B0046D@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190626/179f7614/attachment.html>

From noreply at wordpress.org  Wed Jun 26 23:44:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 23:44:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4528: Provide Data Export
 Request link on the Privacy Policy 'Access to Data' section.
In-Reply-To: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
References: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
Message-ID: <074.4df29f7ee3bcea68882d03c61f5f7359@wordpress.org>

#4528: Provide Data Export Request link on the Privacy Policy 'Access to Data'
section.
-----------------------------+-----------------------------
 Reporter:  garrett-eclipse  |       Owner:  SergeyBiryukov
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  fixed
 Keywords:                   |
-----------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8997" 8997]:
 {{{
 #!CommitTicketReference repository="" revision="8997"
 WordPress.org Main Theme: Privacy: Link to Data Export Request page from
 Privacy Policy.

 Props garrett-eclipse.
 Fixes #4528. See #4223.
 }}}

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

From noreply at wordpress.org  Wed Jun 26 23:44:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 23:44:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4223: Can we link the Data
 Erasure Request form/page into the Privacy Policy
In-Reply-To: <059.6fe749683cc2fd520d472422b3bb2c95@wordpress.org>
References: <059.6fe749683cc2fd520d472422b3bb2c95@wordpress.org>
Message-ID: <074.fb40acd17c5a9e7831274c82d27adfe3@wordpress.org>

#4223: Can we link the Data Erasure Request form/page into the Privacy Policy
-----------------------------+-----------------------------
 Reporter:  garrett-eclipse  |       Owner:  SergeyBiryukov
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  fixed
 Keywords:                   |
-----------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [changeset:"8997" 8997]:
 {{{
 #!CommitTicketReference repository="" revision="8997"
 WordPress.org Main Theme: Privacy: Link to Data Export Request page from
 Privacy Policy.

 Props garrett-eclipse.
 Fixes #4528. See #4223.
 }}}

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

From noreply at wordpress.org  Wed Jun 26 23:59:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Jun 2019 23:59:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4551: Tweak theme templates
 when no author exists
In-Reply-To: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>
References: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>
Message-ID: <073.663a4656bccfcec2225ce66dfbb6656b@wordpress.org>

#4551: Tweak theme templates when no author exists
-----------------------------+---------------------
 Reporter:  jonoaldersonwp   |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  lowest           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+---------------------
Changes (by SergeyBiryukov):

 * component:  Theme Review => Theme Directory


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

From noreply at wordpress.org  Thu Jun 27 00:14:56 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 27 Jun 2019 00:14:56 +0000 (UTC)
Subject: [wp-meta] [8998]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes:
 Theme Directory: Don't display the byline if theme author's display name is
 empty.
Message-ID: <20190627001456.CD3481B004B6@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190627/5f90b428/attachment.html>

From noreply at wordpress.org  Thu Jun 27 00:14:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 00:14:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4551: Tweak theme templates
 when no author exists
In-Reply-To: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>
References: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>
Message-ID: <073.7255a3f3629cb806776cd6c20052b520@wordpress.org>

#4551: Tweak theme templates when no author exists
-----------------------------+-----------------------------
 Reporter:  jonoaldersonwp   |       Owner:  SergeyBiryukov
     Type:  defect           |      Status:  closed
 Priority:  lowest           |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:  seo              |
-----------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8998" 8998]:
 {{{
 #!CommitTicketReference repository="" revision="8998"
 Theme Directory: Don't display the byline if theme author's display name
 is empty.

 Props jonoaldersonwp.
 Fixes #4551.
 }}}

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

From noreply at wordpress.org  Thu Jun 27 00:18:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 00:18:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4554: Formatting on canned
 trac reports
In-Reply-To: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
References: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
Message-ID: <065.1abaf282dca20b4b64506cc13d67cc64@wordpress.org>

#4554: Formatting on canned trac reports
--------------------+---------------------
 Reporter:  pbiron  |       Owner:  (none)
     Type:  defect  |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by SergeyBiryukov):

 > Even if the table is supposed to be full width, it actually breaks on
 mobile (see screenshots to be added shortly).

 IIRC, the table is indeed supposed to be full width. We could try to
 improve the mobile styling though.

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

From noreply at wordpress.org  Thu Jun 27 04:50:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 04:50:55 -0000
Subject: [wp-meta] [Making WordPress.org] #3318: Change two sentences on
 wordpress.org/
In-Reply-To: <055.f2c1a95096fcf6cd25a30678968add81@wordpress.org>
References: <055.f2c1a95096fcf6cd25a30678968add81@wordpress.org>
Message-ID: <070.025d2e0017321cf3a16a9ccc6c82296a@wordpress.org>

#3318: Change two sentences on wordpress.org/
-----------------------------------------+--------------------------------
 Reporter:  IkusiMakusi                  |       Owner:  (none)
     Type:  enhancement                  |      Status:  closed
 Priority:  normal                       |   Milestone:
Component:  General                      |  Resolution:  reported-upstream
 Keywords:  has-patch reporter-feedback  |
-----------------------------------------+--------------------------------
Changes (by tellyworth):

 * status:  reopened => closed
 * resolution:   => reported-upstream


Comment:

 I'm referring this to the marketing team, since decisions about this kind
 of English copy is in their purview and not in ours.

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

From noreply at wordpress.org  Thu Jun 27 05:21:32 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 05:21:32 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.58f3433cf8e6f35584e82521f659d33f@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+-----------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


Comment:

 If we're going to noindex author archives pages, we'll have to do it for
 every author - not just based on the number of themes.

 I can understand why these pages aren't high value in the search index, so
 I'm okay with noindexing them, but I expect others will disagree with
 that.  We should probably make Themes/Plugins more prominent on the
 Profiles page instead though.

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

From noreply at wordpress.org  Thu Jun 27 05:28:15 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 05:28:15 -0000
Subject: [wp-meta] [Making WordPress.org] #4553: 301 redirect
 https://archive.wordpress.org/ to https://archive.wordpress.org/interviews/
In-Reply-To: <058.92656d96b257d645ae512945f1218667@wordpress.org>
References: <058.92656d96b257d645ae512945f1218667@wordpress.org>
Message-ID: <073.66761907541370ea9fecc772e79d138d@wordpress.org>

#4553: 301 redirect https://archive.wordpress.org/ to
https://archive.wordpress.org/interviews/
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  General         |  Resolution:
 Keywords:  seo close       |
----------------------------+---------------------
Changes (by dd32):

 * keywords:  seo => seo close


Comment:

 I believe the intention is that it'll have other content in the future,
 and it's deliberately not linked at present.

 IMHO this is a wontfix.

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

From noreply at wordpress.org  Thu Jun 27 06:35:15 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 27 Jun 2019 06:35:15 +0000 (UTC)
Subject: [wp-meta] [8999]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/theme-directory/class-themes-api.php:
 Theme Directory: When a users `display_name` is blank (historical
 reasons..) fall back to the user nicename.
Message-ID: <20190627063515.2DCB51B00450@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190627/fc95a8d7/attachment.html>

From noreply at wordpress.org  Thu Jun 27 06:35:17 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:35:17 -0000
Subject: [wp-meta] [Making WordPress.org] #4551: Tweak theme templates
 when no author exists
In-Reply-To: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>
References: <058.a96acff6cbeb702c43d0ac713549eece@wordpress.org>
Message-ID: <073.dd467771cf481c7c1aa302ab17a42a19@wordpress.org>

#4551: Tweak theme templates when no author exists
-----------------------------+-----------------------------
 Reporter:  jonoaldersonwp   |       Owner:  SergeyBiryukov
     Type:  defect           |      Status:  closed
 Priority:  lowest           |   Milestone:
Component:  Theme Directory  |  Resolution:  fixed
 Keywords:  seo              |
-----------------------------+-----------------------------

Comment (by dd32):

 In [changeset:"8999" 8999]:
 {{{
 #!CommitTicketReference repository="" revision="8999"
 Theme Directory: When a users `display_name` is blank (historical
 reasons..) fall back to the user nicename.

 Fixes #4551.
 }}}

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

From noreply at wordpress.org  Thu Jun 27 06:46:21 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:46:21 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.9bcc9d0e629789dabfc41c7d333f08d7@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------
Changes (by ocean90):

 * Attachment "4518-ui-ideas.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4518>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 06:46:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:46:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.22e7214de60542f72a4855ffa537d6d7@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------
Changes (by ocean90):

 * Attachment "4518-ui-ideas-1.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4518>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 06:47:17 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:47:17 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.997a4512a7b7f9513ec1326c155544fb@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------
Changes (by ocean90):

 * Attachment "4518-ui-ideas-2.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4518>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 06:47:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:47:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.0d0bbbd3d5abecfe6f3c79796bca3ac5@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------
Changes (by ocean90):

 * Attachment "4518-ui-ideas-3.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4518>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 06:47:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:47:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4518: Plan: translation
 discussions/feedback
In-Reply-To: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
References: <049.5d9208ef4d30ba740a0a32ac40dc6a7c@wordpress.org>
Message-ID: <064.092944bcd89c7b2e2678e71e6af24c3f@wordpress.org>

#4518: Plan: translation discussions/feedback
--------------------------------------+---------------------
 Reporter:  yoavf                     |       Owner:  (none)
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  needs-patch needs-design  |
--------------------------------------+---------------------
Changes (by ocean90):

 * Attachment "4518-ui-ideas-4.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4518>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 06:50:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 06:50:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4528: Provide Data Export
 Request link on the Privacy Policy 'Access to Data' section.
In-Reply-To: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
References: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
Message-ID: <074.46a4e1d2fc8f3361be727b73860475db@wordpress.org>

#4528: Provide Data Export Request link on the Privacy Policy 'Access to Data'
section.
-----------------------------+-----------------------------
 Reporter:  garrett-eclipse  |       Owner:  SergeyBiryukov
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  fixed
 Keywords:                   |
-----------------------------+-----------------------------

Comment (by tellyworth):

 @garrett-eclipse What's the reason for adding the `Note: If you have a
 WP.org account..` text? Is it there because of the double reCaptcha?

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

From noreply at wordpress.org  Thu Jun 27 07:22:22 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 07:22:22 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.92e07f1b88d038f1e56ee6be6328fc19@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+-----------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+-----------------------

Comment (by jonoaldersonwp):

 I don't agree that we need some kind of artificial rule on which is
 indexed and isn't because 'fariness'; that feels a bit silly.

 That said, I'd be equally happy if we noindex'd all of them, and, also
 came up with a way to include/reference them on Profile pages.

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

From noreply at wordpress.org  Thu Jun 27 07:23:08 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 07:23:08 -0000
Subject: [wp-meta] [Making WordPress.org] #4553: 301 redirect
 https://archive.wordpress.org/ to https://archive.wordpress.org/interviews/
In-Reply-To: <058.92656d96b257d645ae512945f1218667@wordpress.org>
References: <058.92656d96b257d645ae512945f1218667@wordpress.org>
Message-ID: <073.c543749782578de4bde62b5032762374@wordpress.org>

#4553: 301 redirect https://archive.wordpress.org/ to
https://archive.wordpress.org/interviews/
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  General         |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------
Changes (by jonoaldersonwp):

 * keywords:  seo close => seo


Comment:

 We can remove the 301 if/when is has content.

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

From noreply at wordpress.org  Thu Jun 27 07:31:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 07:31:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.b0a938958fb8e6801ab65b9978e91bbc@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+-----------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:4 jonoaldersonwp]:
 > I don't agree that we need some kind of artificial rule on which is
 indexed and isn't because 'fariness'; that feels a bit silly.

 While it is in the spirit of fairness, if a "thin" theme author archive
 isn't worth having as a search result then realistically none of them
 really are.
 With >= 3, we'd be dropping 80% of the archives already, so keeping the
 remaining 20% doesn't seem like it'll be of much benefit to end-users as
 it's more likely than not, that the author they're looking for won't be
 listed.

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

From noreply at wordpress.org  Thu Jun 27 07:33:07 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 07:33:07 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.89f1fff52dd6a0a6b0d69bd92c79ff2c@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+-----------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+-----------------------

Comment (by jonoaldersonwp):

 Agreed, let's noindex them all :)

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

From noreply at wordpress.org  Thu Jun 27 07:34:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 07:34:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4549: Noindex'ing thin theme
 author indexes
In-Reply-To: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
References: <058.e01f2e94ec2eff5e6eb63bac2fc6429d@wordpress.org>
Message-ID: <073.3b98e69e046fdf1f6ffd6ba125afbc4f@wordpress.org>

#4549: Noindex'ing thin theme author indexes
-----------------------------+-----------------------
 Reporter:  jonoaldersonwp   |       Owner:  dd32
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:  seo              |
-----------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:4 jonoaldersonwp]:
 > That said, I'd be equally happy if we noindex'd all of them, and, also
 came up with a way to include/reference them on Profile pages.

 FWIW that already exists: https://profiles.wordpress.org/wordpressdotorg
 /#content-themes
 It's just a bit buried unless linked to directly..

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

From noreply at wordpress.org  Thu Jun 27 09:22:31 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 09:22:31 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
In-Reply-To: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
References: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
Message-ID: <070.a52f9fae802a03c7b6952bdaaf749a60@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+---------------------
 Reporter:  Travel_girl       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------
Changes (by tellyworth):

 * Attachment "4519.diff" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4519>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 09:26:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 09:26:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
In-Reply-To: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
References: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
Message-ID: <070.0c708c04d02a7990c73fcd6f80eb3db6@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+-------------------------
 Reporter:  Travel_girl       |       Owner:  tellyworth
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+-------------------------
Changes (by tellyworth):

 * keywords:  needs-patch => has-patch
 * owner:  (none) => tellyworth
 * status:  new => assigned


Comment:

 attachment:4519.diff implements more or less what inclusive-components
 suggests. For example:


 {{{
 <dt id="#%0Ahow%20do%20i%20manage%20my%20products%3F%0A" class="" aria-
 expanded="false">
   <h3>
     <button formaction="#%0Ahow%20do%20i%20manage%20my%20products%3F%0A">
 How do I manage my products?</button>
   </h3>
 </dt>
 <dd>
   ...
 </dd>
 }}}

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

From noreply at wordpress.org  Thu Jun 27 09:46:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 09:46:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4519: Make the FAQ at plugin
 directory accessible
In-Reply-To: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
References: <055.6073b066674db2e2ad2033ed2bd9e20d@wordpress.org>
Message-ID: <070.3935853f83d3fd9d46f87ff499318c2e@wordpress.org>

#4519: Make the FAQ at plugin directory accessible
------------------------------+-------------------------
 Reporter:  Travel_girl       |       Owner:  tellyworth
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+-------------------------

Comment (by Travel_girl):

 Looks good to me! Thanks for your work!

 Replying to [comment:4 tellyworth]:
 > attachment:4519.diff implements more or less what inclusive-components
 suggests. For example:
 >
 >
 > {{{
 > <dt id="#%0Ahow%20do%20i%20manage%20my%20products%3F%0A" class="" aria-
 expanded="false">
 >   <h3>
 >     <button
 formaction="#%0Ahow%20do%20i%20manage%20my%20products%3F%0A">
 > How do I manage my products?</button>
 >   </h3>
 > </dt>
 > <dd>
 >   ...
 > </dd>
 > }}}

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

From noreply at wordpress.org  Thu Jun 27 14:43:42 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 14:43:42 -0000
Subject: [wp-meta] [Making WordPress.org] #4556: Prevent bots from crawling
 filtered URLs on translate
Message-ID: <058.57cbe0e573180cdd84e8358f72f92e15@wordpress.org>

#4556: Prevent bots from crawling filtered URLs on translate
--------------------------------------+--------------------
 Reporter:  jonoaldersonwp            |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  low                       |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:  seo
--------------------------------------+--------------------
 Add the following to the robots.txt file on translate.wordpress.org:

 Disallow: /?filters

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4556>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Thu Jun 27 23:09:25 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Jun 2019 23:09:25 -0000
Subject: [wp-meta] [Making WordPress.org] #4557: Gutenberg Documentation
 Redirect
Message-ID: <048.33fed83cc547d3dcdd82db7ce15645c3@wordpress.org>

#4557: Gutenberg Documentation Redirect
--------------------------------------+-------------------------
 Reporter:  mkaz                      |      Owner:  coffee2code
     Type:  defect                    |     Status:  assigned
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+-------------------------
 There are empty Gutenberg documentation pages at:
 https://make.wordpress.org/docs/handbook/gutenberg/

 Can we get those pages to redirect to the Block Editor Handbook here:
 https://developer.wordpress.org/block-editor/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4557>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 02:04:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:04:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4556: Prevent bots from
 crawling filtered URLs on translate
In-Reply-To: <058.57cbe0e573180cdd84e8358f72f92e15@wordpress.org>
References: <058.57cbe0e573180cdd84e8358f72f92e15@wordpress.org>
Message-ID: <073.cc53f8a3b4b75d6e786a7d1ae2846399@wordpress.org>

#4556: Prevent bots from crawling filtered URLs on translate
--------------------------------------+---------------------
 Reporter:  jonoaldersonwp            |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  seo                       |
--------------------------------------+---------------------

Comment (by tellyworth):

 We use a global robots.txt so this has to be done everywhere, but I think
 that's fine.

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

From noreply at wordpress.org  Fri Jun 28 02:07:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:07:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4556: Prevent bots from
 crawling filtered URLs on translate
In-Reply-To: <058.57cbe0e573180cdd84e8358f72f92e15@wordpress.org>
References: <058.57cbe0e573180cdd84e8358f72f92e15@wordpress.org>
Message-ID: <073.f57094c56fd86a1ccc7329f5295f13f2@wordpress.org>

#4556: Prevent bots from crawling filtered URLs on translate
--------------------------------------+---------------------
 Reporter:  jonoaldersonwp            |       Owner:  (none)
     Type:  defect                    |      Status:  closed
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  fixed
 Keywords:  seo                       |
--------------------------------------+---------------------
Changes (by tellyworth):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in dotorg r15179.

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

From noreply at wordpress.org  Fri Jun 28 02:10:34 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:10:34 -0000
Subject: [wp-meta] [Making WordPress.org] #4557: Gutenberg Documentation
 Redirect
In-Reply-To: <048.33fed83cc547d3dcdd82db7ce15645c3@wordpress.org>
References: <048.33fed83cc547d3dcdd82db7ce15645c3@wordpress.org>
Message-ID: <063.2be6e3a5887664806a26086b7bf96b2f@wordpress.org>

#4557: Gutenberg Documentation Redirect
--------------------------------------+--------------------------
 Reporter:  mkaz                      |       Owner:  coffee2code
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+--------------------------
Changes (by dd32):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 I've unpublished the Gutenberg draft pages that were empty, but I don't
 think a redirect is appropriate here.

 The pages are the Docs team handbook on how to contribute to the various
 documentation efforts that exist on WordPress.org.

 I've updated the base Gutenberg docs page there to be a bit more relevant
 and to link to the correct pages:
 https://make.wordpress.org/docs/handbook/gutenberg/

 I think that's probably enough to fix here.

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

From noreply at wordpress.org  Fri Jun 28 02:19:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:19:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4554: Formatting on canned
 trac reports
In-Reply-To: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
References: <050.b2b8c2c682b79bf7efe90dcf1eff62cd@wordpress.org>
Message-ID: <065.5883b1dd7553ade82b4870f3f7ec8c9d@wordpress.org>

#4554: Formatting on canned trac reports
--------------------+---------------------
 Reporter:  pbiron  |       Owner:  (none)
     Type:  defect  |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:  close   |
--------------------+---------------------
Changes (by tellyworth):

 * keywords:   => close


Comment:

 Even if we fix the styling, there's too much info on that page for it to
 ever really be mobile friendly. Is there anything we can do here that has
 enough benefit to be worth spending time on it?

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

From noreply at wordpress.org  Fri Jun 28 02:22:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:22:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
In-Reply-To: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
References: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
Message-ID: <066.f58a689d78dc36352625d28ecc70317b@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


Comment:

 HelpScout does have an API to allow us to create an email in HelpScout, so
 we could easily push the emails through there.

 Would it be helpful to have a record of the email being sent in HS? or
 should it just be sent directly by the WordPress.org servers, with the
 replies hitting HS?

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

From noreply at wordpress.org  Fri Jun 28 02:28:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:28:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
In-Reply-To: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
References: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
Message-ID: <066.e8a89f5d3992936afee54d1f06335e00@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by Ipstenu):

 Having a record of the email sent via Help Scout would help since
 sometimes people don't reply from the email we have on record, but Help
 Scout keeps them properly threaded so if they remove the body of what
 they're replying to, we can still see it (and figure out what 'my
 plugin!!!!' means a little faster)

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

From noreply at wordpress.org  Fri Jun 28 02:32:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:32:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
In-Reply-To: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
References: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
Message-ID: <066.4c71b0e8781701e24f3ca3ae21a925dc@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:3 Ipstenu]:
 > Having a record of the email sent via Help Scout would help since
 sometimes people don't reply from the email we have on record, but Help
 Scout keeps them properly threaded so if they remove the body of what
 they're replying to, we can still see it (and figure out what 'my
 plugin!!!!' means a little faster)

 That sounds like a great reason to push the sent emails into HS then!

 If we're limiting it to small batches of plugins then we shouldn't have
 any real scale problems here I don't think.

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

From noreply at wordpress.org  Fri Jun 28 02:42:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:42:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4530: Adding missing profile
 badges
In-Reply-To: <050.e99569106133ddd02d31257063a8f346@wordpress.org>
References: <050.e99569106133ddd02d31257063a8f346@wordpress.org>
Message-ID: <065.092cb2073495b9b327c349611898e71e@wordpress.org>

#4530: Adding missing profile badges
----------------------+-----------------------
 Reporter:  stubgo    |       Owner:  dd32
     Type:  task      |      Status:  accepted
 Priority:  low       |   Milestone:
Component:  Profiles  |  Resolution:
 Keywords:            |
----------------------+-----------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => accepted


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

From noreply at wordpress.org  Fri Jun 28 02:43:56 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:43:56 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.c5b499dba43d211840ccbb1ea88c8f32@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+-------------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  closed
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:  maybelater
 Keywords:                        |
----------------------------------+-------------------------
Changes (by tellyworth):

 * status:  new => closed
 * resolution:   => maybelater


Comment:

 If this was a feature of bbPress, or a readily available plugin, we could
 consider trying it out. Otherwise I think it's too controversial to
 consider spending resources on it. I'll close this ticket as `maybelater`;
 if you're able to find support for it either in bbPress core or a plugin
 then feel free to re-open and we'll take a closer look.

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

From noreply at wordpress.org  Fri Jun 28 02:58:57 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 02:58:57 -0000
Subject: [wp-meta] [Making WordPress.org] #4525: Add insights to the
 plugin language packs page
In-Reply-To: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
References: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
Message-ID: <064.6929fb44f99181394ecc3cfbdb8e4cdf@wordpress.org>

#4525: Add insights to the plugin language packs page
--------------------------------------+---------------------
 Reporter:  ramiy                     |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion needs-patch   |
--------------------------------------+---------------------

Comment (by tellyworth):

 What is the problem that this is intended to solve? How would a plugin
 author make use of this data? What would it enable them to do?

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

From noreply at wordpress.org  Fri Jun 28 03:27:28 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 03:27:28 -0000
Subject: [wp-meta] [Making WordPress.org] #4521: Broken link in the
 plugin handbook sidebar
In-Reply-To: <055.aa69d2ba3a9fdd7018283d0d35897d2b@wordpress.org>
References: <055.aa69d2ba3a9fdd7018283d0d35897d2b@wordpress.org>
Message-ID: <070.c5ad4e3ef5ded6ef04f9b81db990e8b2@wordpress.org>

#4521: Broken link in the plugin handbook sidebar
-------------------------+---------------------
 Reporter:  hofmannsven  |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:  needs-patch  |
-------------------------+---------------------
Changes (by dd32):

 * keywords:  close => needs-patch


Comment:

 Apparently when someone who doesn't have `publish_posts` edits the
 `publish`'d documents the post reverts to `pending`.

 It somewhat sounds like a user-role has `edit_published_posts` but not
 `publish_posts` and causes that..

 My thought is that the handbook pages should remain published if a non-
 privledged user edits them, but others have informed me that ideally it'd
 not make their edits public until review (which seems to be what's
 happening now).

 First step seems to be to trust users who have edit access, and keep the
 pages published. Second step sounds like it's to add an editorial plugin
 that lets you put future changes into a review queue.

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

From noreply at wordpress.org  Fri Jun 28 03:28:47 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 03:28:47 -0000
Subject: [wp-meta] [Making WordPress.org] #4557: Gutenberg Documentation
 Redirect
In-Reply-To: <048.33fed83cc547d3dcdd82db7ce15645c3@wordpress.org>
References: <048.33fed83cc547d3dcdd82db7ce15645c3@wordpress.org>
Message-ID: <063.523f71a1a5dce78ae3ec775e636631d5@wordpress.org>

#4557: Gutenberg Documentation Redirect
--------------------------------------+--------------------------
 Reporter:  mkaz                      |       Owner:  coffee2code
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+--------------------------

Comment (by mkaz):

 Looks good, works for me.
 Thanks!

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

From noreply at wordpress.org  Fri Jun 28 05:02:09 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 05:02:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4541: Change the title
 formatting on Profile templates
In-Reply-To: <058.e64a1beeece9d98e2899e4d046edf0f7@wordpress.org>
References: <058.e64a1beeece9d98e2899e4d046edf0f7@wordpress.org>
Message-ID: <073.4dbb19eb216f82197888dbf18ffb70e3@wordpress.org>

#4541: Change the title formatting on Profile templates
----------------------------+--------------------------
 Reporter:  jonoaldersonwp  |       Owner:  coffee2code
     Type:  defect          |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:  seo             |
----------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => accepted


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

From noreply at wordpress.org  Fri Jun 28 05:03:37 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 28 Jun 2019 05:03:37 +0000 (UTC)
Subject: [wp-meta] [9000]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-developer/inc/search.php:
 Developer: Output meta tag to prevent indexing of search results pages.
Message-ID: <20190628050337.7EDDE1B0055A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190628/cc7e7fe0/attachment-0001.html>

From noreply at wordpress.org  Fri Jun 28 05:03:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 05:03:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4540: Noindex search results
 pages in the block editor handbook
In-Reply-To: <058.0cd9f3827395176ad1ca4c48e7f403f6@wordpress.org>
References: <058.0cd9f3827395176ad1ca4c48e7f403f6@wordpress.org>
Message-ID: <073.ec7c2118e073bb47a69987c9b1e8f330@wordpress.org>

#4540: Noindex search results pages in the block editor handbook
----------------------------+--------------------------
 Reporter:  jonoaldersonwp  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  lowest          |   Milestone:
Component:  Developer Hub   |  Resolution:  fixed
 Keywords:  seo             |
----------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"9000" 9000]:
 {{{
 #!CommitTicketReference repository="" revision="9000"
 Developer: Output meta tag to prevent indexing of search results pages.

 Props jonoaldersonwp, coffee2code.
 Fixes #4540.
 }}}

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

From noreply at wordpress.org  Fri Jun 28 05:04:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 05:04:59 -0000
Subject: [wp-meta] [Making WordPress.org] #4540: Noindex search results
 pages in the block editor handbook
In-Reply-To: <058.0cd9f3827395176ad1ca4c48e7f403f6@wordpress.org>
References: <058.0cd9f3827395176ad1ca4c48e7f403f6@wordpress.org>
Message-ID: <073.4a7179a4fe2bf6f7022842e48de07797@wordpress.org>

#4540: Noindex search results pages in the block editor handbook
----------------------------+--------------------------
 Reporter:  jonoaldersonwp  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  lowest          |   Milestone:
Component:  Developer Hub   |  Resolution:  fixed
 Keywords:  seo             |
----------------------------+--------------------------

Comment (by coffee2code):

 FYI: I've applied this to all search results for !DevHub, not just for the
 Block Editor handbook.

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

From noreply at wordpress.org  Fri Jun 28 05:06:08 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 28 Jun 2019 05:06:08 +0000 (UTC)
Subject: [wp-meta] [9001]
 sites/trunk/api.wordpress.org/public_html/core/credits/shortcode.php:
 Credits: Add trailing slash to profiles URLs produced by the `wpcredits`
 shortcode.
Message-ID: <20190628050608.DE07C1B0055A@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190628/00576d21/attachment.html>

From noreply at wordpress.org  Fri Jun 28 05:06:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 05:06:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4542: Contributor references
 in news/announcement posts should have a trailing slash
In-Reply-To: <058.9c4e11908e9e897a181a4718583413ba@wordpress.org>
References: <058.9c4e11908e9e897a181a4718583413ba@wordpress.org>
Message-ID: <073.06831df7b99ca9f1e66dc77be1c4f942@wordpress.org>

#4542: Contributor references in news/announcement posts should have a trailing
slash
----------------------------+--------------------------
 Reporter:  jonoaldersonwp  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  lowest          |   Milestone:
Component:  General         |  Resolution:  fixed
 Keywords:  seo             |
----------------------------+--------------------------
Changes (by coffee2code):

 * owner:  (none) => coffee2code
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"9001" 9001]:
 {{{
 #!CommitTicketReference repository="" revision="9001"
 Credits: Add trailing slash to profiles URLs produced by the `wpcredits`
 shortcode.

 Props jonoaldersonwp, coffee2code.
 Fixes #4542.
 }}}

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

From noreply at wordpress.org  Fri Jun 28 05:10:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 05:10:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4541: Change the title
 formatting on Profile templates
In-Reply-To: <058.e64a1beeece9d98e2899e4d046edf0f7@wordpress.org>
References: <058.e64a1beeece9d98e2899e4d046edf0f7@wordpress.org>
Message-ID: <073.aac9ccc3e1b20d8d7aa0e9a2cb89d015@wordpress.org>

#4541: Change the title formatting on Profile templates
----------------------------+--------------------------
 Reporter:  jonoaldersonwp  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:  fixed
 Keywords:  seo             |
----------------------------+--------------------------
Changes (by coffee2code):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 Fixed in [dotorg-15176].

 I superseded the differing recommendation you made for profile document
 titles in #4277 by using this ticket's recommendation.

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

From noreply at wordpress.org  Fri Jun 28 05:10:22 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 05:10:22 -0000
Subject: [wp-meta] [Making WordPress.org] #4503: Incorrect
 capitalization of nicename not corrected in user profile links
In-Reply-To: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>
References: <051.2b098cc549bd7ae056274b6aadb276bf@wordpress.org>
Message-ID: <066.3bcdd8f9099bc8b4e753790d7786e0b3@wordpress.org>

#4503: Incorrect capitalization of nicename not corrected in user profile links
----------------------+--------------------------
 Reporter:  casiepa   |       Owner:  coffee2code
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:  fixed
 Keywords:            |
----------------------+--------------------------
Changes (by coffee2code):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 Fixed in [dotorg-15175].

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

From noreply at wordpress.org  Fri Jun 28 06:33:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 06:33:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4525: Add insights to the
 plugin language packs page
In-Reply-To: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
References: <049.21b326687172f3562e74e26ad7c9ed49@wordpress.org>
Message-ID: <064.50701365567d47f476712470535e90ef@wordpress.org>

#4525: Add insights to the plugin language packs page
--------------------------------------+---------------------
 Reporter:  ramiy                     |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion has-patch     |
--------------------------------------+---------------------
Changes (by ramiy):

 * keywords:  2nd-opinion needs-patch => 2nd-opinion has-patch


Comment:

 @tellyworth Good questions! here are the answers:

 **What is the problem that this is intended to solve?**

 Currently a plugin author don't really know how many of his language packs
 are update to the latest version. Unless he manually extracts the data
 from the language packs list - counting them one by one.

 **How would a plugin author make use of this data?**

 With this data, plugin authors can decide whether to focus resources on
 translations. For example if over 95% of my language packs are updated to
 the latest version I will do nothing, but if only 40% of the language
 packs are updated to the latest version I will spend time translating my
 plugin or hire someone to do that.

 **What would it enable them to do?**

 Insights is the first step for better decision making. I'm sorry to say,
 but the language pack list is a useless list of raw data. A single pie
 chart provides a better visual representation of the data.

 If you want to allow the plugin author do something on the page, we can
 replace the list with a table with sortable columns. It will be much
 easier to detect language packs for older version.

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

From noreply at wordpress.org  Fri Jun 28 06:36:49 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 06:36:49 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.1f25489d7859e3c4403e76802fc126f9@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+-------------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  closed
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:  maybelater
 Keywords:                        |
----------------------------------+-------------------------

Comment (by casiepa):

 This one used to work on bbPress if I remember well, but not tested in the
 last years: https://wordpress.org/plugins/super-emoji-plus/

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

From noreply at wordpress.org  Fri Jun 28 06:49:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 06:49:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.c7b05aac6a257dc7732f27630baee013@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+-------------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  closed
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:  maybelater
 Keywords:                        |
----------------------------------+-------------------------

Comment (by netweb):

 Replying to [comment:7 casiepa]:
 > This one used to work on bbPress if I remember well, but not tested in
 the last years: https://wordpress.org/plugins/super-emoji-plus/

 Thanks, that plugin allows an “emoji picker” to select an ''emoji'' to add
 to the post content inline, which would work with bbPress, but it’s not
 like the GitHub ''voting'' buttons where a limited selection of ''emoji''
 are available to use as a ''voting'' mechanism by users to vote on topic
 or replies.

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

From noreply at wordpress.org  Fri Jun 28 06:50:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 06:50:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.c33bf7b59194e94b42e13eaf7b1fb910@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+-------------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  closed
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:  maybelater
 Keywords:                        |
----------------------------------+-------------------------

Comment (by casiepa):

 Ah, ok, so then more something like:
 https://wordpress.org/plugins/bbpress-votes/
 https://wordpress.org/plugins/wp-ulike/
 ?

 Replying to [comment:8 netweb]:
 > Replying to [comment:7 casiepa]:
 > > This one used to work on bbPress if I remember well, but not tested in
 the last years: https://wordpress.org/plugins/super-emoji-plus/
 >
 > Thanks, that plugin allows an “emoji picker” to select an ''emoji'' to
 add to the post content inline, which would work with bbPress, but it’s
 not like the GitHub ''voting'' buttons where a limited selection of
 ''emoji'' are available to use as a ''voting'' mechanism by users to vote
 on topic or replies.

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

From noreply at wordpress.org  Fri Jun 28 07:00:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 07:00:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4558: Add details summary block
 to the Theme Review sites
Message-ID: <051.eb2de732b33561ec94ede255a62462cc@wordpress.org>

#4558: Add details summary block to the Theme Review sites
--------------------------+----------------------
 Reporter:  dingo_d       |      Owner:  dd32
     Type:  enhancement   |     Status:  assigned
 Priority:  high          |  Milestone:
Component:  Theme Review  |   Keywords:
--------------------------+----------------------
 I've created a block for creating a `<details>` markup which will allow us
 to add code examples on the theme review handbook without creating a mess
 of that page.

 The plugin is located here: https://wordpress.org/plugins/details-summary-
 block/

 If you can install it to the sites that would be awesome :)

 Thanks

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4558>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 07:01:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 07:01:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4529: Reactions on Support
 Forum Replies
In-Reply-To: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
References: <064.7741790016fbe44060cad7e6c2ce557d@wordpress.org>
Message-ID: <079.7bd84ec801c17f8f99b754d6dc0252ec@wordpress.org>

#4529: Reactions on Support Forum Replies
----------------------------------+-------------------------
 Reporter:  felipeloureirosantos  |       Owner:  (none)
     Type:  enhancement           |      Status:  closed
 Priority:  normal                |   Milestone:
Component:  Support Forums        |  Resolution:  maybelater
 Keywords:                        |
----------------------------------+-------------------------

Comment (by netweb):

 Replying to [comment:9 casiepa]:
 > Ah, ok, so then more something like:
 > https://wordpress.org/plugins/bbpress-votes/

 Thanks, again, no, this plugin adds a numeric ''vote counter'' to each
 topic or reply rather than emoji reactions

 Replying to [comment:9 casiepa]:
 > https://wordpress.org/plugins/wp-ulike/

 This is close, but it is doing far too much ''other'' stuff for
 consideration on w.org

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

From noreply at wordpress.org  Fri Jun 28 09:35:23 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 09:35:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3791: Consider bumping
 pre-commit checker on plugins to PHP 7.1
In-Reply-To: <051.a649e8525280ac88e3ba1f38f27d5c23@wordpress.org>
References: <051.a649e8525280ac88e3ba1f38f27d5c23@wordpress.org>
Message-ID: <066.6323e2222e1bb75f801be5705352a2d1@wordpress.org>

#3791: Consider bumping pre-commit checker on plugins to PHP 7.1
------------------------------+---------------------
 Reporter:  Ipstenu           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  pending-systems   |
------------------------------+---------------------

Comment (by jvanhengeldationnl):

 Same here. Checking in our plugin is blocked for all our libraries use
 7.1+.

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

From noreply at wordpress.org  Fri Jun 28 09:37:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 09:37:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4559: Dedicated robots.txt file
 for translate.wordpress.org
Message-ID: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>

#4559: Dedicated robots.txt file for translate.wordpress.org
--------------------------------------+--------------------
 Reporter:  jonoaldersonwp            |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  high                      |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:  seo
--------------------------------------+--------------------
 This consumes huge amounts of crawl budget, for relatively little return.
 We'd like to block crawling of it entirely, via robots.txt.

 At the moment, it shares a robots.txt with other wordpress.org domains,
 which makes this impossible.

 Can we give it a dedicated robots.txt file, which is separate from other
 sites, with the following contents:

 {{{
 User-agent: *
 Disallow: /*
 Noindex: /*
 Allow: /$
 }}}

 If/when this is complete, the `?filter` rule can be removed from the
 shared/global robots.txt file.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4559>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 09:39:44 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 09:39:44 -0000
Subject: [wp-meta] [Making WordPress.org] #4559: Dedicated robots.txt
 file for translate.wordpress.org
In-Reply-To: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>
References: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>
Message-ID: <073.61a04c59bc7801bc208d3244c2623beb@wordpress.org>

#4559: Dedicated robots.txt file for translate.wordpress.org
--------------------------------------+---------------------
 Reporter:  jonoaldersonwp            |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  high                      |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  seo                       |
--------------------------------------+---------------------
Description changed by jonoaldersonwp:

Old description:

> This consumes huge amounts of crawl budget, for relatively little return.
> We'd like to block crawling of it entirely, via robots.txt.
>
> At the moment, it shares a robots.txt with other wordpress.org domains,
> which makes this impossible.
>
> Can we give it a dedicated robots.txt file, which is separate from other
> sites, with the following contents:
>
> {{{
> User-agent: *
> Disallow: /*
> Noindex: /*
> Allow: /$
> }}}
>
> If/when this is complete, the `?filter` rule can be removed from the
> shared/global robots.txt file.

New description:

 This consumes huge amounts of crawl budget, for relatively little return.
 We'd like to block crawling of it entirely, via robots.txt.

 At the moment, it shares a robots.txt with other wordpress.org domains,
 which makes this impossible.

 Can we give it a dedicated robots.txt file, which is separate from other
 sites, with the following contents:

 {{{
 User-agent: *
 Disallow: /*
 Noindex: /*
 Allow: /$
 }}}

 NB: We'll need to be absolutely certain that this is a standalone file,
 and doesn't bleed through to any other WP domains/contexts, or we'll cause
 the end of the world.

 If/when this is complete, the `?filter` rule can be removed from the
 shared/global robots.txt file.

--

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

From noreply at wordpress.org  Fri Jun 28 09:51:32 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 09:51:32 -0000
Subject: [wp-meta] [Making WordPress.org] #3791: Consider bumping
 pre-commit checker on plugins to PHP 7.1
In-Reply-To: <051.a649e8525280ac88e3ba1f38f27d5c23@wordpress.org>
References: <051.a649e8525280ac88e3ba1f38f27d5c23@wordpress.org>
Message-ID: <066.00481aea6b0b50c520e80408c8e773a8@wordpress.org>

#3791: Consider bumping pre-commit checker on plugins to PHP 7.1
------------------------------+---------------------
 Reporter:  Ipstenu           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  pending-systems   |
------------------------------+---------------------

Comment (by dhuethorst):

 Any updates? Blocked by some libraries using 7.1...

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

From noreply at wordpress.org  Fri Jun 28 10:39:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 10:39:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4560: Delete + redirect empty
 handbook pages
Message-ID: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>

#4560: Delete + redirect empty handbook pages
----------------------------+--------------------
 Reporter:  jonoaldersonwp  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  high            |  Milestone:
Component:  Handbooks       |   Keywords:  seo
----------------------------+--------------------
 The handbook contains tons of empty pages, and, tons of deleted pages
 without redirects.

 This needs better care; we need to make sure that pages which are
 moved/removed ''always'' get redirected.

 The following are examples of URLs I've found which are either empty docs
 pages, or, pages which have been removed but not redirected.

 There are almost certainly more; all of them need removing (if they
 haven't already been) ''and'' redirecting to suitable equivalents.

 Empty pages:
 - https://make.wordpress.org/docs/handbook/past-projects/
 - https://make.wordpress.org/docs/handbook/documentation-team-handbook/
 - https://make.wordpress.org/docs/handbook/helphub/helphub-contributors/
 - https://make.wordpress.org/docs/handbook/helphub/translating-helphub/
 - https://make.wordpress.org/docs/handbook/devhub/devhub-contributors/
 - https://make.wordpress.org/docs/handbook/codex/codex-contributors/
 - https://make.wordpress.org/docs/handbook/documentation-team-handbook
 /getting-started/
 - https://make.wordpress.org/docs/handbook/code-reference/inline-
 documentation/working-with-track/
 - https://make.wordpress.org/docs/handbook/code-reference/editing-articles
 /editing-articles-contributors/
 - https://make.wordpress.org/docs/handbook/code-reference/inline-
 documentation/inline-documentation-contributors/


 Moved/removed pages:
 - https://make.wordpress.org/docs/handbook/gutenberg/gutenberg-
 documentation-contributors/
 - https://make.wordpress.org/docs/handbook/documentation-team-handbook
 /handbook-contributors/
 - https://make.wordpress.org/docs/handbook/core/
 - https://make.wordpress.org/docs/handbook/references/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4560>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 10:40:47 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 10:40:47 -0000
Subject: [wp-meta] [Making WordPress.org] #4560: Delete + redirect empty
 handbook pages
In-Reply-To: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>
References: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>
Message-ID: <073.106b671ad8a9c6fff4eb27facf30dadd@wordpress.org>

#4560: Delete + redirect empty handbook pages
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Handbooks       |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------
Description changed by jonoaldersonwp:

Old description:

> The handbook contains tons of empty pages, and, tons of deleted pages
> without redirects.
>
> This needs better care; we need to make sure that pages which are
> moved/removed ''always'' get redirected.
>
> The following are examples of URLs I've found which are either empty docs
> pages, or, pages which have been removed but not redirected.
>
> There are almost certainly more; all of them need removing (if they
> haven't already been) ''and'' redirecting to suitable equivalents.
>
> Empty pages:
> - https://make.wordpress.org/docs/handbook/past-projects/
> - https://make.wordpress.org/docs/handbook/documentation-team-handbook/
> - https://make.wordpress.org/docs/handbook/helphub/helphub-contributors/
> - https://make.wordpress.org/docs/handbook/helphub/translating-helphub/
> - https://make.wordpress.org/docs/handbook/devhub/devhub-contributors/
> - https://make.wordpress.org/docs/handbook/codex/codex-contributors/
> - https://make.wordpress.org/docs/handbook/documentation-team-handbook
> /getting-started/
> - https://make.wordpress.org/docs/handbook/code-reference/inline-
> documentation/working-with-track/
> - https://make.wordpress.org/docs/handbook/code-reference/editing-
> articles/editing-articles-contributors/
> - https://make.wordpress.org/docs/handbook/code-reference/inline-
> documentation/inline-documentation-contributors/
>

> Moved/removed pages:
> - https://make.wordpress.org/docs/handbook/gutenberg/gutenberg-
> documentation-contributors/
> - https://make.wordpress.org/docs/handbook/documentation-team-handbook
> /handbook-contributors/
> - https://make.wordpress.org/docs/handbook/core/
> - https://make.wordpress.org/docs/handbook/references/

New description:

 The handbook contains tons of empty pages, and, tons of deleted pages
 without redirects.

 This needs better care; we need to make sure that pages which are
 moved/removed ''always'' get redirected. Separately to this cleanup, I'd
 be keen to understand how we prevent this from happening again - it's
 ''extremely'' damaging.

 The following are examples of URLs I've found which are either empty docs
 pages, or, pages which have been removed but not redirected.

 There are almost certainly more; all of them need removing (if they
 haven't already been) ''and'' redirecting to suitable equivalents.

 Empty pages:
 - https://make.wordpress.org/docs/handbook/past-projects/
 - https://make.wordpress.org/docs/handbook/documentation-team-handbook/
 - https://make.wordpress.org/docs/handbook/helphub/helphub-contributors/
 - https://make.wordpress.org/docs/handbook/helphub/translating-helphub/
 - https://make.wordpress.org/docs/handbook/devhub/devhub-contributors/
 - https://make.wordpress.org/docs/handbook/codex/codex-contributors/
 - https://make.wordpress.org/docs/handbook/documentation-team-handbook
 /getting-started/
 - https://make.wordpress.org/docs/handbook/code-reference/inline-
 documentation/working-with-track/
 - https://make.wordpress.org/docs/handbook/code-reference/editing-articles
 /editing-articles-contributors/
 - https://make.wordpress.org/docs/handbook/code-reference/inline-
 documentation/inline-documentation-contributors/


 Moved/removed pages:
 - https://make.wordpress.org/docs/handbook/gutenberg/gutenberg-
 documentation-contributors/
 - https://make.wordpress.org/docs/handbook/documentation-team-handbook
 /handbook-contributors/
 - https://make.wordpress.org/docs/handbook/core/
 - https://make.wordpress.org/docs/handbook/references/
 - https://make.wordpress.org/docs/handbook/developer-resources/code-
 reference/codex-migration/reviewing-migrated-examples/

--

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

From noreply at wordpress.org  Fri Jun 28 10:47:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 10:47:13 -0000
Subject: [wp-meta] [Making WordPress.org] #4561: Links to plugin contributor
 profiles should append a trailing slash
Message-ID: <058.450ddfdcfe26410a58ff6531624f2eb0@wordpress.org>

#4561: Links to plugin contributor profiles should append a trailing slash
------------------------------+--------------------
 Reporter:  jonoaldersonwp    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  lowest            |  Milestone:
Component:  Plugin Directory  |   Keywords:  seo
------------------------------+--------------------
 Links to plugin contributors, such as those found in the "Contributors &
 Developers" section on https://wordpress.org/plugins/akismet/, should
 append a trailing slash to their profile link.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4561>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 10:48:45 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 10:48:45 -0000
Subject: [wp-meta] [Making WordPress.org] #4197: Showcase templates omit
 canonical and next/prev tags
In-Reply-To: <058.9a6eeba5072f1fc7c7eaaa904725633e@wordpress.org>
References: <058.9a6eeba5072f1fc7c7eaaa904725633e@wordpress.org>
Message-ID: <073.c935114e2b7f17f8c7afb0f21c414b1e@wordpress.org>

#4197: Showcase templates omit canonical and next/prev tags
----------------------------+----------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  closed
 Priority:  high            |   Milestone:
Component:  Showcase        |  Resolution:  wontfix
 Keywords:  seo             |
----------------------------+----------------------
Changes (by jonoaldersonwp):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Rel next/prev tags no longer supported by Google.

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

From noreply at wordpress.org  Fri Jun 28 10:52:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 10:52:38 -0000
Subject: [wp-meta] [Making WordPress.org] #4535: Delete "Hello World"
 posts (and tidy up empty blogs)
In-Reply-To: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
References: <058.87dc495106ed159669fe26da9de54680@wordpress.org>
Message-ID: <073.8012dc86bd5e4e680c3ebbf179886c88@wordpress.org>

#4535: Delete "Hello World" posts (and tidy up empty blogs)
-------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  enhancement                    |      Status:  accepted
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+-----------------------

Comment (by jonoaldersonwp):

 Related https://meta.trac.wordpress.org/ticket/4289

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

From noreply at wordpress.org  Fri Jun 28 10:55:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 10:55:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4562: Plugin support links should
 append a trailing slash
Message-ID: <058.1896203732e3788b152d57d019bf4886@wordpress.org>

#4562: Plugin support links should append a trailing slash
------------------------------+--------------------
 Reporter:  jonoaldersonwp    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  lowest            |  Milestone:
Component:  Plugin Directory  |   Keywords:  seo
------------------------------+--------------------
 The 'View support forum' link in the sidebar, and the 'Support' link in
 the plugin nav/tabs (with 'Details' / 'Reviews', 'Installation' etc)
 should append a trailing slash to the link.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4562>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 11:09:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:09:38 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
Message-ID: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+--------------------
 Reporter:  jonoaldersonwp           |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  seo
-------------------------------------+--------------------
 Search results pages, such as https://central.wordcamp.org/?s=cats, should
 output a meta robots tag with a value of 'noindex, follow',

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4563>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 11:12:38 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:12:38 -0000
Subject: [wp-meta] [Making WordPress.org] #4289: Delete placeholder pages
In-Reply-To: <058.ea8feffab078bd39b6b91ea5f5d70670@wordpress.org>
References: <058.ea8feffab078bd39b6b91ea5f5d70670@wordpress.org>
Message-ID: <073.739126fb2df314b55dd81aca939a2785@wordpress.org>

#4289: Delete placeholder pages
-------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                 |       Owner:  ocean90
     Type:  defect                         |      Status:  accepted
 Priority:  low                            |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:  seo                            |
-------------------------------------------+-----------------------
Changes (by ocean90):

 * owner:  defries => ocean90
 * status:  assigned => accepted


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

From noreply at wordpress.org  Fri Jun 28 11:14:10 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:14:10 -0000
Subject: [wp-meta] [Making WordPress.org] #4564: Paginated states of the
 WordCamp homepage should 301 to the site root
Message-ID: <058.3d6c836c0e2f1f07c21c010e4c6518c5@wordpress.org>

#4564: Paginated states of the WordCamp homepage should 301 to the site root
-------------------------------------+--------------------
 Reporter:  jonoaldersonwp           |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  lowest                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  seo
-------------------------------------+--------------------
 E.g., https://central.wordcamp.org/page/5/ should 301 to
 https://central.wordcamp.org/

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4564>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 11:16:06 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:16:06 -0000
Subject: [wp-meta] [Making WordPress.org] #4565: WordCamp pages should
 include the year in the title
Message-ID: <058.254ef66cc58f8eceaab0a21dee5827d4@wordpress.org>

#4565: WordCamp pages should include the year in the title
-------------------------------------+--------------------
 Reporter:  jonoaldersonwp           |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  lowest                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  seo
-------------------------------------+--------------------
 E.g., https://central.wordcamp.org/wordcamps/wordcamp-grand-rapids-mi-2/
 has a title of `WordCamp Grand Rapids, MI | WordCamp Central`. This should
 be `WordCamp Grand Rapids, MI - 2019 | WordCamp Central`.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4565>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 11:17:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:17:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4559: Dedicated robots.txt
 file for translate.wordpress.org
In-Reply-To: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>
References: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>
Message-ID: <073.c91d04867f8ab633b1d812925be5ed2e@wordpress.org>

#4559: Dedicated robots.txt file for translate.wordpress.org
--------------------------------------+---------------------
 Reporter:  jonoaldersonwp            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  seo                       |
--------------------------------------+---------------------
Changes (by ocean90):

 * priority:  high => low
 * type:  defect => enhancement


Comment:

 There are probably a few pages which still should be indexed like /stats,
 /consistency or each /locale/$locale.

 > We'd like to block crawling of it entirely
 Just out of curiosity, who is "we"?

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

From noreply at wordpress.org  Fri Jun 28 11:19:32 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:19:32 -0000
Subject: [wp-meta] [Making WordPress.org] #4566: Image placeholder isn't
 size-constrained
Message-ID: <058.60f90f525c26631779d7c28e37b4643a@wordpress.org>

#4566: Image placeholder isn't size-constrained
-------------------------------------+--------------------
 Reporter:  jonoaldersonwp           |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  lowest                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  seo
-------------------------------------+--------------------
 When a WordCamp page is missing an image, such as with
 https://central.wordcamp.org/wordcamps/wordcamp-grand-rapids/, the
 preview/loading image escapes its bounding.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4566>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 11:21:15 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:21:15 -0000
Subject: [wp-meta] [Making WordPress.org] #4559: Dedicated robots.txt
 file for translate.wordpress.org
In-Reply-To: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>
References: <058.bca6e4035f58d9f9d7208fae8a4121df@wordpress.org>
Message-ID: <073.67d77ecacd40b74e58a5f7803c26a9c4@wordpress.org>

#4559: Dedicated robots.txt file for translate.wordpress.org
--------------------------------------+---------------------
 Reporter:  jonoaldersonwp            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  seo                       |
--------------------------------------+---------------------

Comment (by jonoaldersonwp):

 Happy to add a small number of whitelisted pages. In this case, "we" is me
 and Joost.

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

From noreply at wordpress.org  Fri Jun 28 11:28:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:28:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4567: WordCamp news templates
 should use canonical URL tags
Message-ID: <058.47bc633d4cdd1f7f8c04adac87e01284@wordpress.org>

#4567: WordCamp news templates should use canonical URL tags
-------------------------------------+--------------------
 Reporter:  jonoaldersonwp           |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  low                      |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  seo
-------------------------------------+--------------------
 The following example URLs are all missing canonical tags. In each case,
 and in the cases they represent, canonical tags should be added.

 - https://central.wordcamp.org/news/ (archive)
 - https://central.wordcamp.org/news/page/2/ (paginated archive)
 - https://central.wordcamp.org/news/2018/ (date archive)
 - https://central.wordcamp.org/news/author/sippis/ (author archive)
 - https://central.wordcamp.org/news/category/events/ (category archive)
 - https://central.wordcamp.org/news/tag/announcements/ (tag archive)
 - https://central.wordcamp.org/news/2018/page/2/ (compound paginated
 states)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4567>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 11:37:55 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:37:55 -0000
Subject: [wp-meta] [Making WordPress.org] #4390: Hide duplicates on
 WordCamp attendees page
In-Reply-To: <055.54e74b07de4bd465c7213d9ade3f0e79@wordpress.org>
References: <055.54e74b07de4bd465c7213d9ade3f0e79@wordpress.org>
Message-ID: <070.bcd583b618e84b4091908766fb7945e7@wordpress.org>

#4390: Hide duplicates on WordCamp attendees page
-------------------------------------+---------------------
 Reporter:  hlashbrooke              |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by casiepa):

 @coreymckrill as a workaround this might have done the job, but the same
 issue exists with volunteer tickets: Somebody buys a standard ticket, then
 decides to apply as volunteer, gets accepted and is asked to take the
 (normally free) volunteer ticket. So that person now has 2 tickets and
 will (probably) be shown twice.
 There will be both cases for volunteers:
 - Bought a normal ticket, then took the volunteers one (so keeps both)
 - Waited for the volunteers ticket and only has that one

 A check might have to be done to exclude any double entries of name-email
 unique combination.

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

From noreply at wordpress.org  Fri Jun 28 11:53:09 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 28 Jun 2019 11:53:09 +0000 (UTC)
Subject: [wp-meta] [9002]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/widgets:
 Plugin Directory: Add trailing slash to profile URLs in committers,
 contributors, and support reps lists.
Message-ID: <20190628115309.98F241B0052F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190628/850290e5/attachment-0001.html>

From noreply at wordpress.org  Fri Jun 28 11:53:11 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 11:53:11 -0000
Subject: [wp-meta] [Making WordPress.org] #4561: Links to plugin
 contributor profiles should append a trailing slash
In-Reply-To: <058.450ddfdcfe26410a58ff6531624f2eb0@wordpress.org>
References: <058.450ddfdcfe26410a58ff6531624f2eb0@wordpress.org>
Message-ID: <073.ded1eb5f70dae59852048a53481485ea@wordpress.org>

#4561: Links to plugin contributor profiles should append a trailing slash
------------------------------+-----------------------------
 Reporter:  jonoaldersonwp    |       Owner:  SergeyBiryukov
     Type:  defect            |      Status:  closed
 Priority:  lowest            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  seo               |
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"9002" 9002]:
 {{{
 #!CommitTicketReference repository="" revision="9002"
 Plugin Directory: Add trailing slash to profile URLs in committers,
 contributors, and support reps lists.

 Props jonoaldersonwp.
 Fixes #4561.
 }}}

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

From noreply at wordpress.org  Fri Jun 28 12:00:07 2019
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 28 Jun 2019 12:00:07 +0000 (UTC)
Subject: [wp-meta] [9003]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/class-template.php:
 Plugin Directory: Add trailing slash to support forums URL.
Message-ID: <20190628120007.A752C1B0052F@svn1.ord.wordpress.org>

An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/wp-meta/attachments/20190628/ce557ab9/attachment.html>

From noreply at wordpress.org  Fri Jun 28 12:00:09 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 12:00:09 -0000
Subject: [wp-meta] [Making WordPress.org] #4562: Plugin support links
 should append a trailing slash
In-Reply-To: <058.1896203732e3788b152d57d019bf4886@wordpress.org>
References: <058.1896203732e3788b152d57d019bf4886@wordpress.org>
Message-ID: <073.da37fa88ba2c7a1488800736c346f990@wordpress.org>

#4562: Plugin support links should append a trailing slash
------------------------------+-----------------------------
 Reporter:  jonoaldersonwp    |       Owner:  SergeyBiryukov
     Type:  defect            |      Status:  closed
 Priority:  lowest            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  seo               |
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"9003" 9003]:
 {{{
 #!CommitTicketReference repository="" revision="9003"
 Plugin Directory: Add trailing slash to support forums URL.

 Props jonoaldersonwp.
 Fixes #4562.
 }}}

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

From noreply at wordpress.org  Fri Jun 28 12:12:54 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 12:12:54 -0000
Subject: [wp-meta] [Making WordPress.org] #4560: Delete + redirect empty
 handbook pages
In-Reply-To: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>
References: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>
Message-ID: <073.05108a430faf38a86d7f92b0018eed4d@wordpress.org>

#4560: Delete + redirect empty handbook pages
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Handbooks       |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by dd32):

 FWIW these are all handbook pages from the Docs Team Handbook on how to
 contribute to OTHER handbooks. Most of these pages were published as stubs
 and have never had content.

 I'll ping the #docs team to clean it up.

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

From noreply at wordpress.org  Fri Jun 28 12:14:04 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 12:14:04 -0000
Subject: [wp-meta] [Making WordPress.org] #4560: Delete + redirect empty
 handbook pages
In-Reply-To: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>
References: <058.b731cbc969ca458e0c4e046244f92ae0@wordpress.org>
Message-ID: <073.0240d2c8dc085725d383ffdb8ee324c4@wordpress.org>

#4560: Delete + redirect empty handbook pages
----------------------------+---------------------
 Reporter:  jonoaldersonwp  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Handbooks       |  Resolution:
 Keywords:  seo             |
----------------------------+---------------------

Comment (by jonoaldersonwp):

 Ahhh, interesting! Nice one :)

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

From noreply at wordpress.org  Fri Jun 28 12:23:27 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 12:23:27 -0000
Subject: [wp-meta] [Making WordPress.org] #4390: Hide duplicates on
 WordCamp attendees page
In-Reply-To: <055.54e74b07de4bd465c7213d9ade3f0e79@wordpress.org>
References: <055.54e74b07de4bd465c7213d9ade3f0e79@wordpress.org>
Message-ID: <070.d55aa6d769c1b7d391f1b0e3c687312a@wordpress.org>

#4390: Hide duplicates on WordCamp attendees page
-------------------------------------+---------------------
 Reporter:  hlashbrooke              |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by dd32):

 Replying to [comment:2 casiepa]:
 > @coreymckrill as a workaround this might have done the job, but the same
 issue exists with volunteer tickets: Somebody buys a standard ticket, then
 decides to apply as volunteer, gets accepted and is asked to take the
 (normally free) volunteer ticket. So that person now has 2 tickets and
 will (probably) be shown twice.

 It used to be that only one attendee would be shown per email address, but
 it looks like that was recently changed -
 https://github.com/Automattic/camptix/commit/594077b9500ae18a04b7d76d06b1d5919d4d139c

 You can also just mark one of the tickets as private, so that it doesn't
 show in the attendee listing.

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

From noreply at wordpress.org  Fri Jun 28 12:50:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 12:50:51 -0000
Subject: [wp-meta] [Making WordPress.org] #2259: Ability to rate
 sessions / speakers
In-Reply-To: <049.451385f9720087622ec1830dd54a8bea@wordpress.org>
References: <049.451385f9720087622ec1830dd54a8bea@wordpress.org>
Message-ID: <064.112a7d6123e402224b591668a6b22c35@wordpress.org>

#2259: Ability to rate sessions / speakers
--------------------------------------------------+-----------------------
 Reporter:  Seags                                 |       Owner:  (none)
     Type:  enhancement                           |      Status:  assigned
 Priority:  normal                                |   Milestone:
Component:  WordCamp Site & Plugins               |  Resolution:
 Keywords:  dev-feedback ui-feedback ux-feedback  |
--------------------------------------------------+-----------------------

Comment (by casiepa):

 As per @melchoyce idea, why not using the input from WordPress.tv and
 youtube.com/wordpress?
 Or to think even further: is it not sufficient to read it there? Do we
 need it somewhere else?

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

From noreply at wordpress.org  Fri Jun 28 15:52:59 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 15:52:59 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
In-Reply-To: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
References: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
Message-ID: <073.ee267b20b6f5489579819d5f20ae83a6@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+---------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  seo                      |
-------------------------------------+---------------------

Comment (by iandunn):

 Is there a Core ticket for that? It seems odd to do that on a per-site
 basis if it's a best practice.

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

From noreply at wordpress.org  Fri Jun 28 15:59:16 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 15:59:16 -0000
Subject: [wp-meta] [Making WordPress.org] #4564: Paginated states of the
 WordCamp homepage should 301 to the site root
In-Reply-To: <058.3d6c836c0e2f1f07c21c010e4c6518c5@wordpress.org>
References: <058.3d6c836c0e2f1f07c21c010e4c6518c5@wordpress.org>
Message-ID: <073.a9a95f16919e72cde203291ea8fe0b9e@wordpress.org>

#4564: Paginated states of the WordCamp homepage should 301 to the site root
-------------------------------------+---------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  lowest                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  seo                      |
-------------------------------------+---------------------

Comment (by iandunn):

 That looks like the normal Core behavior when the homepage is setup to
 display a page. Seems like this should be a Core ticket instead?

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

From noreply at wordpress.org  Fri Jun 28 16:00:02 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:00:02 -0000
Subject: [wp-meta] [Making WordPress.org] #4565: WordCamp pages should
 include the year in the title
In-Reply-To: <058.254ef66cc58f8eceaab0a21dee5827d4@wordpress.org>
References: <058.254ef66cc58f8eceaab0a21dee5827d4@wordpress.org>
Message-ID: <073.fe0edb649d47ed411e4b10d5400018da@wordpress.org>

#4565: WordCamp pages should include the year in the title
--------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                  |       Owner:  (none)
     Type:  defect                          |      Status:  assigned
 Priority:  lowest                          |   Milestone:
Component:  WordCamp Site & Plugins         |  Resolution:
 Keywords:  seo needs-patch good-first-bug  |
--------------------------------------------+-----------------------
Changes (by iandunn):

 * keywords:  seo => seo needs-patch good-first-bug
 * status:  new => assigned


Comment:

 +1

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

From noreply at wordpress.org  Fri Jun 28 16:00:41 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:00:41 -0000
Subject: [wp-meta] [Making WordPress.org] #4566: Image placeholder isn't
 size-constrained
In-Reply-To: <058.60f90f525c26631779d7c28e37b4643a@wordpress.org>
References: <058.60f90f525c26631779d7c28e37b4643a@wordpress.org>
Message-ID: <073.e0fb6876eef124fa3341c1582ea32dcc@wordpress.org>

#4566: Image placeholder isn't size-constrained
--------------------------------------------+-----------------------
 Reporter:  jonoaldersonwp                  |       Owner:  (none)
     Type:  defect                          |      Status:  assigned
 Priority:  lowest                          |   Milestone:
Component:  WordCamp Site & Plugins         |  Resolution:
 Keywords:  seo needs-patch good-first-bug  |
--------------------------------------------+-----------------------
Changes (by iandunn):

 * keywords:  seo => seo needs-patch good-first-bug
 * status:  new => assigned


Comment:

 +1

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

From noreply at wordpress.org  Fri Jun 28 16:02:01 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:02:01 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
In-Reply-To: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
References: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
Message-ID: <073.9d0085755f3706e9943715ab9439cbfa@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+---------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  seo                      |
-------------------------------------+---------------------

Comment (by jonoaldersonwp):

 I can't see anything in core trac, but given that I'd actually like to see
 this fixed before the heat death of the universe and without having to
 fight through the politics of Jetpack vs Core vs basic SEO standards, I'm
 hoping that we can just fix this here and pretend that everything is okay.

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

From noreply at wordpress.org  Fri Jun 28 16:07:33 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:07:33 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
In-Reply-To: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
References: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
Message-ID: <073.4e1ba50f97e43e1dda8e1b63089eefd6@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+----------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  wontfix
 Keywords:  seo                      |
-------------------------------------+----------------------
Changes (by iandunn):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 IMO, the low impact wouldn't justify the effort of doing it per-site. I'd
 rather us focus our limited resources on things that will make a
 significant impact for organizers/attendees.

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

From noreply at wordpress.org  Fri Jun 28 16:10:58 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:10:58 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
In-Reply-To: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
References: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
Message-ID: <073.fe19b41cd1ba93f48d830f52aaf5c439@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+----------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  wontfix
 Keywords:  seo                      |
-------------------------------------+----------------------

Comment (by jonoaldersonwp):

 Agreed in principle for most cases, which is why I haven't opened a
 thousand tickets - but this one is particularly serious and actively
 harming performance atm, and worth the investment.

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

From noreply at wordpress.org  Fri Jun 28 16:23:30 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:23:30 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
In-Reply-To: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
References: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
Message-ID: <073.13cbfc27d334f1d7022e4f6ee3e8d049@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+-----------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  reopened
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  seo                      |
-------------------------------------+-----------------------
Changes (by iandunn):

 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 Can you give some details on the performance issues it causes?

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

From noreply at wordpress.org  Fri Jun 28 16:42:34 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 16:42:34 -0000
Subject: [wp-meta] [Making WordPress.org] #4563: Search results pages on
 WordCamp Central should be noindex'd
In-Reply-To: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
References: <058.3b29c401c3d5c1a54e68117f74cde0c9@wordpress.org>
Message-ID: <073.1467149c4a2822a1445e315b86fb4fe6@wordpress.org>

#4563: Search results pages on WordCamp Central should be noindex'd
-------------------------------------+-----------------------
 Reporter:  jonoaldersonwp           |       Owner:  (none)
     Type:  defect                   |      Status:  reopened
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  seo                      |
-------------------------------------+-----------------------

Comment (by jonoaldersonwp):

 Sure, but, can we please not close tickets like this preemptively when
 I've put the time and effort in to determine that they're worth the
 effort/reward trade off?

 Search Google for `site:central.wordcamp.org inurl:s`. The odd Chinese
 character pages you'll see are from a whole bunch of indexed urls where
 Chinese spam networks are executing blind man in the middle attacks in an
 attempt to syphon seo value, or, its a (low level) negative seo attack.
 This is actively harming our crawl budget, relevance, and site quality for
 the whole wordpress.org ecosystem.

 This is one small example, and just the tip of the iceberg. There are a
 thousands of issues like these, where wp core just doesn't meet basic SEO
 requirements.

 I'd love to see these level ofstandards implemented in core, but it's just
 unrealistic that that'll happen any time soon. In the meantime, for every
 day that passes, Wix grow their market share at our expense. For the
 relatively low effort required to solve this locally, we should just do
 so.

 Or, we could install a plugin which handles it all for us automatically,
 eh?

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

From noreply at wordpress.org  Fri Jun 28 19:05:07 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:05:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3318: Change two sentences on
 wordpress.org/
In-Reply-To: <055.f2c1a95096fcf6cd25a30678968add81@wordpress.org>
References: <055.f2c1a95096fcf6cd25a30678968add81@wordpress.org>
Message-ID: <070.d645ad931686032ead51b0355331bec2@wordpress.org>

#3318: Change two sentences on wordpress.org/
-----------------------------------------+--------------------------------
 Reporter:  IkusiMakusi                  |       Owner:  (none)
     Type:  enhancement                  |      Status:  closed
 Priority:  normal                       |   Milestone:
Component:  General                      |  Resolution:  reported-upstream
 Keywords:  has-patch reporter-feedback  |
-----------------------------------------+--------------------------------

Comment (by yvettesonneveld):

 Thank you for reaching out, @tellyworth! From a marketing perspective,
 it's a bit of a tricky one. It's about showing some personality, while not
 offending or excluding anyone at the same time. Since we're such a diverse
 community, I'd recommend to err on the safe side.

 I have some thoughts on the copy but will run them by my co-teamreps
 first. That will help me make sure I'm not overlooking any known
 sensitivities. Will get back to you all soon.

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

From noreply at wordpress.org  Fri Jun 28 19:14:39 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:14:39 -0000
Subject: [wp-meta] [Making WordPress.org] #4568: WordCamps: Render session
 information in page template
Message-ID: <053.745f16986fedbcfbdbeb1beaa78aa9af@wordpress.org>

#4568: WordCamps: Render session information in page template
-------------------------------------+--------------------
 Reporter:  melchoyce                |      Owner:  (none)
     Type:  enhancement              |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 While we input session details (time, location, category, etc.) to session
 pages, that information doesn't get output in the session page itself. If
 you're linking someone to your session page, they'd still need to go and
 look at the schedule just to see when you're speaking. Can we render this
 information below the session description?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4568>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 19:18:21 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:18:21 -0000
Subject: [wp-meta] [Making WordPress.org] #4569: WordCamp: Improve
 individual session and speaker pages
Message-ID: <053.95ef4d620a4c1cdb2c02003db68de8fb@wordpress.org>

#4569: WordCamp: Improve individual session and speaker pages
-------------------------+--------------------
 Reporter:  melchoyce    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 Instead of outputting the speaker/session information at the bottom of the
 page, what if we automatically added the appropriate block, so you could
 control what information is shown on single pages?

 So: On an individual speaker page, it would have the speaker's bio, and
 then the speaker's session, output in the editor as a single session block
 with that speaker's session selected.

 I understand that this is much better suited to an eventual Gutenberg
 template framework, but even though it might be a pain in the short-term
 to update every block if you do want to customize the block settings, I
 think it could be an okay bandaid improvement.

 See attached mockup for what I'm thinking on the front-end.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4569>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 19:18:46 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:18:46 -0000
Subject: [wp-meta] [Making WordPress.org] #4569: WordCamp: Improve
 individual session and speaker pages
In-Reply-To: <053.95ef4d620a4c1cdb2c02003db68de8fb@wordpress.org>
References: <053.95ef4d620a4c1cdb2c02003db68de8fb@wordpress.org>
Message-ID: <068.83130796b5a5b7d7d9fbd8978c3e8110@wordpress.org>

#4569: WordCamp: Improve individual session and speaker pages
-------------------------+---------------------
 Reporter:  melchoyce    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by melchoyce):

 * Attachment "Speaker.png" added.


-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4569>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 19:20:26 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:20:26 -0000
Subject: [wp-meta] [Making WordPress.org] #4569: WordCamp: Improve
 individual session and speaker pages
In-Reply-To: <053.95ef4d620a4c1cdb2c02003db68de8fb@wordpress.org>
References: <053.95ef4d620a4c1cdb2c02003db68de8fb@wordpress.org>
Message-ID: <068.bae6b651a61826e4fb8d871f375ce69c@wordpress.org>

#4569: WordCamp: Improve individual session and speaker pages
-------------------------------------+---------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------
Changes (by melchoyce):

 * component:  General => WordCamp Site & Plugins


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

From noreply at wordpress.org  Fri Jun 28 19:20:30 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:20:30 -0000
Subject: [wp-meta] [Making WordPress.org] #4570: WordCamps: Add duration to
 sessions
Message-ID: <053.0782aa1d77de94171030baffd5938f92@wordpress.org>

#4570: WordCamps: Add duration to sessions
-------------------------------------+--------------------
 Reporter:  melchoyce                |      Owner:  (none)
     Type:  enhancement              |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 Providing a duration lets you show end time for a session. For example, in
 WordCamp Boston's schedule last year, we had to use some hacky css
 `:after` to show end times: https://2018.boston.wordcamp.org/schedule/

 Plus, for the PWA app, adding duration will let us know what’s on “now”
 without relying on another session being after it.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4570>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Fri Jun 28 19:22:08 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 19:22:08 -0000
Subject: [wp-meta] [Making WordPress.org] #4528: Provide Data Export
 Request link on the Privacy Policy 'Access to Data' section.
In-Reply-To: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
References: <059.47a9a6aa6c9020485f72ee9ebed5964f@wordpress.org>
Message-ID: <074.8baf0a3a9055582c9d000f4c38ab059c@wordpress.org>

#4528: Provide Data Export Request link on the Privacy Policy 'Access to Data'
section.
-----------------------------+-----------------------------
 Reporter:  garrett-eclipse  |       Owner:  SergeyBiryukov
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  fixed
 Keywords:                   |
-----------------------------+-----------------------------

Comment (by garrett-eclipse):

 Hi @tellyworth I carried the note over from the pre-existing instructions
 for the erasure request portion in the Privacy Policy. I wasn't too sure
 how that association is done but I did notice that for both forms if you
 are logged in it's pre-populated with your email so I assumed the two had
 similar functions in that respect.

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

From noreply at wordpress.org  Fri Jun 28 20:36:51 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 20:36:51 -0000
Subject: [wp-meta] [Making WordPress.org] #4570: WordCamps: Add duration
 to sessions
In-Reply-To: <053.0782aa1d77de94171030baffd5938f92@wordpress.org>
References: <053.0782aa1d77de94171030baffd5938f92@wordpress.org>
Message-ID: <068.68eda04aad9d05ff3b75f701aceca6e8@wordpress.org>

#4570: WordCamps: Add duration to sessions
-------------------------------------+---------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------

Comment (by iandunn):

 +1, this is also a requirement for the new Schedule block, and I've got it
 partially implemented in the WIP branch for that.

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

From noreply at wordpress.org  Fri Jun 28 22:37:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 22:37:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
In-Reply-To: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
References: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
Message-ID: <066.c00a2c6bbed64e2b31c8172e17679e50@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by Otto42):

 Limiting it to "small batches" may not be the long term case here. Perhaps
 a wp-cron/cavalcade approach is needed, because it could be thousands of
 emails for some of the cases we've had to do this before.

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

From noreply at wordpress.org  Fri Jun 28 22:42:46 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Jun 2019 22:42:46 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
In-Reply-To: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
References: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
Message-ID: <066.95ab2c7ed0f2d8426361f16afae662bd@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by Otto42):

 Note: one assumption we can make is that we're only ever going to want to
 email the people with commit access to the plugin. Should limit the
 lookups a bit.

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

From noreply at wordpress.org  Sat Jun 29 09:51:00 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Jun 2019 09:51:00 -0000
Subject: [wp-meta] [Making WordPress.org] #4360: Trac throwing errors
 about missing or invalid form token/secure cookies on ticket updates
In-Reply-To: <057.21a1b70706d472a227b290e1233f46da@wordpress.org>
References: <057.21a1b70706d472a227b290e1233f46da@wordpress.org>
Message-ID: <072.26088f0ddfca2f16bf09126c485abdf8@wordpress.org>

#4360: Trac throwing errors about missing or invalid form token/secure cookies on
ticket updates
---------------------------+-----------------------
 Reporter:  williampatton  |       Owner:  dd32
     Type:  defect         |      Status:  accepted
 Priority:  normal         |   Milestone:
Component:  Trac           |  Resolution:
 Keywords:                 |
---------------------------+-----------------------

Comment (by rafax):

 I am having the same problem, there is some solution.

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

From noreply at wordpress.org  Sat Jun 29 11:02:03 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Jun 2019 11:02:03 -0000
Subject: [wp-meta] [Making WordPress.org] #4360: Trac throwing errors
 about missing or invalid form token/secure cookies on ticket updates
In-Reply-To: <057.21a1b70706d472a227b290e1233f46da@wordpress.org>
References: <057.21a1b70706d472a227b290e1233f46da@wordpress.org>
Message-ID: <072.a2c174e99b2ebef38d117bb768d66d3a@wordpress.org>

#4360: Trac throwing errors about missing or invalid form token/secure cookies on
ticket updates
---------------------------+-----------------------
 Reporter:  williampatton  |       Owner:  dd32
     Type:  defect         |      Status:  accepted
 Priority:  normal         |   Milestone:
Component:  Trac           |  Resolution:
 Keywords:                 |
---------------------------+-----------------------

Comment (by rozerben):

 Hi I am showing same error?
 What is solution?

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

From noreply at wordpress.org  Sat Jun 29 16:29:13 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Jun 2019 16:29:13 -0000
Subject: [wp-meta] [Making WordPress.org] #215: Feature Request:
 Readme.txt generated tabs on theme pages
In-Reply-To: <055.45befa0024b2058e797056bd27b9cfe6@wordpress.org>
References: <055.45befa0024b2058e797056bd27b9cfe6@wordpress.org>
Message-ID: <070.c0b5d2acd88054819d45b9dcb151d8ee@wordpress.org>

#215: Feature Request: Readme.txt generated tabs on theme pages
-----------------------------+---------------------
 Reporter:  iandstewart      |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+---------------------
Changes (by dingo_d):

 * priority:  normal => high


Comment:

 Since we already have the requirement for themes to implement valid readme
 like the plugins do
 (https://make.wordpress.org/themes/handbook/review/required/#readme-txt-
 file), there is no reason this shouldn't be implemented.

 We discussed this on the WCEU and would like to move forward to unifying
 themes and plugin start page, give themes more versatility etc.

 I'm not sure what is needed for this to happen, the thing that was needed
 from the TRT side is done (readme.txt required).
 So if you can make some guide what needs to happen, some points where we
 can help that would be great :)

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

From noreply at wordpress.org  Sun Jun 30 04:12:19 2019
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 30 Jun 2019 04:12:19 -0000
Subject: [wp-meta] [Making WordPress.org] #4555: Plugin Directory
 Administration: Mass Email Tool
In-Reply-To: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
References: <051.bbabd55368b057f5baf8c4d8aeca7644@wordpress.org>
Message-ID: <066.3236d97308dc37d9b0aa3480264ca056@wordpress.org>

#4555: Plugin Directory Administration: Mass Email Tool
------------------------------+-----------------------
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by Ipstenu):

 I was thinking of intentionally small batches of plugins. This would be
 for things like the mass trademark mails (thank you Facerange/Instabrand)
 or outdated libraries. It should be for everyone with commit access AND
 account listed as owner. But ... generally that's only 3-10 people per
 plugin.

 The cron stuff though, that would be great for the major release emails,
 or things that have to go to everyone. It's more manageable to split up
 the other stuff into chunks of 50-100 plugins at a time. That lets us not
 get overloaded with some of the more ... special replies :) Basically
 emails we're pretty sure will need manual intervention on our end to sort
 shouldn't be done in batches of 1000.

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