Tag Archives: commit

Andrew Nacin 11:25 am on September 27, 2014
Tags: , commit,   

John Blackbourn is leading WordPress 4.1 (and announcing new committers!)

I’m pleased to share John Blackbourn (@johnbillion) is the release leadRelease Lead The community member ultimately responsible for the Release. for WordPress 4.1. But please hold your applause until the end, I have a few announcements to get through!

WordPress 4.1 will be kicking off at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe this weekend. As noted yesterday, the first meeting will be at 1400 UTC on Monday, September 29.

You’ve probably seen John in action over the years (his first contribution was more than seven years ago). I’ll also add it’s pretty awesome that @simonwheatley and @s1m0nd of Code for the People (a six-person shop) jumped at the chance to donate a large chunk of John’s time through the end of the year back to the WordPress project. (See also this post for more on the release lead role.)

New committers for WordPress 4.1

As many of you know, the lead developers review and appoint new committers to serve each release cycle, often to work on a particular component or feature. This guest commit access comes up for review after each release and can be renewed. I in particular work closely with every guest committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., providing feedback.

I’m pleased to announce our largest guest committer class ever: Gary Pendergast (@pento), Boone B. Gorges (@boonebgorges), Konstantin Kovshenin (@kovshenin), Aaron Jorbin (@jorbin), and Jeremy Felt (@jeremyfelt).

Konstantin and Gary both enjoy diving into internals and getting their hands dirty with tough bugs and regressions. Jeremy will be continuing to push multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site forward. Jorbin will be focusing on testing and tooling. Boone has been working on a set of great improvements to tax, date, and 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. queries, with test coverage to come with it.

These five should be strangers to no one — they’ve all been around the community for years, and not only are they top-notch contributors who embody the project, but they’re generally just really good people.

This will also be John Blackbourn’s third release as a guest committer. I’d also like to welcome back Ian Stewart (@iandstewart), who previously was a committer during the development of Twenty Eleven, and will be back to take the commit reins for the next default theme, Twenty Fifteen.

Scott Taylor (@wonderboymusic) was on fire during 4.0, especially if this terrific post is any testament, continuing a great run. Scott’s WP origin story is pretty great — right as he was getting ready to leave the WordCamp San Francisco 2011 after-party, @koop convinced him to stick around a little longer. We were introduced, and not long after (from the party) his first 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. got committed. A thousand contributions later that have made an indelible impact, Scott is now a permanent WordPress committer. We hope to have him around for a long time.

About a year ago Drew Jaynes (@DrewAPicture) was given commit access to lead the hook documentation effort. This was hugely successful. After the effort was complete, Drew’s role evolved into maintaining all inline docsinline docs (phpdoc, docblock, xref), which has just been wonderful. We appreciate his attention to detail and his dedication to this never-ending effort. Drew is now a permanent committer.

Congratulations to John, Drew, Scott, Gary, Konstantin, Jeremy, Jorbin, Ian, and Boone!

#4-1, #commit, #release-lead

Andrew Nacin 5:36 pm on April 30, 2014
Tags: , commit,   

Helen is the WordPress 4.0 release lead

Mike and I are pleased to pass the release leadRelease Lead The community member ultimately responsible for the Release. baton to Helen Hou-Sandí for WordPress 4.0. I don’t think this will come as much of a surprise to most of you, but please offer @helen your congratulations, which are well-deserved.

We’ve already discussed 4.0 a bit in our last two meetings. Expect today’s weekly meeting at 2000 UTC in #wordpress-dev to be the kickoff for WordPress 4.0.

@DrewAPicture, @wonderboymusic, and @johnbillion have all been renewed for guest commit for 4.0. Additionally, I’m happy to announce that, after more than a year as guest committers, Dominik (@ocean90) and Sergey (@SergeyBiryukov) both have permanent commit access. Their prolific contributions have left a lasting mark on WordPress and I hope to see them at it for years to come.

A release lead, if anyone is curious, determines all important parameters for a release, like schedule, deadlines, which feature plugins are merged, and more generally, scope and goals. They take point when it comes to meetings, shepherding contributions, announcement posts, and updates. A release lead is a connector and facilitator, identifying bottlenecks and friction wherever they may be and at the service of the developers and 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 teams that are aiming to have something in a given release, and be in frequent communication with them.

The release lead should should follow what’s being committed, and set the tone for prioritizing and gardening the milestone on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. Given the constraint of time in hitting a date, help with prioritization and ensuring good communication lines are two of the most valuable things a lead can contribute.

The last five release leads were lead developers, but that’s not a requirement, nor is being a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.. I always thought of my “code reviewer” and “committer” hats as being separate, additional responsibilities. (Helen, of course, also wears these same hats.) Regardless: the release lead has the final call on all important decisions related to the release.

Addendum: For those unaware, for WordPress, version 4.0 sounds like a “big” version number but it’s just another major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. for us, like 3.9 and 4.1, constructed over the same ~4-month release cycle. But don’t tell Helen that! Here’s to 4.0 being awesome.

#4-0, #commit, #release-lead

Andrew Nacin 9:26 pm on December 31, 2013
Tags: , commit   

Commit announcements for 3.9

Lots of news to share! First: Helen Hou-Sandí has had guest commit for the past three release cycles. She’s been spending the last year reviewing contributions, mentoring contributors, and working on some of our larger UIUI User interface projects. I’m proud to announce @helen is now a permanent committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. to WordPress!

We’ve invited John Blackbourn (@johnbillion) to be a committer for the 3.9 cycle. His strong, consistent contributions have been backed by excellent judgment and temperament.

Matt Thomas, who led the dashboard redesign in 3.8 (and 3.2, and 2.7, etc.), will keep his commit to continue to maintain and improve WordPress UI. He’s been a great mentor to many contributing designers and his long-term impact is indelible.

For the last few years, we’ve been granting commit access on per-cycle basis, sometimes for a particular component, feature, etc. Generally, after about a year, a guest committer can be considered for permanent commit access. Dominik Schilling, Sergey Biryukov, Drew Jaynes, and Scott Taylor have all had their commit extended for 3.9.

Drew (@DrewAPicture) was given temporary commit for inline documentation starting with 3.7. He’s been heading up the long-running initiative to document every hook in WordPress. Scott (@wonderboymusic) also started committing during 3.7, and has a particular penchant for digging deep into the query and taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. APIs. And Sergey (@SergeyBiryukov) and Dominik (@ocean90), well, they are forces of nature.

(@aaroncampbell was also given guest commit in 3.7, but he ended up not having much time to use it.)

Here’s a full list of those with permanent commit: @markjaquith, @ryan, @westi, @matt, @azaozz, @dd32, @koopersmith, @duck_, @helen, and me (@nacin); @lancewillett for bundled themes; @iammattthomas for UI. You might have also seen commits before from @josephscott (XML-RPC), @nbachiyski (internationalization), and @mdawaffe (secret weapon for really tricky problems).

Next weekly meeting is January 8. Happy new year, everyone. Here’s to a great 2014.

#3-9, #commit

Andrew Nacin 2:20 pm on April 11, 2013
Tags: , commit   

Please join me in congratulating Dominik Schilling @ocean90…

Please join me in congratulating Dominik Schilling (@ocean90 and on Twitter), who has been given guest commit access for the rest of the 3.6 development cycle.

He started contributing more than three years ago, and his contributions, which number well into the hundreds, are always top-notch. If you’ve had a chance to work with him, you probably noticed at least two things: calm judgment and biting sarcasm. I’ve found that the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. period is his bread-and-butter — he goes around polishing and fixing everything he can get his hands on. He’s also taken one for the team more than once on things like fixing RTL, getting IE to behave, and synchronizing color schemes.

Go, Dominik!

#3-6, #commit

Andrew Nacin 3:26 pm on January 22, 2013
Tags: , commit   

Bug Gardening with Sergey Biryukov (new TV show?)

I’m pleased to announce that Sergey Biryukov has been given guest commit access for the 3.6 cycle.

Ryan, Mark, Aaron and I have asked Sergey (twitter: @SergeyBiryukov) to run bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. gardening efforts for 3.6. He’ll be working on both old and new tickets, clearing patches and fixing bugs.

If bug fixes are your thing, or you come across one of those simple random patches that belong in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., Sergey is your man.

Some three years ago, Ryan sent me a note and asked if I wanted commit, half-joking that he was tired of shoveling my patches into core every day of the week.

Allow me to pass the baton. Sergey’s TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. activity can best be described as omnipresent. He has had many hundreds of contributions, large and small, accepted to WordPress core. His contributions are always thoroughly researched, with links to related tickets and changesets often going back to a previous decade. He writes good code, accepts feedback in earnest, and willingly provides rounds of advice and insight to contributors old and new. He has earned the respect of many and we’re really happy to have him leading the maintenance crew.

With Sergey on bug patrol, you’ll find Ryan and I running the architectural projects this cycle, like slashing, caching, and databasing. Something for everyone!

#3-6, #commit

Jen 4:17 pm on August 17, 2011
Tags: , commit,   

Commit This

It is with great pleasure (not to mention optimism, satisfaction, and many other adjectives) that I officially announce the addition of Jon Cave (aka duck_, or said aloud as “duck undah”) to the WordPress version 3.3 commit team. Duck’s consistently good code, communication skills, eye for security, and tireless efforts made it a natural choice to give him a more official role with this release cycle. Also, @ryan is just sick of having to commit his patches. 🙂

duck_ joins permanent committers @nacin, @dd32, Nikolay, and Joseph Scott, as well as @dkoopersmith, whose 3.2 commit stint has been re-upped.

Congrats, you deserve it!

Jon Cave aka "duck_" at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. SF 2011 — photo by Mark Jaquith

#3-3, #commit, #team

Matt Mullenweg 10:32 pm on February 11, 2010
Tags: commit,   

Another community member has impressed u…

Another community member has impressed us all with his contributions, patience, thoughtfulness, and poetic code: please join me in welcoming Nacin to the commit group. 🙂

#commit, #team

Mark Jaquith 10:14 am on February 6, 2010
Tags: commit   

[12987] creates a post with post_status …

[12987] creates a post with post_status of “auto-draft” when you create a new post item. The first save (auto- or otherwise) will change this to a draft. This means that there are no more negative post IDs. You always have a legit post ID from the very beginning.

#commit

Matt Mullenweg 10:16 pm on January 12, 2010
Tags: commit,   

DD32, whatcha gonna do?

On new commit messages you might start seeing a familiar name, DD32 aka Dion Hulse. He’ll be initially focusing on the areas he’s already contributed a ton to like automatic upgrades and HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands.. He has been a mentor to many and is not scared to jump into any part of the code keeping a positive outlook no matter how far down the rabbit hole he ends up. *cough* WP_Query *cough*

A round of applause for the WordPress contributor with the longest hair. 🙂

One of the goals for the team in 2010 is to greatly expand the number of people with direct commit access, so the emphasis is more on review and collaboration. Right now commit access is tied up with being a “lead developer,” of which we’ve always found a small group of 3-5 works best, but now we want commit to be more a recognition of trust, quality, and most importantly activity, and something that can dynamically flow in and out as their level of commitment (har har) changes and decoupled from the “lead dev” role.

#commit, #team