Wednesday I attended to my first meeting in Making WordPress Slack channel.
It was about HTTPS and there are two goals.
The first one is to look for a way to migrate from an HTTP site without human intervention. The other is about introducing a way to enable HTTPS during installation.
Technicalities apart, what struck me was the tone of the discussions.
There were a handful people talking about a difficult problem to tackle. Even if technical issues were discussed, the focus was on the users. How to make it simple for them to use this feature?
The next time you use an open source software and rejoice about a new feature, think about all the people involved in shipping that particular feature.
Many of them gave their time for free to build that particular thing.
Cover image: “People’s Evening”
Deploying to WP Engine, one component at a time.
In the last months at DriveK, I’ve worked a lot with WP Engine.
WP Engine, for those who don’t know, is a managed WordPress hosting company. They have worked hard on their infrastructure performance and security to give a top-notch service.
If you have a WordPress site, just create an install and forget about all those server related issues. It’s all on their side. You only have to think about your application, your themes, and your plugins.
The flip side of this is that the infrastructure is invisible. There is no concept of VPS, server, physical machine, virtual machine and such. And this means (as of January 2016), no SSH access.
That’s where deployment issues arise.
So, it’s the end of the year once again, and we’re all making our year’s balance.
For me, 2015 is the year I turned from an anonymous WordPress developer to an (equally) anonymous WordPress community member.
I’m writing this three weeks after the inaugural WordCamp US in Philadelphia. It’s been (roughly) just one year after my first WordCamp Europe in Sofia. I attended also to WordCamp Europe in Seville and WordCamp Zürich. And, in the middle of that I helped organizing the WordPress Meetup Milan and the first Italian Contributor Day, back in November.
Now I’m starting to understand what WordPress really is.
I’ve been working with WordPress since 2009, but I’ve never been involved in the community. When you are just user of an open source software, you focus on maximizing what you could get from the software. When you start being involved in its community, you start to switch focus, thinking about what you could give to the software.
So you start translating it in your language. You find a typo in the docs and you fix it. You start to take part to discussions. Maybe you’re a developer working with the software as your day job, and you start to contribute with patches, maybe just a single, stupid line. Or you’re a designer, and you help to improve the UI. In short, you show up. And the WordPress community adhere to the old saying:
decisions are made by those who show up
If something makes you feel uncomfortable, just show up and tell. I think that’s really a good way of doing things.
New year’s resolutions
So what will 2016 be like? Of course, I will be contributing more. As a developer I find really challenging and exciting working on an open source software with so many competent contributors. There’s so much to learn!
And what about WordCamps? Well, I have already purchased my ticket for WordCamp Europe in Vienna, so let’s see if I break my 2015’s attendance record!
Two weeks ago I attended WordCamp Europe 2015 and it was truly an amazing experience. This was my second WordCamp (I was in Sofia last year).
Seville was hot! Trust me, I’m from Naples, Italy, and I know what does it mean when it gets hot in Summer. But Seville…as the taxi driver said: “No June, no July, no August, no September..you should come any other month!”
But it’s truly a wonderful city: one morning I got up early just to get lost walking through the streets.
There is just one word: amazing. The organization was just perfect: two tracks well-balanced, talks ranging all the spectrum, the food was tasty.
But the real value in this kind of (non)conferences is in the people. Don’t go to these events and stay on your own. Talk to the people, try to understand what they do, listen to their experiences and I guarantee that you will return home changed. Among developers and the organizers (thanks, all of you!) I talked, for example, to a retired Australian man who was passing by Seville and used WordPress to help charity associations with their websites!
The Community or “Go Italy, Go!”
This WordCamp was important for another reason. Before this event, the Italian WordPress scene wasn’t in a good shape. But there were a lot of Italians in Seville. So we gathered, talked, and asked for suggestions. Then we planned and:
- we have now a rebooted Rosetta Site1, with a brand new showcase and lots of improvements coming by;
the blog is also rocking, with many news about WordPress being translated in Italian;
and finally, a Slack channel has been created, where everyone can contribute to the Italian WordPress scene.
A new hope
This was my experience at WordCamp Europe 2015. Lots of things happened in a short amount of time, but I’m sure that this year will bring more and more. Stay tuned!
- The international versions of the wordpress.org website. ↩
These are the slides for my talk at WordPress Meetup Milano, May 2015
Questo mese il WordPress meetup di Milano si terrà il 16 Luglio.
Parleremo del recente WordCamp Europe Sevilla e pianificheremo la strada per i prossimi incontri.
Se sei di Milano e ti interessa contribuire alla community di WordPress, vieni a trovarci!
Saremo in via Ludovico D’Aragona 9, presso Drivek.
Finalmente ci sono riuscito!!!! E’ da un paio di giorni che sto cercando (inutilmente :S ) di far rilevare il sito da parte di Google, e dopo aver provato varie strade ( prese dal sito di supporto di WordPress.org ), ho cercato di capire qual’era il problema. La verifica, dopo aver caricato la sitemap in Google, consiste nell’upload nella root del sito un file .html di cui il team di Google fornisce il nome/chiave. In questo modo si può verificare la paternità del sito. Non ho ben capito perchè, anche se WordPress e Google sono a conoscenza di questo problema, non sia stato ancora risolto.