WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 2 months ago

#1188 closed enhancement (maybelater)

New updated ticket process format

Reported by: karmatosed Owned by:
Milestone: Priority: normal
Component: Theme Review Keywords:
Cc:

Description

The theme review team have been working on how to get a new process for both updated and new themes. This trac ticket is the start of trying to work out what we need in place to get this done.

Here is the process broken down:

  1. A theme is updated in the normal way.
  2. The theme check plugin runs over the theme.
  3. If theme check passes, the theme goes live.
  4. If theme check fails, the theme doesn’t progress until it’s passed.
  5. If the theme goes live, trac ticket is made.
  6. We need a queue of recently updated tickets – note this may need tickets or something to indicate this. This queue is only for people if want to check updates.
  7. A button is on all themes in directory. This button is ‘report this theme’.

Report theme process

  1. The report button is clicked.
  2. You have to be logged in to report and also a ticket made and put in reported queue. You also have to give a report reason.
  3. The theme review team monitor this queue as a priority. Once a ticket appears there someone takes it and does a review.

We would also like to work in an iteration the addition of rejecting a report of a theme and then a support ticket being made for that theme. We can safely make the assumption that user needs support rather than the theme being fixed then.

I flagged this for trac but it also covers the theme directory.

Change History (18)

This ticket was mentioned in Slack in #themereview by karmatosed. View the logs.


4 years ago

#2 @greenshady
4 years ago

  • Cc justintadlock@… added

#3 @moonomo
4 years ago

  • Cc bangaliana@… added

This ticket was mentioned in Slack in #themereview by karmatosed. View the logs.


4 years ago

#5 @karmatosed
4 years ago

The report button should ask for a reason.

The report button should auto populate:

  • Reporters user name
  • Theme name
  • Link to theme in repo
  • Link to theme on svn (like normal trac tickets
  • Date/time of report

cc's include: reporter and theme author

Version 0, edited 4 years ago by karmatosed (next)

#6 @michaelbeil
4 years ago

  • Cc michaelbeil@… added

#7 @sakinshrestha
4 years ago

  • Cc info@… added

This ticket was mentioned in Slack in #themereview by omo. View the logs.


4 years ago

#9 @nacin
4 years ago

  • Component changed from Trac to Theme Review

#10 @nofearinc
4 years ago

  • Cc nofearinc@… added

This ticket was mentioned in Slack in #meta by dd32. View the logs.


4 years ago

This ticket was mentioned in Slack in #meta by obenland. View the logs.


4 years ago

This ticket was mentioned in Slack in #themereview by karmatosed. View the logs.


4 years ago

This ticket was mentioned in Slack in #themereview by poena. View the logs.


3 years ago

This ticket was mentioned in Slack in #themereview by rabmalin. View the logs.


2 years ago

#16 @obenland
22 months ago

  • Type changed from task to enhancement

This ticket was mentioned in Slack in #themereview by dingo_d. View the logs.


2 months ago

#18 @williampatton
2 months ago

  • Resolution set to maybelater
  • Status changed from new to closed

We looked at this ticket in our first TRT triage meeting today.

Between the time this ticket was made and now things have changed a bit with how our workflow goes.

It is no longer a primary intention to auto-live themes (even ones that pass theme check) as we have discovered that most themes that do pass theme check still have some problematic things inside them (authors just use different methods to add them that don't flag in theme check).

Out of the items in the original list above there are only a few ones that are currently relevant for our workflow.

Theme check runs at upload time.
It blocks themes from being added to trac if they have issues in that check.
The 'report a theme' button has been implemented and is on all theme pages.

This ticket stands right now it is partially resolved. The other parts we no longer want to pursue so strongly and anything we do need in future we will open a smaller ticket for.

Closing as 'maybelater' just now but I expect we might revisit this in future.

Note: See TracTickets for help on using tickets.