Symfony Docs Hack Day Needs You on May 23rd
Ah, spring - a time of flowers, sunshine and hanging out with your open source friends online! Yep, I'm talking about this year's first documentation hack day on Saturday May 23rd.
It's been a really busy year so far - Wouter began posting monthly Documentation blog updates and January was a record-breaking month for the total number of pull requests merged.
But the number of issues and unfinished pull-requests has been creeping up, and we're putting an ever-greater emphasis on making sure that all our docs are up to date, relevant and easy to understand.
And this is where we need your help! Whether you're a seasoned-Symfony veteran, a beginner, or even if you don't think your English is very good, we'd like you to join us on May 23rd for our Symfony Docs Hack Day. Here are the details:
May 23rd from 9am Central European Time to 3pm Eastern Standard Time
We'll meet on IRC at #symfony-docs on Freenode
Hosts weaverryan, WouterJ and xabbuh along with you and all your friends. The Hack Day is for everyone - we need Symfony experts and newcomers. If you're newer to Symfony, you give us a fresh look at the documentation!
And if you're not comfortable with the contributing process, it's no problem: the docs are a great way to start contributing, and we're all very nice and helpful :).
One of us will help make sure you have something to do! Our focus will be:
a) Creating pull requests for actionable issues on GitHub;
b) Adopting existing pull requests where the original contributor is too busy (it happens, no worries);
c) Re-reading certain core documents for accuracy, links that can be added, ease-of-understanding, consistency, and to see if entries can be broken into pieces and made shorter;
If you have any questions, thoughts or suggestions about the documentation or any of this, just drop a comment below. If you're reading this, then you're probably a Symfony user, so the docs are for you, and we like you.
Help the Symfony project!
As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.