Discussion

I've been asked to edit the Standard Issue Tags for Drupal core page to correct its characterization of accessibility issues, and, as usual, the editorial eye found more needing to be fixed than it was asked to review.

Specifically in this case, there are cases in which two issue tags are difficult to distinguish from each other. "Accessibility" and "needs accessibility review" is one such instance. Another is "usability" and "needs usability review." The definitions given for these terms don't help clear things up, either.

Before I make sweeping changes, I would like to get feedback from folks who are familiar with the issue queue about a role- and intent-based approach for telling who should — or, sometimes, who may — use any particular tag.

Before diving into this post let me tl;dr: Fostering good communication with new users.

So I asked around on #drupal-contribute to see if there was a guide for helping and guiding users who want to help out with Drupal. There does not appear to be one so here is an attempt to make one. The goal of this discussion is to create an outline which will then get folded into the Drupal documentation for mentoring users. Lets play out a scenario to show where guidelines could help.

A user comes into the irc channel and states they want to help with a project and asks "Where should I start?"

Ariane and I have been getting inquiries lately about whether we can come to various regional events to host a documentation sprint. It's always exciting when people are interested in working on documentation, and we're glad that there is so much interest in sprints -- they are a great way to get some work done and introduce new people to contributing to documentation. But unfortunately, being a Documentation Team co-lead is a completely volunteer position, and neither of us has unlimited travel time or budget (even if the regional camp offers to pay travel expenses).

I started writing an OpenSUSE tutorial for drupal: http://drupal.org/node/1180202

What I want to do is get feedback and develop a template/checklist to follow to make sure no important information is left out of a server config.

So far I have these categories some of which are not written on the above page yet:

<

ul>

Hey Team!

As many of you know, the April pilot month-long sprint has been going really well - several people have stepped up to help out with the issues I'd selected, and 3 of 5 are currently done. A few of us are still sprinting on the two remaining issues, and hoping to close out the sprint on time.

Hey Docs Teamsters!

Not sure if any of you have been following my posts about trying a more agile/sprint-based method for the online docs work that needs to be done - I wrote a bunch about it here: http://groups.drupal.org/node/134909 (And there's a link to my blog post about it there as well).

Hi. After Drupalcon, trying to get my feet wet addressing some doc tickets. I don't have irc at work, so I can't hang out on it. I posted on the doc IRC and contribute IRC yesterday and got no response. So I am getting a little frustrated, because I really do want to help.

Can someone tell me who to talk to in order to confirm this: http://drupal.org/node/1087102

I gathered up some facts, and need to know if they are indeed true and if I left anything out. If the facts are true, how would I edit the page that the ticket refers to. Thanks.

Hello everyone,

I've just had a debate on the issue queue for core about Fast 404s and how to route around the issue of having Drupal be the 404 handler by default. The debate was enlightening for everyone involved I think. But the consequence should be a documentation page addressing the issue and the multiples available strategies for solving it.

Hello,

My name is Anastasia Cheetham. I'm a developer with and the documentation lead for the Fluid Project (http://fluidproject.org). We're beginning the process of restructuring and redesigning the documentation for our Infusion framework. Part of that process will include migrating to a new platform for the creation and distribution of documentation, and we're interested in learning about the experiences of other open source projects, including Drupal.