From noreply at wordpress.org  Sun Apr  1 00:30:24 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 01 Apr 2018 00:30:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3542: Incorrectly escaped percent
 sign in "about security"
Message-ID: <056.acbbf248a96e4ba2f4e9c62f7c494f91@wordpress.org>

#3542: Incorrectly escaped percent sign in "about security"
-------------------------------------------+--------------------
 Reporter:  tobifjellner                   |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:
-------------------------------------------+--------------------
 Location:
 https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/themes/pub/wporg-main/page-about-security.php around line 77


 {{{
 printf(
 /* translators: 1: WordPress Market share - 30. Note the following % sign
 is escaped as %%. 2: Footnote 3: Market Penetration - 60.  Note the
 following % sign is escaped as %%. */
 __( 'WordPress is a free and open source content management system (CMS).
 It is the most widely-used CMS software in the world and it powers more
 than %1$s%% of the top 10 million websites%2$s, giving it an estimated 58%
 market share of all sites
 using a CMS.', 'wporg' ),
 WP_MARKET_SHARE,
 '<sup id="ref1"><a href="#footnote1">1</a></a></sup>',
 60
 );
 }}}

 The problem here is with "58%", and it's twofold:
 1. "58" would better be a parameter.
 2. The percent sign needs to be escaped into %%

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

From noreply at wordpress.org  Sun Apr  1 06:03:51 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  1 Apr 2018 06:03:51 +0000 (UTC)
Subject: [wp-meta] [6997]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php:
 Main: About: Correct an incorrect placeholder in a string.
Message-ID: <20180401060351.AB3C11B00A6E@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sun Apr  1 06:03:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 01 Apr 2018 06:03:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3542: Incorrectly escaped
 percent sign in "about security"
In-Reply-To: <056.acbbf248a96e4ba2f4e9c62f7c494f91@wordpress.org>
References: <056.acbbf248a96e4ba2f4e9c62f7c494f91@wordpress.org>
Message-ID: <071.056f63481312b8a15be3cc907843251b@wordpress.org>

#3542: Incorrectly escaped percent sign in "about security"
-------------------------------------------+-------------------------
 Reporter:  tobifjellner                   |       Owner:  Dion Hulse
     Type:  defect                         |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  fixed
 Keywords:                                 |
-------------------------------------------+-------------------------
Changes (by Dion Hulse):

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


Comment:

 In [changeset:"6997" 6997]:
 {{{
 #!CommitTicketReference repository="" revision="6997"
 Main: About: Correct an incorrect placeholder in a string.

 H/t tobifjellner.
 Fixes #3542.
 }}}

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

From noreply at wordpress.org  Sun Apr  1 07:25:24 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 01 Apr 2018 07:25:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.b18e2b19743a34a3f889d2d37cc34085@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by ramiy):

 RTL issues in the [https://he.wordpress.org/about/logos/ Graphics & Logos]
 page, see the "Downloads" section.

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

From noreply at wordpress.org  Sun Apr  1 07:57:00 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 01 Apr 2018 07:57:00 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.3d514310b1397e452b502f5429365ab1@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dion Hulse):

 Replying to [comment:151 Remkus de Vries]:
 > Replying to [comment:98 dd32]:
 >
 > > * Decide on how to handle translated slugs, and implement
 > > Slug translation isn't something we've solved on WordPress.org yet for
 rosetta sites (see: /plugins/ and /themes/) and I don't see this as a
 release blocker either.
 > > I've spun this out into #3507 as it's going to require a bit more work
 and will be best handled as it's own mini-project.
 >
 > As much as I love the visual impact of these beautiful about pages, I'm
 sad about having no option whatsoever to have the slugs translated from
 the get go. Because this looks just wrong:
 https://nl.wordpress.org/about/history/ and we, as the Dutch team,
 would've considered this a blocker. Not even mentioning that fact of
 having English pages automatically published before they're translated.
 >
 > Do we really have to wait for core to solve this or can we solve this
 with making the slugs translatable?

 This isn't something we'll wait for core on, but it wasn't something that
 was going to be remotely done before launching these, and honestly may not
 be implemented in the short-term either.

 Discussion and implementation details should be kept to #3507.

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

From noreply at wordpress.org  Sun Apr  1 07:57:48 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 01 Apr 2018 07:57:48 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.d7bbd0eeab674841b2f6d8dec9d87434@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dion Hulse):

 Replying to [comment:155 ramiy]:
 > RTL issues in the [https://he.wordpress.org/about/logos/ Graphics &
 Logos] page, see the "Downloads" section.

 If you could detail the issues on this ticket, that'd be great.

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

From noreply at wordpress.org  Mon Apr  2 15:16:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 15:16:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3543: Download History is not
 showing the exact stats for the newly uploaded plugin
Message-ID: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>

#3543: Download History is not showing the exact stats for the newly uploaded
plugin
------------------------------+--------------------
 Reporter:  abdullahramzan    |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 Hi,

 We have released the new plugin named as '''Contact Form by
 PowerFormBuilder – Drag & Drop + GDPR Tools for WordPress'''. Its download
 history is not showing the exact number of downloads as it is released
 today.

 I am also sharing a direct link for the plugin. Please have a look it.
 https://wordpress.org/plugins/power-forms-builder/advanced/

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

From noreply at wordpress.org  Mon Apr  2 15:17:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 15:17:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3543: Download History is not
 showing the exact stats for the newly uploaded plugin
In-Reply-To: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
References: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
Message-ID: <073.dcae76b121a6470e44cd3e977a45cfbe@wordpress.org>

#3543: Download History is not showing the exact stats for the newly uploaded
plugin
------------------------------+---------------------
 Reporter:  abdullahramzan    |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------
Changes (by abdullahramzan):

 * Attachment "Download History for the newly uploaded plugin.png" added.

 Download History Screenshot

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

From noreply at wordpress.org  Mon Apr  2 16:24:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 16:24:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3544: Plugin Admin: IP Tracker
Message-ID: <051.27c21796e082c5cc62912aae58a1fcde@wordpress.org>

#3544: Plugin Admin: IP Tracker
------------------------------+--------------------
 Reporter:  Ipstenu (Mika E)  |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 We used to have a tool to check the IP address of submissions and compare
 to all others. This was useful to swiftly find people who were making
 serial plugins accounts to avoid previous restrictions.

 {{{ /plugins/admin?ip= }}}

 It works much like the User Card (see an image here -
 https://make.wordpress.org/plugins/handbook/performing-reviews/review-
 walkthrough/ ) and the Author Lookup ( https://wordpress.org/plugins/wp-
 admin/tools.php?page=authorcards ) but is missing as a look up by IP.

 This would be very helpful to hunt down serial abusers.

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

From noreply at wordpress.org  Mon Apr  2 19:01:25 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  2 Apr 2018 19:01:25 +0000 (UTC)
Subject: [wp-meta] [6998]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15:
 WP15: Remove `alt` text from decorative images.
Message-ID: <20180402190125.458591B009AA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  2 19:01:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 19:01:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3541: WP15: Images with only
 visual value should have an empty alt attribute
In-Reply-To: <052.d087b5975289e15a04fcd3f410674526@wordpress.org>
References: <052.d087b5975289e15a04fcd3f410674526@wordpress.org>
Message-ID: <067.9086d5be86a18dc8b3973c7c95ab9bd2@wordpress.org>

#3541: WP15: Images with only visual value should have an empty alt attribute
---------------------------+-----------------------
 Reporter:  audrasjb       |       Owner:  Ian Dunn
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:  accessibility  |
---------------------------+-----------------------
Changes (by Ian Dunn):

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


Comment:

 In [changeset:"6998" 6998]:
 {{{
 #!CommitTicketReference repository="" revision="6998"
 WP15: Remove `alt` text from decorative images.

 Props audrasjb.
 Fixes #3541.
 }}}

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

From noreply at wordpress.org  Mon Apr  2 19:01:42 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 19:01:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3541: WP15: Images with only
 visual value should have an empty alt attribute
In-Reply-To: <052.d087b5975289e15a04fcd3f410674526@wordpress.org>
References: <052.d087b5975289e15a04fcd3f410674526@wordpress.org>
Message-ID: <067.10eba04387ae73a266f8d3159d7ee560@wordpress.org>

#3541: WP15: Images with only visual value should have an empty alt attribute
---------------------------+-----------------------
 Reporter:  audrasjb       |       Owner:  Ian Dunn
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:  accessibility  |
---------------------------+-----------------------

Comment (by Ian Dunn):

 Good catch, thanks!

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

From noreply at wordpress.org  Mon Apr  2 19:10:18 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  2 Apr 2018 19:10:18 +0000 (UTC)
Subject: [wp-meta] [6999]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Add space to make logo and About text more readable.
Message-ID: <20180402191018.B74F31B009AA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  2 19:26:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 19:26:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3512: Localization support
 for jobs.wordpress.net
In-Reply-To: <058.690e712fb63c195b2a7f45576a79b0b3@wordpress.org>
References: <058.690e712fb63c195b2a7f45576a79b0b3@wordpress.org>
Message-ID: <073.35ff37c0de47ee17153b99e201a586e9@wordpress.org>

#3512: Localization support for jobs.wordpress.net
---------------------------------------+---------------------
 Reporter:  claudiosanches             |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Jobs (jobs.wordpress.net)  |  Resolution:
 Keywords:  close                      |
---------------------------------------+---------------------

Comment (by djio):

 +1 High priority! :-)
 Thanks @claudiosanches awesome idea!

 Replying to [ticket:3512 claudiosanches]:
 > Jobs.wordpress.net is a wonderful tool that could be better used if it
 is possible to translate and maybe use sub-domains for each country, as
 it's are done with the Rosetta sites.

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

From noreply at wordpress.org  Mon Apr  2 19:26:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 02 Apr 2018 19:26:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3512: Localization support
 for jobs.wordpress.net
In-Reply-To: <058.690e712fb63c195b2a7f45576a79b0b3@wordpress.org>
References: <058.690e712fb63c195b2a7f45576a79b0b3@wordpress.org>
Message-ID: <073.794e058d8eafbe6dc8a63b0e9df3938d@wordpress.org>

#3512: Localization support for jobs.wordpress.net
---------------------------------------+---------------------
 Reporter:  claudiosanches             |       Owner:  (none)
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Jobs (jobs.wordpress.net)  |  Resolution:
 Keywords:  close                      |
---------------------------------------+---------------------

Comment (by djio):

 +1 High priority! :-)
 Thanks @claudiosanches awesome idea!

 Replying to [ticket:3512 claudiosanches]:
 > Jobs.wordpress.net is a wonderful tool that could be better used if it
 is possible to translate and maybe use sub-domains for each country, as
 it's are done with the Rosetta sites.

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

From noreply at wordpress.org  Mon Apr  2 19:35:30 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  2 Apr 2018 19:35:30 +0000 (UTC)
Subject: [wp-meta] [7000]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/addons/code-of-conduct.php:
 WordCamp tickets: Don't show the CoC checkbox on the edit ticket info
 screen
Message-ID: <20180402193531.02B6C1B000D7@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  2 23:26:59 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  2 Apr 2018 23:26:59 +0000 (UTC)
Subject: [wp-meta] [7001]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15:
 WP15 theme: Updates to Swag template, remove sub-template
Message-ID: <20180402232659.CAA5D1B000EA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  2 23:31:19 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  2 Apr 2018 23:31:19 +0000 (UTC)
Subject: [wp-meta] [7002]
 sites/trunk/wp15.wordpress.net/public_html/content: WP15: Add a search
 input for the event list.
Message-ID: <20180402233119.DB2F81B000EA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 00:10:39 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 00:10:39 +0000 (UTC)
Subject: [wp-meta] [7003]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins/locales.php:
 WP15: Add locale to cache key string
Message-ID: <20180403001039.D3DB21B00113@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 07:10:40 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 07:10:40 -0000
Subject: [wp-meta] [Making WordPress.org] #3543: Download History is not
 showing the exact stats for the newly uploaded plugin
In-Reply-To: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
References: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
Message-ID: <073.c375e75a2db956e3f2756ee40c4bead1@wordpress.org>

#3543: Download History is not showing the exact stats for the newly uploaded
plugin
------------------------------+----------------------
 Reporter:  abdullahramzan    |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------
Changes (by Dion Hulse):

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


Comment:

 The data for the downloads charts takes a little bit of data to be
 processed before it's actually accurate and useful.

 That being said, the screenshot provided seems correct to me.

 It's worth noting that not all downloads will show up in the graphs,
 there's some filtering in the processing scripts, and data may be delayed
 due to caching and nightly/hourly stat processing.

 If you believe there's something very wrong, and not just the numbers
 being slightly out, reply with further details so that it'll be easier to
 diagnose what's happening.

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

From noreply at wordpress.org  Tue Apr  3 08:19:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 08:19:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3543: Download History is not
 showing the exact stats for the newly uploaded plugin
In-Reply-To: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
References: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
Message-ID: <073.9f35724abf498bf4aecebe43b4bd28d0@wordpress.org>

#3543: Download History is not showing the exact stats for the newly uploaded
plugin
------------------------------+----------------------
 Reporter:  abdullahramzan    |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by abdullahramzan):

 Thanks for your feedback.

 Yes, still something wrong there. It released yesterday. Just sum the
 yesterday and today's downloads numbers and it should be 11 and it is
 showing 16.

 You can also check the release date of the plugin.

 Thanks,

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

From noreply at wordpress.org  Tue Apr  3 14:37:38 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 14:37:38 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
Message-ID: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
----------------------+-------------------------
 Reporter:  ChantalC  |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:
Component:  General   |   Keywords:  wp15, theme
----------------------+-------------------------
 When you scroll down, the menu bar gets a fixed position. However the
 language switcher scrolls out of the screen.

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

From noreply at wordpress.org  Tue Apr  3 14:37:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 14:37:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.34a668719c892d1e13939faf03be1de0@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------
Changes (by ChantalC):

 * Attachment "Schermafbeelding 2018-04-03 om 16.33.41.png" added.


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

From noreply at wordpress.org  Tue Apr  3 16:12:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 16:12:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.a7bf749683e3060f51ef907a4d922167@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by Ian Dunn):

 Which browser are you seeing that in?

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

From noreply at wordpress.org  Tue Apr  3 16:42:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 16:42:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.a053d2d1c5ab415390514a068d2e0442@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by ChantalC):

 Replying to [comment:1 Ian Dunn]:
 > Which browser are you seeing that in?

 Safari. In Chrome it also doesn't work nice.

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

From noreply at wordpress.org  Tue Apr  3 16:48:27 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 16:48:27 +0000 (UTC)
Subject: [wp-meta] [7004]
 sites/trunk/api.wordpress.org/public_html/core/credits/wp-49.php: Credits
 API: Update credits for WordPress 4.9.5.
Message-ID: <20180403164827.4EA991B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 17:56:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 17:56:40 +0000 (UTC)
Subject: [wp-meta] [7005] sites/trunk/wp15.wordpress.net/config-public.php:
 WP15: Set cookie path to `/` to allow front-end cookie reads.
Message-ID: <20180403175640.4DF4E1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 18:03:28 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 18:03:28 +0000 (UTC)
Subject: [wp-meta] [7006]
 sites/trunk/wp15.wordpress.net/public_html/content/wp-cache-config.php:
 WP15: Temporarily disable caching until it can support locale cookies.
Message-ID: <20180403180328.60F621B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:40:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 03 Apr 2018 20:40:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.76fc472fc15f2640c7e27ee80a0ffa5a@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by Ian Dunn):

 Hmmm, I can't reproduce it in either of those browsers, or Firefox.
 @coreymckrill, are you seeing it on your system?

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

From noreply at wordpress.org  Tue Apr  3 20:46:30 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:46:30 +0000 (UTC)
Subject: [wp-meta] [7007]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events:
 WP15: Add city and country names to search keys.
Message-ID: <20180403204630.7E7DB1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:46:34 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:46:34 +0000 (UTC)
Subject: [wp-meta] [7008]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events:
 WP15: Use `aria-hidden` attributes for better accessibility.
Message-ID: <20180403204634.5E0B71B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:46:38 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:46:38 +0000 (UTC)
Subject: [wp-meta] [7009]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events:
 WP15: Move Marker Clusterer to separate file to improve organization.
Message-ID: <20180403204638.431291B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:46:42 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:46:42 +0000 (UTC)
Subject: [wp-meta] [7010]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events:
 WP15: Apply coding standards.
Message-ID: <20180403204642.26C7A1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:46:46 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:46:46 +0000 (UTC)
Subject: [wp-meta] [7011]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events:
 WP15: Use `wp_localize_script()` to pass all data to JS.
Message-ID: <20180403204646.0EA8B1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:46:49 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:46:49 +0000 (UTC)
Subject: [wp-meta] [7012]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events:
 WP15: Notify screen readers when search results change dynamically.
Message-ID: <20180403204649.E515D1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 20:59:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 20:59:40 +0000 (UTC)
Subject: [wp-meta] [7013]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/functions.php:
 WP15 theme: Ensure Dashicons are loaded for logged out visitors
Message-ID: <20180403205940.C30911B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 21:58:15 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 21:58:15 +0000 (UTC)
Subject: [wp-meta] [7014]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Size and repeat the header background correctly in IE11.
Message-ID: <20180403215815.C638F1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 21:58:19 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 21:58:19 +0000 (UTC)
Subject: [wp-meta] [7015]
 sites/trunk/wp15.wordpress.net/public_html/content/wp-cache-config.php:
 WP15: Re-enable caching.
Message-ID: <20180403215819.695761B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr  3 23:21:42 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  3 Apr 2018 23:21:42 +0000 (UTC)
Subject: [wp-meta] [7016]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Add fallback styles for older browsers.
Message-ID: <20180403232142.BE3AD1B00245@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 00:07:39 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 00:07:39 +0000 (UTC)
Subject: [wp-meta] [7017]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Layer the small menu above the content area.
Message-ID: <20180404000739.978641B0025D@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 00:40:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 00:40:36 +0000 (UTC)
Subject: [wp-meta] [7018]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-logos.php:
 Main: About: Logos: Fix the URL to the `wmark` assets.
Message-ID: <20180404004036.A50C21B0025D@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 00:40:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 00:40:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.48e8f109017d583d4cbda3c96ba78fd9@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dion Hulse):

 In [changeset:"7018" 7018]:
 {{{
 #!CommitTicketReference repository="" revision="7018"
 Main: About: Logos: Fix the URL to the `wmark` assets.

 See #3046.
 }}}

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

From noreply at wordpress.org  Wed Apr  4 01:11:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 01:11:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.3b7ba2a16091febd6153125a83d42b01@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by coreymckrill):

 I can reproduce in Firefox and Chrome. When you scroll down the page past
 the site header, the navigation bar sticks to the top of the screen via
 some JS and CSS in the Twenty Seventeen parent theme. However, the
 language picker is not actually inside the navigation bar, and is added
 via the child theme, so it doesn't stick.

 Some possible solutions:

 * Move the language picker inside the nav bar, and then redo the CSS Grid
 styles to accommodate that.
 * Recreate the JS and CSS from the parent theme to work with the
 additional language picker element.
 * Let the picker disappear when scrolling down the page.

 Thoughts, @melchoyce?

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

From noreply at wordpress.org  Wed Apr  4 01:16:12 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 01:16:12 +0000 (UTC)
Subject: [wp-meta] [7019]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Fix header image dimensions on IE11.
Message-ID: <20180404011612.637541B0025D@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 01:19:44 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 01:19:44 -0000
Subject: [wp-meta] [Making WordPress.org] #957: Create a community Code
 of Conduct
In-Reply-To: <053.003b95e85f7c7cb56c4aa3750a9b223d@wordpress.org>
References: <053.003b95e85f7c7cb56c4aa3750a9b223d@wordpress.org>
Message-ID: <068.a2164a65f7e458d23ed85aec8f894cd8@wordpress.org>

#957: Create a community Code of Conduct
-------------------------+---------------------
 Reporter:  Mel Choyce   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by Stephen Edgar):

 Via https://make.wordpress.org/community/2018/04/03/code-of-conduct-
 survey/

 > Code of Conduct Survey
 >
 > Our Code of Conduct survey is live!
 >
 > The Community Code of Conduct project goal is to examine the potential
 of expanding the community team’s code of conduct for WordPress events, to
 include other spaces where WordPress contributors collaborate, including
 forums, websites, and official chat channels.
 >
 > We have put together a short survey to help us assess what we need to be
 is where you come in! Please announce this survey to your meetup group,
 and share it as widely as you can within the WordPress community. The
 survey will be open until April 13, so please share it soon and don’t
 forget to take the survey yourself: https://18422602.polldaddy.com/s
 /community-code-of-conduct-survey

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

From noreply at wordpress.org  Wed Apr  4 02:06:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 02:06:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3543: Download History is not
 showing the exact stats for the newly uploaded plugin
In-Reply-To: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
References: <058.cfac5bedcf05e0993690e63e393d4c06@wordpress.org>
Message-ID: <073.cbacb135b3037b709480fb99bab8e027@wordpress.org>

#3543: Download History is not showing the exact stats for the newly uploaded
plugin
------------------------------+----------------------
 Reporter:  abdullahramzan    |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by Dion Hulse):

 It's correct.

 Regardless, we no longer have logs to investigate this. So it's staying
 as-is.

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

From noreply at wordpress.org  Wed Apr  4 02:56:48 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 02:56:48 +0000 (UTC)
Subject: [wp-meta] [7020]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump scripts
 version to ensure that the Trac template update works.
Message-ID: <20180404025648.37D1C1B0025D@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 03:05:25 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 03:05:25 +0000 (UTC)
Subject: [wp-meta] [7021]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/readme:
 Plugin Directory: Readme Validator: Add a warning when a contributor in the
 readme is ignored.
Message-ID: <20180404030525.368CA1B0025D@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 03:05:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 03:05:25 -0000
Subject: [wp-meta] [Making WordPress.org] #249: More Plugin API Encoding
 Issues
In-Reply-To: <050.832d7704913dcdef7519734add385a70@wordpress.org>
References: <050.832d7704913dcdef7519734add385a70@wordpress.org>
Message-ID: <065.54f4685c67fc3947adcbcbe600bf333b@wordpress.org>

#249: More Plugin API Encoding Issues
-------------------------------+-------------------------
 Reporter:  Bryan Petty        |       Owner:  Dion Hulse
     Type:  defect             |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  API                |  Resolution:  fixed
 Keywords:  reporter-feedback  |
-------------------------------+-------------------------
Changes (by Dion Hulse):

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


Comment:

 In [changeset:"7021" 7021]:
 {{{
 #!CommitTicketReference repository="" revision="7021"
 Plugin Directory: Readme Validator: Add a warning when a contributor in
 the readme is ignored.

 Fixes #249.
 }}}

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

From noreply at wordpress.org  Wed Apr  4 03:10:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 03:10:56 -0000
Subject: [wp-meta] [Making WordPress.org] #2844: Javascript Access to
 Meta API disallowed CORS policy
In-Reply-To: <052.b056a26e8305a5ab509f7f73a9afdc7e@wordpress.org>
References: <052.b056a26e8305a5ab509f7f73a9afdc7e@wordpress.org>
Message-ID: <067.9a14b8df5ecb0827d4006dfadb60a3ed@wordpress.org>

#2844: Javascript Access to Meta API disallowed CORS policy
----------------------+-------------------------
 Reporter:  eddhurst  |       Owner:  Dion Hulse
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  API       |  Resolution:  fixed
 Keywords:            |
----------------------+-------------------------
Changes (by Dion Hulse):

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


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

From noreply at wordpress.org  Wed Apr  4 03:11:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 03:11:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3513: FAQ links cause a file
 download dialog with mediawiki blurb within
In-Reply-To: <053.0c5b206fc2f54732cf64c849f6d2de7d@wordpress.org>
References: <053.0c5b206fc2f54732cf64c849f6d2de7d@wordpress.org>
Message-ID: <068.a2768d5e013e671844e323825e400f7c@wordpress.org>

#3513: FAQ links cause a file download dialog with mediawiki blurb within
-----------------------------+-------------------------
 Reporter:  diddledan        |       Owner:  Dion Hulse
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Codex            |  Resolution:
 Keywords:  pending-systems  |
-----------------------------+-------------------------
Changes (by Dion Hulse):

 * keywords:   => pending-systems


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

From noreply at wordpress.org  Wed Apr  4 03:40:06 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 03:40:06 -0000
Subject: [wp-meta] [Making WordPress.org] #3528: Disable auto zoom in
 the Header Search Box on mobile
In-Reply-To: <052.7c14755f59f6bbee86799e89532c7fbe@wordpress.org>
References: <052.7c14755f59f6bbee86799e89532c7fbe@wordpress.org>
Message-ID: <067.788f8ec6e69b80b0f4c5e7e43258015c@wordpress.org>

#3528: Disable auto zoom in the Header Search Box on mobile
-------------------------------------------------+-------------------------
 Reporter:  raajtram                             |       Owner:  Dion Hulse
     Type:  defect                               |      Status:  reviewing
 Priority:  normal                               |   Milestone:
Component:  General                              |  Resolution:
 Keywords:  has-patch has-screenshots needs-     |
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by Dion Hulse):

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


Comment:

 I'm unable to test this, due to not having an iphone and Safari dev mode
 seemingly not supporting the zoom functionality.

 Can someone please verify that this patch works as expected and doesn't
 have any side effects?

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

From noreply at wordpress.org  Wed Apr  4 08:11:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 08:11:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3338: Plugin author search
 doesn't return relevant results
In-Reply-To: <059.2dfb588bcd0763c53e0aef14e3199756@wordpress.org>
References: <059.2dfb588bcd0763c53e0aef14e3199756@wordpress.org>
Message-ID: <074.ab9fd7459a447208caf98b568e853152@wordpress.org>

#3338: Plugin author search doesn't return relevant results
------------------------------+------------------------------
 Reporter:  magicroundabout   |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Improved Search
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------------
Changes (by Stephen Edgar):

 * milestone:   => Improved Search


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

From noreply at wordpress.org  Wed Apr  4 12:37:32 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 12:37:32 +0000 (UTC)
Subject: [wp-meta] [7022]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/support-forums/inc/class-ratings-compat.php:
 Support Forums: Make the language and appearance of "must be logged in"
 notice consistent between reviews and support topics.
Message-ID: <20180404123732.100DB1B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 13:02:08 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 13:02:08 -0000
Subject: [wp-meta] [Making WordPress.org] #3546: Plugin Directory: Improve
 i18n in readme validator
Message-ID: <058.8a01dae2b37a4cc0e2e4622c91207ee4@wordpress.org>

#3546: Plugin Directory: Improve i18n in readme validator
------------------------------+--------------------
 Reporter:  Sergey Biryukov   |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 Strings like these are impossible to translate without looking at the
 source:

 * `No %s listed.`
 * `One or more %1$s listed were ignored.`

 The `Plugin header tag` translator comment doesn't clarify things either.

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

From noreply at wordpress.org  Wed Apr  4 13:02:30 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 13:02:30 +0000 (UTC)
Subject: [wp-meta] [7023]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/readme/class-validator.php:
 Plugin Directory: Make readme validator strings more i18n-friendly.
Message-ID: <20180404130230.4999A1B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 13:02:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 13:02:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3546: Plugin Directory:
 Improve i18n in readme validator
In-Reply-To: <058.8a01dae2b37a4cc0e2e4622c91207ee4@wordpress.org>
References: <058.8a01dae2b37a4cc0e2e4622c91207ee4@wordpress.org>
Message-ID: <073.51917de6532aa0513918bdb235488ed1@wordpress.org>

#3546: Plugin Directory: Improve i18n in readme validator
------------------------------+------------------------------
 Reporter:  Sergey Biryukov   |       Owner:  Sergey Biryukov
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+------------------------------
Changes (by Sergey Biryukov):

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


Comment:

 In [changeset:"7023" 7023]:
 {{{
 #!CommitTicketReference repository="" revision="7023"
 Plugin Directory: Make readme validator strings more i18n-friendly.

 Fixes #3546.
 }}}

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

From noreply at wordpress.org  Wed Apr  4 14:47:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 14:47:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3547: Automate release revision
 numbers in Polyglots handbook
Message-ID: <058.c8ba7da62eb9e1c4d30efca98ce5f160@wordpress.org>

#3547: Automate release revision numbers in Polyglots handbook
--------------------------------------+--------------------
 Reporter:  Sergey Biryukov           |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+--------------------
 The Polyglots handbook has a table of
 [https://make.wordpress.org/polyglots/handbook/translating/packaging-
 localized-wordpress/#release-revisions release revision numbers] for
 locales that still need to build localized WordPress packages manually.

 With 200+ releases, copy/pasting those numbers from
 [https://build.trac.wordpress.org/browser/tags?order=date&desc=1 Build
 Trac] is a tedious task prone to errors. The page should be able to scrape
 them automatically.

 Alternatively, we could probably just remove the table and link to Build
 Trac directly, with some explanation of what column to look at.

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

From noreply at wordpress.org  Wed Apr  4 15:24:02 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 15:24:02 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.ce9e70a26351cc31b3cf63ec4c6894da@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by Mel Choyce):

 > Move the language picker inside the nav bar, and then redo the CSS Grid
 styles to accommodate that.
 > Recreate the JS and CSS from the parent theme to work with the
 additional language picker element.

 What's the difference between these two options?

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

From noreply at wordpress.org  Wed Apr  4 16:37:16 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 16:37:16 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.53ce9c6e71c55b0433e25af3afd9e871@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by coreymckrill):

 Replying to [comment:5 Mel Choyce]:
 > > Move the language picker inside the nav bar, and then redo the CSS
 Grid styles to accommodate that.
 > > Recreate the JS and CSS from the parent theme to work with the
 additional language picker element.
 >
 > What's the difference between these two options?

 The first one requires overriding the parent theme's '''template-
 parts/navigation/navigation-top.php''' so that it includes the language
 switcher template tag, plus a reworking of the CSS grid.

 The second one leaves the language switcher template tag where it is in
 the child theme's '''header.php''' file, but would potentially require
 duplicating some of the parent theme's JS to add a new class to the
 switcher's container when the viewport scrolls down past the header.

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

From noreply at wordpress.org  Wed Apr  4 16:52:33 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 16:52:33 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.4a08e72faf26577b182543c23d4ded91@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by Mel Choyce):

 Thanks for the explanation :) Which one seems like less of a hassle to
 you?

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

From noreply at wordpress.org  Wed Apr  4 19:05:47 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 19:05:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.95d10f79febcc5b57f189ffda93fc66a@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by coreymckrill):

 Replying to [comment:7 Mel Choyce]:
 > Thanks for the explanation :) Which one seems like less of a hassle to
 you?

 I mean, the least hassle would be letting the switcher disappear. Is that
 a viable option?

 Of the other two, I already tried the first approach and got bogged down
 in weird CSS grid stuff, so I would probably try the second approach.

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

From noreply at wordpress.org  Wed Apr  4 19:07:49 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 19:07:49 +0000 (UTC)
Subject: [wp-meta] [7024]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-accessibility.php:
 Main: About: Update URL for accessibility tools.
Message-ID: <20180404190749.B11A41B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 19:07:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 19:07:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.4ff6520c4ddc7c709ff8c76dbab27773@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dominik Schilling):

 In [changeset:"7024" 7024]:
 {{{
 #!CommitTicketReference repository="" revision="7024"
 Main: About: Update URL for accessibility tools.

 See #3046.
 }}}

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

From noreply at wordpress.org  Wed Apr  4 19:18:25 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 19:18:25 +0000 (UTC)
Subject: [wp-meta] [7025]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php:
 Main: About: Remove footnote references in translatable strings.
Message-ID: <20180404191825.6992E1B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 19:18:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 19:18:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.d9d1da1831a5a66dac83a4566ac74d54@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dominik Schilling):

 In [changeset:"7025" 7025]:
 {{{
 #!CommitTicketReference repository="" revision="7025"
 Main: About: Remove footnote references in translatable strings.

 See #3046.
 }}}

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

From noreply at wordpress.org  Wed Apr  4 19:21:35 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 19:21:35 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.4caeba6e4032109977a8d34de9bbeb2d@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by Mel Choyce):

 Replying to [comment:8 coreymckrill]:
 > Replying to [comment:7 Mel Choyce]:
 > > Thanks for the explanation :) Which one seems like less of a hassle to
 you?
 >
 > I mean, the least hassle would be letting the switcher disappear. Is
 that a viable option?

 I feel like as an English speaker, it's not effecting me, so I'd prefer to
 hear more from our non-English speaking community before making that kind
 of decision. Let's see if we can get some more input.

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

From noreply at wordpress.org  Wed Apr  4 19:23:44 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 19:23:44 +0000 (UTC)
Subject: [wp-meta] [7026]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php:
 Main: About: Use HTTPS when available.
Message-ID: <20180404192344.A578D1B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 19:23:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 19:23:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.afc37c42057676a266a5182c7ae458cd@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dominik Schilling):

 In [changeset:"7026" 7026]:
 {{{
 #!CommitTicketReference repository="" revision="7026"
 Main: About: Use HTTPS when available.

 See #3046.
 }}}

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

From noreply at wordpress.org  Wed Apr  4 19:41:21 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 19:41:21 +0000 (UTC)
Subject: [wp-meta] [7027]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-payments/includes/sponsor-payment-stripe.php:
 WordCamp Payments: Verify payload signature before unslashing data.
Message-ID: <20180404194121.815641B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 19:41:25 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  4 Apr 2018 19:41:25 +0000 (UTC)
Subject: [wp-meta] [7028]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-payments/includes/sponsor-payment-stripe.php:
 WordCamp Payments: Apply coding standards.
Message-ID: <20180404194125.5A61A1B00252@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr  4 20:40:47 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 20:40:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.24fa2e64518f5fc3b02a94f3177b7eec@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------
 Reporter:  ChantalC     |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:  wp15, theme  |
-------------------------+---------------------

Comment (by mcsf):

 > I mean, the least hassle would be letting the switcher disappear. Is
 that a viable option?

 My two cents as someone of a different mothertongue is that it's less
 about the switcher not being always available, and more that it disappears
 unexpectedly ("I thought there was a thingy to change the language?")

 > The first one requires overriding the parent theme's template-
 parts/navigation/navigation-top.php so that it includes the language
 switcher template tag, plus a reworking of the CSS grid.

 I'm not familiar with this domain, but is the parent theme
 `twentyseventeen`? Because, if so, changing it doesn't sound like the best
 idea. Or is the parent some other niche theme with less inertia that I may
 have missed?

 Approach two seems viable. A drive-by suggestion, if you'd like to avoid
 duplicating the element-fixing logic from the parent, is to use something
 like `MutationObserver` to react to changes to `.navigation-top`'s
 classes, synchronizing with the local switcher.

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

From noreply at wordpress.org  Wed Apr  4 20:56:35 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 20:56:35 -0000
Subject: [wp-meta] [Making WordPress.org] #3481: Suggestion - Redirect
 wordpress.org/security to right page
In-Reply-To: <051.7b3187827c7e73697fb4b918a8a7c863@wordpress.org>
References: <051.7b3187827c7e73697fb4b918a8a7c863@wordpress.org>
Message-ID: <066.f51d069f4800dcb50fdaad89d4ed694c@wordpress.org>

#3481: Suggestion - Redirect wordpress.org/security to right page
---------------------+---------------------
 Reporter:  mbabker  |       Owner:  (none)
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------
Changes (by Dominik Schilling):

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


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

From noreply at wordpress.org  Wed Apr  4 21:16:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 21:16:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3548: Add simplified logo back to
 the Graphics and Logos page
Message-ID: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>

#3548: Add simplified logo back to the Graphics and Logos page
-------------------------+--------------------------
 Reporter:  mapk         |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  high         |  Milestone:
Component:  General      |   Keywords:  about, logos
-------------------------+--------------------------
 In the transition to the new design, I lost the simplified WordPress logo
 from the Graphic and Logos page. We need to add it back.

 [[Image(https://cldup.com/hkAuF67LPx.png)]]

 It needs to be included on this page: https://wordpress.org/about/logos/
 and with the same styling as the others.

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

From noreply at wordpress.org  Wed Apr  4 21:19:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 21:19:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3548: Add simplified logo
 back to the Graphics and Logos page
In-Reply-To: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>
References: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>
Message-ID: <063.72980196080574a4f6f683583ed91095@wordpress.org>

#3548: Add simplified logo back to the Graphics and Logos page
--------------------------+---------------------
 Reporter:  mapk          |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  high          |   Milestone:
Component:  General       |  Resolution:
 Keywords:  about, logos  |
--------------------------+---------------------

Comment (by mapk):

 Props to @nickhamze for finding this.

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

From noreply at wordpress.org  Wed Apr  4 22:06:43 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 22:06:43 -0000
Subject: [wp-meta] [Making WordPress.org] #45: Theme repository - add
 changelog listing tab
In-Reply-To: <060.3ce3afaaf6614b8cc4df6327d5431801@wordpress.org>
References: <060.3ce3afaaf6614b8cc4df6327d5431801@wordpress.org>
Message-ID: <075.fc44c05dc07d3493ec84e40b493e93b3@wordpress.org>

#45: Theme repository - add changelog listing tab
-----------------------------+---------------------
 Reporter:  Mario Peshev     |       Owner:  (none)
     Type:  task             |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+---------------------

Comment (by joyously):

 For reference, here are current screenshots of a theme page and a plugin
 page.
 [[Image(https://s9.postimg.org/qxxxyqna7/Twenty_Seventeen_Free_Word_Press_Themes-5757.jpg)]]
 [[Image(https://s9.postimg.org/p64z3tw7j/bb_Press_Word_Press_Plugins-0017.jpg)]]

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

From noreply at wordpress.org  Wed Apr  4 22:12:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 22:12:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3549: Meetings : Add shared
 calendar feed
Message-ID: <054.7e7e3d57b36fff1b9618b5a5fca81294@wordpress.org>

#3549: Meetings : Add shared calendar feed
--------------------------------------+-------------------------
 Reporter:  mindmantra                |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:  needs-patch
--------------------------------------+-------------------------
 It gets tricky to keep oneself informed about team meetings listed in
 https://make.wordpress.org/meetings/

 While having this page makes things smoother, it is still not widely
 consumable and doesn't support any notifications or highlights
 changes/deviations. So any deviation/change in meetings can not be
 communicated to users unless they manually check the change or read post,
 if any, in Make blog.

 An ideal solution would be to have a shared calendar feed so one can
 easily integrate it with their choice of calendar solution.

 I propose to use widely supported iCal format to create such feed.

 But this needs considerations on below issues:
 1. How many previous and future meetings should be included in feed?
 2. Should it follow current meeting page? Then is it wise to remove all
 the events other than those published?
 3. Should recurring meetings be marked as recurring? If yes, then how to
 tackle future updates or one-off changes?
 4. Have static .ics file generated post each edit and served from uploads
 folder? or have a dynamic URI/end-point and let caching mechanism handle
 generated feed?

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

From noreply at wordpress.org  Wed Apr  4 22:16:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 22:16:52 -0000
Subject: [wp-meta] [Making WordPress.org] #1658: Meetings: Add a
 calendar view
In-Reply-To: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org>
References: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org>
Message-ID: <066.a745c8c3e4fd3655bb89b1cd31b860cf@wordpress.org>

#1658: Meetings: Add a calendar view
--------------------------------------+-----------------------
 Reporter:  Dominik Schilling         |       Owner:  (none)
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch needs-ui      |
--------------------------------------+-----------------------

Comment (by Stephen Edgar):

 Related: #2955 iCal feed for the entire meetings page

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

From noreply at wordpress.org  Wed Apr  4 22:31:11 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 22:31:11 -0000
Subject: [wp-meta] [Making WordPress.org] #1658: Meetings: Add a
 calendar view
In-Reply-To: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org>
References: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org>
Message-ID: <066.a11bfbd2d5319bb23313f5e78a645595@wordpress.org>

#1658: Meetings: Add a calendar view
--------------------------------------+-----------------------
 Reporter:  Dominik Schilling         |       Owner:  (none)
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch needs-ui      |
--------------------------------------+-----------------------

Comment (by mindmantra):

 This one is different then iCal ticket.

 iCal provides way to have a synchronised calendar with a calendar app of
 user's choice whereas this ticket tackles the '''calendar view''' for the
 meetings page.

 So this should make it more consumable for an user surfing the meetings
 page, while #2955 should work to get shared calendar without the need to
 revisit the page.

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

From noreply at wordpress.org  Wed Apr  4 22:36:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 22:36:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3550: Plugins search with
 countdown keyword does not work
Message-ID: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>

#3550: Plugins search with countdown keyword does not work
------------------------------+-----------------------------------
 Reporter:  adamskaat         |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  high              |  Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |   Keywords:  countdown
------------------------------+-----------------------------------
 Today I tried the search with one keyword (Countdown) but it's return
 nothing you can check this URL
 https://wordpress.org/plugins/search/countdown/

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

From noreply at wordpress.org  Wed Apr  4 23:12:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 23:12:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2955: iCal feed for the
 entire meetings page
In-Reply-To: <054.5f93d79015d3a2aab190dbdbd27b38d6@wordpress.org>
References: <054.5f93d79015d3a2aab190dbdbd27b38d6@wordpress.org>
Message-ID: <069.b2682019f5722b4ca62dcf99bdcf94fc@wordpress.org>

#2955: iCal feed for the entire meetings page
--------------------------------------+---------------------
 Reporter:  schlessera                |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by mindmantra):

 iCalendar Specifications RFC is updated to
 https://www.ietf.org/rfc/rfc5545.txt

 As suggested in ticket description, there is not a need to have a full
 calendar functionality. From available data an iCal can be generated
 dynamically.

 Using endpoints would also make it easy to have near realtime updates
 pushed to clients.

 @schlessera in your suggestion {{{/ical}}} a namespace or custom endpoint
 to core WP api namespace?

 This post type is added using a separate plugin in WP.org See
 [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/plugins/wporg-meeting-posttype
 /sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-meeting-
 posttype]

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

From noreply at wordpress.org  Wed Apr  4 23:16:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 04 Apr 2018 23:16:54 -0000
Subject: [wp-meta] [Making WordPress.org] #3550: Plugins search with
 countdown keyword does not work
In-Reply-To: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>
References: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>
Message-ID: <068.e9658a31f083152767b9ae035bb555b5@wordpress.org>

#3550: Plugins search with countdown keyword does not work
------------------------------+------------------------------
 Reporter:  adamskaat         |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Improved Search
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------------
Changes (by Stephen Edgar):

 * keywords:  countdown =>
 * priority:  high => normal
 * milestone:  Plugin Directory v3.0 => Improved Search


Comment:

 I believe this is most like as noted in #3327:

 https://meta.trac.wordpress.org/ticket/3327#comment:3
 > ...these plugins are not showing at or near the top for the same reason:
 they don't have the Tested up to: header set.
 > Setting that to a recent WordPress version (after testing of course!)
 should restore the expected behaviour.

 https://meta.trac.wordpress.org/ticket/3327#comment:5
 > If a plugin doesn't have proper headers, and it hasn't been updated in a
 while, then it should be harder to find

 The https://wordpress.org/plugins/countdown/ hasn't been updated in 6+
 years

 https://meta.trac.wordpress.org/ticket/3327#comment:6
 > I hear all the arguments for not wanting to surface older plugins to
 people who aren't looking for them. But there's still this specific case
 of knowing which plugin you want to install, and not being able to find or
 install it.

 Searching https://wordpress.org/plugins/search/countdown/ results in no
 results found

 I'm leaning towards that the search results should surface the
 ''countdown'' plugin rather than return no results though how that impacts
 search as a whole I'm not sure of and will defer to the meta eam members
 familiar with this.

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

From noreply at wordpress.org  Thu Apr  5 00:08:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 00:08:34 -0000
Subject: [wp-meta] [Making WordPress.org] #3549: Meetings : Add shared
 calendar feed
In-Reply-To: <054.7e7e3d57b36fff1b9618b5a5fca81294@wordpress.org>
References: <054.7e7e3d57b36fff1b9618b5a5fca81294@wordpress.org>
Message-ID: <069.9202e5609ddcf32793e41ff3431a2125@wordpress.org>

#3549: Meetings : Add shared calendar feed
--------------------------------------+---------------------
 Reporter:  mindmantra                |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+---------------------

Comment (by Otto):

 Dupe of #2955. Will mark as such when trac is fixed.

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

From noreply at wordpress.org  Thu Apr  5 01:08:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 01:08:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3548: Add simplified logo
 back to the Graphics and Logos page
In-Reply-To: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>
References: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>
Message-ID: <063.8a195ba87d4faed0efaf90de36402460@wordpress.org>

#3548: Add simplified logo back to the Graphics and Logos page
-------------------------+---------------------
 Reporter:  mapk         |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  high         |   Milestone:
Component:  General      |  Resolution:
 Keywords:  about logos  |
-------------------------+---------------------
Changes (by Dion Hulse):

 * keywords:  about, logos => about logos


Comment:

 @mapk Do you have the assets for this?

 From what I can tell, the assets which were previously linked differ from
 what is now linked significantly.
 If you need a copy of the previous ones, they're still in their original
 locations:
  - https://s.w.org/about/images/logos/wordpress-logo-simplified-cmyk.pdf
  - https://s.w.org/about/images/logos/wordpress-logo-simplified-rgb.png

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

From noreply at wordpress.org  Thu Apr  5 01:11:58 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 01:11:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.894a6a944a70e169bb84056f8fb4487d@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-------------------------
 Reporter:  Mel Choyce                    |       Owner:  Dion Hulse
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-------------------------

Comment (by Dion Hulse):

 Replying to [comment:161 Dominik Schilling]:
 > In [changeset:"7026" 7026]:
 > {{{
 > #!CommitTicketReference repository="" revision="7026"
 > Main: About: Use HTTPS when available.
 >
 > See #3046.
 > }}}

 @ocean90  Could you please ensure that any changes you've made to the
 whitepaper are pushed to it's primary location -
 https://github.com/WordPress/Security-White-Paper ? otherwise there's
 going to be conflicts with trying to merge it back into the page, etc.

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

From noreply at wordpress.org  Thu Apr  5 02:08:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 02:08:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3549: Meetings : Add shared
 calendar feed
In-Reply-To: <054.7e7e3d57b36fff1b9618b5a5fca81294@wordpress.org>
References: <054.7e7e3d57b36fff1b9618b5a5fca81294@wordpress.org>
Message-ID: <069.a4e951d5188d7a19ccac9b6c83d61f33@wordpress.org>

#3549: Meetings : Add shared calendar feed
--------------------------------------+------------------------
 Reporter:  mindmantra                |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  duplicate
 Keywords:  needs-patch               |
--------------------------------------+------------------------
Changes (by 762e5e74):

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


Comment:

 Duplicate of #2955.

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

From noreply at wordpress.org  Thu Apr  5 02:28:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 02:28:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.d52513820327805c9e4f1b1f7098545b@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-------------------------
 Reporter:  Dion Hulse        |       Owner:  Dion Hulse
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-------------------------
Changes (by Dion Hulse):

 * owner:  Otto => Dion Hulse


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

From noreply at wordpress.org  Thu Apr  5 04:11:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 04:11:34 -0000
Subject: [wp-meta] [Making WordPress.org] #2606: Inaccurate plugin
 rating counts
In-Reply-To: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
References: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
Message-ID: <066.02aedadec593d6226e72f705deec7a1f@wordpress.org>

#2606: Inaccurate plugin rating counts
------------------------------+------------------------------------
 Reporter:  svenl77           |       Owner:  Otto
     Type:  defect            |      Status:  assigned
 Priority:  low               |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+------------------------------------
Changes (by Dion Hulse):

 * priority:  normal => low


Comment:

 Just noting that it looks like some plugins post_meta got out of sync, due
 to the cron only picking up recently added reviews. Removing a review
 doesn't trigger any syncing and that causes it to ultimately be out of
 date.

 When a spam review is removed, the next review added after that will
 trigger the resync. Because the action of adding a new review clears out
 the bad data, this makes this even more low-priority in my eyes.

 Fixing this by using the underlying `WPORG_Ratings` class rather than post
 meta would probably make sense.
 As a temporary work around I just ran a script to resync all the rating
 counts (commit following)

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

From noreply at wordpress.org  Thu Apr  5 04:13:09 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 04:13:09 +0000 (UTC)
Subject: [wp-meta] [7029]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/bin/resync-ratings.php:
 Plugin Directory: Ratings/Reviews: Add a bin script to resync the
 underlying ratings data to plugin post_meta
Message-ID: <20180405041309.6931B1B0030F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 04:13:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 04:13:10 -0000
Subject: [wp-meta] [Making WordPress.org] #2606: Inaccurate plugin
 rating counts
In-Reply-To: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
References: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
Message-ID: <066.7006b6364174304a4cce609c9e35eba2@wordpress.org>

#2606: Inaccurate plugin rating counts
------------------------------+------------------------------------
 Reporter:  svenl77           |       Owner:  Otto
     Type:  defect            |      Status:  assigned
 Priority:  low               |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+------------------------------------

Comment (by Dion Hulse):

 In [changeset:"7029" 7029]:
 {{{
 #!CommitTicketReference repository="" revision="7029"
 Plugin Directory: Ratings/Reviews: Add a bin script to resync the
 underlying ratings data to plugin post_meta
 Sometimes the post_meta gets out of sync with the ratings system data due
 to spam reviews being removed (which don't trigger a sync) and no new
 reviews being added to the plugin for a while. During that time the plugin
 will have the previous review count, and only adding a new review will
 clear that cache.

 See #2606.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 04:16:43 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 04:16:43 +0000 (UTC)
Subject: [wp-meta] [7030]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/bin/resync-ratings.php:
 Plugin Directory: Ratings/Reviews: Enhance the bin script from r7029 to
 also operate on a singular plugin.
Message-ID: <20180405041643.70E8B1B0030F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 04:16:44 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 04:16:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2606: Inaccurate plugin
 rating counts
In-Reply-To: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
References: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
Message-ID: <066.d3bac6a8d2ca500c06f7ce7da0792fdf@wordpress.org>

#2606: Inaccurate plugin rating counts
------------------------------+------------------------------------
 Reporter:  svenl77           |       Owner:  Otto
     Type:  defect            |      Status:  assigned
 Priority:  low               |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+------------------------------------

Comment (by Dion Hulse):

 In [changeset:"7030" 7030]:
 {{{
 #!CommitTicketReference repository="" revision="7030"
 Plugin Directory: Ratings/Reviews: Enhance the bin script from r7029 to
 also operate on a singular plugin.

 See #2606.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 04:18:08 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 04:18:08 -0000
Subject: [wp-meta] [Making WordPress.org] #2606: Inaccurate plugin
 rating counts
In-Reply-To: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
References: <051.0bf781f8f7524fa1b946e2cf4dbff5bb@wordpress.org>
Message-ID: <066.71452f2813c6d33e8268a2073624e413@wordpress.org>

#2606: Inaccurate plugin rating counts
------------------------------+------------------------------------
 Reporter:  svenl77           |       Owner:  Otto
     Type:  defect            |      Status:  assigned
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+------------------------------------
Changes (by Dion Hulse):

 * priority:  low => normal


Comment:

 As I hit enter on the commit, I realised that this is a little more of an
 issue for plugins who have a bunch of spam 5-star reviews removed. As such
 I added a parameter to allow devs to sync a singular plugins ratings too

 Because of 5-star spam reviews, fixing this is a little more important.

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

From noreply at wordpress.org  Thu Apr  5 04:22:27 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 04:22:27 +0000 (UTC)
Subject: [wp-meta] [7031]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15:
 WP15 theme: Keep locale switcher in nav bar when it becomes sticky
Message-ID: <20180405042227.1ECB41B0030F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 04:22:27 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 04:22:27 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.af4d462aa8cdda1d70af38b3b326a21a@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
-------------------------+---------------------------
 Reporter:  ChantalC     |       Owner:  coreymckrill
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:  fixed
 Keywords:  wp15, theme  |
-------------------------+---------------------------
Changes (by coreymckrill):

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


Comment:

 In [changeset:"7031" 7031]:
 {{{
 #!CommitTicketReference repository="" revision="7031"
 WP15 theme: Keep locale switcher in nav bar when it becomes sticky

 Ensure that the nav bar, with all navigation items and the locale
 switcher,
 remains intact and unchanged when scrolling down past the site header,
 which
 causes the bar to become fixed at the top.

 This also changes the layout of the nav bar on narrow screens so that the
 locale switcher and the menu toggle button are on separate rows, with the
 switcher first, allowing the toggled menu items to expand beneath.

 Fixes #3545
 Props coreymckrill, melchoyce, mcsf
 }}}

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

From noreply at wordpress.org  Thu Apr  5 04:29:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 04:29:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3545: WP15 Theme: Language
 switcher doesn't get fixed when scrolling
In-Reply-To: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
References: <052.bec9dd3a27b6a236eac6dcfb70cf1b94@wordpress.org>
Message-ID: <067.aafd8ca726c5d2d29d8b2d58a717ce86@wordpress.org>

#3545: WP15 Theme: Language switcher doesn't get fixed when scrolling
------------------------+---------------------------
 Reporter:  ChantalC    |       Owner:  coreymckrill
     Type:  defect      |      Status:  closed
 Priority:  normal      |   Milestone:
Component:  General     |  Resolution:  fixed
 Keywords:  wp15 theme  |
------------------------+---------------------------
Changes (by coreymckrill):

 * keywords:  wp15, theme => wp15 theme


Comment:

 @melchoyce @mcsf Thanks for helping me think through this!

 @mcsf and thanks for the pointer about `MutationObserver`. Today I
 learned.

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

From noreply at wordpress.org  Thu Apr  5 05:15:12 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 05:15:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2771: Plugin Directory:
 Direct access to changelog via #changelog in URL not working anymore
In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
Message-ID: <067.b2a8645971b2092d56bf8a87cd27945e@wordpress.org>

#2771: Plugin Directory: Direct access to changelog via #changelog in URL not
working anymore
------------------------------+------------------------------------
 Reporter:  galbaras          |       Owner:  Dion Hulse
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------------------
Changes (by Dion Hulse):

 * owner:  Otto => Dion Hulse


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

From noreply at wordpress.org  Thu Apr  5 05:16:44 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 05:16:44 +0000 (UTC)
Subject: [wp-meta] [7032]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins:
 Plugin Directory: Make `#changelog` open the Development tab by default.
Message-ID: <20180405051644.D6CFE1B003F5@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 05:16:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 05:16:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2771: Plugin Directory:
 Direct access to changelog via #changelog in URL not working anymore
In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
Message-ID: <067.716f9b5f6eed6324841f2cf93a581a1d@wordpress.org>

#2771: Plugin Directory: Direct access to changelog via #changelog in URL not
working anymore
------------------------------+------------------------------------
 Reporter:  galbaras          |       Owner:  Dion Hulse
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+------------------------------------
Changes (by Dion Hulse):

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


Comment:

 In [changeset:"7032" 7032]:
 {{{
 #!CommitTicketReference repository="" revision="7032"
 Plugin Directory: Make `#changelog` open the Development tab by default.

 Due to how the tab pre-selection is specified in CSS, it's unfortunately
 not possible to scroll to the correct position, but this at least opens
 the correct tab.

 Fixes #2771.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 05:20:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 05:20:40 +0000 (UTC)
Subject: [wp-meta] [7033]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/css:
 Plugin Directory: Rebuild CSS after r7032 which included an out-of-date
 style.css.
Message-ID: <20180405052040.E87171B003F5@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 05:20:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 05:20:41 -0000
Subject: [wp-meta] [Making WordPress.org] #2771: Plugin Directory:
 Direct access to changelog via #changelog in URL not working anymore
In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
Message-ID: <067.cad879fbb8c7535e506ad7ac5d4485e6@wordpress.org>

#2771: Plugin Directory: Direct access to changelog via #changelog in URL not
working anymore
------------------------------+------------------------------------
 Reporter:  galbaras          |       Owner:  Dion Hulse
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+------------------------------------

Comment (by Dion Hulse):

 In [changeset:"7033" 7033]:
 {{{
 #!CommitTicketReference repository="" revision="7033"
 Plugin Directory: Rebuild CSS after r7032 which included an out-of-date
 style.css.

 See #2771.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 05:28:55 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 05:28:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2771: Plugin Directory:
 Direct access to changelog via #changelog in URL not working anymore
In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
Message-ID: <067.0cc9cbd2fa91c0dace1ff07e6ca26296@wordpress.org>

#2771: Plugin Directory: Direct access to changelog via #changelog in URL not
working anymore
------------------------------+------------------------------------
 Reporter:  galbaras          |       Owner:  Dion Hulse
     Type:  defect            |      Status:  reopened
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------------------
Changes (by Dion Hulse):

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


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

From noreply at wordpress.org  Thu Apr  5 05:29:00 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 05:29:00 +0000 (UTC)
Subject: [wp-meta] [7034]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins:
 Plugin Directory: Revert r7033 & r7032 - Something went missing between
 local test box and commit.
Message-ID: <20180405052900.852531B003F5@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 05:29:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 05:29:01 -0000
Subject: [wp-meta] [Making WordPress.org] #2771: Plugin Directory:
 Direct access to changelog via #changelog in URL not working anymore
In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
Message-ID: <067.1460f4599873ba5c95de7bfb95d7d07a@wordpress.org>

#2771: Plugin Directory: Direct access to changelog via #changelog in URL not
working anymore
------------------------------+------------------------------------
 Reporter:  galbaras          |       Owner:  Dion Hulse
     Type:  defect            |      Status:  reopened
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------------------

Comment (by Dion Hulse):

 In [changeset:"7034" 7034]:
 {{{
 #!CommitTicketReference repository="" revision="7034"
 Plugin Directory: Revert r7033 & r7032 - Something went missing between
 local test box and commit.

 See #2771.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 05:57:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 05:57:40 +0000 (UTC)
Subject: [wp-meta] [7035]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/template-parts/plugin-single.php:
 Plugin Directory: Use some line JS to redirect `#changelog` to
 `#developers` for back-compat.
Message-ID: <20180405055740.72ADF1B003F5@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 05:57:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 05:57:41 -0000
Subject: [wp-meta] [Making WordPress.org] #2771: Plugin Directory:
 Direct access to changelog via #changelog in URL not working anymore
In-Reply-To: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
References: <052.7fec41b2b3a6abfd47dbd3a54c595761@wordpress.org>
Message-ID: <067.1cdcf5ee622bc6c37d02982331b3225a@wordpress.org>

#2771: Plugin Directory: Direct access to changelog via #changelog in URL not
working anymore
------------------------------+------------------------------------
 Reporter:  galbaras          |       Owner:  Dion Hulse
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+------------------------------------
Changes (by Dion Hulse):

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


Comment:

 In [changeset:"7035" 7035]:
 {{{
 #!CommitTicketReference repository="" revision="7035"
 Plugin Directory: Use some line JS to redirect `#changelog` to
 `#developers` for back-compat.

 Using CSS is cleaner here, but there's a few complexities which are out of
 my reach, and the complexity of the CSS makes it more likely to break in
 the future.

 Fixes #2771.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 06:41:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 06:41:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3551: Plugin Directory: Requires
 PHP: Standardise on values
Message-ID: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>

#3551: Plugin Directory: Requires PHP: Standardise on values
------------------------------+-------------------------
 Reporter:  Dion Hulse        |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  needs-patch
------------------------------+-------------------------
 Following on from #2952 a lot of plugins have started implementing the
 `Requires PHP` header.

 Unfortunately, a lot of them are not following any form of computer-
 readable standard.

 For example, a quick selection:
 {{{
 PHP 4
 Yes
 5.3+
 4.6 or greater
 5.6 or later
 4 & 5
 5+
 5.6 or 7.0
 4
 5.6 or higher
 >= 5.4
 5.4 and higher
 4,5
 5.4+
 (PHP 5.6 + libsodium extension) or (PHP 7.2 or above)
 }}}
 (Yes, some plugins have specified they're PHP 4 compatible, I doubt they
 are)

 A quick look suggests that 2,715 plugins have specified a sane identifier
 (x.y, or x.y.z) with a further 156 plugins specifying it in ways such as
 the above list which make it harder to pragmatically use.

 I'd recommend that we validate the number in some form in the readme
 parser to make the data more useful long term.
 I'd suggest
  - Require the version number be specified as `x.y` or `x.y.z`
  - If Other data is in there, pull out the first version-like string, ie.
 `5.3` from `5.3+`, `5.3 or greater`, or `5.3-7.1`. Based on existing data,
 it looks like that should be fine.
  - Add a warning to the readme validator when unexpected values are
 encountered and note if it's truncated/sanitised to something reasonable.

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

From noreply at wordpress.org  Thu Apr  5 06:52:23 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 06:52:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3551: Plugin Directory:
 Requires PHP: Standardise on values
In-Reply-To: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
References: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
Message-ID: <063.15cb237aad79954add710632d05244c5@wordpress.org>

#3551: Plugin Directory: Requires PHP: Standardise on values
------------------------------+---------------------
 Reporter:  Dion Hulse        |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by danieltj):

 My opinion on this - take it as you will is to require a valid version
 number - as you stated; `x.y` or `x.y.z` and if invalid, don't show this
 requires header at all. This would all only correct and relevant data to
 be shown here.

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

From noreply at wordpress.org  Thu Apr  5 07:15:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 07:15:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3552: WP15 Theme: Event date not
 formatted as translated
Message-ID: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>

#3552: WP15 Theme: Event date not formatted as translated
----------------------+--------------------
 Reporter:  ChantalC  |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:
Component:  General   |   Keywords:
----------------------+--------------------
 If I switch language to Dutch, the date as shown for each event is shown
 in the default format. Apparently nothing is done with the translation:

 https://translate.wordpress.org/projects/meta/wp15/nl/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=5857919&filters%5Btranslation_id%5D=54647449

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

From noreply at wordpress.org  Thu Apr  5 14:28:21 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 14:28:21 -0000
Subject: [wp-meta] [Making WordPress.org] #3551: Plugin Directory:
 Requires PHP: Standardise on values
In-Reply-To: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
References: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
Message-ID: <063.cf84b44d507e03b9bd9f96ad93d08163@wordpress.org>

#3551: Plugin Directory: Requires PHP: Standardise on values
------------------------------+---------------------
 Reporter:  Dion Hulse        |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by Otto):

 They do much the same for the Requires at least: and Tested up to:
 headers.

 I say we simply ignore anything that looks unlike a version number. If
 they have anything else there, then the header is completely ignored.
 Force the issue.

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

From noreply at wordpress.org  Thu Apr  5 17:20:09 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 17:20:09 +0000 (UTC)
Subject: [wp-meta] [7036]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Add text domain to date format to localize string.
Message-ID: <20180405172009.BCF581B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 17:20:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 17:20:10 -0000
Subject: [wp-meta] [Making WordPress.org] #3552: WP15 Theme: Event date
 not formatted as translated
In-Reply-To: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
References: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
Message-ID: <067.cbd91f35fd6fa53f5227a868a220e029@wordpress.org>

#3552: WP15 Theme: Event date not formatted as translated
----------------------+-----------------------
 Reporter:  ChantalC  |       Owner:  Ian Dunn
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:  fixed
 Keywords:            |
----------------------+-----------------------
Changes (by Ian Dunn):

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


Comment:

 In [changeset:"7036" 7036]:
 {{{
 #!CommitTicketReference repository="" revision="7036"
 WP15: Add text domain to date format to localize string.

 This isn't using `date_i18n()` -- because it has to convert the date/time
 with respect to the _event's_ local timezone, not the site's -- so the
 `wp15` domain has to be explicitly provided.

 Fixes #3552.
 }}}

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

From noreply at wordpress.org  Thu Apr  5 17:20:13 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 17:20:13 +0000 (UTC)
Subject: [wp-meta] [7037]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Rename date/time variables to improve clarity.
Message-ID: <20180405172013.546711B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 17:25:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 17:25:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3552: WP15 Theme: Event date
 not formatted as translated
In-Reply-To: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
References: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
Message-ID: <067.6e4b40c64b29812facc5caaca470be51@wordpress.org>

#3552: WP15 Theme: Event date not formatted as translated
----------------------+-----------------------
 Reporter:  ChantalC  |       Owner:  Ian Dunn
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:  fixed
 Keywords:            |
----------------------+-----------------------

Comment (by Ian Dunn):

 Thanks!

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

From noreply at wordpress.org  Thu Apr  5 18:09:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 18:09:31 -0000
Subject: [wp-meta] [Making WordPress.org] #1658: Meetings: Add a
 calendar view
In-Reply-To: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org>
References: <051.5c0980b36066c9e8727629f1e7565ffd@wordpress.org>
Message-ID: <066.f20a1a7063097840bbf5d87edfa77ecb@wordpress.org>

#1658: Meetings: Add a calendar view
--------------------------------------+-----------------------
 Reporter:  Dominik Schilling         |       Owner:  (none)
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch needs-ui      |
--------------------------------------+-----------------------

Comment (by boemedia):

 We discussed this ticket in today's Design meeting. As we do encourage
 more visual ways of bringing information to the users of
 make.wordpress.org, we strongly doubt if a calendar view will help people
 '''find this information in the first place'''.

 We don't get the impression many people use the list view anyway, since
 it's not very findable. The dark bar on the .org pages seems to get
 skipped, because it doesn't catch attention. The meeting list is
 incomplete, the order of the meetings is hard to understand. We'd suggest
 to first research on the use of this page (are there statistics of how
 many times this page is viewed?), before putting precious dev & design
 time into something that may not used by many.

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

From noreply at wordpress.org  Thu Apr  5 18:34:29 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 18:34:29 +0000 (UTC)
Subject: [wp-meta] [7038]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins/miscellaneous.php:
 WP15: Show Tagregator log in wp-admin.
Message-ID: <20180405183429.C3ADB1B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 18:34:33 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 18:34:33 +0000 (UTC)
Subject: [wp-meta] [7039]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins: WP15: Apply
 coding standards.
Message-ID: <20180405183433.432C01B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 19:54:00 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 19:54:00 +0000 (UTC)
Subject: [wp-meta] [7040]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/addons:
 WordCamp tickets: Add context to some translation strings
Message-ID: <20180405195400.302341B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 20:01:26 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 20:01:26 +0000 (UTC)
Subject: [wp-meta] [7041]
 sites/trunk/common/includes/slack/trac/comment-handler.php: Slack/Trac: Add
 support for Multipart content type which is used by newer Trac versions.
Message-ID: <20180405200126.D0DC41B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 20:07:21 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 05 Apr 2018 20:07:21 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <065.7aa330a8d1c359b268631df5b8d62eb0@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
---------------------------+--------------------------------
 Reporter:  Stephen Edgar  |       Owner:  Dominik Schilling
     Type:  defect         |      Status:  closed
 Priority:  high           |   Milestone:
Component:  Slack & IRC    |  Resolution:  fixed
 Keywords:  needs-patch    |
---------------------------+--------------------------------

Comment (by Dominik Schilling):

 test

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

From noreply at wordpress.org  Thu Apr  5 22:47:27 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 22:47:27 +0000 (UTC)
Subject: [wp-meta] [7042]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/utilities/class-stripe-client.php:
 Stripe Client: Add more granular error messages to help troubleshoot.
Message-ID: <20180405224727.C1E361B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 22:47:54 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 22:47:54 +0000 (UTC)
Subject: [wp-meta] [7043]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-payments:
 WordCamp Payments: Show error messages thrown by Stripe Client.
Message-ID: <20180405224754.620C41B00381@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr  5 23:03:18 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  5 Apr 2018 23:03:18 +0000 (UTC)
Subject: [wp-meta] [7044]
 sites/trunk/wp15.wordpress.net/public_html/content: WP15: Encourage
 visitors to organize events/groups if one doesn't exist.
Message-ID: <20180405230318.46A1B1B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 00:19:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 00:19:34 -0000
Subject: [wp-meta] [Making WordPress.org] #3551: Plugin Directory:
 Requires PHP: Standardise on values
In-Reply-To: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
References: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
Message-ID: <063.637529410082ef96710828256b329353@wordpress.org>

#3551: Plugin Directory: Requires PHP: Standardise on values
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by dd32):

 Replying to [comment:2 Otto42]:
 > They do much the same for the Requires at least: and Tested up to:
 headers.

 That's what caused me to take a sanity look at the Requires data :)

 > I say we simply ignore anything that looks unlike a version number. If
 they have anything else there, then the header is completely ignored.
 Force the issue.

 It seems like that's the consensus, so yeah, lets just ignore any non-
 version data and throw a warning in the validator then.

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

From noreply at wordpress.org  Fri Apr  6 02:41:48 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 02:41:48 +0000 (UTC)
Subject: [wp-meta] [7045]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/class-plugin-directory.php:
 Plugin Direcyory: Add a route (`/plugins/$slug/geopattern-icon/$color`) to
 serve a plugins default geopattern icon.
Message-ID: <20180406024148.A4FF81B00488@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 02:41:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 02:41:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.83c1536ffcf16e647e1675af05f17956@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7045" 7045]:
 {{{
 #!CommitTicketReference repository="" revision="7045"
 Plugin Direcyory: Add a route (`/plugins/$slug/geopattern-icon/$color`) to
 serve a plugins default geopattern icon.
 This will be served via the CDN and implemented in a further commit.

 See #3265.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 03:09:44 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 03:09:44 +0000 (UTC)
Subject: [wp-meta] [7046]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/class-plugin-directory.php:
 Plugin Directory: GeoPattern icons: Send caching headers with the SVGs.
Message-ID: <20180406030944.584171B00488@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 03:09:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 03:09:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.67da245190e82d85c7cdcc4aaa9dad7a@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7046" 7046]:
 {{{
 #!CommitTicketReference repository="" revision="7046"
 Plugin Directory: GeoPattern icons: Send caching headers with the SVGs.

 See #3265.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 03:51:49 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 03:51:49 +0000 (UTC)
Subject: [wp-meta] [7047]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/class-plugin-directory.php:
 Plugin Directory: Geopattern icons: Change the path the files are available
 at to `/plugins/geopattern-icon/$slug.$color.svg` to aid in debugging.
Message-ID: <20180406035149.AD8741B00488@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 03:51:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 03:51:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.12bd42ac9ce8359facd3837ffe4fac97@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7047" 7047]:
 {{{
 #!CommitTicketReference repository="" revision="7047"
 Plugin Directory: Geopattern icons: Change the path the files are
 available at to `/plugins/geopattern-icon/$slug.$color.svg` to aid in
 debugging.

 See #3265.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 04:27:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 04:27:36 +0000 (UTC)
Subject: [wp-meta] [7048]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory:
 Plugin Directory: Use geopattern icons from a CDN svg rather than using
 data URI's inline on the page.
Message-ID: <20180406042736.3F2291B00488@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 04:27:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 04:27:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.1e66613de92fe6b28269ec55c6ad6b6e@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7048" 7048]:
 {{{
 #!CommitTicketReference repository="" revision="7048"
 Plugin Directory: Use geopattern icons from a CDN svg rather than using
 data URI's inline on the page.

 See #3265.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 04:36:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 04:36:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.ddb69a695de24ae17c877a87e489e8ea@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 That takes care of https://WordPress.org/plugins/ and the `plugins/info`
 api endpoint.

 Still remaining is fixing up the `plugins/update-check` api to use the new
 svg.
 In doing so, we should probably update it to insert a column in the
 `update_source` table for `assets` which contains the banners/icons rather
 than rebuilding it in the API.

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

From noreply at wordpress.org  Fri Apr  6 05:04:55 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 05:04:55 +0000 (UTC)
Subject: [wp-meta] [7049]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/readme:
 Plugin Directory: Readme: Ignore invalid `Requires PHP` headers and add a
 parsing warning clarifying the expected contents.
Message-ID: <20180406050455.4D0011B00488@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 05:04:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 05:04:56 -0000
Subject: [wp-meta] [Making WordPress.org] #3551: Plugin Directory:
 Requires PHP: Standardise on values
In-Reply-To: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
References: <048.b1d18408b01dad90f7c474342c6a154e@wordpress.org>
Message-ID: <063.879762ece6b2d092c8afa50f9f71ac16@wordpress.org>

#3551: Plugin Directory: Requires PHP: Standardise on values
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  needs-patch       |
------------------------------+---------------------
Changes (by dd32):

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


Comment:

 In [changeset:"7049" 7049]:
 {{{
 #!CommitTicketReference repository="" revision="7049"
 Plugin Directory: Readme: Ignore invalid `Requires PHP` headers and add a
 parsing warning clarifying the expected contents.

 Fixes #3551.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 05:08:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 05:08:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3553: Deploy Gutenberg (plugin)
 on Rosetta/team o2
Message-ID: <052.b2717cbc5d905f53f6984aa61312de8a@wordpress.org>

#3553: Deploy Gutenberg (plugin) on Rosetta/team o2
-------------------------------------------+-------------------------
 Reporter:  audrasjb                       |      Owner:  (none)
     Type:  task                           |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:  needs-patch
-------------------------------------------+-------------------------
 Like Make blogs, Rosetta and team o2 of international websites should be
 able to use Gutenberg (as an option when writing a new post).

 Please consider deploying Gutenberg (plugin) on these websites :)

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

From noreply at wordpress.org  Fri Apr  6 07:31:17 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 07:31:17 -0000
Subject: [wp-meta] [Making WordPress.org] #3552: WP15 Theme: Event date
 not formatted as translated
In-Reply-To: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
References: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
Message-ID: <067.07955eda828f4580658b83a2bbef886c@wordpress.org>

#3552: WP15 Theme: Event date not formatted as translated
----------------------+-----------------------
 Reporter:  ChantalC  |       Owner:  iandunn
     Type:  defect    |      Status:  reopened
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:
 Keywords:            |
----------------------+-----------------------
Changes (by ChantalC):

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


Comment:

 @iandunn better now, but the month is shown in English. For example in
 Dutch is shows as "May" where "mei" should be correct.

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

From noreply at wordpress.org  Fri Apr  6 07:39:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 07:39:54 -0000
Subject: [wp-meta] [Making WordPress.org] #3553: Activate Gutenberg
 (plugin) on Rosetta/team o2 (was: Deploy Gutenberg (plugin) on Rosetta/team
 o2)
In-Reply-To: <052.b2717cbc5d905f53f6984aa61312de8a@wordpress.org>
References: <052.b2717cbc5d905f53f6984aa61312de8a@wordpress.org>
Message-ID: <067.fe577a2c746556408523dc9540b65508@wordpress.org>

#3553: Activate Gutenberg (plugin) on Rosetta/team o2
-------------------------------------------+---------------------
 Reporter:  audrasjb                       |       Owner:  (none)
     Type:  task                           |      Status:  new
 Priority:  low                            |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:                                 |
-------------------------------------------+---------------------
Changes (by ocean90):

 * keywords:  needs-patch =>
 * priority:  normal => low


Old description:

> Like Make blogs, Rosetta and team o2 of international websites should be
> able to use Gutenberg (as an option when writing a new post).
>
> Please consider deploying Gutenberg (plugin) on these websites :)

New description:

 Like Make blogs, Rosetta and team o2 of international websites should be
 able to use Gutenberg (as an option when writing a new post).

 Please consider activating Gutenberg (plugin) on these websites :)

--

Comment:

 Once 2.7 has been released we can enable it.This release will hopefully
 ensure that all strings are translated.

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

From noreply at wordpress.org  Fri Apr  6 07:43:12 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 07:43:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3542: Incorrectly escaped
 percent sign in "about security"
In-Reply-To: <056.acbbf248a96e4ba2f4e9c62f7c494f91@wordpress.org>
References: <056.acbbf248a96e4ba2f4e9c62f7c494f91@wordpress.org>
Message-ID: <071.b02eb040c667b868ca062c7221f6fe98@wordpress.org>

#3542: Incorrectly escaped percent sign in "about security"
--------------------------+---------------------
 Reporter:  tobifjellner  |       Owner:  dd32
     Type:  defect        |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by ocean90):

 * component:  International Sites (Rosetta) => General


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

From noreply at wordpress.org  Fri Apr  6 07:47:48 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 07:47:48 +0000 (UTC)
Subject: [wp-meta] [7050]
 sites/trunk/global.wordpress.org/public_html/wp-content/mu-plugins/roles/rosetta-roles.php:
 Rosetta Roles: Replace "plugin author" with "project author".
Message-ID: <20180406074748.568971B0033C@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 07:47:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 07:47:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3532: Change "plugin author"
 to "project author" in the PTE confirmation email
In-Reply-To: <049.1c9b660e145c0d2aa74407cd29e82fe4@wordpress.org>
References: <049.1c9b660e145c0d2aa74407cd29e82fe4@wordpress.org>
Message-ID: <064.9b2b25153fc7b7c5fc6b4c410ea32934@wordpress.org>

#3532: Change "plugin author" to "project author" in the PTE confirmation email
-------------------------------------------+----------------------
 Reporter:  petya                          |       Owner:  ocean90
     Type:  defect                         |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:  fixed
 Keywords:                                 |
-------------------------------------------+----------------------
Changes (by ocean90):

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


Comment:

 In [changeset:"7050" 7050]:
 {{{
 #!CommitTicketReference repository="" revision="7050"
 Rosetta Roles: Replace "plugin author" with "project author".

 Props petya.
 Fixes #3532.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 16:00:07 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 16:00:07 +0000 (UTC)
Subject: [wp-meta] [7051] sites/trunk/doaction.org/: Do Action: Create stub
 directory so SVN permissions can be assigned.
Message-ID: <20180406160007.41A4D1B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 17:27:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 17:27:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3554: WordCamp Central improve
 single day date output
Message-ID: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>

#3554: WordCamp Central improve single day date output
-------------------------------------+--------------------
 Reporter:  soulseekah               |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 Most WordCamps are held over one day. Others are held over multiple days.

 https://central.wordcamp.org/

 The date output for multiple days is nice: April 6-7, for example.

 For single-day events, the output seems a bit off, doesn't it? April 7-7,
 May 26-26, etc.

 Would it not be nice if single-day events are displayed as April 7, May 26
 instead?

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

From noreply at wordpress.org  Fri Apr  6 17:37:59 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 17:37:59 +0000 (UTC)
Subject: [wp-meta] [7052]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Pass dates through `date_i18n()` to localize month names.
Message-ID: <20180406173759.A29801B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 17:38:00 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 17:38:00 -0000
Subject: [wp-meta] [Making WordPress.org] #3552: WP15 Theme: Event date
 not formatted as translated
In-Reply-To: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
References: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
Message-ID: <067.a24e36e20d4541af77f4d22fe60df6b5@wordpress.org>

#3552: WP15 Theme: Event date not formatted as translated
----------------------+----------------------
 Reporter:  ChantalC  |       Owner:  iandunn
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:  fixed
 Keywords:            |
----------------------+----------------------
Changes (by iandunn):

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


Comment:

 In [changeset:"7052" 7052]:
 {{{
 #!CommitTicketReference repository="" revision="7052"
 WP15: Pass dates through `date_i18n()` to localize month names.

 Fixes #3552.
 }}}

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

From noreply at wordpress.org  Fri Apr  6 17:46:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 17:46:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.846d7f083fef3f546a2c39e2d70a2042@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------

Comment (by La Geek):

 https://translate.wordpress.org/projects/meta/wordpress-
 org/de/default?filters%5Boriginal_id%5D=5848163

 > The default theme which ships with core WordPress (currently "Twenty
 Fifteen")

 should be

 > (currently "Twenty Seventeen")

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

From noreply at wordpress.org  Fri Apr  6 17:49:17 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 17:49:17 -0000
Subject: [wp-meta] [Making WordPress.org] #3552: WP15 Theme: Event date
 not formatted as translated
In-Reply-To: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
References: <052.569fe545a1a71ecd7155fe993911216c@wordpress.org>
Message-ID: <067.e4690adf97b645bd52dc5070e5b4dcb4@wordpress.org>

#3552: WP15 Theme: Event date not formatted as translated
----------------------+----------------------
 Reporter:  ChantalC  |       Owner:  iandunn
     Type:  defect    |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  General   |  Resolution:  fixed
 Keywords:            |
----------------------+----------------------

Comment (by iandunn):

 Good catch. I installed the language packs for all locales, deployed
 r7052, and cleared the static page cache.

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

From noreply at wordpress.org  Fri Apr  6 17:53:13 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 17:53:13 -0000
Subject: [wp-meta] [Making WordPress.org] #3554: WordCamp Central
 improve single day date output
In-Reply-To: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
References: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
Message-ID: <069.549d91901a17c31e0ea687b83d1f4bd8@wordpress.org>

#3554: WordCamp Central improve single day date output
-------------------------------------+---------------------
 Reporter:  soulseekah               |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------
Changes (by soulseekah):

 * Attachment "3554.diff" added.


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

From noreply at wordpress.org  Fri Apr  6 17:54:00 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 17:54:00 -0000
Subject: [wp-meta] [Making WordPress.org] #3554: WordCamp Central
 improve single day date output
In-Reply-To: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
References: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
Message-ID: <069.0d777200b24c6ffbd30397c2b8709cbd@wordpress.org>

#3554: WordCamp Central improve single day date output
-------------------------------------+---------------------
 Reporter:  soulseekah               |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------

Comment (by soulseekah):

 This only happens when End Date is provided when editing a WordCamp. If
 it's not provided the date appears "correctly". Patch 3554.diff makes sure
 that the ugly form is never output.

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

From noreply at wordpress.org  Fri Apr  6 18:12:59 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 06 Apr 2018 18:12:59 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.cdb646e96b7bd1202d6ba1b06dcad2bc@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------

Comment (by tobifjellner):

 It would be good to make the whole "About" section more congruent in terms
 of typography. In many places, simple {{{"}}} quotes are used, but in some
 places there are typographical quotes called via html entities.

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

From noreply at wordpress.org  Fri Apr  6 20:15:59 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 20:15:59 +0000 (UTC)
Subject: [wp-meta] [7053] WP15: Ignore languages folder.
Message-ID: <20180406201559.C0FCF1B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 20:26:44 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 20:26:44 +0000 (UTC)
Subject: [wp-meta] [7054]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins/miscellaneous.php:
 WP15: Store the translation status of each locale
Message-ID: <20180406202644.B99CE1B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 20:34:50 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 20:34:50 +0000 (UTC)
Subject: [wp-meta] [7055]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/functions.php:
 WP15: Internationalize menu item titles.
Message-ID: <20180406203450.91A1C1B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 22:17:08 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 22:17:08 +0000 (UTC)
Subject: [wp-meta] [7056]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Improve compatibility with IE11.
Message-ID: <20180406221708.C86C01B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 22:34:48 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 22:34:48 +0000 (UTC)
Subject: [wp-meta] [7057]
 sites/trunk/wp15.wordpress.net/public_html/content: WP15: Add dismissible
 notice when chosen locale is not 100% translated
Message-ID: <20180406223448.9D3EC1B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 22:39:45 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 22:39:45 +0000 (UTC)
Subject: [wp-meta] [7058]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins/locales.php:
 WP15: use the word "percent" instead of "%%" to avoid placeholder confusion
Message-ID: <20180406223945.F34D11B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 23:02:05 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 23:02:05 +0000 (UTC)
Subject: [wp-meta] [7059]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/header.php:
 WP15 theme: Move locale notice to right below the site header
Message-ID: <20180406230205.074631B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 23:03:20 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 23:03:20 +0000 (UTC)
Subject: [wp-meta] [7060]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins/locales.php:
 WP15: Use `filemtime` to version the locale switcher script
Message-ID: <20180406230320.51B691B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr  6 23:24:22 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  6 Apr 2018 23:24:22 +0000 (UTC)
Subject: [wp-meta] [7061]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/page-swag.php:
 WP15 theme: Swag page content edits
Message-ID: <20180406232422.E8EB81B00450@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr  7 01:08:23 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  7 Apr 2018 01:08:23 +0000 (UTC)
Subject: [wp-meta] [7062]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15 theme: Prevent iOS from replacing switcher with native picker UI
Message-ID: <20180407010824.03B4A1B004D9@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr  7 01:17:31 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  7 Apr 2018 01:17:31 +0000 (UTC)
Subject: [wp-meta] [7063]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15 theme: Fix nav bar layout on narrow screens in Safari
Message-ID: <20180407011731.3755B1B004D9@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr  7 13:41:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 07 Apr 2018 13:41:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3554: WordCamp Central
 improve single day date output
In-Reply-To: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
References: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
Message-ID: <069.d800b7ad089d481b609ffb636f92d26e@wordpress.org>

#3554: WordCamp Central improve single day date output
-------------------------------------+---------------------
 Reporter:  soulseekah               |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------
Changes (by soulseekah):

 * Attachment "3554.2.diff" added.


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

From noreply at wordpress.org  Sat Apr  7 13:41:53 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 07 Apr 2018 13:41:53 -0000
Subject: [wp-meta] [Making WordPress.org] #3554: WordCamp Central
 improve single day date output
In-Reply-To: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
References: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
Message-ID: <069.c79bc390539ce182f89ae4f1ed9a924a@wordpress.org>

#3554: WordCamp Central improve single day date output
-------------------------------------+---------------------
 Reporter:  soulseekah               |       Owner:  (none)
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------

Comment (by soulseekah):

 Looking back at this the logic in the first diff is flawed. Fixed in
 second, eek :)

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

From noreply at wordpress.org  Sun Apr  8 10:06:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 10:06:01 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <065.64248e1908051956ac678fba0528dffe@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
-------------------------+----------------------
 Reporter:  netweb       |       Owner:  ocean90
     Type:  defect       |      Status:  closed
 Priority:  high         |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+----------------------
Changes (by ocean90):

 * Attachment "test.txt" added.


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

From noreply at wordpress.org  Sun Apr  8 10:15:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 10:15:30 -0000
Subject: [wp-meta] [Making WordPress.org] #1606: Update Trac to 1.0.16
In-Reply-To: <051.4c1d007b72d6d77edab71bfe4f994476@wordpress.org>
References: <051.4c1d007b72d6d77edab71bfe4f994476@wordpress.org>
Message-ID: <066.88b400ad724ad868920a96a9cd1f244e@wordpress.org>

#1606: Update Trac to 1.0.16
---------------------+---------------------
 Reporter:  ocean90  |       Owner:  (none)
     Type:  task     |      Status:  closed
 Priority:  low      |   Milestone:
Component:  Trac     |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------
Changes (by ocean90):

 * resolution:  maybelater => fixed


Comment:

 See #3526.

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

From noreply at wordpress.org  Sun Apr  8 10:19:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 10:19:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.9f0a94155f0f852765a50a15203f03bc@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by ocean90):

 * Comment preview broken: https://cloudup.com/c_HqVeJebX6
 * Attachment notifications trigger a "New Ticket" Slack notification
 (https://wordpress.slack.com/archives/C02QB8GMM/p1523181962000043)
 * The order of the "Modify Ticket" and "Add Comment" is different. It was
 "Add Comment" - "Modify Ticket" previously.

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

From noreply at wordpress.org  Sun Apr  8 10:33:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 10:33:54 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
-------------------------+----------------------
 Reporter:  netweb       |       Owner:  ocean90
     Type:  defect       |      Status:  closed
 Priority:  high         |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+----------------------
Changes (by ocean90):

 * Attachment "test.txt" removed.


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

From noreply at wordpress.org  Sun Apr  8 10:33:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 10:33:54 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <065.69582ae705221bdab0e8564950ee1172@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
-------------------------+----------------------
 Reporter:  netweb       |       Owner:  ocean90
     Type:  defect       |      Status:  closed
 Priority:  high         |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+----------------------
Changes (by ocean90):

 * Attachment "test.txt" added.

 Description of the file

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

From noreply at wordpress.org  Sun Apr  8 11:29:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 11:29:20 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
-------------------------+----------------------
 Reporter:  netweb       |       Owner:  ocean90
     Type:  defect       |      Status:  closed
 Priority:  high         |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+----------------------
Changes (by ocean90):

 * Attachment "test.txt" removed.

 Description of the file

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

From noreply at wordpress.org  Sun Apr  8 11:43:28 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  8 Apr 2018 11:43:28 +0000 (UTC)
Subject: [wp-meta] [7064] sites/trunk: Slack/Trac: Add support for
 attachment notification mails.
Message-ID: <20180408114328.1FCB91B005E0@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sun Apr  8 11:43:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 08 Apr 2018 11:43:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.1153e720921f85e1eb694f93627a8a40@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by ocean90):

 In [changeset:"7064" 7064]:
 {{{
 #!CommitTicketReference repository="" revision="7064"
 Slack/Trac: Add support for attachment notification mails.

 See #3526.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 01:35:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 01:35:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3555: Clarify with a translator
 comment a WordCamp Stripe string
Message-ID: <050.8de49e14b4090d3bcf8dbd66b6c0924d@wordpress.org>

#3555: Clarify with a translator comment a WordCamp Stripe string
-------------------------------------+--------------------
 Reporter:  netweb                   |      Owner:  (none)
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 String: ''We're sorry, but we can't accept amounts larger than %s. Please
 send the equivalent in USD, or break it up into several smaller payments.
 Feel free to email <a href='mailto:%s'>%s</a> with any questions.''

 A translator comment should be added to note that `USD` should '''not'''
 be translated:

 Via @pento:
 > ''@webaware, @netweb: Looking at the string, I think it's supposed to
 stay as USD. It's for the case where a person is trying to pay a larger
 figure than the Stripe API supports (999,999.99, in any currency). For
 example, 999,999.99 Chilean Pesos is ~$700 USD, which someone could
 conceivably run into.''

 Source:
 https://meta.trac.wordpress.org/browser/sites/trunk/wordcamp.org/public_html
 /wp-content/mu-plugins/utilities/class-stripe-client.php?marks=69#L69

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

From noreply at wordpress.org  Mon Apr  9 01:51:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 01:51:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.aff2a9486826695e1183ae99490e52a3@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------
Description changed by dd32:

Old description:

> As part of the final items of the datacenter move, SVN and Trac are being
> brought over.
>
> The upgrade of Trac from 1.something to 1.2.2 has revealed a few bugs,
> lets track them here.
>
> ----
>
> Known issues:
>
> https://wordpress.slack.com/archives/C02RQBYUG/p1521424454000022
> > #buddypress-firehose does not show new comment in existing ticket
>
> from @dd32
> > A bunch of the JS/CSS files are updated, and Trac doesn't have cache-
> busters (https://trac.edgewall.org/ticket/9936 - seven years and
> counting) so we'll need to update and force-clear caches once all Trac's
> are updated.
>
> ----
>
> Should be fixed:
>
> https://wordpress.slack.com/archives/C02RQBYUG/p1521424715000009
> > plus attached screenshots are not showing in ticket, only when you
> click on the image link
>
> https://wordpress.slack.com/archives/C02QB8GMM/p1521410697000088
> > The BuddyPress trac is showing invalid data for the two most recent
> commits, though a SVN checkout has the `svn log` working correctly. Easy
> to see on https://buddypress.trac.wordpress.org/log (11898, 11899). Can
> anyone help?
>
> https://wordpress.slack.com/archives/C02RQBYUG/p1521424003000027
> > The dropdown for the Keywords is gone for both BP and bbPress tracs and
> one needs to manually add the keywords plus the Add comment textbox is
> now under the Action fieldset
> ''Should be fixed'' pending [6893], [6895], and [6896]
>
> https://wordpress.slack.com/archives/C02RQBYUG/p1521440267000037
> > the Preview box that shows up when you create a new ticket or Add
> comment is missing/gone.
> ''Should be fixed'' pending [6893], [6895], and [6896]

New description:

 As part of the final items of the datacenter move, SVN and Trac are being
 brought over.

 The upgrade of Trac from 1.something to 1.2.2 has revealed a few bugs,
 lets track them here.

 ----

 Known issues:

 from @dd32
 > A bunch of the JS/CSS files are updated, and Trac doesn't have cache-
 busters (https://trac.edgewall.org/ticket/9936 - seven years and counting)
 so we'll need to update and force-clear caches once all Trac's are
 updated.

 ----

 Should be fixed:

 https://wordpress.slack.com/archives/C02RQBYUG/p1521424715000009
 > plus attached screenshots are not showing in ticket, only when you click
 on the image link

 https://wordpress.slack.com/archives/C02QB8GMM/p1521410697000088
 > The BuddyPress trac is showing invalid data for the two most recent
 commits, though a SVN checkout has the `svn log` working correctly. Easy
 to see on https://buddypress.trac.wordpress.org/log (11898, 11899). Can
 anyone help?

 https://wordpress.slack.com/archives/C02RQBYUG/p1521424003000027
 > The dropdown for the Keywords is gone for both BP and bbPress tracs and
 one needs to manually add the keywords plus the Add comment textbox is now
 under the Action fieldset
 ''Should be fixed'' pending [6893], [6895], and [6896]

 https://wordpress.slack.com/archives/C02RQBYUG/p1521440267000037
 > the Preview box that shows up when you create a new ticket or Add
 comment is missing/gone.
 ''Should be fixed'' pending [6893], [6895], and [6896]

 https://wordpress.slack.com/archives/C02RQBYUG/p1521424454000022
 > #buddypress-firehose does not show new comment in existing ticket

--

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

From noreply at wordpress.org  Mon Apr  9 01:55:23 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 01:55:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.33823c019ac48ef4928d36730baebbf2@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------

Comment (by dd32):

 ''' For all further issues, please open new tickets. '''

 I'll transfer any remaining issues from this ticket into new tickets later
 today.

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

From noreply at wordpress.org  Mon Apr  9 03:37:38 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  9 Apr 2018 03:37:38 +0000 (UTC)
Subject: [wp-meta] [7065]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.js: Trac: Don't
 double up the comment deletion buttons.
Message-ID: <20180409033738.B6A4B1B005EF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  9 03:37:39 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 03:37:39 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.78ab373670b44542cbd2ca132991c660@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 In [changeset:"7065" 7065]:
 {{{
 #!CommitTicketReference repository="" revision="7065"
 Trac: Don't double up the comment deletion buttons.

 This needs a follow up once all Tracs are migrated to remove this block of
 code / the extra template changes.

 See #3526.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 03:56:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 03:56:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.56c789acdca2879c2dbd8423980d331e@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 Replying to [comment:13 ocean90]:
 > * Comment preview broken: https://cloudup.com/c_HqVeJebX6

 This is caused by Trac containing this in it's preview HTML:
 {{{
 jQuery.loadStyleSheet("https://s.w.org/style/trac/common/css/trac.css",
 "text/css");
 }}}

 Using the old Trac JS causes `trac.css` to get reloaded after `wp-
 trac.css`.

 Once the new `trac.js` is in use, it'll be fixed as `loadStyleSheet()` now
 contains some logic not to reload the stylesheet if it's already loaded
 into the DOM.

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

From noreply at wordpress.org  Mon Apr  9 03:57:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 03:57:34 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.9071b588c8c58c84a04511f44198eb90@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 Replying to [comment:13 ocean90]:
 > * The order of the "Modify Ticket" and "Add Comment" is different. It
 was "Add Comment" - "Modify Ticket" previously.

 Do we care about that order change? it doesn't seem to be a real issue to
 me

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

From noreply at wordpress.org  Mon Apr  9 03:59:07 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  9 Apr 2018 03:59:07 +0000 (UTC)
Subject: [wp-meta] [7066]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump
 `scripts_version` following [7065].
Message-ID: <20180409035907.2B7101B005EF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  9 03:59:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 03:59:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.afb3b10981f54c38b10d54ddc8286b08@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 In [changeset:"7066" 7066]:
 {{{
 #!CommitTicketReference repository="" revision="7066"
 Trac: Bump `scripts_version` following [7065].

 See #3526.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 04:01:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 04:01:57 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.62ec0b94f80d18870cdb7403d4b13f8b@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 Replying to [comment:19 dd32]:
 > In [changeset:"7066" 7066]:
 > {{{
 > #!CommitTicketReference repository="" revision="7066"
 > Trac: Bump `scripts_version` following [7065].
 >
 > See #3526.
 > }}}

 Bumping `scripts_version` is no longer enough to trigger a Trac Template
 refresh too.

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

From noreply at wordpress.org  Mon Apr  9 06:04:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 06:04:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3556: About section: improve
 typographical details
Message-ID: <054.7a3e1e9000192d188f41babf77b9b6a3@wordpress.org>

#3556: About section: improve typographical details
------------------------+--------------------
 Reporter:  tellyworth  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  General     |   Keywords:
------------------------+--------------------
 There are some inconsistencies in the typography and formatting used on
 the About pages that could stand some improvement.

 Quoting @tobifjellner from
 https://meta.trac.wordpress.org/ticket/3046#comment:164:

  It would be good to make the whole "About" section more congruent in
 terms of typography. In many places, simple " quotes are used, but in some
 places there are typographical quotes called via html entities.

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

From noreply at wordpress.org  Mon Apr  9 06:09:44 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 06:09:44 -0000
Subject: [wp-meta] [Making WordPress.org] #3557: About section: improve
 sizing of highlight boxes
Message-ID: <054.64b9b5e969075c3c220969b86ae4dd80@wordpress.org>

#3557: About section: improve sizing of highlight boxes
------------------------+--------------------
 Reporter:  tellyworth  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  General     |   Keywords:
------------------------+--------------------
 The blue and purple highlight boxes on the main About page are clipped at
 some screen sizes.

 See https://meta.trac.wordpress.org/ticket/3046#comment:144 for details.

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

From noreply at wordpress.org  Mon Apr  9 06:17:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 06:17:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3558: About section: improve
 formatting on Features page
Message-ID: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>

#3558: About section: improve formatting on Features page
-------------------------+--------------------
 Reporter:  tellyworth   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 https://wordpress.org/about/features/ has some quirky formatting of its
 dot-point headings.

 Quoting @mapk from
 https://meta.trac.wordpress.org/ticket/3046#comment:136:

  But yes, I think there should be a line break after each one since the
 words in bold aren't part of the sentence. Something like:
   '''Simplicity'''
   Simplicity makes it possible for you to get online and...

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

From noreply at wordpress.org  Mon Apr  9 06:23:42 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 06:23:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3559: About section: make heading
 sizes consistent
Message-ID: <054.301e9a41376a741bb3cd1b8cc2e4214b@wordpress.org>

#3559: About section: make heading sizes consistent
------------------------+--------------------
 Reporter:  tellyworth  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  General     |   Keywords:
------------------------+--------------------
 Some of the main and subheadings used on different About pages are
 inconsistent and have different CSS.

 It's not entirely clear which ones are intentionally different and which
 are accidental.

 See https://meta.trac.wordpress.org/ticket/3046#comment:122 and follow-up
 discussion.

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

From noreply at wordpress.org  Mon Apr  9 06:31:16 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 06:31:16 -0000
Subject: [wp-meta] [Making WordPress.org] #3559: About section: make
 heading sizes consistent
In-Reply-To: <054.301e9a41376a741bb3cd1b8cc2e4214b@wordpress.org>
References: <054.301e9a41376a741bb3cd1b8cc2e4214b@wordpress.org>
Message-ID: <069.b19ad000447d3ea03cfedd970e69859d@wordpress.org>

#3559: About section: make heading sizes consistent
------------------------+---------------------
 Reporter:  tellyworth  |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  General     |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by tellyworth):

 Related: there are some resulting a11y issues, as pointed out by
 @rianrietveld in https://meta.trac.wordpress.org/ticket/3046#comment:104

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

From noreply at wordpress.org  Mon Apr  9 06:34:06 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 06:34:06 -0000
Subject: [wp-meta] [Making WordPress.org] #3559: About section: make
 heading sizes consistent
In-Reply-To: <054.301e9a41376a741bb3cd1b8cc2e4214b@wordpress.org>
References: <054.301e9a41376a741bb3cd1b8cc2e4214b@wordpress.org>
Message-ID: <069.e907566835ff42ef8f79d67e61368db5@wordpress.org>

#3559: About section: make heading sizes consistent
------------------------+---------------------
 Reporter:  tellyworth  |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  General     |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by rianrietveld):

 You can find more detailed information about semantic heading structure in
 the a11y handbook:
 https://make.wordpress.org/accessibility/handbook/best-practices/markup
 /heading-structure-in-theme-development/

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

From noreply at wordpress.org  Mon Apr  9 07:55:43 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 07:55:43 -0000
Subject: [wp-meta] [Making WordPress.org] #3560: WP15 Theme: Event dates
 translation is showing current date/time
Message-ID: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>

#3560: WP15 Theme: Event dates translation is showing current date/time
---------------------------+--------------------
 Reporter:  pedromendonca  |      Owner:  (none)
     Type:  defect         |     Status:  new
 Priority:  normal         |  Milestone:
Component:  General        |   Keywords:
---------------------------+--------------------
 If I switch the language to Portuguese (pt_PT), the date of all events is
 the current date, and not each event specific date. I've check that it
 also happens for pt_BR locale.

 The date format is currently translated mostly like in WP core for our
 locale.
 https://translate.wordpress.org/projects/meta/wp15/pt/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=5857919&filters%5Btranslation_id%5D=54779825

 https://wp15.wordpress.net/?locale=pt_PT

 An example date from Porto 15th Aniversary event:
 '''May 24th, 2018 7:00pm''' - {{{"F jS, Y g:ia"}}}
 '''9 de Abril de 2018 @ 7:31''' - {{{"j \d\e F \d\e Y @ G:i"}}}

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

From noreply at wordpress.org  Mon Apr  9 07:56:12 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 07:56:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3560: WP15 Theme: Event dates
 translation is showing current date/time
In-Reply-To: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
References: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
Message-ID: <072.5cafae2667c3b36ab23ab6d100977370@wordpress.org>

#3560: WP15 Theme: Event dates translation is showing current date/time
---------------------------+---------------------
 Reporter:  pedromendonca  |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:
 Keywords:                 |
---------------------------+---------------------
Changes (by pedromendonca):

 * Attachment "Screenshot 2018-04-09 08.52.50.png" added.


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

From noreply at wordpress.org  Mon Apr  9 07:56:24 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 07:56:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3560: WP15 Theme: Event dates
 translation is showing current date/time
In-Reply-To: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
References: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
Message-ID: <072.a100e161934e3402e642d182e4598af8@wordpress.org>

#3560: WP15 Theme: Event dates translation is showing current date/time
---------------------------+---------------------
 Reporter:  pedromendonca  |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:
 Keywords:                 |
---------------------------+---------------------
Changes (by pedromendonca):

 * Attachment "Screenshot 2018-04-09 08.53.04.png" added.


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

From noreply at wordpress.org  Mon Apr  9 08:04:58 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 08:04:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3561: WP15: Incorrect link in
 notice to translators
Message-ID: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>

#3561: WP15: Incorrect link in notice to translators
---------------------------+--------------------
 Reporter:  pedromendonca  |      Owner:  (none)
     Type:  defect         |     Status:  new
 Priority:  normal         |  Milestone:
Component:  General        |   Keywords:
---------------------------+--------------------
 For the Portuguese (pt_PT) version of the WP15 site, the call to
 translators to help completing the translation has an incorrect link.

 The call to action is currently hidden as the translation is complete, but
 will surely apear again as soon as there are new strings to translate.


 Current wrong link:
 https://translate.wordpress.org/projects/meta/wp15/pt-pt/default

 It should link to:
 https://translate.wordpress.org/projects/meta/wp15/pt/default

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

From noreply at wordpress.org  Mon Apr  9 08:05:19 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 08:05:19 -0000
Subject: [wp-meta] [Making WordPress.org] #3561: WP15: Incorrect link in
 notice to translators
In-Reply-To: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
References: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
Message-ID: <072.4d10136947c29af265c5415605b38f6f@wordpress.org>

#3561: WP15: Incorrect link in notice to translators
---------------------------+---------------------
 Reporter:  pedromendonca  |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:
 Keywords:                 |
---------------------------+---------------------
Changes (by pedromendonca):

 * Attachment "Screenshot 2018-04-08 19.31.09.png" added.

 Notice for translators

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

From noreply at wordpress.org  Mon Apr  9 08:33:19 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  9 Apr 2018 08:33:19 +0000 (UTC)
Subject: [wp-meta] [7067]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-accessibility.php:
 Main: About: Mark the Accessibility page strings as translatable.
Message-ID: <20180409083319.D77A41B005CE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  9 08:33:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 08:33:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.d791b3e036106eb3e8f7343d9f3d273d@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7067" 7067]:
 {{{
 #!CommitTicketReference repository="" revision="7067"
 Main: About: Mark the Accessibility page strings as translatable.

 H/t rianrietveld.
 See #3046.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 09:50:51 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 09:50:51 -0000
Subject: [wp-meta] [Making WordPress.org] #3562: misleading string on how to
 report a11y issues
Message-ID: <053.ac7bb3e2fa0afde4a7fc92d26170b408@wordpress.org>

#3562: misleading string on how to report a11y issues
-------------------------+--------------------
 Reporter:  Presskopp    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Handbooks    |   Keywords:
-------------------------+--------------------
 To report an Accessibility issue you’ve encountered in WordPress or on
 WordPress.org, please see the Accessibility Handbook on <a
 href="%s">Reporting Accessibility Issues</a>.

 I think this is not correct, bacause the link brings you to
 https://make.wordpress.org/accessibility/handbook/reporting-issues

 and there is no handbook but it's a sub part of the handbook. I propose to
 just use:

 ''To report an Accessibility issue you’ve encountered in WordPress or on
 WordPress.org, please see <a href="%s">Reporting Accessibility
 Issues</a>.''

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

From noreply at wordpress.org  Mon Apr  9 12:45:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 12:45:54 -0000
Subject: [wp-meta] [Making WordPress.org] #3563: typo: All new and updates
 code released in WordPress..
Message-ID: <053.b2d17f23e279acafac472380f0e4374e@wordpress.org>

#3563: typo: All new and updates code released in WordPress..
-----------------------+-------------------------
 Reporter:  Presskopp  |      Owner:  (none)
     Type:  defect     |     Status:  new
 Priority:  normal     |  Milestone:
Component:  General    |   Keywords:  needs-patch
-----------------------+-------------------------
 https://translate.wordpress.org/projects/meta/wordpress-
 org/de/default?filters%5Boriginal_id%5D=5891289

 After asking in slack @danieltj told me this strings needed to be
 ''updated'' instead of ''updates''

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

From noreply at wordpress.org  Mon Apr  9 18:22:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 18:22:10 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <065.3bf2e174ab767cc36b0ac77040369037@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
-------------------------+----------------------
 Reporter:  netweb       |       Owner:  ocean90
     Type:  defect       |      Status:  closed
 Priority:  high         |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+----------------------
Changes (by ocean90):

 * Attachment "test.txt" added.


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

From noreply at wordpress.org  Mon Apr  9 18:22:43 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 18:22:43 -0000
Subject: [wp-meta] [Making WordPress.org] #838: Ticket titles for ticket
 update notifications in Slack are truncated
In-Reply-To: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
References: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>
Message-ID: <050.890f7cb4a10b969ecd33a1843016c2bd@wordpress.org>

#838: Ticket titles for ticket update notifications in Slack are truncated
-------------------------+----------------------
 Reporter:  netweb       |       Owner:  ocean90
     Type:  defect       |      Status:  closed
 Priority:  high         |   Milestone:
Component:  Slack & IRC  |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+----------------------
Changes (by ocean90):

 * Attachment "test.txt" removed.


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

From noreply at wordpress.org  Mon Apr  9 19:27:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  9 Apr 2018 19:27:36 +0000 (UTC)
Subject: [wp-meta] [7068]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-accessibility.php:
 Main: About: Fix typo on Accessibility page.
Message-ID: <20180409192736.53C741B005CE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  9 19:27:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:27:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3563: typo: All new and
 updates code released in WordPress..
In-Reply-To: <053.b2d17f23e279acafac472380f0e4374e@wordpress.org>
References: <053.b2d17f23e279acafac472380f0e4374e@wordpress.org>
Message-ID: <068.17e4e48ae974effc9edbd16296bdf616@wordpress.org>

#3563: typo: All new and updates code released in WordPress..
-------------------------+-----------------------------
 Reporter:  Presskopp    |       Owner:  SergeyBiryukov
     Type:  defect       |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:  fixed
 Keywords:  needs-patch  |
-------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"7068" 7068]:
 {{{
 #!CommitTicketReference repository="" revision="7068"
 Main: About: Fix typo on Accessibility page.

 Props Presskopp.
 Fixes #3563. See #3046.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 19:27:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:27:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.e138050d97c557c770461bd5049f5dd1@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------

Comment (by SergeyBiryukov):

 In [changeset:"7068" 7068]:
 {{{
 #!CommitTicketReference repository="" revision="7068"
 Main: About: Fix typo on Accessibility page.

 Props Presskopp.
 Fixes #3563. See #3046.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 19:49:48 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:49:48 -0000
Subject: [wp-meta] [Making WordPress.org] #3561: WP15: Incorrect link in
 notice to translators
In-Reply-To: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
References: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
Message-ID: <072.e0d1d16cecd4562371749c21d0dddfa6@wordpress.org>

#3561: WP15: Incorrect link in notice to translators
---------------------------+---------------------------
 Reporter:  pedromendonca  |       Owner:  coreymckrill
     Type:  defect         |      Status:  assigned
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:
 Keywords:                 |
---------------------------+---------------------------
Changes (by iandunn):

 * owner:  (none) => coreymckrill
 * status:  new => assigned


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

From noreply at wordpress.org  Mon Apr  9 19:49:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:49:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3564: Trac: Move "Add Comment"
 section above "Modify Ticket"
Message-ID: <058.8223ef78f4215ae6a2da0697a24d4595@wordpress.org>

#3564: Trac: Move "Add Comment" section above "Modify Ticket"
----------------------------+--------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Trac            |   Keywords:
----------------------------+--------------------
 Before Trac upgrade, "Add Comment" section used to be above "Modify
 Ticket", to avoid unintentionally editing the ticket description instead
 of writing a comment.

 After the upgrade, "Modify Ticket" comes first and causes some confusion
 each time I'm leaving a comment.

 Noticed on Meta and bbPress Trac. Core Trac looks good, but still loads
 `wp-trac.css?92` instead of `wp-trac.css?94`, so could be using cached
 templates.

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

From noreply at wordpress.org  Mon Apr  9 19:50:14 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:50:14 -0000
Subject: [wp-meta] [Making WordPress.org] #3565: Trac: Default styles break
 page layout on preview
Message-ID: <058.5c4cd24fd4913d6e672602322cae1b90@wordpress.org>

#3565: Trac: Default styles break page layout on preview
----------------------------+--------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Trac            |   Keywords:
----------------------------+--------------------
 After Trac upgrade, when creating a ticket or commenting on an existing
 one, preview kicks in with some styles from the default template, breaking
 the page layout.

 See the screenshot.

 Noticed on Meta and bbPress Trac. Core Trac looks good, but still loads
 `wp-trac.css?92` instead of `wp-trac.css?94`, so could be using cached
 templates.

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

From noreply at wordpress.org  Mon Apr  9 19:50:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:50:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3565: Trac: Default styles
 break page layout on preview
In-Reply-To: <058.5c4cd24fd4913d6e672602322cae1b90@wordpress.org>
References: <058.5c4cd24fd4913d6e672602322cae1b90@wordpress.org>
Message-ID: <073.cd063890ca0f44d582e71acbe8e34dd2@wordpress.org>

#3565: Trac: Default styles break page layout on preview
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Trac            |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "3565.PNG" added.


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

From noreply at wordpress.org  Mon Apr  9 19:54:09 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:54:09 -0000
Subject: [wp-meta] [Making WordPress.org] #3565: Trac: Default styles
 break page layout on preview
In-Reply-To: <058.5c4cd24fd4913d6e672602322cae1b90@wordpress.org>
References: <058.5c4cd24fd4913d6e672602322cae1b90@wordpress.org>
Message-ID: <073.30edcab7942bac1fc7e89db67321aa04@wordpress.org>

#3565: Trac: Default styles break page layout on preview
----------------------------+------------------------
 Reporter:  SergeyBiryukov  |       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 #3526.

 See https://meta.trac.wordpress.org/ticket/3526#comment:17

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

From noreply at wordpress.org  Mon Apr  9 19:55:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:55:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3564: Trac: Move "Add
 Comment" section above "Modify Ticket"
In-Reply-To: <058.8223ef78f4215ae6a2da0697a24d4595@wordpress.org>
References: <058.8223ef78f4215ae6a2da0697a24d4595@wordpress.org>
Message-ID: <073.52d5e0d9c97f5c498dfca54419ff121a@wordpress.org>

#3564: Trac: Move "Add Comment" section above "Modify Ticket"
----------------------------+------------------------
 Reporter:  SergeyBiryukov  |       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 #3526.

 See https://meta.trac.wordpress.org/ticket/3526#comment:13

 Note that core.trac has not been moved to the new server/version yet.

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

From noreply at wordpress.org  Mon Apr  9 19:56:11 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 19:56:11 -0000
Subject: [wp-meta] [Making WordPress.org] #3562: misleading string on
 how to report a11y issues
In-Reply-To: <053.ac7bb3e2fa0afde4a7fc92d26170b408@wordpress.org>
References: <053.ac7bb3e2fa0afde4a7fc92d26170b408@wordpress.org>
Message-ID: <068.4f51c7922abb623d94d19e19e70845e1@wordpress.org>

#3562: misleading string on how to report a11y issues
-------------------------+---------------------
 Reporter:  Presskopp    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by SergeyBiryukov):

 The existing string looks good to me, it explains where the link goes.
 "on" means "on the topic of" here, not that the page itself is the
 handbook.

 It could probably be made a bit clearer with `"please see the
 Accessibility Handbook page on <a href="%s">Reporting Accessibility
 Issues</a>"`.

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

From noreply at wordpress.org  Mon Apr  9 20:37:36 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 20:37:36 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.743d921594b54993a24d06b89dea7281@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:18 dd32]:
 > Replying to [comment:13 ocean90]:
 > > The order of the "Modify Ticket" and "Add Comment" is different. It
 was "Add Comment" - "Modify Ticket" previously.
 >
 > Do we care about that order change? it doesn't seem to be a real issue
 to me

 The previous order was helpful to avoid unintentionally editing the ticket
 description instead of writing a comment.

 The current order causes some confusion each time I'm leaving a comment,
 and could probably cause even more confusion for new contributors.

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

From noreply at wordpress.org  Mon Apr  9 21:28:29 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  9 Apr 2018 21:28:29 +0000 (UTC)
Subject: [wp-meta] [7069]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Use an unlocalized format when converting between timezones.
Message-ID: <20180409212829.BBE8D1B005CE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  9 21:28:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 21:28:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3560: WP15 Theme: Event dates
 translation is showing current date/time
In-Reply-To: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
References: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
Message-ID: <072.18d0dcf60af7435ccbc64a4844587e54@wordpress.org>

#3560: WP15 Theme: Event dates translation is showing current date/time
---------------------------+----------------------
 Reporter:  pedromendonca  |       Owner:  iandunn
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:                 |
---------------------------+----------------------
Changes (by iandunn):

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


Comment:

 In [changeset:"7069" 7069]:
 {{{
 #!CommitTicketReference repository="" revision="7069"
 WP15: Use an unlocalized format when converting between timezones.

 Props pedromendonca.
 Fixes #3560.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 21:31:44 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 21:31:44 -0000
Subject: [wp-meta] [Making WordPress.org] #3560: WP15 Theme: Event dates
 translation is showing current date/time
In-Reply-To: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
References: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
Message-ID: <072.54e0725d806a1d8b638d58e6cb458c81@wordpress.org>

#3560: WP15 Theme: Event dates translation is showing current date/time
---------------------------+----------------------
 Reporter:  pedromendonca  |       Owner:  iandunn
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:                 |
---------------------------+----------------------

Comment (by iandunn):

 This should be fixed now, thanks for reporting it :)

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

From noreply at wordpress.org  Mon Apr  9 21:45:35 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  9 Apr 2018 21:45:35 +0000 (UTC)
Subject: [wp-meta] [7070]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/utilities/class-stripe-client.php:
 Stripe Client: Add note to clarify that `USD` should not be translated.
Message-ID: <20180409214535.A36911B005CE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr  9 21:45:36 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 21:45:36 -0000
Subject: [wp-meta] [Making WordPress.org] #3555: Clarify with a
 translator comment a WordCamp Stripe string
In-Reply-To: <050.8de49e14b4090d3bcf8dbd66b6c0924d@wordpress.org>
References: <050.8de49e14b4090d3bcf8dbd66b6c0924d@wordpress.org>
Message-ID: <065.229ac15d77fdaf1fda9e88b793b4ad94@wordpress.org>

#3555: Clarify with a translator comment a WordCamp Stripe string
-------------------------------------+----------------------
 Reporter:  netweb                   |       Owner:  iandunn
     Type:  defect                   |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  fixed
 Keywords:                           |
-------------------------------------+----------------------
Changes (by iandunn):

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


Comment:

 In [changeset:"7070" 7070]:
 {{{
 #!CommitTicketReference repository="" revision="7070"
 Stripe Client: Add note to clarify that `USD` should not be translated.

 Props netweb.
 Fixes #3555.
 }}}

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

From noreply at wordpress.org  Mon Apr  9 22:11:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 09 Apr 2018 22:11:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3237: Update the privacy
 policy
In-Reply-To: <049.73832814ca65128b9b52a37611086218@wordpress.org>
References: <049.73832814ca65128b9b52a37611086218@wordpress.org>
Message-ID: <064.55ce7e08d85655545fc6c9504486c304@wordpress.org>

#3237: Update the privacy policy
---------------------+-----------------------
 Reporter:  pento    |       Owner:  pento
     Type:  task     |      Status:  assigned
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+-----------------------

Comment (by robscott):

 @pento just adding 2 cents and a link to reference #43492. Would be great
 to see really specific language in the w.org privacy policy in relation to
 the `api.wordpress.org` data collection. Appreciate this is probably being
 chewed over by various lawyers at present, but would be a great thing if
 the spirit of what is said meets and far exceeds what is legally required.

 Beyond May's deadline, it would be nice to return to this subject at a
 little more leisure and get super transparent on all of this. Am willing
 to help where that is even possible :)

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

From noreply at wordpress.org  Tue Apr 10 00:28:14 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 00:28:14 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.ce7f1cee0289938264551d9135436239@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 Replying to [comment:23 SergeyBiryukov]:
 > Replying to [comment:18 dd32]:
 > > Replying to [comment:13 ocean90]:
 > > > The order of the "Modify Ticket" and "Add Comment" is different. It
 was "Add Comment" - "Modify Ticket" previously.
 > >
 > > Do we care about that order change? it doesn't seem to be a real issue
 to me
 >
 > The previous order was helpful to avoid unintentionally editing the
 ticket description instead of writing a comment. Adding a comment is a
 much more common action than editing the ticket, so it should come first.
 > The current order causes some confusion each time I'm leaving a comment,
 and could probably cause even more confusion for new contributors.

 Although I find it hard to believe that someone would accidentally edit
 the ticket description once used to the UI, and it's worth noting this is
 specifically for Bug Gardeners as regular users can't edit ticket
 descriptions, we might as well flip them back around then.

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

From noreply at wordpress.org  Tue Apr 10 00:48:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 00:48:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.da791d5a429189301df4f8f101e6727c@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:24 dd32]:
 > Although I find it hard to believe that someone would accidentally edit
 the ticket description once used to the UI

 I remember this being an occasional issue over the years, the sections
 were flipped for a reason :)

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

From noreply at wordpress.org  Tue Apr 10 00:50:17 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 00:50:17 +0000 (UTC)
Subject: [wp-meta] [7071]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks:
 WordCamp tickets: Wording changes, add rows to Attendee Info table
Message-ID: <20180410005017.5E99E1B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 00:53:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 00:53:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3560: WP15 Theme: Event dates
 translation is showing current date/time
In-Reply-To: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
References: <057.6e819c8fe19f2687f39d2c760a0b8f34@wordpress.org>
Message-ID: <072.47393835eec025f269f8a3df87d23794@wordpress.org>

#3560: WP15 Theme: Event dates translation is showing current date/time
---------------------------+----------------------
 Reporter:  pedromendonca  |       Owner:  iandunn
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:                 |
---------------------------+----------------------

Comment (by pedromendonca):

 Perfect. Great job!

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

From noreply at wordpress.org  Tue Apr 10 02:24:47 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 02:24:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3558: About section: improve
 formatting on Features page
In-Reply-To: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
References: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
Message-ID: <069.1563b8518b5993d4ba5a8624117b462d@wordpress.org>

#3558: About section: improve formatting on Features page
-------------------------+-----------------------
 Reporter:  tellyworth   |       Owner:  dd32
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Changes (by dd32):

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


Comment:

 Adding the following makes the page feel a little nicer:
  - A line break after `</strong>`
  - A line break after the `</li>`

 Simply adding a line break after `</strong>` doesn't work too well which
 is why i didn't change it at the time.

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

From noreply at wordpress.org  Tue Apr 10 02:26:48 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 02:26:48 -0000
Subject: [wp-meta] [Making WordPress.org] #3558: About section: improve
 formatting on Features page
In-Reply-To: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
References: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
Message-ID: <069.6c9524207faadf7d452404c6c56e3b49@wordpress.org>

#3558: About section: improve formatting on Features page
-------------------------+-----------------------
 Reporter:  tellyworth   |       Owner:  dd32
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Changes (by dd32):

 * Attachment "Screen Shot 2018-04-10 at 12.26.20 pm.png" added.


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

From noreply at wordpress.org  Tue Apr 10 02:42:42 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 02:42:42 +0000 (UTC)
Subject: [wp-meta] [7072]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory:
 Plugin Directory: Use geopattern icon assets in the `plugins/update-check`
 API response.
Message-ID: <20180410024242.E047A1B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 02:42:43 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 02:42:43 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.c8255f9aee6639fe5e48325152a56801@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7072" 7072]:
 {{{
 #!CommitTicketReference repository="" revision="7072"
 Plugin Directory: Use geopattern icon assets in the `plugins/update-check`
 API response.

 This change populates the `update_source` table which the update-check API
 uses, another change is needed to the update check itself to pull them
 through.
 Additionally a bin script to trigger an update for a single row (or all)
 is included.

 See #3265.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 03:45:50 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 03:45:50 +0000 (UTC)
Subject: [wp-meta] [7073]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub: Main:
 Features: Add a line break after the section title and after each dotpoint.
Message-ID: <20180410034550.31E051B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 03:45:51 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 03:45:51 -0000
Subject: [wp-meta] [Making WordPress.org] #3558: About section: improve
 formatting on Features page
In-Reply-To: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
References: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
Message-ID: <069.4c617ba5793de56692328b41e0ccb8a1@wordpress.org>

#3558: About section: improve formatting on Features page
-------------------------+---------------------
 Reporter:  tellyworth   |       Owner:  dd32
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------
Changes (by dd32):

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


Comment:

 In [changeset:"7073" 7073]:
 {{{
 #!CommitTicketReference repository="" revision="7073"
 Main: Features: Add a line break after the section title and after each
 dotpoint.

 Fixes #3558.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 03:47:11 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 03:47:11 +0000 (UTC)
Subject: [wp-meta] [7074]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/css/components/_page-features.scss:
 Main: Features: Add missing sass component from r7073
Message-ID: <20180410034711.3EF661B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 03:47:12 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 03:47:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3558: About section: improve
 formatting on Features page
In-Reply-To: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
References: <054.12bc0f596250af4342651ecfdd677cd1@wordpress.org>
Message-ID: <069.6f6b731c3c37627f74a3c4f123c6537a@wordpress.org>

#3558: About section: improve formatting on Features page
-------------------------+---------------------
 Reporter:  tellyworth   |       Owner:  dd32
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------

Comment (by dd32):

 In [changeset:"7074" 7074]:
 {{{
 #!CommitTicketReference repository="" revision="7074"
 Main: Features: Add missing sass component from r7073

 See #3558.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 04:24:17 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 04:24:17 +0000 (UTC)
Subject: [wp-meta] [7075]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory:
 Plugin Directory: API Updater: Lessen how much data is stored for plugin
 assets.
Message-ID: <20180410042417.89DC71B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 04:24:18 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 04:24:18 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.6a9138f2a839eba3533dad6af804e2a1@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+-----------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7075" 7075]:
 {{{
 #!CommitTicketReference repository="" revision="7075"
 Plugin Directory: API Updater: Lessen how much data is stored for plugin
 assets.

  - `default` is only needed for icons, banners don't need it.
  - `default` is now only used for icons 'geopattern' default icons.

 See #3265.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 04:28:49 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 04:28:49 +0000 (UTC)
Subject: [wp-meta] [7076]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php:
 Main: Security: Make the latest theme name dynamic.
Message-ID: <20180410042849.1D01C1B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 04:28:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 04:28:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.94dd8ac892ca34766c0c4b43b00e05a3@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+-----------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  accepted
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+-----------------------

Comment (by dd32):

 In [changeset:"7076" 7076]:
 {{{
 #!CommitTicketReference repository="" revision="7076"
 Main: Security: Make the latest theme name dynamic. Replaces 'Twenty
 Fifteen' with 'Twenty Seventeen'. Translations should hopefully still
 work.

 H/t la-geek.
 See #3046.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 06:23:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 06:23:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3265: Serve auto-generated
 plugin icons via URL
In-Reply-To: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
References: <048.5b16b7c5b9d75b20debfc3453c56c82c@wordpress.org>
Message-ID: <063.b88d29e18d02c97286580a80ab3dc192@wordpress.org>

#3265: Serve auto-generated plugin icons via URL
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------
Changes (by dd32):

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


Comment:

 The `plugins/update-check/` API has been updated to use this now.

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

From noreply at wordpress.org  Tue Apr 10 06:36:40 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 06:36:40 -0000
Subject: [wp-meta] [Making WordPress.org] #3528: Disable auto zoom in
 the Header Search Box on mobile
In-Reply-To: <052.7c14755f59f6bbee86799e89532c7fbe@wordpress.org>
References: <052.7c14755f59f6bbee86799e89532c7fbe@wordpress.org>
Message-ID: <067.74b495abb029477ca4fda2c9465db742@wordpress.org>

#3528: Disable auto zoom in the Header Search Box on mobile
---------------------------------------+------------------------
 Reporter:  raajtram                   |       Owner:  dd32
     Type:  defect                     |      Status:  reviewing
 Priority:  normal                     |   Milestone:
Component:  General                    |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+------------------------
Changes (by dd32):

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


Comment:

 Tested it out with an iPhone 8plus and looks good.

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

From noreply at wordpress.org  Tue Apr 10 06:38:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 06:38:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3528: Disable auto zoom in
 the Header Search Box on mobile
In-Reply-To: <052.7c14755f59f6bbee86799e89532c7fbe@wordpress.org>
References: <052.7c14755f59f6bbee86799e89532c7fbe@wordpress.org>
Message-ID: <067.7ac04fa2b710e1969309f2ccc29d8ab9@wordpress.org>

#3528: Disable auto zoom in the Header Search Box on mobile
---------------------------------------+---------------------
 Reporter:  raajtram                   |       Owner:  dd32
     Type:  defect                     |      Status:  closed
 Priority:  normal                     |   Milestone:
Component:  General                    |  Resolution:  fixed
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by dd32):

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


Comment:

 In [changeset:"7077" 7077]:
 {{{
 #!CommitTicketReference repository="" revision="7077"
 Styles: Disable Auto-zoom on the mobile search box by increasing the text
 size.

 Props raajtram.
 Fixes #3528.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 06:38:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 06:38:40 +0000 (UTC)
Subject: [wp-meta] [7077] sites/trunk/wordpress.org/public_html/style:
 Styles: Disable Auto-zoom on the mobile search box by increasing the text
 size.
Message-ID: <20180410063840.A19B91B005EB@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 09:21:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 09:21:10 -0000
Subject: [wp-meta] [Making WordPress.org] #3562: misleading string on
 how to report a11y issues
In-Reply-To: <053.ac7bb3e2fa0afde4a7fc92d26170b408@wordpress.org>
References: <053.ac7bb3e2fa0afde4a7fc92d26170b408@wordpress.org>
Message-ID: <068.d0ff1d02a1e604593c080eb3ece666d5@wordpress.org>

#3562: misleading string on how to report a11y issues
-------------------------+---------------------
 Reporter:  Presskopp    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by Presskopp):

 "on" means "on the topic of" here, not that the page itself is the
 handbook.

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

From noreply at wordpress.org  Tue Apr 10 09:33:51 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 09:33:51 +0000 (UTC)
Subject: [wp-meta] [7078]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Append a version
 string to Trac's JavaScript/CSS files hosted on the w.org CDN.
Message-ID: <20180410093351.413001B005EB@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 09:33:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 09:33:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.f675e81c0ebcf50264900698afe410cc@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by ocean90):

 In [changeset:"7078" 7078]:
 {{{
 #!CommitTicketReference repository="" revision="7078"
 Trac: Append a version string to Trac's JavaScript/CSS files hosted on the
 w.org CDN.

 For testing purposes limited to meta.trac for now.

 See #3526.
 }}}

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

From noreply at wordpress.org  Tue Apr 10 15:36:46 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 15:36:46 -0000
Subject: [wp-meta] [Making WordPress.org] #3566: Plugin Admin: Add User
 Notes to Author Card
Message-ID: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>

#3566: Plugin Admin: Add User Notes to Author Card
------------------------------+--------------------
 Reporter:  Ipstenu           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 Currently the plugin admin view has an author card that shows all the
 other plugins they've submitted.

 It would be nice to add here any user notes left by the forums team, so we
 could see if the account was flagged for things like spamming or abuse.

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

From noreply at wordpress.org  Tue Apr 10 15:51:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 15:51:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3567: Redirect my-patches and
 my-patches/all URLs for updated reports
Message-ID: <054.29d03e8c43b1d4e5d725339b3479a980@wordpress.org>

#3567: Redirect my-patches and my-patches/all URLs for updated reports
------------------------+--------------------
 Reporter:  stevenlinx  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  Trac        |   Keywords:
------------------------+--------------------
 There are inconsistencies between "`my-patches` | `my-patches/all`" pair
 and "`my-comments` | `my-comments/all`" pair

 The "`my-comments` | `my-comments/all`" pair work as they should, pointing
 to report {53} and {54} respectively:

    https://core.trac.wordpress.org/my-comments
    https://core.trac.wordpress.org/my-comments/all

 The "`my-patches` | `my-patches/all`" pair need to be updated:

    https://core.trac.wordpress.org/my-patches
    https://core.trac.wordpress.org/my-patches/all

 The respective "patches" reports in question are report {25} and {29}.

 Previously, both report {25} and report {29} were duplicates and show open
 tickets. However, report {29} already has the title "Open Tickets with My
 Patches", so if either one of them need to be updated, updating report
 {25} to include both open & closed tickets is more appropriate.

 After I raised the issue of duplicate reports, one of the meta admins
 acknowledged the issue and has updated the content of report {25} to
 include both open & closed tickets.

 Currently, `my-patches` still points to report {25} when it should be
 redirected to report {29} (open tickets). `my-patches/all` currently does
 not point to any report and should be redirected to the updated report
 {25} (open & closed tickets).

 As a result, the remaining task is to redirect the URLs:

    `my-patches` => report {29} (open tickets)

    `my-patches/all` => report {25} (open & closed tickets)

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

From noreply at wordpress.org  Tue Apr 10 16:44:56 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 16:44:56 +0000 (UTC)
Subject: [wp-meta] [7079]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins: WP15: Move
 pomo functionality to the locales.php file
Message-ID: <20180410164456.A69CB1B005EB@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 17:29:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 17:29:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3561: WP15: Incorrect link in
 notice to translators
In-Reply-To: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
References: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
Message-ID: <072.5ad30ac53642aa9c1d2ae2cd099c5088@wordpress.org>

#3561: WP15: Incorrect link in notice to translators
---------------------------+---------------------------
 Reporter:  pedromendonca  |       Owner:  coreymckrill
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:                 |
---------------------------+---------------------------
Changes (by coreymckrill):

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


Comment:

 In [changeset:"7080" 7080]:
 {{{
 #!CommitTicketReference repository="" revision="7080"
 WP15 locales: Use the correct locale string in the contribute URL

 Fixes #3561
 }}}

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

From noreply at wordpress.org  Tue Apr 10 17:29:44 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 17:29:44 +0000 (UTC)
Subject: [wp-meta] [7080]
 sites/trunk/wp15.wordpress.net/public_html/content/mu-plugins/locales.php:
 WP15 locales: Use the correct locale string in the contribute URL
Message-ID: <20180410172944.81FC51B005EB@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 10 23:08:17 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 10 Apr 2018 23:08:17 -0000
Subject: [wp-meta] [Making WordPress.org] #3561: WP15: Incorrect link in
 notice to translators
In-Reply-To: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
References: <057.36472a0cf036a035970ef3c262db8aab@wordpress.org>
Message-ID: <072.2850db1d9089e17c5342c36f81f41249@wordpress.org>

#3561: WP15: Incorrect link in notice to translators
---------------------------+---------------------------
 Reporter:  pedromendonca  |       Owner:  coreymckrill
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:  fixed
 Keywords:                 |
---------------------------+---------------------------

Comment (by coreymckrill):

 Thanks for the report, @pedromendonca !

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

From noreply at wordpress.org  Tue Apr 10 23:57:13 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 10 Apr 2018 23:57:13 +0000 (UTC)
Subject: [wp-meta] [7081]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/page-swag.php:
 WP15 theme: Use correct markup for Swag page title
Message-ID: <20180410235713.2627B1B005EB@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 00:16:47 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 00:16:47 +0000 (UTC)
Subject: [wp-meta] [7082]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15 theme: RTL adjustments
Message-ID: <20180411001647.44FA21B00613@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 02:38:53 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 02:38:53 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.4b99f6b0486249667e8da91eddfa6564@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 Replying to [comment:26 ocean90]:
 > In [changeset:"7078" 7078]:
 > {{{
 > #!CommitTicketReference repository="" revision="7078"
 > Trac: Append a version string to Trac's JavaScript/CSS files hosted on
 the w.org CDN.
 >
 > For testing purposes limited to meta.trac for now.
 >
 > See #3526.
 > }}}

 @ocean90 It seems like this unfortunately doesn't apply to the dynamic
 stylesheet URI's when included by
 {{{
 <script>jQuery.loadStyleSheet("https://s.w.org/style/trac/common/css/trac.css",
 "text/css");</script>
 }}}

 Causes both of these to be included:
  - https://s.w.org/style/trac/common/css/trac.css?v=94
  - https://s.w.org/style/trac/common/css/trac.css (on preview)

 I guess there's two options:
  1. Override the custom `$.fn.loadStyleSheet` to suffix the param (Which
 can be extracted from one of the existing stylesheets)
  2. Change the `py:match` to also match on
 `<script>jQuery.loadStyleSheet(` (and the script version too) and alter
 the URI in there?

 #1 shouldn't be too hard to achieve in `wp-trac.js`, but I'm curious if #2
 would be cleaner and longer-lasting?

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

From noreply at wordpress.org  Wed Apr 11 03:09:38 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 03:09:38 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.578b833577145360af9263046a6232a3@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
--------------------+---------------------
 Reporter:  dd32    |       Owner:  (none)
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+---------------------

Comment (by dd32):

 All Tracs (including core.trac.wordpress.org) have now been migrated. We
 can start applying the fixes globally.

 > Override the custom `$.fn.loadStyleSheet` to suffix the param
 I'm going to go ahead and do that short-term as I can test it out (I don't
 have a local Trac env), and it should fix the main thing people will
 notice (broken styled previews)

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

From noreply at wordpress.org  Wed Apr 11 04:46:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 04:46:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.2b057d2912a3dafc0c520b34dd23eb97@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------
Changes (by dd32):

 * priority:  normal => high


Comment:

 Bumping priority to get a property change listed on the ticket for
 testing.

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

From noreply at wordpress.org  Wed Apr 11 04:55:32 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 04:55:32 +0000 (UTC)
Subject: [wp-meta] [7083]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.js: Trac: Remove a
 Mozilla hack which will no longer work as `$.browser` has been removed and
 Trac has updated the jQuery version it uses.
Message-ID: <20180411045532.A01C51B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 04:55:33 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 04:55:33 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.0bb12e292d3df785538ee9728a2372c2@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7083" 7083]:
 {{{
 #!CommitTicketReference repository="" revision="7083"
 Trac: Remove a Mozilla hack which will no longer work as `$.browser` has
 been removed and Trac has updated the jQuery version it uses.

 The bug appears to be closed as WorksForMe on the mozilla end.
 See https://bugzilla.mozilla.org/show_bug.cgi?id=394782
 See https://core.trac.wordpress.org/ticket/17051
 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 04:59:27 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 04:59:27 +0000 (UTC)
Subject: [wp-meta] [7084]
 sites/trunk/common/includes/slack/trac/comment-handler.php: Fix warning:
 Undefined variable: multipart in comment-handler.php on line 93
Message-ID: <20180411045927.A19081B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 05:20:21 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 05:20:21 +0000 (UTC)
Subject: [wp-meta] [7085]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.js: Trac: Suffix
 cache buster keys to dynamically loaded JS/CSS files.
Message-ID: <20180411052021.94CE01B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 05:20:22 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 05:20:22 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.d381b40d5b07eacc53b7c27e777e1f0f@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7085" 7085]:
 {{{
 #!CommitTicketReference repository="" revision="7085"
 Trac: Suffix cache buster keys to dynamically loaded JS/CSS files.

 See #3526
 }}}

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

From noreply at wordpress.org  Wed Apr 11 05:49:00 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 05:49:00 +0000 (UTC)
Subject: [wp-meta] [7086]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.js: Trac: Fix the
 'Commits' section to work with jQuery 1.9.
Message-ID: <20180411054900.689C91B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 05:49:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 05:49:01 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.d6b9b3c22a395c5f75b73749922f9574@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7086" 7086]:
 {{{
 #!CommitTicketReference repository="" revision="7086"
 Trac: Fix the 'Commits' section to work with jQuery 1.9.
 As of 1.9 `.after()` cannot be used outside of the DOM, switch to using
 `.append()`.

 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 05:49:53 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 05:49:53 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.72c713d3230fe4293d62887e0b1040c6@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------
Changes (by iandunn):

 * Attachment "3117.diff" added.

 Render grid schedule based on feature flag, copy static markup/css from
 codepen

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

From noreply at wordpress.org  Wed Apr 11 05:54:39 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 05:54:39 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.0704012105ea2cf14e55470b098d58b4@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by iandunn):

 [attachment:3117.diff] is a very rough first pass, to illustrate how the
 feature flag could work. In my local environment I ran `wp wc-misc set-
 skip-feature-flag css-grid-schedule 70`, so that all of the sites with IDs
 `<= 70` will us the old schedule, and all the ones `> 70` will use the new
 one. See `wp help wc-misc set-skip-feature-flag`. You can also just change
 that to `if ( true ) {` for easier local testing.

 I copied over the markup and styles from the CodePen above, but didn't
 have time to start converting it to being generated dynamically.

 Another back-compat consideration is the personalized schedule builder
 from #2733. I don't think that'll pose a big problem, but it'll definitely
 need to be part of the testing process.

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

From noreply at wordpress.org  Wed Apr 11 06:07:57 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:07:57 +0000 (UTC)
Subject: [wp-meta] [7087]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.css: Trac: Update
 wp-trac.css with some more-specific selectors and overrides for Trac 1.2.2
 CSS.
Message-ID: <20180411060757.942501B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:07:58 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:07:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.52ad332571cf2263b1a9063adb01c5a7@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7087" 7087]:
 {{{
 #!CommitTicketReference repository="" revision="7087"
 Trac: Update wp-trac.css with some more-specific selectors and overrides
 for Trac 1.2.2 CSS.

 See #3526
 }}}

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

From noreply at wordpress.org  Wed Apr 11 06:17:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:17:40 +0000 (UTC)
Subject: [wp-meta] [7088]
 sites/trunk/wordpress.org/public_html/style/trac/common: Trac: Sync our
 copy of the trac htdocs with Trac-1.2.2
Message-ID: <20180411061740.2DDC81B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:17:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:17:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.7256e728876f7529b06803f436cd4fbb@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7088" 7088]:
 {{{
 #!CommitTicketReference repository="" revision="7088"
 Trac: Sync our copy of the trac htdocs with Trac-1.2.2

 This brings in the required CSS & JS trac uses.
 Source:  https://svn.edgewall.org/repos/trac/tags/trac-1.2.2/trac/htdocs/

 This change may cause some CSS & JS breakage where we've overridden the
 old trac CSS/JS with our own.

 See #3526
 }}}

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

From noreply at wordpress.org  Wed Apr 11 06:21:54 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:21:54 +0000 (UTC)
Subject: [wp-meta] [7089]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump the
 `scripts_version` for new assets.
Message-ID: <20180411062155.03C181B0069F@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:21:55 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:21:55 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.2e45994b5c8f7d7598682ec7c4615b89@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7089" 7089]:
 {{{
 #!CommitTicketReference repository="" revision="7089"
 Trac: Bump the `scripts_version` for new assets.

 See #3526
 }}}

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

From noreply at wordpress.org  Wed Apr 11 06:41:24 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:41:24 +0000 (UTC)
Subject: [wp-meta] [7090]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.js: Trac: Move
 'Add Comment' to before 'Modify Ticket'.
Message-ID: <20180411064124.E78481B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:41:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:41:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.7d63491d0fb4cc51e41e631404af4827@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7090" 7090]:
 {{{
 #!CommitTicketReference repository="" revision="7090"
 Trac: Move 'Add Comment' to before 'Modify Ticket'.

 This uses JS to move it, not ideal but we move a lot of the page around
 with JS already.

 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 06:43:55 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:43:55 +0000 (UTC)
Subject: [wp-meta] [7091]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.css: Trac: Show
 the property changes inline in comment previews.
Message-ID: <20180411064355.660EC1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:43:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:43:56 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.c8748f1b58c8bc80487429c85779e2ed@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7091" 7091]:
 {{{
 #!CommitTicketReference repository="" revision="7091"
 Trac: Show the property changes inline in comment previews.

 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 06:50:29 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:50:29 +0000 (UTC)
Subject: [wp-meta] [7092]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.css: Trac: Correct
 the colour of the logout link.
Message-ID: <20180411065029.8E6A81B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:50:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:50:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.b912121e30b00e51d5638083623a169f@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7092" 7092]:
 {{{
 #!CommitTicketReference repository="" revision="7092"
 Trac: Correct the colour of the logout link. This was previously an `<a>`
 but is now a `<button>`.

 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 06:57:41 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 06:57:41 +0000 (UTC)
Subject: [wp-meta] [7093]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Append a version
 string to Trac's JavaScript/CSS files hosted on the w.org CDN.
Message-ID: <20180411065741.8A8941B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 06:57:42 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 06:57:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.760cc3da981e38d42f3974b5a5ecc89c@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 In [changeset:"7093" 7093]:
 {{{
 #!CommitTicketReference repository="" revision="7093"
 Trac: Append a version string to Trac's JavaScript/CSS files hosted on the
 w.org CDN.

 This was previously enabled for meta.trac only as testing. It seems to
 have worked out well. Promoting to all Tracs.

 Props ocean90.
 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 07:29:17 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 07:29:17 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.d6cd0bcee61f4386c02a7a913b1f03e7@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 Looks like I broke the TicketGraph plugin with r7088, Trac now has jQuery
 1.9 which dropped the `$.browser` property.

 The Ticket Graph plugin (We're running `1.0-WordPress`) version we're
 using uses an out-of-date jQuery library.

 The latest version appears to have a more recent version of the library,
 I'm not sure what changes we made to the library though.

 https://github.com/trac-hacks/TracTicketGraph
 https://meta.trac.wordpress.org/ticketgraph

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

From noreply at wordpress.org  Wed Apr 11 07:44:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 07:44:57 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.a897cafb5de59f57490871fdec2c6688@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 Replying to [comment:40 dd32]:
 > The Ticket Graph plugin (We're running `1.0-WordPress`) version we're
 using uses an out-of-date jQuery library.
 >
 > The latest version appears to have a more recent version of the library,
 I'm not sure what changes we made to the library though.

 https://github.com/nacin/TracTicketGraph
  - Added Query by Ticket Type (defect/enhancement/task)
  - sqlite & mysql support
  - increased from 30days to 90days by default

 Looks like https://github.com/trac-hacks/TracTicketGraph should probably
 easily merge into our version.

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

From noreply at wordpress.org  Wed Apr 11 08:14:48 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 08:14:48 +0000 (UTC)
Subject: [wp-meta] [7094]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.css: Trac: Update
 wp-trac.css with some more-specific selectors and overrides for Trac 1.2.2
 CSS.
Message-ID: <20180411081448.8663B1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 08:14:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 08:14:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.c33ce237f88dd94ffe73f8292ac30a76@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by ocean90):

 In [changeset:"7094" 7094]:
 {{{
 #!CommitTicketReference repository="" revision="7094"
 Trac: Update wp-trac.css with some more-specific selectors and overrides
 for Trac 1.2.2 CSS.

 See #3526.
 }}}

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

From noreply at wordpress.org  Wed Apr 11 08:47:56 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 08:47:56 +0000 (UTC)
Subject: [wp-meta] [7095]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump scripts
 version.
Message-ID: <20180411084756.5FACA1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 11:23:10 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 11:23:10 +0000 (UTC)
Subject: [wp-meta] [7096]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-plugin-directory/inc/cli/class-set-plugin-project.php:
 Translate, Plugin Directory: Use correct variable for the plugin project.
Message-ID: <20180411112310.036DD1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 14:53:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 14:53:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.6865fa67368266eb8786621d63d99c3e@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------
Changes (by iandunn):

 * Attachment "3117.2.diff" added.

 Dynamically generate markup/css

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

From noreply at wordpress.org  Wed Apr 11 14:54:19 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 14:54:19 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.f8545ab7c1d3147e9f4133363d49a3b5@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by iandunn):

 [attachment:3117.2.diff] is a rough pass at dynamically generating the
 markup and CSS, but it doesn't correctly set the `grid-column` value for
 each `div.session`.

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

From noreply at wordpress.org  Wed Apr 11 15:57:55 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 15:57:55 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.54ec10c15f862de7637d0eea4bc594c8@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------
Changes (by iandunn):

 * Attachment "3117.3.diff" added.

 Create rows for every 5 minutes; remove duplicate sessions

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

From noreply at wordpress.org  Wed Apr 11 16:44:04 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 11 Apr 2018 16:44:04 +0000 (UTC)
Subject: [wp-meta] [7097]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/addons/code-of-conduct.php:
 WordCamp tickets: Use correct textdomain
Message-ID: <20180411164404.CCBE11B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 11 18:19:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 11 Apr 2018 18:19:10 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.951b9f437449662a1149377c20a792b4@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------
Changes (by iandunn):

 * Attachment "3117.4.diff" added.

 Minor iteration on 3.diff

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

From noreply at wordpress.org  Thu Apr 12 00:19:35 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 12 Apr 2018 00:19:35 +0000 (UTC)
Subject: [wp-meta] [7098]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp: Require
 special caps in order to change a WordCamp's sponsor region
Message-ID: <20180412001935.3D0281B006B0@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 12 00:42:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 12 Apr 2018 00:42:36 +0000 (UTC)
Subject: [wp-meta] [7099]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/style.css:
 WP15: Tweak margins on the `About` page.
Message-ID: <20180412004236.A5E3A1B006B0@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 12 00:42:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 12 Apr 2018 00:42:40 +0000 (UTC)
Subject: [wp-meta] [7100]
 sites/trunk/wp15.wordpress.net/public_html/content: WP15: Add a
 `placeholder` value to the event filter input field.
Message-ID: <20180412004240.7431B1B006B0@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 12 02:23:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 02:23:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3566: Plugin Admin: Add User
 Notes to Author Card
In-Reply-To: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>
References: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>
Message-ID: <066.6fbcf54dd26c8dd7077198f1d632c4e7@wordpress.org>

#3566: Plugin Admin: Add User Notes to Author Card
------------------------------+-----------------------------
 Reporter:  Ipstenu           |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


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

From noreply at wordpress.org  Thu Apr 12 12:54:25 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 12 Apr 2018 12:54:25 +0000 (UTC)
Subject: [wp-meta] [7101]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/admin/metabox/class-author-card.php:
 Plugin Directory, Author Card: Display user notes from support forums.
Message-ID: <20180412125425.E28271B00437@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 12 12:54:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 12:54:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3566: Plugin Admin: Add User
 Notes to Author Card
In-Reply-To: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>
References: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>
Message-ID: <066.c54a30b0049958d7dd54d1f5a5c96812@wordpress.org>

#3566: Plugin Admin: Add User Notes to Author Card
------------------------------+-----------------------------
 Reporter:  Ipstenu           |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"7101" 7101]:
 {{{
 #!CommitTicketReference repository="" revision="7101"
 Plugin Directory, Author Card: Display user notes from support forums.

 Fixes #3566.
 }}}

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

From noreply at wordpress.org  Thu Apr 12 13:00:56 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 12 Apr 2018 13:00:56 +0000 (UTC)
Subject: [wp-meta] [7102]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/admin/metabox/class-author-card.php:
 Plugin Directory, Author Card: Remove stray closing tag.
Message-ID: <20180412130056.4F7CE1B00437@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 12 13:00:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 13:00:57 -0000
Subject: [wp-meta] [Making WordPress.org] #3566: Plugin Admin: Add User
 Notes to Author Card
In-Reply-To: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>
References: <051.6a4142721e7d116f1145ebddaa9b8ea4@wordpress.org>
Message-ID: <066.f3d3ab2e90296909f86f3b41ab87948e@wordpress.org>

#3566: Plugin Admin: Add User Notes to Author Card
------------------------------+-----------------------------
 Reporter:  Ipstenu           |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [changeset:"7102" 7102]:
 {{{
 #!CommitTicketReference repository="" revision="7102"
 Plugin Directory, Author Card: Remove stray closing tag.

 See #3566.
 }}}

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

From noreply at wordpress.org  Thu Apr 12 14:31:18 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 14:31:18 -0000
Subject: [wp-meta] [Making WordPress.org] #3568: WP15: Page titles aren't
 internationalized
Message-ID: <051.30ea8ef304c4d5fa5d987a15cc787181@wordpress.org>

#3568: WP15: Page titles aren't internationalized
---------------------+--------------------
 Reporter:  dimadin  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:
---------------------+--------------------
 Related [7055]

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

From noreply at wordpress.org  Thu Apr 12 14:38:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 14:38:10 -0000
Subject: [wp-meta] [Making WordPress.org] #3569: WP15 Theme: Allow
 translators to disable Google Fonts for their language
Message-ID: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>

#3569: WP15 Theme: Allow translators to disable Google Fonts for their language
---------------------+-----------------------
 Reporter:  dimadin  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:  has-patch
---------------------+-----------------------
 Attached is a patch that takes approach from default WordPress themes.
 Note that `subset` query arg
 [https://developers.google.com/fonts/docs/getting_started#specifying_script_subsets
 takes effect only] for browsers that don't support `unicode-range`.

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

From noreply at wordpress.org  Thu Apr 12 14:38:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 14:38:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3569: WP15 Theme: Allow
 translators to disable Google Fonts for their language
In-Reply-To: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
References: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
Message-ID: <066.a95816b550c94458e54148a8a07a445e@wordpress.org>

#3569: WP15 Theme: Allow translators to disable Google Fonts for their language
-----------------------+---------------------
 Reporter:  dimadin    |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------
Changes (by dimadin):

 * Attachment "3569.diff" added.


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

From noreply at wordpress.org  Thu Apr 12 17:27:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 17:27:30 -0000
Subject: [wp-meta] [Making WordPress.org] #1183: Checkbox for
 Contributor Days
In-Reply-To: <052.ab0952f1b1e2743f6bb56d2d7c77bcc3@wordpress.org>
References: <052.ab0952f1b1e2743f6bb56d2d7c77bcc3@wordpress.org>
Message-ID: <067.a179315e35f4f6770dfde9355b3210f9@wordpress.org>

#1183: Checkbox for Contributor Days
-------------------------------------------------+-------------------------
 Reporter:  miss_jwo                             |       Owner:
                                                 |  DrewAPicture
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:
Component:  WordCamp Site & Plugins              |  Resolution:
 Keywords:  good-first-bug needs-testing has-    |
  screenshots has-patch                          |
-------------------------------------------------+-------------------------
Changes (by hlashbrooke):

 * Attachment "1183.2.diff" added.

 Refreshing from origin

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

From noreply at wordpress.org  Thu Apr 12 17:44:27 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 17:44:27 -0000
Subject: [wp-meta] [Making WordPress.org] #3550: Plugins search with
 countdown keyword does not work
In-Reply-To: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>
References: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>
Message-ID: <068.d33d1f9503445a3d0485ee8cf04c49c9@wordpress.org>

#3550: Plugins search with countdown keyword does not work
------------------------------+------------------------------
 Reporter:  adamskaat         |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Improved Search
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------------------

Comment (by gibrown):

 Should be all fixed now, and I've reindexed all plugins. Sorry for the
 slow fix I wanted to make sure I got enough review of the fix since it
 affects all of our indexing.

 The root cause is kinda crazy.

 The cause is:

 1. A doc with post meta of "2e47eb" (this was on the beeketing plugin for
 the color code of the header https://wordpress.org/plugins/beeketing-for-
 woocommerce/)
 2. In addition to indexing the string, we try to index all meta as a long
 and a float.
 3. When php converts to a float, we get 2e47 (Whee!)
 4. When php outputs 2e47 it becomes
 200000000000000008769168609015239470926809530368.0 in the json. (Ugh!)
 5. ES indexes this fine, it doesn't fail. (Hmmm)
 6. Our search queries request a couple of fields beyond just post_id. Some
 of these fields are not "stored" so ES has to take the original _source
 json and reparse it to fulfill the request
 7. The JSON parser for extracting fields though apparently does not handle
 these large values in the same way as the indexing parser. So
 200000000000000008769168609015239470926809530368.0 is unparsable because
 it is so large and an error is thrown.

 Ultimately the fix is to have better boundary checking on the fields when
 indexing.

 Basically any search that was returning the beeketing plugin in the
 results was triggering this failure. "countdown" just happened to be one
 case. It looks like there was at least one other plugin that had this
 problem also. I can see from query logs that this fix has cleaned up a
 number of query failures (they were pretty rare, but had been getting more
 common). Not seeing any query failures now.

 Thanks for reporting this.

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

From noreply at wordpress.org  Thu Apr 12 18:10:22 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 12 Apr 2018 18:10:22 -0000
Subject: [wp-meta] [Making WordPress.org] #3550: Plugins search with
 countdown keyword does not work
In-Reply-To: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>
References: <053.424a7c69a818ac755de772dac7fb325c@wordpress.org>
Message-ID: <068.e684ec9e560f5382b80bf1462bd08827@wordpress.org>

#3550: Plugins search with countdown keyword does not work
------------------------------+------------------------------
 Reporter:  adamskaat         |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Improved Search
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+------------------------------
Changes (by Otto42):

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


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

From noreply at wordpress.org  Thu Apr 12 20:04:10 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 12 Apr 2018 20:04:10 +0000 (UTC)
Subject: [wp-meta] [7103]
 sites/trunk/trac.wordpress.org/conf/common-extended.ini: Enable limit for
 trac changeset view
Message-ID: <20180412200410.4CE561B00437@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 13 00:01:55 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 13 Apr 2018 00:01:55 +0000 (UTC)
Subject: [wp-meta] [7104]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/gutenberg/inc/docs-importer.php:
 Gutenberg Docs: Remove the .md extension from relative links.
Message-ID: <20180413000155.ADC7A1B005CE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 13 12:48:43 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 13 Apr 2018 12:48:43 +0000 (UTC)
Subject: [wp-meta] [7105]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.css: Trac: Update
 wp-trac.css with some more-specific selectors and overrides for Trac 1.2.2
 CSS.
Message-ID: <20180413124843.9382C1B00272@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 13 12:48:44 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 12:48:44 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.a09164c42a2446ff09122c83ac97752a@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by ocean90):

 In [changeset:"7105" 7105]:
 {{{
 #!CommitTicketReference repository="" revision="7105"
 Trac: Update wp-trac.css with some more-specific selectors and overrides
 for Trac 1.2.2 CSS.

 See #3526.
 }}}

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

From noreply at wordpress.org  Fri Apr 13 15:30:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 15:30:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3570: e-mail notification for new
 posts in pending/spam in support forum
Message-ID: <056.bcc91a81ae8adbea14f8a7c166234a42@wordpress.org>

#3570: e-mail notification for new posts in pending/spam in support forum
----------------------------+--------------------
 Reporter:  tobifjellner    |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 Some small forums (like the Swedish one) have limited traffic. There may
 be between 0 and 10 new topics a week.
 With such low traffic, the typical workflow for support volunteers is
 push-enabled: You activate e-mail notifications for new topics in all
 relevant forums, rather than logging in ans browsing for topics that
 haven't got any reply yet.
 This works fine...

 BUT: The queues for pending and spam are even more quiet, so far. Haven't
 yet seen any real spam (knock on wood), but once in a blue moon there will
 be a false positive, and someones question (or answer) will go to the spam
 bucket.
 In this situation, you simply forget to scan spam and pending.
 It would be great to have a setting that would enable me to be notified
 whenever anything lands in these queues. (And, obviusly, to have a
 possibility to turn this off later if and when traffic goes up...)

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

From noreply at wordpress.org  Fri Apr 13 16:39:47 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 16:39:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3568: WP15: Page titles
 aren't internationalized
In-Reply-To: <051.30ea8ef304c4d5fa5d987a15cc787181@wordpress.org>
References: <051.30ea8ef304c4d5fa5d987a15cc787181@wordpress.org>
Message-ID: <066.15fa0d105e85b61c33a1308d3238caae@wordpress.org>

#3568: WP15: Page titles aren't internationalized
---------------------+---------------------
 Reporter:  dimadin  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by iandunn):

 They're internationalized when used in the `<h1 class="entry-title">`, but
 it looks like they're not in `<title>`. Are you seeing anywhere else where
 they're not?

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

From noreply at wordpress.org  Fri Apr 13 16:42:15 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 16:42:15 -0000
Subject: [wp-meta] [Making WordPress.org] #3569: WP15 Theme: Allow
 translators to disable Google Fonts for their language
In-Reply-To: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
References: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
Message-ID: <066.980251738b8225572ddd5894a8291cf3@wordpress.org>

#3569: WP15 Theme: Allow translators to disable Google Fonts for their language
-----------------------+---------------------
 Reporter:  dimadin    |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------

Comment (by iandunn):

 @melchoyce, do you have any preferred backup fonts for locales where Crete
 Round and/or Source Sans Pro are disabled?

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

From noreply at wordpress.org  Fri Apr 13 17:24:29 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 13 Apr 2018 17:24:29 +0000 (UTC)
Subject: [wp-meta] [7106]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15:
 WP15: Internationalize site titles.
Message-ID: <20180413172429.0732A1B00272@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 13 17:24:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 17:24:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3568: WP15: Page titles
 aren't internationalized
In-Reply-To: <051.30ea8ef304c4d5fa5d987a15cc787181@wordpress.org>
References: <051.30ea8ef304c4d5fa5d987a15cc787181@wordpress.org>
Message-ID: <066.26b8b3be4b2bf4f5b14a7d2955f39e41@wordpress.org>

#3568: WP15: Page titles aren't internationalized
---------------------+---------------------
 Reporter:  dimadin  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:
 Keywords:           |
---------------------+---------------------

Comment (by iandunn):

 In [changeset:"7106" 7106]:
 {{{
 #!CommitTicketReference repository="" revision="7106"
 WP15: Internationalize site titles.

 See #3568.
 }}}

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

From noreply at wordpress.org  Fri Apr 13 17:54:11 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 17:54:11 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.91d5e3f850a641e09a0755066b226f03@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by iandunn):

 This should probably output the session categories in addition to the
 session tracks.

 It seems like it'd be better to do that in actual markup, rather than with
 CSS `content`, but I don't remember the reasons why we used `content` for
 the table schedule. It was added in r500 for #353. @nvwd, do you have any
 thoughts on using markup vs `content`? I'm curious if you do as well,
 @mrwweb.

 It seems like markup is more semantic/accessible, and it also allows for
 multiple categories. CSS `content` overrides previous categories, although
 I guess we could change `data-track-title` to include all the category
 names.

 https://wordpress.slack.com/archives/C08M59V3P/p1523525100000375

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

From noreply at wordpress.org  Fri Apr 13 18:47:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 18:47:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.7ff3fb445765c003b9502a66d2f4419d@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by nvwd):

 I don't have a reason to use one over the other. Switching to markup seems
 like a good thing.

 Love the use of CSS grid here.

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

From noreply at wordpress.org  Fri Apr 13 20:04:14 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 20:04:14 -0000
Subject: [wp-meta] [Making WordPress.org] #3282: Profiles: Badges should
 have a textual representation
In-Reply-To: <056.357f13754a427f37d37041161766904f@wordpress.org>
References: <056.357f13754a427f37d37041161766904f@wordpress.org>
Message-ID: <071.030aa4f2e0b965ad95c318b3db5ba045@wordpress.org>

#3282: Profiles: Badges should have a textual representation
--------------------------------------------------+---------------------
 Reporter:  LiamMcArthur                          |       Owner:  (none)
     Type:  enhancement                           |      Status:  new
 Priority:  normal                                |   Milestone:
Component:  Profiles                              |  Resolution:
 Keywords:  needs-design needs-patch ui-feedback  |
--------------------------------------------------+---------------------
Changes (by pratikthink):

 * keywords:   => needs-design needs-patch ui-feedback


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

From noreply at wordpress.org  Fri Apr 13 20:08:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 20:08:07 -0000
Subject: [wp-meta] [Making WordPress.org] #2729: Profiles: Notifications
 from plugin/theme forums should include the plugin/theme name
In-Reply-To: <058.8a525e6c9727d889e75d8c3980be8631@wordpress.org>
References: <058.8a525e6c9727d889e75d8c3980be8631@wordpress.org>
Message-ID: <073.f925199b2964572f842b9125a4607639@wordpress.org>

#2729: Profiles: Notifications from plugin/theme forums should include the
plugin/theme name
-----------------------------------------------------+---------------------
 Reporter:  SergeyBiryukov                           |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:
Component:  Profiles                                 |  Resolution:
 Keywords:  needs-patch ux-feedback has-screenshots  |
-----------------------------------------------------+---------------------
Changes (by pratikthink):

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


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

From noreply at wordpress.org  Fri Apr 13 20:26:40 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 20:26:40 -0000
Subject: [wp-meta] [Making WordPress.org] #871: Inactive Profiles Need a
 Better Design
In-Reply-To: <051.ea0d49f60e0b790fd20f299252e7b14b@wordpress.org>
References: <051.ea0d49f60e0b790fd20f299252e7b14b@wordpress.org>
Message-ID: <066.7eaef5aadccc6c2424397b6989220fd7@wordpress.org>

#871: Inactive Profiles Need a Better Design
-------------------------+-------------------------
 Reporter:  iandunn      |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  low          |   Milestone:
Component:  Profiles     |  Resolution:  maybelater
 Keywords:  needs-ui     |
-------------------------+-------------------------
Changes (by pratikthink):

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


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

From noreply at wordpress.org  Fri Apr 13 20:54:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 20:54:05 -0000
Subject: [wp-meta] [Making WordPress.org] #229: Rosetta API
In-Reply-To: <056.9cbff9b11a27581e0510949dab46fc26@wordpress.org>
References: <056.9cbff9b11a27581e0510949dab46fc26@wordpress.org>
Message-ID: <071.2cacc6e5f19446e5575e076d9531480e@wordpress.org>

#229: Rosetta API
--------------------------------+----------------------
 Reporter:  markoheijnen        |       Owner:  (none)
     Type:  enhancement         |      Status:  closed
 Priority:  lowest              |   Milestone:
Component:  API                 |  Resolution:  wontfix
 Keywords:  dev-feedback close  |
--------------------------------+----------------------
Changes (by pratikthink):

 * keywords:  dev-feedback => dev-feedback close
 * status:  new => closed
 * resolution:   => wontfix


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

From noreply at wordpress.org  Fri Apr 13 21:51:23 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 13 Apr 2018 21:51:23 +0000 (UTC)
Subject: [wp-meta] [7107]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/functions.php:
 WP15 theme: Change context of "Live" page title
Message-ID: <20180413215123.805AE1B00272@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 13 22:41:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 22:41:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3569: WP15 Theme: Allow
 translators to disable Google Fonts for their language
In-Reply-To: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
References: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
Message-ID: <066.7c4ef79aab9c6fa1dc0c976cbb20976a@wordpress.org>

#3569: WP15 Theme: Allow translators to disable Google Fonts for their language
-----------------------+---------------------
 Reporter:  dimadin    |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------

Comment (by melchoyce):

 For the sans serif, we'll probably want to look at Twenty Seventeen's font
 stack. You can't really go wrong with Arial generally.

 Crete Round is more of a stylistic choice, so in that case, it really
 depends on the language/alphabet. I don't want to say "go with a serif,"
 because some alphabets don't necessarily have serifs — and if they do,
 they don't always look great. (I feel like I remember someone — maybe
 @ranyanivhartstein? — saying that Hebrew serif fonts were pretty
 illegible?)

 Would love to get some suggestions if we have designers with experience in
 non-latin alphabets.

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

From noreply at wordpress.org  Fri Apr 13 22:56:43 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 22:56:43 -0000
Subject: [wp-meta] [Making WordPress.org] #3117: Schedule: Support
 sessions that span multiple time slots
In-Reply-To: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
References: <050.68c3c96c6756de1246ef6ce78d108005@wordpress.org>
Message-ID: <065.0241bf2c2c43265bfce50c0c402a4cfa@wordpress.org>

#3117: Schedule: Support sessions that span multiple time slots
-------------------------------------+---------------------
 Reporter:  mrwweb                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+---------------------

Comment (by mrwweb):

 Categories should ''definitely'' be in the source. They'll be more
 flexible to style (they should have a wrapper with a unique class) and for
 accessibility purposes, you can't rely on the `content` property to be
 announced to all screen readers. (At least that's my historical memory.)

 I could imagine a shortcode parameter to show/hide categories might be
 useful if we think not everyone would want them visible. (And if
 implemented, there should NOT be equivalent options to hide track and time
 unless they're left in the source and hidden accessibly, since those
 pieces of info are critical to finding the session.)

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

From noreply at wordpress.org  Fri Apr 13 23:39:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 23:39:01 -0000
Subject: [wp-meta] [Making WordPress.org] #3569: WP15 Theme: Allow
 translators to disable Google Fonts for their language
In-Reply-To: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
References: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
Message-ID: <066.68d2f906f140c8cd6f8e47c118c8cca4@wordpress.org>

#3569: WP15 Theme: Allow translators to disable Google Fonts for their language
-----------------------+---------------------
 Reporter:  dimadin    |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------

Comment (by SergeyBiryukov):

 WordPress core and bundled themes generally use Tahoma for RTL, except for
 Hebrew, which uses Arial. Twenty Seventeen seems to handle this correctly.

 [attachment:3569.diff] looks good to me.

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

From noreply at wordpress.org  Fri Apr 13 23:43:59 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 23:43:59 -0000
Subject: [wp-meta] [Making WordPress.org] #527: Profiles: Badges should
 link to the corresponding team
In-Reply-To: <058.b4481a42668ad35bf6fe6017028c920b@wordpress.org>
References: <058.b4481a42668ad35bf6fe6017028c920b@wordpress.org>
Message-ID: <073.83e98982147ea259d63b67fa86f4a61e@wordpress.org>

#527: Profiles: Badges should link to the corresponding team
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by SergeyBiryukov):

 Related: #3282

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

From noreply at wordpress.org  Fri Apr 13 23:44:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 13 Apr 2018 23:44:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3282: Profiles: Badges should
 have a textual representation
In-Reply-To: <056.357f13754a427f37d37041161766904f@wordpress.org>
References: <056.357f13754a427f37d37041161766904f@wordpress.org>
Message-ID: <071.be6ecb7a5b661210d875542315cfc3e1@wordpress.org>

#3282: Profiles: Badges should have a textual representation
--------------------------------------------------+---------------------
 Reporter:  LiamMcArthur                          |       Owner:  (none)
     Type:  enhancement                           |      Status:  new
 Priority:  normal                                |   Milestone:
Component:  Profiles                              |  Resolution:
 Keywords:  needs-design needs-patch ui-feedback  |
--------------------------------------------------+---------------------

Comment (by SergeyBiryukov):

 Related: #527

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

From noreply at wordpress.org  Sat Apr 14 00:54:21 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 00:54:21 -0000
Subject: [wp-meta] [Making WordPress.org] #871: Inactive Profiles Need a
 Better Design
In-Reply-To: <051.ea0d49f60e0b790fd20f299252e7b14b@wordpress.org>
References: <051.ea0d49f60e0b790fd20f299252e7b14b@wordpress.org>
Message-ID: <066.361be02593a394ed38852cb72456967f@wordpress.org>

#871: Inactive Profiles Need a Better Design
-------------------------+-----------------------
 Reporter:  iandunn      |       Owner:  (none)
     Type:  enhancement  |      Status:  reopened
 Priority:  low          |   Milestone:
Component:  Profiles     |  Resolution:
 Keywords:  needs-ui     |
-------------------------+-----------------------
Changes (by iandunn):

 * status:  closed => reopened
 * resolution:  maybelater =>


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

From noreply at wordpress.org  Sat Apr 14 04:44:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 04:44:49 -0000
Subject: [wp-meta] [Making WordPress.org] #634: SSL for
 planet.wordpress.org
In-Reply-To: <049.a13067e007d8eb2e328fe7fa921a1976@wordpress.org>
References: <049.a13067e007d8eb2e328fe7fa921a1976@wordpress.org>
Message-ID: <064.699dba6ad34f6a8cf8098034f7167f92@wordpress.org>

#634: SSL for planet.wordpress.org
--------------------+-----------------------
 Reporter:  nacin   |       Owner:  Otto42
     Type:  task    |      Status:  assigned
 Priority:  normal  |   Milestone:
Component:  SSL     |  Resolution:
 Keywords:          |
--------------------+-----------------------

Comment (by dougal):

 Sorry, I forgot to come back and update. SSL implemented:

 https://dougal.gunters.org/blog/tag/wordpress/feed/

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

From noreply at wordpress.org  Sat Apr 14 10:06:13 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 10:06:13 -0000
Subject: [wp-meta] [Making WordPress.org] #3571: Add background-repeat &
 background-position in the Plugin directory css
Message-ID: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>

#3571: Add background-repeat & background-position in the Plugin directory css
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  (none)
  mostafa.s1990          |
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Plugin Directory v3.0
Component:  Plugin       |   Keywords:  ui-feedback has-screenshots needs-
  Directory              |  design
-------------------------+-------------------------------------------------
 Hi,

 I'm surprised why these 2 values are not added with (https://s.w.org/wp-
 content/themes/pub/wporg-plugins/css/style.css)


 {{{
 .single .entry-thumbnail .plugin-icon {
     -webkit-background-size: contain!important;
     background-size: contain!important;
     height: 96px!important;
     width: 96px!important;
     background-repeat: no-repeat;
     background-position: center;
 }
 }}}


 See the attachment.
 [[Image(http://mostafa-soufi.ir/wp-content/uploads/2018/04/screenshot-
 wordpress.org-2018.04.14-14-29-31.png)]]

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

From noreply at wordpress.org  Sat Apr 14 10:06:32 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 10:06:32 -0000
Subject: [wp-meta] [Making WordPress.org] #3571: Add background-repeat &
 background-position in the Plugin directory css
In-Reply-To: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
References: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
Message-ID: <072.46765081a3ecd2208013d9688cd1b6ae@wordpress.org>

#3571: Add background-repeat & background-position in the Plugin directory css
-------------------------------------------------+-------------------------
 Reporter:  mostafa.s1990                        |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Plugin
                                                 |  Directory v3.0
Component:  Plugin Directory                     |  Resolution:
 Keywords:  ui-feedback has-screenshots needs-   |
  design                                         |
-------------------------------------------------+-------------------------
Changes (by mostafa.s1990):

 * Attachment "screenshot-wordpress.org-2018.04.14-14-29-31.png" added.


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

From noreply at wordpress.org  Sat Apr 14 13:40:22 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 13:40:22 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit their
 own notes
Message-ID: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------+-----------------------
 Reporter:  keesiemeijer   |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:
Component:  Developer Hub  |   Keywords:  has-patch
---------------------------+-----------------------
 Users should be able to edit their own user contributed notes.
 See [https://meta.trac.wordpress.org/ticket/1504#comment:4 this comment]

 The patch adds the ability for users to edit their own contributed notes.

 Users can only edit a note if it's awaiting moderation. The endpoint
 `reference/comment/edit/{comment_ID}` is created for users to edit their
 notes in the front end of the site. You're redirected to the home page
 (from this endpoint) if the note doesn't exist, or you don't have the
 right edit permissions. A new template `comments-edit.php` is used for the
 edit note form.

 This patch also adds the following rules to the feedback form (similar to
 the note form).
 * This form is not for support requests, spam, bug reports, complaints, or
 self-promotion. Entries of this nature will be deleted.
 * NOTE: All contributions are licensed under GFDL and are moderated before
 appearing on the site.

 Related: #1504

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

From noreply at wordpress.org  Sat Apr 14 13:44:24 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 13:44:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.03ee2c07fd5e3867991d4544eab68714@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------+---------------------
 Reporter:  keesiemeijer   |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  has-patch      |
---------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.patch" added.

 Add ability for user to edit their own user contibuted notes

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

From noreply at wordpress.org  Sat Apr 14 13:58:04 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 13:58:04 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.ba1be8e26faececb0ec4d64b216e9543@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------+---------------------
 Reporter:  keesiemeijer   |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  has-patch      |
---------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.png" added.

 Screenshot of edit note form

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

From noreply at wordpress.org  Sat Apr 14 13:59:04 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 13:59:04 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.81075dbe41e396af53feac34af98c59f@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

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


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

From noreply at wordpress.org  Sat Apr 14 17:23:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 17:23:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.99966065c29e88ec44cfe0cc046214c5@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by ocean90):

 In [changeset:"7108" 7108]:
 {{{
 #!CommitTicketReference repository="" revision="7108"
 Trac: Update wp-trac.css with some more-specific selectors and overrides
 for Trac 1.2.2 CSS.

 See #3526.
 }}}

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

From noreply at wordpress.org  Sat Apr 14 17:23:48 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 14 Apr 2018 17:23:48 +0000 (UTC)
Subject: [wp-meta] [7108]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.css: Trac: Update
 wp-trac.css with some more-specific selectors and overrides for Trac 1.2.2
 CSS.
Message-ID: <20180414172348.A2C6A1B004BF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr 14 17:34:58 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 14 Apr 2018 17:34:58 +0000 (UTC)
Subject: [wp-meta] [7109]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump scripts
 version.
Message-ID: <20180414173458.9ADB11B004BF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr 14 18:43:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 18:43:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3571: Add background-repeat &
 background-position in the Plugin directory css
In-Reply-To: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
References: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
Message-ID: <072.38868ac70ee6ec1510f0439a46e2882b@wordpress.org>

#3571: Add background-repeat & background-position in the Plugin directory css
-------------------------------------------------+-------------------------
 Reporter:  mostafa.s1990                        |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Plugin
                                                 |  Directory v3.0
Component:  Plugin Directory                     |  Resolution:
 Keywords:  ui-feedback has-screenshots needs-   |
  design                                         |
-------------------------------------------------+-------------------------

Comment (by Otto42):

 Well, it's usually not needed, because we expect people to make their
 icons square.

 This icon isn't square:

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

From noreply at wordpress.org  Sat Apr 14 18:44:09 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 14 Apr 2018 18:44:09 -0000
Subject: [wp-meta] [Making WordPress.org] #3571: Add background-repeat &
 background-position in the Plugin directory css
In-Reply-To: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
References: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
Message-ID: <072.1eaaac36ba76d17304d2f1cca281c07a@wordpress.org>

#3571: Add background-repeat & background-position in the Plugin directory css
-------------------------------------------------+-------------------------
 Reporter:  mostafa.s1990                        |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Plugin
                                                 |  Directory v3.0
Component:  Plugin Directory                     |  Resolution:
 Keywords:  ui-feedback has-screenshots needs-   |
  design                                         |
-------------------------------------------------+-------------------------

Comment (by Otto42):

 Well, it's usually not needed, because we expect people to make their
 icons square.

 This icon isn't square: view-source:https://plugins.svn.wordpress.org/wp-
 statistics/assets/icon.svg

 Note the svg header:

 <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 292.12 298.15">

 292.12 != 298.15

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

From noreply at wordpress.org  Sun Apr 15 00:33:32 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 00:33:32 -0000
Subject: [wp-meta] [Making WordPress.org] #3573: Add Speed Setting
Message-ID: <055.51e5c55316dcfe024eed2af18351a5b6@wordpress.org>

#3573: Add Speed Setting
--------------------------+--------------------
 Reporter:  Travel_girl   |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+--------------------
 It would be great, if we could add a setting for the speed control of the
 video, so the users can decide how fast or slow their want to watch a
 video.

 For example if a Speakers speaks really fast, it can make it easier for
 users to understand the talk, if their could see it in a slower way.

 Also, if a user is used to listen to Videos/Podcast/... in a faster speed,
 it would be help to speed up the videos on wordPress.tv as well, so it
 could be possible to watch more videos in a shorter time. It also could
 help for some users to stay focus on the talk, if it is a bit faster.
 Different Users has different needs :-)

 A good example for this function is youtube, where you have multiple
 options on the speed, to set it slower or faster.

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

From noreply at wordpress.org  Sun Apr 15 00:34:06 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 00:34:06 -0000
Subject: [wp-meta] [Making WordPress.org] #3573: Add Speed Setting
In-Reply-To: <055.51e5c55316dcfe024eed2af18351a5b6@wordpress.org>
References: <055.51e5c55316dcfe024eed2af18351a5b6@wordpress.org>
Message-ID: <070.961b43ed27b1be37e643cf2ec4d0926e@wordpress.org>

#3573: Add Speed Setting
--------------------------+---------------------
 Reporter:  Travel_girl   |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:                |
--------------------------+---------------------
Changes (by Travel_girl):

 * Attachment "Bildschirmfoto 2018-04-15 um 01.30.07.png" added.

 youtube speed Control

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

From noreply at wordpress.org  Sun Apr 15 01:19:15 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 01:19:15 -0000
Subject: [wp-meta] [Making WordPress.org] #3339: Not possible to edit
 comments on developer.wordpress.org
In-Reply-To: <052.daaa6ca4b9a05cd456e43ff5097cae8c@wordpress.org>
References: <052.daaa6ca4b9a05cd456e43ff5097cae8c@wordpress.org>
Message-ID: <067.d74ce502c613c9ae14fe06168a8a13eb@wordpress.org>

#3339: Not possible to edit comments on developer.wordpress.org
---------------------------+------------------------
 Reporter:  mnelson4       |       Owner:  (none)
     Type:  enhancement    |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:  duplicate
 Keywords:                 |
---------------------------+------------------------
Changes (by netweb):

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


Comment:

 I'm marking this a duplicate of the #3572 ticket just created because
 #3572 includes a patch 😃

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

From noreply at wordpress.org  Sun Apr 15 10:05:16 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun, 15 Apr 2018 10:05:16 +0000 (UTC)
Subject: [wp-meta] [7110] sites/trunk/wordpress.org/public_html/style/trac:
 Trac: Make Trac ticket buttons always visible instead of only on hover.
Message-ID: <20180415100516.10C041B005C4@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sun Apr 15 10:05:16 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 10:05:16 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.257c1bd57dd393e6fced362b0b3c8e5b@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by ocean90):

 In [changeset:"7110" 7110]:
 {{{
 #!CommitTicketReference repository="" revision="7110"
 Trac: Make Trac ticket buttons always visible instead of only on hover.

 See #3526.
 }}}

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

From noreply at wordpress.org  Sun Apr 15 10:36:27 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 10:36:27 -0000
Subject: [wp-meta] [Making WordPress.org] #3574: Plugin Directory: Required
 PHP string
Message-ID: <051.5f950e9e26da2a1796a4181c2072c33e@wordpress.org>

#3574: Plugin Directory: Required PHP string
------------------------------+--------------------
 Reporter:  Clorith           |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 Currently the required PHP string is set as `Requires PHP Version:`, but
 this confuses users.

 This leads to some user confusion, as they may know their version and it
 doesn't match. Adding `Minimum` as a prefix might be an idea here.

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

From noreply at wordpress.org  Sun Apr 15 10:56:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 10:56:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3574: Plugin Directory:
 Required PHP string
In-Reply-To: <051.5f950e9e26da2a1796a4181c2072c33e@wordpress.org>
References: <051.5f950e9e26da2a1796a4181c2072c33e@wordpress.org>
Message-ID: <066.c9ac61395941a5f92efc2a53ce2f3fb0@wordpress.org>

#3574: Plugin Directory: Required PHP string
------------------------------+---------------------
 Reporter:  Clorith           |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by swissspidy):

 For WordPress version requirements we have `Requires at least:`. Maybe we
 can make this string similar?

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

From noreply at wordpress.org  Sun Apr 15 12:30:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 12:30:34 -0000
Subject: [wp-meta] [Making WordPress.org] #3573: Add Speed Setting
In-Reply-To: <055.51e5c55316dcfe024eed2af18351a5b6@wordpress.org>
References: <055.51e5c55316dcfe024eed2af18351a5b6@wordpress.org>
Message-ID: <070.3125240e812df5d2c7f807957f3e2583@wordpress.org>

#3573: Add Speed Setting
--------------------------+---------------------
 Reporter:  Travel_girl   |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:                |
--------------------------+---------------------

Comment (by SergeyBiryukov):

 I'd love to see this implemented as well. I'm used to watching videos at
 1.5x speed, which is possible for talks uploaded to YouTube, but not for
 any other talks on WordPress.tv. Sometimes I download the file to play it
 locally with the speed I want, but that's not really a convenient way :)

 I thought the goal was to [https://make.wordpress.org/tv/2016/05/26
 /youtube-proposal/ have all talks on YouTube eventually], thought I'm not
 sure what's the progress on that.

 That said, I wonder if Meta Trac is the right venue for suggesting
 enhancements to VideoPress player. Previously, I was told to use
 WordPress.com support forums for that. I reported an issue with
 [https://en.forums.wordpress.com/topic/subtitles-hidden-behind-control-
 bar-in-videopress subtitles hidden behind control bar] there.

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

From noreply at wordpress.org  Sun Apr 15 12:34:45 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun, 15 Apr 2018 12:34:45 +0000 (UTC)
Subject: [wp-meta] [7111]
 sites/trunk/common/includes/slack/trac/comment-handler.php: Slack/Trac:
 Improve detection of Trac email footer.
Message-ID: <20180415123445.29AA81B005C4@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sun Apr 15 12:34:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 12:34:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.4b0681ab2418beb12e5706504d854792@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by ocean90):

 In [changeset:"7111" 7111]:
 {{{
 #!CommitTicketReference repository="" revision="7111"
 Slack/Trac: Improve detection of Trac email footer.

 Some Trac installs like BuddyPress have an extra space after the separator
 which breaks parsing the mail.

 See #3526.
 }}}

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

From noreply at wordpress.org  Sun Apr 15 14:47:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 14:47:01 -0000
Subject: [wp-meta] [Making WordPress.org] Batch modify: #3538, #3539, #3540
In-Reply-To: <056.069c0d14d84df3e6be36d6c1703befdf@wordpress.org>
References: <056.069c0d14d84df3e6be36d6c1703befdf@wordpress.org>
Message-ID: <071.033dfe10464eb9e8626b045ca944a2bd@wordpress.org>

Batch modification to #3538, #3539, #3540 by netweb:


Comment:
See https://wordpress.slack.com/archives/C9GG77GRJ/p1522706611000049 in #council-ops in Slack

-- 
Tickets URL: <https://meta.trac.wordpress.org/query?id=3538%2C3539%2C3540>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

From noreply at wordpress.org  Sun Apr 15 16:43:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 16:43:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.b2214a44d21a6b68e4e2556dfe14bd70@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.2.patch" added.

 Improvements

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

From noreply at wordpress.org  Sun Apr 15 16:45:27 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 15 Apr 2018 16:45:27 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.9bb7e66f334ea7603edb4e25f363f247@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------

Comment (by keesiemeijer):

 @netweb Thanks.

 Patch [attachment:3572.2.patch] adds the following improvements

 * Adds a nonce field to the edit comment form.
 * Verifies the nonce when updating a comment.
 * Adds a notice to the edited note.
 * Improves scrolling to notes for logged in users.

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

From noreply at wordpress.org  Mon Apr 16 01:16:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 01:16:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.86bf9116e598a2f929a345f1ad4835eb@wordpress.org>

#3572: Allow users to edit their own notes
-----------------------------------------------------+---------------------
 Reporter:  keesiemeijer                             |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:
Component:  Developer Hub                            |  Resolution:
 Keywords:  has-patch has-screenshots needs-refresh  |
-----------------------------------------------------+---------------------
Changes (by netweb):

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


Comment:

 FYI, there's some unrelated changes in [attachment:3572.2.patch], there
 should be no changes to the `package.json` file, and also don't include
 the `package-lock.json` file in the patch.

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

From noreply at wordpress.org  Mon Apr 16 02:05:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 02:05:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3571: Add background-repeat &
 background-position in the Plugin directory css
In-Reply-To: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
References: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
Message-ID: <072.dd10083927038601469a76e75e120e61@wordpress.org>

#3571: Add background-repeat & background-position in the Plugin directory css
-------------------------------------------------+-------------------------
 Reporter:  mostafa.s1990                        |       Owner:  (none)
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:
Component:  Plugin Directory                     |  Resolution:  invalid
 Keywords:  ui-feedback has-screenshots needs-   |
  design                                         |
-------------------------------------------------+-------------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Plugin Directory v3.0 =>


Comment:

 The background positioning is deliberately not included, as icons are
 supposed to tile.

 Most plugin icons provided by authors are the correct size, and as a
 result are square and do not tile like that.

 Most geopattern icons are tiled, although some are square, compare:
 https://wordpress.org/plugins/geopattern-icon/baztaz.svg (Square, doesn't
 need to tile, but could)
 https://wordpress.org/plugins/geopattern-icon/foobar.svg  (Rectangular,
 tiles vertically)

 I'm going to close this one as `invalid` myself, as we need tiling, and if
 you make the icon the correct size there's no issues.
 (Sidenote: I don't think core does tiling, and instead stretches icons
 instead incorrectly)

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

From noreply at wordpress.org  Mon Apr 16 04:08:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 04:08:01 -0000
Subject: [wp-meta] [Making WordPress.org] #3575: CampSite 2017: Add Logo
 support in theme
Message-ID: <053.62a3026b91ca279823c6d4ff91e1b67b@wordpress.org>

#3575: CampSite 2017: Add Logo support in theme
-------------------------------------+--------------------
 Reporter:  melchoyce                |      Owner:  (none)
     Type:  enhancement              |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+--------------------
 The CampSite theme doesn't allow you to upload a logo, just a header
 image. We should also support logos.

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

From noreply at wordpress.org  Mon Apr 16 04:19:07 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 16 Apr 2018 04:19:07 +0000 (UTC)
Subject: [wp-meta] [7112]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes:
 Themes: Add a JS minification grunt task for the themes directory.
Message-ID: <20180416041907.C6EF71B00719@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 16 04:54:33 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 16 Apr 2018 04:54:33 +0000 (UTC)
Subject: [wp-meta] [7113]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-themes/js:
 Themes Directory: Upgrade the Google tracking style to the new analytics
 tracker.
Message-ID: <20180416045433.789781B00719@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 16 04:54:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 04:54:34 -0000
Subject: [wp-meta] [Making WordPress.org] #1017: Google Analytics code
 uses old (deprecated format)
In-Reply-To: <057.5494ac7ff4ce9b3e26dc5eb693e7d813@wordpress.org>
References: <057.5494ac7ff4ce9b3e26dc5eb693e7d813@wordpress.org>
Message-ID: <072.5d69042008db311c8046a8c4669387b7@wordpress.org>

#1017: Google Analytics code uses old (deprecated format)
---------------------------+------------------------
 Reporter:  slobodanmanic  |       Owner:  dd32
     Type:  defect         |      Status:  reviewing
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:
 Keywords:                 |
---------------------------+------------------------

Comment (by dd32):

 In [changeset:"7113" 7113]:
 {{{
 #!CommitTicketReference repository="" revision="7113"
 Themes Directory: Upgrade the Google tracking style to the new analytics
 tracker.

 See #1017.
 }}}

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

From noreply at wordpress.org  Mon Apr 16 05:33:23 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 05:33:23 -0000
Subject: [wp-meta] [Making WordPress.org] #1017: Google Analytics code
 uses old (deprecated format)
In-Reply-To: <057.5494ac7ff4ce9b3e26dc5eb693e7d813@wordpress.org>
References: <057.5494ac7ff4ce9b3e26dc5eb693e7d813@wordpress.org>
Message-ID: <072.346f79bb7261ecf2c3025ed814b82a95@wordpress.org>

#1017: Google Analytics code uses old (deprecated format)
---------------------------+------------------------
 Reporter:  slobodanmanic  |       Owner:  dd32
     Type:  defect         |      Status:  reviewing
 Priority:  normal         |   Milestone:
Component:  General        |  Resolution:
 Keywords:                 |
---------------------------+------------------------

Comment (by dd32):

 Updated:
 * WordPress.org
 * WordPress.org/themes
 * Codex.WordPress.org
 * BuddyPress.org
 * bbPress.org
 * mu.WordPress.org

 Others that were already using the newer tracker:
  * core.trac.wordpress.org

 Other properties not yet updated:
 * pingomatic.com
 * browsehappy.com (Still using urchin.js)

 @coffee2code Do you have access to pingo and BH?

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

From noreply at wordpress.org  Mon Apr 16 12:08:11 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 12:08:11 -0000
Subject: [wp-meta] [Making WordPress.org] #3576: Content Limitations -
 custom CSS and aria-label
Message-ID: <049.cdb5bb51eb1b10098762ab9d2ecbe7ff@wordpress.org>

#3576: Content Limitations - custom CSS and aria-label
-------------------------------------------+--------------------
 Reporter:  GaryJ                          |      Owner:  (none)
     Type:  enhancement                    |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:
-------------------------------------------+--------------------
 See https://en-gb.wordpress.org/meetups/

 There are a couple of things I'd like to improve here:

  - consolidate the repeated `style` attributes for each `h3`, `ul`, and
 `li` into class selectors. There doesn't appear to be a way to define
 custom CSS (like WordCamp sites can), and `<style>` tags get stripped.
  - use `aria-label` attributes, so that an extracted list of links doesn't
 just repeat the same link texts but with different URLs. `aria-label`
 attributes are stripped, and I don't want to update the (visual) link
 text.

 Can solutions be provided for these?

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

From noreply at wordpress.org  Mon Apr 16 12:58:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 12:58:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3301: CampTix: Add field to
 mark contributor day attendees
In-Reply-To: <052.7883565f131cdc1de62b1ca473761db8@wordpress.org>
References: <052.7883565f131cdc1de62b1ca473761db8@wordpress.org>
Message-ID: <067.c841521e85549e92bc7c6b110c912bad@wordpress.org>

#3301: CampTix: Add field to mark contributor day attendees
----------------------------------------+---------------------
 Reporter:  camikaos                    |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  good-first-bug needs-patch  |
----------------------------------------+---------------------

Comment (by GaryJ):

 For WordCamp London, we sold free Contributor Day tickets (138, with at
 least 105 attendees on the day), and then marked people as attended. This
 approach has its own drawbacks such as more form-filling for attendees
 (though we can ask CD-specific questions), more work for ensuring
 conference tickets are marked off when they already picked up the badge at
 the CD the day before etc.

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

From noreply at wordpress.org  Mon Apr 16 14:57:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 14:57:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.32d51ef6e99fb89c885f2736b9264f2f@wordpress.org>

#3572: Allow users to edit their own notes
-----------------------------------------------------+---------------------
 Reporter:  keesiemeijer                             |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:
Component:  Developer Hub                            |  Resolution:
 Keywords:  has-patch has-screenshots needs-refresh  |
-----------------------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.3.patch" added.


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

From noreply at wordpress.org  Mon Apr 16 15:00:08 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 15:00:08 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.d2446ac629cd6fb58b9265cdc08ae59a@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

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


Comment:

 In patch [attachment:3572.3.patch] the `package.json` file is restored and
 `package-lock.json` is removed.

 Thanks @netweb, I wasn't sure if I should include the `package-lock.json`
 file or not.

 It also adds the following improvements.
 * Display the 404 template if the global post data or comment is not found
 in the edit template (`comments-edit.php`).
 * Include links to the note and note author in the description of the edit
 template.
 * Add breadcrumb trail items to the reference and post type archive.

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

From noreply at wordpress.org  Mon Apr 16 16:07:08 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 16 Apr 2018 16:07:08 +0000 (UTC)
Subject: [wp-meta] [7114]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-showcase/functions.php:
 Showcase: Force images to use https URLs (some old entries have http ones),
 adjust screenshot image builder to not duplicate code.
Message-ID: <20180416160708.CFA851B005DA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 16 16:23:15 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 16:23:15 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.489adef5ec1cf03b9e3f2eca0b5c649b@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.4.png" added.

 Updated screenshot of the edit note template

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

From noreply at wordpress.org  Mon Apr 16 16:24:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 16:24:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.d6d5c5cd67fd822a07d735abcf21f81c@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.5.png" added.

 Screenshot of edited note notice

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

From noreply at wordpress.org  Mon Apr 16 16:48:43 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 16 Apr 2018 16:48:43 +0000 (UTC)
Subject: [wp-meta] [7115]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-showcase/page-home.php:
 Showcase: Only show published posts in the featured slider box
Message-ID: <20180416164843.0A7EE1B005DA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 16 17:00:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 17:00:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3575: CampSite 2017: Add Logo
 support in theme
In-Reply-To: <053.62a3026b91ca279823c6d4ff91e1b67b@wordpress.org>
References: <053.62a3026b91ca279823c6d4ff91e1b67b@wordpress.org>
Message-ID: <068.d7137f1ae8a2e64675f330cae16f580c@wordpress.org>

#3575: CampSite 2017: Add Logo support in theme
-------------------------------------+---------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------
Changes (by ryelle):

 * Attachment "3575.diff" added.


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

From noreply at wordpress.org  Mon Apr 16 17:06:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 17:06:01 -0000
Subject: [wp-meta] [Making WordPress.org] #3575: CampSite 2017: Add Logo
 support in theme
In-Reply-To: <053.62a3026b91ca279823c6d4ff91e1b67b@wordpress.org>
References: <053.62a3026b91ca279823c6d4ff91e1b67b@wordpress.org>
Message-ID: <068.d7b9cf123d5b3551cee63e908c6970aa@wordpress.org>

#3575: CampSite 2017: Add Logo support in theme
-------------------------------------+---------------------
 Reporter:  melchoyce                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------

Comment (by ryelle):

 I've added [attachment:3575.diff], which adds the custom logo support from
 _s to the CampSite theme. I don't think we need to add any CSS. This
 should not affect any existing WC sites using CampSite, since these sites
 won't have set a logo, `the_custom_logo` won't display anything.

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

From noreply at wordpress.org  Mon Apr 16 19:00:52 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 16 Apr 2018 19:00:52 +0000 (UTC)
Subject: [wp-meta] [7116]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-showcase/functions.php:
 Showcase: use query arg functions to add proper width variables for mshots
Message-ID: <20180416190052.A2D181B005DA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 16 21:32:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 21:32:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3577: Add Dictonary for Captioner
 on WordPress Events
Message-ID: <055.93cd7796cf38021fcaf61bd2f25b273a@wordpress.org>

#3577: Add Dictonary for Captioner on WordPress Events
-------------------------+--------------------
 Reporter:  Travel_girl  |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Handbooks    |   Keywords:
-------------------------+--------------------
 At some WordPress Events there are transcribers who type what the speaker
 is saying on the stage. This allows people to also read what the speaker
 is saying. This makes the whole conference more accessible, especially for
 the hearing impaired and non native speakers.

 Currently speakers are asked to send their slides in advance, so that the
 captioners can prepare und understand the technical and WordPress terms
 which will be used in the talk.

 I chatted with the captioners to find out what I as a speaker could do to
 help them. They showed me, that they had created their own WordPress
 dictionary from the slides they had received from the speakers. They are
 also reusing this dictionary for future WordPress conferences and
 expanding on it with new words, that they get from further slides.

 The problem with this workflow is, that

 1. some speakers don't send the slides beforehand or don't have every
 technical word in the slides.
 2. Questions and last minute changes at the slides could include
 technical/WordPress specific words, which are not in the captioner´s
 dictionary.
 3. Sometimes they do not know how some technical written terms are
 pronounced (like i18n)

 Some examples for WordPress related words

 - Jetpack and other common plugins
 - i18n, A11y ... - the captioners don't know how this is spoken out
 - Aria, ....

 So I thought that we as the WordPress Community could help the
 transcriptioners by providing them an dictionary with WordPress related
 words, which their could use and import into their tool.

 I asked them if this would be helpful and they loved the idea. The good
 side would be that we could give this dictionary to the captioners at
 every WordPress conference which they can import into their tool.

 All they need is the terms and how the term is spoken. An excel sheet
 would be enough.

 To create this table I would suggest to make it like a Wiki, which is Open
 Source and could be extended from the community. But of course this should
 be discussed, what the best way would be, if we decide to realizing it.

 A starting point could be this Dictionary:

 https://make.wordpress.org/marketing/2018/02/28/wordpress-jargon-glossary/

 Maybe we could start with a small table and than ask for feedback from the
 captioners to check, if this is a format their could use (the captioners
 from WordCamp London said, they would like to give us feedback). In this
 way we can make sure, that the format is correct, before we continue.

 The captioners doing an amazing job and having an big impact to make the
 WordCamps more accessible. I would love, if we could make their job more
 easier.

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

From noreply at wordpress.org  Mon Apr 16 22:17:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 22:17:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3577: Add Dictonary for
 Captioner on WordPress Events
In-Reply-To: <055.93cd7796cf38021fcaf61bd2f25b273a@wordpress.org>
References: <055.93cd7796cf38021fcaf61bd2f25b273a@wordpress.org>
Message-ID: <070.44dc8bda8e61605cfcec28ebd08d19d7@wordpress.org>

#3577: Add Dictonary for Captioner on WordPress Events
-------------------------+---------------------
 Reporter:  Travel_girl  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by keesiemeijer):

 I've created a list with all unique words used in WordPress 4.9 functions
 and hooks. Maybe it could help you finding words you want to include in
 the dictionary. Most words are not that useful though.

 https://gist.github.com/keesiemeijer/523ebe22ff09fe8c2edbf9735dddc631

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

From noreply at wordpress.org  Mon Apr 16 23:06:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 16 Apr 2018 23:06:36 +0000 (UTC)
Subject: [wp-meta] [7117]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/functions.php:
 WP15: Only enqueue fonts for locales that they support.
Message-ID: <20180416230636.E29661B005DA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 16 23:06:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 23:06:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3569: WP15 Theme: Allow
 translators to disable Google Fonts for their language
In-Reply-To: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
References: <051.483a5a4cb926e7b55dfd9b5e591c9ec9@wordpress.org>
Message-ID: <066.089c7528c621791b147a3eaa3fca0585@wordpress.org>

#3569: WP15 Theme: Allow translators to disable Google Fonts for their language
-----------------------+----------------------
 Reporter:  dimadin    |       Owner:  iandunn
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:  fixed
 Keywords:  has-patch  |
-----------------------+----------------------
Changes (by iandunn):

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


Comment:

 In [changeset:"7117" 7117]:
 {{{
 #!CommitTicketReference repository="" revision="7117"
 WP15: Only enqueue fonts for locales that they support.

 Props dimadin.
 Fixes #3569.
 }}}

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

From noreply at wordpress.org  Mon Apr 16 23:49:15 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 23:49:15 -0000
Subject: [wp-meta] [Making WordPress.org] #3578: The same sentence has been
 written twice, please see
Message-ID: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>

#3578: The same sentence has been written twice, please see
-------------------------+----------------------------------------
 Reporter:  pratikthink  |      Owner:  (none)
     Type:  task         |     Status:  new
 Priority:  high         |  Milestone:  Plugin Directory v3.0
Component:  Handbooks    |   Keywords:  needs-docs has-screenshots
-------------------------+----------------------------------------
 Mistakenly, the same sentence has been written twice in handbook for
 **[https://make.wordpress.org/core/handbook/best-practices/writing-
 patches/ Writing Patches]**
 \\
 have a look on given list for **Picking a ticket**
 \\
 * Smaller patches get reviewed faster
 * Work on multiple bugs in parallel
 * ~~Smaller patches get reviewed faster~~

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

From noreply at wordpress.org  Mon Apr 16 23:49:46 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 16 Apr 2018 23:49:46 -0000
Subject: [wp-meta] [Making WordPress.org] #3578: The same sentence has
 been written twice, please see
In-Reply-To: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>
References: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>
Message-ID: <070.08c6c76b345345189261f816fad7a24f@wordpress.org>

#3578: The same sentence has been written twice, please see
----------------------------------------+----------------------------------
 Reporter:  pratikthink                 |       Owner:  (none)
     Type:  task                        |      Status:  new
 Priority:  high                        |   Milestone:  Plugin Directory
                                        |  v3.0
Component:  Handbooks                   |  Resolution:
 Keywords:  needs-docs has-screenshots  |
----------------------------------------+----------------------------------
Changes (by pratikthink):

 * Attachment "Writing Patches – Make WordPress Core.jpg" added.


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

From noreply at wordpress.org  Tue Apr 17 00:20:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 00:20:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3578: The same sentence has
 been written twice, please see
In-Reply-To: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>
References: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>
Message-ID: <070.b26e3d2d1e09b3ff97a09d7b2442392b@wordpress.org>

#3578: The same sentence has been written twice, please see
----------------------------------------+---------------------
 Reporter:  pratikthink                 |       Owner:  (none)
     Type:  task                        |      Status:  new
 Priority:  high                        |   Milestone:
Component:  Handbooks                   |  Resolution:
 Keywords:  needs-docs has-screenshots  |
----------------------------------------+---------------------
Changes (by pratikthink):

 * milestone:  Plugin Directory v3.0 =>


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

From noreply at wordpress.org  Tue Apr 17 00:54:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 00:54:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3578: The same sentence has
 been written twice, please see
In-Reply-To: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>
References: <055.dce7e1ea4e481092be0e8837e7a6e63e@wordpress.org>
Message-ID: <070.d0893537688b28daebea2163ed22a8f0@wordpress.org>

#3578: The same sentence has been written twice, please see
-----------------------------+---------------------
 Reporter:  pratikthink      |       Owner:  (none)
     Type:  task             |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Handbooks        |  Resolution:  fixed
 Keywords:  has-screenshots  |
-----------------------------+---------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-docs has-screenshots => has-screenshots
 * priority:  high => normal
 * status:  new => closed
 * resolution:   => fixed


Comment:

 Hi @pratikthink, welcome to WordPress Meta Trac!

 Fixed. Thanks! :)

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

From noreply at wordpress.org  Tue Apr 17 02:36:55 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 02:36:55 -0000
Subject: [wp-meta] [Making WordPress.org] #3576: Content Limitations -
 custom CSS and aria-label
In-Reply-To: <049.cdb5bb51eb1b10098762ab9d2ecbe7ff@wordpress.org>
References: <049.cdb5bb51eb1b10098762ab9d2ecbe7ff@wordpress.org>
Message-ID: <064.0801eda915cdc714fdd708e010f8ba6e@wordpress.org>

#3576: Content Limitations - custom CSS and aria-label
-------------------------------------------+---------------------
 Reporter:  GaryJ                          |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:
Component:  International Sites (Rosetta)  |  Resolution:
 Keywords:                                 |
-------------------------------------------+---------------------

Comment (by dd32):

 While we could enable custom CSS support, I think this kind of page would
 be better off implemented as a page template available to all locales as
 it's a common thing wanted by country-specific locales

 Related: #1292

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

From noreply at wordpress.org  Tue Apr 17 07:27:24 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 07:27:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.680c01738ce2960b63e9d75864e82f37@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------

Comment (by netweb):

 Thanks @keesiemeijer, I'll leave the rest of the code review to
 @coffee2code and @drew who are more familiar with teh DevHub codebase

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

From noreply at wordpress.org  Tue Apr 17 07:38:47 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 17 Apr 2018 07:38:47 +0000 (UTC)
Subject: [wp-meta] [7118]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/gutenberg/functions.php:
 Gutenberg Theme: Ensure previous/next page links are ordered by menu_order,
 rather than post_date.
Message-ID: <20180417073847.813011B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 17 11:23:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 11:23:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3577: Add Dictonary for
 Captioner on WordPress Events
In-Reply-To: <055.93cd7796cf38021fcaf61bd2f25b273a@wordpress.org>
References: <055.93cd7796cf38021fcaf61bd2f25b273a@wordpress.org>
Message-ID: <070.8ce6454ce832b27791fd126015827558@wordpress.org>

#3577: Add Dictonary for Captioner on WordPress Events
-------------------------+---------------------
 Reporter:  Travel_girl  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by casiepa):

 For the polyglots we have our dictionnary:
 https://make.wordpress.org/polyglots/handbook/glossary/

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

From noreply at wordpress.org  Tue Apr 17 12:52:46 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 12:52:46 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.b5288e1b52f55b742afd3fd8b0f7a330@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by Otto42):

 Replying to [comment:40 dd32]:
 > Looks like I broke the TicketGraph plugin with r7088, Trac now has
 jQuery 1.9 which dropped the `$.browser` property.

 Adding in jQuery-migrate should fix that issue in the short term.

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

From noreply at wordpress.org  Tue Apr 17 13:56:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 13:56:57 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.19a74fd09e776a442855e95569d4be3a@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.6.patch" added.

 Add a new rule to the feedback form

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

From noreply at wordpress.org  Tue Apr 17 14:12:46 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 14:12:46 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.1b0aa1eaa9231adb9f4d191f3e1b108c@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------

Comment (by keesiemeijer):

 Patch [attachment:3572.6.patch] adds a new rule to the note feedback form.

 Many users are using the note feedback form to ask (support) questions and
 are not really adding to the documentation.

 That's why I added this new rule.
 * Feedback is part of the documentation. Use this form to report errors or
 to add additional information to this note.

 When editing a note a link to to the note you're replying to is added to
 the rule.
 * Feedback is part of the documentation. Use this form to report errors or
 to add additional information to [# note 22] by admin.

 A screenshot is following.

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

From noreply at wordpress.org  Tue Apr 17 14:27:32 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 14:27:32 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.698b2644fc3ff64bb76190c1d72249ba@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.7.png" added.

 Feedback form with new rule

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

From noreply at wordpress.org  Tue Apr 17 16:39:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 16:39:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3554: WordCamp Central
 improve single day date output
In-Reply-To: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
References: <054.74aa2dbd1ba718ae8678d1a870d1c11e@wordpress.org>
Message-ID: <069.8c87342b96d54239a150eb00d1888420@wordpress.org>

#3554: WordCamp Central improve single day date output
-------------------------------------+---------------------------
 Reporter:  soulseekah               |       Owner:  coreymckrill
     Type:  defect                   |      Status:  reviewing
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------------
Changes (by coreymckrill):

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


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

From noreply at wordpress.org  Tue Apr 17 21:35:40 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 17 Apr 2018 21:35:40 -0000
Subject: [wp-meta] [Making WordPress.org] #3579: Thread "Edit" link not
 keyboard accessible
Message-ID: <051.716de798aa91e0266c31d3d85a4f11eb@wordpress.org>

#3579: Thread "Edit" link not keyboard accessible
----------------------------+--------------------
 Reporter:  anevins         |      Owner:  (none)
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 The "Edit" link on threads is only visible on hover and won't be
 accessible to keyboard-only users.

 I think this is more troublesome to resolve than you might think because
 of the hyphen characters used as styling outside of the links (at least
 what I see as a moderator).

 Still it would be useful for these links to be visible on focus as well.

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

From noreply at wordpress.org  Tue Apr 17 22:20:19 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 17 Apr 2018 22:20:19 +0000 (UTC)
Subject: [wp-meta] [7119]
 sites/trunk/wordpressfoundation.org/public_html/content/plugins/wpf-stripe/wpf-stripe.php:
 WPF Stripe: Move `custom_styles` closer to `render_donate_shortcode`.
Message-ID: <20180417222019.D78121B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 17 22:20:23 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 17 Apr 2018 22:20:23 +0000 (UTC)
Subject: [wp-meta] [7120]
 sites/trunk/wordpressfoundation.org/public_html/content/plugins/wpf-stripe/wpf-stripe.php:
 WPF Stripe: Remove unnecessary `finally` block for readability.
Message-ID: <20180417222023.15B0B1B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 17 22:20:26 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 17 Apr 2018 22:20:26 +0000 (UTC)
Subject: [wp-meta] [7121]
 sites/trunk/wordpressfoundation.org/public_html/content/plugins/wpf-stripe:
 WPF Stripe: Add post type for email templates.
Message-ID: <20180417222026.36D3D1B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 17 22:20:29 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 17 Apr 2018 22:20:29 +0000 (UTC)
Subject: [wp-meta] [7122]
 sites/trunk/wordpressfoundation.org/public_html/content/plugins/wpf-stripe/wpf-stripe.php:
 WPF Stripe: Add WIP webhook handler to send emails for subscriptions.
Message-ID: <20180417222029.0C3F21B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Tue Apr 17 22:45:37 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 17 Apr 2018 22:45:37 +0000 (UTC)
Subject: [wp-meta] [7123]
 sites/trunk/wordpressfoundation.org/public_html/content/plugins/wpf-stripe:
 WPF Stripe: Set `Reply-To` header so donors can reply to emails.
Message-ID: <20180417224537.409A21B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 00:06:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 00:06:10 -0000
Subject: [wp-meta] [Making WordPress.org] #3580: Themes Trac Login Link not
 sending people to login.wordpress.org
Message-ID: <051.93333b9acaf3d7b3096b9ead26bc0d74@wordpress.org>

#3580: Themes Trac Login Link not sending people to login.wordpress.org
---------------------+--------------------
 Reporter:  Ipstenu  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  Trac     |   Keywords:
---------------------+--------------------
 Click on login, goes to https://themes.trac.wordpress.org/login which
 throws an error. Someone needs to fix the redirect please and thank you.

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

From noreply at wordpress.org  Wed Apr 18 01:00:34 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 01:00:34 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.cd73e7c3dabb924ef17a3713846b0cc0@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 Replying to [comment:49 Otto42]:
 > Adding in jQuery-migrate should fix that issue in the short term.

 Upgrading the plugin will also fix it, which should happen today. It seems
 like the newer version of the Trac plugin included all our modifications.

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

From noreply at wordpress.org  Wed Apr 18 01:15:47 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 01:15:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3580: Themes Trac Login Link
 not sending people to login.wordpress.org
In-Reply-To: <051.93333b9acaf3d7b3096b9ead26bc0d74@wordpress.org>
References: <051.93333b9acaf3d7b3096b9ead26bc0d74@wordpress.org>
Message-ID: <066.81889e9549f20f61116c14322d565f48@wordpress.org>

#3580: Themes Trac Login Link not sending people to login.wordpress.org
---------------------+---------------------
 Reporter:  Ipstenu  |       Owner:  (none)
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  Trac     |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------
Changes (by dd32):

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


Comment:

 This has been fixed per systems.

 See Also #3526

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

From noreply at wordpress.org  Wed Apr 18 07:57:00 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 07:57:00 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory homepage
 says that it's also available in nothing
Message-ID: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+-------------------------
 Reporter:  danieltj          |      Owner:  (none)
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  needs-patch
------------------------------+-------------------------
 On the plugin directory homepage, the green translation banner is missing
 the language locale so it says it's also available in (nothing). I've
 attached a screenshot of what I mean.

 Page: https://wordpress.org/plugins/

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

From noreply at wordpress.org  Wed Apr 18 07:57:09 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 07:57:09 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory
 homepage says that it's also available in nothing
In-Reply-To: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
References: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
Message-ID: <067.7ef78faa309d2605648048e7a631333d@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+---------------------
 Reporter:  danieltj          |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------
Changes (by danieltj):

 * Attachment "plugin-directory-bug.png" added.


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

From noreply at wordpress.org  Wed Apr 18 07:58:11 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 07:58:11 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory
 homepage says that it's also available in nothing
In-Reply-To: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
References: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
Message-ID: <067.93b77cce5d356e73bf6561991163c225@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+---------------------
 Reporter:  danieltj          |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by Otto42):

 What language are you sending it in your Accept header? What languages
 does your browser know about?

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

From noreply at wordpress.org  Wed Apr 18 08:03:48 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 08:03:48 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory
 homepage says that it's also available in nothing
In-Reply-To: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
References: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
Message-ID: <067.0960102b959e1751b9c570138c7a20f6@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+---------------------
 Reporter:  danieltj          |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by danieltj):

 I'm using Chrome 65. In the request headers, it sent `accept-language: en-
 GB,en-US;q=0.9,en;q=0.8,la;q=0.7`.

 Hope that helps.

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

From noreply at wordpress.org  Wed Apr 18 08:27:14 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 08:27:14 +0000 (UTC)
Subject: [wp-meta] [7124]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/api/routes/class-locale-banner.php:
 Plugin Directory: Locale Banner: Validate that the Locales can be found by
 `wp_locale` before attempting to use them.
Message-ID: <20180418082714.1AFF71B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 08:27:14 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 08:27:14 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory
 homepage says that it's also available in nothing
In-Reply-To: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
References: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
Message-ID: <067.d051a6e16bc18a5ca357927c00c2fd97@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+---------------------
 Reporter:  danieltj          |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by dd32):

 In [changeset:"7124" 7124]:
 {{{
 #!CommitTicketReference repository="" revision="7124"
 Plugin Directory: Locale Banner: Validate that the Locales can be found by
 `wp_locale` before attempting to use them.

 See #3581.
 }}}

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

From noreply at wordpress.org  Wed Apr 18 08:28:14 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 08:28:14 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory
 homepage says that it's also available in nothing
In-Reply-To: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
References: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
Message-ID: <067.34fcbb7c75d62ca1048903ee5dfa5861@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+---------------------
 Reporter:  danieltj          |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------
Changes (by dd32):

 * keywords:  needs-patch =>


Comment:

 This is happening as `la` is a known locale, but GlotPress doesn't
 understand it's a `wp_locale`

 The correct fix is to fix GlotPress's locales.php to include the
 `wp_locale` like most other languages. That will also allow us to set the
 la.wordpress.org's site language to la.

 https://github.com/GlotPress/GlotPress-
 WP/blob/develop/locales/locales.php#L1314-L1321

 The other fix is to validate that all the `GP_Locale`'s can be found via
 that `wp_locale` as per [7124]

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

From noreply at wordpress.org  Wed Apr 18 08:36:53 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 08:36:53 +0000 (UTC)
Subject: [wp-meta] [7125]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/api/routes/class-locale-banner.php:
 Plugin Directory: Locale Header: Don't fall into the "This plugin isn't yet
 translated" branch when no plugin is specified.
Message-ID: <20180418083653.3E14A1B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 08:36:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 08:36:54 -0000
Subject: [wp-meta] [Making WordPress.org] #3581: Plugin directory
 homepage says that it's also available in nothing
In-Reply-To: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
References: <052.24a5d6e46a9ebf655063da9f2b44a609@wordpress.org>
Message-ID: <067.0ba84aba918ad8d84167f311596f4ce9@wordpress.org>

#3581: Plugin directory homepage says that it's also available in nothing
------------------------------+---------------------
 Reporter:  danieltj          |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by dd32):

 In [changeset:"7125" 7125]:
 {{{
 #!CommitTicketReference repository="" revision="7125"
 Plugin Directory: Locale Header: Don't fall into the "This plugin isn't
 yet translated" branch when no plugin is specified.

 See #3581.
 }}}

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

From noreply at wordpress.org  Wed Apr 18 09:34:10 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 09:34:10 -0000
Subject: [wp-meta] [Making WordPress.org] #3582: Remove closed topics from
 the "Topics with no replies" view
Message-ID: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>

#3582: Remove closed topics from the "Topics with no replies" view
----------------------------+--------------------
 Reporter:  flashbash       |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 When a topic is closed manually it still shows up in the "Topics with no
 replies" view. Its impossible for normal contributors to get it out of
 there (or answer to it) and a mod would need to manually change the status
 of the topic to "no support topic".

 The no-replies view should filter out closed topics.

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

From noreply at wordpress.org  Wed Apr 18 10:32:13 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 10:32:13 -0000
Subject: [wp-meta] [Making WordPress.org] #3582: Remove closed topics
 from the "Topics with no replies" view
In-Reply-To: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>
References: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>
Message-ID: <068.aa886738650178100d45d91cc1f4c4b5@wordpress.org>

#3582: Remove closed topics from the "Topics with no replies" view
----------------------------+---------------------
 Reporter:  flashbash       |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by flashbash):

 Example in the german forums: [https://de.wordpress.org/support/view/no-
 replies/page/3/?days=100]

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

From noreply at wordpress.org  Wed Apr 18 10:41:39 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 10:41:39 -0000
Subject: [wp-meta] [Making WordPress.org] #3582: Remove closed topics
 from the "Topics with no replies" view
In-Reply-To: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>
References: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>
Message-ID: <068.3663f4a2917dc3436fc00381d3d70ba9@wordpress.org>

#3582: Remove closed topics from the "Topics with no replies" view
----------------------------+---------------------
 Reporter:  flashbash       |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by flashbash):

 * Attachment "no-replies-view-closed-topic.PNG" added.

 Screenshot of closed topic in the no-replies-view

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

From noreply at wordpress.org  Wed Apr 18 11:36:21 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 11:36:21 -0000
Subject: [wp-meta] [Making WordPress.org] #3582: Remove closed topics
 from the "Topics with no replies" view
In-Reply-To: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>
References: <053.7f34830041fb6f022056a8380abc412f@wordpress.org>
Message-ID: <068.4ad584f43278149b9aae066c82a46901@wordpress.org>

#3582: Remove closed topics from the "Topics with no replies" view
----------------------------+---------------------
 Reporter:  flashbash       |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by SergeyBiryukov):

 Previously: #530, #832, #2942.

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

From noreply at wordpress.org  Wed Apr 18 14:11:33 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 14:11:33 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.4c927107037990f7d6a0cde721b2459f@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.8.patch" added.

 Don't allow empty comments when editing

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

From noreply at wordpress.org  Wed Apr 18 14:21:06 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 14:21:06 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.88b58a0d15d2cbec19d8a0ea3192e149@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------

Comment (by keesiemeijer):

 Patch [attachment:3572.8.patch] displays an error and a way back to the
 comment form if a comment is empty after editing.

 Other improvements:
 * Add extra checks (post_id, post_type) before updating a comment.
 * Use `htmlspecialchars_decode()` for comment content when editing a top
 level comment.

 Just to recap, this patch:

 * Allows users to edit top level comments and child (feedback) comments
 * Adds a new rewrite rule and theme template file for editing comments
 * Adds comment rules (guidelines) to the feedback form
 * Improves scrolling to notes (adjusting for the admin bar)
 * Works with Javascript disabled

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

From noreply at wordpress.org  Wed Apr 18 14:22:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 14:22:57 -0000
Subject: [wp-meta] [Making WordPress.org] #3583: Make slack url translatable
 in the warning for posts held for moderation after 96 hours
Message-ID: <054.9c6d0444488440f302c1d55a3db53887@wordpress.org>

#3583: Make slack url translatable in the warning for posts held for moderation
after 96 hours
----------------------------+-------------------------
 Reporter:  felipeelia      |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  2nd-opinion
----------------------------+-------------------------
 When a post is held for moderation we currently inform users that it will
 be reviewed. After 96 hours that message changes to another version, with
 a link to #forums slack channel as seen
 [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/themes/pub/wporg-forums/functions.php?marks=262#L262 here].

 Although this message is actually never showed in the internacional forum
 (posts are never hold that time long), in more silent local forums it can
 happen. So making the url translatable could point users to local slack
 instances. That way we could reduce chances of users going to the
 international slack when there is a more appropriate place to ask for
 help.

 p.s.: In Brazilian forums we ended up translating that just assigning the
 placeholder to another attribute, as can be seen
 [https://translate.wordpress.org/projects/meta/forums/pt-
 br/default?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=3477395&filters%5Btranslation_id%5D=54751180
 here], but IMHO making the url translatable is the right thing to do here.

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

From noreply at wordpress.org  Wed Apr 18 14:58:06 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 14:58:06 -0000
Subject: [wp-meta] [Making WordPress.org] #3583: Make slack url
 translatable in the warning for posts held for moderation after 96 hours
In-Reply-To: <054.9c6d0444488440f302c1d55a3db53887@wordpress.org>
References: <054.9c6d0444488440f302c1d55a3db53887@wordpress.org>
Message-ID: <069.bcedf59d3417cd4622365d59ec927bc4@wordpress.org>

#3583: Make slack url translatable in the warning for posts held for moderation
after 96 hours
----------------------------+---------------------
 Reporter:  felipeelia      |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  2nd-opinion     |
----------------------------+---------------------

Comment (by tobifjellner):

 For the Swedish forum I'd love to be able to put a lower number than 96.
 With a stray entry in moderation once every 1-2 months, it would be good
 to have the user himself reminding us about posts pending moderation.

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

From noreply at wordpress.org  Wed Apr 18 15:01:24 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 15:01:24 +0000 (UTC)
Subject: [wp-meta] [7126]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support:
 Support Theme: Make inline topic/reply admin links visible on focus in
 addition to hover.
Message-ID: <20180418150124.3938A1B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 15:01:25 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 15:01:25 -0000
Subject: [wp-meta] [Making WordPress.org] #3579: Thread "Edit" link not
 keyboard accessible
In-Reply-To: <051.716de798aa91e0266c31d3d85a4f11eb@wordpress.org>
References: <051.716de798aa91e0266c31d3d85a4f11eb@wordpress.org>
Message-ID: <066.e8071034faddd59de3547c871d110c20@wordpress.org>

#3579: Thread "Edit" link not keyboard accessible
----------------------------+-----------------------------
 Reporter:  anevins         |       Owner:  SergeyBiryukov
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"7126" 7126]:
 {{{
 #!CommitTicketReference repository="" revision="7126"
 Support Theme: Make inline topic/reply admin links visible on focus in
 addition to hover.

 Props anevins.
 Fixes #3579.
 }}}

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

From noreply at wordpress.org  Wed Apr 18 15:01:45 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 15:01:45 +0000 (UTC)
Subject: [wp-meta] [7127]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Extend the date range to find more WP15 events.
Message-ID: <20180418150145.D6BD11B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 15:16:42 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 15:16:42 +0000 (UTC)
Subject: [wp-meta] [7128]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 Support Theme: Bump CSS version for cache bust.
Message-ID: <20180418151642.3795F1B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 16:31:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 16:31:36 +0000 (UTC)
Subject: [wp-meta] [7129]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 Support Theme: Make Slack URL and moderation timeframe in pending posts
 notice translatable.
Message-ID: <20180418163136.D74B21B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 16:31:37 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 16:31:37 -0000
Subject: [wp-meta] [Making WordPress.org] #3583: Make slack url
 translatable in the warning for posts held for moderation after 96 hours
In-Reply-To: <054.9c6d0444488440f302c1d55a3db53887@wordpress.org>
References: <054.9c6d0444488440f302c1d55a3db53887@wordpress.org>
Message-ID: <069.7bf14c97141972916c86a490ef14662e@wordpress.org>

#3583: Make slack url translatable in the warning for posts held for moderation
after 96 hours
----------------------------+-----------------------------
 Reporter:  felipeelia      |       Owner:  SergeyBiryukov
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  2nd-opinion     |
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"7129" 7129]:
 {{{
 #!CommitTicketReference repository="" revision="7129"
 Support Theme: Make Slack URL and moderation timeframe in pending posts
 notice translatable.

 Props felipeelia, tobifjellner.
 Fixes #3583.
 }}}

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

From noreply at wordpress.org  Wed Apr 18 17:38:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 18 Apr 2018 17:38:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3571: Add background-repeat &
 background-position in the Plugin directory css
In-Reply-To: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
References: <057.443e99f4a6d62c2d6b1e47605f31e8dc@wordpress.org>
Message-ID: <072.addaef9ef3b23636bf7c6c925e8b9a0a@wordpress.org>

#3571: Add background-repeat & background-position in the Plugin directory css
-------------------------------------------------+-------------------------
 Reporter:  mostafa.s1990                        |       Owner:  (none)
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:
Component:  Plugin Directory                     |  Resolution:  invalid
 Keywords:  ui-feedback has-screenshots needs-   |
  design                                         |
-------------------------------------------------+-------------------------

Comment (by mostafa.s1990):

 Thank you @dd32, @Otto42,

 The issue solved.

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

From noreply at wordpress.org  Wed Apr 18 21:22:07 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 21:22:07 +0000 (UTC)
Subject: [wp-meta] [7130]
 sites/trunk/wp15.wordpress.net/public_html/content: WP15: Set new
 Tagregator posts to `pending` for manual approval.
Message-ID: <20180418212207.A479C1B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 18 22:11:45 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 18 Apr 2018 22:11:45 +0000 (UTC)
Subject: [wp-meta] [7131]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-site-cloner/wordcamp-site-cloner.php:
 WordCamp Site Cloner: Cache site list in an option instead of a transient
Message-ID: <20180418221145.369C61B00476@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 01:01:09 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 19 Apr 2018 01:01:09 -0000
Subject: [wp-meta] [Making WordPress.org] #3584: Support Theme: Remove
 timeframe from pending posts notice
Message-ID: <058.0c1f1dc83b16c0916112680d5388e234@wordpress.org>

#3584: Support Theme: Remove timeframe from pending posts notice
----------------------------+--------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  task            |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 Per the latest [https://make.wordpress.org/support/2018/04/april-12th-
 support-team-meeting-summary/ Support Team meeting]:
 > When a post is held for moderation we currently inform users that it
 will be reviewed within 72 hours. Unfortunately users get hung up on “72”
 and don’t read the bit before it explaining that’s the longest period we
 expect them to wait.
 >
 > In light of this, we’ll be modifying the string to instead indicate that
 their post will be manually reviewed by a moderator to hopefully remove
 the scare element of the high number.

 Current text: "This post has been held for moderation by our automated
 system. It will be reviewed within 72 hours."

 Proposed text: "This post has been held for moderation by our automated
 system and will be manually reviewed by a moderator."

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

From noreply at wordpress.org  Thu Apr 19 01:02:55 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 01:02:55 +0000 (UTC)
Subject: [wp-meta] [7132]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support/functions.php:
 Support Theme: Remove timeframe from pending posts notice.
Message-ID: <20180419010255.508131B00728@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 01:02:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 19 Apr 2018 01:02:56 -0000
Subject: [wp-meta] [Making WordPress.org] #3584: Support Theme: Remove
 timeframe from pending posts notice
In-Reply-To: <058.0c1f1dc83b16c0916112680d5388e234@wordpress.org>
References: <058.0c1f1dc83b16c0916112680d5388e234@wordpress.org>
Message-ID: <073.2db7ca962e0b9c068706c96b9fcd68c6@wordpress.org>

#3584: Support Theme: Remove timeframe from pending posts notice
----------------------------+-----------------------------
 Reporter:  SergeyBiryukov  |       Owner:  SergeyBiryukov
     Type:  task            |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"7132" 7132]:
 {{{
 #!CommitTicketReference repository="" revision="7132"
 Support Theme: Remove timeframe from pending posts notice.

 Fixes #3584.
 }}}

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

From noreply at wordpress.org  Thu Apr 19 10:25:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 10:25:40 +0000 (UTC)
Subject: [wp-meta] [7133]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-bbp-topic-resolution/inc/class-plugin.php:
 Support Forums, Topic Resolution: Remove stray `</span>` tag.
Message-ID: <20180419102540.3188C1B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 10:52:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 10:52:40 +0000 (UTC)
Subject: [wp-meta] =?utf-8?q?=5B7134=5D_sites/trunk/wordpress=2Eorg/public?=
 =?utf-8?q?=5Fhtml/wp-content/themes/pub/wporg-support/footer=2Ephp=3A_Sup?=
 =?utf-8?q?port_Theme=3A_Add_missing_closing_tag_for_=60=3Cdiv_id=3D=22pag?=
 =?utf-8?b?ZSI+YC4=?=
Message-ID: <20180419105240.9AAEB1B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 11:39:32 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 11:39:32 +0000 (UTC)
Subject: [wp-meta] [7135]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support:
 Support Theme: After [7126],
 reorder styles for inline admin links for better browser compatibility.
Message-ID: <20180419113932.D63221B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 11:39:33 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 19 Apr 2018 11:39:33 -0000
Subject: [wp-meta] [Making WordPress.org] #3579: Thread "Edit" link not
 keyboard accessible
In-Reply-To: <051.716de798aa91e0266c31d3d85a4f11eb@wordpress.org>
References: <051.716de798aa91e0266c31d3d85a4f11eb@wordpress.org>
Message-ID: <066.a0a0f189c9903e452cc241407846736a@wordpress.org>

#3579: Thread "Edit" link not keyboard accessible
----------------------------+-----------------------------
 Reporter:  anevins         |       Owner:  SergeyBiryukov
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [changeset:"7135" 7135]:
 {{{
 #!CommitTicketReference repository="" revision="7135"
 Support Theme: After [7126], reorder styles for inline admin links for
 better browser compatibility.

 See #3579.
 }}}

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

From noreply at wordpress.org  Thu Apr 19 11:45:44 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 11:45:44 +0000 (UTC)
Subject: [wp-meta] [7136]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-support:
 Support Theme: Bump CSS version for cache bust.
Message-ID: <20180419114544.90E321B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 21:23:16 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 21:23:16 +0000 (UTC)
Subject: [wp-meta] [7137]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-showcase/404.php:
 Showcase: Replace 404 page with one showing a random site from the
 showcase.
Message-ID: <20180419212316.61EA51B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 22:09:09 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 22:09:09 +0000 (UTC)
Subject: [wp-meta] [7138]
 sites/trunk/wp15.wordpress.net/public_html/content/themes/twentyseventeen-wp15/page-swag.php:
 WP15 theme: Embed t-shirt product on Swag page
Message-ID: <20180419220909.EB4F51B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 19 22:12:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 19 Apr 2018 22:12:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3585: Polyglots mobile styling
 issue
Message-ID: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>

#3585: Polyglots mobile styling issue
--------------------------------------+--------------------
 Reporter:  seusmaniqbal              |      Owner:  (none)
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 There seems to be a mobile styling issue on the Polyglots main page
 "https://make.wordpress.org/polyglots/". Pinned post icon overlapping the
 author name. I've tested this on Huawei Y6 Pro.

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

From noreply at wordpress.org  Thu Apr 19 22:14:32 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 19 Apr 2018 22:14:32 -0000
Subject: [wp-meta] [Making WordPress.org] #3585: Polyglots mobile
 styling issue
In-Reply-To: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>
References: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>
Message-ID: <071.d9030a196ba64e8aa22eb68a5ff88a9f@wordpress.org>

#3585: Polyglots mobile styling issue
--------------------------------------+---------------------
 Reporter:  seusmaniqbal              |       Owner:  (none)
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by seusmaniqbal):

 * Attachment "Polyglots_mobile_styling _issue.png" added.

 Polyglots mobile styling issue

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

From noreply at wordpress.org  Thu Apr 19 22:24:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 19 Apr 2018 22:24:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3585: Polyglots mobile
 styling issue
In-Reply-To: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>
References: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>
Message-ID: <071.d733bc290c6bc3e667462dc68651f20c@wordpress.org>

#3585: Polyglots mobile styling issue
-----------------------------------------+---------------------
 Reporter:  seusmaniqbal                 |       Owner:  (none)
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Translate Site & Plugins     |  Resolution:
 Keywords:  needs-patch has-screenshots  |
-----------------------------------------+---------------------
Changes (by abdullahramzan):

 * keywords:   => needs-patch has-screenshots


Comment:

 Hello @seusmaniqbal ,

 Welcome to the WordPress Meta Trac.

 I have tested it on my end as well. It looks pinned icon overlapped with
 the author name.

 @gibrown can you please give some feedback on it.

 Thanks,

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

From noreply at wordpress.org  Thu Apr 19 23:14:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 19 Apr 2018 23:14:36 +0000 (UTC)
Subject: [wp-meta] [7139]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-showcase/404.php:
 Showcase: Fix closing tag and apostrophe.
Message-ID: <20180419231436.6C7D41B005CA@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 00:40:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 20 Apr 2018 00:40:40 +0000 (UTC)
Subject: [wp-meta] [7140]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/addons/code-of-conduct.php:
 WordCamp tickets: Add context to CoC answer translation string
Message-ID: <20180420004040.11EFF1B00710@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 01:27:12 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 20 Apr 2018 01:27:12 +0000 (UTC)
Subject: [wp-meta] [7141]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/gutenberg/inc/docs-importer.php:
 Gutenberg Theme: When importing docs,
 replace relative URLs with absolute URLs,
 so that the docs in the repo can link to the correct place.
Message-ID: <20180420012712.E171C1B00710@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 01:50:06 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 20 Apr 2018 01:50:06 +0000 (UTC)
Subject: [wp-meta] [7142]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/gutenberg/inc/docs-importer.php:
 Gutenberg theme: Make the Markdown importer a little stricter on which URLs
 it chooses to transform when importing.
Message-ID: <20180420015006.0CED71B00710@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 06:02:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 06:02:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3585: Polyglots mobile
 styling issue
In-Reply-To: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>
References: <056.1b42f9bcb9711e315781b1549384b35f@wordpress.org>
Message-ID: <071.195e4cc0c5f4bc3a20cd6fb6fa2f584f@wordpress.org>

#3585: Polyglots mobile styling issue
-----------------------------------------+---------------------
 Reporter:  seusmaniqbal                 |       Owner:  (none)
     Type:  defect                       |      Status:  new
 Priority:  low                          |   Milestone:
Component:  Make (Get Involved) / P2     |  Resolution:
 Keywords:  needs-patch has-screenshots  |
-----------------------------------------+---------------------
Changes (by ocean90):

 * priority:  normal => low
 * component:  Translate Site & Plugins => Make (Get Involved) / P2


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

From noreply at wordpress.org  Fri Apr 20 07:04:06 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 20 Apr 2018 07:04:06 +0000 (UTC)
Subject: [wp-meta] [7143]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Give announce
 to flixos90 in #core-restapi.
Message-ID: <20180420070406.63A741B004DF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 13:11:09 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 13:11:09 -0000
Subject: [wp-meta] [Making WordPress.org] #3586: Enhancement: Display if a
 project has translation validators in the editors waiting projects page
Message-ID: <053.98e3d8cc8aac21e459db3e572556390f@wordpress.org>

#3586: Enhancement: Display if a project has translation validators in the editors
waiting projects page
--------------------------------------+--------------------
 Reporter:  lenasterg                 |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 Hi.
 It would be useful for the locales GTE if the "waiting projects" page had
 info/indication on each project which has PTE.
 [[Image(https://ibb.co/mU7obn)]]
 Something like the [https://ibb.co/mU7obn] draft screenshot or other
 implementation like: new page "Waiting - no PTE"

 Thanks in advance.

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

From noreply at wordpress.org  Fri Apr 20 13:34:12 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 13:34:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3586: Enhancement: Display if
 a project has translation validators in the editors waiting projects page
In-Reply-To: <053.98e3d8cc8aac21e459db3e572556390f@wordpress.org>
References: <053.98e3d8cc8aac21e459db3e572556390f@wordpress.org>
Message-ID: <068.6652742ca3cfd0608e31f2512c26a89c@wordpress.org>

#3586: Enhancement: Display if a project has translation validators in the editors
waiting projects page
--------------------------------------+---------------------
 Reporter:  lenasterg                 |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Description changed by SergeyBiryukov:

Old description:

> Hi.
> It would be useful for the locales GTE if the "waiting projects" page had
> info/indication on each project which has PTE.
> [[Image(https://ibb.co/mU7obn)]]
> Something like the [https://ibb.co/mU7obn] draft screenshot or other
> implementation like: new page "Waiting - no PTE"
>
> Thanks in advance.

New description:

 Hi.
 It would be useful for the locales GTE if the "waiting projects" page had
 info/indication on each project which has PTE.

 Something like the [https://ibb.co/mU7obn] draft screenshot or other
 implementation like: new page "Waiting - no PTE"

 Thanks in advance.

--

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

From noreply at wordpress.org  Fri Apr 20 13:34:30 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 13:34:30 -0000
Subject: [wp-meta] [Making WordPress.org] #3586: Enhancement: Display if
 a project has translation validators in the editors waiting projects page
In-Reply-To: <053.98e3d8cc8aac21e459db3e572556390f@wordpress.org>
References: <053.98e3d8cc8aac21e459db3e572556390f@wordpress.org>
Message-ID: <068.16ec0b0723e2cdd5e9376e6676e8db7f@wordpress.org>

#3586: Enhancement: Display if a project has translation validators in the editors
waiting projects page
--------------------------------------+---------------------
 Reporter:  lenasterg                 |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "validator_waiting.png" added.


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

From noreply at wordpress.org  Fri Apr 20 13:43:58 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 13:43:58 -0000
Subject: [wp-meta] [Making WordPress.org] #3587: Default image when sharing
 forum topics on social networks
Message-ID: <054.dabd3bd44094eda958896ec9f5605cc7@wordpress.org>

#3587: Default image when sharing forum topics on social networks
----------------------------+-------------------------
 Reporter:  felipeelia      |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  low             |  Milestone:
Component:  Support Forums  |   Keywords:  2nd-opinion
----------------------------+-------------------------
 While sharing [https://wordpress.org/support/topic/gdpr-and-the-forum-of-
 wordpress-org/ this forum topic] on Facebook, I've noticed that
 differently from what happens when we share a `/news` blog post, there is
 not a default image with it. As a fallback, Facebook tries to get the
 first image, so the topic is displayed with the user avatar (in this case
 a random image).

 Can we use some default image for these cases too?

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

From noreply at wordpress.org  Fri Apr 20 19:14:42 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 19:14:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3588: Add Hosting badges for
 Team/Contributors.
Message-ID: <056.58068755dc2463ff64287097a2bc0e89@wordpress.org>

#3588: Add Hosting badges for Team/Contributors.
--------------------------+--------------------
 Reporter:  mikeschroder  |      Owner:  (none)
     Type:  task          |     Status:  new
 Priority:  normal        |  Milestone:
Component:  Profiles      |   Keywords:
--------------------------+--------------------
 Could you please add Hosting team badges for this initial list of folks?

 Team (and Contributor):
 @andrewtaylor-1 @danielbachhuber @jadonn (looks like @mikeschroder is
 already added)

 Contributor:
 @boogah @aaroncampbell @smaffulli @jorbin @mikehansenme @octalmage
 @voldemortensen @squidboylan @coreymckrill @samuelsidler @lukecavanagh
 @ipstenu @robertpd @straussd @pdclark @brettface @ifyouwillit @dhsean
 @timbutlerau @fuegas @nathanielks @dws122 @jstrotmann @mikeschinkel
 @dgorton

 Thanks much!

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

From noreply at wordpress.org  Fri Apr 20 19:22:35 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 19:22:35 -0000
Subject: [wp-meta] [Making WordPress.org] #3588: Add Hosting badges for
 Team/Contributors.
In-Reply-To: <056.58068755dc2463ff64287097a2bc0e89@wordpress.org>
References: <056.58068755dc2463ff64287097a2bc0e89@wordpress.org>
Message-ID: <071.d68e35d8f60ce7010a36eead5db19cba@wordpress.org>

#3588: Add Hosting badges for Team/Contributors.
--------------------------+---------------------
 Reporter:  mikeschroder  |       Owner:  (none)
     Type:  task          |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Profiles      |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by Otto42):

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


Comment:

 Added all those users to the relevant groups.

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

From noreply at wordpress.org  Fri Apr 20 20:29:38 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 20 Apr 2018 20:29:38 +0000 (UTC)
Subject: [wp-meta] [7144]
 sites/trunk/api.wordpress.org/public_html/events/1.0/tests/test-index.php:
 Events: Update geolocation for `80.95.186.144` test case.
Message-ID: <20180420202938.361701B004DF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 20:29:41 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 20 Apr 2018 20:29:41 +0000 (UTC)
Subject: [wp-meta] [7145]
 sites/trunk/api.wordpress.org/public_html/events/1.0: Events: Only restrict
 results to a country when explicitly requested.
Message-ID: <20180420202941.09DD71B004DF@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 20 23:14:52 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 23:14:52 -0000
Subject: [wp-meta] [Making WordPress.org] #3589: Username on meta.trac page
 not showing properly
Message-ID: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>

#3589: Username on meta.trac page not showing properly
-------------------------+-------------------------------------------------
 Reporter:  pratikthink  |      Owner:  (none)
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Trac         |   Keywords:  has-screenshots ui-feedback needs-
                         |  design
-------------------------+-------------------------------------------------
 I got this issue when I clicked on the
 [https://meta.trac.wordpress.org/ticketgraph Ticket Graph] tab.

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

From noreply at wordpress.org  Fri Apr 20 23:15:38 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 23:15:38 -0000
Subject: [wp-meta] [Making WordPress.org] #3589: Username on meta.trac
 page not showing properly
In-Reply-To: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
References: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
Message-ID: <070.eecc4042c5a1533fa73d202bde50821f@wordpress.org>

#3589: Username on meta.trac page not showing properly
-------------------------------------------------+-------------------------
 Reporter:  pratikthink                          |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Trac                                 |  Resolution:
 Keywords:  has-screenshots ui-feedback needs-   |
  design                                         |
-------------------------------------------------+-------------------------
Changes (by pratikthink):

 * Attachment "2018-04-21 04_34_11-Ticket Graph – Making WordPress.org.jpg"
 added.


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

From noreply at wordpress.org  Fri Apr 20 23:18:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 20 Apr 2018 23:18:54 -0000
Subject: [wp-meta] [Making WordPress.org] #3589: Username on meta.trac
 page not showing properly
In-Reply-To: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
References: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
Message-ID: <070.5b8595a41bb87e8752dcaf9730956559@wordpress.org>

#3589: Username on meta.trac page not showing properly
-------------------------------------------------+-------------------------
 Reporter:  pratikthink                          |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Trac                                 |  Resolution:
 Keywords:  has-screenshots ui-feedback needs-   |
  design                                         |
-------------------------------------------------+-------------------------

Comment (by pratikthink):

 also on [https://core.trac.wordpress.org/ticketgraph core.trac]

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

From noreply at wordpress.org  Sat Apr 21 01:34:39 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 01:34:39 -0000
Subject: [wp-meta] [Making WordPress.org] #3590: Added some important
 navigation menu in the headline wrapper
Message-ID: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>

#3590: Added some important navigation menu in the headline wrapper
-------------------------+-------------------------------------------------
 Reporter:  pratikthink  |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  high         |  Milestone:
Component:  Trac         |   Keywords:  has-patch needs-testing ui-feedback
                         |  ux-feedback
-------------------------+-------------------------------------------------
 There were some menus on the [https://core.trac.wordpress.org/ WordPressk
 Trac] page that was not on the [https://meta.trac.wordpress.org/ Meta
 Trac] page.
 I've made some improvements to the menu and **added some links**.
 If you find it appropriate, add it to the page.

 **(menu added in the headline wrapper)**

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

From noreply at wordpress.org  Sat Apr 21 01:35:08 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 01:35:08 -0000
Subject: [wp-meta] [Making WordPress.org] #3590: Added some important
 navigation menu in the headline wrapper
In-Reply-To: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
References: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
Message-ID: <070.071cbd0d52942f26bf4fdfad104d03e5@wordpress.org>

#3590: Added some important navigation menu in the headline wrapper
-------------------------------------------------+-------------------------
 Reporter:  pratikthink                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  high                                 |   Milestone:
Component:  Trac                                 |  Resolution:
 Keywords:  has-patch needs-testing ui-feedback  |
  ux-feedback                                    |
-------------------------------------------------+-------------------------
Changes (by pratikthink):

 * Attachment "3590.diff" added.

 Patch file for Nav Menu

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

From noreply at wordpress.org  Sat Apr 21 01:39:00 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 01:39:00 -0000
Subject: [wp-meta] [Making WordPress.org] #3590: Added some important
 navigation menu in the headline wrapper
In-Reply-To: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
References: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
Message-ID: <070.4a61b40065f2f2cce9e4ff39cc82ee14@wordpress.org>

#3590: Added some important navigation menu in the headline wrapper
-------------------------------------------------+-------------------------
 Reporter:  pratikthink                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  high                                 |   Milestone:
Component:  Trac                                 |  Resolution:
 Keywords:  has-patch needs-testing ui-feedback  |
  ux-feedback                                    |
-------------------------------------------------+-------------------------
Changes (by pratikthink):

 * Attachment "3590.2.diff" added.


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

From noreply at wordpress.org  Sat Apr 21 01:41:01 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 01:41:01 -0000
Subject: [wp-meta] [Making WordPress.org] #3590: Added some important
 navigation menu in the headline wrapper
In-Reply-To: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
References: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
Message-ID: <070.1f99d50c27ea78519323a8146e09155c@wordpress.org>

#3590: Added some important navigation menu in the headline wrapper
-----------------------------------------------+---------------------
 Reporter:  pratikthink                        |       Owner:  (none)
     Type:  enhancement                        |      Status:  new
 Priority:  high                               |   Milestone:
Component:  Trac                               |  Resolution:
 Keywords:  has-patch ui-feedback ux-feedback  |
-----------------------------------------------+---------------------
Changes (by pratikthink):

 * keywords:  has-patch needs-testing ui-feedback ux-feedback => has-patch
     ui-feedback ux-feedback


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

From noreply at wordpress.org  Sat Apr 21 11:15:43 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 11:15:43 -0000
Subject: [wp-meta] [Making WordPress.org] #3590: Added some important
 navigation menu in the headline wrapper
In-Reply-To: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
References: <055.aabbf8d3ec5366dc58e2f0d57ebf7f61@wordpress.org>
Message-ID: <070.fff6191daf15c493d8214891f987ec20@wordpress.org>

#3590: Added some important navigation menu in the headline wrapper
-----------------------------------------------+---------------------
 Reporter:  pratikthink                        |       Owner:  (none)
     Type:  enhancement                        |      Status:  new
 Priority:  high                               |   Milestone:
Component:  Trac                               |  Resolution:
 Keywords:  has-patch ui-feedback ux-feedback  |
-----------------------------------------------+---------------------
Changes (by pratikthink):

 * Attachment "3590.3.diff" added.


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

From noreply at wordpress.org  Sat Apr 21 13:58:57 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 13:58:57 -0000
Subject: [wp-meta] [Making WordPress.org] #3591: Codex Main Page - Broken
 Link
Message-ID: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>

#3591: Codex Main Page - Broken Link
--------------------+--------------------
 Reporter:  xmic    |      Owner:  (none)
     Type:  defect  |     Status:  new
 Priority:  normal  |  Milestone:
Component:  Codex   |   Keywords:
--------------------+--------------------
 The [https://codex.wordpress.org/Main_Page Codex main page] has a broken
 link.

 [https://codex.wordpress.org/FAQ Frequently Asked Questions] should link
 to here instead:
 - https://codex.wordpress.org/FAQ_New_To_WordPress

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

From noreply at wordpress.org  Sat Apr 21 14:53:46 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 14:53:46 -0000
Subject: [wp-meta] [Making WordPress.org] #3591: Codex Main Page -
 Broken Link
In-Reply-To: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>
References: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>
Message-ID: <063.e3f6727ee214afbf05321cf45bb59248@wordpress.org>

#3591: Codex Main Page - Broken Link
--------------------+---------------------
 Reporter:  xmic    |       Owner:  (none)
     Type:  defect  |      Status:  closed
 Priority:  normal  |   Milestone:
Component:  Codex   |  Resolution:  fixed
 Keywords:          |
--------------------+---------------------
Changes (by Otto42):

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


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

From noreply at wordpress.org  Sat Apr 21 18:32:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 21 Apr 2018 18:32:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3591: Codex Main Page -
 Broken Link
In-Reply-To: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>
References: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>
Message-ID: <063.ead89a8e5e03c57d1579cd2f7f3a1b50@wordpress.org>

#3591: Codex Main Page - Broken Link
--------------------+---------------------
 Reporter:  xmic    |       Owner:  (none)
     Type:  defect  |      Status:  closed
 Priority:  normal  |   Milestone:
Component:  Codex   |  Resolution:  fixed
 Keywords:          |
--------------------+---------------------

Comment (by SergeyBiryukov):

 The previous link was correct, it's supposed to be a list of other FAQ
 pages:
 https://web.archive.org/web/20180202182642/https://codex.wordpress.org/FAQ

 It stopped working after a recent upgrade, see #3513 for more details.

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

From noreply at wordpress.org  Sun Apr 22 15:48:32 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 22 Apr 2018 15:48:32 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.6836e3d9c661b90ed9b18cb41fb19d10@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.9.patch" added.

 Redirect after a comment is edited

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

From noreply at wordpress.org  Sun Apr 22 15:53:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 22 Apr 2018 15:53:56 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.f0ae122351358e6ae3d1120c1fa8a56c@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------

Comment (by keesiemeijer):

 With patch [attachment:3572.9.patch] you're redirected to the edited
 comment after a comment is updated.
 This matches what happens after a new comment is created.

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

From noreply at wordpress.org  Mon Apr 23 00:34:16 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 00:34:16 +0000 (UTC)
Subject: [wp-meta] [7146]
 sites/trunk/buddypress.org/public_html/wp-content/plugins: BuddyPress:
 remove some `#wp-toolbar` styling from hardcoded `toolbar.php` files.
Message-ID: <20180423003416.EF28A1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 00:35:36 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 00:35:36 +0000 (UTC)
Subject: [wp-meta] [7147]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress: tweak some header & toolbar styling.
Message-ID: <20180423003536.4EE4B1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 00:38:43 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 00:38:43 +0000 (UTC)
Subject: [wp-meta] [7148]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress: put `#wp-toolbar` margin back for normal width pages.
Message-ID: <20180423003843.BD98F1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:33:10 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:33:10 +0000 (UTC)
Subject: [wp-meta] [7149]
 sites/trunk/buddypress.org/public_html/wp-content/plugins: BuddyPress: move
 more admin-bar styling tweaks into bb-base theme.
Message-ID: <20180423013310.92B311B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:34:11 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:34:11 +0000 (UTC)
Subject: [wp-meta] [7150]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress: first pass making primary menu nav responsive.
Message-ID: <20180423013411.654EE1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:35:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:35:40 +0000 (UTC)
Subject: [wp-meta] [7151]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress: make responsive hamburger menu target bigger.
Message-ID: <20180423013540.F36C31B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:40:32 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:40:32 +0000 (UTC)
Subject: [wp-meta] [7152]
 sites/trunk/buddypress.org/public_html/wp-content/plugins: BuddyPress: set
 admin-bar top to always be `81px`.
Message-ID: <20180423014032.1A3CD1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:44:40 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:44:40 +0000 (UTC)
Subject: [wp-meta] [7153]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress: more responsive nav tweaks.
Message-ID: <20180423014440.D46461B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:50:45 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:50:45 +0000 (UTC)
Subject: [wp-meta] [7154]
 sites/trunk/buddypress.org/public_html/wp-content/themes: BuddyPress:
 Update codex theme headers.
Message-ID: <20180423015045.D93F91B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 01:57:14 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 01:57:14 +0000 (UTC)
Subject: [wp-meta] [7155]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base/header-head.php:
 BuddyPress: add `viewport` meta tag, so responsiveness kicks in.
Message-ID: <20180423015714.141621B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 02:08:05 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 23 Apr 2018 02:08:05 -0000
Subject: [wp-meta] [Making WordPress.org] #3589: Username on meta.trac
 page not showing properly
In-Reply-To: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
References: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
Message-ID: <070.3ebf247737d114d1e3bc4aa6ab2402b1@wordpress.org>

#3589: Username on meta.trac page not showing properly
-------------------------------------------------+-------------------------
 Reporter:  pratikthink                          |       Owner:  (none)
     Type:  defect                               |      Status:  closed
 Priority:  normal                               |   Milestone:
Component:  Trac                                 |  Resolution:  duplicate
 Keywords:  has-screenshots ui-feedback needs-   |
  design                                         |
-------------------------------------------------+-------------------------
Changes (by dd32):

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


Comment:

 This will be fixed once the JS is working on the ticketgraph page again.
 See #3526

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

From noreply at wordpress.org  Mon Apr 23 02:41:19 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 02:41:19 +0000 (UTC)
Subject: [wp-meta] [7156]
 sites/trunk/buddypress.org/public_html/wp-content/themes: BuddyPress: more
 responsive CSS tweaks for codex.
Message-ID: <20180423024119.5285C1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 02:50:29 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 02:50:29 +0000 (UTC)
Subject: [wp-meta] [7157]
 sites/trunk/buddypress.org/public_html/wp-content/themes: BuddyPress: bump
 CSS versions, tweak codex activity styling for mobile.
Message-ID: <20180423025029.1782F1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 05:22:42 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 23 Apr 2018 05:22:42 +0000 (UTC)
Subject: [wp-meta] [7158]
 sites/trunk/buddypress.org/public_html/wp-content/themes/bb-base:
 BuddyPress: add `:not(.home)` to content margin styling.
Message-ID: <20180423052242.CC81A1B00735@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Mon Apr 23 11:16:42 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 23 Apr 2018 11:16:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3589: Username on meta.trac
 page not showing properly
In-Reply-To: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
References: <055.b5d11b3b737b4615f1a37d50fa9fbf45@wordpress.org>
Message-ID: <070.e4b9a4f65c9701998aa34b1c39dc6d4e@wordpress.org>

#3589: Username on meta.trac page not showing properly
-----------------------------+------------------------
 Reporter:  pratikthink      |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  low              |   Milestone:
Component:  Trac             |  Resolution:  duplicate
 Keywords:  has-screenshots  |
-----------------------------+------------------------
Changes (by pratikthink):

 * keywords:  has-screenshots ui-feedback needs-design => has-screenshots
 * priority:  normal => low


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

From noreply at wordpress.org  Mon Apr 23 15:53:47 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 23 Apr 2018 15:53:47 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.de811bc5b9f36b1c57ee18cd92ee0304@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------
Changes (by keesiemeijer):

 * Attachment "3572.10.patch" added.

 Don't show edit notice if a comment wasn't updated

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

From noreply at wordpress.org  Mon Apr 23 15:56:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 23 Apr 2018 15:56:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3572: Allow users to edit
 their own notes
In-Reply-To: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
References: <056.baff25b4b95dde62b1cc208b44b262a2@wordpress.org>
Message-ID: <071.2cdd30cdcda3de9c83af358e9b4d2bf1@wordpress.org>

#3572: Allow users to edit their own notes
---------------------------------------+---------------------
 Reporter:  keesiemeijer               |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Developer Hub              |  Resolution:
 Keywords:  has-patch has-screenshots  |
---------------------------------------+---------------------

Comment (by keesiemeijer):

 Patch [attachment:3572.10.patch] removes the edit notice if a comment
 wasn't updated after editing. Comments are now updated on the `init` hook
 with priority 20. This ensures the theme (or the WP Parser) have
 registered the parsed post types needed to check if a the current user can
 edit a comment.

 Sorry for the many patches. This was a work in progress that (I think) is
 now stable for commit.

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

From noreply at wordpress.org  Tue Apr 24 03:09:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 24 Apr 2018 03:09:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3526: Fix any brokenness in
 Trac 1.2.2
In-Reply-To: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
References: <048.f0b3b598bb607f8ccfc1b0b787f28823@wordpress.org>
Message-ID: <063.e499ec6acccb216e1dd779fef15f93c9@wordpress.org>

#3526: Fix any brokenness in Trac 1.2.2
------------------+---------------------
 Reporter:  dd32  |       Owner:  (none)
     Type:  task  |      Status:  new
 Priority:  high  |   Milestone:
Component:  Trac  |  Resolution:
 Keywords:        |
------------------+---------------------

Comment (by dd32):

 The Ticket Graph plugin has been upgraded by Systems, looks to be working
 well. Might need to force-refresh your browser.

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

From noreply at wordpress.org  Tue Apr 24 03:23:27 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 24 Apr 2018 03:23:27 -0000
Subject: [wp-meta] [Making WordPress.org] #3046: WordPress.org/about
 page outdated
In-Reply-To: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
References: <053.c6f562bc755f53601156863a7128273e@wordpress.org>
Message-ID: <068.299e9d691ab2e2830050f5366aa4478e@wordpress.org>

#3046: WordPress.org/about page outdated
------------------------------------------+---------------------
 Reporter:  melchoyce                     |       Owner:  dd32
     Type:  task                          |      Status:  closed
 Priority:  high                          |   Milestone:
Component:  General                       |  Resolution:  fixed
 Keywords:  neso ui-feedback ux-feedback  |
------------------------------------------+---------------------
Changes (by dd32):

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


Comment:

 I'm going to mark this as fixed with all future issues to be Ticketed.

 See the following list of related tickets: (It's a dynamic list)

 [[TicketQuery(component=General,summary^=about)]]

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

From noreply at wordpress.org  Tue Apr 24 03:24:04 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 24 Apr 2018 03:24:04 -0000
Subject: [wp-meta] [Making WordPress.org] #3548: About: Add simplified
 logo back to the Graphics and Logos page (was: Add simplified logo back to
 the Graphics and Logos page)
In-Reply-To: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>
References: <048.c80102e1ea5f388d20813da76dc82499@wordpress.org>
Message-ID: <063.af5a22500f2709d078411bb4c24ad684@wordpress.org>

#3548: About: Add simplified logo back to the Graphics and Logos page
-------------------------+---------------------
 Reporter:  mapk         |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  high         |   Milestone:
Component:  General      |  Resolution:
 Keywords:  about logos  |
-------------------------+---------------------

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

From noreply at wordpress.org  Tue Apr 24 03:33:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 24 Apr 2018 03:33:45 -0000
Subject: [wp-meta] [Making WordPress.org] #629: SSL for Mailing list
 access (was: Mailing list access not loading)
In-Reply-To: <051.f9dd6a009c90b5f9c019ff2ee2f73686@wordpress.org>
References: <051.f9dd6a009c90b5f9c019ff2ee2f73686@wordpress.org>
Message-ID: <066.36658c86f607e6633523bbc05bbe6837@wordpress.org>

#629: SSL for Mailing list access
---------------------+---------------------
 Reporter:  jenmylo  |       Owner:  (none)
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:
Component:  SSL      |  Resolution:
 Keywords:           |
---------------------+---------------------
Changes (by dd32):

 * component:  Mailing Lists => SSL


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

From noreply at wordpress.org  Tue Apr 24 10:09:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 24 Apr 2018 10:09:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <066.e8815e36d47cbc15c46399eb2581f965@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by Presskopp):

 This would be a very welcome enhancement for the onboarding process! +1

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

From noreply at wordpress.org  Tue Apr 24 13:42:23 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 24 Apr 2018 13:42:23 -0000
Subject: [wp-meta] [Making WordPress.org] #3506: Core SVN commit blocked
 by a pre-commit hook
In-Reply-To: <058.70839433da2709f4c81ee709e46c0391@wordpress.org>
References: <058.70839433da2709f4c81ee709e46c0391@wordpress.org>
Message-ID: <073.914e6305e3fb65f2d75a380204b0129f@wordpress.org>

#3506: Core SVN commit blocked by a pre-commit hook
-----------------------------+---------------------
 Reporter:  SergeyBiryukov   |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Version Control  |  Resolution:
 Keywords:                   |
-----------------------------+---------------------

Comment (by markjaquith):

 Replying to [comment:3 SergeyBiryukov]:
 > Replying to [comment:1 Otto42]:
 > > Is this new syntax to 7.1?
 >
 > No, [http://php.net/manual/en/migration70.new-features.php#migration70
 .new-features.return-type-declarations it appeared in 7.0].

 Return type declarations were introduced in 7.0, but the `void` return
 type declaration was introduced in PHP 7.1

 http://php.net/manual/en/migration71.new-features.php

 Though that linting error on the `:` does seem to suggest that the `:` is
 the problem it is having, not the `void` after it. :-)

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

From noreply at wordpress.org  Wed Apr 25 04:36:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 04:36:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
Message-ID: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+--------------------
 Reporter:  Nao          |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  low          |  Milestone:
Component:  General      |   Keywords:
-------------------------+--------------------
 In the metropolitan Tokyo area, close to 10 events may be scheduled per
 month within the 400km range.

 This means that users may not see a local meetup close to their home until
 when there are only 2 other events within the 400km range, even if the
 organizer schedules it a month ahead of the time.

 Depending on the schedule, the timing could be a few weeks before the
 local event takes place.

 I'd say it's unlikely users go to an event over 100 km away because they
 can find a closer event (unless it's a large one with lots of speakers or
 WordCamp). A 400km radius covers about a third of the country.

 == Ideal Solution for Our Case ==

 Just writing this out, even though I understand our situation is an edge
 case.

 Personally, I feel the right mix to be the following for the case of
 cities near Tokyo.

 * 1 upcoming WordCamp within the country (Once a WC is scheduled it stays
 until it's over)
 * 5 meetups within a 100km radius

 But for other cities in Japan, a 200km radius may be more reasonable.

 == Compromised Solution ==

 If tweaking the radius range (or making exceptions) per city/country is
 not feasible, I'd like to see more upcoming events in the widget. This
 change provides 1) an incentive for organizers to schedule their events
 ahead of the time 2) a chance for attendees to find out their nearby
 events.

 **How about showing 5 events instead of 3 when they exist?** This change
 will not affect areas will less frequent meetups but will help those with
 several nearby meetups.

 Keeping the 400km radius isn't ideal for my location, but I can live with
 it as long as more meetups are shown.

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

From noreply at wordpress.org  Wed Apr 25 04:36:45 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 04:36:45 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.3cc07fcfccb3780646216466ced8985f@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  low          |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by Nao):

 * Attachment "japan-400km.png" added.

 Map of 400 km radius from Tokyo

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

From noreply at wordpress.org  Wed Apr 25 08:47:17 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 08:47:17 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.e320424f6821fee6bc31e12cabc65451@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  low          |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by casiepa):

 How about making it parameters that a site admin can set?
 - Number of meetups to show (between 2 and 4)
 - Number of WordCamps to show (between 1 and 3)
 - Radius: 100km - 400km
 - Limit to country: Y/N
 But the total of the first 2 can never be over 5

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

From noreply at wordpress.org  Wed Apr 25 10:36:12 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 10:36:12 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.cf7ae0236c6534157e7167d01e1d91dc@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  low          |   Milestone:
Component:  General      |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by nukaga):

 I agree that a site admin can set. The situation of the place where we
 live is various.

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

From noreply at wordpress.org  Wed Apr 25 13:20:22 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 13:20:22 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.18829bf5a073e57ae718c49373f46c04@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by iandunn):

 * priority:  low => normal
 * component:  General => API


Comment:

 Replying to [ticket:3592 Nao]:
 > In the metropolitan Tokyo area, close to 10 events may be scheduled per
 month within the 400km range.

 The 400km range is only for WordCamps, for meetups the range is
 100k.[[br]][[br]]


 > * 1 upcoming WordCamp within the country (Once a WC is scheduled it
 stays until it's over)

 The upcoming change to pin camps to the widget (#wp41112) should help with
 that.[[br]][[br]]


 > How about showing 5 events instead of 3 when they exist? This change
 will not affect areas will less frequent meetups but will help those with
 several nearby meetups.

 It could affect some infrequent meetups, if they setup recurring events
 several months into the future. We could avoid that by having the API only
 include meetups that are less than ~4 weeks away, though.

 I still worry about adding too much clutter to the UI, though. In the
 original design, `3` was chosen specifically to try and balance the amount
 of information that users are presented with.[[br]][[br]]


 > Just writing this out, even though I understand our situation is an edge
 case.

 I think it's still worth considering, and it's very helpful to get
 feedback from various communities, since they're all so different.

 I definitely agree that there isn't a good one-size-fits-all solution, but
 I also have a hard time finding an elegant solution for all (or even most)
 use cases that doesn't have considerable downsides (for UX,
 maintainability, complexity, etc).

 I think it's also important to keep in mind that the original purpose of
 the widget wasn't to help insiders like us keep track of 100% of the
 events that we’re interested in; it was to introduce new people to their
 local WP community. If someone wants to keep to track of 100% of events,
 then there are probably better ways, like signing up for meetup.com email
 notifications.

 If we can find elegant ways to make the list of events more relevant to
 the user, though, that's definitely worthwhile. Maybe the API can look at
 the total number of upcoming events, and if there are more than ~3 in the
 next ~2 weeks, then it would remove some of the farther events from the
 response, so that events closer to the user are given precedence.

 Another idea would be to use a translated string to set the radius per
 locale, and then pass that value to the API. That way smaller countries
 with large populations and active communities could set different locales
 than larger countries where driving longer distances is common. Using a
 translated string would prevent us from having to build/maintain per-
 country logic in the API itself. The API would probably want to enforce a
 reasonable min/max value, though.

 One downside to that approach is that the best value for a locale is
 subjective, and different translators might have conflicting opinions.
 That's not necessarily a huge problem, though, since the translation
 editors could help find a reasonable compromise.[[br]][[br]]

 Related #wp41442, #2998

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

From noreply at wordpress.org  Wed Apr 25 13:55:55 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 13:55:55 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <066.9265831f62a03bf4a35220fd7f4ed657@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by oschmehr):

 We often see contributors translating strings (with best intentions) but
 they're not aware of local rules, our glossary and the german #polyglots
 channel.
 Such a custumizable hint as described above would be a great help for them
 (and us). +1

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

From noreply at wordpress.org  Wed Apr 25 17:16:09 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 17:16:09 +0000 (UTC)
Subject: [wp-meta] [7159]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Give announce
 to @jadonn in #hosting-community.
Message-ID: <20180425171609.1B4A51B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 17:37:59 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 17:37:59 +0000 (UTC)
Subject: [wp-meta] [7160]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/privacy.php:
 Privacy: Set a consistent privacy policy URL for the entire network.
Message-ID: <20180425173759.957A41B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 18:13:15 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 18:13:15 +0000 (UTC)
Subject: [wp-meta] [7161]
 sites/trunk/wordcamp.org/public_html/wp-content/themes/campsite-2017/footer.php:
 CampSite 2017: Use HTTPS when linking to `wordpress.org`.
Message-ID: <20180425181315.C6FC01B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 18:13:19 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 18:13:19 +0000 (UTC)
Subject: [wp-meta] [7162]
 sites/trunk/wordcamp.org/public_html/wp-content/themes/campsite-2017/footer.php:
 CampSite 2017: Remove redundant `title` attribute from link.
Message-ID: <20180425181319.315A31B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 18:13:22 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 18:13:22 +0000 (UTC)
Subject: [wp-meta] [7163]
 sites/trunk/wordcamp.org/public_html/wp-content/themes: WordCamp Themes:
 Apply coding standards.
Message-ID: <20180425181322.BFBCE1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 18:13:26 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 18:13:26 +0000 (UTC)
Subject: [wp-meta] [7164]
 sites/trunk/wordcamp.org/public_html/wp-content/themes: WordCamp Themes:
 Add Privacy Policy links to the footer.
Message-ID: <20180425181326.AA24D1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 18:13:30 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 18:13:30 +0000 (UTC)
Subject: [wp-meta] [7165]
 sites/trunk/wordcamp.org/public_html/wp-content/themes/wordcamp-central-2012/functions.php:
 WordCamp Central: Apply coding standards.
Message-ID: <20180425181330.39C831B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 18:14:11 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 18:14:11 +0000 (UTC)
Subject: [wp-meta] [7166]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-coming-soon-page/views/template-coming-soon.php:
 WordCamp Coming Soon Page: Add Privacy Policy link to footer.
Message-ID: <20180425181411.A81EA1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 21:13:17 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 21:13:17 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <066.62248ab18795bf3a833c88e752c46519@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by Presskopp):

 * Attachment "1.jpg" added.


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

From noreply at wordpress.org  Wed Apr 25 21:13:27 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 21:13:27 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <066.70f08222c92c6ee407007890f7ecb036@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by Presskopp):

 * Attachment "2.jpg" added.


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

From noreply at wordpress.org  Wed Apr 25 21:19:13 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 21:19:13 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <066.9f73a6c79482a9feb9e8ac683b32e9c6@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "37572729-b4f4cb8e-2b0f-11e8-8fed-095712fad96b.jpg" added.


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

From noreply at wordpress.org  Wed Apr 25 21:19:29 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 25 Apr 2018 21:19:29 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "37572729-b4f4cb8e-2b0f-11e8-8fed-095712fad96b.jpg" removed.


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

From noreply at wordpress.org  Wed Apr 25 21:24:50 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 21:24:50 +0000 (UTC)
Subject: [wp-meta] [7167]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Extend date range to include more events.
Message-ID: <20180425212450.7F4DC1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 23:32:06 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 23:32:06 +0000 (UTC)
Subject: [wp-meta] [7168]
 sites/trunk/wordcamp.org/public_html/wp-content/themes: WordCamp Themes:
 Update privacy policy link separator.
Message-ID: <20180425233206.285041B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Wed Apr 25 23:32:09 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 25 Apr 2018 23:32:09 +0000 (UTC)
Subject: [wp-meta] [7169]
 sites/trunk/wordcamp.org/public_html/wp-content/themes/campsite-2017/footer.php:
 CampSite 2017: Remove extra space from Central link
Message-ID: <20180425233209.57A2B1B003FE@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 26 01:51:41 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 26 Apr 2018 01:51:41 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.617fcb9cce166543cf8e124d324c7f45@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by Nao):

 Thanks @iandunn !

  The 400km range is only for WordCamps, for meetups the range is 100k.

 @casiepa and others mentioned this in Slack, thanks for confirming.

  It could affect some infrequent meetups, if they setup recurring events
 several months into the future.

 I didn't think of such a case. I agree that seeing 4+ upcoming meetups
 that are months away could be not so useful for users.

  We could avoid that by having the API only include meetups that are less
 than ~4 weeks away, though.

  I think it's also important to keep in mind that the original purpose of
 the widget wasn't to help insiders like us keep track of 100% of the
 events that we’re interested in; it was to introduce new people to their
 local WP community.

 It was not my intention to keep track of all events (We already have
 [https://calendar.google.com/calendar/embed?src=wpja.team at gmail.com
 WordPress Events Calendar] for that in Japan). I get the feedback that the
 number of new attendees visibly increased for many meetup groups here,
 therefore the organizers are really eager to see their own event listed as
 soon as possible after scheduling one (they love this feature! and I think
 that's one of the reasons the number of meetups incresed this year).

 Generally speaking, I'm not a huge fan of using translation string to set
 a value for default configuration, but it sounds like a possible good
 solution for this. One downside I can think of is that it doesn't really
 work for transplant users who are using WP in their native language (e.g.
 someone who lives in Germany but is from Australia, using WP in en_AU).

  If we can find elegant ways to make the list of events more relevant to
 the user, though, that's definitely worthwhile. Maybe the API can look at
 the total number of upcoming events, and if there are more than ~3 in the
 next ~2 weeks, then it would remove some of the farther events from the
 response, so that events closer to the user are given precedence.

 I like this too, and I think it will work for Japanese users if the
 threshold is set right. For me, 100km is a quite long distance to travel
 for a short meetup. I originally said 100k for Tokyo, but now that I see
 the map more closely, 50k is probably a more reasonable number.

 As you said, the distance one's wiling to travel for a meeting can be very
 subjective. It will depend the public transportaiton system, car
 ownership, family and work situation, etc. I'm interested in hearing
 opinions from people in various situations.

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

From noreply at wordpress.org  Thu Apr 26 01:52:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 26 Apr 2018 01:52:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.d919db8259b6e5a9fc1c6a8f57f6da00@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by Nao):

 * Attachment "100km-radius.png" added.

 100km radius from Tokyo, Kawaguchi (Saitama Prefecture), Takasaki (Gunma
 Prefecture)

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

From noreply at wordpress.org  Thu Apr 26 01:52:42 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 26 Apr 2018 01:52:42 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.5315c0bfea71840aaaf5945bcc46efc7@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+---------------------
Changes (by Nao):

 * Attachment "50km-radius.png" added.

 50km radius from Tokyo, Kawaguchi (Saitama Prefecture), Takasaki (Gunma
 Prefecture)

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

From noreply at wordpress.org  Thu Apr 26 02:03:18 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 26 Apr 2018 02:03:18 -0000
Subject: [wp-meta] [Making WordPress.org] #3592: Dashboard Event Widget:
 Display 5 meetups instead of 3
In-Reply-To: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
References: <047.793bce9b43d4ac91e851b1a2bac0e61e@wordpress.org>
Message-ID: <062.01ee7b0101dce741e68f16aa0c6e4ee7@wordpress.org>

#3592: Dashboard Event Widget: Display 5 meetups instead of 3
-------------------------+---------------------
 Reporter:  Nao          |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by dd32):

 It's worth noting that the radius is a box, not circular, so it's a box of
 100km north/east/south/west of the central points. When you're looking at
 meetups which are at the NW/NE/SE/SW directions that means it's closer to
 150KM radius.

 I think the ideal solution for areas such as Japan where there's lots of
 events within a small radius is that the API continues to return data as
 it does, but the client-side code slims it down to only those which are
 relevant, for example, "Only show meetups within a 30km radius".

 The API could also add the circular radius checks (and return any boxed
 area events if the circular radius doesn't return anything, to maintain
 current results) which may also help slightly in the case of Japan, as it
 seems the locations are more likely to be at those box corners.

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

From noreply at wordpress.org  Thu Apr 26 02:14:23 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 26 Apr 2018 02:14:23 +0000 (UTC)
Subject: [wp-meta] [7170]
 sites/trunk/buddypress.org/public_html/wp-content/themes: BuddyPress.org &
 bbPress.org: Add footer link to privacy policy
Message-ID: <20180426021423.060491B00727@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 26 05:47:31 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 26 Apr 2018 05:47:31 -0000
Subject: [wp-meta] [Making WordPress.org] #3522: Hint to locale
 translation rules instead to handbook
In-Reply-To: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
References: <051.4b788e6304085f83ee2c2d9688115033@wordpress.org>
Message-ID: <066.adb494fafcd3652c9bda4dff200821fb@wordpress.org>

#3522: Hint to locale translation rules instead to handbook
--------------------------------------+---------------------
 Reporter:  La Geek                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+---------------------

Comment (by casiepa):

 Please note that polyglots is keeping track of local slacks
 (https://make.wordpress.org/polyglots/handbook/about/teams/local-slacks/)
 and Style guides, glossaries
 (https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-
 wordpress-org/list-of-glossaries-per-locale/).

 Technically speaking, if this is to become a CPT, polyglots could continue
 to keep it updated.

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

From noreply at wordpress.org  Thu Apr 26 17:37:20 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 26 Apr 2018 17:37:20 +0000 (UTC)
Subject: [wp-meta] [7171]
 sites/trunk/wp15.wordpress.net/public_html/content/plugins/wp15-meetup-events/wp15-meetup-events.php:
 WP15: Add a few more event matching keywords.
Message-ID: <20180426173720.479561B00137@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 26 22:18:25 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 26 Apr 2018 22:18:25 +0000 (UTC)
Subject: [wp-meta] [7172]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-coming-soon-page:
 WordCamp Coming Soon Page: Update privacy policy link separator.
Message-ID: <20180426221825.663241B00281@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Thu Apr 26 22:18:32 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 26 Apr 2018 22:18:32 +0000 (UTC)
Subject: [wp-meta] [7173]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-coming-soon-page:
 WordCamp Coming Soon Page: Apply coding standards.
Message-ID: <20180426221832.6D9F91B00281@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Fri Apr 27 14:07:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 27 Apr 2018 14:07:56 -0000
Subject: [wp-meta] [Making WordPress.org] #3593: Centralize GitHub Markdown
 importer
Message-ID: <054.0a678546eed37353565504e6af8f2f5f@wordpress.org>

#3593: Centralize GitHub Markdown importer
-------------------------+--------------------
 Reporter:  schlessera   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Handbooks    |   Keywords:
-------------------------+--------------------
 There are currently a few teams that want GitHub Markdown importing to
 feed their handbook: [https://meta.trac.wordpress.org/changeset/4733 CLI],
 [https://meta.trac.wordpress.org/ticket/2968 REST API],
 [https://meta.trac.wordpress.org/changeset/6304 Gutenberg],
 [https://meta.trac.wordpress.org/ticket/3377 WPCS], and probably more to
 come in the future, I think it would be worth a small refactoring effort
 to produce a reusable plugin that handle this across all teams & sites.

 @rmccue has already done a lot of preliminary work for making this
 reusable in https://github.com/WP-API/markdown-sync, but some details are
 still missing.

 Basic functionality could look like the following:

 1. Field to enter a markdown source on GitHub. This could be a nice,
 proper UI, but simply accepting a custom field under a common field key
 convention would be enough for an MVP. Something like [https://github.com
 /WP-API/markdown-sync/blob/master/inc/class-importer.php#L17
 wporg_markdown_source] would do the trick.
 2. Refresh button in the post edit screen to fetch the latest version of
 the content from GitHub and make updates as needed.
 3. Cron job that goes through all posts that have a custom field as
 registered on 1. and update as needed.
 4. Ability to specifiy a manifest file that defines the posts (and their
 post type) to create and their respective markdown sources.
 5. Cron job that goes through the manifest file and adds/removes/updates
 posts as needed.

 1., 2. & 3. are also great for one-off pages/posts that should be updated
 from an arbitrary GitHub file, without it being tied in an automated
 structure. As an example, a feature project page like the one from
 [https://make.wordpress.org/core/features/servehappy/ servehappy] could be
 set up to be updated from the corresponding GitHub repo's
 [https://github.com/WordPress/servehappy/blob/master/README.md README.md
 file], or individual pages in the different team handbooks could be set up
 for easier collaboration.

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

From noreply at wordpress.org  Fri Apr 27 14:41:59 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 27 Apr 2018 14:41:59 -0000
Subject: [wp-meta] [Making WordPress.org] #3594: Email notifications not
 sent for updates to watched tickets
Message-ID: <051.294660e8bdaaeaf58c5707084c793b20@wordpress.org>

#3594: Email notifications not sent for updates to watched tickets
---------------------+--------------------
 Reporter:  iandunn  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  high     |  Milestone:
Component:  Trac     |   Keywords:
---------------------+--------------------
 It looks like email notifications are no longer being sent for watched
 tickets. They're still sent for tickets that the user has reported or
 replied to.

 It's likely that this broke during the recent migration.

 https://wordpress.slack.com/archives/C0C89GD35/p1524083152000448

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

From noreply at wordpress.org  Fri Apr 27 15:17:49 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 27 Apr 2018 15:17:49 -0000
Subject: [wp-meta] [Making WordPress.org] #3595: Add link to "Create topic"
 above topic list in support forums
Message-ID: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>

#3595: Add link to "Create topic" above topic list in support forums
----------------------------+--------------------
 Reporter:  tobifjellner    |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+--------------------
 For new users (and not only) it's not always obvious that the form to
 submit a new topic is located much further down on the page. On a
 relatively wide screen, there's a sidebar link ready ''+ Create Topic'',
 but on a narrow screen (like mobile) the sidebar is also located much
 further down the page (when you'd actually need it the most...)

 Suggestion:
 Add the same link **+ Create Topic** just above the topic list.
 And perhaps also on top of every single topic view.

 This small change should give us quite a few less "hi-jacked" threads in
 the forums.

 I'll add a home-cooked mockup.

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

From noreply at wordpress.org  Fri Apr 27 15:18:33 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 27 Apr 2018 15:18:33 -0000
Subject: [wp-meta] [Making WordPress.org] #3595: Add link to "Create
 topic" above topic list in support forums
In-Reply-To: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>
References: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>
Message-ID: <071.62bc5bcdf76b2e2b350c4c11a3e9fe55@wordpress.org>

#3595: Add link to "Create topic" above topic list in support forums
----------------------------+---------------------
 Reporter:  tobifjellner    |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by tobifjellner):

 * Attachment "create-topic.png" added.

 An example what it might be like if we add the link "+ Create Topic" just
 before the topic list.

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

From noreply at wordpress.org  Sat Apr 28 00:21:35 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 00:21:35 -0000
Subject: [wp-meta] [Making WordPress.org] #3595: Add link to "Create
 topic" above topic list in support forums
In-Reply-To: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>
References: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>
Message-ID: <071.22b0c802aaabc8614b02bf33ce151b6a@wordpress.org>

#3595: Add link to "Create topic" above topic list in support forums
----------------------------+---------------------
 Reporter:  tobifjellner    |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by netweb):

 * Attachment "create-topic2.png" added.


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

From noreply at wordpress.org  Sat Apr 28 00:24:20 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 00:24:20 -0000
Subject: [wp-meta] [Making WordPress.org] #3595: Add link to "Create
 topic" above topic list in support forums
In-Reply-To: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>
References: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>
Message-ID: <056.ee0da2f10e815d686538761bb47880ad@wordpress.org>

#3595: Add link to "Create topic" above topic list in support forums
----------------------------+---------------------
 Reporter:  tobifjellner    |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Changes (by netweb):

 * Attachment "create-topic2.png" removed.


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

From noreply at wordpress.org  Sat Apr 28 00:30:04 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 00:30:04 -0000
Subject: [wp-meta] [Making WordPress.org] #3593: Centralize GitHub
 Markdown importer
In-Reply-To: <054.0a678546eed37353565504e6af8f2f5f@wordpress.org>
References: <054.0a678546eed37353565504e6af8f2f5f@wordpress.org>
Message-ID: <069.ee2af339cc9c47e2310c7e1c92fbde59@wordpress.org>

#3593: Centralize GitHub Markdown importer
-------------------------+---------------------
 Reporter:  schlessera   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by netweb):

 Agreed, the Training team have recently migrated their
 [https://github.com/wptrainingteam lesson plans to GitHub] so that the
 100+ lesson plans they have including assets can be under version control.

 At some stage, this content will need to be sync'd back to w.org, more
 than likely to https://learn.wordpress.org/

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

From noreply at wordpress.org  Sat Apr 28 10:23:55 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 28 Apr 2018 10:23:55 +0000 (UTC)
Subject: [wp-meta] [7174]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/rosetta/inc/admin/network/class-locale-associations-view.php:
 Rosetta: Add a list of sites without a locale association to the locale
 associations screen.
Message-ID: <20180428102355.441481B0043E@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr 28 10:36:28 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 10:36:28 -0000
Subject: [wp-meta] [Making WordPress.org] #3596: Sidebar Menu not scrolling
 in small screen size
Message-ID: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>

#3596: Sidebar Menu not scrolling in small screen size
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  (none)
  jitendrabanjara1991    |
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  General      |   Keywords:  needs-patch ux-feedback ui-feedback
                         |  has-screenshots
-------------------------+-------------------------------------------------
 I was checking the development page on my Mobile and I am facing
 difficulty to scroll the menu in the left sidebar.

 Please check the attached screenshot.

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

From noreply at wordpress.org  Sat Apr 28 10:36:39 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 10:36:39 -0000
Subject: [wp-meta] [Making WordPress.org] #3596: Sidebar Menu not
 scrolling in small screen size
In-Reply-To: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
References: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
Message-ID: <078.7062be9602e07c7a6cbb17944d513c54@wordpress.org>

#3596: Sidebar Menu not scrolling in small screen size
-------------------------------------------------+-------------------------
 Reporter:  jitendrabanjara1991                  |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  General                              |  Resolution:
 Keywords:  needs-patch ux-feedback ui-feedback  |
  has-screenshots                                |
-------------------------------------------------+-------------------------
Changes (by jitendrabanjara1991):

 * Attachment "patch.png" added.


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

From noreply at wordpress.org  Sat Apr 28 10:38:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 10:38:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3596: Sidebar Menu not
 scrolling in small screen size
In-Reply-To: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
References: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
Message-ID: <078.348decf0cadd35d836d7ec36b4e289cc@wordpress.org>

#3596: Sidebar Menu not scrolling in small screen size
-------------------------------------------------+-------------------------
 Reporter:  jitendrabanjara1991                  |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  General                              |  Resolution:
 Keywords:  needs-patch ux-feedback ui-feedback  |
  has-screenshots                                |
-------------------------------------------------+-------------------------
Changes (by jitendrabanjara1991):

 * Attachment "3596" added.


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

From noreply at wordpress.org  Sat Apr 28 10:39:24 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 10:39:24 -0000
Subject: [wp-meta] [Making WordPress.org] #3596: Sidebar Menu not
 scrolling in small screen size
In-Reply-To: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
References: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
Message-ID: <078.ea19cad3d42660e65409d9990ac791cd@wordpress.org>

#3596: Sidebar Menu not scrolling in small screen size
-------------------------------------------------+-------------------------
 Reporter:  jitendrabanjara1991                  |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  General                              |  Resolution:
 Keywords:  ux-feedback ui-feedback has-         |
  screenshots has-patch                          |
-------------------------------------------------+-------------------------
Changes (by jitendrabanjara1991):

 * keywords:  needs-patch ux-feedback ui-feedback has-screenshots => ux-
     feedback ui-feedback has-screenshots has-patch


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

From noreply at wordpress.org  Sat Apr 28 10:40:26 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 10:40:26 -0000
Subject: [wp-meta] [Making WordPress.org] #3596: Sidebar Menu not
 scrolling in small screen size
In-Reply-To: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
References: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
Message-ID: <078.2901a0ff7a9691d2e5df40866c6ccc64@wordpress.org>

#3596: Sidebar Menu not scrolling in small screen size
-------------------------------------------------+-------------------------
 Reporter:  jitendrabanjara1991                  |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  General                              |  Resolution:
 Keywords:  ux-feedback ui-feedback has-         |
  screenshots has-patch                          |
-------------------------------------------------+-------------------------
Changes (by jitendrabanjara1991):

 * Attachment "3596.patch" added.


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

From noreply at wordpress.org  Sat Apr 28 11:47:50 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 28 Apr 2018 11:47:50 +0000 (UTC)
Subject: [wp-meta] [7175]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/wporg-gp-plugin-directory/inc/sync/class-translation-sync.php:
 Translate,
 Plugin Directory: Include fuzzy status in check for existing translations
 and clear the cache after a sync.
Message-ID: <20180428114750.E46DF1B0043E@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sat Apr 28 18:22:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 18:22:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3597: Update WordPress.org
 username
Message-ID: <052.094818e8b606ee9f88f494dffcbfc32a@wordpress.org>

#3597: Update WordPress.org username
----------------------+--------------------
 Reporter:  jbpaul17  |      Owner:  (none)
     Type:  task      |     Status:  new
 Priority:  normal    |  Milestone:
Component:  Profiles  |   Keywords:
----------------------+--------------------
 I'd like to update my .ORG username (`@jbpaul17`) so that it will match my
 Slack username (`@jeffpaul`). I’ve noticed a couple Make posts trying to
 ping me but using the “wrong” .ORG username. I’ve checked with the current
 person in possession of the `@jeffpaul` .ORG username and they’re fine to
 hand over to me as they’re otherwise inactive. I’m trying to make it
 easier for people to know how to properly ping me for help or whatever on
 things.

 So, assuming this is feasible, can you please help update the username on
 my account?

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

From noreply at wordpress.org  Sat Apr 28 22:30:59 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 22:30:59 -0000
Subject: [wp-meta] [Making WordPress.org] #3597: Update WordPress.org
 username
In-Reply-To: <052.094818e8b606ee9f88f494dffcbfc32a@wordpress.org>
References: <052.094818e8b606ee9f88f494dffcbfc32a@wordpress.org>
Message-ID: <067.0320db43ca0d441d4c05591eab9d0579@wordpress.org>

#3597: Update WordPress.org username
----------------------+---------------------
 Reporter:  jbpaul17  |       Owner:  (none)
     Type:  task      |      Status:  new
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:
 Keywords:            |
----------------------+---------------------

Comment (by Otto42):

 By and large, that is not possible.

 If you want to stop using jbpaul17 and switch to the new username, then go
 right ahead. If you have the account, then just start using it and stop
 using the old one.

 However, the username on w.org is the same one as used by trac and SVN.
 Basically, you will lose the history there. This ticket was created by
 jbpaul17, it was not created by jeffpaul. Changing the name on w.org
 doesn't change the tickets in trac or the history of the SVN systems.

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

From noreply at wordpress.org  Sat Apr 28 23:23:51 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 28 Apr 2018 23:23:51 -0000
Subject: [wp-meta] [Making WordPress.org] #3596: Sidebar Menu not
 scrolling in small screen size
In-Reply-To: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
References: <063.2c69eb517f13d1b55f225d0c355b0c37@wordpress.org>
Message-ID: <078.a24cb24c693e84602955320218e93d62@wordpress.org>

#3596: Sidebar Menu not scrolling in small screen size
-------------------------------------------------+-------------------------
 Reporter:  jitendrabanjara1991                  |       Owner:  (none)
     Type:  defect                               |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Developer Hub                        |  Resolution:
 Keywords:  ux-feedback ui-feedback has-         |
  screenshots has-patch                          |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * component:  General => Developer Hub


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

From noreply at wordpress.org  Sun Apr 29 13:26:46 2018
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun, 29 Apr 2018 13:26:46 +0000 (UTC)
Subject: [wp-meta] [7176]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Give announce
 to desrosj and allendav in #gdpr-compliance.
Message-ID: <20180429132646.697B01B005A0@svn1.ord.wordpress.org>

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

From noreply at wordpress.org  Sun Apr 29 15:51:54 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 29 Apr 2018 15:51:54 -0000
Subject: [wp-meta] [Making WordPress.org] #3597: Update WordPress.org
 username
In-Reply-To: <052.094818e8b606ee9f88f494dffcbfc32a@wordpress.org>
References: <052.094818e8b606ee9f88f494dffcbfc32a@wordpress.org>
Message-ID: <067.b7ba14b44a7bb912788fb2fdbb964a11@wordpress.org>

#3597: Update WordPress.org username
----------------------+----------------------
 Reporter:  jbpaul17  |       Owner:  (none)
     Type:  task      |      Status:  closed
 Priority:  normal    |   Milestone:
Component:  Profiles  |  Resolution:  wontfix
 Keywords:            |
----------------------+----------------------
Changes (by jbpaul17):

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


Comment:

 Thanks @Otto42, good to understand the options. It'll suck to lose the
 history behind `@jbpau17` but for ease of use between .ORG and Slack I'll
 work on using the `@jeffpaul` account.

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

From noreply at wordpress.org  Mon Apr 30 00:32:56 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 00:32:56 -0000
Subject: [wp-meta] [Making WordPress.org] #3513: FAQ links cause a file
 download dialog with mediawiki blurb within
In-Reply-To: <053.0c5b206fc2f54732cf64c849f6d2de7d@wordpress.org>
References: <053.0c5b206fc2f54732cf64c849f6d2de7d@wordpress.org>
Message-ID: <068.0c346a366180143141550c629ce6ffed@wordpress.org>

#3513: FAQ links cause a file download dialog with mediawiki blurb within
-----------------------+---------------------
 Reporter:  diddledan  |       Owner:  dd32
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  Codex      |  Resolution:  fixed
 Keywords:             |
-----------------------+---------------------
Changes (by dd32):

 * keywords:  pending-systems =>
 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 This has been fixed.

 Re-opening #3591

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

From noreply at wordpress.org  Mon Apr 30 00:33:36 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 00:33:36 -0000
Subject: [wp-meta] [Making WordPress.org] #3591: Codex Main Page -
 Broken Link
In-Reply-To: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>
References: <048.5eaf8d6042295b9fb12e3cd10e78a4b6@wordpress.org>
Message-ID: <063.6c86a0374a8c967272ddff6154c34902@wordpress.org>

#3591: Codex Main Page - Broken Link
--------------------+-----------------------
 Reporter:  xmic    |       Owner:  (none)
     Type:  defect  |      Status:  reopened
 Priority:  normal  |   Milestone:
Component:  Codex   |  Resolution:
 Keywords:          |
--------------------+-----------------------
Changes (by dd32):

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


Comment:

 As per #3513 the `/FAQ` page now works again, and this change should be
 reverted to deliver it to the correct page.

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

From noreply at wordpress.org  Mon Apr 30 00:35:18 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 00:35:18 -0000
Subject: [wp-meta] [Making WordPress.org] #3506: Core SVN commit blocked
 by a pre-commit hook
In-Reply-To: <058.70839433da2709f4c81ee709e46c0391@wordpress.org>
References: <058.70839433da2709f4c81ee709e46c0391@wordpress.org>
Message-ID: <073.0b2e1200b44f9db80a6b8486ca483dc6@wordpress.org>

#3506: Core SVN commit blocked by a pre-commit hook
-----------------------------+---------------------
 Reporter:  SergeyBiryukov   |       Owner:  (none)
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Version Control  |  Resolution:  fixed
 Keywords:                   |
-----------------------------+---------------------
Changes (by dd32):

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


Comment:

 This should've been fixed with the SVN host migration recently - pre-
 commit linting should be now PHP7

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

From noreply at wordpress.org  Mon Apr 30 01:42:07 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 01:42:07 -0000
Subject: [wp-meta] [Making WordPress.org] #3593: Centralize GitHub
 Markdown importer
In-Reply-To: <054.0a678546eed37353565504e6af8f2f5f@wordpress.org>
References: <054.0a678546eed37353565504e6af8f2f5f@wordpress.org>
Message-ID: <069.417b7961b9acf50567dfb492ee7f4cf7@wordpress.org>

#3593: Centralize GitHub Markdown importer
-------------------------+---------------------
 Reporter:  schlessera   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by rmccue):

 Replying to [ticket:3593 schlessera]:
 > @rmccue has already done a lot of preliminary work for making this
 reusable in https://github.com/WP-API/markdown-sync, but some details are
 still missing.

 Happy to give access to this repo if anyone wants to help maintain, or
 move it to a different org if we want it somewhere else

 > Basic functionality could look like the following:
 >
 > 1. Field to enter a markdown source on GitHub. This could be a nice,
 proper UI, but simply accepting a custom field under a common field key
 convention would be enough for an MVP. Something like [https://github.com
 /WP-API/markdown-sync/blob/master/inc/class-importer.php#L17
 wporg_markdown_source] would do the trick.

 Right now, markdown-sync is just a library, so it has no opinions on this.
 In one of the themes I have using it, we've built the ability to supply
 the repo URL into the Customiser; I'm happy to bring this back upstream if
 we want to build this out into more of a plugin.

 I'd rather not allow the per-page meta to be editable, as this meant to be
 controlled by the manifest file instead. You can implement this in another
 plugin atop markdown-sync though, potentially.

 > 2. Refresh button in the post edit screen to fetch the latest version of
 the content from GitHub and make updates as needed.

 I think we may also have code somewhere for this (and API endpoints for
 the same).

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

From noreply at wordpress.org  Mon Apr 30 06:55:03 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 06:55:03 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.0c5828850e478bd6bb09a32b4e5f0f78@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by mindmantra):

 Recently I came across similar situation for https://wordpress.org/plugins
 /debug-bar-super-globals/

 I totally understand points made in ticket:3327#comment:5.

 But it seems there is same weightage applied for ''normal keyword based''
 and ''exact name'' searches. If a search can be determined as exact name
 search then shouldn't be weightage tweaked to find if an exact match
 should be ranked above all or not?

 We could include additional criteria for this such as install base, review
 average; or, to be stricter, installs & reviews in lets say last two major
 releases?

 This needs more thought though. This is an issue worth to look at.

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

From noreply at wordpress.org  Mon Apr 30 07:03:16 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 07:03:16 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.ebb19c771c7fd347aa8077086dcc6cb6@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by Otto42):

 @mindmantra A plugin that has not been updated in 6 years and which is 17
 major versions behind probably should not be at the top of any search
 query, realistically.

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

From noreply at wordpress.org  Mon Apr 30 07:13:59 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 07:13:59 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.061abb1f2ec98c35032e7cf7f99b3275@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------
Changes (by mindmantra):

 * Attachment "Search Results for “Debug Bar Super Globals” — WordPress
 Plugins.png" added.

 Search Results showing results not even related to searched terms

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

From noreply at wordpress.org  Mon Apr 30 07:16:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 07:16:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.b70c5aa9895120dcaa527d5aa92d94db@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by mindmantra):

 @Otto42 You are right. But not every plugin needs to get updated to be
 compatible. Still, I do concur with you on keeping it in check.

 My point above, is more in terms of the general issue and not specific to
 single plugin. I am suggesting that we take in consideration of the recent
 installs and reviews at least in such edge cases.

 My reason being that not every plugin, such as one mentioned above, needs
 to be updated for every release. And with recent install base and/or
 reviews avg would indicate that it is working for people. Not saying that
 this is definitive answer but if good thought is put in it then overall
 search experience would be better for all.

 ''Another issue, which probably should be a separate ticket, is that the
 results which are shown are not at all relavant to keywords. Even the
 plugins in the results have no logical relavance to each other.See
 attachement above.''

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

From noreply at wordpress.org  Mon Apr 30 07:18:53 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 07:18:53 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.8dad6f9088526ae1e128c4caea387e61@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by Otto42):

 If you search for the exact phrase "Debug Bar Super Globals" then the
 plugin you're looking for here is on the second page of results.

 Okay, yes, it's not at the top, but like I said earlier, it probably
 should not be at the top. It is still listed and available though.

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

From noreply at wordpress.org  Mon Apr 30 07:22:21 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 07:22:21 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.2c5dff41db174709afdd4fbd4cadf321@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by danieltj):

 Is there a way the search query can be 'slugified'? In @magicroundabout
 case, he mentioned searching for 'WP Help'. That's quite an easy example
 where you could change that into a slug, so `wp-help` and then try and
 match plugin slugs first perhaps? Or give more weight to exact matches?

 I myself try and search for my own plugins and decided to just favourite
 them as it's easier using the favourites tab instead because Unlist My
 Post (an exact match for the plugin title) doesn't seem to appear high
 enough when unrelated plugins seems to appear. I think the slug searches
 would go along way to helping sort this issue.

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

From noreply at wordpress.org  Mon Apr 30 08:41:50 2018
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 30 Apr 2018 08:41:50 -0000
Subject: [wp-meta] [Making WordPress.org] #3327: Searching with exact
 plugin name has it on page 3 of results
In-Reply-To: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
References: <059.b9c0c002c66e9440f618570810fa28ea@wordpress.org>
Message-ID: <074.7967f68694a7929187c8d3ccab090e92@wordpress.org>

#3327: Searching with exact plugin name has it on page 3 of results
------------------------------+----------------------
 Reporter:  garrett-eclipse   |       Owner:  (none)
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  invalid
 Keywords:                    |
------------------------------+----------------------

Comment (by magicroundabout):

 @danieltj I'd say it's massively user-unfriendly to have to have a guess
 at a slug in order to find and install a plugin that you know exists.

 @Otto42 I actually disagree. Well, partly. If I know the name of a plugin
 that I want to install, I should be able to install it with little hassle
 or effort. Its age or declared compatibility is not always a measure of
 its (lack of) quality.

 I totally understand why you don't want to surface these old plugins. My
 previous suggestion to "show incompatible/old plugins" stands.  I hold
 that people should be able to easily find and install a plugin by name.

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