Earlier this week, I attended and gave a talk (Motivating Developers to write API Documentation -- based on my experiences with the Drupal project) at the first WriteTheDocs conference in Portland, Oregon. The conference overall was pretty good:
One of the problems that I think every open-source software project faces is how to get new contributors to the project started. It's always necessary to recruit new contributors -- not all of a project's existing contributors will stay around forever, and any project benefits from new people with fresh ideas. But it can take a lot of time from the established contributors to get new people started contributing "the right way" in an established open-source project.
Sometido por jhodgdon el 17 octubre 2011 - 9:59am.
We're having a Drupal API documentation cleanup sprint, to bring the function and file documentation headers up our Drupal 7 documentation standards. If you want to participate, see issue http://drupal.org/node/1310084 for instructions -- new contributors welcome!
Sometido por jhodgdon el 8 septiembre 2011 - 2:58pm.
At DrupalCon London a couple of weeks ago, I was approached by several developers who wanted to do projects that would help the Drupal Documentation team. I had a few thoughts then, but now I have something more organized... If you are a Drupal site builder or a Drupal/PHP programmer, the Documentation team needs your help with the tasks listed here: http://groups.drupal.org/node/174499
At local Drupal group meetings I've been to lately, the big question among those of us who build sites with Drupal is (as you might guess): Is it time to switch to Drupal 7? I can't give you a simple yes or no answer to this question -- I think it depends on your situation, mainly due to the state of contributed modules and some key core bugs -- how disappointing!
There's a lot of energy right now in the Drupal Documentation Team, which is great! My docs team co-lead Ariane has put together a team of dedicated folks who are regularly contributing to the Drupal.org on-line documentation, and their efforts are really paying off in better documentation.
But there isn't quite so much energy in the API/programmer section of the docs team, which I'm in charge of, so I'd like to make a Call to Action. What I'd like to have on the Docs Team:
I'm in Chicago this week for DrupalCon! I'm looking forward to a few days of collaborating in person with the people I collaborate on-line with the rest of the year. I'm also co-presenting as part of two sessions, and participating in a couple of "core conversations", where we'll be discussing what to do for the next version of Drupal and how to do it. Should be both fun and productive!