Welcome to the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team!

The Meta team is responsible for maintaining and managing WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ websites. Our work is mostly done on the meta trac. If you see a bug, file a ticket!

We’re currently working on these fine projects, with more in store.

Check out our handbook to learn how to get involved.

Konstantin Obenland 7:19 pm on February 24, 2015
Tags: theme directory ( 17 ), themereview, Themes API ( 4 )

Theme Directory Launch Checklist

Tomorrow we’re going live with the new Directory! We’ll start going through the checklist February 25th 2015 1700 UTC.

Disable uploads on bbpress themes.
Replace the uploader page with an “uploads temporarily offline” message.

Disable themes.trac sync process.

Announce launch in WPTRT meeting.
Commit an early return to sync-theme-review-results.php.
Inform Admins directly: No setting themes live between February 25th 2015 1600 UTC and the new directory is live.
Channel notification in #themereview.

Migrate themes to WP.
Run migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. script in /bin/themes/

Switch over Directory to not use API.

Commit https://cloudup.com/ckhD3Zl0Iso
Test on /themesnew.

Test themesnew API.

Switch to use themesnew.php on sandbox.
Test /wp-admin/theme-install.php locally.

Test themesnew downloads.

Switch to use themesnew.php on sandbox.
Test downloads locally and on /themesnew.

Up until here, no real damage is done, marks the last chance to postpone the launch.

Switch over downloads and API scripts.
mv index.php old-api.php
mv themesnew.php index.php

Switch over URLs and redirect.

Commit /themes removal.
Notify @seanosh about making the switch.
Commit mu-plugins commercial change.
Test the hell out of /themes.

Switch over review sync script.
mv sync-theme-review-results.php sync-theme-review-results-old.php
mv sync-theme-review-results-themesnew.php sync-theme-review-results.php

Enable theme uploads in directory plugin.
Remove custom message and uncomment upload handler.

#theme-directory, #themes-api

Andrew Nacin 9:19 pm on February 24, 2015
Are there actually redirects that need to occur? Are nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. rules already written for this? As far as I know, we should just need to remove bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org.-specific rules and let /themes/ fall through to WordPress.

This is actually a bit complicated. The order of operations should be to change the DB to reflect /themes not /themesnew, and then remove the rules. But, that’s not quite enough. We also need to remove the /themes bbPress external. This external will *not* be fully removed upon deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. — because it has externals inside of it, it will leave behind directories in the form of e.g. /themes/bb-includes/backpress/includes/pomo.

So, all of this needs to happen at basically the same time:
- /themes needs to be deleted from dotorg.svn, and deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors..
- The remnants of /themes/* needs to be removed manually from production servers.
- nginx needs to be reloaded (with rules removed).
I don’t think anyone has tested these steps. 🙂 @seanosh should be able to remove the /themes-specific nginx rules on your sandbox for you, then you can test the rest. The wporg-plugins-themes nginx conf file would also be a good thing to review as it might illustrate missing features from the new themes directory as well as what existing URLs should be supported, including /rss, /profile, /browse, etc. You can view these files from your sandbox.

We should probably create a script to do this in one go, as in, you commit to dotorg.svn and do not deploy, then @seanosh runs this as a global command:
svn up public_html # remove /themes, essentially deploying rm -r public_html/themes/ # actually remove /themes /etc/init.d/nginx reload # let it fall through to WordPress
- Konstantin Obenland 11:17 pm on February 24, 2015
  
  We also need to remove the /themes bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. external.
  
  As far as I can tell, there are only two externals, bbpress and backpress/includes, yes?
seanosh 11:23 pm on February 24, 2015

I’d prefer if the deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. itself went through the deploy script instead of calling “svn up” everywhere. If need be, we can execute commands immediately after the deploy has taken place. Or is that not possible, @nacin?

Welcome to the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team!

Contact

Share this: