Agenda for ticket scrub on October 24th

This bi-weekly ticket scrub will happen on 2017-10-24 19:00 UTC in #meta-wordcamp.

The focus is on Meta tickets with the WordCamp Site & Plugins component.

Specific tickets

Other items?

Comment below if there’s any other ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

#1794-meta, #2501-meta, #3035-meta

Recap of ticket scrub on October 10th

Participants: @coreymckrill @grapplerulrich @kau-boy @sergeybiryukov

We focused on open tickets relating to WordCamp sessions and the schedule.


We determined that this issue is a fairly obscure edge case, as it only affects WordCamp schedules when viewing them in iOS Safari while in Reader mode. A good solution to the issue was not immediately clear to the group. We decided to add a screenshot of the issue and downgrade its priority level for the time being.


@Kau-Boy volunteered to take on this ticket, using an approach very similar to previous work done on the [sponsors] shortcode.


This ticket was actually fixed with a patch for #1896-meta.


We had some discussion about the best way to approach a solution for this ticket, but ultimately decided more information was needed first.

The next Ticket Scrub meeting will be in two weeks, 2017-10-24 19:00 UTC, in #meta-wordcamp.

#recap #ticket-scrub #wordcamp

#1896-meta, #3044-meta, #3111-meta, #3115-meta, #3117-meta

Agenda for ticket scrub on October 10th

This bi-weekly ticket scrub will happen on 2017-10-10 19:00 UTC in #meta-wordcamp.

The focus is on Meta tickets that have the WordCamp Site & Plugins component.

Specific tickets

Here are several available tickets related to Sessions:

Other items?

Comment below if there’s any other ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

#3044-meta, #3111-meta, #3115-meta, #3117-meta

Recap of ticket scrub on September 26th

Participants: @coreymckrill @grapplerulrich @miss_jwo @kau-boy @ryelle @sergeybiryukov

We started off by discussing some strategies for managing WordCamp tickets in Meta Trac. Historically, when new tickets have been created, an admin such as @iandunn or @coreymckrill has reviewed the ticket and “accepted” it as a way of marking it as a valid issue. The side effect of this has been that they are then “assigned” to that ticket, even if they intend to leave it as a “good-first-bug” for someone else. A lack of clarity around the meaning of an “assigned” user on a ticket may cause some people to pass over tickets that are actually available to work on.

@coreymckrill proposed that instead of accepting a ticket, it should be left as “new”, but relevant keywords such as “needs-patch” and “good-first-bug” should still be added. Then when someone submits a patch or indicates that they want to work on a ticket, they can be assigned to it. This would have a couple of benefits:

  • Easier to see which tickets are not being worked on yet
  • Easier to follow up with a ticket assignee if nothing has happened on it for a while

The group had general agreement that this strategy would be worth trying. Unfortunately, there does not appear to be a way in Trac to unassign a ticket and return it to “new” status, so this will only apply to new tickets going forward.


This is an issue that @miss_jwo has personally experienced. She volunteered to work on a patch, so @coreymckrill officially “assigned” it to her 🙂 A bit more research also needs to be done to determine the exact conditions that cause the issue.


The discussion here revolved around whether adding a heading parameter to each of the WordCamp CPT shortcodes is the best solution, as opposed to something like a feature flag (i.e. “all sites created after a certain date will show an H3 heading level instead of an H2”). The group decided on sort of a hybrid approach:

  • Add a new heading parameter that defaults to H2 for back-combat
  • Update the content in post/page stubs for new WordCamp sites so that the shortcodes include the heading parameter with the desired H3 specified.

@kau-boy volunteered to work on this ticket.


Several of us learned why adding a separate singular placeholder translation is necessary for some languages. @coreymckrill will commit the patch and follow up with the submitter about some minor code styling issues.

The next Ticket Scrub meeting will be in two weeks, 2017-10-10 19:00 UTC, in #meta-wordcamp.

#recap #ticket-scrub #wordcamp

#2851-meta, #3116-meta, #3156-meta

X-post: Gutenberg on WordCamp sites?

X-comment from Comment on Gutenberg on WordCamp sites?

Agenda for ticket scrub on September 26th

This bi-weekly ticket scrub will happen on 2017-09-26 19:00 UTC in #meta-wordcamp.

Specific tickets

Other items

  • Discuss ticket management
  • Continue going through the list of WordCamp-related good-first-bug tickets, review their status, and adjust status/keywords as necessary.

cc @sergeybiryukov @xkon @grapplerulrich @miss_jwo

#agenda #ticket-scrub #wordcamp

#2851-meta, #3116-meta

Recap of ticket scrub on August 29th

I will be AFK on 2017-09-12, so the next Ticket Scrub meeting will be in four weeks, 2017-09-26 19:00 UTC, in #meta-wordcamp.

Here is a summary of this week’s discussion:

Participants: @coreymckrill @sergeybiryukov @xkon


The latest patch from @grapplerulrich is ready to commit. @coreymckrill will add a slight wording tweak to it to clarify the Coming Soon notification:

Coming Soon mode is enabled. Site subscribers will not receive email notifications about published posts.


After the last scrub, @iandunn provided some clarification about the functionality in the current patch for this ticket:

If we don’t create menus at all, then the layout often breaks because the custom CSS assumes that they’re there. It wouldn’t make sense to add links to missing pages, though, and there aren’t any pages on the destination site yet, so it seemed like creating menus with just a Home link was the best we could do.

… I wonder if we could copy over the menu items for links that do exist on the destination site? A lot of pages like Location, Contact, etc are pre-populated, so they’ll exist. We could just skip the pages that don’t exist.

We decided it would be best to pursue the additional functionality suggested by Ian before committing, so that the menus wouldn’t just contain a “Home” link, which could be just as confusing as a broken layout.

@coreymckrill will update the ticket to see if the patch author wants to try making the update.


The patches provided by @kau-boy look good. @coreymckrill will do an additional round of local testing and then commit them, and then @kau-boy can update the handbook with documentation on the new shortcode attributes.


This one has an extensive patch from @xkon that has already been tested successfully on Since it involves remote requests, it just needs a security review before we merge it into the plugin.

@xkon also mentioned a fork of Tagregator that they built that is completely PHP-based instead of having a React component:

Social Mentions

#2218-meta, #3075-meta

These two tickets will enable more flexibility for the meetings functionality on Meta sites, which will allow us to include this meeting (since it is biweekly instead of every week)!

#recap #ticket-scrub #wordcamp

#1109-meta, #1751-meta, #2218-meta, #2907-meta, #3075-meta

Notice of Password Deactivation

Hello everyone, some of you will have the following email in your inbox:

Your password on has been deactivated, and you need to reset it to log in again.

We recently discovered your login credentials in a list of compromised emails and passwords published by a group of security researchers. This list was not generated as the result of any exploit on, but rather someone gaining access to the email & password combination you also used on another service.

To reset your password and get access to your account, please follow these steps:
1. Go to
2. Click on the link “Lost your password?”
3. Enter your username:
4. Click the “Get New Password” button

It is very important that your password be unique. Using the same password on different web sites increases the risk of your account being hacked.

If you have any further questions or trouble resetting your password, please reply to this message to get help from our support team. We will never ask you to supply your account password via email.

At this point we don’t have a reason to believe any accounts have been compromised, but out of an abundance of caution passwords are proactively disabled just to make sure.

If you have any questions don’t hesitate to post them in the comments.

[EDIT]: Updated the list typo to now go in order. ticket scrub agenda for August 29th

This is the agenda for our bi-weekly ticket scrub, which will happen 2017-08-29 19:00 UTC in #meta-wordcamp.

Specific tickets

Other items

  • Continue going through the list of WordCamp-related good-first-bug tickets, review their status, and adjust status/keywords as necessary.

If you would like to add a ticket or other item to the agenda, feel free to comment on this post. See you in the chat!

#agenda #ticket-scrub #wordcamp

#1109-meta, #1751-meta

O2 Plugin Request: The Final Word

For a little while on the Community Team we have been discussing how useful it would be to have a ‘top comment’ feature on O2 that would allow us to sum up a thread with a single comment. This would be similar to the ‘accepted answer’ function that you see on Stack Exchange and other support forums where one reply is highlighted and shown at the top of the comment thread. It’s great for long discussion threads and anything that requires a final decision (as a lot of our discussions on the Community P2 do).

In order to make this happen, I built a plugin called The Final Word (Plugin Directory / GitHub) that works with O2 to provide this functionality. I have opened a ticket for including this plugin that contains some screenshots of what this would look like.

The features of this plugin include:

  • Marking a chosen comment as the ‘top comment’
  • The top comment is displayed at the top of the comment list with a ‘view in context’ anchor link
  • The top comment is also highlighted in context in the thread
  • Only one comment can be selected as the top comment
  • The top comment flag can be removed
  • Only users who are able to edit the post can select a top comment
  • Includes basic styling for top comments

It’s worth noting that there is nothing in the plugin that will conflict with any existing features on Make and it barely adds any additional technical overhead, so if it is only used by a handful of teams, then the other teams won’t be negatively affected.

Assuming this is accepted and can be added to the Make blogs, the only additional code that we might need to add would be some additional CSS for the top comment styling. I purposefully built the CSS included the plugin to be very generic, so it may need some slight tweaking for the Make network. I would test this out locally, but the Meta Environment has not yet been updated to include O2, so I can’t do this effectively.

Thanks to @ocean90 for an initial code review, as well as @pento for some general pointers with regards to extending O2.

Also pinging @coreymckrill and @iandunn about this.