Team Update: XML-RPC – Taxonomies and Terms

Team Update: XML-RPC (Friday)

We finished our first cycle last week and the implementation of the CRUDCRUD Create, read, update and delete, the four basic functions of storing data. (More on Wikipedia.) functions for Posts (and all Custom Post Types) has been committed to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. see #18429 for more info.

For our second cycle we decided to focus on CRUD for Taxonomies and Terms taking the patches from GSOC and iterating on them we are using #18438 as the tracker ticker for a single patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to cover all the different methods.

We also decides to put more focus and effort into unit testing this cycle and have started creating some XML-RPC test case for existing/new functionality.

Relevant Tickets: #18438, #18439, #18440, #18441, #18442, #18443, and #18444

Office hours: 5pm-6pm UTC Mon-Fri

#team-update

Team Update: Gardening

  • duck_ finished the rewrite tickets that were in our sights and moved on to import/export.
  • The WP_Query improvements might land soon (#18536). I want to do some more testing with memcached first.
  • The ajax code reorg is done (#15327). A few variable scope related bugs were fixed. Unit tests added.
  • post_content_filtered is now the same size as post_content (#19387). Rejoice. I think this concludes the schema changes for 3.4.
  • Review, test, commit, and pinch hit for other teams.
  • Profiling of various adminadmin (and super admin) pages, looking for slow things.
  • And the usual gardening activities. The winnowing is slow but steady.

Coming up:

  • Land WP_Query changes
  • Import/export
  • More unit tests
  • Particularly autop unit tests. Anyone?
  • Pick a couple of new components to ticketticket Created for both bug reports and feature development on the bug tracker. target. Suggestions?

#team-update

Team Update i18n Our first two week cycle…

Team Update: i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

Our first two-week cycle comes to a close. Very successful, with more than 20 tickets outright closed, and more in the pipeline or nearing completion. Some highlights since last week’s update:

  • Fixed localization issues when a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party calls wp_enqueue_script() too early. #19959, #11526
  • Fixed ajax calls for IDN domains (broken in IE and Opera). We partnered with Ryan on this one, to introduce a new ‘relative’ scheme for the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org functions. #18952
  • Hebrew letter nun no longer breaks search results. (Good UTF-8 fix.) #19033
  • We finished off #19852 and, again, #18180, #19924, and #19600
  • Commas (when used to separate tags) were internationalized. A very helpful fix for a number of locales. #7897
  • Finalized RTL styling changes in #19598
  • Made the TinyMCE spellchecker dropdown localizable #19962
  • The document for translators is current (view it here)
  • Awaiting feedback from translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. teams in #19980, #8759, and #19601
  • Ryan and I want to revisit #19599

Our next cycle will start in a few days. It will focus on the raw implementation of language packs. Dion will be spearheading the upgrade/install bits while I continue to work on infrastructure as well as the contents of said packs. For now, Sergey is looking at transliteration and character conversion, while I will work on #19597 and #15858.

#3-4, #i18n, #team-update

Team update: Browsing Buddies

Current Cycle Focus: Themes Screen Infinite Scrolling (#19815); ends this Thursday, 2/9

This week we talked a bit about the UIUI User interface/UXUX User experience of it all and decided to hide pagination links if infinite scrolling is on. Latest patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. on the ticketticket Created for both bug reports and feature development on the bug tracker. also moves the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. into the existing theme.js. Discussed with rboren and decided to raise the per_page number on the installed themes screen to something high (999 in the current patch, or in essence, everything). Related: #19469

With the commits of patches for #18094 and #19853, search filters and the details link are now fully functional with infinite scroll. DH-Shredder is working on the display of the spinner, and a refreshed patch should be up on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. before tomorrow’s dev chat for review and more eyes, especially on the JS. Looks like we’re on track to finish this cycle on time.

Next up: Multiple screenshots for themes (#19816). Comps still wanted over at Make UI.

#browsing-buddies, #team-update

Team Update: Twenty Twelve

We are the team formerly known as “Twenty Twelve Two”—now three strong with Drew Strojny joining up for the 3.4 release cycle as the theme designer. Welcome Drew!

What we’re calling our “first cycle” ends today with Drew delivering us the first working prototype with the basic layout in place. Matt committed it with r19842. (See also #19978.)

Consider this version 0.5

This is not yet a fully working theme—we’ll be adding in more features and lots of missing styles over the next 3–4 weeks. Including post formats, comments, archives and page templates, more in-post styling, and a nav menu rework so the main content comes ahead of the navigation.

Our goal for the next cylcle is to finish up all the missing visual styles from Drew, with Lance making relevant code changes as needed. Deliverable is a finished theme that everyone can start using and testing in earnest.

Schedule notes

1. Due to schedule conflicts we need to be going slowly over the next week or two, picking it up again in earnest Feb 20–Feb 29.
2. Office hours will probably be on Mondays, I’ll post the actual times soon.

Update: We’ll end our cycle on Feb 29th.

#bundled-theme, #team-update, #twentytwelve

Team Update Bugs RPC Realized this morning that…

Team Update: Bugs-RPC

Realized this morning that we totally missed our Friday update, so I’m posting it now.

Went over every ticketticket Created for both bug reports and feature development on the bug tracker. on our list for this cycle. All but two (and possibly a third) look commit ready. We’ll have a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev give those a quick look. If that all passes then I’ll plan on committing them. Beyond that we’ll look at other two or three that need a bit more feedback and try to get them commit ready and in this cycle.

#bugs-rpc, #team-update

Team Update XML RPC Friday We made great…

Team Update: XML-RPC (Friday)

We made great progress this week continuing our focus on the major ticketticket Created for both bug reports and feature development on the bug tracker. for implementing wp.newPost (#18429) and working to keep the other bits of this APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. supporting the same formats. Our 2 week cycle ended on Friday and we are really close to having a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. ready for commit but didn’t quite make it in time. The team are continuing work on the patch and will re-group on Monday to review progress and plan the next cycle.

Relevant Tickets: #18429, #18430, #18431, #18432, #18433
Office hours: 5pm-6pm UTC Mon-Fri

#team-update

Team Gardening Update

Decided to allow small schema changes in this release so as to clear out some of the schema updates we’ve long considered.

  • #19935 – Drop comment_approved index. It has been redundant for a long time.
  • #17188 – Remove blog_id column from wp_options. It has never been used.

We’re also considering:

  • #19387 post_content_filtered should be longtext
  • #10483 – Change post_name’s length from 200 to 400

kurtpayne modified the ajax handlers to use wp_die() — allowing unit tests to provide a custom die handler — and added more ajax unit tests. #15327

duck_ continued with rewrite improvements: #19876 #16092

scribu continued with work on WP_Query performance in #18536. The results look promising.

And there was the usual tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. gardening, unit testing, and housekeeping.

#team-update

Team Update i18n Technically our cycle started today…

Team Update: i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

Technically, our cycle started today. Really though, a few of us have been hammering away at a pre-cycle cycle for the past week or so. What we’ve been doing is focusing on bugs and enhancements, some of them quite old, that will provide more targeted control to translators.

Since Dion is back in action starting next week, we’re back-dating our current cycle, if you will, to have started on January 23, and end on Feb 6. Soon thereafter a new cycle will begin, and that cycle will focus on the development of language pack installation. This cycle will continue to lay the groundwork for that to happen.

Things that have happened so far:

  • Created a document for translators, Important Changes for WordPress 3.4, which outlines all of the changes (audience: translators) what I’m about to outline for you (audience: developers).
  • Worked with Gardener Boren on splitting up the pot files and only loading adminadmin (and super admin) strings in the admin. This required some work on GlotPress, WP.org, the i18n repo, and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. #19852
  • RTL locales are now automatically detected. #19600 and #19924
  • wp_salt() now falls back to the database for all keys and salts, and is much smarter about when it should fall back. The way we handle default secret keys is now improved and will prevent pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party errors when running a localized version of core. #19599 #14024
  • wptexturize() now has better localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. support for all kinds of curly quotes/apostrophes/primes. This means that a localization like Hebrew can actually turn off curly quote replacement, without needing to resort to weird hacks in their he_IL.php file. #19602
  • RSS feeds now properly reflect the language of the blogblog (versus network, site). The rss_language option is gone. #13440
  • Locales can now specify a default timezone and start of week through translated strings (rather than PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher). Also, default links can be localized, #19601
  • setup-config.php nows use a regex to replace wp-config-sample.php placeholders, preventing translators from needing to keep the placeholders sync’d. #18180
  • The non-gettexted WP_I18N_ strings are all gone. Core now leverages wp_load_translations_early(), which is carefully designed to work in the particular situations we need it. (Not for plugins, yo.) #18180
  • setup-config.php is now fully internationalized and uses wp_load_translations_early() to ensure the local package’s mo file is loaded. Between this and the secret key changes, there is no longer a file in wp-admin or wp-includes that translators need to modify in their distribution. #18180
  • Like the gardening team, we have been using Future Release and Awaiting Review as a potential gold mine, picking through all of the i18n tickets to find the good enhancements and missed bugs. So far, this has resulted in fixes for #19364, #11270, #18770, #19698, #19788, and a few other tickets now slated for 3.4.

Things that will probably happen in the next week:

  • Some decision on support for RTL in feeds. #6425
  • Word count work. #8759
  • Comma fun. #7897
  • Finishing off locale-specific modifications in core. #19603 #19601
  • Themes gaining headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. abilities, and translating page template names. Sergey is going to work on this and I’ll follow up with the makepot.php changes. #15858 #6007
  • And other things on this report, as well as other aspects of laying the groundwork for language packs.

Office Hours: Daily. We will likely set formal office hours for the second cycle as that will include me, Dion, and Sergey, and we’re evenly spaced around the world (UTC -5, +4, +10).

#3-4, #i18n, #team-update

Team Update – Headerators

We focused on flexible headers this cycle (#17242). We have a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. that we think is ready for commit, which adds flexible height and width. We had Nacin and Mark Jaquith look at the patch, they made some recommendations that we integrated, and it seems ready to go into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for some testing.

You can test with the latest version of the Essence Theme on Github or see comment 48 on the ticket for information on how to add support to your own theme.

#headerators, #team-update