Hi guys!

I'll have an official blog post up on symfony.com about it, but I wanted to
post about the upcoming doc hunt, which I'm organizing along with WouterJ,
who's taken on a bigger role recently with the documentation. The date is
March 30th, which is a bit soon - but this is our first (but not last), and
I wanted to get it going as quickly as possible.

This is the dev-board, and if any core-devs can spare some time on that
day, it would be great. For you all, we'll be focusing on re-reading some
of the core documents for consistency, accuracy, best practices etc. If you
have some time, you don't even need to make a PR - just proofread and then
offer a list of problems, recommendations thoughts, etc. It's a unique
opportunity to use just a little bit of effort to get more core eyes on the
most important pages.

If anyone has any comments, thoughts, desires to help, let me know! If you
can help on March 30th, just show up - we'll be organized. Below is the
blog post that'll be going up:

Thanks!

------------------------------------------------------------

Title: Symfony Docs Hack Day Needs You on March 30th

Hi guys! It's a great time to be in the world of Symfony! [Symfony 2.2 is
out](http://symfony.com/blog/symfony-2-2-0),
Symfony 2.3 (the first LTS) is [around the corner](
http://symfony.com/blog/symfony-2-2-0#what-s-next),
and we're looking forward to the release of more projects that use Symfony
components, like Drupal 8 and Laravel 4. So far, we have two
big conferences scheduled this year, including [Symfony Live Portland](
http://portland2013.live.symfony.com/),
whose partially-released schedule is already amazing, including topics on
Laravel, security, caching, the HttpKernel and more. See you there!

Beyond all that, there's a lot of real work being done on the core code and
the documentation. The first commit to the Symfony documentation was over
[3 years ago](
https://github.com/symfony/symfony-docs/commit/ff7a1417e62e6ad687c0d7d15c7f239bdad59e84
),
and since then, we've grown to include a full book, lots of cookbook
entries,
and sections for most of the individual components. Almost [500 people have
contributed](http://symfony.com/contributors),
including a group that helps every single day to review pull requests.

But as we grow, we want to stay aggressive and continue to improve the
quality
of the docs. This means ensuring that code examples are accurate and pages
are easy to understand, balancing the info you need with excess technical
clutter. It means adding links between topics so that if there's more
to know, you can dig in. Improving the docs means making entries shorter
when possible, adding missing reference details, and making sure that we're
recommending the best possible solutions.

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 March 30th for our first ever Symfony Docs Hack Day. Here
are the details:

#### When:

March 30th from 9am Central European Time to 5pm Eastern Standard Time

#### Where:

We'll meet on IRC at #symfony-docs on Freenode

#### Who:

Hosts [weaverryan](https://github.com/weaverryan) and [WouterJ](
https://github.com/WouterJ)
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 :).

#### Then What?

Either WouterJ or I will help make sure you have something to do! Our focus
will be:

a) Creating pull requests for [actionable issues](
https://github.com/symfony/symfony-docs/issues?labels=Actionable&page=1&state=open
)
on GitHub;

b) 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;

c) Add documentation for important and missing configuration options;

d) Add missing "options" and form view "variables" to the form field
reference docs.

#### What else!

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.

Cheers!


Ryan Weaver
US Office Head & Trainer - KnpLabs - Nashville, TN
http://www.knplabs.com <http://www.knplabs.com/en>
http://knpuniversity.com
Twitter: @weaverryan

-- 
-- 
If you want to report a vulnerability issue on Symfony, please read the 
procedure on http://symfony.com/security

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to symfony-devs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to