Meta Environment Now Supports Contributing with Git

The Meta Environment has always managed its core functionality in Git, but up until now, it used Subversion to check out the actual files that make up each Meta website. New contributors are much more likely to be familiar with Git than SVN, though. Requiring them to learn SVN in addition to all of  our other tools and processes introduced an unnecessary burden.

The goal of the Environment is to help make contributing as easy as possible, so it makes sense to switch to Git instead. As of today, that switch is complete, and new installations will use Git automatically.

The two exceptions are: 1) Any plugin or theme that doesn’t have an official Git mirror; 2) the entire translate.wordpress.org site, since it’s in the process of migrating to GlotPress 2. In those cases, SVN is still used.

If you have an existing installation, it will continue to use Subversion until you git pull the latest copy of the Environment, and run vagrant provision. During that provision, each site’s public_html folder will be backed up to public_html-old-svn-backup, and a new Git-based public_html folder will be provisioned. If you’re working on any unfinished patches, just copy the modified files from the old directory to the new one.

If you’d like to learn more about contributing with Git, check out this guide from the Meta Handbook:

Contributing With Git

#wordpress-meta-environment

New Home for the Meta Environment

We’ve moved the Meta Environment from github.com/iandunn/wordpress-meta-environment to github.com/wordpress/meta-environment. Links to the old repository will redirect to the new one.

The goal of the Environment is to make it easy to contribute to the Meta team by giving you a local development environment that’s already setup with the official websites, so you don’t have to manually piece them together.

If you’ve been wanting to working on a patch for something, please check it out 🙂

 

#wordpress-meta-environment

Weekly i18n Chat Notes – September 1, 2015

Howdy! We have our weekly i18n chat tomorrow at 11:00 UTC. Please join us.

Last week, we discussed the following things:

  • Translate: A stats dashboard has been created. We’ll track the most important projects on this dashboard. We still need to add a couple of features for admins. A bit of time was spent on ways to improve the dashboard and, if you attend tomorrow, you’ll discover that a number of changes were made.
  • Meta Environment: Not a normal topic for us, but a pull request exists that adds translate.wordpress.org to the meta environment so developing for it will be easier.

What’s up for the next week’s worth of work? Maybe some of the things mentioned here.

At the end of the chat we mentioned that we’re on track to start importing plugins in ~2 weeks. Since I’m posting this about a week late, that means next week we plan to begin the plugin import.

#i18n, #l10n, #meeting-notes, #plugins, #stats, #wordpress-meta-environment

Project Updates: Meta Environment, WordCamp Payments, and WPTV

Since WCSF, we’ve made significant improvements to the Meta Environment, launched the WordCamp Payments plugin, and open-sourced WordPress.tv.

Meta Environment

The Meta Environment has seen a lot of improvements since it was introduced in June, especially in the past few weeks.

  • We’ve added developer.wordpress.org, global.wordpress.org, apps.wordpress.org, wordpress.tv, and jobs.wordpress.net.
  • It’s also transitioned from being a full fork of Varying Vagrant Vagrants, to being only the scripts needed to provision the sites into an existing VVV installation, which is a huge win for maintainability.
  • Also dozens of smaller tweaks and improvements.

So far the feedback has all been positive, and I think it’s becoming a useful tool for contributors. props to @netweb, @iamfriendly, and @miyauchi for their contributions.

WordCamp Payments

The new WordCamp Payments plugin has launched, along with the corresponding Payments Dashboard plugin by @kovshenin. These plugins provide a centralized and streamlined way for WordCamp organizers to request payments to their vendors by WordCamp Central, which will save a lot of time over the current method.

We’ve also discussed here, and here expanding the plugins to include sponsor invoices as well.

WordPress.tv

The theme and plugins[1] for WordPress.tv are now open source, thanks to @obenland, and some improvements are already being planned by the WPTV moderators.

It’s also been added to the Meta Environment to make contributing easier.

[1] – Since it’s hosted on WordPress.com, the plugins are bundled in a plugins folder inside the theme, which is the convention for VIP sites.

Get Involved

In addition to contributing to the projects above, there’s been some recent discussions — here, and here — on an invoicing feature for CampTix, which would save a lot of time for WordCamp organizers.

If you’d like to help out, read through the chat transcripts, and then submit a patch to #103 on GitHub.

#updates, #varying-vagrant-vagrants, #wordcamp-org, #wordpress-meta-environment, #wordpress-tv

WordPress Meta Environment

Setting up local development environments to contribute to the Meta sites can be an obstacle for those without access to the private subversion repositories or a sandbox, especially at a meetup or WordCamp contributor day, where time is limited.

We’ve talked a bit before about making this easier by creating a Vagrant configuration, so I put together a prototype based on Varying Vagrant Vagrants, with WordCamp.org as the first site. The sample data needs a little love, but other than that I think it works pretty well.

I’ll test it out with some people this weekend at WordCamp Seattle. If anyone on the team wants to add other sites or make any changes, just let me know and I’ll add you to the repo.

#contributing, #vagrant, #varying-vagrant-vagrants, #wordcamp-org, #wordpress-meta-environment