From noreply at wordpress.org  Sat Oct  1 00:01:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 00:01:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2054: Forums: Missing i18n in
 wporg-forums theme
In-Reply-To: <058.f40ffbd4acce743ca5406e0ef864ea9d@wordpress.org>
References: <058.f40ffbd4acce743ca5406e0ef864ea9d@wordpress.org>
Message-ID: <073.9ac1d943bad3700565ce295528837ded@wordpress.org>

#2054: Forums: Missing i18n in wporg-forums theme
------------------------------+---------------------
 Reporter:  SergeyBiryukov    |       Owner:  netweb
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  buddypress.org    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+---------------------

Comment (by SergeyBiryukov):

 Follow-up: #2102

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

From noreply at wordpress.org  Sat Oct  1 10:55:54 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 10:55:54 -0000
Subject: [wp-meta] [Making WordPress.org] #2103: Codexify strips spaces in
	titles
Message-ID: <051.ab6265caf992d69d7a90427eec598ef7@wordpress.org>

#2103: Codexify strips spaces in titles
----------------------------+-------------------------
 Reporter:  ocean90         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch
----------------------------+-------------------------
 Report: https://wordpress.org/support/topic/forum-bugs-and-broken-
 things/#post-8240018

 > It appears the forum?s double bracket Codex link shortcut is stripping
 spaces instead of replacing with underscores. When I do `[[Hardening
 WordPress]]` the link becomes codex.wordpress.org/HardeningWordPress which
 is missing the underscore that used to be inserted for the space.


 Input: `[[Hardening WordPress]]`
 Actual output: `<a href="https://codex.wordpress.org/HardeningWordPress"
 rel="nofollow">HardeningWordPress</a>`
 Expected output: `<a
 href="https://codex.wordpress.org/Hardening_WordPress"
 rel="nofollow">Hardening WordPress</a>`

 Plugin:
 https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/plugins/wporg-bbp-codexify

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

From noreply at wordpress.org  Sat Oct  1 12:10:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 12:10:25 -0000
Subject: [wp-meta] [Making WordPress.org] #2103: Codexify strips spaces
	in titles
In-Reply-To: <051.ab6265caf992d69d7a90427eec598ef7@wordpress.org>
References: <051.ab6265caf992d69d7a90427eec598ef7@wordpress.org>
Message-ID: <066.685a68834b6d11a0e69e3960f649c1a1@wordpress.org>

#2103: Codexify strips spaces in titles
------------------------------+------------------
 Reporter:  ocean90           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------
Changes (by SergeyBiryukov):

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


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

From noreply at wordpress.org  Sat Oct  1 13:41:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 13:41:53 -0000
Subject: [wp-meta] [Making WordPress.org] #1561: Messages caught in the
 moderation queue need visual feedback
In-Reply-To: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
References: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
Message-ID: <073.936f86d79ae8e5150a0b46a3cd72ace2@wordpress.org>

#1561: Messages caught in the moderation queue need visual feedback
------------------------------+------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------
Changes (by SergeyBiryukov):

 * keywords:   => has-patch commit


Comment:

 [attachment:meta-1561.patch] implements comment:4, see
 [attachment:meta-1561.PNG].

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

From noreply at wordpress.org  Sat Oct  1 14:58:17 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 14:58:17 -0000
Subject: [wp-meta] [Making WordPress.org] #2104: Forums: Misaligned Reply
 link on RTL forums
Message-ID: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>

#2104: Forums: Misaligned Reply link on RTL forums
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 As seen on https://he.wordpress.org/support/topic/?????-??-??-??????-????-
 ?????-?/.

 See the screenshot.

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

From noreply at wordpress.org  Sat Oct  1 14:59:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 14:59:12 -0000
Subject: [wp-meta] [Making WordPress.org] #1903: Hardcoded strings in
 WordCamp.org plugin camptix-attendance
In-Reply-To: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
References: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
Message-ID: <067.a98f411543aa0269dd74831fe71d99d5@wordpress.org>

#1903: Hardcoded strings in WordCamp.org plugin camptix-attendance
-------------------------------------+------------------------
 Reporter:  kossmann                 |       Owner:  kovshenin
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+------------------------

Comment (by kossmann):

 Hi, is everything OK with my changes? Should I do something else?

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

From noreply at wordpress.org  Sat Oct  1 15:08:28 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 15:08:28 -0000
Subject: [wp-meta] [Making WordPress.org] #1903: Hardcoded strings in
 WordCamp.org plugin camptix-attendance
In-Reply-To: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
References: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
Message-ID: <067.2360c9137555d865654dbb38dfd89c3a@wordpress.org>

#1903: Hardcoded strings in WordCamp.org plugin camptix-attendance
-------------------------------------+------------------------
 Reporter:  kossmann                 |       Owner:  kovshenin
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+------------------------

Comment (by SergeyBiryukov):

 I think `<strong>Note</strong>: Anyone with the secret link can access the
 attendance UI...` should be a single string rather than two separate
 strings (`Note:` and `Anyone with the secret link...`).

 Looks good to me otherwise.

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

From noreply at wordpress.org  Sat Oct  1 16:01:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 01 Oct 2016 16:01:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2103: Codexify strips spaces
	in titles
In-Reply-To: <051.ab6265caf992d69d7a90427eec598ef7@wordpress.org>
References: <051.ab6265caf992d69d7a90427eec598ef7@wordpress.org>
Message-ID: <066.9a98c9b1e7618cfa41aafaaee499cf27@wordpress.org>

#2103: Codexify strips spaces in titles
------------------------------+---------------------
 Reporter:  ocean90           |       Owner:  jmdodd
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+---------------------
Changes (by jmdodd):

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


Comment:

 In [changeset:"4175"]:
 {{{
 #!CommitTicketReference repository="" revision="4175"
 Support Forums: Replace spaces with underscores in Codex link shortcut.

 Codex link shortcuts were incorrectly stripping spaces from the link and
 title rather than replacing them with an underscore.

 Props SergeyBiryukov.
 Fixes #2103.
 }}}

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

From noreply at wordpress.org  Sat Oct  1 16:01:55 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  1 Oct 2016 16:01:55 +0000 (UTC)
Subject: [wp-meta] [4175]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-bbp-codexify/wporg-bbp-codexify.php: Support Forums: Replace spaces
 with underscores in Codex link shortcut.
Message-ID: <20161001160155.338821080270@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct  1 21:15:34 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  1 Oct 2016 21:15:34 +0000 (UTC)
Subject: [wp-meta] [4176]
 sites/trunk/api.wordpress.org/public_html/translations/lib.php:
 Translations API: Fix English name of the `de_CH_informal` locale.
Message-ID: <20161001211534.3CCF41080270@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct  2 12:53:35 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 02 Oct 2016 12:53:35 -0000
Subject: [wp-meta] [Making WordPress.org] #1910: An emoji in the title
 of a plugin review doesn't render and affects comment link
In-Reply-To: <051.d1a3435943b30241437c8013349845cf@wordpress.org>
References: <051.d1a3435943b30241437c8013349845cf@wordpress.org>
Message-ID: <066.028b1ad5cf2418bc321ca7314ed5269e@wordpress.org>

#1910: An emoji in the title of a plugin review doesn't render and affects comment
link
----------------------------+---------------------
 Reporter:  Shelob9         |       Owner:
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by SergeyBiryukov):

 * component:  General => Support Forums


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

From noreply at wordpress.org  Sun Oct  2 17:38:30 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  2 Oct 2016 17:38:30 +0000 (UTC)
Subject: [wp-meta] [4177]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/ wordcamp-docs:
 WordCamp Docs: Add two new visa templates to the docs generator.
Message-ID: <20161002173830.0548910802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct  2 18:34:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 02 Oct 2016 18:34:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2065: Add year to dates on
 http://central.wordcamp.org/schedule/
In-Reply-To: <059.ac3962f242437219871b68a88feac608@wordpress.org>
References: <059.ac3962f242437219871b68a88feac608@wordpress.org>
Message-ID: <074.44a4293fa6ac72345667c740c70058ec@wordpress.org>

#2065: Add year to dates on http://central.wordcamp.org/schedule/
--------------------------------------+-----------------------
 Reporter:  andreamiddleton           |       Owner:  iandunn
     Type:  enhancement               |      Status:  accepted
 Priority:  low                       |   Milestone:
Component:  WordCamp Site & Plugins   |  Resolution:
 Keywords:  good-first-bug has-patch  |
--------------------------------------+-----------------------
Changes (by frq):

 * keywords:  needs-patch good-first-bug => good-first-bug has-patch


Comment:

 This is the first time submitting a patch, so forgive if I am doing
 something wrong.

 Although I doubt there will be a WordCamp with different start and end
 years, I left the possibility, just like there is one for months.

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

From noreply at wordpress.org  Sun Oct  2 19:47:48 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  2 Oct 2016 19:47:48 +0000 (UTC)
Subject: [wp-meta] [4178]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-gp-customizations/templates: Translate: Update templates for
 GlotPress 2.2.
Message-ID: <20161002194748.077FE1080224@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct  2 20:09:36 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  2 Oct 2016 20:09:36 +0000 (UTC)
Subject: [wp-meta] [4179]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-gp-customizations/templates: Translate: Don' t call `clone` if the
 locale doesn't exist.
Message-ID: <20161002200936.BD53F10802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct  2 20:44:07 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  2 Oct 2016 20:44:07 +0000 (UTC)
Subject: [wp-meta] [4180]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-gp-routes/inc/routes/class-stats.php: Translate,
 Stats Overview:  Limit number of WordPress projects to a maximum of three.
Message-ID: <20161002204407.9EF5A10802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct  2 21:04:18 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 02 Oct 2016 21:04:18 -0000
Subject: [wp-meta] [Making WordPress.org] #2097: Disable oEmbed displays
 on the forums
In-Reply-To: <051.1ea881aab1cec942e57bd6dd25b4dafe@wordpress.org>
References: <051.1ea881aab1cec942e57bd6dd25b4dafe@wordpress.org>
Message-ID: <066.70a0cb14269f4693914cd9b2d9e30762@wordpress.org>

#2097: Disable oEmbed displays on the forums
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by ocean90):

 In [changeset:"4181"]:
 {{{
 #!CommitTicketReference repository="" revision="4181"
 Support Forums: Disable `<link>` tag discovery for oEmbed.

 See #2097.
 }}}

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

From noreply at wordpress.org  Sun Oct  2 21:04:18 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun,  2 Oct 2016 21:04:18 +0000 (UTC)
Subject: [wp-meta] [4181]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-hooks.php: Support Forums: Disable `<link> ` tag
 discovery for oEmbed.
Message-ID: <20161002210418.308DF10802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct  3 12:34:38 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Oct 2016 12:34:38 +0000 (UTC)
Subject: [wp-meta] [4182]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/widgets/class-meta.php: Plugin Directory: Fix typo in
 singular form of "Tag".
Message-ID: <20161003123438.1623B10802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct  3 12:48:11 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 12:48:11 -0000
Subject: [wp-meta] [Making WordPress.org] #1654: Allow import of
 translations as waiting
In-Reply-To: <049.eb089ab177c0e591e07d6ea3d1f98eaa@wordpress.org>
References: <049.eb089ab177c0e591e07d6ea3d1f98eaa@wordpress.org>
Message-ID: <064.ec0a2900b918832f610f09f29d208ea1@wordpress.org>

#1654: Allow import of translations as waiting
--------------------------------------+------------------
 Reporter:  akirk                     |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  has-patch                 |
--------------------------------------+------------------

Comment (by ocean90):

 [attachment:1654.3.diff] allows all users to import plugin/theme
 translations as waiting. @akirk, can I get a sanity check on
 [attachment:1654.3.diff]?

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

From noreply at wordpress.org  Mon Oct  3 13:11:54 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 13:11:54 -0000
Subject: [wp-meta] [Making WordPress.org] #1654: Allow import of
 translations as waiting
In-Reply-To: <049.eb089ab177c0e591e07d6ea3d1f98eaa@wordpress.org>
References: <049.eb089ab177c0e591e07d6ea3d1f98eaa@wordpress.org>
Message-ID: <064.59cd9d01e92c66ad21cbb2a6dfd0b99f@wordpress.org>

#1654: Allow import of translations as waiting
--------------------------------------+------------------
 Reporter:  akirk                     |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  has-patch                 |
--------------------------------------+------------------

Comment (by akirk):

 The diff looks good! The only thing I noticed is that PTEs and GTEs won't
 be able to import as waiting on projects other than plugins or themes. But
 I understand this is intentional for now.

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

From noreply at wordpress.org  Mon Oct  3 14:05:43 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon,  3 Oct 2016 14:05:43 +0000 (UTC)
Subject: [wp-meta] [4183]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-gp-rosetta-roles/inc/class-plugin.php: Translate,
 Rosetta Roles: Allow import of translations as waiting for plugins and
 themes.
Message-ID: <20161003140543.2515D10802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct  3 14:05:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 14:05:43 -0000
Subject: [wp-meta] [Making WordPress.org] #1654: Allow import of
 translations as waiting
In-Reply-To: <049.eb089ab177c0e591e07d6ea3d1f98eaa@wordpress.org>
References: <049.eb089ab177c0e591e07d6ea3d1f98eaa@wordpress.org>
Message-ID: <064.f0808acc266b688f6e333ae121d0d665@wordpress.org>

#1654: Allow import of translations as waiting
--------------------------------------+------------------
 Reporter:  akirk                     |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  has-patch                 |
--------------------------------------+------------------

Comment (by ocean90):

 In [changeset:"4183"]:
 {{{
 #!CommitTicketReference repository="" revision="4183"
 Translate, Rosetta Roles: Allow import of translations as waiting for
 plugins and themes.

 A PTE/GTE can import translations as waiting for all projects, logged in
 users only for plugins and themes.

 Props akirk, ocean90.
 See #1654.
 }}}

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

From noreply at wordpress.org  Mon Oct  3 14:41:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 14:41:27 -0000
Subject: [wp-meta] [Making WordPress.org] #1903: Hardcoded strings in
 WordCamp.org plugin camptix-attendance
In-Reply-To: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
References: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
Message-ID: <067.44c15731298cff7e21207b6815ff19c9@wordpress.org>

#1903: Hardcoded strings in WordCamp.org plugin camptix-attendance
-------------------------------------+------------------------
 Reporter:  kossmann                 |       Owner:  kovshenin
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+------------------------

Comment (by kossmann):

 Done!

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

From noreply at wordpress.org  Mon Oct  3 18:02:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 18:02:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2105: Feature Request: Introduce
 Search for plugin specific issues
Message-ID: <059.fa89a57b0ca98ee76a84a835494a276e@wordpress.org>

#2105: Feature Request: Introduce Search for plugin specific issues
-----------------------------+-----------------
 Reporter:  garrett-eclipse  |      Owner:
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:
Component:  Support Forums   |   Keywords:
-----------------------------+-----------------
 Hello,

 I'd like to request a feature to make mine and I'm sure many peoples lives
 easier.

 I often use Google to search issues, but it would be nice if I could
 search for issues on a spefici plugin from within it's support section;
 https://wordpress.org/support/plugin/nextgen-gallery

 This search would only go through topics posted to that specific plugins
 thread.

 Thank you

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

From noreply at wordpress.org  Mon Oct  3 18:06:28 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 18:06:28 -0000
Subject: [wp-meta] [Making WordPress.org] #2105: Feature Request:
 Introduce Search for plugin specific issues
In-Reply-To: <059.fa89a57b0ca98ee76a84a835494a276e@wordpress.org>
References: <059.fa89a57b0ca98ee76a84a835494a276e@wordpress.org>
Message-ID: <074.15470e62d4f70fd8ebd0755209fcb70b@wordpress.org>

#2105: Feature Request: Introduce Search for plugin specific issues
-----------------------------+------------------------
 Reporter:  garrett-eclipse  |       Owner:
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Support Forums   |  Resolution:  duplicate
 Keywords:                   |
-----------------------------+------------------------
Changes (by Otto42):

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


Comment:

 Duplicate of #7.

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

From noreply at wordpress.org  Mon Oct  3 20:43:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 03 Oct 2016 20:43:50 -0000
Subject: [wp-meta] [Making WordPress.org] #1708: "Project-Id-Version"
 should contain plugin name
In-Reply-To: <047.1e8c0ee75693502bb522338c3dac5fea@wordpress.org>
References: <047.1e8c0ee75693502bb522338c3dac5fea@wordpress.org>
Message-ID: <062.af73aba433f7e65e16c2141220aedecb@wordpress.org>

#1708: "Project-Id-Version" should contain plugin name
--------------------------------------+----------------------
 Reporter:  jrf                       |       Owner:
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  invalid
 Keywords:  needs-patch upstream      |
--------------------------------------+----------------------
Changes (by ocean90):

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


Comment:

 Closing as invalid since it was changed in GlotPress directly.

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

From noreply at wordpress.org  Tue Oct  4 02:22:18 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 02:22:18 -0000
Subject: [wp-meta] [Making WordPress.org] #2106: WordPress.tv: Filter
 intended to prevent orphaned words creates them
Message-ID: <058.827e65da2fb5f1f45f0c95d298a5eb35@wordpress.org>

#2106: WordPress.tv: Filter intended to prevent orphaned words creates them
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  WordPress.tv    |   Keywords:
----------------------------+-----------------
 On WordPress.tv, there's a code that adds `&nbsp;` before the last word in
 video titles.

 I could not find it in the open sourced theme, but I guess it's similar to
 `rosetta_orphan_control()` in Rosetta:
 {{{
 /**
  * Makes final space a non-breaking one, to prevent orphaned word.
  *
  * @param string $string
  * @return string
  */
 function rosetta_orphan_control( $string ) {
         return substr_replace( $string, '&nbsp;', strrpos( $string, ' ' ),
 1 );
 }
 add_filter( 'no_orphans', 'rosetta_orphan_control' );
 }}}

 The problem is that it doesn't work well for languages with longer words,
 see the screenshot.

 As seen on http://wordpress.tv/event/wordcamp-moscow-2016/, this title
 does not wrap correctly with `&nbsp;`:
 {{{
 ??????? ????????: ??? ????? ?????????&nbsp;??????????
 }}}

 The function should probably only replace spaces preceded by shorter words
 (1 to 3 letters or so).

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

From noreply at wordpress.org  Tue Oct  4 04:10:21 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 04:10:21 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.1a571df2b6a9249d286e487cc197b957@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by jmdodd):

 In [changeset:"4184"]:
 {{{
 #!CommitTicketReference repository="" revision="4184"
 Support Forums: Add plugin-committer view and feed.

 See #2071.
 }}}

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

From noreply at wordpress.org  Tue Oct  4 04:10:20 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Oct 2016 04:10:20 +0000 (UTC)
Subject: [wp-meta] [4184]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums: Add
 plugin-committer view and feed.
Message-ID: <20161004041020.A5F2E1080433@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct  4 04:37:04 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Oct 2016 04:37:04 +0000 (UTC)
Subject: [wp-meta] [4185]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums: Unlimit
 plugin-committer query in production.
Message-ID: <20161004043704.219231080433@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct  4 08:26:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 08:26:25 -0000
Subject: [wp-meta] [Making WordPress.org] #2107: Prevent posting 10k lines
 of logs in replies, recommend Pastebin or GitHub gists
Message-ID: <051.e9dd8e784c0bf6431049f4ff7e210453@wordpress.org>

#2107: Prevent posting 10k lines of logs in replies, recommend Pastebin or GitHub
gists
----------------------------+-----------------
 Reporter:  ocean90         |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  low             |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 To provide debugging information some users post their full logs in a
 reply. These can be up to 10k lines which makes reading the page really
 annoying because you have to scroll like 5 minutes.

 Examples:
 *
 https://wordpress.org/support/topic/qtranslate-x-compatibility-2/#post-8250157
 * https://wordpress.org/support/topic/no-confirmation-email-
 received-2/#post-8235539

 I suggest to prevent posting replies which have more than X
 chars/words/lines and to recommend using a service like Pastebin or GitHub
 gists.

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

From noreply at wordpress.org  Tue Oct  4 10:20:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 10:20:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2104: Forums: Misaligned
 Reply link on RTL forums
In-Reply-To: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
References: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
Message-ID: <073.4d35897da5a78d4b5ffa385dc0d76df5@wordpress.org>

#2104: Forums: Misaligned Reply link on RTL forums
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------
Changes (by netweb):

 * keywords:   => has-patch


Comment:

 Patch [attachment:meta-2104.patch] is RTL equivalent of
 [https://meta.trac.wordpress.org/browser/sites/trunk/buddypress.org/public_html
 /wp-content/themes/bb-base/style.css?marks=1180-1186#L1180 /bb-
 base/style.css?marks=1180-1186#L1180]

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

From noreply at wordpress.org  Tue Oct  4 10:47:59 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Oct 2016 10:47:59 +0000 (UTC)
Subject: [wp-meta] [4186]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Add
 johnbillion to the announce whitelist for the #feature-notifications
 channel.
Message-ID: <20161004104759.0E1C710802F6@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct  4 11:21:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 11:21:50 -0000
Subject: [wp-meta] [Making WordPress.org] #2102: Missing i18n in bb-base
	theme
In-Reply-To: <058.a89ea38c205dad7ebd7442aff5180413@wordpress.org>
References: <058.a89ea38c205dad7ebd7442aff5180413@wordpress.org>
Message-ID: <073.b1ecfd81065500e13e4b8e3b9a984159@wordpress.org>

#2102: Missing i18n in bb-base theme
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  bbpress.org     |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------
Changes (by netweb):

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


Comment:

 Updated [attachment:meta-2102.2.patch] to use the `bborg` text domain as
 noted [https://meta.trac.wordpress.org/ticket/2054#comment:1
 2054#comment:1]

 Replying to [comment:1 netweb]:
 >
 > #1284 BuddyPress.org - String localization
 > #1285 bbPress.org - String localization
 >
 > Shared "bb-base" common components should be: `bborg`
 > bbPress plugins, theme, and codex theme should be: `bbporg`
 > BuddyPress plugins, theme, and codex theme should be: `bpporg`

 Will refresh #1284 and #1285 and commit all 3 tickets together soon.

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

From noreply at wordpress.org  Tue Oct  4 12:27:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 12:27:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2101: Forums:
 Spam/Pending/Archived views should display topic titles
In-Reply-To: <058.5afb3a9b1f90b5117ed8ae807d3afbd6@wordpress.org>
References: <058.5afb3a9b1f90b5117ed8ae807d3afbd6@wordpress.org>
Message-ID: <073.897547501fb53994d2765f01b114cdca@wordpress.org>

#2101: Forums: Spam/Pending/Archived views should display topic titles
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------
Changes (by netweb):

 * keywords:   => has-patch


Comment:

 Patch [attachment:meta-2101.patch] adds topic and reply headers based on
 #2002 for the spam, pending, and archive views:

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

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

From noreply at wordpress.org  Tue Oct  4 12:42:45 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Oct 2016 12:42:45 +0000 (UTC)
Subject: [wp-meta] [4187]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-gp-customizations/templates: Translate: Show a notice for inactive
 projects.
Message-ID: <20161004124245.0FE8F10802F6@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct  4 12:46:59 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue,  4 Oct 2016 12:46:59 +0000 (UTC)
Subject: [wp-meta] [4188]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-gp-plugin-directory/inc: Translate,
 Plugin Directory: Add CLI command to update active status of plugin
 projects.
Message-ID: <20161004124659.E222C10802F6@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct  4 20:35:56 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 20:35:56 -0000
Subject: [wp-meta] [Making WordPress.org] #2108: Create a routine for update
 the language packages for WordCamps sites
Message-ID: <058.c5f87af0cc881c3a996bce53d7adb197@wordpress.org>

#2108: Create a routine for update the language packages for WordCamps sites
-------------------------------------+-----------------
 Reporter:  claudiosanches           |      Owner:
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+-----------------
 Don't looks like that have anything able to update automatically the
 translations of the WordCamps sites.

 I helped translate all string for pt_BR on April, but no one updated the
 translations in the WordCamp sites, not even after some organizers ask for
 it, so in this time we had 3 WordCamps half translated... And only now
 after weeks requesting for update the translations that we could have our
 first WordCamp site in Brazil with all translated.
 So it's clear that the process is manually and it should be improved, at
 least update once a month, but need to some automatic routine to updated
 it.

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

From noreply at wordpress.org  Tue Oct  4 21:02:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 21:02:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2108: Create a routine for
 update the language packages for WordCamps sites
In-Reply-To: <058.c5f87af0cc881c3a996bce53d7adb197@wordpress.org>
References: <058.c5f87af0cc881c3a996bce53d7adb197@wordpress.org>
Message-ID: <073.0cfc9f81f6675364986f025db58a66a6@wordpress.org>

#2108: Create a routine for update the language packages for WordCamps sites
-------------------------------------+------------------
 Reporter:  claudiosanches           |       Owner:
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+------------------

Comment (by ocean90):

 Based on [https://meta.trac.wordpress.org/ticket/1076#comment:15 this
 comment] this should now happen.

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

From noreply at wordpress.org  Tue Oct  4 21:56:37 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 21:56:37 -0000
Subject: [wp-meta] [Making WordPress.org] #2110: Forums: Wrong page number
 in some reply links
Message-ID: <058.8494a61fcda1c27774f171dad62c5eb8@wordpress.org>

#2110: Forums: Wrong page number in some reply links
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 1. Open this reply: [[BR]]
  https://wordpress.org/support/topic/after-update-to-46-keep-getting-curl-
 error-23/page/2/#post-7680728.
 2. The next reply on the same page suddenly has `/page/3/` instead of
 `/page/2/`: [[BR]]
  https://wordpress.org/support/topic/after-update-to-46-keep-getting-curl-
 error-23/page/3/#post-8157376

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

From noreply at wordpress.org  Tue Oct  4 21:52:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 21:52:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2109: Forums: Incorrect data in
	Forum Info
Message-ID: <058.94d1352080c47e4bebdd1555a548fe02@wordpress.org>

#2109: Forums: Incorrect data in Forum Info
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 Might be a duplicate of #1971 or #2043 or a known caching issue, but the
 sidebar info on https://wordpress.org/support/forum/plugins-and-hacks/
 looks wrong:

 * `836,866 topics (+ -541 hidden)` (note the negative value)
 * `Last activity: 4 months, 1 week ago` (the last activity was 2 minutes
 ago)

 See the screenshot.

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

From noreply at wordpress.org  Tue Oct  4 22:50:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 04 Oct 2016 22:50:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2108: Create a routine for
 update the language packages for WordCamps sites
In-Reply-To: <058.c5f87af0cc881c3a996bce53d7adb197@wordpress.org>
References: <058.c5f87af0cc881c3a996bce53d7adb197@wordpress.org>
Message-ID: <073.286df85d77290a21807462a0c9a224de@wordpress.org>

#2108: Create a routine for update the language packages for WordCamps sites
-------------------------------------+------------------------
 Reporter:  claudiosanches           |       Owner:
     Type:  defect                   |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  duplicate
 Keywords:                           |
-------------------------------------+------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Duplicate of #1076.

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

From noreply at wordpress.org  Wed Oct  5 09:21:07 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 09:21:07 -0000
Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the
 registration page
In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org>
References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org>
Message-ID: <066.6f8f64cfc32fa7ee22b0c169b8b8912a@wordpress.org>

#148: Restyle/redesign the registration page
-------------------------------------+------------------------
 Reporter:  j.conti                  |       Owner:
     Type:  task                     |      Status:  reviewing
 Priority:  high                     |   Milestone:
Component:  Login & Authentication   |  Resolution:
 Keywords:  ui-feedback needs-patch  |
-------------------------------------+------------------------

Comment (by ocean90):

 Replying to [comment:18 melchoyce]:

 > If we redirected people to their profiles after registration (not sure
 what we do now) we could prompt them to fill in more information and keep
 the initial form a little shorter? I agree it's pretty long.

 That might be possible. I created a few screenshots of the current
 registration flow (which is so bad in many points):
 https://cloudup.com/c_3-CLuIVzL

 @mapk Concept 2 seems to be the way to go, maybe without the profile
 information section. How should we display error messages? That's what
 WordPress does: https://cloudup.com/cSPVngF3NkH

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

From noreply at wordpress.org  Wed Oct  5 11:29:13 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed,  5 Oct 2016 11:29:13 +0000 (UTC)
Subject: [wp-meta] [4189]
 sites/trunk/common/includes/wporg-sso/wp-plugin.php: WordPress.org SSO:
 Filter register URL and login post URL to use login.wordpress.org.
Message-ID: <20161005112913.6632510802B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct  5 12:22:17 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 12:22:17 -0000
Subject: [wp-meta] [Making WordPress.org] #1995: Incomplete Redirect URL
 coming from translate.wordpress.org
In-Reply-To: <051.af6e78942c7cd6e4408fb094ffa384f0@wordpress.org>
References: <051.af6e78942c7cd6e4408fb094ffa384f0@wordpress.org>
Message-ID: <066.a6eb799011f55b9dbf3d0b4596ec155d@wordpress.org>

#1995: Incomplete Redirect URL coming from translate.wordpress.org
--------------------------------------+---------------------
 Reporter:  DeFries                   |       Owner:
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------
Changes (by ocean90):

 * keywords:  needs-patch =>
 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in [4178] and https://github.com/GlotPress/GlotPress-WP/issues/558.

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

From noreply at wordpress.org  Wed Oct  5 18:24:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 18:24:44 -0000
Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the
 registration page
In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org>
References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org>
Message-ID: <066.ff6d73e11b5617bce1efe3b7e6242330@wordpress.org>

#148: Restyle/redesign the registration page
-------------------------------------+------------------------
 Reporter:  j.conti                  |       Owner:
     Type:  task                     |      Status:  reviewing
 Priority:  high                     |   Milestone:
Component:  Login & Authentication   |  Resolution:
 Keywords:  ui-feedback needs-patch  |
-------------------------------------+------------------------

Comment (by mapk):

 Replying to [comment:19 ocean90]:
 > Replying to [comment:18 melchoyce]:
 >
 > > If we redirected people to their profiles after registration (not sure
 what we do now) we could prompt them to fill in more information and keep
 the initial form a little shorter? I agree it's pretty long.
 >
 > That might be possible. I created a few screenshots of the current
 registration flow (which is so bad in many points):
 https://cloudup.com/c_3-CLuIVzL

 I like this idea of cutting it down and pushing the user to their profile
 page. Here's the form without the Profile info.
 [[Image(https://cldup.com/21DzoDp8BZ.png)]]


 >
 > @mapk Concept 2 seems to be the way to go, maybe without the profile
 information section. How should we display error messages? That's what
 WordPress does: https://cloudup.com/cSPVngF3NkH

 Keeping the same error pattern is good. Here is an idea incorporating
 @melchoyce's error example from above. It's just a thicker border and in
 red. I understand that some users might be colorblind, but the weight of
 the border and error msg above should be enough to indicate the problem
 and where it is. I wouldn't mind adding an error icon next to the input
 field, but am unsure the structure of the markup allows for that (it may
 not even allow the border change as it is).

 If we do add in an input change on error, we should make sure that pattern
 gets carried over to the login and forgot password pages as well.

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

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

From noreply at wordpress.org  Wed Oct  5 20:52:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 20:52:03 -0000
Subject: [wp-meta] [Making WordPress.org] #1903: Hardcoded strings in
 WordCamp.org plugin camptix-attendance
In-Reply-To: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
References: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
Message-ID: <067.b0991e07a48bde40fcac915c11b59f48@wordpress.org>

#1903: Hardcoded strings in WordCamp.org plugin camptix-attendance
-------------------------------------+-----------------------
 Reporter:  kossmann                 |       Owner:  iandunn
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+-----------------------
Changes (by iandunn):

 * owner:  kovshenin => iandunn


Comment:

 It looks like `Note` isn't a separate string in `3.diff`, but I can make
 that change when I commit it. The rest looks good to me.

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

From noreply at wordpress.org  Wed Oct  5 20:53:01 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 20:53:01 -0000
Subject: [wp-meta] [Making WordPress.org] #1903: Hardcoded strings in
 WordCamp.org plugin camptix-attendance
In-Reply-To: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
References: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
Message-ID: <067.ad6bb00976a6ed85e17a275f1d33a13d@wordpress.org>

#1903: Hardcoded strings in WordCamp.org plugin camptix-attendance
-------------------------------------+-----------------------
 Reporter:  kossmann                 |       Owner:  iandunn
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+-----------------------

Comment (by iandunn):

 Er, nevermind, I misread Sergey's comment. `3.diff` is correct.

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

From noreply at wordpress.org  Wed Oct  5 21:02:30 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 21:02:30 -0000
Subject: [wp-meta] [Making WordPress.org] #1903: Hardcoded strings in
 WordCamp.org plugin camptix-attendance
In-Reply-To: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
References: <052.d0d3b01d9843e1829ed43e09e216b72d@wordpress.org>
Message-ID: <067.423a71f8833774103f99fd5178acc82e@wordpress.org>

#1903: Hardcoded strings in WordCamp.org plugin camptix-attendance
-------------------------------------+-----------------------
 Reporter:  kossmann                 |       Owner:  iandunn
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+-----------------------

Comment (by SergeyBiryukov):

 [attachment:1903.diff] makes the whole string bold, I didn't mean that :)

 I just meant the string can be wrapped with `esc_html_e()` as is, no need
 to separate it. Occasional HTML tags in translatable strings are fine,
 unless thay wrap the whole string or placeholders (e.g.
 `<code>%s</code>`), in which case they can be moved out of the string.

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

From noreply at wordpress.org  Wed Oct  5 21:07:22 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 21:07:22 -0000
Subject: [wp-meta] [Making WordPress.org] #2065: Add year to dates on
 http://central.wordcamp.org/schedule/
In-Reply-To: <059.ac3962f242437219871b68a88feac608@wordpress.org>
References: <059.ac3962f242437219871b68a88feac608@wordpress.org>
Message-ID: <074.fdaf3b28f438db4b1f3d8adbbf3325a3@wordpress.org>

#2065: Add year to dates on http://central.wordcamp.org/schedule/
--------------------------------------+-----------------------
 Reporter:  andreamiddleton           |       Owner:  iandunn
     Type:  enhancement               |      Status:  accepted
 Priority:  low                       |   Milestone:
Component:  WordCamp Site & Plugins   |  Resolution:
 Keywords:  good-first-bug has-patch  |
--------------------------------------+-----------------------

Comment (by iandunn):

 The patch looks great, thanks @frq!

 I'd make two suggestions to improve it:

 1) `the_wordcamp_date()` is called by multiple templates, so adding the
 year unconditionally will create side-effects for them. One way to avoid
 that would be by adding a `$year` parameter that defaults to `'excluded'`.
 If `'included'` is passed, then the year is shown.

 2) Add a header for each year, similar to the Past WordCamps template. You
 can use `group_wordcamps_by_year()` to make that easier.

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

From noreply at wordpress.org  Wed Oct  5 22:50:35 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 22:50:35 -0000
Subject: [wp-meta] [Making WordPress.org] #1639: Themes Trac browser
 does not display UTF-8 text correctly
In-Reply-To: <058.02b6120490346ff36855bbab3cf3faf8@wordpress.org>
References: <058.02b6120490346ff36855bbab3cf3faf8@wordpress.org>
Message-ID: <073.aaefc6e187a2434f562d675486d4a139@wordpress.org>

#1639: Themes Trac browser does not display UTF-8 text correctly
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Trac            |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 BuddyPress Trac appears to have the same issue. UTF-8 text in this patch
 is not displayed correctly:
 https://buddypress.trac.wordpress.org/attachment/ticket/7275/7275.01.patch

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

From noreply at wordpress.org  Wed Oct  5 23:38:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 05 Oct 2016 23:38:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration tools
 from wp-admin to front end
Message-ID: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+--------------------------------------
 Reporter:  tellyworth        |      Owner:
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  Plugin Directory v3 - M8
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------------------------
 Most of the plugin administration tools currently located within wp-admin
 need to move to the front end.

 Full list TDB.

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

From noreply at wordpress.org  Thu Oct  6 00:19:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 00:19:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2112: Review API endpoints
Message-ID: <054.84c7ff2c115b270aa8cb711e3c4d23dc@wordpress.org>

#2112: Review API endpoints
------------------------------+--------------------------------------
 Reporter:  tellyworth        |      Owner:
     Type:  task              |     Status:  new
 Priority:  normal            |  Milestone:  Plugin Directory v3 - M8
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------------------------
 Copied from https://meta.trac.wordpress.org/ticket/1579#comment:13 -

 We need

 * A stand alone PHP script which reads the WordPress postmeta table to
 perform updates
 * (ideally) A stand alone PHP script which can handle the
 plugin_information requests & /hello-dolly.json requests. I'd probably
 suggest we should just cache a full response from the REST API (/wp-
 json/plugins/v1/plugin/hello-dolly/) and handle the fields and conditional
 wp_version checks, as well as the output format (PHP serialized, XML, and
 JSON) in that handler
 * A REST API Endpoint which can be used for the hot_tags endpoint
 * A REST API Endpoint which can be used for the query_plugins endpoints,
 this mostly wraps WP_Query but has a lot of random and weird logic burried
 in it

 Loading WordPress for all these requests isn't going to be viable, but for
 some we'll have little choice.

 * The update handler should most definitely not load WordPress at all.
 * The hot_tags handler could just cache the result of the WordPress
 endpoint, so it doesn't require * loading WordPress often.
 * The plugin_information handler would be a good one to cache, and not hit
 WordPress on, as it's requested often enough and accounts for a
 significant amount of the api traffic.
 * The plugin_information handler via hello-dolly.json should be made
 cacheable, that means it should only use the data contained within the URL
 for the response, fetching the WordPress version from the user_agent isn't
 viable

 Task - review above, and create tickets for anything missing or broken.
 Those tickets probably belong in Milestone 8.

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

From noreply at wordpress.org  Thu Oct  6 00:24:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 00:24:04 -0000
Subject: [wp-meta] [Making WordPress.org] #1691: Internationalisation
In-Reply-To: <048.7263d91539fdc66a81cdcc7d96969d8d@wordpress.org>
References: <048.7263d91539fdc66a81cdcc7d96969d8d@wordpress.org>
Message-ID: <063.92ab4fb38c98e39ec1d5c26b3b6dfa8f@wordpress.org>

#1691: Internationalisation
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:
     Type:  task              |      Status:  reviewing
 Priority:  high              |   Milestone:  Plugin Directory v3 - M8
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M7 => Plugin Directory v3 - M8


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

From noreply at wordpress.org  Thu Oct  6 00:21:06 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Oct 2016 00:21:06 +0000 (UTC)
Subject: [wp-meta] [4190]
 sites/trunk/common/includes/slack/announce/config.php: Slack API: Add
 tellyworth to the /announce and / here whitelist for the #meta channel.
Message-ID: <20161006002106.206BF10805B2@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct  6 00:30:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 00:30:24 -0000
Subject: [wp-meta] [Making WordPress.org] #1828: Improve Screenshots
	section
In-Reply-To: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
References: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
Message-ID: <071.1f5522f51324bdd26ad142b59394f381@wordpress.org>

#1828: Improve Screenshots section
------------------------------+---------------------------------------
 Reporter:  samuelsidler      |       Owner:  mapk
     Type:  task              |      Status:  assigned
 Priority:  high              |   Milestone:  Plugin Directory v3 - M8
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M7 => Plugin Directory v3 - M8


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

From noreply at wordpress.org  Thu Oct  6 00:51:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 00:51:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.d7b0f0d0ebe15fb2bc3d56d6c91aa1ad@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M8
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Description changed by tellyworth:

Old description:

> Most of the plugin administration tools currently located within wp-admin
> need to move to the front end.
>
> Full list TDB.

New description:

 Most of the plugin administration tools currently located within wp-admin
 need to move to the front end. Specifically:

 * Plugin Controls (Status and Tested With)
 * Committers
 * Stats
 * Author plugins list
 * Admin/reviewer tools

--

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

From noreply at wordpress.org  Thu Oct  6 01:06:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:06:04 -0000
Subject: [wp-meta] [Making WordPress.org] #1691: Internationalisation
In-Reply-To: <048.7263d91539fdc66a81cdcc7d96969d8d@wordpress.org>
References: <048.7263d91539fdc66a81cdcc7d96969d8d@wordpress.org>
Message-ID: <063.a4f9c531cd1cde7eda90d307376e32e5@wordpress.org>

#1691: Internationalisation
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:
     Type:  task              |      Status:  reviewing
 Priority:  high              |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M8 => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct  6 01:06:59 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:06:59 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.b82f719e64eb2645fb5b8b6c965f2314@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M8 => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct  6 01:07:09 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:07:09 -0000
Subject: [wp-meta] [Making WordPress.org] #2112: Review API endpoints
In-Reply-To: <054.84c7ff2c115b270aa8cb711e3c4d23dc@wordpress.org>
References: <054.84c7ff2c115b270aa8cb711e3c4d23dc@wordpress.org>
Message-ID: <069.f69c4ed7b8083b9e8fbe2a6c3c0152c7@wordpress.org>

#2112: Review API endpoints
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M8 => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct  6 01:09:28 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:09:28 -0000
Subject: [wp-meta] [Making WordPress.org] #1840: Seamless Donations
 plugin doesn't show the right developer name
In-Reply-To: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
References: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
Message-ID: <067.837aa27d352dbd3dc725ef3506d9d3bf@wordpress.org>

#1840: Seamless Donations plugin doesn't show the right developer name
------------------------------+---------------------------------------
 Reporter:  dgewirtz          |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M6 => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct  6 01:09:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:09:46 -0000
Subject: [wp-meta] [Making WordPress.org] #1692: Plugin search quality
	improvements
In-Reply-To: <054.64f5df0f616286cc9021639b02dbca8a@wordpress.org>
References: <054.64f5df0f616286cc9021639b02dbca8a@wordpress.org>
Message-ID: <069.6a5906e91aeb92d40a21a6049fee2aa1@wordpress.org>

#1692: Plugin search quality improvements
-------------------------------------+-------------------------------------
 Reporter:  tellyworth               |       Owner:  tellyworth
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  Plugin Directory v3 -
Component:  Plugin Directory         |  M9
 Keywords:  dev-feedback needs-docs  |  Resolution:
  2nd-opinion                        |
-------------------------------------+-------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M5 => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct  6 01:07:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:07:38 -0000
Subject: [wp-meta] [Making WordPress.org] #1828: Improve Screenshots
	section
In-Reply-To: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
References: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
Message-ID: <071.e5be3f4d572ac14e1942efbcc114299d@wordpress.org>

#1828: Improve Screenshots section
------------------------------+---------------------------------------
 Reporter:  samuelsidler      |       Owner:  mapk
     Type:  task              |      Status:  assigned
 Priority:  high              |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:  Plugin Directory v3 - M8 => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct  6 01:09:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 01:09:05 -0000
Subject: [wp-meta] [Making WordPress.org] #1579: Plugins API
In-Reply-To: <052.c9092ef0a49c7a06d6a23dcbd8c8e564@wordpress.org>
References: <052.c9092ef0a49c7a06d6a23dcbd8c8e564@wordpress.org>
Message-ID: <067.c50e1675e819c6e052f6fb8d2f1533c8@wordpress.org>

#1579: Plugins API
------------------------------+---------------------------------------
 Reporter:  obenland          |       Owner:  dd32
     Type:  task              |      Status:  closed
 Priority:  high              |   Milestone:  Plugin Directory v3 - M7
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

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


Comment:

 Closing this, replaced by #2112.

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

From noreply at wordpress.org  Thu Oct  6 05:34:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 05:34:03 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.a28b7eecb933fa87fc15d46170a8a08e@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by jkohlbach):

 Replying to [comment:2 codeofconduct]:
 > [https://wordpress.org/plugins/simply-static/ My plugin] has 0 of 10
 threads marked as resolved, even though a decent number of the threads
 have been resolved. Note that it was legitimately 0 threads resolved
 before the bbPress upgrade; the threads were marked as resolved after the
 upgrade. For my plugin it kind of seems like the count is frozen in time.

 I'm also seeing this "frozen in time" effect on
 https://wordpress.org/plugins/woocommerce-wholesale-prices/

 The total number of support threads in the last 2 months is incorrect
 (we've had more than 3) and the number of unresolved threads is now 0, not
 2.

 The current stats that it's reporting on the plugin page are what we had
 just prior to the bbPress upgrade and it none of the numbers haven't
 changed at all since that day regardless of activity on the support forum.

 My theory is it's not pulling the data from the correct source at all.

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

From noreply at wordpress.org  Thu Oct  6 08:41:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 08:41:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2113: Implement sidebar toggle to
 the top of threads for small viewports
Message-ID: <050.e62762af5bbcd1474de274a794172ab4@wordpress.org>

#2113: Implement sidebar toggle to the top of threads for small viewports
----------------------------+-------------------------
 Reporter:  netweb          |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch
----------------------------+-------------------------
 Currently the sidebar gets moved under the thread when on smaller
 viewports, as it should be because it's not the primary focus.

 This can lead to a lot of scrolling in those cases one needs to get to the
 sidebar options, this should probably have a toggle before the thread as
 well to display it on smaller devices as threads can become quite long in
 some cases.

 Migrated from #bbPress3007

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

From noreply at wordpress.org  Thu Oct  6 09:31:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 09:31:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on popular
 themes list based on active installs
Message-ID: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+-----------------
 Reporter:  acosmin          |      Owner:
     Type:  defect           |     Status:  new
 Priority:  high             |  Milestone:
Component:  Theme Directory  |   Keywords:
-----------------------------+-----------------
 The Theme Review Theme doesn't police theme names anymore and this can
 lead to possible abuses of the popular themes list.

 If an author chooses a theme name and that theme name already exists
 outside the .org directory it will inherit all the active installs from
 that theme.

 Best example is with Themeforest themes:

 This newly released theme (just as an example, I don't want to say this
 theme abuses the system, it was released a long time ago when active
 installs were not part of the algorithm)
 https://wordpress.org/themes/total/

 gets all the active installs from this popular TF theme
 https://themeforest.net/item/total-responsive-multipurpose-wordpress-
 theme/6339019

 The solution could be to add a few more parameters in the mix and change
 the algorithm.
  * use the Author Name or Author URI or Theme URI to get unique results.
  * maybe a new tag in style.css

 This isn't fair to theme authors and needs a fix.

 Thanks!

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

From noreply at wordpress.org  Thu Oct  6 09:35:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 09:35:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.f89bda19191ee4f5144af0ae1667724f@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by ocean90):

 Related: #1604 for plugins

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

From noreply at wordpress.org  Thu Oct  6 09:55:41 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 09:55:41 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.998e431769ba224dff47935e1f25f497@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by grapplerulrich):

 Thank you for creating the ticket. A problem may arise if the Author or
 Theme URI gets changed of the time. We could warn Theme authors about this
 in advance.

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

From noreply at wordpress.org  Thu Oct  6 10:36:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 10:36:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.b0c555e3c99e1f03df01a9f36af35078@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  high             |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by acosmin):

 Another option, in TF's case, would be to look for this in style.css
 {{{
 License: Custom license
 License URI: http://themeforest.net/licenses/terms/regular
 }}}
 There are only
 [https://themeforest.net/tags/gpl?category=wordpress&referrer=search&utf8=%E2%9C%93&view=list
 18 themes fully GPL compatible] with not so many sales. Tthe rest are on a
 custom license.

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

From noreply at wordpress.org  Thu Oct  6 11:06:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 11:06:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.3f0972f8e6036473934af5747481d893@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  low              |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------
Changes (by dd32):

 * priority:  high => low


Comment:

 I'll refer this off to [https://core.trac.wordpress.org/ticket/14179
 #14179 on Core trac].
 The only solution here is to adjust how core theme update notifications
 are done, if an alteration is made there, then this will flow through to
 the active install counts for themes (and likewise for plugins),

 It's well documented that at present theme updates are based purely on the
 theme slug (folder name), and for Plugins although it's based on more data
 points, at the end of the day it's based almost purely upon the plugin
 slug (folder name) and plugin header name.

 The ideal solution for this is to include a unique header/UUID/hash in the
 headers to base update notifications off (as suggested in
 [https://core.trac.wordpress.org/ticket/10814 Core #10814] and others).

 I'd argue that TRT should probably reject theme names which are already
 used in the wild, primarily to prevent the unexpected update notifications
 from existing themes to the new w.org hosted theme.
 If this was something the TRT is interested in, I could hook up something
 to determine that based on our existing stat engines and report it, say if
 100+ sites in the wild already use that name. However that gets murky when
 you consider many themes are live in the wild via the authors site for
 months before approval on w.org, and it'll also significantly reduce the
 number of usable theme names (Hint: all the good ones are taken, with
 millions of theme names in the wild).

 Marking `low` as to be honest, this is something we've known about for 7+
 years and never made a move on, marking this as a duplicate of one of the
 core tickets is also an option.

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

From noreply at wordpress.org  Thu Oct  6 12:00:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 12:00:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.b5f41d02bcbf3472efb5c9132755fb1c@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  low              |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by StephenCronin):

 Replying to [comment:4 acosmin]:
 > Another option, in TF's case, would be to look for this in style.css
 > {{{
 > License: Custom license
 > License URI: http://themeforest.net/licenses/terms/regular
 > }}}
 > There are only
 [https://themeforest.net/tags/gpl?category=wordpress&referrer=search&utf8=%E2%9C%93&view=list
 18 themes fully GPL compatible] with not so many sales. The rest are on a
 custom license.

 Hi @acosmin,

 This is sort of irrelevant given Dion's response (which makes sense to
 me), but just wanted to let you know that you can't rely on that tag to
 work out how many 100% GPL themes there are on ThemeForest.
 [https://themeforest.net/collections/4930724-100-gpl-premium-wordpress-
 themes?utf8=%E2%9C%93&sort_by=sales_count&type_id=4930724 This collection]
 has 100 themes and I doubt it has them all.

 Also, I just checked a few ThemeForest themes (I work for Envato) and
 found that the use of the license field is pretty inconsistent, with some
 themes not even including it in style.css - so it can't be relied on.

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

From noreply at wordpress.org  Thu Oct  6 16:09:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 16:09:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.3e68cc0cb2279370a721045e4730a545@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  low              |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by edge22):

 If that's the case, perhaps the algorithm on the Popular tab needs to be
 tweaked.

 The way it is now, this theme is going to skyrocket to the top of the list
 after the first two weeks (or whatever it is).

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

From noreply at wordpress.org  Thu Oct  6 17:11:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 17:11:05 -0000
Subject: [wp-meta] [Making WordPress.org] #1561: Messages caught in the
 moderation queue need visual feedback
In-Reply-To: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
References: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
Message-ID: <073.4f93dc1648d541855785d2e16fa4c22e@wordpress.org>

#1561: Messages caught in the moderation queue need visual feedback
------------------------------+------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------

Comment (by SergeyBiryukov):

 [attachment:meta-1561.patch] got positive feedback in the latest Support
 Team meeting, see the logs above.

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

From noreply at wordpress.org  Thu Oct  6 19:02:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 19:02:02 -0000
Subject: [wp-meta] [Making WordPress.org] #2115: Please help me
Message-ID: <058.c301213a174b08c4f3a78b9090073dd0@wordpress.org>

#2115: Please help me
------------------------------------+---------------------------
 Reporter:  shahjahanbdsyl          |      Owner:
     Type:  defect                  |     Status:  new
 Priority:  high                    |  Milestone:
Component:  Login & Authentication  |   Keywords:  needs-refresh
------------------------------------+---------------------------
 Dear Sir
 I am Md. Shahjahan  from Bangladesh.
 I faced a problem every time in word press blog.
 After Sign in, when I wants submit new post, or publish new post, or wants
 any plugins setting.
 Every time I faced sign in problem.

 Why is it? Where did I mistake?
 Have you got any Idea and advice for me for that?
 Please help me.
 I look forward to getting your response.
 Have a nice day.

 Sincerely yours
 Md.Shahjahan

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

From noreply at wordpress.org  Thu Oct  6 19:09:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 19:09:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2115: Please help me
In-Reply-To: <058.c301213a174b08c4f3a78b9090073dd0@wordpress.org>
References: <058.c301213a174b08c4f3a78b9090073dd0@wordpress.org>
Message-ID: <073.f9de08f1983cfe80126eb3a18c678f40@wordpress.org>

#2115: Please help me
----------------------------+----------------------
 Reporter:  shahjahanbdsyl  |       Owner:
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  General         |  Resolution:  invalid
 Keywords:                  |
----------------------------+----------------------
Changes (by ocean90):

 * keywords:  needs-refresh =>
 * priority:  high => normal
 * status:  new => closed
 * component:  Login & Authentication => General
 * resolution:   => invalid


Comment:

 Hello @shahjahanbdsyl, this Trac is not for support. Please post your
 issue in our support forums https://wordpress.org/support/. Thanks!

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

From noreply at wordpress.org  Thu Oct  6 19:04:35 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Oct 2016 19:04:35 +0000 (UTC)
Subject: [wp-meta] [4191]
 sites/trunk/common/includes/slack/announce/config.php: Slack Announce:
 Update `#outreach` name to `#community-team`
Message-ID: <20161006190435.90E55108034A@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct  6 20:30:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 06 Oct 2016 20:30:04 -0000
Subject: [wp-meta] [Making WordPress.org] #1561: Messages caught in the
 moderation queue need visual feedback
In-Reply-To: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
References: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
Message-ID: <073.88c0d163fd49e498e226f2d15f00e9bc@wordpress.org>

#1561: Messages caught in the moderation queue need visual feedback
------------------------------+------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------

Comment (by coffee2code):

 In the message for a post that is still pending after 96 hours, isn't the
 opening `If this message is not yet approved` unnecessary? After all, the
 person is seeing that notice in the first place because the post is indeed
 still pending and older than 96 hours. That would leave `Please come to
 Slack #forums and let us know. Provide a link to the post.` as the
 message, which could use some sort of prefatory text. Maybe something
 like:

 `This post seems to be taking longer than expected to get approved. Please
 come to the #forums channel on WordPress Slack and let us know. Provide a
 link to this post.`

 Also, for spam intentionally not approved beyond 72 hours, do we still
 want the notice to display the `It will be reviewed within 72 hours.`
 sentence? It could just simply say `This post has been held for moderation
 by our automated system.` in this scenario, giving neither a timeline nor
 a call to action.

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

From noreply at wordpress.org  Thu Oct  6 21:58:00 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Oct 2016 21:58:00 +0000 (UTC)
Subject: [wp-meta] [4192]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/
 lets-encrypt-helper.php: Let's Encrypt Helper: Migrate from closed-source
 repository
Message-ID: <20161006215800.E1A51108034A@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct  6 22:42:49 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu,  6 Oct 2016 22:42:49 +0000 (UTC)
Subject: [wp-meta] [4193]
 sites/trunk/common/includes/slack/announce/config.php: Slack Announce: Add
 WordCamp Central members in Community/ WordCamp channels
Message-ID: <20161006224249.156EB108034A@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 00:10:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 00:10:57 -0000
Subject: [wp-meta] [Making WordPress.org] #1964: Forum Submit Button
 needs Ajax Love to show 'something' is happening.
In-Reply-To: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
References: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
Message-ID: <066.5e16bae0984889c8a895821f806e706f@wordpress.org>

#1964: Forum Submit Button needs Ajax Love to show 'something' is happening.
----------------------------+------------------
 Reporter:  Ipstenu         |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 The form should also actually prevent duplicate posts, like WordPress core
 does:
 {{{
 Duplicate comment detected; it looks as though you've already said that!
 }}}

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

From noreply at wordpress.org  Fri Oct  7 00:39:48 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 00:39:48 -0000
Subject: [wp-meta] [Making WordPress.org] #1984: Forums: ?view=all link
 should be more noticeable and always shown for moderators
In-Reply-To: <058.f58c421c9dc44dc7c8d200e9601fadf2@wordpress.org>
References: <058.f58c421c9dc44dc7c8d200e9601fadf2@wordpress.org>
Message-ID: <073.c7e5b2f0d7207f29dfb1b19f5988e585@wordpress.org>

#1984: Forums: ?view=all link should be more noticeable and always shown for
moderators
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 > In the new forums theme, the `?view=all` link for
 deleted/archived/pending messages is displayed in a small font in the
 sidebar

 Correction: for archived posts, the link is currently not displayed at
 all, see comment:2:ticket:2043. So there's no way to know if the current
 thread has any archived posts, unless you manually append `?view=all` to
 the URL.

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

From noreply at wordpress.org  Fri Oct  7 00:51:28 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 00:51:28 -0000
Subject: [wp-meta] [Making WordPress.org] #1984: Forums: ?view=all link
 should be more noticeable and always shown for moderators
In-Reply-To: <058.f58c421c9dc44dc7c8d200e9601fadf2@wordpress.org>
References: <058.f58c421c9dc44dc7c8d200e9601fadf2@wordpress.org>
Message-ID: <073.1e66b9d75f011daf484050f01d2bccda@wordpress.org>

#1984: Forums: ?view=all link should be more noticeable and always shown for
moderators
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Replying to [comment:1 ocean90]:
 > I don't see this part at all in the
 [https://make.wordpress.org/meta/2016/08/19/support-forum-preliminary-
 mockups/ latest mockups]. This should probably be mentioned there too so
 it doesn't get lost.

 Thanks, done.

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

From noreply at wordpress.org  Fri Oct  7 00:51:30 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 00:51:30 -0000
Subject: [wp-meta] [Making WordPress.org] #1986: Forums: Move reply
 permalink from .bp-topic-author column to .bbp-topic-content
In-Reply-To: <058.b7b86c798592bc39015a8906d91e4e5e@wordpress.org>
References: <058.b7b86c798592bc39015a8906d91e4e5e@wordpress.org>
Message-ID: <073.2c786bf07ae8f32d617ce8be695413f8@wordpress.org>

#1986: Forums: Move reply permalink from .bp-topic-author column to .bbp-topic-
content
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Replying to [comment:2 ocean90]:
 > Is this already covered in the
 [https://make.wordpress.org/meta/2016/08/19/support-forum-preliminary-
 mockups/ latest mockups for the redesign]? If not, this should probably be
 mentioned there too.

 Thanks, done.

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

From noreply at wordpress.org  Fri Oct  7 00:51:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 00:51:39 -0000
Subject: [wp-meta] [Making WordPress.org] #1996: Forums: "Stick" and "to
 front" links should be visually separated
In-Reply-To: <058.5ea26fb3c2ae9eca832013552ae9221b@wordpress.org>
References: <058.5ea26fb3c2ae9eca832013552ae9221b@wordpress.org>
Message-ID: <073.4ddef1aff330fd09125469a02e5920ca@wordpress.org>

#1996: Forums: "Stick" and "to front" links should be visually separated
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Replying to [comment:2 ocean90]:
 > Is this already covered in the
 [https://make.wordpress.org/meta/2016/08/19/support-forum-preliminary-
 mockups/ latest mockups for the redesign]? If not, this should probably be
 mentioned there too.

 Thanks, done.

 Another idea: maybe the placement can stay as is, but "to front" should be
 replaced with "to all forums" for clarity.

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

From noreply at wordpress.org  Fri Oct  7 02:01:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 02:01:39 -0000
Subject: [wp-meta] [Making WordPress.org] #2101: Forums:
 Spam/Pending/Archived views should display topic titles
In-Reply-To: <058.5afb3a9b1f90b5117ed8ae807d3afbd6@wordpress.org>
References: <058.5afb3a9b1f90b5117ed8ae807d3afbd6@wordpress.org>
Message-ID: <073.45b5693e3b4b0c90b4e903ea6bd95433@wordpress.org>

#2101: Forums: Spam/Pending/Archived views should display topic titles
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------

Comment (by SergeyBiryukov):

 The screenshots look good to me.

 Noticed a couple of things:
 * `'In forum: '` and `' topic: '` ? spaces should be moved out of
 translatable string, we can't count on all translators to notice and keep
 them.
 * The search template have a different styling for topic titles:
 https://ru.wordpress.org/support/search/test/, but that can wait for the
 theme revamp.

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

From noreply at wordpress.org  Fri Oct  7 02:05:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 02:05:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2104: Forums: Misaligned
 Reply link on RTL forums
In-Reply-To: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
References: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
Message-ID: <073.d7fd22284278f678e7ab81463c5290ff@wordpress.org>

#2104: Forums: Misaligned Reply link on RTL forums
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Seems good, shouldn't this be resolved in the bb-base theme itself though?

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

From noreply at wordpress.org  Fri Oct  7 02:18:08 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 02:18:08 -0000
Subject: [wp-meta] [Making WordPress.org] #2104: Forums: Misaligned
 Reply link on RTL forums
In-Reply-To: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
References: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
Message-ID: <073.3e5f9e9f6b742bb3918a3d73765ad139@wordpress.org>

#2104: Forums: Misaligned Reply link on RTL forums
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------

Comment (by netweb):

 Replying to [comment:2 SergeyBiryukov]:
 > Seems good, shouldn't this be resolved in the bb-base theme itself
 though?

 It could do, currently bb-base has no RTL support, there's also no plans
 to add more locale bbpress.org or buddypress.org sites, there's a plan
 somewhere to actually retire the existing BP locale sites from memory.

 So I went with the quickest and easiest solution :)

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

From noreply at wordpress.org  Fri Oct  7 03:42:54 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 03:42:54 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.34e91dadf20a20b69cfa3d9c5837f8a8@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by codeofconduct):

 Replying to [comment:3 jkohlbach]:
 >
 > My theory is it's not pulling the data from the correct source at all.

 One point in favor of that: my plugin now has 0 of 6 threads resolved. So
 the numbers aren't "frozen", they're slowly ticking down over time. It's
 just that they're not the right numbers :)

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

From noreply at wordpress.org  Fri Oct  7 04:31:15 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 04:31:15 +0000 (UTC)
Subject: [wp-meta] [4194]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/readme/class-parser.php: Plugin Directory: Readme Parsing
 : Use UTF8-aware line splitting to avoid matching newline charaters half
 way through a utf8 character byte.
Message-ID: <20161007043115.2EE6B1080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 04:31:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 04:31:15 -0000
Subject: [wp-meta] [Making WordPress.org] #1724: Readme parsing bugs
In-Reply-To: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
References: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
Message-ID: <063.9e084955350d60cb6d42762480f57003@wordpress.org>

#1724: Readme parsing bugs
------------------------------+------------------
 Reporter:  dd32              |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 In [changeset:"4194"]:
 {{{
 #!CommitTicketReference repository="" revision="4194"
 Plugin Directory: Readme Parsing: Use UTF8-aware line splitting to avoid
 matching newline charaters half way through a utf8 character byte.

 See #1724.
 }}}

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

From noreply at wordpress.org  Fri Oct  7 04:33:14 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 04:33:14 +0000 (UTC)
Subject: [wp-meta] [4195]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/cli/class-svn-watcher.php: Plugin Directory: Fix a typo in
 the SVN watcher.
Message-ID: <20161007043314.BA07F1080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 04:33:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 04:33:15 -0000
Subject: [wp-meta] [Making WordPress.org] #1720: post-commit svn hook
In-Reply-To: <048.fd1e468f716ec561c60812a81521e1e6@wordpress.org>
References: <048.fd1e468f716ec561c60812a81521e1e6@wordpress.org>
Message-ID: <063.b2742d1213194970fcb8cc0fcd3af68e@wordpress.org>

#1720: post-commit svn hook
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:
     Type:  task              |      Status:  closed
 Priority:  highest omg bbq   |   Milestone:  Plugin Directory v3 - M5
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4195"]:
 {{{
 #!CommitTicketReference repository="" revision="4195"
 Plugin Directory: Fix a typo in the SVN watcher.

 See #1720
 }}}

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

From noreply at wordpress.org  Fri Oct  7 04:35:28 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 04:35:28 +0000 (UTC)
Subject: [wp-meta] [4196]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/readme/class-parser.php: Plugin Directory: Readme Parsing
 : Standardise on `user_nicename` rather than `user_login` for the
 Contributors header.
Message-ID: <20161007043528.1D3FD1080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 04:35:28 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 04:35:28 -0000
Subject: [wp-meta] [Making WordPress.org] #1724: Readme parsing bugs
In-Reply-To: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
References: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
Message-ID: <063.6a25cd9b0d19969065e72ce28c51b147@wordpress.org>

#1724: Readme parsing bugs
------------------------------+------------------
 Reporter:  dd32              |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 In [changeset:"4196"]:
 {{{
 #!CommitTicketReference repository="" revision="4196"
 Plugin Directory: Readme Parsing: Standardise on `user_nicename` rather
 than `user_login` for the Contributors header.
 On WordPress.org we've got a lot of accounts for which the Login contains
 spaces, uppercase characters, email addresses, etc. Standardising on
 user_nicename simplifies the rest of the code.

 See #1724
 }}}

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

From noreply at wordpress.org  Fri Oct  7 04:44:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 04:44:39 -0000
Subject: [wp-meta] [Making WordPress.org] #1724: Readme parsing bugs
In-Reply-To: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
References: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
Message-ID: <063.f24f5ae4aeb5424059d2ae2f47812f8c@wordpress.org>

#1724: Readme parsing bugs
------------------------------+------------------
 Reporter:  dd32              |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 In [changeset:"4197"]:
 {{{
 #!CommitTicketReference repository="" revision="4197"
 Plugin Directory: Switch Contributors from being stored as post meta to a
 taxonomy to allow for more efficient querying.

 `/author/$author/` / `author_name` queries are now based on this taxonomy
 rather than by the `post_author`.

 See #1724, #1840.
 }}}

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

From noreply at wordpress.org  Fri Oct  7 04:44:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 04:44:39 -0000
Subject: [wp-meta] [Making WordPress.org] #1840: Seamless Donations
 plugin doesn't show the right developer name
In-Reply-To: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
References: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
Message-ID: <067.c5cb121dc1b03fcf6a30f294b080763b@wordpress.org>

#1840: Seamless Donations plugin doesn't show the right developer name
------------------------------+---------------------------------------
 Reporter:  dgewirtz          |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4197"]:
 {{{
 #!CommitTicketReference repository="" revision="4197"
 Plugin Directory: Switch Contributors from being stored as post meta to a
 taxonomy to allow for more efficient querying.

 `/author/$author/` / `author_name` queries are now based on this taxonomy
 rather than by the `post_author`.

 See #1724, #1840.
 }}}

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

From noreply at wordpress.org  Fri Oct  7 04:44:39 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 04:44:39 +0000 (UTC)
Subject: [wp-meta] [4197]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Switch Contributors from being stored as post meta to a
 taxonomy to allow for more efficient querying.
Message-ID: <20161007044439.502A11080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 05:41:24 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 05:41:24 +0000 (UTC)
Subject: [wp-meta] [4198]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/shortcodes/class-developers.php: Plugin Directory: Base
 the `[developers] ` shortcode off of Contributors rather than
 Contributors+Committers.
Message-ID: <20161007054124.25CC31080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 05:41:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 05:41:24 -0000
Subject: [wp-meta] [Making WordPress.org] #1724: Readme parsing bugs
In-Reply-To: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
References: <048.f0a4034ffeb07046bc76b987bdf394f2@wordpress.org>
Message-ID: <063.10217dbfe1e5045cd2332dc074f69eda@wordpress.org>

#1724: Readme parsing bugs
------------------------------+------------------
 Reporter:  dd32              |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 In [changeset:"4198"]:
 {{{
 #!CommitTicketReference repository="" revision="4198"
 Plugin Directory: Base the `[developers]` shortcode off of Contributors
 rather than Contributors+Committers.
 This is required after r4197.

 See #1724
 }}}

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

From noreply at wordpress.org  Fri Oct  7 06:16:29 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 06:16:29 +0000 (UTC)
Subject: [wp-meta] [4199]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-plugins/inc/template-tags.php: Plugin Directory: Remove unused ( and
 irrelevant) template tags which don't apply to the plugin directory.
Message-ID: <20161007061629.6777D1080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 06:17:36 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 06:17:36 +0000 (UTC)
Subject: [wp-meta] [4200]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-plugins/template-parts/plugin-single.php: Plugin Directory: Trial
 switching out the Author Byline to utilise the plugin header Author fields.
Message-ID: <20161007061736.CC8F21080575@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 06:17:37 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 06:17:37 -0000
Subject: [wp-meta] [Making WordPress.org] #1719: Plugin Directory Theme
In-Reply-To: <052.31ffb9bf9f16ccfccd1148337f9eccd8@wordpress.org>
References: <052.31ffb9bf9f16ccfccd1148337f9eccd8@wordpress.org>
Message-ID: <067.d531eeeff6404ddedc519d61d2ad66d3@wordpress.org>

#1719: Plugin Directory Theme
------------------------------+---------------------------------------
 Reporter:  obenland          |       Owner:  obenland
     Type:  task              |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M4
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4200"]:
 {{{
 #!CommitTicketReference repository="" revision="4200"
 Plugin Directory: Trial switching out the Author Byline to utilise the
 plugin header Author fields.

 This improves the consistency with how WordPress itself displays plugins
 both in the plugin listing, and in the plugin installer.

 See #1719.
 }}}

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

From noreply at wordpress.org  Fri Oct  7 06:16:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 06:16:29 -0000
Subject: [wp-meta] [Making WordPress.org] #1719: Plugin Directory Theme
In-Reply-To: <052.31ffb9bf9f16ccfccd1148337f9eccd8@wordpress.org>
References: <052.31ffb9bf9f16ccfccd1148337f9eccd8@wordpress.org>
Message-ID: <067.906b5325933b9e45b98ac0564367208f@wordpress.org>

#1719: Plugin Directory Theme
------------------------------+---------------------------------------
 Reporter:  obenland          |       Owner:  obenland
     Type:  task              |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M4
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4199"]:
 {{{
 #!CommitTicketReference repository="" revision="4199"
 Plugin Directory: Remove unused (and irrelevant) template tags which don't
 apply to the plugin directory.

 See #1719
 }}}

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

From noreply at wordpress.org  Fri Oct  7 06:19:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 06:19:49 -0000
Subject: [wp-meta] [Making WordPress.org] #1840: Seamless Donations
 plugin doesn't show the right developer name
In-Reply-To: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
References: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
Message-ID: <067.820f0ae1b60b6a1695193020cbd87fb7@wordpress.org>

#1840: Seamless Donations plugin doesn't show the right developer name
------------------------------+---------------------------------------
 Reporter:  dgewirtz          |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 Forgot to reference this ticket. This change means we're not currently
 relying upon post_author. This change may not stay around.

 > r4200: Plugin Directory: Trial switching out the Author Byline to
 utilise the plugin header Author fields.
 >
 > This improves the consistency with how WordPress itself displays plugins
 both in the plugin listing, and in the plugin installer.
 >
 > See #1719.

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

From noreply at wordpress.org  Fri Oct  7 06:37:32 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri,  7 Oct 2016 06:37:32 +0000 (UTC)
Subject: [wp-meta] [4201]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Conditionally show the `Tested up to: ` field based on
 whether the plugin has specified one,
 Automatically display the latest compatible minor release when appropriate.
Message-ID: <20161007063732.CC71810802F6@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct  7 06:37:33 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 06:37:33 -0000
Subject: [wp-meta] [Making WordPress.org] #2093: Plugin Directory:
 "Tested up to" version should include minor releases
In-Reply-To: <058.a7b09dd141ce664b82e084636d6d9402@wordpress.org>
References: <058.a7b09dd141ce664b82e084636d6d9402@wordpress.org>
Message-ID: <073.02c2caf2ef3697c399af73bd8205b4c7@wordpress.org>

#2093: Plugin Directory: "Tested up to" version should include minor releases
------------------------------+---------------------
 Reporter:  SergeyBiryukov    |       Owner:  dd32
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  needs-patch       |
------------------------------+---------------------
Changes (by dd32):

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


Comment:

 In [changeset:"4201"]:
 {{{
 #!CommitTicketReference repository="" revision="4201"
 Plugin Directory: Conditionally show the `Tested up to:` field based on
 whether the plugin has specified one, Automatically display the latest
 compatible minor release when appropriate.
 For example, a plugin specifying `Tested up to: 4.5.1` should
 automatically display `Tested up to: 4.5.2` as appropriate.

 Fixes #2093
 }}}

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

From noreply at wordpress.org  Fri Oct  7 06:43:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 06:43:44 -0000
Subject: [wp-meta] [Making WordPress.org] #1860: Broken paging for a
 certain plugin search query
In-Reply-To: <058.140d2a07efe37598829bdae6fb36fb09@wordpress.org>
References: <058.140d2a07efe37598829bdae6fb36fb09@wordpress.org>
Message-ID: <073.3b9c9ed7fa3df7106d27f4d051bf21df@wordpress.org>

#1860: Broken paging for a certain plugin search query
------------------------------+------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 Just noting this can be reproduced from the command line:
 {{{
 $ curl -v 'https://wordpress.org/plugins/search.php?page=2&q=plugin'
 *   Trying 66.155.40.250...
 * Connected to wordpress.org (127.0.0.1) port 443 (#0)
 * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 * Server certificate: *.wordpress.org
 * Server certificate: Go Daddy Secure Certificate Authority - G2
 * Server certificate: Go Daddy Root Certificate Authority - G2
 > GET /plugins/search.php?page=2&q=plugin HTTP/1.1
 > Host: wordpress.org
 > User-Agent: curl/7.43.0
 > Accept: */*
 >
 * Empty reply from server
 * Connection #0 to host wordpress.org left intact
 curl: (52) Empty reply from server
 }}}

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

From noreply at wordpress.org  Fri Oct  7 08:37:00 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 08:37:00 -0000
Subject: [wp-meta] [Making WordPress.org] #1964: Forum Submit Button
 needs Ajax Love to show 'something' is happening.
In-Reply-To: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
References: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
Message-ID: <066.cf77a82e10ef26721216386eceb3b5cc@wordpress.org>

#1964: Forum Submit Button needs Ajax Love to show 'something' is happening.
----------------------------+------------------
 Reporter:  Ipstenu         |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 Replying to [comment:1 SergeyBiryukov]:
 > The form should also actually prevent duplicate posts, like WordPress
 core does:
 > {{{
 > Duplicate comment detected; it looks as though you've already said that!
 > }}}


 bbPress should already handle cases of this with a topic or reply message
 like so:
 {{{
 ERROR: Duplicate reply detected; it looks as though you've already said
 that!
 }}}

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

From noreply at wordpress.org  Fri Oct  7 08:41:41 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 08:41:41 -0000
Subject: [wp-meta] [Making WordPress.org] #1561: Messages caught in the
 moderation queue need visual feedback
In-Reply-To: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
References: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
Message-ID: <073.610961859d327ce0c4a77a265382e04b@wordpress.org>

#1561: Messages caught in the moderation queue need visual feedback
------------------------------+------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------

Comment (by netweb):

 Replying to [comment:8 coffee2code]:
 > Also, for spam intentionally not approved beyond 72 hours, do we still
 want the notice to display the `It will be reviewed within 72 hours.`
 sentence? It could just simply say `This post has been held for moderation
 by our automated system.` in this scenario, giving neither a timeline nor
 a call to action.

 +1 Giving spammers any insight into the moderation workflow should reveal
 as little as possible

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

From noreply at wordpress.org  Fri Oct  7 09:58:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 09:58:14 -0000
Subject: [wp-meta] [Making WordPress.org] #1964: Forum Submit Button
 needs Ajax Love to show 'something' is happening.
In-Reply-To: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
References: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
Message-ID: <066.d5735be1d291c6e6055ccf4488043b39@wordpress.org>

#1964: Forum Submit Button needs Ajax Love to show 'something' is happening.
----------------------------+------------------
 Reporter:  Ipstenu         |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Replying to [comment:2 netweb]:
 > bbPress should already handle cases of this with a topic or reply
 message like so:
 > {{{
 > ERROR: Duplicate reply detected; it looks as though you've already said
 that!
 > }}}

 Hmm, it didn't catch my duplicate reply here:
 https://ru.wordpress.org/support/topic/?????????????-?????????-?????????-
 ru-wordpre/?view=all

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

From noreply at wordpress.org  Fri Oct  7 10:05:34 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 10:05:34 -0000
Subject: [wp-meta] [Making WordPress.org] #1964: Forum Submit Button
 needs Ajax Love to show 'something' is happening.
In-Reply-To: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
References: <051.1a8ea472882f8cb60a8db48c7a6be459@wordpress.org>
Message-ID: <066.747901300dc006a4a88469e9d46eeb0a@wordpress.org>

#1964: Forum Submit Button needs Ajax Love to show 'something' is happening.
----------------------------+------------------
 Reporter:  Ipstenu         |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by ocean90):

 Replying to [comment:3 SergeyBiryukov]:
 > Hmm, it didn't catch my duplicate reply here:
 > https://ru.wordpress.org/support/topic/?????????????-?????????-
 ?????????-ru-wordpre/?view=all

 Maybe you shouldn't be a moderator... ?
 https://bbpress.trac.wordpress.org/browser/trunk/src/includes/common/functions.php?rev=6085&marks=686#L666

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

From noreply at wordpress.org  Fri Oct  7 10:22:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 10:22:50 -0000
Subject: [wp-meta] [Making WordPress.org] #2116: Forums should have a way to
 view user's website URL from WP.org profile
Message-ID: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>

#2116: Forums should have a way to view user's website URL from WP.org profile
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 With the upgrade to bbPress 2.x, it's no longer possible to view user's
 website URL specified in their WP.org profile.

 This is important for moderators, because users often forget to mention
 the site they need help with in their initial post. Most of the time it's
 the site from their WP.org profile, so showing it in their forum profile
 would help to avoid unnecessary questions and provide relevant answers
 faster.

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

From noreply at wordpress.org  Fri Oct  7 10:23:40 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 10:23:40 -0000
Subject: [wp-meta] [Making WordPress.org] #2116: Forums should have a
 way to view user's website URL from WP.org profile
In-Reply-To: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>
References: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>
Message-ID: <073.594f279c5036e5f4d61bba9e8bebdf1c@wordpress.org>

#2116: Forums should have a way to view user's website URL from WP.org profile
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #2068

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

From noreply at wordpress.org  Fri Oct  7 10:26:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 10:26:50 -0000
Subject: [wp-meta] [Making WordPress.org] #2116: Forums should have a
 way to view user's website URL from WP.org profile
In-Reply-To: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>
References: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>
Message-ID: <073.16d5b17c8e699a26070ba2e272f29512@wordpress.org>

#2116: Forums should have a way to view user's website URL from WP.org profile
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 Moderators also utilize this to more reliably verify spam accounts in many
 cases.

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

From noreply at wordpress.org  Fri Oct  7 10:23:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 10:23:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2068: Forum profiles should
 have a link to the WP.org profile
In-Reply-To: <058.b29b614082c8dc87d5576c1adca6b4dd@wordpress.org>
References: <058.b29b614082c8dc87d5576c1adca6b4dd@wordpress.org>
Message-ID: <073.b14199f659ec042687449b67424b639e@wordpress.org>

#2068: Forum profiles should have a link to the WP.org profile
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #2116

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

From noreply at wordpress.org  Fri Oct  7 19:26:10 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 19:26:10 -0000
Subject: [wp-meta] [Making WordPress.org] #2117: Sticky header when
 scrolling down long Trac tickets
Message-ID: <055.d2d244beeef4aa0c206338a61823f773@wordpress.org>

#2117: Sticky header when scrolling down long Trac tickets
-------------------------+-------------------------------------
 Reporter:  johnbillion  |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  low          |  Milestone:
Component:  Trac         |   Keywords:  ui-feedback needs-patch
-------------------------+-------------------------------------
 I'm not the world's biggest fan of sticky headers, but when used carefully
 they can provide real value.

 After scrolling down through the comments of a long ticket and then
 getting distracted by something else and coming back to it, it's common to
 need to scroll back to the top to remind yourself which ticket you're
 reading.

 A small sticky header that contains the ticket number, summary, and status
 would be useful. Potentially just the top of the main ticket info box:

 [[Image(https://i.imgur.com/DI1bmbU.png)]]

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

From noreply at wordpress.org  Fri Oct  7 22:38:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 07 Oct 2016 22:38:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.e08ad761ef294eefe9ef34105d5a1845@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  low              |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by Shaped Pixels):

 Looks like my comment about this in Slack got some attention...I've
 actually noticed the discrepancies from time-to-time from minimal counts
 to crazy numbers like the 30,000 active installs on a new theme. I follow
 the theme lists on a regular basis, so glad to see this was brought forth.

 I would assume that in some cases, it's accidental, while others it could
 be a loophole someone discovered which would lead to the possibility of
 abuse--especially when it comes to the Popular List. There's at least a
 couple themes there, plus others I've seen over the months that have
 numbers that seem out of the ordinary.

 As a side note and as a theme developer (author), I would still love to
 see the total downloads count along side the active installs count. Gives
 the author (and users) a way of seeing the ratio of active installs to
 downloads. I know for me, it would give me a better idea of how my themes
 perform. If a theme has large download counts but low active installs,
 that would tell me users are not overly happy with the theme, therefore,
 creates incentive for the author to do better.

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

From noreply at wordpress.org  Sat Oct  8 04:23:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 04:23:49 -0000
Subject: [wp-meta] [Making WordPress.org] #1840: Seamless Donations
 plugin doesn't show the right developer name
In-Reply-To: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
References: <052.499008590ffa9204b62558aec9d2a90a@wordpress.org>
Message-ID: <067.1029cc2e70971a0a892d85cd4004a7fe@wordpress.org>

#1840: Seamless Donations plugin doesn't show the right developer name
------------------------------+---------------------------------------
 Reporter:  dgewirtz          |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4202"]:
 {{{
 #!CommitTicketReference repository="" revision="4202"
 Plugin Directory: Treat `/author/$author` queries as taxonomy queries, and
 not author queries.
 This is unfortunately needed as WordPress expects that the `post_author`
 of the posts is the Author for author templates, and as a result displays
 an incorrect archive title.

 See #1840.
 }}}

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

From noreply at wordpress.org  Sat Oct  8 04:23:48 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  8 Oct 2016 04:23:48 +0000 (UTC)
Subject: [wp-meta] [4202]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/class-plugin-directory.php: Plugin Directory: Treat `/
 author/$author` queries as taxonomy queries, and not author queries.
Message-ID: <20161008042348.A817C10805FB@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct  8 10:51:26 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  8 Oct 2016 10:51:26 +0000 (UTC)
Subject: [wp-meta] [4203] sites/trunk/common/includes/wporg-sso:
 WordPress.org SSO: Use a support email address for email/password change
 emails.
Message-ID: <20161008105126.DEE481080334@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct  8 17:35:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 17:35:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2118: [Homepage] "Download
 WordPress" doesn't display at 820px width
Message-ID: <051.2600cf88d2e79a5729bd0c27aafffe52@wordpress.org>

#2118: [Homepage] "Download WordPress" doesn't display at 820px width
---------------------+-----------------
 Reporter:  mbabker  |      Owner:
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:
---------------------+-----------------
 On the WordPress homepage, when the browser has a 820px width the
 "Download WordPress" button does not display.  The media queries for the
 button in the main header and the mobile download section both target
 820px for their 'display: none;' declarations.

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

From noreply at wordpress.org  Sat Oct  8 18:27:17 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 18:27:17 -0000
Subject: [wp-meta] [Making WordPress.org] #2118: [Homepage] "Download
 WordPress" doesn't display at 820px width
In-Reply-To: <051.2600cf88d2e79a5729bd0c27aafffe52@wordpress.org>
References: <051.2600cf88d2e79a5729bd0c27aafffe52@wordpress.org>
Message-ID: <066.158233613449baf0bb14e64952090108@wordpress.org>

#2118: [Homepage] "Download WordPress" doesn't display at 820px width
---------------------+---------------------
 Reporter:  mbabker  |       Owner:
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------
Changes (by Otto42):

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


Comment:

 Changing the min-width on the #download-mobile to 821px eliminates the
 issue by allowing that div to appear at 820px.

 wp4.css line 636:

 @media screen and (min-width:821px) {
     #download-mobile {
         display: none;
     }
 }

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

From noreply at wordpress.org  Sat Oct  8 18:28:33 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat,  8 Oct 2016 18:28:33 +0000 (UTC)
Subject: [wp-meta] [4204]
 sites/trunk/wordpress.org/public_html/style/wp4.css: Homepage: Adjust
 styling to allow div to appear at the correct breakpoint for mobile.
Message-ID: <20161008182833.3AC2C1080334@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct  8 18:30:16 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 18:30:16 -0000
Subject: [wp-meta] [Making WordPress.org] #2118: [Homepage] "Download
 WordPress" doesn't display at 820px width
In-Reply-To: <051.2600cf88d2e79a5729bd0c27aafffe52@wordpress.org>
References: <051.2600cf88d2e79a5729bd0c27aafffe52@wordpress.org>
Message-ID: <066.6da0f58dc59d462a287ac768a8a8febe@wordpress.org>

#2118: [Homepage] "Download WordPress" doesn't display at 820px width
---------------------+---------------------
 Reporter:  mbabker  |       Owner:
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------

Comment (by Otto42):

 Fixed in [4204].

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

From noreply at wordpress.org  Sat Oct  8 18:35:35 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 18:35:35 -0000
Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications
 should have an option to match whole words only
In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
Message-ID: <073.daa59a512e13a428f0ffe022e5c0aea6@wordpress.org>

#2119: Profiles: Notifications should have an option to match whole words only
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Otto42):

 Ideally, I think this should be extended to all usernames should be whole-
 word only. I don't want to get notifications for "bottom" or something
 like that either.

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

From noreply at wordpress.org  Sat Oct  8 18:32:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 18:32:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications
 should have an option to match whole words only
Message-ID: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>

#2119: Profiles: Notifications should have an option to match whole words only
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Profiles        |   Keywords:
----------------------------+-----------------
 One of ru_RU forum administrators has a notification for `yui` (her WP.org
 display name on and Slack username).

 She's getting unrelated notifications for strings like `wp-content/plugins
 /widget-options/assets/css/jqueryui`.

 There should be an option to match whole words only to avoid irrelevant
 matches.

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

From noreply at wordpress.org  Sat Oct  8 18:38:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 18:38:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications
 should have an option to match whole words only
In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
Message-ID: <073.b230af633dadb14786541ef6ea71fae5@wordpress.org>

#2119: Profiles: Notifications should have an option to match whole words only
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:                  |
----------------------------+------------------
Description changed by SergeyBiryukov:

Old description:

> One of ru_RU forum administrators has a notification for `yui` (her
> WP.org display name on and Slack username).
>
> She's getting unrelated notifications for strings like `wp-
> content/plugins/widget-options/assets/css/jqueryui`.
>
> There should be an option to match whole words only to avoid irrelevant
> matches.

New description:

 One of ru_RU forum administrators has a notification for `yui` (her WP.org
 display name and Slack username).

 She's getting unrelated notifications for strings like `wp-content/plugins
 /widget-options/assets/css/jqueryui`.

 There should be an option to match whole words only to avoid irrelevant
 matches.

--

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

From noreply at wordpress.org  Sat Oct  8 19:42:19 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 19:42:19 -0000
Subject: [wp-meta] [Making WordPress.org] #2120: Forums: Make search input
	wider
Message-ID: <058.bdc6a99db4ac521641432c425ac54547@wordpress.org>

#2120: Forums: Make search input wider
----------------------------+------------------------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  has-patch commit
----------------------------+------------------------------
 English and Rosetta support forums currently use different search forms,
 see [3926].

 Search inputs in both forms have a couple of issues:
 * The default `140px` width is too short.
 * The input on https://wordpress.org/support/ has an extra header and is
 missing bottom margin.


 See the screenshots. The inputs also have different background color, but
 I'm not sure which one is "canonical", so the patch only handles the two
 points above.

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

From noreply at wordpress.org  Sat Oct  8 22:15:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 22:15:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2121: Forums: Increase time limit
 to edit a post
Message-ID: <058.c535d0b5393a3046a5c93382fdb8c163@wordpress.org>

#2121: Forums: Increase time limit to edit a post
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 One of ru_RU forum members raised a point that time limit for editing
 posts should be increased.

 Apparently it's set to just a couple of minutes now, which might not be
 enough to catch all the typos or fix code formatting issues. And if you
 submit corrections in a follow-up post, the topic goes out of the "No
 Replies" view and gets less attention.

 A workaround is to prepare the post in advance using Notepad or other text
 editor, but that's not a very friendly UX.

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

From noreply at wordpress.org  Sat Oct  8 23:23:19 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 23:23:19 -0000
Subject: [wp-meta] [Making WordPress.org] #2121: Forums: Increase time
 limit to edit a post
In-Reply-To: <058.c535d0b5393a3046a5c93382fdb8c163@wordpress.org>
References: <058.c535d0b5393a3046a5c93382fdb8c163@wordpress.org>
Message-ID: <073.94c3016814a4e8a7af0f29a3ec0a00d6@wordpress.org>

#2121: Forums: Increase time limit to edit a post
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 bbPress' default time is 5 minutes...

 https://bbpress.trac.wordpress.org/browser/trunk/src/includes/core/options.php#L33

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

From noreply at wordpress.org  Sat Oct  8 23:29:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 08 Oct 2016 23:29:49 -0000
Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications
 should have an option to match whole words only
In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
Message-ID: <073.1b49854907d5aabfb53f9a765b168ef0@wordpress.org>

#2119: Profiles: Notifications should have an option to match whole words only
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 Yes please, I currently get notifications for user `netweb logic` (Without
 the space) and I'd rather not

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

From noreply at wordpress.org  Sun Oct  9 11:06:47 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 11:06:47 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.764889a787e57f5f76b5b7dfdf615a24@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by dimadin):

 This view feed that has only latest topics but not their replies is not as
 useful as it should be. I was thinking how can we incorporate replies too
 and I came to idea that both topics and replies have meta fields with data
 about plugin/theme. We can then use that in the same query before
 `bbp_request_feed_trap()`. See attached (untested and rough) patch for
 more details.

 Problem with this approach is that existing topics and their replies in
 this taxonomy must be updated.

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

From noreply at wordpress.org  Sun Oct  9 11:14:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 11:14:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2122: WordPress.tv: Introduce
 "watch later" functionality
Message-ID: <058.68a50cc54ffadc577ed08c6c66ab57fa@wordpress.org>

#2122: WordPress.tv: Introduce "watch later" functionality
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  WordPress.tv    |   Keywords:
----------------------------+-----------------
 When I stumble upon some interesting talks that I'd like to watch in the
 nearest future, they tend to pile up in my browser tabs and sometimes are
 lost if the browser eventually crashes.

 There should be a "watch later" functionality that would allow you to save
 talks for later reference.

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

From noreply at wordpress.org  Sun Oct  9 12:03:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 12:03:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.38cc656d4f079c37f2485e475a5cf410@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by StephenCronin):

 @SergeyBiryukov - I see you just updated your post above to say that the
 following two now work:

 > [Works] Committer view: https://wordpress.org/support/view/plugin-
 committer/sergeybiryukov
 > [Works] Committer feed: https://wordpress.org/support/rss/view/plugin-
 committer/sergeybiryukov

 However if you compare the two you'll see that the first one shows entries
 from both 'Plugins and Hack' and 'Reviews', while the second one (the
 feed) only shows 'Reviews'. So I think the second one isn't quite fixed.

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

From noreply at wordpress.org  Sun Oct  9 12:20:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 12:20:39 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.2547c0c93cc34a1c3bb9a64623adbce3@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Replying to [comment:13 StephenCronin]:
 > However if you compare the two you'll see that the first one shows
 entries from both 'Plugins and Hack' and 'Reviews', while the second one
 (the feed) only shows 'Reviews'. So I think the second one isn't quite
 fixed.

 Thanks, added.

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

From noreply at wordpress.org  Sun Oct  9 13:31:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 13:31:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2121: Forums: Increase time
 limit to edit a post
In-Reply-To: <058.c535d0b5393a3046a5c93382fdb8c163@wordpress.org>
References: <058.c535d0b5393a3046a5c93382fdb8c163@wordpress.org>
Message-ID: <073.d29ef1b711d294052ffa07fc332c5adc@wordpress.org>

#2121: Forums: Increase time limit to edit a post
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Ideally, there should also be a way to preview posts before submitting,
 see #153.

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

From noreply at wordpress.org  Sun Oct  9 13:32:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 13:32:50 -0000
Subject: [wp-meta] [Making WordPress.org] #153: Allow previewing posts
 in WordPress.org support forums
In-Reply-To: <052.a972d6ed31b11330a5736068f5969539@wordpress.org>
References: <052.a972d6ed31b11330a5736068f5969539@wordpress.org>
Message-ID: <067.c9de74ec6d816d844fe9494b42784190@wordpress.org>

#153: Allow previewing posts in WordPress.org support forums
----------------------------+------------------
 Reporter:  Daedalon        |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  lowest          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #2121

 Now that the forums are on bbPress 2.x (#1544), it would be great to take
 a stab at this.

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

From noreply at wordpress.org  Sun Oct  9 14:55:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 14:55:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2123: Forums: Misaligned "Topic
 Tag: %s" heading
Message-ID: <058.c832f4c2ea8458fa735d12cd7a542afe@wordpress.org>

#2123: Forums: Misaligned "Topic Tag: %s" heading
----------------------------+------------------------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  has-patch commit
----------------------------+------------------------------
 `Topic Tag: %s` heading is too large and is displayed on the same line
 with breadcrumbs, see the screenshot.

 It's the only `<h1>` heading in the theme, the rest are `<h2>`. For
 consistency, it should be `<h2>` too.

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

From noreply at wordpress.org  Sun Oct  9 22:56:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 09 Oct 2016 22:56:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2124: Simplify meeting attendance
	lists
Message-ID: <051.b2d6bad6a6df9ea7de96a5a651b21eba@wordpress.org>

#2124: Simplify meeting attendance lists
--------------------------------------+-----------------
 Reporter:  Clorith                   |      Owner:
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+-----------------
 I'd like to propose the use of https://wordpress.org/plugins/meeting-
 attendance-for-slack/, or a derivative of it, on the make sites.

 The current approach (at least for normal users) involves manually going
 over all messages and reactions after a meeting in the Slack archives,
 this is both time consuming and frustrating in the long run and adds
 needless strain on the role of meeting organizers.

 The plugin simplifies the process of keeping attendance, all that's needed
 is to supply archive links for the start and end of a meeting, and which
 channel it was held in, everything else is handled via a shortcode.

 This means you can grab the link when you start the meeting, and when it
 ends, and there's no longer a need to go to the archives at all for the
 attendance part.

 There's also a filter, `slack_attendance_user_real_name`, which provides
 the user object of each user that is matched, this can be used to return a
 .org user instead of a Slack name as we've already got a link between
 usernames that is used on the profiles page.

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

From noreply at wordpress.org  Mon Oct 10 00:19:20 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 00:19:20 -0000
Subject: [wp-meta] [Making WordPress.org] #2065: Add year to dates on
 http://central.wordcamp.org/schedule/
In-Reply-To: <059.ac3962f242437219871b68a88feac608@wordpress.org>
References: <059.ac3962f242437219871b68a88feac608@wordpress.org>
Message-ID: <074.309e9473a581e3b15dda4e1d30a4dccb@wordpress.org>

#2065: Add year to dates on http://central.wordcamp.org/schedule/
--------------------------------------+-----------------------
 Reporter:  andreamiddleton           |       Owner:  iandunn
     Type:  enhancement               |      Status:  accepted
 Priority:  low                       |   Milestone:
Component:  WordCamp Site & Plugins   |  Resolution:
 Keywords:  good-first-bug has-patch  |
--------------------------------------+-----------------------

Comment (by frq):

 Hey @iandunn, thanks for the support.

 I tried to do as you pointed me, hope I undestood it correctly.

 1) Added a `show_year` that defaults to false in `the_wordcamp_date`. If
 true, the year is shown as in the first patch.

 2) Modified `template_schedule.php` to show the list of WordCamps grouped
 by year, as in `template-past-wordcamps.php`. Thought about adding a
 conditional here to show or not the headings with the year, but was not
 sure about it.

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

From noreply at wordpress.org  Mon Oct 10 06:29:11 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 06:29:11 -0000
Subject: [wp-meta] [Making WordPress.org] #1915: Heading level for
 Changelog entries
In-Reply-To: <049.c90071192296c1ce4fe454299feb0c12@wordpress.org>
References: <049.c90071192296c1ce4fe454299feb0c12@wordpress.org>
Message-ID: <064.ceb1a39a7cf6a8813a8c4efb117d5a17@wordpress.org>

#1915: Heading level for Changelog entries
------------------------------+------------------
 Reporter:  GaryJ             |       Owner:
     Type:  defect            |      Status:  new
 Priority:  low               |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+------------------
Changes (by dd32):

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


Comment:

 This is an unfortunate side effect of the markdown parsing, which doesn't
 allow us to easily change the header style for elements - it's based on
 what heading level was specified in the markdown.

 For screen readers, we shouldn't skip levels, but due to the complexity
 i'm lowering the priority.

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

From noreply at wordpress.org  Mon Oct 10 15:07:30 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 15:07:30 -0000
Subject: [wp-meta] [Making WordPress.org] #2065: Add year to dates on
 http://central.wordcamp.org/schedule/
In-Reply-To: <059.ac3962f242437219871b68a88feac608@wordpress.org>
References: <059.ac3962f242437219871b68a88feac608@wordpress.org>
Message-ID: <074.c8b4d74a08d6954742f89d7ceaea3fe7@wordpress.org>

#2065: Add year to dates on http://central.wordcamp.org/schedule/
--------------------------------------+-----------------------
 Reporter:  andreamiddleton           |       Owner:  iandunn
     Type:  enhancement               |      Status:  accepted
 Priority:  low                       |   Milestone:
Component:  WordCamp Site & Plugins   |  Resolution:
 Keywords:  good-first-bug has-patch  |
--------------------------------------+-----------------------

Comment (by iandunn):

 Those look great, thanks :) I'll add this to my list of patches to commit.

 There's a few places where it doesn't match the coding standards, but I
 can quickly fix those before I commit it. For future reference, though,
 keep these in mind:

 * https://make.wordpress.org/core/handbook/best-practices/coding-
 standards/php/#self-explanatory-flag-values-for-function-arguments
 * https://make.wordpress.org/core/handbook/best-practices/coding-
 standards/php/#brace-style

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

From noreply at wordpress.org  Mon Oct 10 16:30:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 16:30:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2125: Malformed comment when
 referencing a changeset in a commit message
Message-ID: <055.aa7aa959b47502ad38ac673c72be9378@wordpress.org>

#2125: Malformed comment when referencing a changeset in a commit message
-------------------------+-------------------------
 Reporter:  johnbillion  |      Owner:
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Trac         |   Keywords:  needs-patch
-------------------------+-------------------------
 [WP38761] referenced [WP38759] in its commit message, but
 [https://core.trac.wordpress.org/ticket/38256#comment:4 the corresponding
 comment posted to the ticket] is malformed.

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

From noreply at wordpress.org  Mon Oct 10 18:21:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 18:21:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2125: Malformed comment when
 referencing a changeset in a commit message
In-Reply-To: <055.aa7aa959b47502ad38ac673c72be9378@wordpress.org>
References: <055.aa7aa959b47502ad38ac673c72be9378@wordpress.org>
Message-ID: <070.cdd765ec24bbbcea1f4c0faf3cee5242@wordpress.org>

#2125: Malformed comment when referencing a changeset in a commit message
------------------------------+------------------
 Reporter:  johnbillion       |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Trac              |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------
Changes (by SergeyBiryukov):

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


Comment:

 [attachment:meta-2125.patch] adds `requires` to the list of reserved terms
 that should not be converted to a mention.

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

From noreply at wordpress.org  Mon Oct 10 18:24:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 18:24:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2126: Deter Developers from
 Leaving Reviews On Their Own Product
Message-ID: <051.dbb5835f62448a84c558890890be135f@wordpress.org>

#2126: Deter Developers from Leaving Reviews On Their Own Product
----------------------------+-----------------
 Reporter:  Ipstenu         |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 It's not BAD to review your own product, but people should be honest about
 this stuff.

 We should alert developers that they should leave productive and disclosed
 reviews on their work.

 For example, on https://wordpress.org/support/plugin/akismet/reviews/ if
 you were someone with commit access (or listed as an author) you should
 get a message like this:

 "A review should be the review of an experience a user has with your
 plugin, not for self-promotion. Since you work on this [plugin|theme],
 please consider <em>not</em> leaving a review on your own work. You were
 probably going to give it five stars anyway."

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

From noreply at wordpress.org  Mon Oct 10 18:36:22 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 18:36:22 -0000
Subject: [wp-meta] [Making WordPress.org] #2094: Moderator badge
 shouldn't overwrite author badge in user profile replies loop
In-Reply-To: <050.5f13853ce82f506dc5e39cd0db3978d3@wordpress.org>
References: <050.5f13853ce82f506dc5e39cd0db3978d3@wordpress.org>
Message-ID: <065.6e37665e0a36135ceae32324f5a00ff8@wordpress.org>

#2094: Moderator badge shouldn't overwrite author badge in user profile replies
loop
----------------------------+--------------------------
 Reporter:  netweb          |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  needs-patch     |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4205"]:
 {{{
 #!CommitTicketReference repository="" revision="4205"
 Support Forums, User Badges: Display plugin/theme author/contributor badge
 in user profile replies loop (and other out-of-forum-context views).

 Fixes #2094.
 }}}

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

From noreply at wordpress.org  Mon Oct 10 18:36:21 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 18:36:21 +0000 (UTC)
Subject: [wp-meta] [4205]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-bbp-user-badges/inc/class-plugin.php: Support Forums,
 User Badges: Display plugin/theme author/ contributor badge in user profile
 replies loop ( and other out-of-forum-context views).
Message-ID: <20161010183621.D9F0F1080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 19:46:38 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 19:46:38 +0000 (UTC)
Subject: [wp-meta] [4206]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-forums:
 Forums Theme: Show Slack username and/ or WordPress.org username (linked to
 profiles.wordpress.org) in user profiles.
Message-ID: <20161010194638.103CE1080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 19:46:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 19:46:39 -0000
Subject: [wp-meta] [Making WordPress.org] #2068: Forum profiles should
 have a link to the WP.org profile
In-Reply-To: <058.b29b614082c8dc87d5576c1adca6b4dd@wordpress.org>
References: <058.b29b614082c8dc87d5576c1adca6b4dd@wordpress.org>
Message-ID: <073.2f5dc2a5959a3abc0687597a8b3718f8@wordpress.org>

#2068: Forum profiles should have a link to the WP.org profile
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4206"]:
 {{{
 #!CommitTicketReference repository="" revision="4206"
 Forums Theme: Show Slack username and/or WordPress.org username (linked to
 profiles.wordpress.org) in user profiles.

 Also adds missing translator comments for all the placeholders in the same
 block.

 Props SergeyBiryukov.
 Fixes #2068.
 }}}

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

From noreply at wordpress.org  Mon Oct 10 19:53:12 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 19:53:12 +0000 (UTC)
Subject: [wp-meta] [4207]
 sites/trunk/wordpress.org/public_html/style/trac/wp-trac.js: Trac: Add
 `requires` to the list of reserved terms that should not be converted to a
 mention.
Message-ID: <20161010195312.90ED91080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 19:53:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 19:53:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2125: Malformed comment when
 referencing a changeset in a commit message
In-Reply-To: <055.aa7aa959b47502ad38ac673c72be9378@wordpress.org>
References: <055.aa7aa959b47502ad38ac673c72be9378@wordpress.org>
Message-ID: <070.f0256482e1c0cc55767d056f074f91f9@wordpress.org>

#2125: Malformed comment when referencing a changeset in a commit message
------------------------------+--------------------------
 Reporter:  johnbillion       |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Trac              |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4207"]:
 {{{
 #!CommitTicketReference repository="" revision="4207"
 Trac: Add `requires` to the list of reserved terms that should not be
 converted to a mention.

 Props SergeyBiryukov.
 Fixes #2125.
 }}}

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

From noreply at wordpress.org  Mon Oct 10 19:58:55 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 19:58:55 +0000 (UTC)
Subject: [wp-meta] [4208]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/functions.php: Forums Theme: Fix display of "Topic Tag: %s"
 heading.
Message-ID: <20161010195855.218741080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 19:58:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 19:58:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2123: Forums: Misaligned
 "Topic Tag: %s" heading
In-Reply-To: <058.c832f4c2ea8458fa735d12cd7a542afe@wordpress.org>
References: <058.c832f4c2ea8458fa735d12cd7a542afe@wordpress.org>
Message-ID: <073.13a462b205bc6e35f253e594e16a178a@wordpress.org>

#2123: Forums: Misaligned "Topic Tag: %s" heading
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4208"]:
 {{{
 #!CommitTicketReference repository="" revision="4208"
 Forums Theme: Fix display of "Topic Tag: %s" heading.

 The heading was too large and displayed on the same line as the preceding
 breadcrumbs.

 Props SergeyBiryukov.
 Fixes #2123.
 }}}

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

From noreply at wordpress.org  Mon Oct 10 20:12:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 20:12:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2120: Forums: Make search
	input wider
In-Reply-To: <058.bdc6a99db4ac521641432c425ac54547@wordpress.org>
References: <058.bdc6a99db4ac521641432c425ac54547@wordpress.org>
Message-ID: <073.792edaf9b2ab85d00d626d7677dafce6@wordpress.org>

#2120: Forums: Make search input wider
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4209"]:
 {{{
 #!CommitTicketReference repository="" revision="4209"
 Forums Theme: Fix display of search form on forum front page.

 * Double width of input field
 * Add margin below input field
 * Remove unnecessary search form header

 Props SergeyBiryukov.
 Fixes #2120.
 }}}

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

From noreply at wordpress.org  Mon Oct 10 20:12:04 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 20:12:04 +0000 (UTC)
Subject: [wp-meta] [4209]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/style.css: Forums Theme: Fix display of search form on forum
 front page.
Message-ID: <20161010201204.ED9221080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 20:20:37 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 20:20:37 +0000 (UTC)
Subject: [wp-meta] [4210]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-plugins/page-add.php: Plugin Directory: Remove defunct link "
 Deploying your plugin" from the "Add Your Plugin" page.
Message-ID: <20161010202037.91A231080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 20:20:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 20:20:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2088: Unexisting URL
 wordpress-org/deploying-your-plugin/
In-Reply-To: <051.e8e505a9deb05bc363ebcdbce9fc0b55@wordpress.org>
References: <051.e8e505a9deb05bc363ebcdbce9fc0b55@wordpress.org>
Message-ID: <066.f733a3f165366f80263fdc1e105cb44b@wordpress.org>

#2088: Unexisting URL wordpress-org/deploying-your-plugin/
------------------------------+--------------------------
 Reporter:  casiepa           |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4210"]:
 {{{
 #!CommitTicketReference repository="" revision="4210"
 Plugin Directory: Remove defunct link "Deploying your plugin" from the
 "Add Your Plugin" page.

 The page had been merged into the already-linked "How to use SVN" page.

 Props SergeyBiryukov.
 Fixes #2088.
 }}}

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

From noreply at wordpress.org  Mon Oct 10 20:23:04 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 10 Oct 2016 20:23:04 +0000 (UTC)
Subject: [wp-meta] [4211]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/functions.php: Forums Theme: Bump CSS version for cache bust.
Message-ID: <20161010202304.AE7C41080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 10 20:37:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 20:37:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.5ba5dc14d4ede2ebb8a19744712cd2f9@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by mapk):

 While there should be a link/button for the author's admin section right
 on the plugin page itself, I'm wondering if there should be a more
 generalized link someone else within the plugin directory to take the
 author to an admin overview of ALL their plugins?

 Below are examples of where the individual plugin admin link could reside,
 and they would only be visible to Authors/Admins who are logged in.

 v1 - Button under the 'Download' button
 https://cldup.com/2r9cLaqTvV.png

 v2 - Link under the author's name
 https://cldup.com/b2QvF1Mhe2.png

 v3 - Link under the 'Download' button
 https://cldup.com/uLCTIxlGg9.png

 v4 - Link in sidebar under meta data (or above)
 https://cldup.com/a-mtRlbi-O.png

 Clicking these would take the user to the admin panel for the specific
 Plugin.

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

From noreply at wordpress.org  Mon Oct 10 20:56:00 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 20:56:00 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.b024e62ddb97deec71d75d546e7c3fde@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by samuelsidler):

 Thinking longer term, ideally everything could be edited on the front-end,
 which would automatically sync the changes to SVN for the plugin author.
 Thinking about it from that point of view, "admin" access is really
 equivalent to "edit" access for a given plugin. Would an edit button/link
 make more sense than something called "admin"?

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

From noreply at wordpress.org  Mon Oct 10 21:01:13 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 21:01:13 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.b6a303b9c0a8315b33de16f1700f1fcc@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by moonomo):

 Replying to [comment:4 mapk]:
 > v3 - Link under the 'Download' button
 > https://cldup.com/uLCTIxlGg9.png

 This placement and style looks better than the others.

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

From noreply at wordpress.org  Mon Oct 10 21:32:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 10 Oct 2016 21:32:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.c50b7e218b819609b403bc2b7feed25e@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by ramiy):

 Replying to [comment:4 mapk]:
 > v1 - Button under the 'Download' button
 > https://cldup.com/2r9cLaqTvV.png
 >
 > v4 - Link in sidebar under meta data (or above)
 > https://cldup.com/a-mtRlbi-O.png

 I like the button and the sidebar options.

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

From noreply at wordpress.org  Tue Oct 11 00:14:37 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 00:14:37 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.cad36e3b513775596dd483d456aecf55@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by mapk):

 Replying to [comment:5 samuelsidler]:
 > Thinking longer term, ideally everything could be edited on the front-
 end, which would automatically sync the changes to SVN for the plugin
 author. Thinking about it from that point of view, "admin" access is
 really equivalent to "edit" access for a given plugin. Would an edit
 button/link make more sense than something called "admin"?

 It would if it only concerned this plugin, but ideally the user would be
 able to jump from plugin to plugin within this view... and see an overview
 of all their plugins together, so in that sense it becomes more of an
 admin.

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

From noreply at wordpress.org  Tue Oct 11 00:35:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 00:35:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications
 should have an option to match whole words only
In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
Message-ID: <073.a7e6d85f5ecc5d7be39e6ef0ae2ecf2b@wordpress.org>

#2119: Profiles: Notifications should have an option to match whole words only
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 Another use case is the #polyglots team suggests notification
 subscriptions to your locale, e.g `#pt-br` for Portuguese (Brazil), though
 subscribers to `#pt` for Portuguese (Portugal) would receive both locales
 notifications.

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

From noreply at wordpress.org  Tue Oct 11 01:13:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 01:13:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2127: enhancement: WordPress.tv:
 add an optional slug field for the video submission form
Message-ID: <047.774d7f3f5e1b6a43ab203b63bda8372f@wordpress.org>

#2127: enhancement: WordPress.tv: add an optional slug field for the video
submission form
--------------------------+-----------------
 Reporter:  Nao           |      Owner:
     Type:  enhancement   |     Status:  new
 Priority:  low           |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+-----------------
 Current submission form at http://wordpress.tv/submit-video/ generates a
 post where the slug is the title field.

 For some locales such as Japanese, the auto-generated slug is problematic
 because it uses percent-encoding and can be 1) hard to read, 2) very long,
 and 3) just not pretty.

 The slug for a video titled "CMS??????????????WordPress??
 ??????????" will become:

 {{{
 hiroshi-tokumaru-
 cms%e5%9b%9b%e5%a4%a9%e7%8e%8b%e3%81%b8%e3%81%ae%e6%94%bb%e6%92%83%e3%83%87%e3%83%a2%e3%82%92%e9%80%9a%e3%81%98%e3%81%a6%e3%80%81wordpress%e3%81%ae%e5%8a%b9%e6%9e%9c%e7%9a%84
 }}}

 I'd like to request an addition of an optional custom slug field.

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

From noreply at wordpress.org  Tue Oct 11 01:20:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 01:20:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2128: Add front-end readme
	validator
Message-ID: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>

#2128: Add front-end readme validator
------------------------------+--------------------------------------
 Reporter:  dd32              |      Owner:
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------------------------
 There needs to be a readme validator accessible to non-logged-in users.

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

From noreply at wordpress.org  Tue Oct 11 06:27:26 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 06:27:26 +0000 (UTC)
Subject: [wp-meta] [4212]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Remove wp-admin access and a bunch of code that's no
 longer needed.
Message-ID: <20161011062726.40CE610800F6@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 06:27:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 06:27:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.676cbc57b9938372490f931b7f4e5deb@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4212"]:
 {{{
 #!CommitTicketReference repository="" revision="4212"
 Plugin Directory: Remove wp-admin access and a bunch of code that's no
 longer needed.

 See #2111.
 }}}

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

From noreply at wordpress.org  Tue Oct 11 06:42:46 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 06:42:46 +0000 (UTC)
Subject: [wp-meta] [4213] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: Allow non-published plugins to be viewed on the front-end
 by reviewers and contributors /commiters/submitters of the plugin.
Message-ID: <20161011064246.3E90E10800F6@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 06:42:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 06:42:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.0a54d7df8f12e3ccd35ddd29e6c1ab26@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4213"]:
 {{{
 #!CommitTicketReference repository="" revision="4213"
 Plugin Directory: Allow non-published plugins to be viewed on the front-
 end by reviewers and contributors/commiters/submitters of the plugin.

 This also adds a notice on the top of plugin pages with the status of the
 plugin.

 See #2111.
 }}}

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

From noreply at wordpress.org  Tue Oct 11 08:27:15 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 08:27:15 +0000 (UTC)
Subject: [wp-meta] [4214]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Add a `plugin_committer` taxonomy and sync it with the
 svn_access table.
Message-ID: <20161011082715.75F6B1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 08:27:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 08:27:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.808655b8bec945b29be6c217cc9e88db@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4214"]:
 {{{
 #!CommitTicketReference repository="" revision="4214"
 Plugin Directory: Add a `plugin_committer` taxonomy and sync it with the
 svn_access table.
 The taxonomy is only used to ease querying, and allows for `/author/$self`
 to display both plugins you're listed as a contributor for and those you
 have commit access for.

 See #2111
 }}}

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

From noreply at wordpress.org  Tue Oct 11 11:22:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 11:22:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2126: Deter Developers from
 Leaving Reviews On Their Own Product
In-Reply-To: <051.dbb5835f62448a84c558890890be135f@wordpress.org>
References: <051.dbb5835f62448a84c558890890be135f@wordpress.org>
Message-ID: <066.3a38fccfd39c09ab311427291f406c03@wordpress.org>

#2126: Deter Developers from Leaving Reviews On Their Own Product
----------------------------+------------------
 Reporter:  Ipstenu         |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 To highlight an alternate case, before I had commit access to bbPress I
 wrote this review of bbPress:
 * https://wordpress.org/support/topic/learning-php-1/

 Side note: The review also doesn't add the CSS flair to the review
 highlighting that I am a "Plugin Author" either, it probably should

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

From noreply at wordpress.org  Tue Oct 11 11:41:13 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 11:41:13 -0000
Subject: [wp-meta] [Making WordPress.org] #2129: bbPress.org forum profiles
 should have a link to the WP.org profile
Message-ID: <050.985cd3a49c540bf3d52523ab88155de5@wordpress.org>

#2129: bbPress.org forum profiles should have a link to the WP.org profile
----------------------------+-----------------
 Reporter:  netweb          |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  buddypress.org  |   Keywords:
----------------------------+-----------------
 Follow up to #2068 for bbPress.org

 bbPress.org forum profiles should have a link to the users WP.org profile,
 like `@netweb on WordPress.org` on the WP.org profile itself.

 Creating a patch from [4206] for bbPress only in bb-base theme should be
 relatively straight forward.

 Note: Not required for Buddypress.org as Buddypress.org use BuddyPress
 member profiles

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

From noreply at wordpress.org  Tue Oct 11 11:42:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 11:42:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2119: Profiles: Notifications
 should have an option to match whole words only
In-Reply-To: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
References: <058.0e5ddec94026ef8887b7fb79e9528bc5@wordpress.org>
Message-ID: <073.2f446d8fbfafe526c19a3f75087b3d2d@wordpress.org>

#2119: Profiles: Notifications should have an option to match whole words only
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Profiles        |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 And subscribers to `#fr` for French (France) currently get notifications
 for things like `#front-page` :)

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

From noreply at wordpress.org  Tue Oct 11 12:31:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 12:31:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.de6e2a51b6e113de634ae475e46cb506@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 Looks like the script to calculate this data hasn't been updated to read
 from the bbPress2 tables after the forums migration.

 The script isn't open sourced, so I'd include a chunk of it, but It
 wouldn't do much help reading it..

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

From noreply at wordpress.org  Tue Oct 11 12:50:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 12:50:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2089: DevHub: No search form
	on 404 page
In-Reply-To: <058.1bb112179eee67a84a633d074b74ee8a@wordpress.org>
References: <058.1bb112179eee67a84a633d074b74ee8a@wordpress.org>
Message-ID: <073.e23094d31dd8976f53fdd22d95a939f3@wordpress.org>

#2089: DevHub: No search form on 404 page
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Developer Hub   |  Resolution:
 Keywords:  has-patch       |
----------------------------+------------------
Changes (by keesiemeijer):

 * keywords:   => has-patch


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

From noreply at wordpress.org  Tue Oct 11 13:22:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 13:22:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2126: Deter Developers from
 Leaving Reviews On Their Own Product
In-Reply-To: <051.dbb5835f62448a84c558890890be135f@wordpress.org>
References: <051.dbb5835f62448a84c558890890be135f@wordpress.org>
Message-ID: <066.dcae82206de6c9e6c19a93b78449c375@wordpress.org>

#2126: Deter Developers from Leaving Reviews On Their Own Product
----------------------------+------------------
 Reporter:  Ipstenu         |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Ipstenu):

 @netweb - As that happened ''before'' you had access then you wouldn't
 have the alert box :) No harm, no foul. Which is why I'm not asking for
 plugin author to be noted. We don't have a way to check, after the fact,
 if the review was left when someone wasn't an author/committer.

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

From noreply at wordpress.org  Tue Oct 11 13:59:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 13:59:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2130: Username not accepted when
 submitting a video
Message-ID: <051.13f83aff1840410cd05a55c10ae15edb@wordpress.org>

#2130: Username not accepted when submitting a video
--------------------------+-----------------
 Reporter:  casiepa       |      Owner:
     Type:  defect        |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+-----------------
 On the http://wordpress.tv/submit-video page, when adding a wordpress.org
 username like 'casiepa' or 'nao' results in an error:

 Error: please enter a valid WordPress.org username for the producer, or
 leave the field empty.

 Thanks, Pascal.

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

From noreply at wordpress.org  Tue Oct 11 18:33:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 18:33:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2114: Possible abuse on
 popular themes list based on active installs
In-Reply-To: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
References: <051.c2336c6ef6bfff003ca79f4dc2f83e8d@wordpress.org>
Message-ID: <066.fcf064945a6ad138cdfa9bf3cc8963be@wordpress.org>

#2114: Possible abuse on popular themes list based on active installs
-----------------------------+------------------
 Reporter:  acosmin          |       Owner:
     Type:  defect           |      Status:  new
 Priority:  low              |   Milestone:
Component:  Theme Directory  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by ionutn):

 Hey,

 For me this looks a directory related bug, we should somehow calculate the
 nr of active installs since the theme is live in the repo, it isn't
 perfect in all cases but better than what we have now :)

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

From noreply at wordpress.org  Tue Oct 11 18:49:59 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 18:49:59 +0000 (UTC)
Subject: [wp-meta] [4215]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/bbpress/user-profile.php: Forums Theme: Add user' s website to
 their support forum profile page.
Message-ID: <20161011184959.652AE1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 18:49:59 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 18:49:59 -0000
Subject: [wp-meta] [Making WordPress.org] #2116: Forums should have a
 way to view user's website URL from WP.org profile
In-Reply-To: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>
References: <058.0539b231d104ac25fa8b97f6176df8c7@wordpress.org>
Message-ID: <073.2a63c4e4e8edce89071ed05c3832247a@wordpress.org>

#2116: Forums should have a way to view user's website URL from WP.org profile
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4215"]:
 {{{
 #!CommitTicketReference repository="" revision="4215"
 Forums Theme: Add user's website to their support forum profile page.

 Fixes #2116.
 }}}

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

From noreply at wordpress.org  Tue Oct 11 18:52:07 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 18:52:07 +0000 (UTC)
Subject: [wp-meta] [4216]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-forums:
 Forums Theme: Add notice indicating that a topic is being held for
 moderation.
Message-ID: <20161011185207.E4D301080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 18:52:08 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 18:52:08 -0000
Subject: [wp-meta] [Making WordPress.org] #1561: Messages caught in the
 moderation queue need visual feedback
In-Reply-To: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
References: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
Message-ID: <073.1f102fed053c14212f8800c709332ac6@wordpress.org>

#1561: Messages caught in the moderation queue need visual feedback
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4216"]:
 {{{
 #!CommitTicketReference repository="" revision="4216"
 Forums Theme: Add notice indicating that a topic is being held for
 moderation.

 Can display one of five possible messages:

 * For moderators, that a topic is flagged as spam.
 * For moderators, that a topic is pending.
 * For blocked users, that the topic has been held for moderation by the
 automated system.
 * When a topic is pending for less than 96 hours, that the topic has been
 held for moderation and will be reviewed.
 * When a topic is pending for more than 96 hours, that the topic has been
 held for moderation but that moderators should be asked (via Slack) about
 it.

 Props SergeyBiryukov, coffee2code, Ipstenu.
 Fixes #1561.
 }}}

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

From noreply at wordpress.org  Tue Oct 11 19:11:10 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 19:11:10 +0000 (UTC)
Subject: [wp-meta] [4217]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: Add styling for a `<select> ` element
 which will be used for the editor on make/polyglots.
Message-ID: <20161011191110.961351080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 19:15:52 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 19:15:52 +0000 (UTC)
Subject: [wp-meta] [4218]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/style-rtl.css: Forums Theme: Align admin-links links to the
 left when RTL.
Message-ID: <20161011191552.E3C9E1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 19:19:38 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 11 Oct 2016 19:19:38 +0000 (UTC)
Subject: [wp-meta] [4219]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/functions.php: Forums Theme: Bump CSS versions for cache bust.
Message-ID: <20161011191938.D2FE21080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 11 19:15:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 19:15:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2104: Forums: Misaligned
 Reply link on RTL forums
In-Reply-To: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
References: <058.40be3560c0b464283d859dbfb905fde0@wordpress.org>
Message-ID: <073.034007b2b1923a5a8505f3d51f6d0395@wordpress.org>

#2104: Forums: Misaligned Reply link on RTL forums
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4218"]:
 {{{
 #!CommitTicketReference repository="" revision="4218"
 Forums Theme: Align admin-links links to the left when RTL.

 Props netweb.
 Fixes #2104.
 }}}

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

From noreply at wordpress.org  Tue Oct 11 20:52:51 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 20:52:51 -0000
Subject: [wp-meta] [Making WordPress.org] #1561: Messages caught in the
 moderation queue need visual feedback
In-Reply-To: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
References: <058.3b8e59f618cf3cce77ac7798049f26b2@wordpress.org>
Message-ID: <073.c3bfe05246ce17bd1ff348f41d5e1e7b@wordpress.org>

#1561: Messages caught in the moderation queue need visual feedback
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------

Comment (by coffee2code):

 The committed implementation of this will show at most one of five
 possible messages:

 * For moderators, if topic is flagged as spam:[[br]]`This post has been
 flagged as spam.`
 * For moderators, if topic is pending:[[br]]`This post is currently
 pending.`
 * For blocked author of a topic that is either pending or spam:[[br]]`This
 post has been held for moderation by our automated system.`
 * For author of a topic that is pending for less than 96 hours:[[br]]`This
 post has been held for moderation by our automated system. It will be
 reviewed within 72 hours.`
 * For author of a topic that is pending for more than 96 hours:[[br]]`This
 post was held for moderation by our automated system but has taken longer
 than expected to get approved. Please come to the #forums channel on <a
 href="https://make.wordpress.org/chat/">WordPress Slack</a> and let us
 know. Provide a link to the post.`

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

From noreply at wordpress.org  Tue Oct 11 21:39:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 21:39:14 -0000
Subject: [wp-meta] [Making WordPress.org] #1776: Allow multiple links to
 wordpress.org on make blogs
In-Reply-To: <050.6c9d97506c0a1ec004e8451dcd9cdfc6@wordpress.org>
References: <050.6c9d97506c0a1ec004e8451dcd9cdfc6@wordpress.org>
Message-ID: <065.d6a39e70f8de5ee04f0481464e760078@wordpress.org>

#1776: Allow multiple links to wordpress.org on make blogs
--------------------------------------+------------------
 Reporter:  jorbin                    |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:  needs-patch               |
--------------------------------------+------------------

Comment (by ocean90):

 The `$comment` parameter has been committed in [core38748].

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

From noreply at wordpress.org  Tue Oct 11 23:56:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 11 Oct 2016 23:56:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.c043303565a520e3ce09c68dde8c8ec8@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------
Changes (by mapk):

 * keywords:   => has-screenshots


Comment:

 Just trying to get some content onto a page to review. This is a mockup of
 a layout idea for the edit screen of the plugin. Most information is
 pulled directly from the existing wp-admin section that we have up right
 now.

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

 Notes:
 1. Top header section stays visible.
 2. Main content area shows a form for updating (fields copied from current
 wp-admin), and stats.
 3. Sidebar keeps some meta data visible but now some of it becomes
 editable. Committers and Authors are also added.
 4. Bottom section shows author's info and other plugins they developed.
 The dropdown would quickly jump the author to another plugin relating to
 this author.

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

From noreply at wordpress.org  Wed Oct 12 01:29:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 01:29:43 -0000
Subject: [wp-meta] [Making WordPress.org] #2130: Username not accepted
 when submitting a video
In-Reply-To: <051.13f83aff1840410cd05a55c10ae15edb@wordpress.org>
References: <051.13f83aff1840410cd05a55c10ae15edb@wordpress.org>
Message-ID: <066.a95e995329f9fdbc3503891dee47e199@wordpress.org>

#2130: Username not accepted when submitting a video
--------------------------+---------------------
 Reporter:  casiepa       |       Owner:
     Type:  defect        |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by dd32):

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


Comment:

 Thanks for reporting @casiepa!

 I've fixed this in the WordPress.tv codebase, which unfortunately is not
 open-sourced.

 This was broken when WordPress.tv switched to running WordPress 4.6 as the
 result from `wp_remote_retrieve_headers()` changed from an array to an
 object and subsequently `array_key_exists()` failed (cc @rmccue - no,
 nothing needs changing!)

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

From noreply at wordpress.org  Wed Oct 12 03:07:59 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 03:07:59 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.8e5daea99ccef21317befd5b02dca0e0@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 This should be fixed by [dotorg12504].
 I've done a manual glance at a few plugins and everything looks correct,
 can those of you who were seeing incorrect numbers check it's fixed for
 you?

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

From noreply at wordpress.org  Wed Oct 12 04:03:11 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 04:03:11 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.fd479b245d5b5bbb50d25f08bace0d44@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by jkohlbach):

 Looks good on my end so far!

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

From noreply at wordpress.org  Wed Oct 12 04:08:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 04:08:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.579371b3096ce6b0a262d334513e4e3a@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by codeofconduct):

 This is fixed for my plugin. Thanks so much!

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

From noreply at wordpress.org  Wed Oct 12 04:19:54 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 04:19:54 -0000
Subject: [wp-meta] [Making WordPress.org] #7: Search individual
	plugin/theme forums
In-Reply-To: <052.23d43efa7253dd627a836f71be9519f0@wordpress.org>
References: <052.23d43efa7253dd627a836f71be9519f0@wordpress.org>
Message-ID: <067.816cd979b48a65988fe4fe152b608c1b@wordpress.org>

#7: Search individual plugin/theme forums
---------------------------------------+------------------
 Reporter:  Daedalon                   |       Owner:
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Support Forums             |  Resolution:
 Keywords:  needs-refresh 2nd-opinion  |
---------------------------------------+------------------

Comment (by planetside):

 Sweet jesus, we need search for individual plugin support forums!
 Wordpress development is rapid and impressive, yet this request has been
 sitting here, unaddressed, for 3 years? Confusing and disappointing.

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

From noreply at wordpress.org  Wed Oct 12 11:13:18 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 11:13:18 -0000
Subject: [wp-meta] [Making WordPress.org] #2130: Username not accepted
 when submitting a video
In-Reply-To: <051.13f83aff1840410cd05a55c10ae15edb@wordpress.org>
References: <051.13f83aff1840410cd05a55c10ae15edb@wordpress.org>
Message-ID: <066.244533ddbbd96bbdb9632374ad603a94@wordpress.org>

#2130: Username not accepted when submitting a video
--------------------------+---------------------
 Reporter:  casiepa       |       Owner:  dd32
     Type:  defect        |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by dd32):

 * owner:   => dd32


Comment:

 In [changeset:"4220"]:
 {{{
 #!CommitTicketReference repository="" revision="4220"
 WordPress.tv: Fix `wporg_username_exists()` to work after the `Requests`
 `WP_HTTP` changes in 4.6.

 The response from `wp_remote_retrieve_headers()` changed from a "real
 array" to an object implementing ArrayAccess, `array_key_exists()` is
 pretty much the one function that could've been used here that was
 incompatible with it.

 Fixes #2130
 }}}

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

From noreply at wordpress.org  Wed Oct 12 11:13:17 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 11:13:17 +0000 (UTC)
Subject: [wp-meta] [4220]
 sites/trunk/wordpress.tv/public_html/wp-content/themes/wptv2/
 functions.php: WordPress.tv: Fix `wporg_username_exists() ` to work after
 the `Requests` `WP_HTTP` changes in 4.6.
Message-ID: <20161012111317.C4CA21080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 11:34:22 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 11:34:22 +0000 (UTC)
Subject: [wp-meta] [4221]
 sites/trunk/wordpress.tv/public_html/wp-content/themes/wptv2: WordPress.tv:
 Allow subtitling privately published posts.
Message-ID: <20161012113422.5F5781080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 11:39:45 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 11:39:45 +0000 (UTC)
Subject: [wp-meta] [4222]
 sites/trunk/wordpress.tv/public_html/wp-content/themes/wptv2: WordPress.tv:
 Fix up the footer spacing.
Message-ID: <20161012113945.9D2961080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 11:57:11 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 11:57:11 -0000
Subject: [wp-meta] [Making WordPress.org] #2131: Submit video page CSS issue
Message-ID: <051.01b7ef4aed1d1c782674f43b6beb6a7d@wordpress.org>

#2131: Submit video page CSS issue
--------------------------+-----------------
 Reporter:  casiepa       |      Owner:
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+-----------------
 On page http://wordpress.tv/submit-video/ the very last line where the
 video filename is to be attached has arrows for scrolling, but there is
 nothing to scroll.

 In the CSS `.video-upload p { overflow: auto; }` is probably the issue
 (thanks @dd32)
 As @ocean90 indicated : A proper `clearfix` should be used instead.

 Thanks for changing.

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

From noreply at wordpress.org  Wed Oct 12 12:43:49 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 12:43:49 +0000 (UTC)
Subject: [wp-meta] [4223] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: Set `svn:eol-style: native` on all files.
Message-ID: <20161012124349.D9AE41080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 13:03:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 13:03:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.90f09e12e291a04992e00aa65ea84926@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4224"]:
 {{{
 #!CommitTicketReference repository="" revision="4224"
 Plugin Directory: Add the first foundations for the front-end admin
 /plugin-edit screen.

 See #2111
 }}}

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

From noreply at wordpress.org  Wed Oct 12 13:03:26 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 13:03:26 +0000 (UTC)
Subject: [wp-meta] [4224] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: Add the first foundations for the front-end
 admin/plugin-edit screen.
Message-ID: <20161012130326.9A0AD1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 15:31:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 15:31:29 -0000
Subject: [wp-meta] =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232132=3A_Chang?=
 =?utf-8?q?e_=E2=80=9CBrowse_in_Trac=E2=80=9D_link_to_something_more_meani?=
 =?utf-8?q?ngful?=
Message-ID: <053.aa05bdc8881b9ca848cccfac499dca40@wordpress.org>

#2132: Change ?Browse in Trac? link to something more meaningful
------------------------------+-----------------
 Reporter:  geekysoft         |      Owner:
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+-----------------
 Please split the ?Browse in Track? link on individual plugin pages into
 two links to facilitate better use of the Track system and encourage more
 contributions.

 <a href="https://plugins.trac.wordpress.org/query?status=!closed&component
 =PLUGIN-SLUG">List all known issues</a>

 <a href="https://plugins.trac.wordpress.org/newticket?component=PLUGIN-
 SLUG">Report a new issue or submit patches</a>

 I strongly believe that having these two links instead of the rather
 cryptic ?Browse in Trac? link will increase engagement. The suggested
 links don?t require prior knowledge of what Trac is and makes Trac easier
 to use for new users by bypassing the complications of locating the
 correct component (and knowing what component to choose from a list of
 thousands of plugins). Automatically assigning/notifying the plugin author
 is of course required for this to work properly.

 Only 1906 out of the 47 161 total plugins (4,04 %) have components in
 Trac. Why? Either get rid of Trac entirely to not confuse people, or fix
 it so it works for all plugins.

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

From noreply at wordpress.org  Wed Oct 12 15:52:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 15:52:03 -0000
Subject: [wp-meta] [Making WordPress.org] #1806: Re-add subscriptions to
	o2
In-Reply-To: <049.6d5fc620f1020bd9eaa17b9d8657ca6d@wordpress.org>
References: <049.6d5fc620f1020bd9eaa17b9d8657ca6d@wordpress.org>
Message-ID: <064.4f24dca170ec1b838d33c803ed7b5766@wordpress.org>

#1806: Re-add subscriptions to o2
--------------------------------------+---------------------
 Reporter:  pento                     |       Owner:
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------
Changes (by ocean90):

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


Comment:

 The notice was fixed in [dotorg12352].

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

From noreply at wordpress.org  Wed Oct 12 16:30:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 16:30:49 -0000
Subject: [wp-meta]
 =?utf-8?q?=5BMaking_WordPress=2Eorg=5D_=232132=3A_Chang?=
 =?utf-8?q?e_=E2=80=9CBrowse_in_Trac=E2=80=9D_link_to_something_more_meani?=
 =?utf-8?q?ngful?=
In-Reply-To: <053.aa05bdc8881b9ca848cccfac499dca40@wordpress.org>
References: <053.aa05bdc8881b9ca848cccfac499dca40@wordpress.org>
Message-ID: <068.e93903d89cf86eb1ef9bad7a718447e0@wordpress.org>

#2132: Change ?Browse in Trac? link to something more meaningful
------------------------------+----------------------
 Reporter:  geekysoft         |       Owner:
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  wontfix
 Keywords:                    |
------------------------------+----------------------
Changes (by Otto42):

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


Comment:

 Currently, the plugins trac ticketing system is not actually used for
 plugin bug-reports and patch submissions. It's there, but really, nobody
 ever really used it and I'd guess that it's likely that we'll simply wipe
 it and delete all those tickets.

 We really only use the plugins.trac as a convienent way to look at the SVN
 for diffs and the like. There's no point in adding a "new ticket" link
 when we don't really want people adding new tickets there where plugin
 authors will never actually see them.

 By and large, the plugin SVN is not meant for development and
 collaboration. It's a release repository. Yes, you can do development on
 it, but most people prefer to collaborate on systems like github, and then
 push only the final release versions to the SVN for deployment to the
 directory.

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

From noreply at wordpress.org  Wed Oct 12 18:16:00 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 18:16:00 -0000
Subject: [wp-meta] =?utf-8?b?W01ha2luZyBXb3JkUHJlc3Mub3JnXSAjMjEzMzog4oCc?=
 =?utf-8?q?Last_updated=E2=80=9D_time_not_updated_when_updating_=E2=80=9CT?=
 =?utf-8?q?ested_up_to=E2=80=9D_in_repo?=
Message-ID: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>

#2133: ?Last updated? time not updated when updating ?Tested up to? in repo
------------------------------+-----------------
 Reporter:  geekysoft         |      Owner:
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+-----------------
 Look at the ?Last updated? time on:
 https://wordpress.org/plugins-wp/cache-control/
 https://wordpress.org/plugins/cache-control/

 Last updated was updated on the old version when I committed rev. 1513554
 where I increased the version number in the ?Tested up to? field. So the
 old plugin directory right now shows last updated 10 minutes ago, and the
 new directory design says it was 3 months ago. Both show the updated
 ?Tested up to? version number.

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

From noreply at wordpress.org  Wed Oct 12 18:44:45 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 18:44:45 +0000 (UTC)
Subject: [wp-meta] [4225]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/bbpress/loop-posts.php: Forums Theme: Show context for posts
 listed in special views (e.g.
Message-ID: <20161012184445.311801080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 18:44:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 18:44:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2101: Forums:
 Spam/Pending/Archived views should display topic titles
In-Reply-To: <058.5afb3a9b1f90b5117ed8ae807d3afbd6@wordpress.org>
References: <058.5afb3a9b1f90b5117ed8ae807d3afbd6@wordpress.org>
Message-ID: <073.0c0a9d11e0a07b483efb420fc2ebfa99@wordpress.org>

#2101: Forums: Spam/Pending/Archived views should display topic titles
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4225"]:
 {{{
 #!CommitTicketReference repository="" revision="4225"
 Forums Theme: Show context for posts listed in special views (e.g.
 spam/pending/archived).

 * Always show linked forum name.
 * Show topic name for topic posts.
 * Show linked topic name for reply posts.

 Props netweb, coffee2code.
 Fixes #2101.
 }}}

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

From noreply at wordpress.org  Wed Oct 12 18:48:21 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 18:48:21 +0000 (UTC)
Subject: [wp-meta] [4226]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/bbpress/loop-posts.php: Forums Theme: Remove unnecessary ( and
 incorrect) listing header from special views.
Message-ID: <20161012184821.D26B01080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 19:35:47 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 19:35:47 -0000
Subject: [wp-meta] [Making WordPress.org] #1825: Style handbook with new
	O2 design
In-Reply-To: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
References: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
Message-ID: <068.39f5e2917c884d2dfb158f17191ac260@wordpress.org>

#1825: Style handbook with new O2 design
--------------------------------------+------------------
 Reporter:  chriscct7                 |       Owner:
     Type:  task                      |      Status:  new
 Priority:  high                      |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by ocean90):

 In [changeset:"4227"]:
 {{{
 #!CommitTicketReference repository="" revision="4227"
 Breathe: Add some basic styling for handbooks's "Table of Contents" box.

 See #1825.
 }}}

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

From noreply at wordpress.org  Wed Oct 12 19:35:47 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 19:35:47 +0000 (UTC)
Subject: [wp-meta] [4227]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: Add some basic styling for handbooks's "
 Table of Contents" box.
Message-ID: <20161012193547.71FEF1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 19:48:23 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 19:48:23 -0000
Subject: [wp-meta] [Making WordPress.org] #2035: Improve i18n in
	Ratings_Compat
In-Reply-To: <058.5cf9adfc0148e897fb9b8105bf94e1c1@wordpress.org>
References: <058.5cf9adfc0148e897fb9b8105bf94e1c1@wordpress.org>
Message-ID: <073.6b8108858d7bd027928960601a38b676@wordpress.org>

#2035: Improve i18n in Ratings_Compat
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+--------------------------

Comment (by coffee2code):

 In [changeset:"4228"]:
 {{{
 #!CommitTicketReference repository="" revision="4228"
 Support Forums: Another i18n improvement in Ratings_Compat.

 * Move HTML out from translatable string
 * Add missing text domain and translator comment
 * Add use of `number_format_i18n()`

 Props SergeyBiryukov.
 See #2035.
 }}}

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

From noreply at wordpress.org  Wed Oct 12 19:48:22 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 19:48:22 +0000 (UTC)
Subject: [wp-meta] [4228]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-ratings-compat.php: Support Forums: Another i18n
 improvement in Ratings_Compat.
Message-ID: <20161012194822.E70321080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 20:09:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 20:09:49 -0000
Subject: [wp-meta] [Making WordPress.org] #2035: Improve i18n in
	Ratings_Compat
In-Reply-To: <058.5cf9adfc0148e897fb9b8105bf94e1c1@wordpress.org>
References: <058.5cf9adfc0148e897fb9b8105bf94e1c1@wordpress.org>
Message-ID: <073.a2111f1af8cd73372dfebb9a5e851ff4@wordpress.org>

#2035: Improve i18n in Ratings_Compat
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+--------------------------

Comment (by coffee2code):

 In [changeset:"4229"]:
 {{{
 #!CommitTicketReference repository="" revision="4229"
 Support Forums: Use `%s` instead of `%d` as placeholder since markup and a
 potentially commaified value is being inserted rather than a simple
 number.

 See #2035, r4228.
 }}}

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

From noreply at wordpress.org  Wed Oct 12 20:09:49 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 20:09:49 +0000 (UTC)
Subject: [wp-meta] [4229]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-ratings-compat.php: Support Forums: Use `%s`
 instead of `%d` as placeholder since markup and a potentially commaified
 value is being inserted rather than a simple number.
Message-ID: <20161012200949.6C0771080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 20:28:51 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 20:28:51 +0000 (UTC)
Subject: [wp-meta] [4230]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-ratings-compat.php: Support Forums: Allow for
 pluralization of the string for the number of stars in the ratings widget.
Message-ID: <20161012202851.D484C1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 12 20:28:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 20:28:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2035: Improve i18n in
	Ratings_Compat
In-Reply-To: <058.5cf9adfc0148e897fb9b8105bf94e1c1@wordpress.org>
References: <058.5cf9adfc0148e897fb9b8105bf94e1c1@wordpress.org>
Message-ID: <073.3345d73d10296cbc412f327226fd694f@wordpress.org>

#2035: Improve i18n in Ratings_Compat
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4230"]:
 {{{
 #!CommitTicketReference repository="" revision="4230"
 Support Forums: Allow for pluralization of the string for the number of
 stars in the ratings widget.

 Syncs the ratings widget with changes made to the old plugin directory a
 year ago to handle just this very thing.

 Props SergeyBiryukov.
 Fixes #2035.
 }}}

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

From noreply at wordpress.org  Wed Oct 12 20:35:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 12 Oct 2016 20:35:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2090: Forum Translation
 Housekeeping Ideas
In-Reply-To: <053.d983f07e58b45670b44480b8a45353b6@wordpress.org>
References: <053.d983f07e58b45670b44480b8a45353b6@wordpress.org>
Message-ID: <068.52b0189b70cdde29e8520eb757e887f4@wordpress.org>

#2090: Forum Translation Housekeeping Ideas
------------------------------+--------------------------
 Reporter:  Presskopp         |       Owner:  coffee2code
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Support Forums    |  Resolution:  fixed
 Keywords:  has-patch commit  |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4231"]:
 {{{
 #!CommitTicketReference repository="" revision="4231"
 Support Forums: I18n improvement in Ratings_Compat to move HTML out from
 translatable string.

 Props SergeyBiryukov.
 Fixes #2090.
 }}}

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

From noreply at wordpress.org  Wed Oct 12 20:35:51 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 12 Oct 2016 20:35:51 +0000 (UTC)
Subject: [wp-meta] [4231]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-ratings-compat.php: Support Forums: I18n
 improvement in Ratings_Compat to move HTML out from translatable string.
Message-ID: <20161012203551.C260C1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 13 00:04:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 00:04:57 -0000
Subject: [wp-meta]
 =?utf-8?b?W01ha2luZyBXb3JkUHJlc3Mub3JnXSAjMjEzMzog4oCc?=
 =?utf-8?q?Last_updated=E2=80=9D_time_not_updated_when_updating_=E2=80=9CT?=
 =?utf-8?q?ested_up_to=E2=80=9D_in_repo?=
In-Reply-To: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
References: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
Message-ID: <068.5b999f21a34058349f7fce8b121e292e@wordpress.org>

#2133: ?Last updated? time not updated when updating ?Tested up to? in repo
------------------------------+---------------------------------------
 Reporter:  geekysoft         |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * milestone:   => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Thu Oct 13 00:06:33 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 00:06:33 -0000
Subject: [wp-meta] [Making WordPress.org] #2128: Add front-end readme
	validator
In-Reply-To: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
References: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
Message-ID: <063.76c4c951bd2f5b29d5ee174d5d78052f@wordpress.org>

#2128: Add front-end readme validator
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:  tellyworth
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

 * owner:   => tellyworth
 * status:  new => accepted


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

From noreply at wordpress.org  Thu Oct 13 00:31:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 00:31:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
In-Reply-To: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
References: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
Message-ID: <073.49489c1f7237973a9e38fa13129a7c2b@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #1984

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

From noreply at wordpress.org  Thu Oct 13 00:35:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 00:35:02 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.ad91da4d1765e8cbc0057f0a2b1c26eb@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by wfasa):

 I just tested this and I can't seem to get the total number to update.
 When I set a thread to resolved it is not immediately reflected on the
 first page. Is there a delay in this number being updated? Thanks!

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

From noreply at wordpress.org  Thu Oct 13 00:30:08 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 00:30:08 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
Message-ID: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 Since [4225], Spam/Pending/Archived views have some context for posts
 (i.e. forum name, topic name, topic link).

 However, if you follow the topic/reply links from those views, you can't
 see the actual spam/pending/archived post on the topic page, because
 `?view=all` is missing in the URL.

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

From noreply at wordpress.org  Thu Oct 13 02:30:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 02:30:43 -0000
Subject: [wp-meta]
 =?utf-8?b?W01ha2luZyBXb3JkUHJlc3Mub3JnXSAjMjEzMzog4oCc?=
 =?utf-8?q?Last_updated=E2=80=9D_time_not_updated_when_updating_=E2=80=9CT?=
 =?utf-8?q?ested_up_to=E2=80=9D_in_repo?=
In-Reply-To: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
References: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
Message-ID: <068.8ba60406ab876ef3babe0cc98795537c@wordpress.org>

#2133: ?Last updated? time not updated when updating ?Tested up to? in repo
------------------------------+-------------------------
 Reporter:  geekysoft         |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  worksforme
 Keywords:                    |
------------------------------+-------------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => worksforme
 * milestone:  Plugin Directory v3 - M9 =>


Comment:

 Not sure what the problem was here, but it's fixed.

 I suspect it was a cache that didn't clear correctly, as I saw it
 incorrect earlier, but is now correct.
 I haven't been able to duplicate a bad cache either though.

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

From noreply at wordpress.org  Thu Oct 13 05:53:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 05:53:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
In-Reply-To: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
References: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
Message-ID: <073.88c839763d319a81a4ab7fc40c529434@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+--------------------------
Changes (by coffee2code):

 * owner:   => coffee2code
 * status:  new => accepted


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

From noreply at wordpress.org  Thu Oct 13 06:41:33 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 06:41:33 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.110508775c4cc20da1217aba2d3307f8@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+---------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------
Changes (by Clorith):

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


Comment:

 @wfasa That's expected, there's caching in place so numbers won't
 instantly update anywhere on the front end.

 Can confirm it's working as expected now, marking as fixed.

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

From noreply at wordpress.org  Thu Oct 13 09:31:21 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 09:31:21 -0000
Subject: [wp-meta] [Making WordPress.org] #2135: Support Forums: old link
 format doesn't work anymore
Message-ID: <051.c6ffb94598e097b652f9fd2d70723a8b@wordpress.org>

#2135: Support Forums: old link format doesn't work anymore
----------------------------+-----------------
 Reporter:  jeherve         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 Steps to reproduce:

 1. Go to Google.com
 2. Search for a specific string in an old support forum thread, e.g.
 {{{site:http://wordpress.org/support/topic/ jetpack safecss}}}
 3. You'll find links to old forum threads:

     - https://wordpress.org/support/topic/2411469
     - https://wordpress.org/support/topic/1496215

 Those links don't work anymore. I'm afraid a lot of people won't be able
 to reach the WordPress.org forums when googling for answers to old
 questions.

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

From noreply at wordpress.org  Thu Oct 13 09:41:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 09:41:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2136: O2 - missing string
Message-ID: <054.e2576647fa4a5ae493b8cc6c6a7060c8@wordpress.org>

#2136: O2 - missing string
--------------------------------------+-----------------
 Reporter:  adrian.pop                |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+-----------------
 The label of the checkbox "Notify me of new comments via email." is
 missing from the translation project.

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

From noreply at wordpress.org  Thu Oct 13 09:59:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 09:59:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2135: Support Forums: old
 link format doesn't work anymore
In-Reply-To: <051.c6ffb94598e097b652f9fd2d70723a8b@wordpress.org>
References: <051.c6ffb94598e097b652f9fd2d70723a8b@wordpress.org>
Message-ID: <066.68ea39f42a6d384fcb48d33e79b00a6d@wordpress.org>

#2135: Support Forums: old link format doesn't work anymore
----------------------------+------------------------
 Reporter:  jeherve         |       Owner:
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  duplicate
 Keywords:                  |
----------------------------+------------------------
Changes (by netweb):

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


Comment:

 Duplicate of #1954.

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

From noreply at wordpress.org  Thu Oct 13 14:43:37 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 14:43:37 -0000
Subject: [wp-meta] [Making WordPress.org] #2136: O2 - missing string
In-Reply-To: <054.e2576647fa4a5ae493b8cc6c6a7060c8@wordpress.org>
References: <054.e2576647fa4a5ae493b8cc6c6a7060c8@wordpress.org>
Message-ID: <069.0baf34ba5a86743abe94fdca6dbdd796@wordpress.org>

#2136: O2 - missing string
--------------------------------------+------------------
 Reporter:  adrian.pop                |       Owner:
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by Otto42):

 That string is not in O2, it's in the mu-plugin named "jetpack-follow-
 link-for-o2.php" and it doesn't have a proper text-domain.

 @ocean90 Not sure what text-domain that one should have to get into
 translate.w.org properly. wporg?

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

From noreply at wordpress.org  Thu Oct 13 15:40:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 15:40:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2137: Full Reviews no longer show
 when looking at ratings.
Message-ID: <051.fa4d463ecf1a348962cd4cbdefff3124@wordpress.org>

#2137: Full Reviews no longer show when looking at ratings.
---------------------+-------------------------------------
 Reporter:  jdailey  |      Owner:
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:  ui-feedback ux-feedback
---------------------+-------------------------------------
 The new UI looks nice but removing the review body text makes it very
 difficult to look through and compare reviews. I am only seeing the
 ability to click into every review based on its title. Many of the review
 titles are the same and don't say much about the users experience and why
 they liked or disliked the plugin/theme they are writing about.

 If it is a space issue could we show at least first sentence with a read
 more option? This would give people investigating a plugin a better sense
 of what the author likes or dislikes about the plugin.

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

From noreply at wordpress.org  Thu Oct 13 23:11:05 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Oct 2016 23:11:05 +0000 (UTC)
Subject: [wp-meta] [4232]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-moderators.php: Support Forums,
 Moderators:  Add class constant VIEWS to list moderator-only views.
Message-ID: <20161013231105.35E0F1080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 13 23:11:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 23:11:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
In-Reply-To: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
References: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
Message-ID: <073.72274d6d52fb7f3094810d03ba251ebc@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  accepted
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+--------------------------

Comment (by coffee2code):

 In [changeset:"4232"]:
 {{{
 #!CommitTicketReference repository="" revision="4232"
 Support Forums, Moderators: Add class constant VIEWS to list moderator-
 only views.

 See #2134.
 }}}

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

From noreply at wordpress.org  Thu Oct 13 23:26:24 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 13 Oct 2016 23:26:24 +0000 (UTC)
Subject: [wp-meta] [4233]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-forums/bbpress/loop-posts.php: Forums Theme: Append '?view=all' to
 context forum and topic links for posts listed in moderator views ( e.g.
Message-ID: <20161013232624.2ED011080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 13 23:26:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 13 Oct 2016 23:26:24 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
In-Reply-To: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
References: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
Message-ID: <073.1573308a2b15bdf577c523cb435145fe@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4233"]:
 {{{
 #!CommitTicketReference repository="" revision="4233"
 Forums Theme: Append '?view=all' to context forum and topic links for
 posts listed in moderator views (e.g. spam/pending/archived).

 Fixes #2134.
 }}}

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

From noreply at wordpress.org  Fri Oct 14 00:59:17 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 00:59:17 -0000
Subject: [wp-meta] [Making WordPress.org] #1984: Forums: ?view=all link
 should be more noticeable and always shown for moderators
In-Reply-To: <058.f58c421c9dc44dc7c8d200e9601fadf2@wordpress.org>
References: <058.f58c421c9dc44dc7c8d200e9601fadf2@wordpress.org>
Message-ID: <073.26303f4a3b949b1bf7fb6bd1201e8a2e@wordpress.org>

#1984: Forums: ?view=all link should be more noticeable and always shown for
moderators
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 Related: #bbPress2938

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

From noreply at wordpress.org  Fri Oct 14 00:59:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 00:59:25 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
In-Reply-To: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
References: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
Message-ID: <073.a2ba0bbb325444b9fcd9c305a8b49dd0@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------

Comment (by netweb):

 Related: #bbPress2938

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

From noreply at wordpress.org  Fri Oct 14 01:58:48 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 01:58:48 -0000
Subject: [wp-meta] [Making WordPress.org] #2102: Missing i18n in bb-base
	theme
In-Reply-To: <058.a89ea38c205dad7ebd7442aff5180413@wordpress.org>
References: <058.a89ea38c205dad7ebd7442aff5180413@wordpress.org>
Message-ID: <073.88ea8e8aa20116026a72efe07f0020b6@wordpress.org>

#2102: Missing i18n in bb-base theme
----------------------------+-----------------------
 Reporter:  SergeyBiryukov  |       Owner:  netweb
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:
Component:  bbpress.org     |  Resolution:
 Keywords:  has-patch       |
----------------------------+-----------------------
Changes (by coffee2code):

 * owner:   => netweb
 * status:  new => assigned


Comment:

 Assigning to you @netweb (along with #1284 and #1285) since it seems you
 have them in hand.

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

From noreply at wordpress.org  Fri Oct 14 02:00:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 02:00:26 -0000
Subject: [wp-meta] [Making WordPress.org] #1284: BuddyPress.org - String
 localization
In-Reply-To: <049.c90b42371a13fa881ceebe17fa81506c@wordpress.org>
References: <049.c90b42371a13fa881ceebe17fa81506c@wordpress.org>
Message-ID: <064.48824bb3dcd15895bee819db50922afd@wordpress.org>

#1284: BuddyPress.org - String localization
-------------------------------------+-----------------------
 Reporter:  ramiy                    |       Owner:  netweb
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  buddypress.org           |  Resolution:
 Keywords:  has-patch needs-refresh  |
-------------------------------------+-----------------------
Changes (by coffee2code):

 * owner:   => netweb
 * status:  new => assigned


Comment:

 Assigning to you @netweb (along with #1285 and #2102) since it seems you
 [https://meta.trac.wordpress.org/ticket/2102#comment:1 have them in hand].

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

From noreply at wordpress.org  Fri Oct 14 02:00:48 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 02:00:48 -0000
Subject: [wp-meta] [Making WordPress.org] #1285: bbPress.org - String
	localization
In-Reply-To: <049.77d30d039155e50178a6341a4b8a4263@wordpress.org>
References: <049.77d30d039155e50178a6341a4b8a4263@wordpress.org>
Message-ID: <064.109c2cdc000021abaa7d76ec7f00d3ae@wordpress.org>

#1285: bbPress.org - String localization
-------------------------+-----------------------
 Reporter:  ramiy        |       Owner:  netweb
     Type:  defect       |      Status:  assigned
 Priority:  normal       |   Milestone:
Component:  bbpress.org  |  Resolution:
 Keywords:  has-patch    |
-------------------------+-----------------------
Changes (by coffee2code):

 * owner:   => netweb
 * status:  new => assigned


Comment:

 Assigning to you @netweb (along with #1284 and #2102) since it seems you
 [https://meta.trac.wordpress.org/ticket/2102#comment:1 have them in hand].

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

From noreply at wordpress.org  Fri Oct 14 02:13:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 02:13:50 -0000
Subject: [wp-meta] [Making WordPress.org] #2138: Update bbPress and
 BuddyPress "standalone" PTE projects
Message-ID: <050.90883f4166dad9870d2fa8e89e9a1cb7@wordpress.org>

#2138: Update bbPress and BuddyPress "standalone" PTE projects
--------------------------------------+-----------------
 Reporter:  netweb                    |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+-----------------
 Previously bbPress and BuddyPress translation projects were "standalone"
 translation projects, and had their own sections in the Translation Editor
 UI:

 [[Image(https://cldup.com/5-Dh8djnYP.png)]]

 This is no longer the case, the bbPress and BuddyPress translation
 projects are no longer standalone translation projects, if the UI cannot
 facilitate an updated path for these two plugins they should be removed
 from the UI.

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

From noreply at wordpress.org  Fri Oct 14 02:36:44 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 02:36:44 +0000 (UTC)
Subject: [wp-meta] [4234]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums: Sort plugin
 committer feed by date rather than by post id.
Message-ID: <20161014023644.5DD9A108059F@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 02:36:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 02:36:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.2918adc56a9e891207461377218731cd@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by jmdodd):

 In [changeset:"4234"]:
 {{{
 #!CommitTicketReference repository="" revision="4234"
 Support Forums: Sort plugin committer feed by date rather than by post id.

 Because the plugin reviews forum was imported after the plugin support
 forum, the topic ids are not a reliable sort order for the combined
 results.

 See #2071.
 }}}

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

From noreply at wordpress.org  Fri Oct 14 02:44:36 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 02:44:36 -0000
Subject: [wp-meta] [Making WordPress.org] #2134: Forums:
 Spam/Pending/Archived views should append ?view=all to topic/reply links
In-Reply-To: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
References: <058.23aadf4a6861d8181c912eb0ff11ad69@wordpress.org>
Message-ID: <073.ba7960d17496da5d1b725eb3c88220d3@wordpress.org>

#2134: Forums: Spam/Pending/Archived views should append ?view=all to topic/reply
links
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  reopened
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+--------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Noticed a couple of things:

 * `In reply to:` is a link, `As the topic:` is not. It should be a link
 too for consistency.
 * Forum and topic links now have `?view=all`, but individual post links in
 `.bbp-topic-post-date` and `.bbp-reply-post-date` do not, so you have to
 additionally scroll to the post you clicked on, and it might not even be
 on the first page.

 [attachment:meta-2134.patch] handles the first point. Should the second
 point wait for #bbPress2938?

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

From noreply at wordpress.org  Fri Oct 14 02:57:17 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 02:57:17 +0000 (UTC)
Subject: [wp-meta] [4235]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-directory-compat.php: Support Forums: Allow plugin
 contributors to mark a topic as resolved.
Message-ID: <20161014025717.C497D108059F@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 02:57:18 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 02:57:18 -0000
Subject: [wp-meta] [Making WordPress.org] #1413: Support Forums: allow
 all plugin authors to mark threads as resolved and stick threads
In-Reply-To: <051.f7e8abd80fbc33abf4ab1498cbf7f562@wordpress.org>
References: <051.f7e8abd80fbc33abf4ab1498cbf7f562@wordpress.org>
Message-ID: <066.85b66bacf210dbe19e9b5b251dac5369@wordpress.org>

#1413: Support Forums: allow all plugin authors to mark threads as resolved and
stick threads
----------------------------+-----------------------
 Reporter:  jeherve         |       Owner:  Otto42
     Type:  enhancement     |      Status:  reopened
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by jmdodd):

 In [changeset:"4235"]:
 {{{
 #!CommitTicketReference repository="" revision="4235"
 Support Forums: Allow plugin contributors to mark a topic as resolved.

 See #1413.
 }}}

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

From noreply at wordpress.org  Fri Oct 14 05:09:31 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 05:09:31 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.c5b54cf4af2e73289eed26d86560cfa6@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by StephenCronin):

 @jmdodd Ah, that explains it. I was just about to post that 2 new support
 posts have now appeared in my feed - now I know why. Thanks

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

From noreply at wordpress.org  Fri Oct 14 06:00:10 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 06:00:10 -0000
Subject: [wp-meta] [Making WordPress.org] #2139: The WordPress Swag store
 doesn't send email notifications when items are restocked
Message-ID: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>

#2139: The WordPress Swag store doesn't send email notifications when items are
restocked
---------------------+-----------------------------
 Reporter:  netweb   |      Owner:
     Type:  defect   |     Status:  new
 Priority:  normal   |  Milestone:
Component:  General  |   Keywords:  has-screenshots
---------------------+-----------------------------
 For example WP coffee mugs https://mercantile.wordpress.org/product
 /wordpress-coffee-mug/

 These are (at time of writing) currently in stock, I'd previously added my
 email address to be notified when new stock was available and an email
 never arrived.

 FYI: I may have added my email to this coffee mug item half a dozen times
 over the past couple of years

 The following item is out of stock and I've just added my email address
 and clicked "Join waitlist"
 * https://mercantile.wordpress.org/product/samurai-wapuu-sticker/
 * https://cloudup.com/cnTf1jReNdC

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

From noreply at wordpress.org  Fri Oct 14 08:10:23 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 08:10:23 -0000
Subject: [wp-meta] [Making WordPress.org] #2139: The WordPress Swag
 store doesn't send email notifications when items are restocked
In-Reply-To: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
References: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
Message-ID: <065.49288cdd644a9779882ffdb3e004b346@wordpress.org>

#2139: The WordPress Swag store doesn't send email notifications when items are
restocked
-----------------------------+------------------
 Reporter:  netweb           |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by samuelsidler):

 I've forwarded this to the group that works on the store.

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

From noreply at wordpress.org  Fri Oct 14 09:04:28 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 09:04:28 -0000
Subject: [wp-meta] [Making WordPress.org] #2138: Update bbPress and
 BuddyPress "standalone" PTE projects
In-Reply-To: <050.90883f4166dad9870d2fa8e89e9a1cb7@wordpress.org>
References: <050.90883f4166dad9870d2fa8e89e9a1cb7@wordpress.org>
Message-ID: <065.9b59b96843c693dcf128d80302edfe5d@wordpress.org>

#2138: Update bbPress and BuddyPress "standalone" PTE projects
--------------------------------------+----------------------
 Reporter:  netweb                    |       Owner:
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  wontfix
 Keywords:                            |
--------------------------------------+----------------------
Changes (by ocean90):

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


Comment:

 There is nothing to update. The top-level projects GlotPress, BuddyPress
 and bbPress still exist on translate.wordpress.org and for legacy reasons
 PTEs can still be assigned to one of the projects. For example bbPress
 1.1.x is still used for the WordPress plugin directory.

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

From noreply at wordpress.org  Fri Oct 14 09:08:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 09:08:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2138: Update bbPress and
 BuddyPress "standalone" PTE projects
In-Reply-To: <050.90883f4166dad9870d2fa8e89e9a1cb7@wordpress.org>
References: <050.90883f4166dad9870d2fa8e89e9a1cb7@wordpress.org>
Message-ID: <065.08cbce9b85b3a80851e91ed20974cc31@wordpress.org>

#2138: Update bbPress and BuddyPress "standalone" PTE projects
--------------------------------------+----------------------
 Reporter:  netweb                    |       Owner:
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  wontfix
 Keywords:                            |
--------------------------------------+----------------------

Comment (by netweb):

 @ocean90 Can you think of something that could be implemented that would
 help avoid thhis scenario that happened
 today?https://make.wordpress.org/polyglots/2016/10/13/please-add-me-as-
 editor-of-the-chinese-4/

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

From noreply at wordpress.org  Fri Oct 14 09:47:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 09:47:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2140: Add ability to filter
 feedback on the form
Message-ID: <051.a0595bc88b70c6d036b13fd1f5d60701@wordpress.org>

#2140: Add ability to filter feedback on the form
-------------------------------------+-----------------
 Reporter:  atimmer                  |      Owner:
     Type:  enhancement              |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+-----------------
 Currently, when there are different forms for several related areas it is
 hard to find what you are looking for.

 The ability to filter based on which form the feedback was left in should
 make it easier to find what you are looking for.

 Feature request by @tacoverdo.

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

From noreply at wordpress.org  Fri Oct 14 10:04:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 10:04:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2141: Add ability to mark tickets
 as invalid/revoked
Message-ID: <051.02c61bb6bbb4e7c620fc197c01b13011@wordpress.org>

#2141: Add ability to mark tickets as invalid/revoked
-------------------------------------+-----------------
 Reporter:  atimmer                  |      Owner:
     Type:  enhancement              |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:
-------------------------------------+-----------------
 Currently, it is impossible to remove tickets that have been erroneously
 created. For example for WordCamp NL a volunteer ordered two tickets by
 accident. The organisation has no way to revoke this ticket.

 Feature request by @tacoverdo.

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

From noreply at wordpress.org  Fri Oct 14 15:17:33 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 15:17:33 +0000 (UTC)
Subject: [wp-meta] [4236]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/functions.php: Breathe: Add each site' s slug to the body
 class, so that CSS rules can target specific sites.
Message-ID: <20161014151733.754B51080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 15:24:47 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 15:24:47 +0000 (UTC)
Subject: [wp-meta] [4237]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: Add further styling for a post/ request
 type selector on make/polyglots.
Message-ID: <20161014152447.318581080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 15:34:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 15:34:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2139: The WordPress Swag
 store doesn't send email notifications when items are restocked
In-Reply-To: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
References: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
Message-ID: <065.d9b027e3183e168c8279c1866f3aba8f@wordpress.org>

#2139: The WordPress Swag store doesn't send email notifications when items are
restocked
-----------------------------+------------------
 Reporter:  netweb           |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by vskylabv):

 Hey. I've tried testing this but haven't been able to reproduce the issue.
 Have you checked your spam directory? What's the email you provided on the
 swag store? I can double check to make sure you've been added to those
 items.

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

From noreply at wordpress.org  Fri Oct 14 19:00:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 19:00:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2142: My Speaker Badge Disappeared
Message-ID: <054.a30cef6099aeafd6384ece53ffdf8795@wordpress.org>

#2142: My Speaker Badge Disappeared
------------------------+-----------------
 Reporter:  binarygary  |      Owner:
     Type:  defect      |     Status:  new
 Priority:  low         |  Milestone:
Component:  General     |   Keywords:
------------------------+-----------------
 I'm almost certain this is NOT the place for this...but I'm
 wondering/hoping someone could point me to who can help me out.
 I spoke at WCJAX16 and WCTPA16.  At some point (after Jax) I had the badge
 that showed me as a WC speaker...but now it's disappeared.

 https://profiles.wordpress.org/binarygary

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

From noreply at wordpress.org  Fri Oct 14 19:38:15 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 19:38:15 +0000 (UTC)
Subject: [wp-meta] [4238]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp Organizer
 Nags: Rename plugin to WordCamp Dashboard Widgets
Message-ID: <20161014193815.E3C701080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 19:43:12 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 19:43:12 +0000 (UTC)
Subject: [wp-meta] [4239]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/
 wordcamp-organizer-nags/: WordCamp Organizer Nags: Remove empty directory
 leftover from r4238
Message-ID: <20161014194312.0BD871080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 19:53:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 19:53:43 -0000
Subject: [wp-meta] [Making WordPress.org] #2143: Internationalize WordCamp
 Dashboard Widgets plugin
Message-ID: <051.ac2fb135d76211e836e67cf2461852b8@wordpress.org>

#2143: Internationalize WordCamp Dashboard Widgets plugin
----------------------------------+----------------------------------------
 Reporter:  iandunn               |      Owner:
     Type:  defect                |     Status:  new
 Priority:  low                   |  Milestone:
Component:  WordCamp Site &       |   Keywords:  needs-patch good-first-bug
  Plugins                         |
----------------------------------+----------------------------------------
 The WordCamp Dashboard Widgets plugin needs to be internationalized.

 The escaping translation functions (`esc_html__()`, `esc_attr_e()`, etc)
 should be used instead of their non-escaping counterparts.

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

From noreply at wordpress.org  Fri Oct 14 19:53:59 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 19:53:59 -0000
Subject: [wp-meta] [Making WordPress.org] #2143: Internationalize
 WordCamp Dashboard Widgets plugin
In-Reply-To: <051.ac2fb135d76211e836e67cf2461852b8@wordpress.org>
References: <051.ac2fb135d76211e836e67cf2461852b8@wordpress.org>
Message-ID: <066.e411a75e2b3a1781e45cdce9171de01a@wordpress.org>

#2143: Internationalize WordCamp Dashboard Widgets plugin
----------------------------------------+-----------------------
 Reporter:  iandunn                     |       Owner:  iandunn
     Type:  defect                      |      Status:  accepted
 Priority:  low                         |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------
Changes (by iandunn):

 * owner:   => iandunn
 * status:  new => accepted


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

From noreply at wordpress.org  Fri Oct 14 20:17:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 20:17:26 -0000
Subject: [wp-meta] [Making WordPress.org] #1586: Check box labels are
 misaligned in comment form
In-Reply-To: <050.eef1315f02043959772d3f28de5bd252@wordpress.org>
References: <050.eef1315f02043959772d3f28de5bd252@wordpress.org>
Message-ID: <065.efee7e82475ca3772d8a53c289bc5680@wordpress.org>

#1586: Check box labels are misaligned in comment form
--------------------------------------+--------------------------
 Reporter:  juhise                    |       Owner:  coffee2code
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:  has-patch                 |
--------------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4240"]:
 {{{
 #!CommitTicketReference repository="" revision="4240"
 W.org P2 child theme: Align comment subscription checkboxes with reply
 button.

 Props juhise.
 Fixes #1586.
 }}}

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

From noreply at wordpress.org  Fri Oct 14 20:17:25 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 20:17:25 +0000 (UTC)
Subject: [wp-meta] [4240]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-p2/style.css: W.org P2 child theme: Align comment subscription
 checkboxes with reply button.
Message-ID: <20161014201725.A55DB1080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 20:28:22 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 20:28:22 +0000 (UTC)
Subject: [wp-meta] [4241]
 sites/trunk/wordpress.org/public_html/style/wp4.css: wp4.css: Match
 appearance of Mobile Apps page with that of the plugin and theme
 directories (white cards on gray background).
Message-ID: <20161014202822.995221080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 20:28:23 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 20:28:23 -0000
Subject: [wp-meta] [Making WordPress.org] #1557: Mobile Apps -
 consistent design with plugins and themes
In-Reply-To: <049.b3443b465b100657dfa8876d198585a3@wordpress.org>
References: <049.b3443b465b100657dfa8876d198585a3@wordpress.org>
Message-ID: <064.15c405af9c29964c4307235a8c1069af@wordpress.org>

#1557: Mobile Apps - consistent design with plugins and themes
---------------------------------------+--------------------------
 Reporter:  ramiy                      |       Owner:  coffee2code
     Type:  defect                     |      Status:  closed
 Priority:  normal                     |   Milestone:
Component:  General                    |  Resolution:  fixed
 Keywords:  has-screenshots has-patch  |
---------------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4241"]:
 {{{
 #!CommitTicketReference repository="" revision="4241"
 wp4.css: Match appearance of Mobile Apps page with that of the plugin and
 theme directories (white cards on gray background).

 Props ramiy.
 Fixes #1557.
 }}}

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

From noreply at wordpress.org  Fri Oct 14 21:29:30 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 21:29:30 -0000
Subject: [wp-meta] [Making WordPress.org] #2089: DevHub: No search form
	on 404 page
In-Reply-To: <058.1bb112179eee67a84a633d074b74ee8a@wordpress.org>
References: <058.1bb112179eee67a84a633d074b74ee8a@wordpress.org>
Message-ID: <073.5760feb5037cf4d900504a322bab428a@wordpress.org>

#2089: DevHub: No search form on 404 page
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Developer Hub   |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4242"]:
 {{{
 #!CommitTicketReference repository="" revision="4242"
 developer.wordpress.org: Add search form to 404 pages.

 Props keesiemeijer.
 Fixes #2089.
 }}}

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

From noreply at wordpress.org  Fri Oct 14 21:29:29 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 21:29:29 +0000 (UTC)
Subject: [wp-meta] [4242]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-developer: developer.wordpress.org: Add search form to 404 pages.
Message-ID: <20161014212929.A6B231080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 21:57:14 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 21:57:14 +0000 (UTC)
Subject: [wp-meta] [4243]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-developer/functions.php: developer.wordpress.org: Bump CSS version
 for cache bust.
Message-ID: <20161014215714.05FB41080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 22:07:13 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 14 Oct 2016 22:07:13 +0000 (UTC)
Subject: [wp-meta] [4244]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-p2/functions.php: W.org P2 child theme: Bump CSS version for cache
 bust.
Message-ID: <20161014220713.EA9251080292@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 14 22:12:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 22:12:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2089: DevHub: No search form
	on 404 page
In-Reply-To: <058.1bb112179eee67a84a633d074b74ee8a@wordpress.org>
References: <058.1bb112179eee67a84a633d074b74ee8a@wordpress.org>
Message-ID: <073.366c1721aa00b2493eff054b5cdcd9a5@wordpress.org>

#2089: DevHub: No search form on 404 page
----------------------------+--------------------------
 Reporter:  SergeyBiryukov  |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Developer Hub   |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+--------------------------

Comment (by coffee2code):

 @keesiemeijer: Thanks, as always, for the patch!

 I committed the patch with a slight change: I still assigned the
 'searchform-handbook' for the search form when appearing in a handbook and
 left that as the original exception for enabling autocomplete. This
 allowed the autocomplete to work in the 404 search form outside the
 handbook. This necessitated a CSS tweak to ensure the autocomplete's list
 didn't get clipped due to the rather short 404 page content space.

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

From noreply at wordpress.org  Fri Oct 14 22:44:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 22:44:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2139: The WordPress Swag
 store doesn't send email notifications when items are restocked
In-Reply-To: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
References: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
Message-ID: <065.26deeaf1646500afdda7ae2a9415fa54@wordpress.org>

#2139: The WordPress Swag store doesn't send email notifications when items are
restocked
-----------------------------+------------------
 Reporter:  netweb           |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by netweb):

 Replying to [comment:2 vskylabv]:
 > Hey. I've tried testing this but haven't been able to reproduce the
 issue. Have you checked your spam directory? What's the email you provided
 on the swag store? I can double check to make sure you've been added to
 those items.

 The email I used is `stephen at netweb dot com dot au` and without a
 shadow of a doubt I've updated that coffee mug waiting list a bunch of
 times over the past couple of years, I really wanted^([#hn note])^ one of
 these mugs.

 Note:'' I really wanted one of these until they became available, then I
 found out the [https://twitter.com/netweb/status/786801250792644608
 shipping costs] equates to extortion ? ''

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

From noreply at wordpress.org  Fri Oct 14 22:52:22 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 22:52:22 -0000
Subject: [wp-meta] [Making WordPress.org] #2139: The WordPress Swag
 store doesn't send email notifications when items are restocked
In-Reply-To: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
References: <050.5059fbcdd86502db99e96540793582a3@wordpress.org>
Message-ID: <065.e58a3a073b82d8dc583b2c9055d96af9@wordpress.org>

#2139: The WordPress Swag store doesn't send email notifications when items are
restocked
-----------------------------+-------------------------
 Reporter:  netweb           |       Owner:
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |  Resolution:  worksforme
 Keywords:  has-screenshots  |
-----------------------------+-------------------------
Changes (by netweb):

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


Comment:

 @vskylabv Apologies, I didn't see your Jetpack Battery  Pack test above
 when I posted my reply above, thinking on this further maybe I hadn't
 updated my subscription at mercantile.wordpress.org, quite possibly I had
 only done this in the old swag store before the switch to
 mercantile.wordpress.org....

 I'll close this as `worksforme`, thanks for looking and testing :+1

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

From noreply at wordpress.org  Fri Oct 14 22:56:47 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 22:56:47 -0000
Subject: [wp-meta] [Making WordPress.org] #2144: CampTix Badge Generator
 should generate some blank entries
Message-ID: <051.52deb2eaa98338e0360861fa2c886c88@wordpress.org>

#2144: CampTix Badge Generator should generate some blank entries
----------------------------------+----------------------------------------
 Reporter:  iandunn               |      Owner:
     Type:  enhancement           |     Status:  new
 Priority:  normal                |  Milestone:
Component:  WordCamp Site &       |   Keywords:  needs-patch good-first-bug
  Plugins                         |
----------------------------------+----------------------------------------
 There are always attendees who register after the badge artwork has been
 sent to the printer, so registration tables need blank badges for me.

 Currently, the badge generator doesn't generate any, so we should add
 some. It'd probably be enough to add a single page of them at the end,
 because the printer can just print `n` copies of that page, based on the
 need.

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

From noreply at wordpress.org  Fri Oct 14 22:57:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 22:57:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2145: Gravatar Hovercards should
 be disabled in the CampTix Badge Generator
Message-ID: <051.2cf67a47962d9f8311fc9882dc5452b8@wordpress.org>

#2145: Gravatar Hovercards should be disabled in the CampTix Badge Generator
----------------------------------+----------------------------------------
 Reporter:  iandunn               |      Owner:
     Type:  enhancement           |     Status:  new
 Priority:  low                   |  Milestone:
Component:  WordCamp Site &       |   Keywords:  good-first-bug needs-patch
  Plugins                         |
----------------------------------+----------------------------------------
 They get in the way and don't add any value.

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

From noreply at wordpress.org  Fri Oct 14 23:41:34 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 14 Oct 2016 23:41:34 -0000
Subject: [wp-meta] [Making WordPress.org] #2146: Topics should also have
	user badges
Message-ID: <050.862bb5d62a6ea57cbc603029f926efd3@wordpress.org>

#2146: Topics should also have user badges
----------------------------+-------------------------
 Reporter:  netweb          |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch
----------------------------+-------------------------
 In #1544 / [3978] badges were added to user replies in support/review
 forums where the reply author has commit access or is listed as a
 contributor, the same badges should be added for topic authors.

 Use case: [https://wordpress.org/support/topic/support-forum-closed-send-
 your-queries-to-helpinfinitewp-com/?view=all This topic] in its plugins
 support forum created an "announcment" topic in their support forum and it
 is not immediadely obvious that the topic author is the actual plugin
 author.

 Related: [https://wordpress.slack.com/archives/forums/p1476440045010242
 Slack discussion] where this issue was raised

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

From noreply at wordpress.org  Sat Oct 15 00:09:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 00:09:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2142: My Speaker Badge
	Disappeared
In-Reply-To: <054.a30cef6099aeafd6384ece53ffdf8795@wordpress.org>
References: <054.a30cef6099aeafd6384ece53ffdf8795@wordpress.org>
Message-ID: <069.25177ea58abc0e0a3837139371510f22@wordpress.org>

#2142: My Speaker Badge Disappeared
------------------------+------------------------
 Reporter:  binarygary  |       Owner:
     Type:  defect      |      Status:  closed
 Priority:  low         |   Milestone:
Component:  General     |  Resolution:  duplicate
 Keywords:              |
------------------------+------------------------
Changes (by iandunn):

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


Comment:

 Duplicate of #683.

 Sorry about that, it's a known issue, but I haven't been able to reproduce
 it yet.

 Typically, if the organizer removes the username from the Speaker post in
 `wp-admin`, then saves, then adds it back and saves again, that will
 restore the badge. I did that and it worked in this case, so you've got
 the badge again.

 You can also ask in the `#meta-wordcamp` channel on
 [https://chat.wordpress.org Slack].

 ----

 ''Notes to self: In this case, it seems like both the activity item and
 association were added for the first camp (Jacksonville), but then when
 the attempt was made to add the second activity/association for Tampa, the
 activity was never added, and the association was removed.''

 ''Maybe add some logging to the handler to help figure out exactly what
 happens. The Tampa post had several revisions, but that's probably not
 relevant.''

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

From noreply at wordpress.org  Sat Oct 15 00:23:51 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 00:23:51 -0000
Subject: [wp-meta] [Making WordPress.org] #2142: My Speaker Badge
	Disappeared
In-Reply-To: <054.a30cef6099aeafd6384ece53ffdf8795@wordpress.org>
References: <054.a30cef6099aeafd6384ece53ffdf8795@wordpress.org>
Message-ID: <069.dada7d56497ac6e350b0f16a55ef57dd@wordpress.org>

#2142: My Speaker Badge Disappeared
------------------------+------------------------
 Reporter:  binarygary  |       Owner:
     Type:  defect      |      Status:  closed
 Priority:  low         |   Milestone:
Component:  Profiles    |  Resolution:  duplicate
 Keywords:              |
------------------------+------------------------
Changes (by SergeyBiryukov):

 * component:  General => Profiles


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

From noreply at wordpress.org  Sat Oct 15 09:53:20 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 09:53:20 -0000
Subject: [wp-meta] [Making WordPress.org] #2063: Breathe: Improve
 styling of sticky posts
In-Reply-To: <051.5bf68a4c2a3bcc3fb96885bc3f383ea6@wordpress.org>
References: <051.5bf68a4c2a3bcc3fb96885bc3f383ea6@wordpress.org>
Message-ID: <066.9b1ffee335c926a1bbe30a581fb2ba71@wordpress.org>

#2063: Breathe: Improve styling of sticky posts
--------------------------------------+----------------------
 Reporter:  ocean90                   |       Owner:  ocean90
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:  needs-patch               |
--------------------------------------+----------------------
Changes (by ocean90):

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


Comment:

 In [changeset:"4245"]:
 {{{
 #!CommitTicketReference repository="" revision="4245"
 Breathe: Style sticky posts.

 Fixes #2063.
 }}}

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

From noreply at wordpress.org  Sat Oct 15 09:53:19 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 09:53:19 +0000 (UTC)
Subject: [wp-meta] [4245]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: Style sticky posts.
Message-ID: <20161015095319.E34851080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 15 10:01:23 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 10:01:23 +0000 (UTC)
Subject: [wp-meta] [4246]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/functions.php: Breathe: Bump CSS version for cache bust.
Message-ID: <20161015100123.1D9F51080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 15 11:51:23 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 11:51:23 +0000 (UTC)
Subject: [wp-meta] [4247]
 sites/trunk/wordpress.org/public_html/style/wp4.css: wp4.css: Fix a typo in
 the selector of the make/polyglots icon.
Message-ID: <20161015115123.2E1281080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 15 14:13:52 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 14:13:52 +0000 (UTC)
Subject: [wp-meta] [4248]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub: Support Theme:
 Commit the inital new theme.
Message-ID: <20161015141352.951231080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 15 15:23:00 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 15:23:00 +0000 (UTC)
Subject: [wp-meta] [4249]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wp-i18n-teams/wp-i18n-teams.php: WP i18n teams: Change priority for
 `link_locales`.
Message-ID: <20161015152300.2483A1080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 15 17:57:31 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 17:57:31 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Forums: New theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.c414907bb35b5ccff671861a291405c2@wordpress.org>

#2147: Forums: New theme needs styling for badges
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 How does [attachment:meta-2147.1st-pass.png] look like? It uses these
 styles:
 {{{
 #bbpress-forums .by-moderator {
         border-right: 3px solid #33B4CE;
 }
 #bbpress-forums .by-plugin-author,
 #bbpress-forums .by-plugin-contributor,
 #bbpress-forums .by-theme-author,
 #bbpress-forums .by-theme-contributor {
         border-right: 3px solid green;
 }

 #bbpress-forums .author-badge {
         color: #fff;
         padding: 0 8px;
         float: right;
         font-style: italic;
         text-shadow: 1px 1px 3px #666;
 }

 #bbpress-forums .author-badge-moderator {
         background-color: #33B4CE;
 }

 #bbpress-forums .author-badge-plugin, #bbpress-forums .author-badge-theme
 {
         background-color: green;
 }
 }}}

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

From noreply at wordpress.org  Sat Oct 15 17:53:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 17:53:49 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Forums: New theme needs
 styling for badges
Message-ID: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>

#2147: Forums: New theme needs styling for badges
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 New theme for https://wordpress.org/support/ was committed in [4248].

 It needs styling for moderator badges added in #2073.

 Currently the badges are displayed in plain text, see the screenshot.

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

From noreply at wordpress.org  Sat Oct 15 18:00:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 18:00:39 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Forums: New theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.a508cec7e115918905c12003e27470aa@wordpress.org>

#2147: Forums: New theme needs styling for badges
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 [attachment:meta-2147.old-theme.png] is a screenshot of the old theme, for
 reference.

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

From noreply at wordpress.org  Sat Oct 15 20:23:58 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 20:23:58 +0000 (UTC)
Subject: [wp-meta] [4250]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: Add styles for additional post author
 meta on make/polyglots.
Message-ID: <20161015202358.B38651080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 15 20:30:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 20:30:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2064: Use user_nicename for
	@-mentions
In-Reply-To: <051.e9f24c031787ad2285eff018cdf6949a@wordpress.org>
References: <051.e9f24c031787ad2285eff018cdf6949a@wordpress.org>
Message-ID: <066.a7abe4d0d0c23bd647f6b3ec46c7d5e4@wordpress.org>

#2064: Use user_nicename for @-mentions
--------------------------------------+---------------------
 Reporter:  ocean90                   |       Owner:
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+---------------------
Changes (by ocean90):

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


Comment:

 Fixed in [dotorg12515].

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

From noreply at wordpress.org  Sat Oct 15 21:22:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 15 Oct 2016 21:22:39 -0000
Subject: [wp-meta] [Making WordPress.org] #1825: Style handbook with new
	O2 design
In-Reply-To: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
References: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
Message-ID: <068.3202876243461d84fa2c2b9c243f5b2e@wordpress.org>

#1825: Style handbook with new O2 design
--------------------------------------+------------------
 Reporter:  chriscct7                 |       Owner:
     Type:  task                      |      Status:  new
 Priority:  high                      |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by ocean90):

 In [changeset:"4251"]:
 {{{
 #!CommitTicketReference repository="" revision="4251"
 Breathe: Show sidebar on handbook landing page.

 See #1825.
 }}}

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

From noreply at wordpress.org  Sat Oct 15 21:22:38 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 15 Oct 2016 21:22:38 +0000 (UTC)
Subject: [wp-meta] [4251]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/single-handbook.php: Breathe: Show sidebar on handbook
 landing page.
Message-ID: <20161015212238.E39A21080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct 16 07:25:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 07:25:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2148: Homepage not displaying
 link to new official YouTube channel
Message-ID: <051.324b2227375307c4d545f10e79d6e0c1@wordpress.org>

#2148: Homepage not displaying link to new official YouTube channel
--------------------------+-----------------
 Reporter:  casiepa       |      Owner:
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+-----------------
 The homepage of WordPress.tv , under the Resources box (bottom right) has
 a link to the OLD YouTube channel. The new OFFICIAL YouTube channel is now
 being used.

 I propose to modify the link from https://www.youtube.com/c/wordpresstv to
 https://www.youtube.com/c/wordpress

 Pascal

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

From noreply at wordpress.org  Sun Oct 16 07:30:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 07:30:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2149: Browsing by categories:
 Missing year 2015
Message-ID: <051.53efd61eb84c6d13996a8bc3b4b4efff@wordpress.org>

#2149: Browsing by categories: Missing year 2015
--------------------------+-----------------
 Reporter:  casiepa       |      Owner:
     Type:  defect        |     Status:  new
 Priority:  normal        |  Milestone:
Component:  WordPress.tv  |   Keywords:
--------------------------+-----------------
 When browsing on WordPress.tv by category (e.g.
 https://wordpress.tv/category/wordcamptv/), in the left bar 'Browse by
 Year' the year 2015 is missing.

 Props to @emanweb

 Pascal.

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

From noreply at wordpress.org  Sun Oct 16 12:15:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 12:15:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Forums: New theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.c65ef3a6c5d6e15a42c7b755307d0985@wordpress.org>

#2147: Forums: New theme needs styling for badges
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  ui-feedback     |
----------------------------+------------------
Changes (by SergeyBiryukov):

 * keywords:   => ui-feedback


Comment:

 Needs UI feedback for comment:1.

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

From noreply at wordpress.org  Sun Oct 16 12:25:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 12:25:49 -0000
Subject: [wp-meta] [Making WordPress.org] #2148: Homepage not displaying
 link to new official YouTube channel
In-Reply-To: <051.324b2227375307c4d545f10e79d6e0c1@wordpress.org>
References: <051.324b2227375307c4d545f10e79d6e0c1@wordpress.org>
Message-ID: <066.13943091177fb3977d561ba2e8669a6a@wordpress.org>

#2148: Homepage not displaying link to new official YouTube channel
--------------------------+---------------------
 Reporter:  casiepa       |       Owner:
     Type:  enhancement   |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by SergeyBiryukov):

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


Comment:

 Thanks for the ticket, I've updated the link.

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

From noreply at wordpress.org  Sun Oct 16 13:17:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 13:17:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2150: Breathe: Child menu items
 are larger than parent items
Message-ID: <058.61885c0c5a8cf4b4c2aa09776a727000@wordpress.org>

#2150: Breathe: Child menu items are larger than parent items
--------------------------------------+-----------------
 Reporter:  SergeyBiryukov            |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:
--------------------------------------+-----------------
 In the new O2 design on https://make.wordpress.org/polyglots/handbook/,
 child menu items are larger than their parent items.

 See the screenshot.

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

From noreply at wordpress.org  Sun Oct 16 13:18:20 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 13:18:20 -0000
Subject: [wp-meta] [Making WordPress.org] #1825: Style handbook with new
	O2 design
In-Reply-To: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
References: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
Message-ID: <068.24aed4634b7b0433bb2fa1463cea3b22@wordpress.org>

#1825: Style handbook with new O2 design
--------------------------------------+------------------
 Reporter:  chriscct7                 |       Owner:
     Type:  task                      |      Status:  new
 Priority:  high                      |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #2150

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

From noreply at wordpress.org  Sun Oct 16 13:18:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 13:18:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2150: Breathe: Child menu
 items are larger than parent items
In-Reply-To: <058.61885c0c5a8cf4b4c2aa09776a727000@wordpress.org>
References: <058.61885c0c5a8cf4b4c2aa09776a727000@wordpress.org>
Message-ID: <073.7968691feae9d4572e24690b33f79c81@wordpress.org>

#2150: Breathe: Child menu items are larger than parent items
--------------------------------------+------------------
 Reporter:  SergeyBiryukov            |       Owner:
     Type:  defect                    |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #1825

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

From noreply at wordpress.org  Sun Oct 16 22:49:01 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 16 Oct 2016 22:49:01 -0000
Subject: [wp-meta] [Making WordPress.org] #2149: Browsing by categories:
 Missing year 2015
In-Reply-To: <051.53efd61eb84c6d13996a8bc3b4b4efff@wordpress.org>
References: <051.53efd61eb84c6d13996a8bc3b4b4efff@wordpress.org>
Message-ID: <066.e80554522492ddad4a48fb84a61e6353@wordpress.org>

#2149: Browsing by categories: Missing year 2015
--------------------------+---------------------
 Reporter:  casiepa       |       Owner:
     Type:  defect        |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:  fixed
 Keywords:                |
--------------------------+---------------------
Changes (by SergeyBiryukov):

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


Comment:

 Fixed by @roseapplemedia:
 https://wordpress.slack.com/archives/wptv/p1476633867001616

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

From noreply at wordpress.org  Mon Oct 17 03:29:19 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 03:29:19 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.b776408ff00148e1680fb6597557971b@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+---------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------

Comment (by dd32):

 Just a quick note - This used to be relatively instant with the bbPress1
 forums, the `_plugin-support-listing.php` plugin handled updating the
 plugin directory with the updated data when it was updated.

 There's room for it to be made instant again, but right now it's being
 updated every ~20 minutes via cron.

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

From noreply at wordpress.org  Mon Oct 17 04:49:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 04:49:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2082: Enable revisions on the
 front end for DevHub/HelpHub/Handbook pages
In-Reply-To: <054.5f03cf90d2836f9f736d4e89f123fb0c@wordpress.org>
References: <054.5f03cf90d2836f9f736d4e89f123fb0c@wordpress.org>
Message-ID: <069.9d396ac2a61aa81b0b25a15eb2794974@wordpress.org>

#2082: Enable revisions on the front end for DevHub/HelpHub/Handbook pages
-------------------------+------------------
 Reporter:  atachibana   |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  low          |   Milestone:
Component:  Support Hub  |  Resolution:
 Keywords:               |
-------------------------+------------------
Changes (by Kenshino):

 * priority:  normal => low
 * component:  Handbooks => Support Hub


Comment:

 So I discussed this with @sam, sounds like a great plugin to be built for
 v2 of Helphub.

 Let's KIV this.

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

From noreply at wordpress.org  Mon Oct 17 13:50:31 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 13:50:31 -0000
Subject: [wp-meta] [Making WordPress.org] #1814: Style Code Reference
 ToC links to better indicate interaction
In-Reply-To: <057.384f4ff49584c70bc39d82798f61f0a7@wordpress.org>
References: <057.384f4ff49584c70bc39d82798f61f0a7@wordpress.org>
Message-ID: <072.2e83278d43142041236aaf8237089494@wordpress.org>

#1814: Style Code Reference ToC links to better indicate interaction
-------------------------------------------------+-------------------------
 Reporter:  kevinwhoffman                        |       Owner:
     Type:  enhancement                          |  kevinwhoffman
 Priority:  normal                               |      Status:  assigned
Component:  Developer Hub                        |   Milestone:
 Keywords:  has-screenshots ui-feedback has-     |  Resolution:
  patch                                          |
-------------------------------------------------+-------------------------

Comment (by keesiemeijer):

 In the context of the handbooks it's more obvious (to me) that the TOC
 items are linked chapters in a book. The items are also made up of
 sentences instead of just words like 'Parameters' or 'Source'. By
 displaying the ToC items from the code reference as links you get an
 instant clue what the highlighted section might do (when looking at it at
 a glance).

 The ToC items are the same for all parsed post types and only link to
 sections within the page itself. This makes the title "Table of Contents"
 seem a bit off. We could rename it to "Contents" like in the screenshots
 of @kevinwhoffman or leave it off completely.

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

From noreply at wordpress.org  Mon Oct 17 19:29:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 19:29:39 -0000
Subject: [wp-meta] [Making WordPress.org] #1717: Add "subtitled" tag to
 WordPress.tv
In-Reply-To: <049.e052f969a2462ddee0a21e4cc38eed84@wordpress.org>
References: <049.e052f969a2462ddee0a21e4cc38eed84@wordpress.org>
Message-ID: <064.5a64a7d406223efa75f6a6793cabbc07@wordpress.org>

#1717: Add "subtitled" tag to WordPress.tv
--------------------------+------------------
 Reporter:  mor10         |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  WordPress.tv  |  Resolution:
 Keywords:                |
--------------------------+------------------

Comment (by casiepa):

 https://wordpress.tv/tag/subtitles/

 Is that what you were looking for ?

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

From noreply at wordpress.org  Mon Oct 17 21:12:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 21:12:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2066: Resolved topics count
	is incorrect
In-Reply-To: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
References: <051.096b162c818ab19b913ef4157619c3f7@wordpress.org>
Message-ID: <066.b4ac4d523e3669a0fc9d13eb0867e426@wordpress.org>

#2066: Resolved topics count is incorrect
------------------------------+---------------------
 Reporter:  Clorith           |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------

Comment (by Clorith):

 I'd say the wait isn't a terrible problem, so whichever option is most
 beneficial performance wise across the board should be the one we stick to

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

From noreply at wordpress.org  Mon Oct 17 22:53:10 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 22:53:10 -0000
Subject: [wp-meta] [Making WordPress.org] #2058: login.wordpress.org
 still links to bbPress 1.x
In-Reply-To: <058.efd75c0c220ca74d941ad79fee0257f4@wordpress.org>
References: <058.efd75c0c220ca74d941ad79fee0257f4@wordpress.org>
Message-ID: <073.e22325c42013802f7322d8b190d4dde1@wordpress.org>

#2058: login.wordpress.org still links to bbPress 1.x
------------------------------------+------------------
 Reporter:  SergeyBiryukov          |       Owner:
     Type:  defect                  |      Status:  new
 Priority:  high                    |   Milestone:
Component:  Login & Authentication  |  Resolution:
 Keywords:                          |
------------------------------------+------------------
Changes (by Clorith):

 * priority:  normal => high


Comment:

 Bumping this up a notch.

 After the move to bbPress2 we've seen a substantial decrease in people
 seeking help via the forums, that we're telling them everything has been
 down for the past month and a half is most likely the cause of this and
 I'd hate for people to be "turned away at the door" so to speak.

 It's also a bit awkward since this is the login and registration page for
 all of .org, even if it does state that it only relates to the support
 forums you never know how well that translates as it's not a localized
 warning.

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

From noreply at wordpress.org  Mon Oct 17 23:00:34 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 23:00:34 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Forums: New theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.51b843928f25ad1e8dec0e04d164d22b@wordpress.org>

#2147: Forums: New theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------
Changes (by coffee2code):

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


Comment:

 Added [attachment:meta-2147.left-badge.png] as an example of the badge and
 border on the left (same as for old theme).

 Same styles as [comment:1 above] but replace the 2 occurrences of `border-
 right` with `border-left`, and change the `float: right;` to

 {{{
 position: absolute;
 top: 12px;
 left: 0;
 }}}

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

From noreply at wordpress.org  Mon Oct 17 23:46:06 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 23:46:06 -0000
Subject: [wp-meta] [Making WordPress.org] #2058: login.wordpress.org
 still links to bbPress 1.x
In-Reply-To: <058.efd75c0c220ca74d941ad79fee0257f4@wordpress.org>
References: <058.efd75c0c220ca74d941ad79fee0257f4@wordpress.org>
Message-ID: <073.91f8b0c2989f7c735584f59047357a4b@wordpress.org>

#2058: login.wordpress.org still links to bbPress 1.x
------------------------------------+------------------
 Reporter:  SergeyBiryukov          |       Owner:
     Type:  defect                  |      Status:  new
 Priority:  high                    |   Milestone:
Component:  Login & Authentication  |  Resolution:
 Keywords:                          |
------------------------------------+------------------

Comment (by Otto42):

 As a temporary measure, I have removed the maintenance notice from the old
 forums. Eventually, I suspect we want registration to occur through
 login.wordpress.org itself.

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

From noreply at wordpress.org  Mon Oct 17 23:49:48 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 17 Oct 2016 23:49:48 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Forums: New theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.6c0bdef593c3c982dad46674829af294@wordpress.org>

#2147: Forums: New theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------

Comment (by SergeyBiryukov):

 [attachment:meta-2147.left-badge.png] was my initial attempt as well, but
 I thought it doesn't look good, because there's no space between the
 border and Gravatar. Adding some space would help, but it would also break
 left alignment for non-moderator posts.

 @mapk: What would you prefer here?

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

From noreply at wordpress.org  Tue Oct 18 00:20:17 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 00:20:17 +0000 (UTC)
Subject: [wp-meta] [4252]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins: WordCamp
 Logger: Add a few common password field keys to the blacklist.
Message-ID: <20161018002017.284DB1080607@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 18 00:22:10 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 00:22:10 +0000 (UTC)
Subject: [wp-meta] [4256]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/
 multi-event-sponsors: Multi Event Sponsors: Hide `Push sponsors` checkbox
 if the site doesn't exist
Message-ID: <20161018002210.0448B1080607@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 18 00:20:21 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 00:20:21 +0000 (UTC)
Subject: [wp-meta] [4253]
 sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/
 helper-functions.php: WordCamp Helpers: Wrap `CampTix_Plugin: esc_csv`
 instead of duplicating it
Message-ID: <20161018002021.903521080607@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 18 00:22:01 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 00:22:01 +0000 (UTC)
Subject: [wp-meta] [4254]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/
 wcpt-wordcamp: WordCamp Post Type: Add logging to the site creation process
Message-ID: <20161018002201.C5B901080607@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 18 00:22:06 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 00:22:06 +0000 (UTC)
Subject: [wp-meta] [4255]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/
 wcpt-wordcamp/wordcamp-new-site.php: WordCamp Post Type: Clean up
 formatting.
Message-ID: <20161018002206.44F0D1080607@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 18 03:10:30 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 03:10:30 -0000
Subject: [wp-meta] [Making WordPress.org] #2151: Support Theme i18n
Message-ID: <058.768332fc70976526d12ad9509c460645@wordpress.org>

#2151: Support Theme i18n
----------------------------+-------------------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch
----------------------------+-------------------------
 See [4248] for initial Support Theme commit.

 There are some strings hardcoded in English, and the rest use `wporg-
 forums` text domain from the previous theme.

 All strings should be marked for translation using `wporg-support` text
 domain.

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

From noreply at wordpress.org  Tue Oct 18 03:10:40 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 03:10:40 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Support Theme needs
 styling for badges (was: Forums: New theme needs styling for badges)
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.6914ffb3fbfcdb774626dac75fd594b7@wordpress.org>

#2147: Support Theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------

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

From noreply at wordpress.org  Tue Oct 18 06:08:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 06:08:43 -0000
Subject: [wp-meta] [Making WordPress.org] #1932: Add Normalize.css to to
	CreditsAPI
In-Reply-To: <050.ea076c4e5eff716291d5b4139b6bff96@wordpress.org>
References: <050.ea076c4e5eff716291d5b4139b6bff96@wordpress.org>
Message-ID: <065.f63f29896a5affb2d695349d7c8901c1@wordpress.org>

#1932: Add Normalize.css to to CreditsAPI
-----------------------+-------------------------
 Reporter:  netweb     |       Owner:
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  API        |  Resolution:  maybelater
 Keywords:  has-patch  |
-----------------------+-------------------------
Changes (by netweb):

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


Comment:

 Replying to [ticket:1932 netweb]:
 > See #WP37596

 The above ticket has been moved to "future release", more than likely
 Normalize will be removed, as such, closing this as maybe later, can
 reopened if needed

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

From noreply at wordpress.org  Tue Oct 18 07:31:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 07:31:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2058: login.wordpress.org
 still links to bbPress 1.x
In-Reply-To: <058.efd75c0c220ca74d941ad79fee0257f4@wordpress.org>
References: <058.efd75c0c220ca74d941ad79fee0257f4@wordpress.org>
Message-ID: <073.d8c2e950130df057fb84b2850ad7626c@wordpress.org>

#2058: login.wordpress.org still links to bbPress 1.x
------------------------------------+---------------------
 Reporter:  SergeyBiryukov          |       Owner:
     Type:  defect                  |      Status:  closed
 Priority:  normal                  |   Milestone:
Component:  Login & Authentication  |  Resolution:  fixed
 Keywords:                          |
------------------------------------+---------------------
Changes (by ocean90):

 * priority:  high => normal
 * status:  new => closed
 * resolution:   => fixed


Comment:

 The second issue was fixed a while ago. For the new registration form we
 have #148.

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

From noreply at wordpress.org  Tue Oct 18 07:35:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 07:35:57 -0000
Subject: [wp-meta] [Making WordPress.org] #148: Restyle/redesign the
 registration page
In-Reply-To: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org>
References: <051.ab1c08ab370895eaf5a087029eef46c5@wordpress.org>
Message-ID: <066.5d90a84a7ff4298792f8d301c061775c@wordpress.org>

#148: Restyle/redesign the registration page
-------------------------------------+-----------------------
 Reporter:  j.conti                  |       Owner:  ocean90
     Type:  task                     |      Status:  accepted
 Priority:  high                     |   Milestone:
Component:  Login & Authentication   |  Resolution:
 Keywords:  ui-feedback needs-patch  |
-------------------------------------+-----------------------
Changes (by ocean90):

 * owner:   => ocean90
 * status:  reviewing => accepted


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

From noreply at wordpress.org  Tue Oct 18 07:49:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 07:49:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2081: Clean up spam topics
 and topic tag spam
In-Reply-To: <050.40962b0c6179f0cf5def93998d52ddcc@wordpress.org>
References: <050.40962b0c6179f0cf5def93998d52ddcc@wordpress.org>
Message-ID: <065.a912f2ea510bbb60943f284df1c19609@wordpress.org>

#2081: Clean up spam topics and topic tag spam
----------------------------+-------------------------
 Reporter:  netweb          |       Owner:
     Type:  task            |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  worksforme
 Keywords:                  |
----------------------------+-------------------------
Changes (by Kenshino):

 * keywords:  2nd-opinion =>
 * status:  new => closed
 * resolution:   => worksforme


Comment:

 I cleaned up Taiwan forums. It's fine now. Closing :)

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

From noreply at wordpress.org  Tue Oct 18 13:51:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 13:51:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2152: Support Theme subheading is
 inconsistent with other WP.org sections
Message-ID: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>

#2152: Support Theme subheading is inconsistent with other WP.org sections
----------------------------+-----------------------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  has-screenshots
----------------------------+-----------------------------
 Most of WP.org sections have a grey `<h2>` subheading. This includes:
 * https://wordpress.org/showcase/
 * https://wordpress.org/themes/
 * https://wordpress.org/plugins/
 * https://wordpress.org/mobile/
 * https://codex.wordpress.org/Main_Page
 * https://make.wordpress.org/
 * https://wordpress.org/about/

 The new Support Theme is different:

 1. On home page, the subheading is large, screen-wide, `<h1>`.
 2. Internal forum pages do have a proper subheading, but it's `<p>` on a
 blue background, with a underline.

 It's similar to make.wordpress.org sites with o2/Breathe, e.g.
 https://make.wordpress.org/polyglots/.

 My suggestions:
 * There should be a consistent "Support" subheading on all pages in
 Support section.
 * It should probably be grey for consistency with other sections.
 Alternatively, other sections should be updated to use o2/Breathe styles.

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

From noreply at wordpress.org  Tue Oct 18 13:57:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 13:57:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2152: Support Theme
 subheading is inconsistent with other WP.org sections
In-Reply-To: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
References: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
Message-ID: <073.9df19c2c801439773398ae7b2ab92eb4@wordpress.org>

#2152: Support Theme subheading is inconsistent with other WP.org sections
-----------------------------+------------------
 Reporter:  SergeyBiryukov   |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by Otto42):

 I think that's intentional (mostly). We're switching everything over to
 the newer look, slowly, doing away with the gray subheading in favor of
 the blue style.

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

From noreply at wordpress.org  Tue Oct 18 13:57:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 13:57:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2152: Support Theme
 subheading is inconsistent with other WP.org sections
In-Reply-To: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
References: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
Message-ID: <073.5170abd6b99a3ae3eaa1e44740011831@wordpress.org>

#2152: Support Theme subheading is inconsistent with other WP.org sections
-----------------------------+------------------
 Reporter:  SergeyBiryukov   |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by ocean90):

 > It should probably be grey for consistency with other sections.
 Alternatively, other sections should be updated to use o2/Breathe styles.

 The blue header is actually the new one. It will be used for all new
 themes. See also https://wordpress.org/plugins-wp/.

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

From noreply at wordpress.org  Tue Oct 18 18:22:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 18:22:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Support Theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.3a9f913190135f7730d5b97643eee055@wordpress.org>

#2147: Support Theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------

Comment (by mapk):

 Replying to [comment:5 SergeyBiryukov]:
 > [attachment:meta-2147.left-badge.png] was my initial attempt as well,
 but I thought it doesn't look good, because there's no space between the
 border and Gravatar. Adding some space would help, but it would also break
 left alignment for non-moderator posts.
 >
 > @mapk: What would you prefer here?

 I like the direction. Thanks for picking this up!  What if we adjusted the
 CSS so it's a `box-shadow` instead of a `border-left`? Something like
 this:

 {{{
 .by-moderator {
     box-shadow: -4px 0 0 white, -6px 0 0 #33B4CE;
 }
 }}}

 and

 {{{
 .by-moderator .author-badge-moderator {
     position: absolute;
     top: 14px;
     left: -6px;
     padding: 2px 5px;
     background: #33B4CE;
     color: white;
     font-size: 0.6rem;
     letter-spacing: 1px;
     border-radius: 0 2px 2px 0;
 }
 }}}

 The double box-shadow values help push the blue border/shadow away from
 the avatar. Let me know what you think? Are there other tags that we
 should also consider? Maybe we can come up with a color scheme for them?

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

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

From noreply at wordpress.org  Tue Oct 18 18:38:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 18:38:03 -0000
Subject: [wp-meta] [Making WordPress.org] #2152: Support Theme
 subheading is inconsistent with other WP.org sections
In-Reply-To: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
References: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
Message-ID: <073.3206d8682bcb026138295f18483c1cef@wordpress.org>

#2152: Support Theme subheading is inconsistent with other WP.org sections
-----------------------------+------------------
 Reporter:  SergeyBiryukov   |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Support Forums   |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by mapk):

 Both, @Otto42 and @ocean90 are correct. We're moving toward a common blue
 bar which will display the section title and subnav items along with a
 search capability. It's being implemented slowly across the site as
 redesigns happen.

 Should we close this ticket?

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

From noreply at wordpress.org  Tue Oct 18 18:41:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 18:41:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2152: Support Theme
 subheading is inconsistent with other WP.org sections
In-Reply-To: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
References: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
Message-ID: <073.f5cee263616e6b4ee79b0844f9a7d227@wordpress.org>

#2152: Support Theme subheading is inconsistent with other WP.org sections
-----------------------------+----------------------
 Reporter:  SergeyBiryukov   |       Owner:
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Support Forums   |  Resolution:  invalid
 Keywords:  has-screenshots  |
-----------------------------+----------------------
Changes (by Otto42):

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


Comment:

 There's still a few minor styling issues like the underline under the
 header that says Support, but since this isn't really done or launched
 yet, then I don't think we need individual tickets for each particular
 thing at present.

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

From noreply at wordpress.org  Tue Oct 18 19:59:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 19:59:02 -0000
Subject: [wp-meta] [Making WordPress.org] #1919: Allow locales to create
 localised handbooks on Rosetta sites
In-Reply-To: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
References: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
Message-ID: <066.7930198595b3a2d3bbc45be32e1db989@wordpress.org>

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

Comment (by casiepa):

 Hi @samuelsidler , just a small ping to see if you can somewhere plan this
 now that we have our team sites. Thanks.

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

From noreply at wordpress.org  Tue Oct 18 20:03:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 20:03:39 -0000
Subject: [wp-meta] [Making WordPress.org] #2153: Subprojects not
 consistently displayed on translate.w.org
Message-ID: <051.08425ffa34999bdb14dbf1b08f211358@wordpress.org>

#2153: Subprojects not consistently displayed on translate.w.org
--------------------------------------+-----------------
 Reporter:  casiepa                   |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+-----------------
 On https://translate.wordpress.org/locale/fr/default/wp-plugins/custom-
 post-widget Stable is on the 2nd row, however on
 https://translate.wordpress.org/locale/fr/default/wp-plugins/tailor Stable
 is on the 3rd row.

 The issue might be coming from line 523 on
 https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/plugins/wporg-gp-routes/inc/routes/class-locale.php where the
 order is set by ID.
 For a better consistent view, it might be better to order by 'title'.

 Thanks, Pascal.

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

From noreply at wordpress.org  Tue Oct 18 20:50:31 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 20:50:31 -0000
Subject: [wp-meta] [Making WordPress.org] #1919: Allow locales to create
 localised handbooks on Rosetta sites
In-Reply-To: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
References: <051.855d4c1ea5302d1ca4ffafe475770f0e@wordpress.org>
Message-ID: <066.722a9f098d50ac5f57c34f1d66f95363@wordpress.org>

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

 * priority:  normal => low


Comment:

 @casiepa To roll out more handbooks we've to improve the compatibility
 with o2 first. This also includes the design see #1825. Are you able to
 help with some CSS/JS work?

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

From noreply at wordpress.org  Tue Oct 18 21:03:50 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 21:03:50 +0000 (UTC)
Subject: [wp-meta] [4257]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-support:
 Removed bottom-border on links.
Message-ID: <20161018210350.6A2131080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 18 22:04:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 22:04:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2141: Add ability to mark
 tickets as invalid/revoked
In-Reply-To: <051.02c61bb6bbb4e7c620fc197c01b13011@wordpress.org>
References: <051.02c61bb6bbb4e7c620fc197c01b13011@wordpress.org>
Message-ID: <066.b3d2633c44f7a1a438ccc59814a742af@wordpress.org>

#2141: Add ability to mark tickets as invalid/revoked
-------------------------------------+-------------------------
 Reporter:  atimmer                  |       Owner:
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  maybelater
 Keywords:                           |
-------------------------------------+-------------------------
Changes (by iandunn):

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


Comment:

 It is possible to [https://make.wordpress.org/community/handbook/wordcamp-
 organizer/first-steps/web-presence/using-camptix-event-ticketing-
 plugin/#refunds refund] the ticket, and some camps work around it by
 encouraging attendees to gift the ticket to someone else (and update the
 attendee info), or just write it off as a donation, since it's relatively
 cheap for most people.

 Those don't always work, though, so I can see a use case for this too.
 It'll need to be [https://make.wordpress.org/community/feature-requests-
 for-community-sites/ proposed to the Community Team first], though, so
 I'll close it for now.

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

From noreply at wordpress.org  Tue Oct 18 22:00:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 18 Oct 2016 22:00:49 -0000
Subject: [wp-meta] [Making WordPress.org] #2140: Add ability to filter
 feedback on the form
In-Reply-To: <051.a0595bc88b70c6d036b13fd1f5d60701@wordpress.org>
References: <051.a0595bc88b70c6d036b13fd1f5d60701@wordpress.org>
Message-ID: <066.07e408a0de86e26a09cd9aa2b7e99ac5@wordpress.org>

#2140: Add ability to filter feedback on the form
-------------------------------------+-------------------------
 Reporter:  atimmer                  |       Owner:
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  maybelater
 Keywords:                           |
-------------------------------------+-------------------------
Changes (by iandunn):

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


Comment:

 Hi :)

 Which forms is this about? If it's the `[contact-form]` shortcode, that's
 part of Jetpack, so you'd need to suggest it to them.

 If it's some of WordCamp.org's custom code, then
 [https://make.wordpress.org/community/feature-requests-for-community-
 sites/ feature requests need to be proposed on the Community Team's p2
 first], and approved by them, before the Meta team does anything with
 them.

 Closing for now, but this can be re-opened if the Community Team approves
 it.

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

From noreply at wordpress.org  Tue Oct 18 22:01:10 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 18 Oct 2016 22:01:10 +0000 (UTC)
Subject: [wp-meta] [4258] sites/trunk: Trac/Slack: Add davidakennedy to the
	committers list.
Message-ID: <20161018220110.6B4021080358@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 00:05:20 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 00:05:20 -0000
Subject: [wp-meta] [Making WordPress.org] #2152: Support Theme
 subheading is inconsistent with other WP.org sections
In-Reply-To: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
References: <058.f8954aa5d3193f27aa1c5ec50e930984@wordpress.org>
Message-ID: <073.59045a31a7b6a016763a43b5920e3d59@wordpress.org>

#2152: Support Theme subheading is inconsistent with other WP.org sections
-----------------------------+----------------------
 Reporter:  SergeyBiryukov   |       Owner:
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Support Forums   |  Resolution:  invalid
 Keywords:  has-screenshots  |
-----------------------------+----------------------

Comment (by netweb):

 Changeset [4257] missed this ticket:

 > Removed bottom-border on links. This also fixes the underline in the
 subnav for the section title.

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

From noreply at wordpress.org  Wed Oct 19 02:30:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 02:30:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.254a4552b3ca10fda41e38d290a4fc15@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4260"]:
 {{{
 #!CommitTicketReference repository="" revision="4260"
 Plugin Directory: Move the Stats from `wp-admin` to the front-end
 `/$plugin/admin/` screen.
 This also implements the capabilities required for access to the plugin
 admin screen for each plugin.

 See #2111
 }}}

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

From noreply at wordpress.org  Wed Oct 19 02:30:54 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 02:30:54 +0000 (UTC)
Subject: [wp-meta] [4260] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: Move the Stats from `wp-admin` to the front-end
 `/$plugin/admin/` screen.
Message-ID: <20161019023054.926D210805FB@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 02:27:58 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 02:27:58 +0000 (UTC)
Subject: [wp-meta] [4259]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Add readme-validator shortcode class,
 and tweak the Validator class a little to work on the front-end as well.
Message-ID: <20161019022758.CCD1310805FB@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 02:27:59 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 02:27:59 -0000
Subject: [wp-meta] [Making WordPress.org] #2128: Add front-end readme
	validator
In-Reply-To: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
References: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
Message-ID: <063.804500c67094e4928ae6e512148e6319@wordpress.org>

#2128: Add front-end readme validator
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:  tellyworth
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by tellyworth):

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


Comment:

 In [changeset:"4259"]:
 {{{
 #!CommitTicketReference repository="" revision="4259"
 Add readme-validator shortcode class, and tweak the Validator class a
 little to work on the front-end as well.

 Fixes #2128
 }}}

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

From noreply at wordpress.org  Wed Oct 19 03:27:01 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 03:27:01 -0000
Subject: [wp-meta] [Making WordPress.org] #2128: Add front-end readme
	validator
In-Reply-To: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
References: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
Message-ID: <063.137e67c2fb5287a0b1b1c35a129a2d3b@wordpress.org>

#2128: Add front-end readme validator
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:  tellyworth
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4261"]:
 {{{
 #!CommitTicketReference repository="" revision="4261"
 Plugin Directory: Readme Validator: Strip out the `wp-admin` handling in
 the readme handler and streamline the error checks a little.

 See #2128
 }}}

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

From noreply at wordpress.org  Wed Oct 19 03:27:01 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 03:27:01 +0000 (UTC)
Subject: [wp-meta] [4261]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Readme Validator: Strip out the `wp-admin` handling in
 the readme handler and streamline the error checks a little.
Message-ID: <20161019032701.1F50A10805FB@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 03:29:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 03:29:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2128: Add front-end readme
	validator
In-Reply-To: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
References: <048.71a4fd1c21c93c12b224e6ea1258ff4e@wordpress.org>
Message-ID: <063.d4fb014e21ef2f2e439fd20484429c67@wordpress.org>

#2128: Add front-end readme validator
------------------------------+---------------------------------------
 Reporter:  dd32              |       Owner:  tellyworth
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4262"]:
 {{{
 #!CommitTicketReference repository="" revision="4262"
 Pligin Directory: Readme Validator: Fix a typo in r4261.

 See #2128
 }}}

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

From noreply at wordpress.org  Wed Oct 19 03:29:52 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 03:29:52 +0000 (UTC)
Subject: [wp-meta] [4262]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/shortcodes/class-readme-validator.php: Pligin Directory:
 Readme Validator: Fix a typo in r4261.
Message-ID: <20161019032952.B5F1410805FB@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 06:23:13 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 06:23:13 +0000 (UTC)
Subject: [wp-meta] [4263] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: Add `no-js` handling for JS-only sections and add the
 start of the admin sidebars.
Message-ID: <20161019062313.47DA210805FB@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 06:23:13 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 06:23:13 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.7ee9f02584a06ec7de7b0b4edc4e2868@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4263"]:
 {{{
 #!CommitTicketReference repository="" revision="4263"
 Plugin Directory: Add `no-js` handling for JS-only sections and add the
 start of the admin sidebars.

 See #2111
 }}}

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

From noreply at wordpress.org  Wed Oct 19 07:28:49 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 07:28:49 +0000 (UTC)
Subject: [wp-meta] [4264]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-plugins/package.json: Plugin Directory: Drop the grunt-postcss
 version to 0.7.2 which supports Node 0.10 ( which is in use on
 WordPress.org).
Message-ID: <20161019072849.CFA491080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 08:21:07 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 08:21:07 -0000
Subject: [wp-meta] [Making WordPress.org] #2154: Ensures that i18n-teams.css
 loads after P2-Breath to prevent getting overridden.
Message-ID: <052.486109d2fbb26828045ad337f0d707c8@wordpress.org>

#2154: Ensures that i18n-teams.css loads after P2-Breath to prevent getting
overridden.
--------------------------------------+-----------------------
 Reporter:  Kenshino                  |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:  has-patch
--------------------------------------+-----------------------
 Will help to fix the responsive table issue on
 https://make.wordpress.org/polyglots/teams/

 Tables are currently messed up in mobile view due to P2-Breathe overriding
 key styles

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

From noreply at wordpress.org  Wed Oct 19 11:33:16 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 11:33:16 -0000
Subject: [wp-meta] [Making WordPress.org] #2155: Breathe: Header styles are
 inconsistent with new Support and Plugins themes
Message-ID: <058.102b708ce19b707d768dc1a727bc4cc8@wordpress.org>

#2155: Breathe: Header styles are inconsistent with new Support and Plugins themes
--------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov            |      Owner:
     Type:  defect                    |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Make (Get Involved) / P2  |   Keywords:  has-screenshots
--------------------------------------+-----------------------------
 * The "Search WordPress.org" text in search form is too small.
 * The underline on menu items looks different due to different styles:
  * Support & Plugins: `.main-navigation a.active { border-bottom: 1px
 solid; }`
  * Breathe: `.navigation-main ul li.current-menu-item a { text-decoration:
 underline; }`

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

From noreply at wordpress.org  Wed Oct 19 11:47:19 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 11:47:19 -0000
Subject: [wp-meta] [Making WordPress.org] #2156: Plugin Directory: No "My
 Favorites" link on home page
Message-ID: <058.51b2f86b475c1364fe6f33e767c26c86@wordpress.org>

#2156: Plugin Directory: No "My Favorites" link on home page
------------------------------+-----------------
 Reporter:  SergeyBiryukov    |      Owner:
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+-----------------
 On https://wordpress.org/plugins-wp/, you cannot quickly view your
 favorite plugins.

 You have to click on some random plugin first to see the "My Favorites"
 link.

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

From noreply at wordpress.org  Wed Oct 19 11:52:17 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 11:52:17 -0000
Subject: [wp-meta] [Making WordPress.org] #2157: Plugin Directory: "Edit
 Plugin" link is displayed for non-admins
Message-ID: <058.399d0c0756a93aea58237725226b6850@wordpress.org>

#2157: Plugin Directory: "Edit Plugin" link is displayed for non-admins
------------------------------+-----------------------------
 Reporter:  SergeyBiryukov    |      Owner:
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  has-screenshots
------------------------------+-----------------------------
 On https://wordpress.org/plugins-wp/akismet/, there's "Edit Plugin" link,
 although I'm not an admin of that plugin.

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

From noreply at wordpress.org  Wed Oct 19 11:56:48 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 11:56:48 -0000
Subject: [wp-meta] [Making WordPress.org] #2157: Plugin Directory: "Edit
 Plugin" link is displayed for non-admins
In-Reply-To: <058.399d0c0756a93aea58237725226b6850@wordpress.org>
References: <058.399d0c0756a93aea58237725226b6850@wordpress.org>
Message-ID: <073.a34fb572e72cd8afc5b7b1c5574a4d1a@wordpress.org>

#2157: Plugin Directory: "Edit Plugin" link is displayed for non-admins
------------------------------+------------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  duplicate
 Keywords:  has-screenshots   |
------------------------------+------------------------
Changes (by ocean90):

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


Comment:

 Confirmed, but closing as a dup of #2111 since it's WIP.

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

From noreply at wordpress.org  Wed Oct 19 11:57:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 11:57:25 -0000
Subject: [wp-meta] [Making WordPress.org] #2157: Plugin Directory: "Edit
 Plugin" link is displayed for non-admins
In-Reply-To: <058.399d0c0756a93aea58237725226b6850@wordpress.org>
References: <058.399d0c0756a93aea58237725226b6850@wordpress.org>
Message-ID: <073.dbc0eb161574e6659c7b03cc9cb91bde@wordpress.org>

#2157: Plugin Directory: "Edit Plugin" link is displayed for non-admins
------------------------------+------------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  duplicate
 Keywords:  has-screenshots   |
------------------------------+------------------------

Comment (by SergeyBiryukov):

 Appears to be fixed [4260], maybe it's just not deployed yet.

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

From noreply at wordpress.org  Wed Oct 19 14:00:09 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 14:00:09 +0000 (UTC)
Subject: [wp-meta] [4265]
 sites/trunk/common/includes/slack/announce/config.php: Slack Announce: Add
 @lucasartoni to #wceu-volunteers.
Message-ID: <20161019140009.EDF171080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 17:56:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 17:56:25 -0000
Subject: [wp-meta] [Making WordPress.org] #2158: Handbook Table of Contents
 need to be toggle-able on small screens
Message-ID: <055.00389ec1ed165ba86fbaa02bc6616413@wordpress.org>

#2158: Handbook Table of Contents need to be toggle-able on small screens
-------------------------+-------------------------------------------
 Reporter:  morganestes  |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Handbooks    |   Keywords:  needs-patch needs-screenshots
-------------------------+-------------------------------------------
 After [2016], I found at least one more place that the old behavior of not
 toggling the Handbook nav on heading click.

 The selector used in [2016] doesn't work for
 https://make.wordpress.org/training/handbook/, which uses a different
 widget for the table of contents (`.widget_nav_menu` instead of
 `.widget_wporg_handbook_pages`). I don't know if that's a network-wide
 change, but I'm opening this ticket to track how each of the handbooks are
 set up on the front end to find out how they're implemented, and see if
 there's a better selector to use across all of them.

 Related: #467

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

From noreply at wordpress.org  Wed Oct 19 18:10:03 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 18:10:03 +0000 (UTC)
Subject: [wp-meta] [4266]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-p2/style.css: W.org P2 child theme: Improve spacing around 3rd tier
 list elements of chapters listing in handbook sidebar.
Message-ID: <20161019181003.B6D331080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 18:11:25 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 18:11:25 +0000 (UTC)
Subject: [wp-meta] [4267]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: Improve spacing around 3rd tier list
 elements of chapters listing in handbook sidebar.
Message-ID: <20161019181125.3EB721080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 18:11:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 18:11:25 -0000
Subject: [wp-meta] [Making WordPress.org] #814: Balance spacing on tier
 3 sidebar items
In-Reply-To: <057.3c05bc82fc1dfd5988e98c96b752906c@wordpress.org>
References: <057.3c05bc82fc1dfd5988e98c96b752906c@wordpress.org>
Message-ID: <072.72a8fe09c928e5df6a6ea0506d87dc1c@wordpress.org>

#814: Balance spacing on tier 3 sidebar items
--------------------------------+--------------------------
 Reporter:  Craig Ralston       |       Owner:  coffee2code
     Type:  enhancement         |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Handbooks           |  Resolution:  fixed
 Keywords:  has-patch needs-ui  |
--------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4267"]:
 {{{
 #!CommitTicketReference repository="" revision="4267"
 Breathe: Improve spacing around 3rd tier list elements of chapters listing
 in handbook sidebar.

 Fixes #814.
 }}}

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

From noreply at wordpress.org  Wed Oct 19 18:10:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 18:10:04 -0000
Subject: [wp-meta] [Making WordPress.org] #814: Balance spacing on tier
 3 sidebar items
In-Reply-To: <057.3c05bc82fc1dfd5988e98c96b752906c@wordpress.org>
References: <057.3c05bc82fc1dfd5988e98c96b752906c@wordpress.org>
Message-ID: <072.c44027e183122d11f20dcd6d07b7c0b5@wordpress.org>

#814: Balance spacing on tier 3 sidebar items
--------------------------------+------------------
 Reporter:  Craig Ralston       |       Owner:
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:
Component:  Handbooks           |  Resolution:
 Keywords:  has-patch needs-ui  |
--------------------------------+------------------

Comment (by coffee2code):

 In [changeset:"4266"]:
 {{{
 #!CommitTicketReference repository="" revision="4266"
 W.org P2 child theme: Improve spacing around 3rd tier list elements of
 chapters listing in handbook sidebar.

 Props craig-ralston.
 See #814.
 }}}

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

From noreply at wordpress.org  Wed Oct 19 18:15:36 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 18:15:36 +0000 (UTC)
Subject: [wp-meta] [4268]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/style.css: Breathe: A nested list should have the same font
 size as its parent.
Message-ID: <20161019181536.4AC8E1080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 18:15:36 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 18:15:36 -0000
Subject: [wp-meta] [Making WordPress.org] #2150: Breathe: Child menu
 items are larger than parent items
In-Reply-To: <058.61885c0c5a8cf4b4c2aa09776a727000@wordpress.org>
References: <058.61885c0c5a8cf4b4c2aa09776a727000@wordpress.org>
Message-ID: <073.51903c4bd32d9a99397a4f17d08d975a@wordpress.org>

#2150: Breathe: Child menu items are larger than parent items
--------------------------------------+--------------------------
 Reporter:  SergeyBiryukov            |       Owner:  coffee2code
     Type:  defect                    |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4268"]:
 {{{
 #!CommitTicketReference repository="" revision="4268"
 Breathe: A nested list should have the same font size as its parent.

 Overrides p2-breathe styling.

 Fixes #2150.
 }}}

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

From noreply at wordpress.org  Wed Oct 19 18:36:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 18:36:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2154: Ensures that
 i18n-teams.css loads after P2-Breath to prevent getting overridden.
In-Reply-To: <052.486109d2fbb26828045ad337f0d707c8@wordpress.org>
References: <052.486109d2fbb26828045ad337f0d707c8@wordpress.org>
Message-ID: <067.b00ee9e50c7d76f3667b67492f528b38@wordpress.org>

#2154: Ensures that i18n-teams.css loads after P2-Breath to prevent getting
overridden.
-----------------------------------------+------------------
 Reporter:  Kenshino                     |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Make (Get Involved) / P2     |  Resolution:
 Keywords:  has-patch reporter-feedback  |
-----------------------------------------+------------------
Changes (by coffee2code):

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


Comment:

 @Kenshino: Can you provide before and after screenshots of an example of
 what this change will fix? The table on the page looks the same before and
 after the patch is applied, which is to say it still looks bad at small
 page widths. (I verified that the CSS source ordering was changed to
 ensure i18n-teams.css came after the p2-breathe styling as you intended.)

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

From noreply at wordpress.org  Wed Oct 19 19:09:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 19:09:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2146: Topics should also have
 user badges
In-Reply-To: <050.862bb5d62a6ea57cbc603029f926efd3@wordpress.org>
References: <050.862bb5d62a6ea57cbc603029f926efd3@wordpress.org>
Message-ID: <065.b82b229931270e19b246a67fd73ac22c@wordpress.org>

#2146: Topics should also have user badges
----------------------------+--------------------------
 Reporter:  netweb          |       Owner:  coffee2code
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:  needs-patch     |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4269"]:
 {{{
 #!CommitTicketReference repository="" revision="4269"
 Support Forums, User Badges: Allow author badges to display for topics as
 well.

 Also adds some missing docblocks and explicitly return false rather than
 null in a few places.

 Fixes #2146.
 }}}

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

From noreply at wordpress.org  Wed Oct 19 19:09:38 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 19:09:38 +0000 (UTC)
Subject: [wp-meta] [4269]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-bbp-user-badges/inc/class-plugin.php: Support Forums,
 User Badges:  Allow author badges to display for topics as well.
Message-ID: <20161019190938.338941080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 19:16:12 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 19:16:12 +0000 (UTC)
Subject: [wp-meta] [4270]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-p2/functions.php: W.org P2 child theme: Bump CSS version for cache
 bust.
Message-ID: <20161019191612.842321080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 19:18:02 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 19:18:02 +0000 (UTC)
Subject: [wp-meta] [4271]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-breathe/functions.php: Breathe: Bump CSS version for cache bust.
Message-ID: <20161019191802.3B2791080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 20:04:19 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 20:04:19 +0000 (UTC)
Subject: [wp-meta] [4273]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/
 wcpt-wordcamp/wordcamp-new-site.php: WordCamp Post Type: Delete `_site_id`
 when clearing URL
Message-ID: <20161019200419.BFA471080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 20:04:15 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 20:04:15 +0000 (UTC)
Subject: [wp-meta] [4272]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/
 wcpt-wordcamp/wordcamp-new-site.php: WordCamp Post Type: Return early
 instead of indenting to improve readability
Message-ID: <20161019200415.1F0581080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 20:04:24 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 19 Oct 2016 20:04:24 +0000 (UTC)
Subject: [wp-meta] [4274]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/
 wcpt-wordcamp/wordcamp-new-site.php: WordCamp Post Type: Re-align
 statements after r4272
Message-ID: <20161019200424.7DEFD1080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 19 22:55:19 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 19 Oct 2016 22:55:19 -0000
Subject: [wp-meta]
 =?utf-8?b?W01ha2luZyBXb3JkUHJlc3Mub3JnXSAjMjEzMzog4oCc?=
 =?utf-8?q?Last_updated=E2=80=9D_time_not_updated_when_updating_=E2=80=9CT?=
 =?utf-8?q?ested_up_to=E2=80=9D_in_repo?=
In-Reply-To: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
References: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
Message-ID: <068.2372cc397f4415fba75eca7e3933485a@wordpress.org>

#2133: ?Last updated? time not updated when updating ?Tested up to? in repo
------------------------------+-----------------------
 Reporter:  geekysoft         |       Owner:
     Type:  defect            |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------
Changes (by geekysoft):

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


Comment:

 It?s not fixed.

 The [https://wordpress.org/plugins/post-archival/ post-archival plugin]
 was [https://plugins.trac.wordpress.org/log/post-archival/tags?rev=1518147
 updated a week ago]. The [https://wordpress.org/plugins-wp/post-archival/
 new page] shows ?Tested up to: 4.6.1? and yet ?Last updated: 5 months
 ago?. The [https://wordpress.org/plugins/post-archival/ old page] shows
 ?Tested up to: 4.6.1? and ?Last updated: 1 week ago?.

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

From noreply at wordpress.org  Thu Oct 20 00:28:51 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 00:28:51 -0000
Subject: [wp-meta]
 =?utf-8?b?W01ha2luZyBXb3JkUHJlc3Mub3JnXSAjMjEzMzog4oCc?=
 =?utf-8?q?Last_updated=E2=80=9D_time_not_updated_when_updating_=E2=80=9CT?=
 =?utf-8?q?ested_up_to=E2=80=9D_in_repo?=
In-Reply-To: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
References: <053.427ed51275b4248fe95ee92cf4f6a51a@wordpress.org>
Message-ID: <068.e71c8767ed7908586675f8baa108e206@wordpress.org>

#2133: ?Last updated? time not updated when updating ?Tested up to? in repo
------------------------------+-----------------------
 Reporter:  geekysoft         |       Owner:
     Type:  defect            |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 Yeah.. not sure what happened here.

 The import a week ago succeeded, but `post_modified` and `last_updated`
 meta didn't update.
 Re-running the import command from logs also succeeded, but they updated
 this time.

 We're not checking the return value from `wp_update_post()` or the other
 `update_post_meta()` / `wp_set_post_terms()` calls, so it's entirely
 possible that they've failed.

 I've improved some of the logging and will see if anything pops up. If
 anyone spots other plugins which don't update with a commit after ''now''
 then let me know.

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

From noreply at wordpress.org  Thu Oct 20 00:34:46 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Oct 2016 00:34:46 +0000 (UTC)
Subject: [wp-meta] [4275]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/wcpt/
 wcpt-wordcamp/wordcamp-new-site.php: WordCamp Post Type: Ensure
 `maybe_create_new_site()` only runs once
Message-ID: <20161020003446.2D94D1080630@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 20 04:07:33 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Oct 2016 04:07:33 +0000 (UTC)
Subject: [wp-meta] [4276]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/class-capabilities.php: Plugin directory: Fix a PHP
 warning introduced in [4260].
Message-ID: <20161020040733.64A5F1080630@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 20 04:07:33 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 04:07:33 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.0357ed9ab1d379532b3f9bf9782dfbea@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------

Comment (by pento):

 In [changeset:"4276"]:
 {{{
 #!CommitTicketReference repository="" revision="4276"
 Plugin directory: Fix a PHP warning introduced in [4260].

 The return value of `get_the_terms()` needs to be tested to ensure it's an
 array.

 See #2111.
 }}}

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

From noreply at wordpress.org  Thu Oct 20 04:19:40 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 20 Oct 2016 04:19:40 +0000 (UTC)
Subject: [wp-meta] [4277] sites/trunk/common/includes/slack/trac/config.php:
 Slack: When piping commit messages into channels,
 re-enable core themes being sent to #core, originally disable in [1121].
Message-ID: <20161020041940.5B8591080630@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 20 13:54:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 13:54:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2159: WordCamp Organizers: Add a
 custom taxonomy for teams
Message-ID: <051.f912ee03564157103d5a560640e6a177@wordpress.org>

#2159: WordCamp Organizers: Add a custom taxonomy for teams
-------------------------------------+-----------------------
 Reporter:  Kau-Boy                  |      Owner:
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  WordCamp Site & Plugins  |   Keywords:  has-patch
-------------------------------------+-----------------------
 I am part of the WCEU organizing team and as we are currently around 50
 organizers, we are split into different groups. We want to show these
 different groups on the organizers page and therefore need a custom
 taxonomy as well as a shortcode argument.

 I already implemented this new custom taxonomy and we tested it on our
 staging site. All looks good so far.

 I also tried to stick as close to the current code as possible. The new
 custom taxonomy and shortcode argument should also not create any issues
 with current WordCamp sites.

 It would really help us a lot, if this could be merged in as soon as
 possible :)

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

From noreply at wordpress.org  Thu Oct 20 13:58:05 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 13:58:05 -0000
Subject: [wp-meta] [Making WordPress.org] #2159: WordCamp Organizers:
 Add a custom taxonomy for teams
In-Reply-To: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
References: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
Message-ID: <066.7bb8b40a69ec7011a8a804ecd2a3489b@wordpress.org>

#2159: WordCamp Organizers: Add a custom taxonomy for teams
-------------------------------------+------------------
 Reporter:  Kau-Boy                  |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+------------------
Changes (by Kau-Boy):

 * type:  defect => enhancement


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

From noreply at wordpress.org  Thu Oct 20 14:11:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 14:11:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2159: WordCamp Organizers:
 Add a custom taxonomy for teams
In-Reply-To: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
References: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
Message-ID: <066.5bae65fa83cc4a6d73f674738a3c1bb9@wordpress.org>

#2159: WordCamp Organizers: Add a custom taxonomy for teams
-------------------------------------+------------------
 Reporter:  Kau-Boy                  |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+------------------

Comment (by sonjanyc):

 Thanks Bernhard for working on this!
 We wanted to extend this functionality so any WordCamp, especially larger
 ones like WordCamp U.S. and WordCamp Europe, with bigger organizing teams
 can take advantage of it, and structure the org team page better.

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

From noreply at wordpress.org  Thu Oct 20 16:36:08 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 16:36:08 -0000
Subject: [wp-meta] [Making WordPress.org] #2160: Flagging postings
Message-ID: <051.f39fc98a4964317369eea7d62917ec2f@wordpress.org>

#2160: Flagging postings
---------------------------------------+-----------------
 Reporter:  Clorith                    |      Owner:
     Type:  defect                     |     Status:  new
 Priority:  normal                     |  Milestone:
Component:  Jobs (jobs.wordpress.net)  |   Keywords:
---------------------------------------+-----------------
 When viewing individual offerings there is a little flag followed by the
 position type when viewing General.

 This is the icon for "General", but the visual implication is that this is
 a means to flag a post for moderation.

 The icon should either be changed to something less confusing, or an
 actual flag mechanic should be considered that would fit in nicely in that
 location.

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

From noreply at wordpress.org  Thu Oct 20 16:38:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 16:38:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2160: Flagging postings
In-Reply-To: <051.f39fc98a4964317369eea7d62917ec2f@wordpress.org>
References: <051.f39fc98a4964317369eea7d62917ec2f@wordpress.org>
Message-ID: <066.6e6ee66457b917ef9a7217c33dc6bb8e@wordpress.org>

#2160: Flagging postings
---------------------------------------+------------------
 Reporter:  Clorith                    |       Owner:
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Jobs (jobs.wordpress.net)  |  Resolution:
 Keywords:                             |
---------------------------------------+------------------

Comment (by melchoyce):

 Maybe we could use something like
 https://developer.wordpress.org/resource/dashicons/#businessman or
 https://developer.wordpress.org/resource/dashicons/#desktop instead?

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

From noreply at wordpress.org  Thu Oct 20 16:42:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 16:42:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2160: Flagging postings
In-Reply-To: <051.f39fc98a4964317369eea7d62917ec2f@wordpress.org>
References: <051.f39fc98a4964317369eea7d62917ec2f@wordpress.org>
Message-ID: <066.e2a83c3ad49838dc31b0bc241d595d06@wordpress.org>

#2160: Flagging postings
---------------------------------------+------------------
 Reporter:  Clorith                    |       Owner:
     Type:  defect                     |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Jobs (jobs.wordpress.net)  |  Resolution:
 Keywords:                             |
---------------------------------------+------------------

Comment (by Clorith):

 The businessman one looks like it would go best with the current set of
 postings I see in general, they all seem to target individuals so +1 for
 that

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

From noreply at wordpress.org  Thu Oct 20 16:45:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 16:45:43 -0000
Subject: [wp-meta] [Making WordPress.org] #2161: Support Theme topic page
 shows replies butted up against pagination
Message-ID: <048.14790cbc25409293fb10f3715e6bc3cc@wordpress.org>

#2161: Support Theme topic page shows replies butted up against pagination
----------------------------+-------------------------------------
 Reporter:  mapk            |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch ui-feedback
----------------------------+-------------------------------------
 The 'viewing replies...' text is too close to the pagination both on the
 top and bottom of the topic/replies.

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

 The 'viewing replies' text should probably be left aligned.

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

From noreply at wordpress.org  Thu Oct 20 16:53:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 16:53:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Forum Theme: Post notices
 push content down
Message-ID: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>

#2162: Forum Theme: Post notices push content down
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 The `clear: both` from bb core is causing some headaches in the new theme
 with displaying post content, as they drop down to below the author
 section.

 Applying a `clear: none` to `.bbpress #bbpress-forums div.bbp-template-
 notice` in https://wordpress.org/support/wp-content/themes/pub/wporg-
 support/sass/site/_bbpress.scss sorts out the pushing of notices.

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

From noreply at wordpress.org  Thu Oct 20 16:58:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 16:58:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2163: Support Theme forum page
 shows the wrong 'last activity' date/post in the sidebar
Message-ID: <048.4cceb4d4e20b37309daba04f264be8e4@wordpress.org>

#2163: Support Theme forum page shows the wrong 'last activity' date/post in the
sidebar
----------------------------+-------------------------
 Reporter:  mapk            |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch
----------------------------+-------------------------
 The Last Activity in the sidebar shows the wrong the date and post link.
 Notice how the one in the image says last activity was 5 months ago, but
 the most recent post was 14 minutes ago.

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

 The logic for this may have gotten messed up with the theme switch, I'm
 uncertain.

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

From noreply at wordpress.org  Thu Oct 20 17:00:40 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 17:00:40 -0000
Subject: [wp-meta] [Making WordPress.org] #2163: Support Theme forum
 page shows the wrong 'last activity' date/post in the sidebar
In-Reply-To: <048.4cceb4d4e20b37309daba04f264be8e4@wordpress.org>
References: <048.4cceb4d4e20b37309daba04f264be8e4@wordpress.org>
Message-ID: <063.012001ceacb1d27ffe83e435833c6441@wordpress.org>

#2163: Support Theme forum page shows the wrong 'last activity' date/post in the
sidebar
----------------------------+------------------------
 Reporter:  mapk            |       Owner:
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  duplicate
 Keywords:                  |
----------------------------+------------------------
Changes (by ocean90):

 * keywords:  needs-patch =>
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #2109.

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

From noreply at wordpress.org  Thu Oct 20 22:47:21 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 20 Oct 2016 22:47:21 -0000
Subject: [wp-meta] [Making WordPress.org] #2164: Forum Theme: pagination on
 profiles pushes content left
Message-ID: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>

#2164: Forum Theme: pagination on profiles pushes content left
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 Looking at topics and posts created in a profile the float for the bbp
 navigation causes things to be pushed to the left

 Topics:
 [[Image(http://imgur.com/wftYWx0.png)]]

 Posts:
 [[Image(http://imgur.com/rumvZCx.png)]]

 Seems caused by a `float: right;` in https://wordpress.org/support/wp-
 content/themes/pub/wporg-support/sass/site/_bbpress.scss:128

 For reference here's the replies page with the float back at `float:
 none`from the bb-base style:

 [[Image(http://imgur.com/IcDROIP.png)]]

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

From noreply at wordpress.org  Fri Oct 21 04:23:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 04:23:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Forum Theme: Post
 notices push content down
In-Reply-To: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
References: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
Message-ID: <066.25a0ccf4e1304da27ad0150f5d6cf156@wordpress.org>

#2162: Forum Theme: Post notices push content down
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 A screenshot would be helpful here.

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

From noreply at wordpress.org  Fri Oct 21 05:57:46 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 05:57:46 +0000 (UTC)
Subject: [wp-meta] [4278] sites/trunk/wordpress.org/public_html/wp-content:
 Plugin Directory: Add some basic Committer/Contributor widgets for the
 plugin "admin" view.
Message-ID: <20161021055746.3289810805A0@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 05:57:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 05:57:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.91990405a1de97c9ce552dec288f52da@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4278"]:
 {{{
 #!CommitTicketReference repository="" revision="4278"
 Plugin Directory: Add some basic Committer/Contributor widgets for the
 plugin "admin" view.

 See #2111
 }}}

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

From noreply at wordpress.org  Fri Oct 21 06:09:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 06:09:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2164: Forum Theme: pagination
 on profiles pushes content left
In-Reply-To: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
References: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
Message-ID: <066.ca787c88a7d3e1de817862e7e53e6eaa@wordpress.org>

#2164: Forum Theme: pagination on profiles pushes content left
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 Should be similar to this:

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

 Also the headers on each page (similar to the `Viewing 8 discussions of 28
 total` above:
 * Topics header: `Viewing 15 topics - 1 through 15 (of 20 total)`
 * Replies header: `Viewing 15 posts - 1 through 15 (of 1,254 total)`

 The replies header is there, topics header is not, topics were removed in
 [3898]

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

From noreply at wordpress.org  Fri Oct 21 07:45:16 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 07:45:16 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Forum Theme: Post
 notices push content down
In-Reply-To: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
References: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
Message-ID: <066.19e52edd8cdc1fc26037469bcb7d2666@wordpress.org>

#2162: Forum Theme: Post notices push content down
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 Ahh of course, forgot to add them, here they come:

 The current display of a post if it has a notice
 [[Image(http://imgur.com/By0jS15.png)]]

 Here is the same view if we introduce the `clear: none`
 [[Image(http://imgur.com/9a262WW.png)]]

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

From noreply at wordpress.org  Fri Oct 21 08:30:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 08:30:04 -0000
Subject: [wp-meta] [Making WordPress.org] #2165: Easier thread control for
 plugin/theme authors
Message-ID: <051.4456d51b2130b795c3fc933fc13e12b8@wordpress.org>

#2165: Easier thread control for plugin/theme authors
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 We currently let plugin and theme authors do a bit more with topics in
 their own support forums, but this is all hidden behind a hover-to-show
 link on a topics original post.

 We should introduce the sidebar widget on topics for these users when
 applicable so they don't need to go hunting for the options they should
 have access to.

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

From noreply at wordpress.org  Fri Oct 21 08:35:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 08:35:04 -0000
Subject: [wp-meta] [Making WordPress.org] #2166: Forum Theme: Moving topics
 needs style wrappers
Message-ID: <051.3f6487a93948602d41039ed044d1c46a@wordpress.org>

#2166: Forum Theme: Moving topics needs style wrappers
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 When acting on a post in a topic (in this case moving a post out into its
 own thread), the content is shown wit hthe sidebars pushed under

 [[Image(http://imgur.com/I3LYt0o.png)]]

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

From noreply at wordpress.org  Fri Oct 21 08:52:19 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 08:52:19 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Forum Theme: No easy access
 to your profile
Message-ID: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>

#2167: Forum Theme: No easy access to your profile
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 In all previous versions of the theme we've had the username displayed at
 the top of the page which takes you to the bbPress, in the new theme there
 is no clean way unless you know the URL your self or go find one of your
 previous posts.

 One alternative would be changing the profile link in the admin bar to
 redirect to the profile page of our choosing instead of the default
 WordPress one, and making the bar visible to all users.

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

From noreply at wordpress.org  Fri Oct 21 09:06:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 09:06:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2168: Forum notification emails
 don't say which plugin they relate to
Message-ID: <055.eb5efed1ee65ab25d29a381d30c32edf@wordpress.org>

#2168: Forum notification emails don't say which plugin they relate to
----------------------------+-------------------------
 Reporter:  hlashbrooke     |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:  needs-patch
----------------------------+-------------------------
 As a plugin author, when I receive an email notification from the support
 forum for any activity on my plugin's forums the email does not say which
 plugin it relates to. I have 15 plugins in the directory (but there are
 other authors with way more than that) and sometimes the review or the
 support request is so generic that the content doesn't help to indicate
 which plugin it is a query about.

 It would be great if the email body had the plugin name (or at least the
 slug) at the top so that it would be more clear which plugin the email is
 referring to. Having the plugin name in the subject line as well as the
 email body would be ideal.

 I'll attach a screenshot of an email as an example of what content is
 currently included.

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

From noreply at wordpress.org  Fri Oct 21 09:14:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 09:14:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2168: Forum notification
 emails don't say which plugin they relate to
In-Reply-To: <055.eb5efed1ee65ab25d29a381d30c32edf@wordpress.org>
References: <055.eb5efed1ee65ab25d29a381d30c32edf@wordpress.org>
Message-ID: <070.4f216afa84224c6d3ab28667863d51ca@wordpress.org>

#2168: Forum notification emails don't say which plugin they relate to
----------------------------+------------------------
 Reporter:  hlashbrooke     |       Owner:
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  duplicate
 Keywords:                  |
----------------------------+------------------------
Changes (by ocean90):

 * keywords:  needs-patch =>
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #2016.

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

From noreply at wordpress.org  Fri Oct 21 10:06:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 10:06:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2169: Forum Theme: Individual
 reviews do not show star ratings
Message-ID: <051.75802c844716edb03e28ccd6d0159fb4@wordpress.org>

#2169: Forum Theme: Individual reviews do not show star ratings
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 Viewing individual reviews show no star ratings in the new forum theme.

 The stars are displayed as expected in the list of reviews for a plugin or
 theme so only individual views are missing this.

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

From noreply at wordpress.org  Fri Oct 21 12:15:37 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 12:15:37 -0000
Subject: [wp-meta] [Making WordPress.org] #2170: sidebar too wide
Message-ID: <053.697026b69e3596efe244df95e27a121d@wordpress.org>

#2170: sidebar too wide
----------------------------+-----------------
 Reporter:  sterndata       |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 a thought on the new UI -- make the sidebar 20% and the entry-content 75%.
 Give more room to the content. none of the links on the sidebar require
 going to 30%.

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

From noreply at wordpress.org  Fri Oct 21 12:25:22 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 12:25:22 -0000
Subject: [wp-meta] [Making WordPress.org] #2170: sidebar too wide
In-Reply-To: <053.697026b69e3596efe244df95e27a121d@wordpress.org>
References: <053.697026b69e3596efe244df95e27a121d@wordpress.org>
Message-ID: <068.fe01cbdac0a00edfa34958e6869a6fa6@wordpress.org>

#2170: sidebar too wide
----------------------------+------------------
 Reporter:  sterndata       |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 I like keeping it at 30%, the sidebar accounts for more than just a few
 view links, it has to work with plugin and theme pages (with icons), and
 also translations which are generally longer than English strings, so
 giving them a little bit more to work with is fine.

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

From noreply at wordpress.org  Fri Oct 21 13:26:48 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 13:26:48 -0000
Subject: [wp-meta] [Making WordPress.org] #2170: Support Theme: Sidebar
 too wide (was: sidebar too wide)
In-Reply-To: <053.697026b69e3596efe244df95e27a121d@wordpress.org>
References: <053.697026b69e3596efe244df95e27a121d@wordpress.org>
Message-ID: <068.89b6fcf45c46441432dae35862f9b195@wordpress.org>

#2170: Support Theme: Sidebar too wide
----------------------------+------------------
 Reporter:  sterndata       |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 I actually like the sidebar as is. As @Clorith mentioned, it's more
 friendly for translations, and localized forum admins always appreciate
 UIs that don't cause unnecesary wrapping.

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

From noreply at wordpress.org  Fri Oct 21 13:32:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 13:32:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2159: WordCamp Organizers:
 Add a custom taxonomy for teams
In-Reply-To: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
References: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
Message-ID: <066.9e70b6926fd0d10661be363837d0fd56@wordpress.org>

#2159: WordCamp Organizers: Add a custom taxonomy for teams
-------------------------------------+------------------
 Reporter:  Kau-Boy                  |       Owner:
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch commit         |
-------------------------------------+------------------
Changes (by SergeyBiryukov):

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


Comment:

 [attachment:2159.diff] seems like a good first step to extend this
 functionality for all WordCamps.

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

From noreply at wordpress.org  Fri Oct 21 14:48:54 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 14:48:54 -0000
Subject: [wp-meta] [Making WordPress.org] #2171: Forums: "+X hidden" link
 should include archived posts
Message-ID: <058.ae14ca749e5a414205c17bcf3e37a19c@wordpress.org>

#2171: Forums: "+X hidden" link should include archived posts
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 With the introduction of the "Archived" status, there's no way to know if
 the current topic has any archived posts, unless you add `?view=all` to
 the URL manually.

 Related: #1984, #2043.

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

From noreply at wordpress.org  Fri Oct 21 14:51:00 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 14:51:00 -0000
Subject: [wp-meta] [Making WordPress.org] #2043: Last Post ignores post
	status
In-Reply-To: <051.3e7c22e2d3a403baf305c5ef13b7c8a3@wordpress.org>
References: <051.3e7c22e2d3a403baf305c5ef13b7c8a3@wordpress.org>
Message-ID: <066.d37de4d1055bc2157a2df165e81fa566@wordpress.org>

#2043: Last Post ignores post status
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Replying to [comment:3 netweb]:
 > No, this is actually because the custom "Archive" status added here on
 w.org, as such the `?view=all` has not been added to take into account
 this custom status, we'll add that as part of #1984

 #1984 is about the UI, while this is a functionality issue. Created a
 separate ticket for that: #2171.

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

From noreply at wordpress.org  Fri Oct 21 15:01:20 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:01:20 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Support Theme: Post
 notices push content down (was: Forum Theme: Post notices push content
 down)
In-Reply-To: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
References: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
Message-ID: <066.425f923813e3b62284804403d8c3d47b@wordpress.org>

#2162: Support Theme: Post notices push content down
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 The border on the notice is also missing, and it's hard to see light
 orange on light pink.

 @mapk: Is that intentional? In the old theme, the notice was much more...
 noticeable :) See [attachment:meta-2162.png].

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

From noreply at wordpress.org  Fri Oct 21 15:03:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:03:50 -0000
Subject: [wp-meta] [Making WordPress.org] #2164: Support Theme:
 Pagination on profiles pushes content left (was: Forum Theme: pagination on
 profiles pushes content left)
In-Reply-To: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
References: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
Message-ID: <066.e90ffbd438546dafe7a08431c910a5d9@wordpress.org>

#2164: Support Theme: Pagination on profiles pushes content left
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

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

From noreply at wordpress.org  Fri Oct 21 15:04:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:04:12 -0000
Subject: [wp-meta] [Making WordPress.org] #2166: Support Theme: Moving
 topics needs style wrappers (was: Forum Theme: Moving topics needs style
 wrappers)
In-Reply-To: <051.3f6487a93948602d41039ed044d1c46a@wordpress.org>
References: <051.3f6487a93948602d41039ed044d1c46a@wordpress.org>
Message-ID: <066.1702c0ae1092449462be4caeb9f3a7d8@wordpress.org>

#2166: Support Theme: Moving topics needs style wrappers
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

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

From noreply at wordpress.org  Fri Oct 21 15:04:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:04:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile (was: Forum Theme: No easy access to your profile)
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.931f0b8a820ac4b5964099e35858694c@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

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

From noreply at wordpress.org  Fri Oct 21 15:08:39 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:08:39 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.75cdc5ca8012e6203cb986a386aa98b0@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 Yeah, the issue with large screen-wide subheadings is that some important
 links are gone and now require additional actions instead of a single
 click.

 See #2156 for a similar issue with "My Favorites" link in the new plugin
 directory.

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

From noreply at wordpress.org  Fri Oct 21 15:09:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:09:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2169: Support Theme:
 Individual reviews do not show star ratings (was: Forum Theme: Individual
 reviews do not show star ratings)
In-Reply-To: <051.75802c844716edb03e28ccd6d0159fb4@wordpress.org>
References: <051.75802c844716edb03e28ccd6d0159fb4@wordpress.org>
Message-ID: <066.2c39c5ffc15057b3269601fe36b29373@wordpress.org>

#2169: Support Theme: Individual reviews do not show star ratings
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

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

From noreply at wordpress.org  Fri Oct 21 15:32:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:32:27 -0000
Subject: [wp-meta] [Making WordPress.org] #1913: Expand documentation of
 WP_Term_Query() in Code Reference.
In-Reply-To: <057.ec0e58eaef9334630b9d1e5af3ead8a1@wordpress.org>
References: <057.ec0e58eaef9334630b9d1e5af3ead8a1@wordpress.org>
Message-ID: <072.59f0a5d5c15923b55c2ded5afbe1844c@wordpress.org>

#1913: Expand documentation of WP_Term_Query() in Code Reference.
-----------------------------+---------------------------
 Reporter:  kevinwhoffman    |       Owner:  DrewAPicture
     Type:  enhancement      |      Status:  accepted
 Priority:  normal           |   Milestone:
Component:  Developer Hub    |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+---------------------------
Changes (by keesiemeijer):

 * keywords:   => has-screenshots


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

From noreply at wordpress.org  Fri Oct 21 15:28:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 15:28:44 -0000
Subject: [wp-meta] [Making WordPress.org] #1913: Expand documentation of
 WP_Term_Query() in Code Reference.
In-Reply-To: <057.ec0e58eaef9334630b9d1e5af3ead8a1@wordpress.org>
References: <057.ec0e58eaef9334630b9d1e5af3ead8a1@wordpress.org>
Message-ID: <072.23cbc069acb7a3c662d41ca45543ba08@wordpress.org>

#1913: Expand documentation of WP_Term_Query() in Code Reference.
---------------------------+---------------------------
 Reporter:  kevinwhoffman  |       Owner:  DrewAPicture
     Type:  enhancement    |      Status:  accepted
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:                 |
---------------------------+---------------------------

Comment (by keesiemeijer):

 Screenshot [attachment:1913.png]  is a simple UI mock-up for adding
 parameters to Class pages. You can choose from three options:

 * Use parameters from a class method.
 * Use parameters from another post. (Some classes use the parameters from
 their parent class)
 * Use Text. ( Link to parameters, or explain them )

 Your thoughts on this UI are welcome.

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

From noreply at wordpress.org  Fri Oct 21 16:10:02 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 16:10:02 +0000 (UTC)
Subject: [wp-meta] [4280]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/
 wordcamp-site-cloner: WordCamp Site Cloner: Convert to REST/ Backbone to
 improve scalability
Message-ID: <20161021161002.45BF41080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 16:10:08 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 16:10:08 +0000 (UTC)
Subject: [wp-meta] [4281]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/
 wordcamp-site-cloner/wordcamp-site-cloner.css: WordCamp Site Cloner:
 Re-align whitespace
Message-ID: <20161021161008.1A1D61080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 16:10:08 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 16:10:08 -0000
Subject: [wp-meta] [Making WordPress.org] #1112: Site Cloner: Scale to
 support hundreds of sites
In-Reply-To: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
References: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
Message-ID: <066.f32d60348b2418cb7a838d438d103bc1@wordpress.org>

#1112: Site Cloner: Scale to support hundreds of sites
-------------------------------------+-----------------------
 Reporter:  iandunn                  |       Owner:  iandunn
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+-----------------------

Comment (by iandunn):

 In [changeset:"4281"]:
 {{{
 #!CommitTicketReference repository="" revision="4281"
 WordCamp Site Cloner: Re-align whitespace

 See #1112
 }}}

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

From noreply at wordpress.org  Fri Oct 21 16:10:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 16:10:02 -0000
Subject: [wp-meta] [Making WordPress.org] #1112: Site Cloner: Scale to
 support hundreds of sites
In-Reply-To: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
References: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
Message-ID: <066.52de7f5f0f3ee46bf0bcc6fe4c9d0071@wordpress.org>

#1112: Site Cloner: Scale to support hundreds of sites
-------------------------------------+-----------------------
 Reporter:  iandunn                  |       Owner:  iandunn
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+-----------------------

Comment (by iandunn):

 In [changeset:"4280"]:
 {{{
 #!CommitTicketReference repository="" revision="4280"
 WordCamp Site Cloner: Convert to REST/Backbone to improve scalability

 See #1112
 Props prettyboymp
 }}}

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

From noreply at wordpress.org  Fri Oct 21 16:13:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 16:13:04 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Support Theme: Post
 notices push content down
In-Reply-To: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
References: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
Message-ID: <066.bbb7fb314777cff976f1f93263f5ff07@wordpress.org>

#2162: Support Theme: Post notices push content down
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by mapk):

 This was not intentional.

 Overall, dropping the borders from the notifications ''is'' a design
 decision I was hoping to implement throughout the site, but I didn't
 realize they showed up on top of the light pink forum posts.

 Can we drop the background of these posts since there's a notification?
 Isn't the notification enough to signify the status of this post?

 Also, I notice these posts don't follow the layout of the new forum posts.
 We should probably fix that. Maybe a new ticket? I also noticed the
 pending posts page needs a lot of work.

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

From noreply at wordpress.org  Fri Oct 21 16:09:56 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 16:09:56 +0000 (UTC)
Subject: [wp-meta] [4279]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins: WordCamp Coming
 Soon Page: Define `wp.customize.WordCamp` before referencing it
Message-ID: <20161021160956.D8E471080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 16:17:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 16:17:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Support Theme: Post
 notices push content down
In-Reply-To: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
References: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
Message-ID: <066.46c1792a36d89206c0c2cadb52e5dc5b@wordpress.org>

#2162: Support Theme: Post notices push content down
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 I'd be more than happy to see the background colours go away, they reduce
 readability even for those with "normal" eyesight.

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

From noreply at wordpress.org  Fri Oct 21 17:05:20 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 17:05:20 +0000 (UTC)
Subject: [wp-meta] [4282]
 sites/trunk/common/includes/slack/announce/config.php: Slack: Rename the
 `core-image` channel to `core-media`.
Message-ID: <20161021170520.6A6F21080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 18:50:51 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 18:50:51 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.5c2b951c12e4959988103d5e4b6ba2f7@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by bcworkz):

 Not having an easy link to one's profile is certainly annoying. I think
 not having the related log in/out links that were next to the profile link
 is an even bigger problem.

 It'd also be nice to have a log in link in the "You must be logged in to
 reply to this topic" message that appears where the reply form usually
 occurs.

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

From noreply at wordpress.org  Fri Oct 21 19:46:50 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 19:46:50 -0000
Subject: [wp-meta] [Making WordPress.org] #2172: Support Theme: 3 up forums
 list needs consistent CSS units
Message-ID: <051.62dada9c8a79981d13695b691f70b87a@wordpress.org>

#2172: Support Theme: 3 up forums list needs consistent CSS units
-------------------------+-------------------------------------------------
 Reporter:  bcworkz      |      Owner:
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Support      |   Keywords:  needs-patch ui-feedback has-
  Forums                 |  screenshots
-------------------------+-------------------------------------------------
 To prevent potential clipping as shown in attached screenshot, (the "View
 forum >" links in two instances) the individual div heights should be a
 multiple of font height and line height properties and use the same units.

 Right now font height is 0.8rem and line height is 1.5, which may be fine,
 but the div height is 200px. The units here should match the font height,
 i.e. rem. As things stand, I suggest 10.8rem (0.8 * 1.5 * 9) is a better
 div height than an arbitrary pixel height. This accounts for variances in
 browser and user provided fonts and sizing.

 Of course the final rem height would need to be adjusted once the forum
 titles and descriptions are finalized. Further accommodation may be needed
 due to different lengths of translated content.

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

From noreply at wordpress.org  Fri Oct 21 20:30:29 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 20:30:29 +0000 (UTC)
Subject: [wp-meta] [4283]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-plugins/front-page.php: Plugin Directory: Add 'My Favorites' section
 to the front page if the user is logged in and has favorites.
Message-ID: <20161021203029.34E2B1080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 20:30:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 20:30:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2156: Plugin Directory: No
 "My Favorites" link on home page
In-Reply-To: <058.51b2f86b475c1364fe6f33e767c26c86@wordpress.org>
References: <058.51b2f86b475c1364fe6f33e767c26c86@wordpress.org>
Message-ID: <073.565e38e9a8ac56bf2c4c59c3b502a495@wordpress.org>

#2156: Plugin Directory: No "My Favorites" link on home page
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4283"]:
 {{{
 #!CommitTicketReference repository="" revision="4283"
 Plugin Directory: Add 'My Favorites' section to the front page if the user
 is logged in and has favorites.

 Fixes #2156.
 }}}

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

From noreply at wordpress.org  Fri Oct 21 20:33:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 20:33:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2156: Plugin Directory: No
 "My Favorites" link on home page
In-Reply-To: <058.51b2f86b475c1364fe6f33e767c26c86@wordpress.org>
References: <058.51b2f86b475c1364fe6f33e767c26c86@wordpress.org>
Message-ID: <073.ca521f0e8a20d54c7d671d68230087c7@wordpress.org>

#2156: Plugin Directory: No "My Favorites" link on home page
------------------------------+--------------------------
 Reporter:  SergeyBiryukov    |       Owner:  coffee2code
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+--------------------------

Comment (by coffee2code):

 In keeping with the format of the front page, 'My Favorites' was added as
 a section alongside 'Featured', 'Popular', and 'Beta', and also with a
 link to the favorites view from there.

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

From noreply at wordpress.org  Fri Oct 21 20:47:41 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 20:47:41 +0000 (UTC)
Subject: [wp-meta] [4284]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-support:
 Support Theme: Fix display of user topic and reply listings due to float of
 pagination controls.
Message-ID: <20161021204741.CB6711080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 20:47:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 20:47:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2164: Support Theme:
 Pagination on profiles pushes content left
In-Reply-To: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
References: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
Message-ID: <066.763769ece9f7a9bfafdbfa972a3dbb4f@wordpress.org>

#2164: Support Theme: Pagination on profiles pushes content left
----------------------------+--------------------------
 Reporter:  Clorith         |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4284"]:
 {{{
 #!CommitTicketReference repository="" revision="4284"
 Support Theme: Fix display of user topic and reply listings due to float
 of pagination controls.

 Props Clorith.
 Fixes #2164.
 }}}

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

From noreply at wordpress.org  Fri Oct 21 21:02:56 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 21:02:56 -0000
Subject: [wp-meta] [Making WordPress.org] #2164: Support Theme:
 Pagination on profiles pushes content left
In-Reply-To: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
References: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
Message-ID: <066.38a4012d94637d10a1dfcd9258bced2f@wordpress.org>

#2164: Support Theme: Pagination on profiles pushes content left
----------------------------+--------------------------
 Reporter:  Clorith         |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------

Comment (by coffee2code):

 Replying to [comment:1 netweb]:
 > The replies header is there, topics header is not, topics were removed
 in [3898]

 @netweb: I'm not clear what you're saying here. That the `.bbp-pagination-
 count` content is blank/missing in certain views whereas the `.bbp-
 pagination-links` is always present? If so, that sounds like it should be
 opened as a separate issue.

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

From noreply at wordpress.org  Fri Oct 21 21:12:33 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 21:12:33 -0000
Subject: [wp-meta] [Making WordPress.org] #1112: Site Cloner: Scale to
 support hundreds of sites
In-Reply-To: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
References: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
Message-ID: <066.8674a18b69a7d0193a05f007058d04f1@wordpress.org>

#1112: Site Cloner: Scale to support hundreds of sites
-------------------------------------+-----------------------
 Reporter:  iandunn                  |       Owner:  iandunn
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+-----------------------

Comment (by iandunn):

 In [changeset:"4285"]:
 {{{
 #!CommitTicketReference repository="" revision="4285"
 WordCamp Site Cloner: Lower sites query limit to `250` to avoid transient
 bug

 See #1112
 }}}

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

From noreply at wordpress.org  Fri Oct 21 21:12:32 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 21:12:32 +0000 (UTC)
Subject: [wp-meta] [4285]
 sites/trunk/wordcamp.org/public_html/wp-content/plugins/
 wordcamp-site-cloner/wordcamp-site-cloner.php: WordCamp Site Cloner: Lower
 sites query limit to `250` to avoid transient bug
Message-ID: <20161021211232.A90B51080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 21:19:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 21:19:24 -0000
Subject: [wp-meta] [Making WordPress.org] #1112: Site Cloner: Scale to
 support hundreds of sites
In-Reply-To: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
References: <051.9e9578072cd29b0a6c70474d0645382c@wordpress.org>
Message-ID: <066.e9feafb8d5db70612ee7f2cd5c8bbced@wordpress.org>

#1112: Site Cloner: Scale to support hundreds of sites
-------------------------------------+-----------------------
 Reporter:  iandunn                  |       Owner:  iandunn
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+-----------------------

Comment (by iandunn):

 Sorry it took so long to merge this. I ran into some problems while
 testing some of my changes, so I removed the batching in order to get the
 rest of the patch deployed. That limits the number of sites at `500`,
 though, so it'd be good to come back and add the batching back in, I just
 didn't have time to do that myself right now.

 After deploying it, I noticed a bug on production, and ended up having to
 lower the limit to `250`. The comment in r4285 has more details. I wasn't
 able to reproduce it in my dev environment. That'll need to be fixed
 before the batching can be restored.

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

From noreply at wordpress.org  Fri Oct 21 21:41:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 21:41:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2173: Error when WP_Query parses
 orderby array in function parse_order
Message-ID: <051.bea0edf9ea510b8a28d8f9e3ec021f85@wordpress.org>

#2173: Error when WP_Query parses orderby array in function parse_order
---------------------+------------------------------------
 Reporter:  oloynet  |      Owner:
     Type:  defect   |     Status:  new
 Priority:  high     |  Milestone:
Component:  API      |   Keywords:  dev-feedback has-patch
---------------------+------------------------------------
 Example of request where I want to order by two custom fields in meta
 query
 start_date_order and is_sticky

 {{{
 $args = array(
     'no_found_rows'  => true ,
     'posts_per_page' => 4,
     'post_type'      => 'event',
     'post_status'    => 'publish',

     'meta_query' => array(
         'relation' => 'AND',
         array(
             'key'  => 'start_date_order',
             'type' => 'UNSIGNED',
         ),
         array(
             'key'  => 'is_sticky',
             'type' => 'UNSIGNED',
         ),
     ),
     'orderby' => array(
         'start_date_order' => 'DESC',
         'is_sticky'        => 'ASC',
     ),
 );
 }}}

 The '$primary_meta_query' var in method parse_order( $order ) is set
 forever with the first item of '$meta_clauses' array

 see line 2336 /wp-includes/query.php

 {{{#!php
 <?php
 $primary_meta_query = reset( $meta_clauses );
 }}}


 I fix the problem with the following PHP code

 {{{#!php
 <?php
 //$primary_meta_query = reset( $meta_clauses );

 $primary_meta_query = array();
 foreach( $meta_clauses as $meta_clause ) {

     if( $meta_clause['key'] == $orderby ) {
         $primary_meta_query = $meta_clause;
         break;
     }
 }

 }}}

 Now the good sql query is look like :


 {{{
 SELECT wp_posts.ID
 FROM wp_posts
 INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id )
 INNER JOIN wp_postmeta AS mt1 ON ( wp_posts.ID = mt1.post_id )
 WHERE 1=1
 AND (
   wp_postmeta.meta_key = 'start_date_order'
   AND mt1.meta_key = 'is_sticky'
 )
 AND wp_posts.post_type = 'event'
 AND ((wp_posts.post_status = 'publish'))
 GROUP BY wp_posts.ID
 ORDER BY CAST(wp_postmeta.meta_value AS UNSIGNED) DESC,
 CAST(mt1.meta_value AS UNSIGNED) ASC
 LIMIT 0, 3
 }}}

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

From noreply at wordpress.org  Fri Oct 21 21:43:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 21:43:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2174: "Unresolved Topics" view on
 plugin/theme level
Message-ID: <053.d1281ac629207481f7386e2251e9906a@wordpress.org>

#2174: "Unresolved Topics" view on plugin/theme level
----------------------------+-----------------
 Reporter:  Hinjiriyo       |      Owner:
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 The forum provides the list of all unresolved topics aka "Unresolved
 Topics" view, to find under
 https://wordpress.org/support/view/support-forum-no/

 For authors of plugins and themes it would be helpful to have such a
 feature not for all topics but only in the forum of a single plugin or
 theme.

 It would be also helpful to have the other forum views at plugin/theme
 level:
 * Most popular topics
 * Topics with no replies
 * Non-support topics
 * Resolved topics

 For me as a plugin author the "Unresolved Topics" view would be the most
 helpful one.

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

From noreply at wordpress.org  Fri Oct 21 21:50:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 21:50:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2173: Error when WP_Query
 parses orderby array in function parse_order
In-Reply-To: <051.bea0edf9ea510b8a28d8f9e3ec021f85@wordpress.org>
References: <051.bea0edf9ea510b8a28d8f9e3ec021f85@wordpress.org>
Message-ID: <066.88bf66a29664b0330536922e0f31adf1@wordpress.org>

#2173: Error when WP_Query parses orderby array in function parse_order
---------------------+----------------------
 Reporter:  oloynet  |       Owner:
     Type:  defect   |      Status:  closed
 Priority:  normal   |   Milestone:
Component:  General  |  Resolution:  invalid
 Keywords:           |
---------------------+----------------------
Changes (by ocean90):

 * keywords:  dev-feedback has-patch =>
 * priority:  high => normal
 * status:  new => closed
 * component:  API => General
 * resolution:   => invalid


Comment:

 Hello @oloynet,

 this Trac is for WordPress.org. For the software WordPress we have
 https://core.trac.wordpress.org/.

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

From noreply at wordpress.org  Fri Oct 21 22:13:35 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 22:13:35 +0000 (UTC)
Subject: [wp-meta] [4286]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-support/Gruntfile.js: Support Theme: Use a build task as the default
 grunt task.
Message-ID: <20161021221335.C510F1080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 22:17:11 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 21 Oct 2016 22:17:11 +0000 (UTC)
Subject: [wp-meta] [4287]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-support:
 Support Theme: Let the RTL stylesheet replace the LTR stylesheet.
Message-ID: <20161021221711.3BC861080360@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 21 23:22:55 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 21 Oct 2016 23:22:55 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Support Theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.ffc431fdce1e22301acd40bbb6aceb54@wordpress.org>

#2147: Support Theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------

Comment (by coffee2code):

 @mapk: Nice! I like that. Unfortunately the box-shadow doesn't appear on
 the user replies view (e.g.
 https://wordpress.org/support/users/sterndata/replies/). See
 [attachment:meta-2147.box-shadow-missing.png]. I didn't initially resolve
 it so I'm leaving [attachment:meta-2147.diff] for anyone to try out.

 As for badges, there are currently five:

 * Moderators
 * Plugin Author
 * Plugin Contributor
 * Theme Author
 * Theme Contributor (not currently utilized)

 The plugin and theme badges were green (for no real reason) and have
 existed the longest. The moderator badge is more recent and was thus given
 a different badge color -- that of the support team's
 profiles.wordpress.org badge.

 The plugin and theme badges could be likewise be re-colored to match their
 respective team badges:

 * Plugins: `#f06723`
 * Themes: `#4e3288`

 Attached is [attachment:meta-2147.diff], which applies [comment:7 comment
 7] styling and minor tweaks and includes the modification of those badge
 colors. See [attachment:meta-2147.plugin-badge.png] and
 [attachment:meta-2147.theme-badge.png] for examples of those re-colored
 badges.

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

From noreply at wordpress.org  Sat Oct 22 02:19:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 02:19:43 -0000
Subject: [wp-meta] [Making WordPress.org] #2164: Support Theme:
 Pagination on profiles pushes content left
In-Reply-To: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
References: <051.bf3e3779802b55e0ff7a628d85120e51@wordpress.org>
Message-ID: <066.0ea96f7bdd341133d776d0197b772a4d@wordpress.org>

#2164: Support Theme: Pagination on profiles pushes content left
----------------------------+--------------------------
 Reporter:  Clorith         |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------

Comment (by netweb):

 Replying to [comment:5 coffee2code]:
 > Replying to [comment:1 netweb]:
 > > The replies header is there, topics header is not, topics were removed
 in [3898]
 >
 > @netweb: I'm not clear what you're saying here. That the `.bbp-
 pagination-count` content is blank/missing in certain views whereas the
 `.bbp-pagination-links` is always present? If so, that sounds like it
 should be opened as a separate issue.

 This doesn't make sense to me either this morning ;)

 As part of the initial forums switch to bbPress 2.x, the forum topics
 pagination counts were removed for performance optimization, see
 [https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/plugins/support-forums/inc/class-hooks.php?rev=3898#L9
 /support-forums/inc/class-hooks.php?rev=3898#L9 ], I was expecting to see
 this on the users profile though, I'll create a new ticket for this.

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

From noreply at wordpress.org  Sat Oct 22 09:45:56 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 09:45:56 -0000
Subject: [wp-meta] [Making WordPress.org] #2172: Support Theme: 3 up
 forums list needs consistent CSS units
In-Reply-To: <051.62dada9c8a79981d13695b691f70b87a@wordpress.org>
References: <051.62dada9c8a79981d13695b691f70b87a@wordpress.org>
Message-ID: <066.c2fb548ff415072b37ff53438be11209@wordpress.org>

#2172: Support Theme: 3 up forums list needs consistent CSS units
-----------------------------------------------------+------------------
 Reporter:  bcworkz                                  |       Owner:
     Type:  defect                                   |      Status:  new
 Priority:  normal                                   |   Milestone:
Component:  Support Forums                           |  Resolution:
 Keywords:  needs-patch ui-feedback has-screenshots  |
-----------------------------------------------------+------------------

Comment (by Clorith):

 We could probably solve this in a much cleaner fashion by using flex (and
 maintain BC for older browsers if we want with flexibility), we could then
 do away with the fixed height altogether and not have to worry about font
 sizes and the likes.

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

From noreply at wordpress.org  Sat Oct 22 09:53:41 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 09:53:41 -0000
Subject: [wp-meta] [Making WordPress.org] #1873: Restore views menu in
 bbPress 2.x forums header
In-Reply-To: <058.d406212806a2a34b80cfa01b1b69c306@wordpress.org>
References: <058.d406212806a2a34b80cfa01b1b69c306@wordpress.org>
Message-ID: <073.e8aa16353e838550f63492071b44d4d3@wordpress.org>

#1873: Restore views menu in bbPress 2.x forums header
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by SergeyBiryukov):

 [attachment:meta-1873.png] is a screenshot of the links in the bbPress 1.x
 theme, for refence.

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

From noreply at wordpress.org  Sat Oct 22 09:53:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 09:53:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.5eef0a9aa9d5598de62e7a07f09ac1d1@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by SergeyBiryukov):

 @mapk: What would be the preferred place for the Profile / Admin / Log Out
 links here?

 [attachment:meta-2167.png] is a screenshot of the links in the old theme,
 for reference.

 On a related note, it would also be nice to bring the "All Topics | No
 Replies | Not Resolved | No Tags" links somewhere closer to the header to
 avoid too much scrolling, see #1873.

 [attachment:meta-2167.2.png] is a screenshot of those links in the bbPress
 1.x theme.

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

From noreply at wordpress.org  Sat Oct 22 09:55:41 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 09:55:41 -0000
Subject: [wp-meta] [Making WordPress.org] #2175: Support Theme: More
 information on profiles for moderators
Message-ID: <051.3b3342d6dd7d87a9cc8b8d8a826864ca@wordpress.org>

#2175: Support Theme: More information on profiles for moderators
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 This was implemented in #1967 on the old theme.

 The user profile now only shows forum role and the amount of topics and
 posts a user has, on the old theme we had also implemented the following:
 - Email
 - Slack user
 - Website
 - Member since

 All of these are handy to moderators, member since, website and email are
 great for confirming/checking for spam accounts in cases of doubt, the
 Slack user is great if we want to DM or ping someone (this can be seen
 from profiles. but then we'd have to manually change the URL at this
 point).

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

From noreply at wordpress.org  Sat Oct 22 10:01:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 10:01:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2176: Support Theme: Custom
	titles are wiped
Message-ID: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>

#2176: Support Theme: Custom titles are wiped
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 On the new theme, all custom titles are missing (replaced by a new meta
 perhaps?), we can set a new title, and it is retained both in the profile
 edit screen and is displayed in the actual forums, but the title that we
 already had is not present.

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

From noreply at wordpress.org  Sat Oct 22 19:24:31 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 22 Oct 2016 19:24:31 +0000 (UTC)
Subject: [wp-meta] [4288]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-support/bbpress/user-profile.php: Support Theme: Port profile changes
 recently made in wporg-forums theme.
Message-ID: <20161022192431.A14FB1080224@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 22 19:24:32 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 19:24:32 -0000
Subject: [wp-meta] [Making WordPress.org] #2175: Support Theme: More
 information on profiles for moderators
In-Reply-To: <051.3b3342d6dd7d87a9cc8b8d8a826864ca@wordpress.org>
References: <051.3b3342d6dd7d87a9cc8b8d8a826864ca@wordpress.org>
Message-ID: <066.392df8fd9507129453d026747f620f51@wordpress.org>

#2175: Support Theme: More information on profiles for moderators
----------------------------+--------------------------
 Reporter:  Clorith         |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4288"]:
 {{{
 #!CommitTicketReference repository="" revision="4288"
 Support Theme: Port profile changes recently made in wporg-forums theme.

 Restores display of email address, title, website, member since,
 profiles.wordpress.org link, Slack username.

 Fixes #2175.
 }}}

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

From noreply at wordpress.org  Sat Oct 22 23:16:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 22 Oct 2016 23:16:12 -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.e60f20ac78bbb49afff64d81003c04b5@wordpress.org>

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

Comment (by netweb):

 Linking here for reference the new [https://help.github.com/articles
 /github-community-guidelines/ GitHub Community Guidelines] that were
 introduced last week.
 GitHub are seeking feedback [https://github.com/blog/2267-introducing-
 github-community-guidelines here] on these new guidlines.

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

From noreply at wordpress.org  Sun Oct 23 01:04:01 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 01:04:01 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.1ba6f8f68bf235428ee3b9070b35afb2@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 I'll add that the bb's (bbpress.org and buddypress.org) relocate the admin
 bar menu:

 * [[Image(https://cldup.com/9zpoYq4x0F.png)]]

 And add the bbPress profiles links to the user drop down:

 * [[Image(https://cldup.com/E_6-67QndX.png)]]

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

From noreply at wordpress.org  Sun Oct 23 01:30:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 01:30:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2176: Support Theme: Custom
 titles are wiped
In-Reply-To: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>
References: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>
Message-ID: <066.883b68fdb558c225e098615180ed10e4@wordpress.org>

#2176: Support Theme: Custom titles are wiped
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 I see my custom title `bzzz... bbPress`, and I've not edited it, when I go
 to edit it is also displayed there correctly.

 Looking at another user that I doubt has edited theirs recently I see
 `WordPress.org Tech Dude` for Otto

 Looks like [4288] fixed this, can you confirm @Clorith please?

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

From noreply at wordpress.org  Sun Oct 23 02:39:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 02:39:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2162: Support Theme: Post
 notices push content down
In-Reply-To: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
References: <051.c834c9ceb5166ba076242b0580133f9f@wordpress.org>
Message-ID: <066.59c6d5f6bc3b665ac3ef12cb184f26df@wordpress.org>

#2162: Support Theme: Post notices push content down
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 The purpose of the background colors based on post status which is "by
 design" in bbPress core is to make highlighting posts with a quick visual
 queue, i.e. the reddish #fdd for `spam`, and yellowish #fef7f1 for
 `pending`, and the w.org specific `archived` status also using #fdd. ''

 The addition of the template notices inside each topic or reply added in
 #1561 could allow the background to be removed for replies, though we'd
 need to come up with a solution for topics

 A users replies view as how it would be seen by a moderator (padding issue
 not withstanding):
 *  https://wordpress.org/support/users/netweb/replies/?view=all
 * [[Image(https://cldup.com/3GFzCbsygT.png)]]

 And the same users topics view as how it would be seen by a moderator:
 *  https://wordpress.org/support/users/netweb/topics/?view=all
 * [[Image(https://cldup.com/1d5uWNPAXO.png)]]

 A view of some `pending` WordPress comments:
 * [[Image(https://cldup.com/ZooOnxB7hC.png)]]

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

From noreply at wordpress.org  Sun Oct 23 12:39:23 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 12:39:23 -0000
Subject: [wp-meta] [Making WordPress.org] #2177: the search box throws code
	on screen
Message-ID: <058.0c67b15552928a3bcf80d8c4bc526e3f@wordpress.org>

#2177: the search box throws code on screen
----------------------------+-----------------
 Reporter:  stratmccloskey  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  General         |   Keywords:
----------------------------+-----------------
 I've tried to use the search wordpress.org box in the upper right corner
 and it keeps throwing the following up on the screen:
 (function() {
 var _UDS_CONST_LOCALE = 'en';
 var _UDS_CONST_SHORT_DATE_PATTERN = 'MDY';
 var _UDS_MSG_SEARCHER_IMAGE = ('Image');
 var _UDS_MSG_SEARCHER_WEB = ('Web');
 var _UDS_MSG_SEARCHER_BLOG = ('Blog');
 var _UDS_MSG_SEARCHER_VIDEO = ('Video');
 var _UDS_MSG_SEARCHER_LOCAL = ('Local');
 var _UDS_MSG_SEARCHCONTROL_SAVE = ('save');
 var _UDS_MSG_SEARCHCONTROL_KEEP = ('keep');
 var _UDS_MSG_SEARCHCONTROL_INCLUDE = ('include');
 var _UDS_MSG_SEARCHCONTROL_COPY = ('copy');
 var _UDS_MSG_SEARCHCONTROL_CLOSE = ('close');
 var _UDS_MSG_SEARCHCONTROL_SPONSORED_LINKS = ('Sponsored Links');
 var _UDS_MSG_SEARCHCONTROL_SEE_MORE = ('see more...');
 var _UDS_MSG_SEARCHCONTROL_WATERMARK = ('clipped from Google');
 var _UDS_MSG_SEARCHER_CONFIG_SET_LOCATION = ('Search location');
 var _UDS_MSG_SEARCHER_CONFIG_DISABLE_ADDRESS_LOOKUP = ('Disable address
 lookup');

 I deleted the other 600 lines out of courtesy. This problem has been going
 on for a while. Very annoying when your trying to research something.

 Strat McCloskey

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

From noreply at wordpress.org  Sun Oct 23 12:49:18 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 12:49:18 -0000
Subject: [wp-meta] [Making WordPress.org] #2177: the search box throws
 code on screen
In-Reply-To: <058.0c67b15552928a3bcf80d8c4bc526e3f@wordpress.org>
References: <058.0c67b15552928a3bcf80d8c4bc526e3f@wordpress.org>
Message-ID: <073.6fdf6534bf328cf4c5595f889e4218f8@wordpress.org>

#2177: the search box throws code on screen
----------------------------+------------------
 Reporter:  stratmccloskey  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  General         |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 Hi,

 The search is JavaScript driven (it'll search after the page loads) as it
 uses Google for the search results.

 The search functions as expected for me when testing just now, do you by
 any chance have any browser extensions that are interfering, or are on a
 restricted network of some kind that might be filtering traffic?

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

From noreply at wordpress.org  Sun Oct 23 18:12:42 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun, 23 Oct 2016 18:12:42 +0000 (UTC)
Subject: [wp-meta] [4289]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums: Use the user
 object for view queries.
Message-ID: <20161023181242.56F421080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct 23 18:12:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 18:12:43 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.5e2fd670b43a1b8381a6890b5708f1aa@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by jmdodd):

 In [changeset:"4289"]:
 {{{
 #!CommitTicketReference repository="" revision="4289"
 Support Forums: Use the user object for view queries.

 Allows empty forums for non-contributing users, and 404s for non-existent
 users.

 Abstracts some logic to make adding a plugin-contributors view easier.

 See #2071.
 }}}

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

From noreply at wordpress.org  Sun Oct 23 18:39:39 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sun, 23 Oct 2016 18:39:39 +0000 (UTC)
Subject: [wp-meta] [4290]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums: Add plugin
 contributor view.
Message-ID: <20161023183939.31D5E1080269@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sun Oct 23 18:39:40 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 18:39:40 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.eef8bae7547085f36f851aa877360c7f@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by jmdodd):

 In [changeset:"4290"]:
 {{{
 #!CommitTicketReference repository="" revision="4290"
 Support Forums: Add plugin contributor view.

 Adds rewrite rules, feed, and custom view handlers.

 See #2071.
 }}}

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

From noreply at wordpress.org  Sun Oct 23 19:25:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 23 Oct 2016 19:25:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2177: the search box throws
 code on screen
In-Reply-To: <058.0c67b15552928a3bcf80d8c4bc526e3f@wordpress.org>
References: <058.0c67b15552928a3bcf80d8c4bc526e3f@wordpress.org>
Message-ID: <073.cec7bbbf1a49d13450cee627ceaa6f7c@wordpress.org>

#2177: the search box throws code on screen
----------------------------+------------------
 Reporter:  stratmccloskey  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  General         |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Presskopp):

 Seems more User/Browser- than Wordpress related, see:

 https://groups.google.com/forum/#!topic/mozilla.support.firefox/k9BfdQeFjLI

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

From noreply at wordpress.org  Mon Oct 24 12:57:33 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 12:57:33 -0000
Subject: [wp-meta] [Making WordPress.org] #2178: Stars to not show in reviews
Message-ID: <053.fb6f25a30e21e448a0a1a9491fd45261@wordpress.org>

#2178: Stars to not show in reviews
----------------------------+-----------------
 Reporter:  sterndata       |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 The new theme does not show stars in reviews

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

From noreply at wordpress.org  Mon Oct 24 14:29:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 14:29:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2159: WordCamp Organizers:
 Add a custom taxonomy for teams
In-Reply-To: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
References: <051.f912ee03564157103d5a560640e6a177@wordpress.org>
Message-ID: <066.d1fe13e5da5c90806e096b3970af8cc4@wordpress.org>

#2159: WordCamp Organizers: Add a custom taxonomy for teams
-------------------------------------+-------------------------
 Reporter:  Kau-Boy                  |       Owner:
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:  maybelater
 Keywords:  has-patch                |
-------------------------------------+-------------------------
Changes (by iandunn):

 * keywords:  has-patch commit => has-patch
 * status:  new => closed
 * resolution:   => maybelater


Comment:

 Hey Bernhard, thanks for the patch. It does look good, but the Community
 team will need to discuss the idea before the Meta team can implement
 anything. Check out [https://make.wordpress.org/community/feature-
 requests-for-community-sites/ the process for feature requests] for more
 details.

 I'm closing the ticket for now, but it can be re-opened and committed if
 the Community team approves it.

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

From noreply at wordpress.org  Mon Oct 24 14:50:07 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 14:50:07 -0000
Subject: [wp-meta] [Making WordPress.org] #2179: Add `rest-api` as focus
 keyword for Core Trac
Message-ID: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>

#2179: Add `rest-api` as focus keyword for Core Trac
-------------------------+-------------------------
 Reporter:  flixos90     |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Trac         |   Keywords:  needs-patch
-------------------------+-------------------------
 Since the REST API content endpoints have been merged into Core, it makes
 sense to add a focus keyword `rest-api` to Core Trac. There are tickets
 that belong to another specific component, but mainly focus on REST API
 functionality.

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

From noreply at wordpress.org  Mon Oct 24 15:07:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 15:07:42 -0000
Subject: [wp-meta] [Making WordPress.org] #2179: Add `rest-api` as focus
 keyword for Core Trac
In-Reply-To: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>
References: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>
Message-ID: <067.caa2d135465adb79b435bcd39fb1e4c6@wordpress.org>

#2179: Add `rest-api` as focus keyword for Core Trac
-------------------------+------------------
 Reporter:  flixos90     |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:
 Keywords:  has-patch    |
-------------------------+------------------
Changes (by flixos90):

 * keywords:  needs-patch => has-patch


Comment:

 [attachment:2179.diff] adds a `restapi` focus keyword (I left out the
 hyphen in order to better align with the other focus keywords).

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

From noreply at wordpress.org  Mon Oct 24 16:09:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 16:09:02 -0000
Subject: [wp-meta] [Making WordPress.org] #2180: Tags missing from plugin
Message-ID: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>

#2180: Tags missing from plugin
------------------------------+-----------------
 Reporter:  johnbillion       |      Owner:
     Type:  defect            |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+-----------------
 The readme.txt file in my [https://wordpress.org/plugins/query-monitor/
 Query Monitor plugin] contains a bunch of tags, but the plugin isn't
 tagged with these in the plugin repo. The tags aren't listed on the plugin
 page, and the plugin doesn't show up when browsing the archive for any of
 its tags.

 The readme file is valid according to the readme validator.

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

From noreply at wordpress.org  Mon Oct 24 18:24:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 18:24:02 -0000
Subject: [wp-meta] [Making WordPress.org] #2180: Tags missing from plugin
In-Reply-To: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>
References: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>
Message-ID: <070.cd3f8520e7bf59ecd202c2189aa3817e@wordpress.org>

#2180: Tags missing from plugin
------------------------------+-------------------------
 Reporter:  johnbillion       |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  worksforme
 Keywords:                    |
------------------------------+-------------------------
Changes (by Otto42):

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


Comment:

 Tags are showing up fine for your plugin. Bottom of the page.

 Also, please delete some of the old tagged versions from your plugin:

 https://plugins.svn.wordpress.org/query-monitor/tags/

 That many tagged versions makes it take a lot longer to process your
 plugin, since a ZIP has to be built for each of those directories on every
 update. You don't need to offer all of those old versions, do you? Just
 the latest in each major set is probably good enough.

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

From noreply at wordpress.org  Mon Oct 24 18:36:41 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 18:36:41 -0000
Subject: [wp-meta] [Making WordPress.org] #2178: Stars to not show in
	reviews
In-Reply-To: <053.fb6f25a30e21e448a0a1a9491fd45261@wordpress.org>
References: <053.fb6f25a30e21e448a0a1a9491fd45261@wordpress.org>
Message-ID: <068.7b506c03b4f65268dbe0b6e2df368268@wordpress.org>

#2178: Stars to not show in reviews
----------------------------+------------------------
 Reporter:  sterndata       |       Owner:
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  duplicate
 Keywords:                  |
----------------------------+------------------------
Changes (by Clorith):

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


Comment:

 Duplicate of #2169.

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

From noreply at wordpress.org  Mon Oct 24 19:05:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 19:05:03 -0000
Subject: [wp-meta] [Making WordPress.org] #2176: Support Theme: Custom
 titles are wiped
In-Reply-To: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>
References: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>
Message-ID: <066.618ea2dd5278a8a0f31ec4ab90c1fd1b@wordpress.org>

#2176: Support Theme: Custom titles are wiped
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 I set my own title as a test, so I'm not a good test person (unless
 someone else removed my title after the bbPress move, since they didn't
 display front end I never took the time to look but it used to be
 `Volunteer Moderator`).

 It obviously works after having saved the new one, on the new theme so I'm
 not quite sure how to test this one I*m afraid, if nobody else is
 observing this then i'm happy to close as worksforme

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

From noreply at wordpress.org  Mon Oct 24 19:11:47 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 24 Oct 2016 19:11:47 -0000
Subject: [wp-meta] [Making WordPress.org] #2181: Support Theme: Breadcrumb
 links for plugins
Message-ID: <051.0e338a5ddc6f0704f981571bffd8c543@wordpress.org>

#2181: Support Theme: Breadcrumb links for plugins
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 When viewing a review or a support topic for a plugin or theme, clicking
 the breadcrumbs for `Reviews` or `Support` will take you to the big
 gathering forums, and not the specific plugin/themes review or support
 threads as expected.

 This is not a new thing, and is the way the current theme handles it as
 well, but expectations dictate that clicking reviews in a breadcrumb when
 viewing an individual review takes you to the list of reviews I was
 previously at.

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

From noreply at wordpress.org  Tue Oct 25 04:42:58 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 04:42:58 -0000
Subject: [wp-meta] [Making WordPress.org] #2176: Support Theme: Custom
 titles are wiped
In-Reply-To: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>
References: <051.a3a180d8f05d6519175dceec0211e460@wordpress.org>
Message-ID: <066.ef6e8cd4df1526a53c364d9214456b35@wordpress.org>

#2176: Support Theme: Custom titles are wiped
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  close           |
----------------------------+------------------
Changes (by netweb):

 * keywords:   => close


Comment:

 Cool, lets leave it open for a couple of weeks "just in case" and close
 when we have the next #meta bug scrub

 FYI: ''There is no #meta bug scrub planned, but we should in the not too
 distant future''

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

From noreply at wordpress.org  Tue Oct 25 14:02:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 14:02:03 -0000
Subject: [wp-meta] [Making WordPress.org] #2182: Incorrect semicolon in a
 PHP code snippet
Message-ID: <054.7baa0f82772877880b304441bfeb3362@wordpress.org>

#2182: Incorrect semicolon in a PHP code snippet
---------------------------+-------------------------------
 Reporter:  fahidjavid     |      Owner:
     Type:  defect         |     Status:  new
 Priority:  normal         |  Milestone:
Component:  Developer Hub  |   Keywords:  reporter-feedback
---------------------------+-------------------------------
 Hi,

 I have found an unnecessary semicolon in a PHP code snippet while I was
 using Customizer API to add customizer control in my project.

 If you find the following code on this page
 https://developer.wordpress.org/themes/advanced-topics/customizer-api/

 {{{#!php
 <?php
 $wp_customize->add_control(
   new WP_Customize_Color_Control(
     $wp_customize, // WP_Customize_Manager
     'accent_color', // Setting id
     array( // Args, including any custom ones.
       'label' => __( 'Accent Color' ),
       'section' =>; 'colors',
     )
   )
 );
 }}}

 You can see the unnecessary semicolon next to the ''''section' =>'''
 parameter.

 Here is the related screenshot:

 [[Image(http://content.screencast.com/users/fahidjaivid/folders/Jing/media/054c82f0-856e-4955-ad17-65ca78d8a11c/00000914.png)]]

 Thank you,

 Fahid

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

From noreply at wordpress.org  Tue Oct 25 17:07:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 17:07:03 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.e02ef99940c7ac843c384395b8330044@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by ocean90):

 Replying to [comment:6 mapk]:
 > And if user is logged in... the bar is already there it looks like.

 The toolbar is currently only shown if the current user is a "real" member
 of at least one site on w.org. But we should be able to force the toolbar
 to be always there.

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

From noreply at wordpress.org  Tue Oct 25 17:07:54 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 17:07:54 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Support Theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.adbe9b7c052256b92d9d200c85c8b50a@wordpress.org>

#2147: Support Theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------

Comment (by mapk):

 Replying to [comment:8 coffee2code]:
 > @mapk: Nice! I like that. Unfortunately the box-shadow doesn't appear on
 the user replies view (e.g.
 https://wordpress.org/support/users/sterndata/replies/). See
 [attachment:meta-2147.box-shadow-missing.png]. I didn't initially resolve
 it so I'm leaving [attachment:meta-2147.diff] for anyone to try out.

 So looks like we need to restyle the layout of the user replies page, yes?
 Is that the solution that's needed?

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

From noreply at wordpress.org  Tue Oct 25 17:03:35 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 17:03:35 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.81205d4dff51fa6781398a3b3cff0a3d@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by mapk):

 @SergeyBiryukov @netweb

 I think it's mentioned, but adding the wp admin bar to the top seems the
 way to go (the black bar at the very top).

 If user is not logged in, they'll see something like this:
 [[Image(https://cldup.com/Fg1RDwOT81.png)]]

 And if user is logged in... the bar is already there it looks like.
 [[Image(https://cldup.com/nxZFNQZgtv.png)]]

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

From noreply at wordpress.org  Tue Oct 25 17:11:45 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 17:11:45 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.20e2234af1c2f678d09e00642626f0c7@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by mapk):

 Replying to [comment:7 ocean90]:
 > Replying to [comment:6 mapk]:
 > > And if user is logged in... the bar is already there it looks like.
 >
 > The toolbar is currently only shown if the current user is a "real"
 member of at least one site on w.org. But we should be able to force the
 toolbar to be always there.

 I'm not sure I understand what a "real" member means, but if we can force
 it to show, I think that's the way to go. The login ability is essential
 here.

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

From noreply at wordpress.org  Tue Oct 25 17:17:07 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 17:17:07 -0000
Subject: [wp-meta] [Making WordPress.org] #2167: Support Theme: No easy
 access to your profile
In-Reply-To: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
References: <051.bad748f17bcf8d2534b08a6563314606@wordpress.org>
Message-ID: <066.4b74f3d807aa23d5eb9545565b9a7655@wordpress.org>

#2167: Support Theme: No easy access to your profile
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by ocean90):

 Replying to [comment:8 mapk]:
 > I'm not sure I understand what a "real" member means, but if we can
 force it to show, I think that's the way to go. The login ability is
 essential here.

 Sorry, by "real" I mean a user who has a role like editor, author,
 moderator etc. and not a bbPress role like [https://codex.bbpress.org
 /getting-started/before-installing/bbpress-user-roles-and-capabilities
 /#summary-of-roles blocked, spectator or participant].

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

From noreply at wordpress.org  Tue Oct 25 20:58:35 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 20:58:35 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Support Theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.0035b53593df411cfe71f02efb886a7e@wordpress.org>

#2147: Support Theme needs styling for badges
-----------------------------------------+------------------
 Reporter:  SergeyBiryukov               |       Owner:
     Type:  defect                       |      Status:  new
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+------------------

Comment (by coffee2code):

 Replying to [comment:9 mapk]:
 > So looks like we need to restyle the layout of the user replies page,
 yes? Is that the solution that's needed?

 I don't think we need to go that far unless there are reasons unrelated to
 badge-styling for doing so. I've played around with it and have badge-
 styling looking decent on that view. I'll test the changes a bit more and
 then just commit those changes atop [attachment:meta-2147.diff] and we can
 just iterate from there.

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

From noreply at wordpress.org  Tue Oct 25 21:11:46 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Oct 2016 21:11:46 +0000 (UTC)
Subject: [wp-meta] [4291]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 wporg-bbp-user-badges/inc/class-plugin.php: Support Forums,
 User Badges: Add 'author-has-badge' class to generically indicate that
 author was assigned any badge.
Message-ID: <20161025211146.409291080366@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 25 21:21:11 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 21:21:11 -0000
Subject: [wp-meta] [Making WordPress.org] #1828: Improve Screenshots
	section
In-Reply-To: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
References: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
Message-ID: <071.9d1b2e7bd066a1dd271460f72255b69b@wordpress.org>

#1828: Improve Screenshots section
------------------------------+---------------------------------------
 Reporter:  samuelsidler      |       Owner:  mapk
     Type:  task              |      Status:  reopened
 Priority:  high              |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by mapk):

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


Comment:

 I pre-emptively closed this. My commit should take care of a lot, but I'm
 re-opening because there are a few things not yet fixed.

 1. The height change animation.
 2. Thumbnails being the same square size.

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

From noreply at wordpress.org  Tue Oct 25 21:16:56 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Oct 2016 21:16:56 +0000 (UTC)
Subject: [wp-meta] [4292]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-plugins:
 Fixing the Screenshot Viewer styling for the new Plugin Directory.
Message-ID: <20161025211656.B080C1080366@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 25 21:16:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 21:16:57 -0000
Subject: [wp-meta] [Making WordPress.org] #1828: Improve Screenshots
	section
In-Reply-To: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
References: <056.a322e8ee1e890fb270e533b183c5cb04@wordpress.org>
Message-ID: <071.014ca9de538eafc1460f3d0b2759dd4c@wordpress.org>

#1828: Improve Screenshots section
------------------------------+---------------------------------------
 Reporter:  samuelsidler      |       Owner:  mapk
     Type:  task              |      Status:  closed
 Priority:  high              |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by mapk):

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


Comment:

 In [changeset:"4292"]:
 {{{
 #!CommitTicketReference repository="" revision="4292"
 Fixing the Screenshot Viewer styling for the new Plugin Directory.

 See https://meta.trac.wordpress.org/ticket/1828#comment:52

 Fixes #1828
 }}}

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

From noreply at wordpress.org  Tue Oct 25 21:48:02 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Oct 2016 21:48:02 +0000 (UTC)
Subject: [wp-meta] [4293]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-support:
 Support Theme: Add styling for user badges.
Message-ID: <20161025214802.26D3B1080366@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 25 21:48:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 21:48:02 -0000
Subject: [wp-meta] [Making WordPress.org] #2147: Support Theme needs
 styling for badges
In-Reply-To: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
References: <058.7adf1685f6edb67301b1333409bf0679@wordpress.org>
Message-ID: <073.db57dd2371753c30ad0c4922f4d5e176@wordpress.org>

#2147: Support Theme needs styling for badges
-----------------------------------------+--------------------------
 Reporter:  SergeyBiryukov               |       Owner:  coffee2code
     Type:  defect                       |      Status:  closed
 Priority:  normal                       |   Milestone:
Component:  Support Forums               |  Resolution:  fixed
 Keywords:  ui-feedback has-screenshots  |
-----------------------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4293"]:
 {{{
 #!CommitTicketReference repository="" revision="4293"
 Support Theme: Add styling for user badges.

 Also changes colors of plugin- and theme-related badges to match their
 respective profiles.wordpress.org team colors.

 Props mapk, SergeyBiryukov, coffee2code.
 Fixes #2147.
 }}}

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

From noreply at wordpress.org  Tue Oct 25 21:59:19 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Oct 2016 21:59:19 +0000 (UTC)
Subject: [wp-meta] [4294]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/handbook/
 handbook.php: Handbook plugin: Change handling for noting is_handbook_root.
Message-ID: <20161025215919.E69B21080366@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 25 22:10:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 22:10:53 -0000
Subject: [wp-meta] [Making WordPress.org] #1744: Plugin Directory Theme:
 Improve "Description" section
In-Reply-To: <051.c7d7b35a0c56ed362205338b5774d915@wordpress.org>
References: <051.c7d7b35a0c56ed362205338b5774d915@wordpress.org>
Message-ID: <066.a49a43ade50f7c4d977acf5e9699af60@wordpress.org>

#1744: Plugin Directory Theme: Improve "Description" section
------------------------------+---------------------------------------
 Reporter:  ocean90           |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------------------------
Changes (by mapk):

 * type:  enhancement => task


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

From noreply at wordpress.org  Tue Oct 25 22:10:24 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 22:10:24 -0000
Subject: [wp-meta] [Making WordPress.org] #1744: Plugin Directory Theme:
 Improve "Description" section
In-Reply-To: <051.c7d7b35a0c56ed362205338b5774d915@wordpress.org>
References: <051.c7d7b35a0c56ed362205338b5774d915@wordpress.org>
Message-ID: <066.df19523beb0898285160bb576d35a038@wordpress.org>

#1744: Plugin Directory Theme: Improve "Description" section
------------------------------+---------------------------------------
 Reporter:  ocean90           |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------------------------
Changes (by mapk):

 * priority:  lowest => normal
 * milestone:   => Plugin Directory v3 - M9


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

From noreply at wordpress.org  Tue Oct 25 22:19:21 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 22:19:21 -0000
Subject: [wp-meta] [Making WordPress.org] #2183: Add back meta information
 to plugin cards for homepage and search results
Message-ID: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>

#2183: Add back meta information to plugin cards for homepage and search results
------------------------------+--------------------------------------
 Reporter:  mapk              |      Owner:
     Type:  task              |     Status:  new
 Priority:  normal            |  Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------------------------
 Let's add back the plugin meta information like: Author, Active Installs,
 Compatible with, and Last Updated to the Plugin Cards for the homepage and
 search results. Adding this information back is highly requested by
 community and important when searching for specific plugins.

 Example of new UI: http://codepen.io/mapk/pen/jqxqbo
 props @webdevmattcrom for helping with design.

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

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

From noreply at wordpress.org  Tue Oct 25 22:16:54 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Tue, 25 Oct 2016 22:16:54 +0000 (UTC)
Subject: [wp-meta] [4295]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-support/functions.php: Support Theme: Bump CSS version for cache
 bust.
Message-ID: <20161025221654.C90B11080366@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Tue Oct 25 22:37:04 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 22:37:04 -0000
Subject: [wp-meta] [Making WordPress.org] #2183: Add back meta
 information to plugin cards for homepage and search results
In-Reply-To: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
References: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
Message-ID: <063.351f378f680ce0ce4d84e76f2727765f@wordpress.org>

#2183: Add back meta information to plugin cards for homepage and search results
------------------------------+---------------------------------------
 Reporter:  mapk              |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by webdevmattcrom):

 Love it! Let's make it happen.

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

From noreply at wordpress.org  Tue Oct 25 22:47:03 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Tue, 25 Oct 2016 22:47:03 -0000
Subject: [wp-meta] [Making WordPress.org] #2180: Tags missing from plugin
In-Reply-To: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>
References: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>
Message-ID: <070.0b0b3e6cef505330159dac796725fd0a@wordpress.org>

#2180: Tags missing from plugin
------------------------------+-------------------------
 Reporter:  johnbillion       |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  worksforme
 Keywords:                    |
------------------------------+-------------------------

Comment (by johnbillion):

 Thanks. The tags definitely weren't there when I reported this so there
 must have been an issue generating the list of tags, although the plugin
 hasn't been updated in two months.

 Regarding tagged releases -- deleting tags kind of defeats the point of
 tagging releases, no? This sounds like an infrastructure issue rather than
 something that every plugin developer needs to address.

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

From noreply at wordpress.org  Wed Oct 26 05:13:21 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 05:13:21 -0000
Subject: [wp-meta] [Making WordPress.org] #2180: Tags missing from plugin
In-Reply-To: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>
References: <055.49e48165a39cf2b12df4a19775dd9823@wordpress.org>
Message-ID: <070.d214ce8a1c2427be31e04a3dc5bdcede@wordpress.org>

#2180: Tags missing from plugin
------------------------------+-------------------------
 Reporter:  johnbillion       |       Owner:
     Type:  defect            |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  worksforme
 Keywords:                    |
------------------------------+-------------------------

Comment (by dd32):

 > This sounds like an infrastructure issue rather than something that
 every plugin developer needs to address.

 Correct, it's also fixed in the new plugin directory, as it doesn't take
 the same hard rebuild-every-zip-on-every-commit that the existing
 directory does. That's why plugins with lots of tags often have issues, as
 the process can sometimes (but rarely) timeout while doing the build.
 In this case I believe the issue was bad caching (unless someone re-ran
 the plugin import).

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

From noreply at wordpress.org  Wed Oct 26 06:46:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 06:46:29 -0000
Subject: [wp-meta] [Making WordPress.org] #633: Add sync for
 develop.git.wordpress.org with Github
In-Reply-To: <050.5567621cdca267cdc75d67c2dd966981@wordpress.org>
References: <050.5567621cdca267cdc75d67c2dd966981@wordpress.org>
Message-ID: <065.97443f02f0d921a2886390c68180de1b@wordpress.org>

#633: Add sync for develop.git.wordpress.org with Github
-----------------------------+------------------
 Reporter:  jorbin           |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Version Control  |  Resolution:
 Keywords:                   |
-----------------------------+------------------

Comment (by netweb):

 Just an update, this was brought up again today in #core:

 https://wordpress.slack.com/archives/core/p1477460871009583

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

From noreply at wordpress.org  Wed Oct 26 11:48:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 11:48:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2184: Overall translation
 contributor stats for a locale
In-Reply-To: <058.8d5b9f7b8386415a62f5c9192c3a602a@wordpress.org>
References: <058.8d5b9f7b8386415a62f5c9192c3a602a@wordpress.org>
Message-ID: <073.cc5a860b0d7407343195c26c3e15c665@wordpress.org>

#2184: Overall translation contributor stats for a locale
--------------------------------------+------------------
 Reporter:  SergeyBiryukov            |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by SergeyBiryukov):

 Related: #1044, #1388.

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

From noreply at wordpress.org  Wed Oct 26 11:48:25 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 11:48:25 -0000
Subject: [wp-meta] [Making WordPress.org] #2184: Overall translation
 contributor stats for a locale
Message-ID: <058.8d5b9f7b8386415a62f5c9192c3a602a@wordpress.org>

#2184: Overall translation contributor stats for a locale
--------------------------------------+-----------------
 Reporter:  SergeyBiryukov            |      Owner:
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+-----------------
 With the second [https://wptranslationday.org/ Global WordPress
 Translation Day] upcoming, it would be nice if GTEs could see and
 recognize contributors who translated the most strings during the event.

 Two things would be helpful here:
 * An ability to view the list of contributors whose translations were
 approved between two particular dates.
 * An ability to view all contributors for the locale, sorted by approved
 strings count.

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

From noreply at wordpress.org  Wed Oct 26 14:27:38 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 14:27:38 -0000
Subject: [wp-meta] [Making WordPress.org] #2185: All my messages are always
 "held for moderation"
Message-ID: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>

#2185: All my messages are always "held for moderation"
------------------------------------+-----------------
 Reporter:  Astrix                  |      Owner:
     Type:  defect                  |     Status:  new
 Priority:  normal                  |  Milestone:
Component:  Login & Authentication  |   Keywords:
------------------------------------+-----------------
 Hello,

 What is the reason for this ?

 Even posts that do not contain links or images. Even just text posts are
 displaying  "This post has been held for moderation by our automated
 system. It will be reviewed within 72 hours."

 It's quite annoying to wait for 72hours for a simple post on a support
 forum...

 Thank you !

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

From noreply at wordpress.org  Wed Oct 26 14:38:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 14:38:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2185: All my messages are
 always "held for moderation"
In-Reply-To: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
References: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
Message-ID: <065.08317ed0819b2df3d56b279c7d626edf@wordpress.org>

#2185: All my messages are always "held for moderation"
----------------------------+------------------
 Reporter:  Astrix          |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------
Changes (by SergeyBiryukov):

 * component:  Login & Authentication => Support Forums


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

From noreply at wordpress.org  Wed Oct 26 14:41:22 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 14:41:22 -0000
Subject: [wp-meta] [Making WordPress.org] #2185: All my messages are
 always "held for moderation"
In-Reply-To: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
References: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
Message-ID: <065.fdbf54f05e779e19cc5a5e8576d24b8d@wordpress.org>

#2185: All my messages are always "held for moderation"
------------------------------------+----------------------
 Reporter:  Astrix                  |       Owner:
     Type:  defect                  |      Status:  closed
 Priority:  normal                  |   Milestone:
Component:  Login & Authentication  |  Resolution:  invalid
 Keywords:  close                   |
------------------------------------+----------------------
Changes (by geoffreyshilling):

 * keywords:   => close
 * resolution:   => invalid
 * status:  new => closed
 * component:  Support Forums => Login & Authentication


Comment:

 Aloha Astrix,  I apologize for that frustration.  Your account had been
 flagged by our old system for some reason.  I have corrected this and your
 posts should now show up.  Thanks for your patience and understanding!

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

From noreply at wordpress.org  Wed Oct 26 14:42:49 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 14:42:49 -0000
Subject: [wp-meta] [Making WordPress.org] #2185: All my messages are
 always "held for moderation"
In-Reply-To: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
References: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
Message-ID: <065.eca1d6ec914ee07d494b3614a57d1a03@wordpress.org>

#2185: All my messages are always "held for moderation"
----------------------------+----------------------
 Reporter:  Astrix          |       Owner:
     Type:  task            |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  invalid
 Keywords:                  |
----------------------------+----------------------
Changes (by Kenshino):

 * keywords:  close =>
 * type:  defect => task
 * component:  Login & Authentication => Support Forums


Comment:

 Take note though Trac isn't the right place for such questions - feel free
 to come onto Slack https://make.wordpress.org/chat/ #forums where you can
 ask the Support Team for such issues.

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

From noreply at wordpress.org  Wed Oct 26 16:11:10 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 16:11:10 -0000
Subject: [wp-meta] [Making WordPress.org] #2185: All my messages are
 always "held for moderation"
In-Reply-To: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
References: <050.675ec6cff3aa530e562a422ea09d5f96@wordpress.org>
Message-ID: <065.23e8bb6b43aafbc9adec02427b858d18@wordpress.org>

#2185: All my messages are always "held for moderation"
----------------------------+----------------------
 Reporter:  Astrix          |       Owner:
     Type:  task            |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  invalid
 Keywords:                  |
----------------------------+----------------------

Comment (by Astrix):

 Hi admins,

 I'm sorry for having posted on the wrong place !

 Thanks a lot for your help and understanding !

 Cheers

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

From noreply at wordpress.org  Wed Oct 26 21:13:00 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Oct 2016 21:13:00 +0000 (UTC)
Subject: [wp-meta] [4296]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-support:
 Support Theme: Apply proper content and sidebar floats for topic-tag views.
Message-ID: <20161026211300.E0B261080375@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 26 22:39:44 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Oct 2016 22:39:44 +0000 (UTC)
Subject: [wp-meta] [4297]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-directory-compat.php: Support Forums,
 Directory Compat: Split bulk of `get_object() ` off into static
 `get_object_by_slug_and_type() ` to facilitate use elsewhere to fetch
 plugin or theme object by slug.
Message-ID: <20161026223944.101CC1080375@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 26 22:59:53 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Oct 2016 22:59:53 +0000 (UTC)
Subject: [wp-meta] [4299]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-support/functions.php: Support Theme: Bump CSS version for cache
 bust.
Message-ID: <20161026225953.B49931080375@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 26 22:59:07 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Wed, 26 Oct 2016 22:59:07 +0000 (UTC)
Subject: [wp-meta] [4298]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums,
 Support Compat: Insert link to plugin or theme' s support or review view
 into breadcrumbs in single topic view.
Message-ID: <20161026225907.E6AFB1080375@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Wed Oct 26 22:59:08 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Wed, 26 Oct 2016 22:59:08 -0000
Subject: [wp-meta] [Making WordPress.org] #2181: Support Theme:
 Breadcrumb links for plugins
In-Reply-To: <051.0e338a5ddc6f0704f981571bffd8c543@wordpress.org>
References: <051.0e338a5ddc6f0704f981571bffd8c543@wordpress.org>
Message-ID: <066.cb8b8a67b25c6362abb65adafef15f65@wordpress.org>

#2181: Support Theme: Breadcrumb links for plugins
----------------------------+--------------------------
 Reporter:  Clorith         |       Owner:  coffee2code
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+--------------------------
Changes (by coffee2code):

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


Comment:

 In [changeset:"4298"]:
 {{{
 #!CommitTicketReference repository="" revision="4298"
 Support Forums, Support Compat: Insert link to plugin or theme's support
 or review view into breadcrumbs in single topic view.

 The breadcrumb was already modified in this manner in plugin and theme
 support/review views, but not for their constituent topics.

 Fixes #2181.
 }}}

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

From noreply at wordpress.org  Thu Oct 27 06:01:29 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 27 Oct 2016 06:01:29 +0000 (UTC)
Subject: [wp-meta] [4300]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-support/: Support Theme: Add `node_modules` folder to `svn:ignore`
Message-ID: <20161027060129.418EC108060E@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 27 06:31:28 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 27 Oct 2016 06:31:28 +0000 (UTC)
Subject: [wp-meta] [4301]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Add plugin committer management to the new plugin admin.
Message-ID: <20161027063128.E299C1080335@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 27 06:31:29 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 06:31:29 -0000
Subject: [wp-meta] [Making WordPress.org] #2111: Move administration
 tools from wp-admin to front end
In-Reply-To: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
References: <054.bcc4457568e61ee2c2f3052ed8b17eee@wordpress.org>
Message-ID: <069.23c2ef1cf1cf396c5cd38b3589fc18b4@wordpress.org>

#2111: Move administration tools from wp-admin to front end
------------------------------+---------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-screenshots   |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4301"]:
 {{{
 #!CommitTicketReference repository="" revision="4301"
 Plugin Directory: Add plugin committer management to the new plugin admin.

 See #2111.
 }}}

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

From noreply at wordpress.org  Thu Oct 27 10:50:17 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 10:50:17 -0000
Subject: [wp-meta] [Making WordPress.org] #1825: Style handbook with new
	O2 design
In-Reply-To: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
References: <053.217697cf1994a666a81d0e40546d4041@wordpress.org>
Message-ID: <068.8b80d1f199fcc120ca194c18f42817d6@wordpress.org>

#1825: Style handbook with new O2 design
--------------------------------------+------------------
 Reporter:  chriscct7                 |       Owner:
     Type:  task                      |      Status:  new
 Priority:  high                      |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:
 Keywords:                            |
--------------------------------------+------------------

Comment (by pento):

 In [changeset:"4302"]:
 {{{
 #!CommitTicketReference repository="" revision="4302"
 Breathe: Add some styling for the the handbook "Chapters" menu.

 See #1825.
 }}}

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

From noreply at wordpress.org  Thu Oct 27 10:50:16 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Thu, 27 Oct 2016 10:50:16 +0000 (UTC)
Subject: [wp-meta] [4302]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/ wporg-breathe:
 Breathe: Add some styling for the the handbook "Chapters" menu.
Message-ID: <20161027105016.CACD41080366@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Thu Oct 27 14:23:43 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 14:23:43 -0000
Subject: [wp-meta] [Making WordPress.org] #2186: Login link missing from new
	theme
Message-ID: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>

#2186: Login link missing from new theme
----------------------------+-----------------
 Reporter:  sterndata       |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 On the old theme, there's a login link on the menu bar at the top right.
 On the new theme, there's no way to login... even the "you must login to
 post" does not have "login" linked.

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

From noreply at wordpress.org  Thu Oct 27 16:19:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 16:19:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2186: Support Theme: Login
 link missing from new theme
In-Reply-To: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>
References: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>
Message-ID: <068.347023c087deef5cf59ea87ca27937cf@wordpress.org>

#2186: Support Theme: Login link missing from new theme
----------------------------+------------------
 Reporter:  sterndata       |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------
Changes (by sterndata):

 * component:  Handbooks => Support Forums


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

From noreply at wordpress.org  Thu Oct 27 16:18:51 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 16:18:51 -0000
Subject: [wp-meta] [Making WordPress.org] #2186: Support Theme: Login
 link missing from new theme (was: Login link missing from new theme)
In-Reply-To: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>
References: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>
Message-ID: <068.b6a67aef451bfa26a5980d58931980cf@wordpress.org>

#2186: Support Theme: Login link missing from new theme
-----------------------+------------------
 Reporter:  sterndata  |       Owner:
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  Handbooks  |  Resolution:
 Keywords:             |
-----------------------+------------------
Changes (by sterndata):

 * component:  Support Forums => Handbooks


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

From noreply at wordpress.org  Thu Oct 27 16:28:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 16:28:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2186: Support Theme: Login
 link missing from new theme
In-Reply-To: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>
References: <053.445c29e4eeebc258e3dd8a266e8340a5@wordpress.org>
Message-ID: <068.ffe7675e4488bab0944ff3134f1da2b5@wordpress.org>

#2186: Support Theme: Login link missing from new theme
----------------------------+------------------
 Reporter:  sterndata       |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by samuelsidler):

 In general, we decided to add the admin bar to the site when logged out,
 to cover this case (which I just did on the main support forums). But we
 should linkify that text for login. I see this text:
 > You must be logged in to reply to this topic.
 We should be linking it to the appropriate login.wordpress.org page that
 redirects back to the current URL.

 @sergeybiryukov: Want to fix this up?

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

From noreply at wordpress.org  Thu Oct 27 19:01:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Thu, 27 Oct 2016 19:01:53 -0000
Subject: [wp-meta] [Making WordPress.org] #2187: Allow ticket queries in
 Trac to use keywords combinations (and, or)
Message-ID: <054.19488d2ccfaa527e82872ac5cbe494cd@wordpress.org>

#2187: Allow ticket queries in Trac to use keywords combinations (and, or)
-------------------------+-----------------
 Reporter:  flefebvre2   |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Trac         |   Keywords:
-------------------------+-----------------
 Regarding [https://core.trac.wordpress.org/query custom queries] for
 tickets in Trac

 == Actual behavior ==

 The only possible filter pattern to filter tickets on is :

 Keywords [contains,is,is not...] somekeyword1 '''or''' somekeyword2
 '''or''' somekeyword3 ...

 == Proposed behavior ==

 It would be great to filter with filters looking like :

 Keywords [contains,is,is not...] somekeyword1 '''and''' [contains,is,is
 not...] somekeyword2...

 Ex. Keywords contains good-first-bug and contains needs-patch

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

From noreply at wordpress.org  Fri Oct 28 06:32:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Oct 2016 06:32:53 -0000
Subject: [wp-meta] [Making WordPress.org] #1744: Plugin Directory Theme:
 Improve "Description" section
In-Reply-To: <051.c7d7b35a0c56ed362205338b5774d915@wordpress.org>
References: <051.c7d7b35a0c56ed362205338b5774d915@wordpress.org>
Message-ID: <066.60b11103156a79ad0b530ca808a6d706@wordpress.org>

#1744: Plugin Directory Theme: Improve "Description" section
------------------------------+---------------------------------------
 Reporter:  ocean90           |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------------------------

Comment (by tellyworth):

 In [changeset:"4303"]:
 {{{
 #!CommitTicketReference repository="" revision="4303"
 Plugin Directory Theme: don't show Read More links if the content is less
 than 125% of the available height.

 See #1744
 }}}

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

From noreply at wordpress.org  Fri Oct 28 06:32:52 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 28 Oct 2016 06:32:52 +0000 (UTC)
Subject: [wp-meta] [4303]
 sites/trunk/wordpress.org/public_html/wp-content/themes/pub/
 wporg-plugins/js/section-accordion.js: Plugin Directory Theme: don' t show
 Read More links if the content is less than 125% of the available height.
Message-ID: <20161028063252.D15951080347@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Fri Oct 28 07:05:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Oct 2016 07:05:52 -0000
Subject: [wp-meta] [Making WordPress.org] #2183: Add back meta
 information to plugin cards for homepage and search results
In-Reply-To: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
References: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
Message-ID: <063.0cb66c7f94c768fa19436e9338534cf3@wordpress.org>

#2183: Add back meta information to plugin cards for homepage and search results
------------------------------+---------------------------------------
 Reporter:  mapk              |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 How do you propose we handle the Author section where it has multiple
 authors?
 For an example of that, check out
 [https://wordpress.org/plugins/search.php?q=debug%20bar this search].

 The existing directory limits it to the first six listed contributors on
 this view.

 The other option, is that we use the `Plugin Author` field from the
 plugin, but we won't be able to use that to link to an archive/search of
 their plugins.

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

From noreply at wordpress.org  Fri Oct 28 13:00:22 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Oct 2016 13:00:22 -0000
Subject: [wp-meta] [Making WordPress.org] #2188: REST-API Json decode error
 will not give back an error
Message-ID: <057.9236ed6e76638ad5fb560694051d39e4@wordpress.org>

#2188: REST-API Json decode error will not give back an error
---------------------------+-----------------
 Reporter:  danielhuesken  |      Owner:
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:
Component:  API            |   Keywords:
---------------------------+-----------------
 If you send a Request to the Rest API with a defect json in body than it
 will not return a error. That is not so good, because you get back a
 response that suggest all is ok.

 METHOD: POST
 WordPress: 3.6.1

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

From noreply at wordpress.org  Fri Oct 28 13:18:51 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Oct 2016 13:18:51 -0000
Subject: [wp-meta] [Making WordPress.org] #2188: REST-API Json decode
 error will not give back an error
In-Reply-To: <057.9236ed6e76638ad5fb560694051d39e4@wordpress.org>
References: <057.9236ed6e76638ad5fb560694051d39e4@wordpress.org>
Message-ID: <072.4988305ce2432670a7c13a86a5897bf0@wordpress.org>

#2188: REST-API Json decode error will not give back an error
---------------------------+----------------------
 Reporter:  danielhuesken  |       Owner:
     Type:  enhancement    |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  API            |  Resolution:  invalid
 Keywords:                 |
---------------------------+----------------------
Changes (by danielhuesken):

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


Comment:

 Sorry false track.

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

From noreply at wordpress.org  Fri Oct 28 17:06:20 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Fri, 28 Oct 2016 17:06:20 -0000
Subject: [wp-meta] [Making WordPress.org] #2183: Add back meta
 information to plugin cards for homepage and search results
In-Reply-To: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
References: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
Message-ID: <063.3e57304962edb57aa728268e51037c10@wordpress.org>

#2183: Add back meta information to plugin cards for homepage and search results
------------------------------+---------------------------------------
 Reporter:  mapk              |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by webdevmattcrom):

 @dd32 If I recall correctly, we did plan to use the Plugin Author. I
 assumed that the link on that Plugin Author would go to their Profile
 page, just like it does currently. Like from your search link, clicking
 the Author "WordPress.org" goes here:
 https://profiles.wordpress.org/wordpressdotorg/

 Isn't that possible with the Plugin Author field?

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

From noreply at wordpress.org  Fri Oct 28 19:05:15 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Fri, 28 Oct 2016 19:05:15 +0000 (UTC)
Subject: [wp-meta] [4304]
 sites/trunk/common/includes/slack/announce/config.php: Slack Announce: Add
 @empireoflight to #design-dashicons.
Message-ID: <20161028190515.8A4001080399@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 29 01:21:13 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 01:21:13 -0000
Subject: [wp-meta] [Making WordPress.org] #2183: Add back meta
 information to plugin cards for homepage and search results
In-Reply-To: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
References: <048.7c48e5226195dc27ac9b452800b3fe19@wordpress.org>
Message-ID: <063.6c96c28c516fc85a2acedd1d973dd36c@wordpress.org>

#2183: Add back meta information to plugin cards for homepage and search results
------------------------------+---------------------------------------
 Reporter:  mapk              |       Owner:
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 > Isn't that possible with the Plugin Author field?

 Nope, the `Plugin Author` field are these two lines from the readme.txt:
 https://plugins.trac.wordpress.org/browser/debug-bar/tags/0.8.4/debug-
 bar.php?marks=6,8 - There's no ability to link that to a user profile (in
 this case the name matches a WordPress.org username, but that's in the
 minority).

 Where as the `By: WordPress.org, Ryan Boren, Peter Westwood, koopersmith,
 Jon Cave, and others.` line on the existing directory is from this line:
 https://plugins.trac.wordpress.org/browser/debug-
 bar/tags/0.8.4/readme.txt?marks=2 (Each of which is a WordPress.org
 username, which has a profile, and is listed as the 'Authors' in the
 directory).

 Personally, I think it should be the `Plugin Author` field and we live
 with the fact it doesn't have an archive ability attached to it. Probably
 best to strip out the off-site link there though too.

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

From noreply at wordpress.org  Sat Oct 29 10:31:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 10:31:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2189: Forums: Detect
 non-image URLs in <img> tags
In-Reply-To: <058.113c040a0af04221c25c37008c590a1b@wordpress.org>
References: <058.113c040a0af04221c25c37008c590a1b@wordpress.org>
Message-ID: <073.a4b2dd74b9baf3b4e7fe26b95a25c83a@wordpress.org>

#2189: Forums: Detect non-image URLs in <img> tags
----------------------------+------------------
 Reporter:  SergeyBiryukov  |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------
Description changed by SergeyBiryukov:

Old description:

> With the upgrade to bbPress 2.x, it's now possible to insert images
> directly into support forum posts.
>
> However, most new forum members incorrectly use `<img>` tags for web
> pages instead of images, which results in a broken image in their post. A
> recent example:
> {{{
> <img src="https://gyazo.com/c57448863a8cd682d3bc6ba718506547"
> alt="Shipping Options" />
> }}}
> The URL here is a web page with an image, but not the an image itself.
>
> This should be more user-friendly. We could probably detect that the URL
> provided for `src` is not an image and automatically convert the code to
> a regular link in that case:
> {{{
> <a href="https://gyazo.com/c57448863a8cd682d3bc6ba718506547">Shipping
> Options</a>
> }}}

New description:

 With the upgrade to bbPress 2.x, it's now possible to insert images
 directly into support forum posts.

 However, most new forum members incorrectly use `<img>` tags for web pages
 instead of images, which results in a broken image in their post. A recent
 example:
 {{{
 <img src="https://gyazo.com/c57448863a8cd682d3bc6ba718506547"
 alt="Shipping Options" />
 }}}
 The URL here is a web page with an image, but not the image itself.

 This should be more user-friendly. We could probably detect that the URL
 provided for `src` is not an image and automatically convert the code to a
 regular link in that case:
 {{{
 <a href="https://gyazo.com/c57448863a8cd682d3bc6ba718506547">Shipping
 Options</a>
 }}}

--

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

From noreply at wordpress.org  Sat Oct 29 10:31:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 10:31:14 -0000
Subject: [wp-meta] [Making WordPress.org] #2189: Forums: Detect non-image
 URLs in <img> tags
Message-ID: <058.113c040a0af04221c25c37008c590a1b@wordpress.org>

#2189: Forums: Detect non-image URLs in <img> tags
----------------------------+-----------------
 Reporter:  SergeyBiryukov  |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 With the upgrade to bbPress 2.x, it's now possible to insert images
 directly into support forum posts.

 However, most new forum members incorrectly use `<img>` tags for web pages
 instead of images, which results in a broken image in their post. A recent
 example:
 {{{
 <img src="https://gyazo.com/c57448863a8cd682d3bc6ba718506547"
 alt="Shipping Options" />
 }}}
 The URL here is a web page with an image, but not the an image itself.

 This should be more user-friendly. We could probably detect that the URL
 provided for `src` is not an image and automatically convert the code to a
 regular link in that case:
 {{{
 <a href="https://gyazo.com/c57448863a8cd682d3bc6ba718506547">Shipping
 Options</a>
 }}}

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

From noreply at wordpress.org  Sat Oct 29 10:59:57 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 29 Oct 2016 10:59:57 +0000 (UTC)
Subject: [wp-meta] [4305] sites/trunk/wordpress.org/public_html: Trac: Add
 `rest-api` as focus keyword for Core Trac.
Message-ID: <20161029105957.532B01080371@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 29 10:59:57 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 10:59:57 -0000
Subject: [wp-meta] [Making WordPress.org] #2179: Add `rest-api` as focus
 keyword for Core Trac
In-Reply-To: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>
References: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>
Message-ID: <067.f71ecc923cb6766852c1c2be053d47f2@wordpress.org>

#2179: Add `rest-api` as focus keyword for Core Trac
-------------------------+----------------------
 Reporter:  flixos90     |       Owner:  ocean90
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:  fixed
 Keywords:  has-patch    |
-------------------------+----------------------
Changes (by ocean90):

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


Comment:

 In [changeset:"4305"]:
 {{{
 #!CommitTicketReference repository="" revision="4305"
 Trac: Add `rest-api` as focus keyword for Core Trac.

 Props flixos90.
 Fixes #2179.
 }}}

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

From noreply at wordpress.org  Sat Oct 29 11:30:20 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 29 Oct 2016 11:30:20 +0000 (UTC)
Subject: [wp-meta] [4306]
 sites/trunk/trac.wordpress.org/templates/site.html: Trac: Bump scripts
 version.
Message-ID: <20161029113020.5DC241080371@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 29 11:41:26 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 29 Oct 2016 11:41:26 +0000 (UTC)
Subject: [wp-meta] [4307] sites/trunk/common/includes/slack/trac/config.php:
 Slack: Send `rest-api` focus tickets to #core-restapi.
Message-ID: <20161029114126.ABDF71080371@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 29 11:41:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 11:41:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2179: Add `rest-api` as focus
 keyword for Core Trac
In-Reply-To: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>
References: <052.ba0732adcbbe2168d58285878651382f@wordpress.org>
Message-ID: <067.1e644ba4f24ca5052665bf74a13bce9c@wordpress.org>

#2179: Add `rest-api` as focus keyword for Core Trac
-------------------------+----------------------
 Reporter:  flixos90     |       Owner:  ocean90
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:  fixed
 Keywords:  has-patch    |
-------------------------+----------------------

Comment (by ocean90):

 In [changeset:"4307"]:
 {{{
 #!CommitTicketReference repository="" revision="4307"
 Slack: Send `rest-api` focus tickets to #core-restapi.

 See #2179.
 }}}

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

From noreply at wordpress.org  Sat Oct 29 17:36:15 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 17:36:15 -0000
Subject: [wp-meta] [Making WordPress.org] #2071: Plugin contributor
 feeds are broken, showing posts from across the forums
In-Reply-To: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
References: <055.295ec3ea1656bf1ef339bb41ffef42c5@wordpress.org>
Message-ID: <070.db59e83bbb289ea6104c03fdfa8b59d9@wordpress.org>

#2071: Plugin contributor feeds are broken, showing posts from across the forums
----------------------------+------------------
 Reporter:  johnbillion     |       Owner:
     Type:  defect          |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by jmdodd):

 In [changeset:"4308"]:
 {{{
 #!CommitTicketReference repository="" revision="4308"
 Support Forums: Use nicename for pagination rather than user login.

 See #2071.
 }}}

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

From noreply at wordpress.org  Sat Oct 29 17:36:15 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 29 Oct 2016 17:36:15 +0000 (UTC)
Subject: [wp-meta] [4308]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forums: Use nicename
 for pagination rather than user login.
Message-ID: <20161029173615.299381080371@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 29 19:35:06 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Sat, 29 Oct 2016 19:35:06 +0000 (UTC)
Subject: [wp-meta] [4309]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 support-forums/inc/class-support-compat.php: Support Forum: Redirect
 bbPress topic id shortlinks to new bbPress 2 permalinks.
Message-ID: <20161029193506.E0D911080371@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Sat Oct 29 19:35:07 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sat, 29 Oct 2016 19:35:07 -0000
Subject: [wp-meta] [Making WordPress.org] #1954: Forums: Add a redirect
 for old numeric topic URLs
In-Reply-To: <058.a7312a23a4cb84fb2aa989a0db8ccdd5@wordpress.org>
References: <058.a7312a23a4cb84fb2aa989a0db8ccdd5@wordpress.org>
Message-ID: <073.60607f6fb9e75234f9a9643fe7589f0d@wordpress.org>

#1954: Forums: Add a redirect for old numeric topic URLs
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  jmdodd
     Type:  defect          |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:  fixed
 Keywords:                  |
----------------------------+---------------------
Changes (by jmdodd):

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


Comment:

 In [changeset:"4309"]:
 {{{
 #!CommitTicketReference repository="" revision="4309"
 Support Forum: Redirect bbPress topic id shortlinks to new bbPress 2
 permalinks.

 bbPress 1 used topic ids to create shortlinks which were indexed by search
 engines and used in our own profile history. These links currently produce
 a 404 error.

 The `redirect_old_topic_id` function uses a custom table to dereference
 the old topic's new post id rather than the postmeta table for performance
 reasons.

 Fixes #1954.
 }}}

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

From noreply at wordpress.org  Sun Oct 30 12:11:02 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 30 Oct 2016 12:11:02 -0000
Subject: [wp-meta] [Making WordPress.org] #2190: Limit No Replies on bbPress
	2
Message-ID: <051.e01daeedcec4bd125997cc579e5df3cf@wordpress.org>

#2190: Limit No Replies on bbPress 2
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 In #887 we set the time we consider a no-replied topic to be relevant to
 21 days, and introduced a query arg for specifying the date if we wanted a
 different time window.

 After the move to bbPress2 we no longer limit this and display all the
 things, could we re-implement the old limit here.

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

From noreply at wordpress.org  Sun Oct 30 12:14:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 30 Oct 2016 12:14:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2191: Support Theme: Sub-forums
 are not discoverable
Message-ID: <051.c9c3752856afc512147dcc759e1bc09f@wordpress.org>

#2191: Support Theme: Sub-forums are not discoverable
----------------------------+-----------------
 Reporter:  Clorith         |      Owner:
     Type:  defect          |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Support Forums  |   Keywords:
----------------------------+-----------------
 We (at the moment) have one sub-forum,
 [https://wordpress.org/support/forum/plugins-and-hacks/hacks/ Hacks] under
 Plugins and Hacks.

 The new theme doesn't account for the possibility of subforums, so this is
 not discoverable without knowing the URL already.

 Ideally, we can do some gardening and actually remove the need for the
 subforums, but having support for it somehow would make sense to avoid
 needing to hack something in at a later date if it should ever become
 needed.

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

From noreply at wordpress.org  Sun Oct 30 12:31:46 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 30 Oct 2016 12:31:46 -0000
Subject: [wp-meta] [Making WordPress.org] #2191: Support Theme:
 Sub-forums are not discoverable
In-Reply-To: <051.c9c3752856afc512147dcc759e1bc09f@wordpress.org>
References: <051.c9c3752856afc512147dcc759e1bc09f@wordpress.org>
Message-ID: <066.65f476ff344ae3eb10372a63dc4488d9@wordpress.org>

#2191: Support Theme: Sub-forums are not discoverable
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by Clorith):

 While we're at it we should probably re-introduce #530 as well

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

From noreply at wordpress.org  Sun Oct 30 20:35:53 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Sun, 30 Oct 2016 20:35:53 -0000
Subject: [wp-meta] [Making WordPress.org] #1856: Attendance UI search
 does not handle apostrophes
In-Reply-To: <054.5edbbbee77c80bf5b8f9056959ecf632@wordpress.org>
References: <054.5edbbbee77c80bf5b8f9056959ecf632@wordpress.org>
Message-ID: <069.4327dde13118efb062fbad3c4228e62d@wordpress.org>

#1856: Attendance UI search does not handle apostrophes
-------------------------------------+------------------------
 Reporter:  johneckman               |       Owner:  kovshenin
     Type:  defect                   |      Status:  assigned
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  has-patch                |
-------------------------------------+------------------------
Changes (by BandonRandon):

 * keywords:  good-first-bug needs-patch => has-patch


Comment:

 Tested Patch, works as expected. cc @kovshenin

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

From noreply at wordpress.org  Mon Oct 31 01:06:44 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 01:06:44 -0000
Subject: [wp-meta] [Making WordPress.org] #2191: Support Theme:
 Sub-forums are not discoverable
In-Reply-To: <051.c9c3752856afc512147dcc759e1bc09f@wordpress.org>
References: <051.c9c3752856afc512147dcc759e1bc09f@wordpress.org>
Message-ID: <066.cc4cb87736bec506c7b65d5de53662c1@wordpress.org>

#2191: Support Theme: Sub-forums are not discoverable
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by netweb):

 Related #1959 Missing sub-forum description

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

From noreply at wordpress.org  Mon Oct 31 01:07:12 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 01:07:12 -0000
Subject: [wp-meta] [Making WordPress.org] #1959: Missing sub-forum
	description
In-Reply-To: <050.051735c2f450d2037bea7689eba31c02@wordpress.org>
References: <050.051735c2f450d2037bea7689eba31c02@wordpress.org>
Message-ID: <065.0822d47246b313a74c27a7bf9369d2e1@wordpress.org>

#1959: Missing sub-forum description
----------------------------+------------------
 Reporter:  netweb          |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:  needs-patch     |
----------------------------+------------------

Comment (by netweb):

 Related: #2191 Support Theme: Sub-forums are not discoverable

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

From noreply at wordpress.org  Mon Oct 31 01:40:14 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 31 Oct 2016 01:40:14 +0000 (UTC)
Subject: [wp-meta] [4310]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/
 plugin-directory/api/routes/class-plugin.php: Plugin Directory: Revert [
 3863] as the Reviews markup in the API is intentionally different from the
 markup used on WordPress.org.
Message-ID: <20161031014014.411FC10806CD@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 31 01:40:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 01:40:14 -0000
Subject: [wp-meta] [Making WordPress.org] #1719: Plugin Directory Theme
In-Reply-To: <052.31ffb9bf9f16ccfccd1148337f9eccd8@wordpress.org>
References: <052.31ffb9bf9f16ccfccd1148337f9eccd8@wordpress.org>
Message-ID: <067.21ea4210486df09116c0d30751e6d9b9@wordpress.org>

#1719: Plugin Directory Theme
------------------------------+---------------------------------------
 Reporter:  obenland          |       Owner:  obenland
     Type:  task              |      Status:  closed
 Priority:  normal            |   Milestone:  Plugin Directory v3 - M4
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4310"]:
 {{{
 #!CommitTicketReference repository="" revision="4310"
 Plugin Directory: Revert [3863] as the Reviews markup in the API is
 intentionally different from the markup used on WordPress.org.

 This fixes review display when WordPress is using the new API.

 See #1579, #1719.
 }}}

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

From noreply at wordpress.org  Mon Oct 31 01:40:14 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 01:40:14 -0000
Subject: [wp-meta] [Making WordPress.org] #1579: Plugins API
In-Reply-To: <052.c9092ef0a49c7a06d6a23dcbd8c8e564@wordpress.org>
References: <052.c9092ef0a49c7a06d6a23dcbd8c8e564@wordpress.org>
Message-ID: <067.8db1dad523e4ccd94ac2145947425eb7@wordpress.org>

#1579: Plugins API
------------------------------+---------------------------------------
 Reporter:  obenland          |       Owner:  dd32
     Type:  task              |      Status:  closed
 Priority:  high              |   Milestone:  Plugin Directory v3 - M7
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4310"]:
 {{{
 #!CommitTicketReference repository="" revision="4310"
 Plugin Directory: Revert [3863] as the Reviews markup in the API is
 intentionally different from the markup used on WordPress.org.

 This fixes review display when WordPress is using the new API.

 See #1579, #1719.
 }}}

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

From noreply at wordpress.org  Mon Oct 31 01:41:00 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 01:41:00 -0000
Subject: [wp-meta] [Making WordPress.org] #2192: Change the name of
 "invalid" ticket resolution
Message-ID: <049.3049ff7b9301b2a104134a574ebbe139@wordpress.org>

#2192: Change the name of "invalid" ticket resolution
--------------------+-----------------
 Reporter:  pento   |      Owner:
     Type:  defect  |     Status:  new
 Priority:  normal  |  Milestone:
Component:  Trac    |   Keywords:
--------------------+-----------------
 Particularly for Trac newbies, "invalid" can feel like a bit of a put-
 down, even with an explanation of why the ticket is being closed.

 Maybe `not-a-bug`, `not-a-core-bug`, or something of that nature would be
 better?

 Bikeshedding welcome on this ticket.

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

From noreply at wordpress.org  Mon Oct 31 02:00:27 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 02:00:27 -0000
Subject: [wp-meta] [Making WordPress.org] #2193: Add pointer to meta.trac
 from core.trac
Message-ID: <049.568ef687bfd53875867168c86046b7e1@wordpress.org>

#2193: Add pointer to meta.trac from core.trac
--------------------+-----------------
 Reporter:  pento   |      Owner:
     Type:  defect  |     Status:  new
 Priority:  normal  |  Milestone:
Component:  Trac    |   Keywords:
--------------------+-----------------
 Similar to how we add a pointer for security issues, based on keywords in
 the description, it'd be helpful to point folks to meta.trac when they ask
 about meta issues on core.trac.

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

From noreply at wordpress.org  Mon Oct 31 02:47:42 2016
From: noreply at wordpress.org (noreply at wordpress.org)
Date: Mon, 31 Oct 2016 02:47:42 +0000 (UTC)
Subject: [wp-meta] [4311]
 sites/trunk/wordpress.org/public_html/wp-content/plugins/ plugin-directory:
 Plugin Directory: Pull reviews from bbPress2 rather than the old bbPress1
 support forums.
Message-ID: <20161031024742.31ADE10806CD@svn1.lax.wordpress.org>

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

From noreply at wordpress.org  Mon Oct 31 02:47:42 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 02:47:42 -0000
Subject: [wp-meta] [Making WordPress.org] #1579: Plugins API
In-Reply-To: <052.c9092ef0a49c7a06d6a23dcbd8c8e564@wordpress.org>
References: <052.c9092ef0a49c7a06d6a23dcbd8c8e564@wordpress.org>
Message-ID: <067.fa3614e2ed716daa0ba1d7ced8ac6b86@wordpress.org>

#1579: Plugins API
------------------------------+---------------------------------------
 Reporter:  obenland          |       Owner:  dd32
     Type:  task              |      Status:  closed
 Priority:  high              |   Milestone:  Plugin Directory v3 - M7
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------------------------

Comment (by dd32):

 In [changeset:"4311"]:
 {{{
 #!CommitTicketReference repository="" revision="4311"
 Plugin Directory: Pull reviews from bbPress2 rather than the old bbPress1
 support forums.

 See #1579
 }}}

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

From noreply at wordpress.org  Mon Oct 31 11:02:21 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 11:02:21 -0000
Subject: [wp-meta] [Making WordPress.org] #2194: Contact Form should set the
 sender as the reply-to header
Message-ID: <048.e44fdba835a647effdc698f437562587@wordpress.org>

#2194: Contact Form should set the sender as the reply-to header
-------------------------------------------+-----------------
 Reporter:  dd32                           |      Owner:
     Type:  defect                         |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:
-------------------------------------------+-----------------
 Currently the Rosetta sites have a contact form that's very rudimentary,
 and which also sets the `From` and `Sender` headers to that of the user
 who is submitting the form.

 Unfortunately this can trigger DKIM & SPF failures which result in the
 email being marked as spam, for example:
 `Authentication-Results: mx.google.com; spf=fail (google.com: domain of
 my at email.com.au does not designate 66.155.40.8 as permitted sender)
 smtp.mailfrom=my at email.com.au`

 We should instead use a `noreply at w.org` email address and set the `Reply-
 To` header so that the replies go to the right location.

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

From noreply at wordpress.org  Mon Oct 31 11:47:26 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 11:47:26 -0000
Subject: [wp-meta] [Making WordPress.org] #2192: Change the name of
 "invalid" ticket resolution
In-Reply-To: <049.3049ff7b9301b2a104134a574ebbe139@wordpress.org>
References: <049.3049ff7b9301b2a104134a574ebbe139@wordpress.org>
Message-ID: <064.7526c220e26d8eeecb56f40257dc716c@wordpress.org>

#2192: Change the name of "invalid" ticket resolution
--------------------+------------------
 Reporter:  pento   |       Owner:
     Type:  defect  |      Status:  new
 Priority:  normal  |   Milestone:
Component:  Trac    |  Resolution:
 Keywords:          |
--------------------+------------------

Comment (by SergeyBiryukov):

 `not-a-core-bug` seems good to me. It would be helpful for things like
 #WP38428, where the report is technically valid, it's just not a core
 issue.

 However, if the new resolution contains dashes, others should be updated
 to use dashes too for consistency: `wont-fix`, `works-for-me`, `maybe-
 later`.

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

From noreply at wordpress.org  Mon Oct 31 21:05:52 2016
From: noreply at wordpress.org (Making WordPress.org)
Date: Mon, 31 Oct 2016 21:05:52 -0000
Subject: [wp-meta] [Making WordPress.org] #1824: Improve "Contributors &
 Developers" box
In-Reply-To: <056.0b3df93a528db4e3dab9f97146db6038@wordpress.org>
References: <056.0b3df93a528db4e3dab9f97146db6038@wordpress.org>
Message-ID: <071.b7760adf90e7972786918c06562f1d9b@wordpress.org>

#1824: Improve "Contributors & Developers" box
------------------------------+---------------------------------------
 Reporter:  samuelsidler      |       Owner:
     Type:  task              |      Status:  new
 Priority:  low               |   Milestone:  Plugin Directory v3 - M9
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------------------------
Changes (by mapk):

 * milestone:   => Plugin Directory v3 - M9


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