@otto42: Can you get rid of the make.wordpress.org/events blog? We pushed it into /community a long time ago, but the site is still there, and people still wind up there and leave comments that no one responds to.
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
Heads up, meta team! We’re getting ready to publish details about the plans for WordCamp San Francisco this October (which includes a mini team meetup), so if you’re thinking of attending, please read the post at http://make.wordpress.org/updates/2014/06/12/wordcamp-san-francisco-travel-contributor-days/ and take the short survey linked at the end of it so I’ll know how many team members to plan for (don’t worry, this isn’t a commitment or anything, I just need to get some rough numbers for budgeting purposes). Thanks!
- Last week we finished triaging the General component.
- This week we quickly went through the Codex component.
- Then we did a quick run through of the Theme Directory component to ensure @Otto42 has a list of things to work on in his rewrite.
- Finally, we looked at the make.wordpress.org / P2 component.
We’d love some feedback on #30. That is, anyone interested in creating better theme preview data, it’d be great to have it submitted to the ticket. There’s a current proposal that could use some feedback as well.
@jenmylo: For #482, will the training team be using their P2 or using the community P2? They’ve been using the community one recently. If they’ll continue to use the community P2, we can wontfix that ticket.
Next week (Friday at 17:00 UTC), we’ll be looking at the Plugins Directory component (I won’t be present).
We did a meta trac triage on Friday.
- @Clorith, @coffee2code, @georgestephanis, @iandunn, @otto42, @samuelsidler attended
- We’ll be doing another meta trac triage exactly a week later on May 16, 2014 17:00 UTC.
- Our focus this time (and next) was on the General component in trac and closing out some of the issues. We made it through about half of the tickets in that component (20) and a handful were fixed.
- @otto42 wants to ask anyone and everyone for help with responsive fixes for WordPress.org (#461)
- A number of tickets need follow up. Some have been assigned so we know who’s on point. I’m taking a number of others.
Those interested, we’ll see you next week!
We’re going to do a meta trac triage this coming Friday at 17:00 UTC (10am PDT, 1pm EDT) in #WordPress-meta. We’ll be steering clear of devhub tickets (the devhub chat is a good time to look through those) and focusing on older tickets. If you’re interested in working with the meta team, join us!
Over the last month, I’ve been making a lot of improvements to Trac, which have been announced and documented on make/core.
At this point, I’ve brought most of these improvements to most Tracs on WordPress.org.
Core, meta, bbPress, BuddyPress, GlotPress, themes, and plugins now all use WP.org cookie authentication, SSL, and the refreshed design. bbPress and BuddyPress received their own skins. These Tracs also all gained image attachment previews, email address syncing, IRC cross-references (for #wordpress-meta, #buddypress-dev, #bbpress-dev, #glotpress, #wordpress-gsoc), and various bug fixes and tweaks. A few other improvements (like comments columns) require Trac report SQL updates, versus template or configuration changes. I’m happy to help the developers on other Tracs to help make their reporting better, something we’re also doing for core.
The meta repository now includes configuration files shared by various Tracs, to shine as much light as possible on everything. These files join MySQL schemas, patches to Trac, a number of template files, a lot of JS and CSS, and even a WordPress plugin.
Notifications are coming very soon to BuddyPress, bbPress, GlotPress, and meta. Probably in the next few days. Once a Trac is running the new notifications feature, that means it has been migrated to MySQL, which means the data is more accessible to the rest of WP.org, as well.
I’m sure I’ll continue to make tweaks to Core Trac in the coming months, but as everything is now shared and well-organized, it won’t even need to “trickle down” — they’ll be deployed everywhere on the first run.
The accessibility team needs a plugin for their site that will allow them to create tables for displaying tabular data/content in their accessibility reports (pages). I know TMCE has a table builder that we could add, but what I’m not sure about is if it creates accessible tables.
1. Getting tables on there at all: better with a plugin that’s already out there, or better to write a one-off that just adds that one thing?
2. Once the options are identified something in place, @accessiblejoe can take a look at the table output to see if it’s accessible of if we need to write an add-on to make it that way.
Talked with @coffee2code about Profiles today.
- He’s going to deploy (and test, and fix any bugs) the profile/buddypress stuff that Mert did during GSoC. At this time only the back-end stuff is going to be deployed, no UI changes.
- Scott is going to install/turn on the plugin(s) to pull Make posts and comments, trac comments, etc into the activity stream to make it more inclusive.
- I’ll work with @melchoyce on new UI for profiles based on my conversation with Scott.
- After the back end stuff is running smoothly, will work on launching UI improvement.
Later follow-up work/projects:
- Bring activity from events (wordcamps, meetups, etc) into the stream.
- Create one .org profile instead of 2 (bring in the support stuff).
- Related: upgrade forums to current bbPress plugin (big standalone project, big implications, but will tie in)
George Stephanis, Xavier Borderie, WordPress › Community Team Update, January 17 « Make.WordPress.Org Updates, and 5 others are discussing. Toggle Comments
Trunk’s current readme does point to 2.6 as the stable tag.
Today, on Thanksgiving, I’m thankful that this is just a minor bugfix point release that slipped out early, and everything that changed in it should be safe and good to have deployed. However, users that upgrade to or install it via their dashboard, or download the zip are still getting told that it’s a beta release, which can certainly scare users.
I’m going to be trying to do whitespace commits to some of the readme.txt files, hoping to glitch it back to being correct again.