Drupal NZ

visit my site www.osman.netne.net www. guysex.tk vimeos.tk ...malesex.tk .....

Voting is now open for the 2012 election of at large directors of the Drupal Association. Two directors will be elected from among the ten candidates.

When we designed a new governance structure for the Drupal Association last year, we decided that most of the board is selected through a nominating committee with the goal to carefully balance many factors like needed skills and geographical and sector representation. However, it was also deemed important that we have directors chosen directly by the Drupal community to make sure that the community is always well-represented.

We're holding our first open community elections! Two community "at large" directors will be elected to the Drupal Association Board of Directors, and YOU can get to say who they are!

• Review their nomination profiles.
• Read the notes from the two all candidates' meetings at http://groups.drupal.org/node/207398.

Voting is open to all individuals who registered an account on drupal.org prior to January 18, 2012 and who have logged into that account at least once in the one-year period prior to February 3, 2012.

There is no need to register to vote. The voting system has been set up and prepopulated with the list of eligible voters.

• Log in to this site.
• Visit the https://association.drupal.org/2012-vote page. After clicking through, you will be asked to rank each of the eligible voters, from 1st (top choice) to 10th (last choice). You also need to check a box confirming you're an eligible voter. Make your selections and save the form. That's it!

The voting is done using the "Instant Runoff" voting method, powered by Decisions module. For more about this method of voting, please see this helpful YouTube video which explains it with post-it notes: http://www.youtube.com/watch?v=wA3_t-08Vr0

Yes! Before the close of voting, you can return to the voting form, cancel your previous vote, and submit a new vote.

Tuesday, February 7, 2012 is the last day of voting. Voting will close at 00:00 UTC on Wednesday, February 8, 2012.

When voting closes, a four-member elections team will review the results and post them to this site (association.drupal.org). Results will then be forwarded to the Drupal Association board for ratification.

The election team includes Angela Byron, DA board member; Cary Gordon, DA board member; Nedjo Rogers, DA advisory board member; and Thomas Svenson, Drupal community member who participated in the community process of planning the elections.

We had focused a bit too much on organizing the elections and left finalizing the actual voting system till the last minute. After several community members and Drupal Association staff pitched in, we got the elections system up about 3 hours after the planned opening of voting.

Despite the fact that the voting form lists far fewer, there are actually 270K Drupal.org accounts that fit the voter eligibility criteria. Valid accounts are added to the electorate list when they visit the Association website. These shenanigans are due to the Bakery module, our single-sign on solution, and the requirement to reconcile peoples' Association.drupal.org user IDs and their Drupal.org user IDs.

If you believe you are eligible to vote and try to vote and cannot or encounter some error, please post an issue to the Drupal Association issue queue, selecting "elections" as the component.

• The nominations announcement.
• The elections plan.
• All elections posts.

Drupal 7.11 and 6.23, maintenance releases which fix security vulnerabilities are now available for download.

Drupal 7.12 and 6.24 also fix other issues reported through the bug tracking system.

Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement, more information on the 6.x releases can be found in the Drupal 6.0 release announcement. Drupal 5 is no longer maintained, upgrading to Drupal 6 is recommended.

We have a security announcement mailing list, a history of all security advisories, and an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 7 and 6 include the built-in Update status module, which informs you about important updates to your modules and themes.

Both Drupal 7.x and 6.x branches are being maintained, so given enough bug fixes (not just bug reports) more maintenance releases will be made available, according to our monthly release cycle.

Drupal 7.11 only includes fixes for security issues. Drupal 7.12 also includes bugfixes. The full list of changes between the 7.10 and 7.12 releases can be found by reading the 7.12 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Drupal 6.23 only includes fixes for security issues. Drupal 6.24 also includes bugfixes. The full list of changes between the 6.22 and 6.24 releases can be found by reading the 6.24 release notes. A complete list of all bug fixes in the stable 6.x branch can be found at git commit log.

Drupal 7.11 and 6.23 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

• SA-CORE-2012-001

To fix the security problem, please upgrade Drupal.

We made two versions of both Drupal 7 and 6 available, so you can choose to only include security fixes (Drupal 7.11 and 6.23 respectively) or security fixes and bugfixes (Drupal 7.12 and 6.24). You can choose your preferred version. We are trying to make it easier and quicker to roll out security updates by making security-only releases available as well as ones with bugfixes included. We hope this helps you roll out the fixes as soon as possible. Read more details in the handbook.

The default.settings.php file was changed in Drupal 7.12, to add documentation about PDO attribute override capabilities that were added as a result of #1309278: Make PDO connection options configurable.

The robots.txt file was changed in Drupal 6.24 to block filter tips from search engines. The .htaccess and (default.)settings.php files were not changed in Drupal 6. Additionally, indexes were added to the node_comment_statistics and comment tables, for performance.

The Drupal 7.11 release is only an incremental release off of Drupal 7.9, instead of 7.10, so it is missing bug fixes introduced in 7.10. Discussion is ongoing at #1430404: Drupal 7.11 is missing all the bug fixes from Drupal 7.10.

Drupal 7.12 is also only compatible with Menu Block 7.x-2.3 and higher, and Internationalization (i18n) 7.x-1.4 and higher.

In Drupal 6.24, if you have the contributed user_delete module enabled on your site, the update will fail with a Cannot redeclare user_delete_access() error. An update of user_delete module is being worked on.

In Drupal 6.24 if you had locale module enabled earlier, but it is not currently turned on, the update will fail with Call to undefined function locale_inc_callback(). A fix is being worked on for Drupal core.

In Drupal 6.24 if you run your updates with Drush, you might experience duplicate entry errors in your system table. See the ongoing discussion at http://drupal.org/node/1425868

Elections for at large Drupal Association elections are kicking into high gear with two all candidates meetings this week before voting opens Friday.

Election candidates will participate in all candidates meetings are scheduled over the next two days (Wed., Thurs. or Fri., depending on your location). The first meeting, intended to work for people in the Asia and the Pacific, is scheduled for 01:00 UTC on Thursday. That's 5 PM PST on Wednesday for those in the US and Canada.

The second all candidates meeting at 17:00 UTC Thursday is timed for participants in Europe, Africa, and the Americas.

Then on Friday voting will open. Details on voting will be posted to association.drupal.org.

See the elections announcement for more on how to learn about the candidates.

Just thought you might like to know.
http://www.mittromney.com/

On behalf of The Drupal Association I would like to ask the whole Drupal Community ..

Hunt your hard drives, dig through Flickr, I know there must be thousands of fabulous shots out there.

With a little help from you we can make the official DrupalCon really amazing. See https://www.facebook.com/DrupalCon?sk=photos , not all the DrupalCons are present, and it shows a small glimpse of what happened.

Every photo will have a byline with your name (if you want) as a thankyou.

Please contact me using my Drupal.org contact form http://drupal.org/user/72810/contact

This week there are only a few theme updates: http://opennomad.com/drupal-themes/2012-01-29%20Theme%20updates

Enjoy,

\@matthias

The final session selections for DrupalCon Denver were announced this week. DrupalCon will take place March 19-23, 2012. Get your tickets soon so that you don't miss out on over 100 sessions across 8 tracks! This year we have added tracks specifically for Non-profit, Government & Education, in addition to Community, Commerce, Mobile, Design & User Experience, Business & Strategy, Coding & Development, Site Building, and Core Conversations.

Conference Dates:
March 19 - Pre-conference trainings -- over 16 from beginners to advanced + API Hack-a-thon

March 20 - 22 - Three complete days of 104 sessions starting with Keynotes: Dries Buytaert, Founder of Drupal and Drupal Project lead, Mitchell Baker, chairperson for the Mozilla Foundation, and Luke Wroblewski, digital product leader coming to talk about mobile.

March 22 - Drupal Means Business - included with conference registration to learn how to integrate Drupal into your business.

March 23 - All-day Contribution Sprint -- one of the largest anywhere!

Plus, parties, ski trips, networking, contests and more, all for the $350 conference fee! Thank you to our wonderful sponsors for helping this to remain one of the lowest cost open source conferences around.

Get your ticket to DrupalCon Denver today. What are you waiting for? We want to see you in Denver!

P.S. Conference registration is $350 until February 21 or when tickets are gone! Early registration helps us to plan the conference and keep our costs low by only ordering what is needed. A limited number of 1/2-priced student tickets are still available.

Follow @drupalcon on Twitter or find us on Facebook.

Packt Publishing announces the publication of Drupal 7 Business Solutions by Trevor James and Mark Noble.

• Install and set up Drupal
• Add blogs to attract customers to your business site
• Add customer accounts to your site
• Incorporate e-commerce in your site to sell your products online using Ubercart and the new Commerce modules.
• Integrate Google maps, YouTube videos, and e-newsletter with your site which will help you increase your profits
• Insert online surveys and polls in your site to improve business through customer feedback
• Take care of and maintain your site.

You can use the Drupal 7 content management system to build a small business website quickly. You may add blogs, images, maps, e-commerce, social application integration, and more to your site to connect with your customers and make more money from your business.

Drupal 7 Business Solutions will give you hands-on practical tutorials on how to build a rich and dynamic website for your business quickly using one of the most popular tools in open source.

You’ll start by adding blogs and images to your website. Then you’ll learn how to add a VIP section to your site so that you can give your logged in users special discounts and other VIP freebies. Next, you will learn to send your customers e-mail newsletters and show them a dynamic events calendar.

The book will then teach you to add e-commerce to your site so you can sell your products online. You’ll add YouTube videos and Google maps to help enhance your business site. You will then learn to incorporate feedback mechanisms for your customers.

The book also explains how to maintain your site, upgrade it, and continue adding dynamic content to it.

This book takes a step-by-step approach to building a complete business website using Drupal and enhancing it to include modern technology used by cutting-edge companies. All instructions are written in such a way that they make sense to readers of any technical level.

This book is for anyone who wants to learn how to set up a website quickly for their business using the super powerful Drupal open source content management software.

Trevor is a Drupal developer based in Middletown, MD, USA. Trevor has been designing Web sites for 14 years using a combination of HTML, XHTML, CSS and ColdFusion, and has been using Drupal intensively for over four years. Trevor’s focus is on building Web applications and portals for education, non-profit, medical systems, and small business environments. He is interested in best methods of integrating Web services with Drupal sites; optimizing Drupal site performance, and using Drupal content types, Views, Panels and other contributed modules to develop front end interfaces that support data intensive websites. He loves teaching people about Drupal and how to use this excellent open source content management framework. Trevor authored the Packt book Drupal Web Services, published in November 2010. For more on this title visit: http://www.packtpub.com/drupal-web-services/book Trevor co-authored the Packt title Drupal 6 Performance Tips, published in February 2010. For more on this title visit: https://www.packtpub.com/drupal-6-performance-tips- to-maximize-and-optimize-your-framework/book.
Trevor created an 11+ hour video tutorial series titled Introduction to Drupal 6 for VTC (Virtual Training Company) in 2009. The video is available via the VTC website here: http://www.vtc.com/products/Introduction-To-Drupal-6-Tutorials.htm. He recently produced a Drupal 7 video tutorial course for VTC.

Mark Noble has worked in software development and website design for over 13 years in a variety of capacities including development, quality assurance, and management. He takes pride in developing software and websites to make businesses run more effectively and delights in helping users to get their jobs done more easily.

Mark currently works developing websites to help libraries manage their books. He also does occasional contract work for clients in a variety of industries.

When he isn’t in front of a computer, Mark enjoys playing with his family, photography, and geocaching.

Packt Publishing has graciously offered to sponsor a giveaway of our book Drupal 7 Business Solutions. Trevor will be giving away 1 copy of the book to a random winner who sends contacts us via the contact form on Trevor's Web site. The rules are that you need to submit the Contact form with your e-mail address and a note in the comments box about what you are planning to use Drupal for in 2012. Submissions will be collected for a week from the book's publication date (approximately Jan. 30, 2012). Then one lucky winner will be chosen. Packt will then send the person a copy of the print version of the book (if you live in US or Europe); or 1 copy of the e-version of the book to those who live elsewhere. Again, only 1 copy (print or e-version) will be given out.

So if you want to participate please send a note via the site's contact form here: http://variantcube.com/contact.

You can learn more about the book and it's official release date and download a sample chapter here on the Packt Web site:
http://www.packtpub.com/drupal-7-business-solutions-to-build-powerful-we...

-Trevor James

Drupal.org has over 725,000 registered members in 228 countries. However, only a very small percentage of this members contribute back to the project. Why is this? How can we attract more contributors? What can we do to make it easier for people to contribute? Which areas of the Drupal project would people want to contribute?

To get answers to these questions, two surveys were conducted in 2011 by the community to understand the experience of contributing or considering to contribute to the Drupal project.

This is a combined report of 358 respondents’ responses to the surveys.

The first survey focused on the Drupal contribution experience for the Prairie initiative and received 303 responses. It was written and conducted by Leisa Reichelt (leisareichelt) that ran from April 25, 2011 to September 20, 2011.

The second, the Getting Involved survey, [list of questions] received 55 responses. It was written and conducted by Heather James (heather), Dharmesh Mistry (dcmistry) and Lisa Rex (lisarex) from October 21, 2011 to November 9, 2011. This survey focused on the respondent’s Drupal profile; their expectations, roadblocks, motivations; and Drupal areas that need most contributors, among many other things.

Of the 303 respondents, 64% were non-coders and 31% were non-active contributors.
A big majority (71%) of the respondents from the survey identified themselves as “an established, active member of the community”. The majority of the respondents regularly contribute (41%) and a good amount stated that they contribute occasionally (36%). The majority of the non-active contributors (36%) have never contributed to the project.

The majority of the respondents identified themselves as Site Builder (68%), and/or Developer (59%). A significant portion of respondents identified themselves as Themer (34%) and/or Project Manager (29%). It is also worth noting that 73% of the respondents cited Drupal as their source of income.

Note: Each of the surveys focused on different aspects of Drupal contributions.

The findings from both surveys are summarized below, but also see:

• Detailed analysis and findings from the Prairie 2011 survey
• Detailed analysis and findings from the Getting Involved 2011 survey

From the Getting Involved survey, it was found that the big motivator for people to contribute was simply to improve Drupal and support its community (40%). The other motivator was to grow their knowledge and network (25%). However, when the Getting Involved survey asked about their opinion about the existing community structure, a majority of the respondents (48.9%) had a negative reaction. They thought it was fragmented, chaotic, not great and could use improvements.

The majority of respondents of the Prairie survey thought the experience of contributing was:

• “Very much” rewarding and collaborative: Majority of the respondents of the Prairie survey thought the experience of contributing to the Drupal project was “very much” collaborative (47%) and rewarding (46%). However, the non-coders and the non-active contributors either stayed with “somewhat” or swayed between “very much” and “somewhat” with no statistical significance.
• “Not really” to “somewhat” efficient: Majority thought the process of contribution was “not really” efficient (43%) or “somewhat” efficient (40%) with no significant statistical difference between the responses. Non coders shared the same feeling.
• “Somewhat” intimidating, confusing, unwieldy and supportive: The respondents of the second survey thought the experience of contributing to the Drupal project was “somewhat” intimidating (46%), confusing (49%), unwieldy (43%) and supportive (52%).
• Split between “Very much” and “Somewhat” inspiring, exciting and friendly: When asked about the experience of contributing in terms of inspiration, excitement and friendliness, the majority swayed between “very much” and “somewhat” responses with no significant statistical difference. It is worth noting that in all the four categories (Rewarding, Inspiring, Excitement and Friendly), the majority of non-coders and non-active contributors stuck to “somewhat”.

Respondents of the Getting Involved survey mostly want to contribute on Documentation/technical writing and PHP development/LAMP (54% each). The next area with the most interest is training (46%) and Mentoring/Support (32%).

The respondents thought documentation (12 respondents), Drupal.org. (7 respondents) and Design/UX/Usability (6 respondents) needed the most attention from other contributors.

Although the respondents from the second survey thought the contributing experience was “very much” collaborative, majority (47%) thought “Redesign the issue page to make it easier to collaborative effectively” as a “very important” initiative. Besides that, the respondents (overall, non coders and non active contributors) agreed (47%) that “Redesigning parts of Drupal.org to help newbies find ways to start contributing” as “very important”. This number was higher for non active contributors (55%) than the others.

Across profiles (of the second survey), “Creating ‘team’ pages to aggregate activities and people interested in a topic” (48%) and “Designing better tools for planning large initiatives” (41%) were deemed as “quite important”.

For “Designing a reputation system to show what different people are expert in and how well they are known by the Drupal community” majority of respondents swayed between quite important (32%) to less important (39%). This was also true for non coders and non active contributors.

The major roadblock from they getting involved was lack of information on how to get involved (and whom to contact) (42%). This issue of getting started (48%) was also found in the Prairie survey.

• Lack of information on how to contribute, what to work on or whom to contact (42%)
• Don’t have time (18%)
• “I don’t know enough technically” (16%)
• Intimidation factor (13%)
• Want to talk/need guidance from mentors (13%)
• Slow turn around time to get feedback/or to get committed (7%)

Only 16% of the respondents of the Prairie survey visit the ‘Get Involved’ pages on Drupal.org. 46% of Prairie survey respondents took the opportunity to complain about Drupal.org. They wanted a better Drupal.org. (24%), better tools to collaborate (5%), and an efficient issue queue (5%). For Drupal.org., they particularly wanted to find information easily (4%).

To make the experience of contributing better, non-contributors wanted better information to get started. And the contributors reiterated this when asked what would have been helpful when they started contributing. Besides that, the second most important thing that mattered was the human aspect. The personal touch would have been helpful to the contributors while they were starting and the non contributors want to work with experienced contributors. It is worth noting here that a significant number of respondents are interested in helping with this (Training - 46%, Mentoring/Support - 32%). (Responses from the Getting Involved survey)

• Designers and non-programmers who responded (11) to open-ended question in the Prairie survey complained that contributing to the project was heavily code focused, that designers did not get the credit they deserved, and that they did not know how the non-coders could contribute to the project. Like the respondents from the Getting Involved survey, the non-programmers also reiterated that they did not know where they were needed.
• A small but considerate amount of Prairie survey respondents were discouraged by other community members and slow turn around time (8% each)
• The Getting Involved survey also asked as to what do they expect from a community leader, and they wanted someone who could moderate discussions/issues, offer guidance, and carve a plan for the community.

We hope the findings from the survey will be helpful to the Drupal Association and the community on the next big priorities for Drupal.org. It is evident from the findings that a significant effort is required to provide effective, easy-to-find information on how to get started with contributing to the Drupal community. However, help from other community members is needed to keep the momentum going.

Some conversations/efforts have begun toward this goal of improving the contributor experience, such as redesigning the Community, Support and Getting started landing pages, redesigning the issue queue and more.

We need to identify areas that need leaders, and areas that need contributors. Contributors are in demand for documentation especially.

If you are interested to contribute to this effort to provide better documentation for getting started with contributing, great! There are several open issues on improving Getting Involved content, including the Getting Involved landing page and Getting Involved Guide. Please visit this link to read about other community initiatives that might be of interest to you. If you are unsure where you can best help, please contact Lisa Rex (lisarex), who can point you in the right direction.

If you have any questions about the survey/findings, please feel free to contact Dharmesh Mistry (dcmistry).

Dear Drupal Community,

The DrupalCon Facebook page could look so much better with a little help from you. See https://www.facebook.com/DrupalCon?sk=photos

I have started to upload images from the Drupal Association Flickr account of DrupalCons past, however there are not that many. (http://www.flickr.com/photos/drupalassoc/)

I know many of you must have hard drives full of superb images from DrupalCons, PLEASE PLEASE can you donate some to the Drupal Association for use in the DrupalCon Facebook photo archive.

Why are we doing this?
People new to Drupal can quickly form a good impression of what a fantastic experience DrupalCon is. We are working hard to improve the marketing of Drupal, this is one way you can make a valuable contribution.

How do I send the images?
Contact me, Paul Johnson at pdjpro@gmail.com and we can arrange from there.

Many thanks.

Paul

Just a few updates this week http://opennomad.com/drupal-themes/2012-01-19%20Theme%20updates. The updated new themes are

• async
• cti_flex
• glassical (disabled due to not rendering content fully)
• wedding_bells (disabled due to not rendering content fully)

The following themes were updated:

• journalcrunch
• touchpro (still disabled due to lots of errors)
• tundra

http://opennomad.com/drupal-themes/

Enjoy!

\@matthias

Come one, come all! As of January 18, 2012 nominations are open for the 2012 elections of two "at large" directors of the Drupal Association.

The at large directors are intended to represent the Drupal community. Specifics of the election were decided through a community-based process with participation by dozens of Drupal community members. More details are in the proposal that was approved by the Drupal Association board.

Voting is open to all individuals who have a drupal.org account by the time the elections begin and who have logged in at least once in the past year. These individuals' accounts will be added to the voters list on association.drupal.org and they will have access to the voting.

To vote, you will rank candidates in order of your preference (1st, 2nd, 3rd, etc.). The results will be calculated using an "instant runoff" method. For an accessible explanation of how instant runoff vote tabulation works, see videos linked in this discussion.

Candidates needed! If you are considering running, please head over to the nominations page and read up on what's involved. From there you can fill out a candidate profile. You'll be asked for some information about yourself, like why you're running . When the nominations close, your candidate profile will be published and available for Drupal community members to browse. Comments will be enabled, so please monitor your candidate profile so you can respond to questions from community members.

Elections will be held from January 30 to February 7, 2012. During this period, you can review and comment on candidate profiles on association.drupal.org and engage all candidates through posting to the Drupal Association group. We'll also be scheduling and announcing two phone-in all candidates meetings, where community members and candidates can ask questions and get to know each other.

Thanks and see you at the polls! We'll post another front-page announcement and announce via @drupal on Twitter when we're ready to go.

Hello from Jennifer, your friendly Drupal Documentation Team leader! It’s time for a quarterly update on what’s happening in the Documentation team. As you probably heard, Ariane's role in the Documentation Team has changed, and she is no longer my co-leader (sob!), so I'm looking for a new deputy leader or co-leader (watch http://groups.drupal.org/documentation-team for details). Here's what Ariane and I oversaw in the Documentation Team at the end of 2011, with a look forward to 2012.

• The Documentation Team is holding weekly ”Documentation Office Hours"—one-hour IRC meetings on Tuesday afternoon (North American time), open to anyone for questions and discussions about contributing to documentation. It seems like it's been very helpful to have a definite time when people can get together on IRC, and we plan to continue with this schedule for the foreseeable future.
• In October, I was able to attend the Friday of the Bay Area Drupal Camp (BADCamp). We had a small documentation sprint, and a few people got up to speed on writing API documentation patches. Also, Kathy (kathyh) spent the afternoon writing a new guide for novice contributors to Drupal core, based on her experiences as a novice contributor -- thanks Kathy!
• We started an API documentation cleanup sprint in November, to bring the Drupal 8 and Drupal 7 core API documentation much more in line with our documentation standards (see meta issue). My big hopes for this sprint:
  1. Lots of documentation cleanup -- YES! The sprint is not finished yet, but MUCH more of our documentation is up to standards. In the process, a lot of weird wording has been fixed, and the documentation is clearer and easier to scan. Also, people usually copy/paste an existing documentation header when creating new documentation (or at least use an existing one as a model), so the more we clean up existing documentation, the better future documentation is likely to be.
  2. Lots of participants -- YES! My hope was that some people new to contributing to Drupal API documentation would see the sprint as a good way to get up to speed on making Drupal patches, and on the API documentation standards. And they did!
  3. Build a Drupal Core Documentation Issue Queue Squad -- Yes! Part-way through the sprint, I put out a call for participants to start reviewing other people's patches as well as creating patches, and they did! And now some of them are helping out with the "documentation" component of the Drupal Core issue queue -- watching for new issues, making patches, reviewing other's patches -- which was my secret hope all along (for the last several years, it's been a rather lonely issue queue, since I have had to either write or review nearly every patch in it -- that model is not sustainable, so I'm really happy to have some company).

  Thanks to xjm, xenophyle, sven.lauer, Lars Toomre, aenw, rc_100, jn2, aspilicious, chris.leversuch, barlantz, synth3tk, agentrickard, ... and probably more who joined after I made this list -- sorry if I forgot your name! This sprint is still going on, so if you’d like to participate, visit the meta issue, which has full instructions (novice contributors welcome!).

The last quarter of 2011 saw some changes to Drupal.org that are quite beneficial to Documentation writers, editors, and users -- and more are on the way! Here's a list:

• After much discussion, we came up with an overview plan for how to restructure Drupal documentation into Community, Curated/Help, API, and External Index documentation in September of 2011 (see http://groups.drupal.org/node/175174). During this quarter, we started putting the transformation into place. The first step was a mammoth design issue (190+ comments!) for the Community Documentation (which is a rename of the existing Documentation on Drupal.org in the early fall. The results of that process are partly deployed (read on for details), and more are coming soon.
• One of the main conclusions of the mammoth design issue was that one of the biggest barriers we see to people contributing to the online documentation on drupal.org is reluctance to click the Edit button -- people just aren’t sure whether it’s really OK. So, the redesign of the documentation pages that was deployed in January 2012 included:
  • The existing Documentation pages on Drupal.org have now been renamed "Community Documentation", to reduce the perception that you have to be part of the "documentation team" in order to edit.
  • The page status and other meta-information has been moved to the sidebar
  • At the top, there’s a list of several people who have edited the page, with a clear invitation for you to edit the page.

  Hopefully these changes will help overcome this barrier -- we’ll see!

• We added two taxonomies to Drupal.org documentation pages: keywords and experience level. Right now, they have only been selected on a few pages, but hopefully going forward the keywords will help people find related pages, and the level will help set expectations for the knowledge level needed to understand the page.
• Everyone can now upload images to Drupal.org (issue). Angie/webchick and Daniel/sun made a module that made it safe for people to upload images, and it was deployed in October of 2011. There are followup plans to remove the restrictive Documentation input format from most pages (i.e., to unlock those pages), and to get rid of the Documentation Admin role -- no one should need this role now, since everyone can now upload images and use tables using the default Filtered HTML input format.
• BUEditor was deployed on Drupal.org in October of 2011. This module adds a small toolbar with HTML shortcuts to rich text fields (documentation node bodies, comments, etc.). While this falls short of being a WYSIWYG editor, due to security concerns with existing WYSIWYG modules, this is probably as close as we'll get for the foreseeable future.
• Neil Drumm and Jennifer spearheaded an effort to commit and deploy some updates to the software for api.drupal.org in November 2011 -- thanks to aenw, solotandem, and Greyside for contributing patches for that deployment! If you would like to work on the API module, check out the issue queue (http://drupal.org/project/issues/api) or find jhodgdon in IRC to get oriented. A new deployment to api.drupal.org should be coming shortly, with a lot of user interface updates and more new contributors. Stay tuned!

If you're interested in helping with Drupal documentation:

• New contributors: start at http://drupal.org/contribute/documentation to learn all about contributing to documentation, or come to the weekly office hours (see Events section above) to ask questions and get started. (Jennifer recently edited this whole section, so it should be up to date.)
• Drupal Documentation announcements, discussions, and events are posted on http://groups.drupal.org/documentation-team and on Twitter (@drupaldocs).
• API documentation cleanup sprint (for programmer-documenters): http://drupal.org/node/1310084
• Work on the API module: http://drupal.org/project/issues/api -- the issues are all prioritized, so look for ones with priority "major" for the current priorities. Or pick up any issue you're interested in -- we won't say No to a good patch.

Hi everybody -

Hope you all had a great holiday, and are easing into 2012 nicely! I'll cut right to the chase with this announcement: effective pretty well immediately (as this has been in the works for a little while now), I'm stepping down as Documentation Co-lead.

Awwww, sad, I know! It's been quite the experience, and I feel like along with Jennifer and the other docs enthusiasts, we've gotten a lot done over the course of the last year and a bit of official leadership term. It's been great helping set the direction of the documentation plans, and working with everyone who's been interested in improving the documentation, as well as many of the core and contrib development teams.

After taking some time off in the summer to decompress and figure out where I wanted to go with all of this, I realized that despite feeling like I've been effective in the position, it's taken a lot of my time away from other things in my life, and from actually writing docs and working on other areas of Drupal. And that was definitely okay for a certain timeframe, but it's not something I want to do forever. Now that the Community Documentation infrastructure changes have been rolled out, my side of the leadership role is effectively being put on hiatus. We've talked this over with Dries, and he also feels it's fine for Jennifer to continue managing the API docs and infra solo.

What does this mean to you all? Probably not any huge changes, I'll still poke my head in on the issue queue, IRC, etc. now and then. But my "official responsibilities" will no longer exist, including hosting Documentation sprints, attending meetings and docs hour, doing docs conference sessions, etc. And when I do work on Docs, it'll more often be in a writing/editing capacity. I'm also hoping to spend some more time doing other fun things like patch reviews for Drupal core, and continuing to attend Drupal events. ...And also, spending more time knitting, socializing, doing yoga, and all those other things I neglected while I was spending all my evenings online!

My time helping lead the project's documentation team has had high points and low points, but overall I feel like I've learned a ton, gotten a lot done, and am leaving the state of the docs in a better place than when I started. That's really all I could hope for! Thanks so much to Jennifer for being an amazing co-lead with whom to share a brain, and to all the fantastic Drupal and docs enthusiasts who've made this experience a positive one.

I hope to see the tentative docs infrastructure plans come to fruition during the coming year. This will result in a small team of dedicated core docs maintainers (including myself) taking over the helm of the future "curated" core docs section, and also see docs maintainers appointed for other contrib projects' curated documentation. And of course, work on API documentation and docs infrastructure will continue; Jennifer and other team members have been focused on this for a while now.

Keep rocking the docs folks, thanks for everything, and I will see you around!

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

Jennifer here... I'd like to thank Ariane for a great year of co-leadership! I'm currently planning on staying on as Documentation Team Leader for 2012.

What I'd like to do is take on a deputy leader or co-leader sometime soon (watch http://groups.drupal.org/documentation-team for details and an official call for interest/applications). This way we can have a smooth transition to the next documentation leader, and start the trend of time-limited leadership for positions like this in the Drupal community (to prevent burn-out, let new people have a chance to lead, etc.). Anyway, rest assured I'll still be asking Ariane for advice and help, and I'm excited that she's still excited about being involved in documentation in her new capacity!

Hi All

Could you please explain for campaign monitor module and register

Regards
Selvaraj.C

I've encountered an error (and so has another Drupal developer) when updating to the current version of Acquia's Dev Desktop Control Panel (1.2.40) for Mac OSX.

Upgrading from a previous version to the current version can destroy the Apache configuration settings needed to direct your web browser to the appropriate directory on your local computer. As a result, any existing Drupal installations that you created on your laptop will break. Instead of going to the intended website, you will be directed to the empty Drupal site that Dev Desktop creates upon installation.

The bug will not destroy your MySQL databases or your Drupal code, just the configuration needed to make it display in your laptop. However, repairing the configuration can be time-consuming, especially if you have multiple Drupal sites set up on your local computer. I recommend making a backup of the app or at least its configuration files (vhosts.conf and dynamic.ini) before attempting an upgrade.

You can find a more detailed description of the bug and instructions for how to fix things if your sites get hosed on the Acquia forum: https://network.acquia.com/node/1887722

Wir sind Taiwan Letswin Technology Co., Ltd., wir bieten ein Netzwerk für Dart Maschinen in Taiwan. Wir bieten einen rationalen Preis. Das Gerät hat ein 22 Zoll breiten HD LCD Bildschirm, mit remote battle function. Des Weiteren hat das Gerät eine einzigartige Kartenzahlvorrichtung und ein backstage Managementsystem. Dies schließt auch eine Vielzahl attraktiver Challenge-Speile ein.
Es ist eine brillante kommerzielle Unterhaltungsmaschine! Check www.vdarts.tv.

Hi folks,

I hacked up a module that will wait until January 18th and blackout your Drupal site for the day:

https://github.com/mcantelon/drupal-sopa-blackout

It was developed for, and tested on, a Drupal 6 site although it may work on Drupal 7 as well.

Cheers,
Mike

Three new themes this time: http://opennomad.com/drupal-themes/2012-01-13 Theme updates

• designer_relief
• livethemer_base
• summertime

There were also some updates to the following themes:

• alpine
• bigdaddy
• kanji
• om

http://opennomad.com/drupal-themes/

\@matthias