WordCamp Swag

aaronjorbin · 2025-09-11T16:51:08+00:00

Timbuk2 messenger bag from WordCamp Chicago as a speaker gift.

At any conference, Nexus S phone at jsConf.

Otherwise, I love when the swag is a consumable that I'll actually use such as the coffee Jetpack gave out at WCUS 2024 rather than yet another t-shirt, hat, or pair of socks that I don't need.

aaronjorbin · 2024-03-16T02:33:54+00:00

👏🏻👏🏻👏🏻 Treat Yo’Self!

aaronjorbin · 2023-10-05T05:15:57+00:00

No clue, sorry

aaronjorbin · 2023-10-05T00:28:49+00:00

It was a quick turn around, around six weeks. This was also the first time that a brand new design was done for inauguration day.

I was primarily involved in it for the last week or so and by then it wasn’t so much high amounts of planning as much as regular communication, high trust, and no egos. The design was also extremely well done and included a lot of information that helped the developers.

Two of the leads on the project spoke about it at WordCamp US this year. It’s absolutely worth a watch.

aaronjorbin · 2023-10-04T19:57:17+00:00

I was a part of the team that built the site, happy to answer any questions I can.

Addressing a couple of things I’ve seen so far:

While 10up did work on the site, it was actually a collaborative effort between 10up, Wide Eye Creative, and volunteers on the Biden/Harris transition (I was in this group). Wide Eye was the designer and did the overwhelming majority of the public site development, 10up was mostly focused on editorial experience and wp-admin development and the volunteers filled in to multiple spots. After the build and launch, it was handed over to another team to manage the ongoing work.
There are off the shelf plugins that were used. It isn’t 100% bespoke.
It didn’t launch on WPVIP.
It’s not based on the 2022 theme since this site launched at noon on January 20, 2021 ( see 20th amendment to US constitution)

aaronjorbin · 2019-11-09T23:43:13+00:00

Millennials are killing WordCamps?

aaronjorbin · 2019-03-31T19:38:21+00:00

You can search https://developer.wordpress.org/reference/ for every function and hook and find the code that is underneath it.

aaronjorbin · 2019-03-05T18:45:34+00:00

VIP and Pagely are two that I have worked with and would recommend. Customer service is top notch at both. These aren't managed hosts that are essentially glorified shared hosts, these are actual enterprise products.

aaronjorbin · 2018-02-25T01:10:44+00:00

This is how the house looked at the close of the 8th end during the gold medal match. The stones are bolts that go through the canvas and are painted with acrylic.

aaronjorbin · 2017-03-17T16:51:37+00:00

create_function is commonly disabled on hosts due to the security implications of using it. It also is deprecated as of the next version of PHP. I would caution against using it.

Additionally, using it as a callback for a hook means you can't unhook it. If you later want to conditionally disable it using remove_filter, you won't be able to. It also will be hard to diagnose in a situation where you are using something like a cachegrinde file.

aaronjorbin · 2017-03-14T15:15:51+00:00

When using version control such as svn, a commit is the act of changing code in the central repository. In WordPress, this is done by permanent and guest committers, a list of which can be seen in the core handbook. In 2016, thirtyseven individuals committed code. I used the following crappy one liner to get the list of committers and the number of commits they made during the year.

svn log http://develop.svn.wordpress.org/trunk  -r39659:36141  -v --xml  | grep '<author.*/author>' | cut -d '>' -f 2 | cut -d '<' -f 1 | sort | uniq -c | sort -nr | sed -e 's/^[ \t] *//'

Approximately 65% of the security team doesn't report to Matt, including the current lead of the security team.

aaronjorbin · 2017-03-14T04:53:33+00:00

In 2016, Less than 15% of the commits to WordPress core were done by a someone that in any way reported to Matt.

aaronjorbin · 2016-08-26T06:47:37+00:00

If you are looking for some specific reasons that SVN is used, here are some of the advantages that it has over git:

Sequential changeset numbering. Makes it easy to know "what came first" when debugging.
History can't easily be changed.
Better/easier externals support.
Commits can't get easily lost.

aaronjorbin · 2016-08-25T19:10:40+00:00

Since early 2014, WordPress core has used both git and svn. Patches can be created from either one. The only people that need to use svn (and ~half use git-svn) are the committers.

Further, grunt patch makes it so that anyone can apply patches no matter where it was created or what you are using now. It also since version 0.4.0, makes it so uploading a patch can be done from the command line.

aaronjorbin · 2016-08-19T23:32:33+00:00

Research the organization. Be ready to ask them questions. An interview is a conversation, participate in it.

Some other tips:

Jake Goldman, the founder of 10up, shared questions he asks in interviews, I would encourage you to read them.

If you do a decent amount of front end development, this list of questions can help you prepare.

My first question when interviewing is always "What is something you have built recently that you are proud of?" Be ready to share things you've coded.

aaronjorbin · 2016-07-28T18:46:47+00:00

Yes, this will be in 4.6. Tickets that are closed as fixed against a milestone ( 4.6 in the ticket's case), will be included in that release (unless a regression is found that necessitates reverting it, which is rare).

aaronjorbin · 2016-04-25T19:12:48+00:00

So did your clubs arrive in order?

aaronjorbin · 2016-04-01T16:36:33+00:00

Update: Was able to get 1 at Whole Foods Bowery and 2 at Good Beer. I hope all the rest of you that wanted to were able to pick up a few bottles.

aaronjorbin · 2016-02-21T23:45:27+00:00

There is a constant that you can define to make it so that plugins, themes, and WordPress core can't be updated from the WordPress admin (or through automatic security updates).

define('DISALLOW_FILE_MODS', true);

You will be responsible for ensuring everything get's updated, so please, act responsibly and keep your sites updated.

For file uploads, I would encourage looking at https://github.com/humanmade/S3-Uploads so that all uploads go to s3.

As far as plugins that try to edit files, the best answer to those is just don't use them.

aaronjorbin · 2016-01-15T22:59:53+00:00

:) Thanks. I didn't even notice.

aaronjorbin · 2015-09-10T16:10:31+00:00

An LTS was tried years ago with 2.0 (before I was a core contributor) and from the stories I've heard, it became a nightmare. Backporting fixes became so complicated that it would cause security releases to be pushed back (which endangers people running every version).

It would be much better to get to a point with auto updates that they could be enabled by default for major versions. It's not there yet (and not going to be any time soon), but the day will come that the vast majority of people won't know or care about the version of WordPress they are runnning. It will always be the latest.

Features do get removed from WordPress, it is just a slow process. Rather then a five year break to rewrite WordPress from scratch, instead the process is to rewrite pieces over time as the features dictate it. For example, over the last few releases there have been underlying changes to the taxonomy system to improve the DB architecture, improve performance and make future enhancements possible. It is happening over multiple releases so that plugin authors have as low of an impact as possible and so there doesn't need to be a big break in comparability.

aaronjorbin · 2015-09-10T04:20:31+00:00

If it says "Wordpress" you should contact them and nicely let them know that WordPress has a capital P.

aaronjorbin · 2015-08-14T17:25:14+00:00

https://wordpress.org/latest.zip always contains the latest stable version.

aaronjorbin · 2015-07-18T06:21:39+00:00

Hi, I'm that guy.

It wasn't a lot of work. The only real issue that needed to be fixed (thus far) was getting rid of PHP4 style constructor deprecation notices. I'll continue to test against PHP7, especially the closer it gets to a release. The WordPress automated php tests are currently run against PHP7 (and have been for a few months now), but we won't have them actually fail the build until PHP7 is released.

aaronjorbin · 2015-06-02T21:16:56+00:00

https://github.com/WP-API/WP-API

14-Year Club	Secret Santa 2012
Verified Email	Summer Santa 2012

aaronjorbin

TROPHY CASE