Open floor notes for September 12, 2017

A Slack account is needed to view the archives.

  • Child theme names [link]
  • Global admin notices [link]
  • Display author email addresses [link]
  • How-to review page draft [link]

September/October meeting times

Tuesday, 5th of September – No meeting

Thursday, 7th of September – “How to do a review” document meeting (formerly requirements rewrite)
Channel: #themereview | Time: 2017-09-7 17:00 UTC 17:00 UTC.

Tuesday, 12th of September – Open floor meeting
You can suggest topics by posting a comment. Let us know if you want to lead this meeting.
Channel: #themereview | Time: 2017-09-12 17:00 UTC 17:00 UTC.

Tuesday, 19th of September – No meeting

Tuesday 26th of September – Team meeting.
This meeting will be lead by @thinkupthemes.  Agenda will be posted at a later date. You can suggest topics by posting a comment.
Channel: #themereview | Time: 2017-09-26 17:00 UTC 17:00 UTC.

Tuesday, 3rd of October – No meeting

Tuesday, 10th of October – Open floor meeting
You can suggest topics by posting a comment. Let us know if you want to lead this meeting.
Channel: #themereview | Time: 2017-10-10 at 17:00 UTC 17:00 UTC.

Tuesday, 17th of October – No meeting

Review queue and theme maintenance tasks

We have gathered a list of tasks that the team needs to do regularly in order to maintain the review flow, besides reviewing themes.

If you feel “Oh yeah I can do that!” Please leave a comment, and we will include it in our spreadsheet and on the team members page.  If you are maybe interested, but you are not sure, you can ask team leads or moderators for more details.

  • Monitor report #22 to make sure no tickets are abandoned
    • Locating tickets that has had no replies within the last 7 days, and either close the ticket due to inactivity or return the ticket to the queue so that it can be picked up by a new reviewer.
    • Assigned to @rabmalin
  • Monitor report #16 to make sure no tickets were closed by mistake
    • Locate tickets that have been closed as not approved without cause, and return them to the queue.
    • Assigned to @kevinhaig
  • Monitor report #2 to answer general questions
  • Monitor the reports to make sure that authors only have one open ticket
    • Locating duplicate tickets, informing about the one theme policy and closing tickets as not approved.
  • Monitor report #24 to make sure no tickets were approved without a full review
    • Locate tickets that have been approved without a full review, and reopen them so that the reviewer can continue, or return it to the queue.
    • Assigned to @kevinhaig
  • Authors requesting new reviewers
    • Respond to authors who are requesting new reviewers, for example if the reviewer has not replied in 7 days.
    • Return the ticket to the queue.
  • Authors requesting tickets to be reopened
    • Respond to authors who are requesting their closed tickets to be reopened, for example if the theme was closed for less than five (required) issues.
  • Reviewers requesting to be removed from tickets
    • Respond to reviewers who are no longer able to continue with the review.
    • Return the ticket to the queue.
  • Closing theme copies
    • Locating tickets where the theme is a copy of an existing theme, explaining to the author why, and closing the ticket as not approved.
  • Closing and removing copies of commercial themes
    • Locating tickets where the theme is a copy of an existing commercial theme, explaining to the author why, and closing the ticket as not approved.
    • Notifying Otto42 so that the copy can be removed.

 

  • Theme author transfer requests
    • Moderators who already have access to the back end can help with transfer requests. We are looking to assign  one or two “go to” people who authors can contact directly if they need theme transfers.
    • assigned to @djrmom

 

 

  • Monitor open Theme Review meta tickets
  • Revise documentation and requirements
  • Occasional posts to remind authors of upcoming major theme changes (core changes)

Every 6 months:

  • Theme reviewer badges
  • Promote theme mods / demote theme mods that has not reviewed in the last 6 months (access required)

Meeting notes for August 29, 2017

Meeting [ link ]. A Slack account is need to view the archives.

Items discussed:

  • microformats [ link ]
  • Gutenberg [ link ]
  • Page on front [ link ]
  • Moderators [ link ]
  • Tasks [ link ]

Hello everyone, some of you…

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

Your password on WordPress.org 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 WordPress.org, 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 login.wordpress.org
2. Click on the link “Lost your password?”
3. Enter your WordPress.org 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.