Drupal Newsletter

A reminder that we have until February 15 for submissions, so we can spend a few days editing and tweaking. Also after that time will be a culling process, where things that are incomplete or not appropriate for this issue will be moved to the March newsletter or deleted. Publication is planned for the 21st.

Thanks for all the hard work!

Aaron Winborn

Hi all!

We are looking for speakers for the upcoming DrupalCon in Boston. Since you are subscribed to the Newsletters group, you might be especially interested in the "Business and Marketing" track (see http://boston2008.drupalcon.org/business-and-marketing-track-descriptions ).

This track covers the following topics:

• The Drupal ecosystem
• Businesses learning to use Drupal
• Case studies
• Showcases: NPO, Education, News, Media, Government, Healthcare

Great work! We published http://drupal.org/newsletter/2008/january and we're ready for the next month. Thanks to all the folks who helped make that ready.

For the next issue, let's get a better structure in place. First, we should make the wiki page for that issue sticky: Robin, or someone with the right access, can you do that? The wiki is http://groups.drupal.org/node/8258 for the February Newsletter.

Ok, been reviewing the most recent newsletter, and writing some notes. I've been mostly going through all the modules, to see what modules we might want to highlight. I think we should only feature a few modules, with a paragraph or two about each, ensuring we're featuring mature, maintained, and moderately useful modules.

Some quick ideas I have for newsletter, after discussion with Alex Urevick-Ackelsberg and Franz Hartl:

• cull the groups for posts for the newsletter
• cull planet drupal for the same reason
• write articles about the effects of drupal in the community and in society
• interviews
• tutorials

more to come. post your ideas too!

Drupal Newsletter Team

The Drupal Newsletter Team shall be responsible for publishing the periodic Drupal Newsletter at http://drupal.org/newsletter. They shall meet using this group, at http://groups.drupal.org/drupal-newsletter. Its members shall be all volunteers who subscribe to this group. Whenever the team calls for a vote, any subscribed member may vote. Unless otherwise stated, any vote shall be conducted with a poll (linked to a motion in another post if required for length), with a duration of two weeks, succeeding where a majority of those voting for a pass/fail motion vote to pass the motion. The results of a vote shall be recorded, and the Team shall ensure that it abides by these results.

Now that this baby's put to bed, I thought we could try something different.

Working with volunteer groups in the past on releasing newsletters, I've had success in getting things out the door when we've set up an editorial schedule.

An editorial schedule lets you:

• identify or highlight certain themes,
• gives anyone interested in writing a list of subjects to choose from or, at the very least, a range of topics from which to start
• helps set the tone of the publication.
• idenitifies more complex topics that might need multiple articles or more extensive research.