SEO Expert Blog

What is Simple Field? The Simple Field module provides a simplified UI for creating Fields. The primary goal is to make it easier to allow non-powerusers to administer fields without necessarily giving them access to the entire core Field interface. Simple Field also allows for more fine-grained control of what types of fields users may create, and what field settings they have access to. The module can separate the process of field creation from the process of field instance creation. This allows admins to create pre-defined fields, and then allow other users to add the fields to entity types without the complex UI usually associated with adding field instances. API Simple Field simplifies the Field UI by making use of default Field settings, overriding defaults in code and only allowing modification of specific field settings. To accomplish this, Simple Field defines it's own 'types' that encompass both field type and widget type settings, and any custom types must define forms for editing values they wish to override. For information on creating new types, among other things, take a look at the documentation. Todo Submodule for defining new Simple Field types in the UI Dependencies Entity Ctools (for Simple Field Modal submodule) Sponsorship The project is sponsored by Evolving Web.

---

This is a port of http://drupal.org/project/form_beautifier to D7. Three new settings have been added: In-field labels. Using the jQuery In-field labels plugin. Inline labels. Adds CSS to make labels appear inline with a 10em left-margin. Drop-down checklist. Using the jQuery DDCL plugin used in the sexy_exposed module. I mostly use these three plugins and have not thoroughly tested the other plugins that were a part of the D6 version of form_beautifier.

---

Expose voting API methods as a service resource. Development starts from initial code posted in http://drupal.org/node/241453.

---

This module implements power of Debugging tool from Nette Framework. Installation To get Nette Debbuger fully worked, download library from http://files.nette.org/NDebugger.zip and extract it into sites/all/libraries directory. Usage Type $stop(); in a place of code where you wan't to stop your script and display informations. Example:function node_type_get_base($node) {  $type = _node_extract_type($node);  $types = _node_types_build()->types;  stop();  return isset($types[$type]) && isset($types[$type]->base) ? $types[$type]->base : FALSE;}

---

I knew the moment my laptop didn't wake from sleep mode something was amiss. Having retired to my office safe haven for the evening I just wanted to wrap up a few items, log my time and call it a night - the basic end to any Drupal developer's day. My Macbook, however, had other plans. It was the quintessential nightmare for those of use who live on our computers, a dream we often visualize as worse-case situations but often do nothing to lessen the pain of actualities: a complete computer crash with limited hope of a reboot. But despite the Macabre vibe usually surrounding such thoughts, it's something that doesn't always have to be the ultimate disaster. 

---

Add some intelligent date formatting based on start and end dates.

---

Makes it possible to use the Feeds module to import data from a MongoDB database.

---

A MongoDB backend for Views. Based on the module of the same name in Chx' sandbox.

---

img.right {float:right;clear:right;padding-left:1em;padding-bottom:1em;} img.left {float:left;clear:left;padding-right:1em;padding-bottom:1em;} h2, h3 {clear:both;padding-top:10px;} While this article focuses primarily on the state of Drupal “contrib” (modules and themes which are not part of the “core” Drupal download), it also takes a look at the greater “State of Drupal” in terms of sites known to be running on some version of Drupal, comparisons of the rate of uptake after Drupal 6 and Drupal 7 release, and a small case study involving attempting to perform a “major upgrade” from Drupal 6 to Drupal 7 on a site using a significant number of contributed modules. The recent history of Drupal core usage As a starting point, I think it is helpful to look at the recent history of Drupal core usage and compare the uptake of Drupal 6, after its release, with the uptake of Drupal 7. On June 22nd, 2008, when Drupal 6.0 was released, there were already significantly more sites using Drupal 6 than Drupal 5 (almost 32,000 on Drupal 6 vs almost 17,000 on Drupal 5). Both core versions of Drupal steadily gained users for a time, with Drupal 5 reaching a peak of about 24,000 sites about 7 months later, but by that time Drupal 6 was running on more than 100,000 sites. By late July 2009 (a similar point to now in terms of months after the major version release), Drupal 5 usage had dropped to about 20,000 sites and Drupal 6 was running on more than 160,000 sites; more than eight times as many installations. Since then, Drupal 5 usage has tapered to about 7,000 sites; a bit more than 1% of total Drupal usage (please note: it’s likely that many of the existing Drupal 5 sites do not report usage back to Drupal.org). Now let’s look at the usage of Drupal 6 and Drupal 7 since the time of Drupal 7’s release. Drupal 6 peaked with about 355,000 sites, shortly after Drupal 7’s release in January 2011. At that time Drupal 7 was running on about 24,000 sites, a fraction of Drupal 6 usage at that time. Since then, while sites running on Drupal 7 have steadily increased to their present values, about 280,000 sites, Drupal 6 has hovered around the same value, drifting between about 320,000 and 350,000 sites, but not yet significantly dropping. Almost 13 months after Drupal 7’s official release, we still have more sites running Drupal 6 than Drupal 7 (and I suspect that a significant percentage of the Drupal 7 sites are in development rather than production). But what does this really say? Let’s look a bit closer at the numbers and trends: Note: I banged this graph out in Excel since the Google chart of Drupal usage, normally displayed on project pages, seems to fail as “too large to process” for “core” usage statistics. Drupal usage has grown by leaps and bounds since Drupal 6’s release. In June 2008, there were fewer than 50,000 sites using Drupal 5 and 6 combined. Now, a bit more than three-and-a-half years later, there are more than 615,000 sites running on some version of Drupal — more than a 12-fold increase in that time period! A year ago, this figure was less than 400,000, so Drupal 7 sites make up a large proportion of the more-than-200,000 Drupal sites added since then. The growth was steeper after Drupal 6’s release, but we still did not have 200,000 sites, total, by July 2009. In any case, it’s safe to say that for most use cases, we have the modules necessary to build a good site based on Drupal 7, so if you are hesitant to use it, don’t be. There are many great advantages to Drupal 7 and with the continual improvement of the contributed modules, we should probably build new sites on Drupal 6, only if modules critical to the use case are lacking for Drupal 7 (or if the “new” site is another site in an existing Drupal 6 “multi-sites” installation). Even if a “critical” module exists for Drupal 6 and not yet for Drupal 7, it may still be worth building the site on Drupal 7 if you have the coding experience to port the Drupal 6 module to Drupal 7, which would help alleviate the current issue that many significant modules are not yet available for Drupal 7. State of Drupal 7 contrib (modules) Good news: Almost all “Top 100” Drupal 6 Modules are ported to Drupal 7 The good news, especially for site builders creating a new Drupal 7 site, is that most of the top 100 modules are ready for use on Drupal 7. Nine of them are redundant (now included in “core”), 43 have “stable” releases, 23 have beta or RC, 11 have an alpha release, and 9 are in “dev” status, while a couple others recommend using another module which performs similarly. read more

---

Ubercart currency module used to support multi currency when place orders.

---

If you have a test and a development instance and use drush sql-sync then you often have the problem that you have different paths on the test and on the dev environment. For example if your test environment has:/sites/site.test.com And your dev environment has:/sites/site.dev.com Then you are likely to get a lot of error messages (possible even fatal ones) that drupal can't include particular files because of broken paths in system/registry tables. This extension to drush sql-sync uses the sanitize hook to perform some additional cleanups.

---

jQuery GPS provides a user interface for jQuery GPS Library.

---

We now have an official Media Support Squad to keep the momentum for the Media Initiative at he high pace. First task is to help getting a stable Media 1.0 released. Read on to find out more and how you can enlist to become a squad member.Tweet Widget Google Plus One Digg Smart Button Share on Facebook

---

We wanted to bring to light a change that we made a few weeks ago; the switching of our SSL certificate away from GoDaddy. As an Association that supports an open source project we did not want to continue to be aligned with an organization that at any point would support such devastating legislation. The SSL certificates have been moved over to Namecheap because we value their commitment to the Electronic Frontier Foundation (EFF), their stance against SOPA, and their position on keeping an open web.

---

Custom expandable menu block (CEMB) provides a sitemap like block that shows the customizable structure of a menu.

---

There have been plenty of articles about Drupal 7 and entities already. Entities are great. They provide a unified way to work with different data units in Drupal. Drupal 7 is all about entities. They are everywhere: nodes, users, taxonomy terms, vocabularies... Let's take a closer look at how developers can create their own entities using the Entity API module, which is a great toolbox. read more

---

Field group multiple extends the field group module displays and widgets by multiple functionality

---

This module provides number of count to be shown in footer if pager is implemented in view's display.

---

I'm running for election as an "At Large" board member of the Drupal Association. "Meet the candidates" forums were scheduled so members of the Drupal community could ask questions of the nominees.  We were all asked to do a brief introduction, then respond to questions either by voice, or by IRC, and then were all asked to make a final statement.  Rather than adding to the already lengthy wiki summary of the candidate meetings, I'm posting the edited version of my responses here instead.  See the full IRC transcript, and others summaries here: http://groups.drupal.org/node/207398 My formal candidate statement is here: https://association.drupal.org/node/14388 Further information on the election, as well as details on voter eligibility, and how to vote is here: https://association.drupal.org/2012-elections-voting General Intro I'm in Melbourne, Australia. Run my own small business, called creative contingencies. Been using Drupal for about 5 years. I'm really passionate about open source and the fact it enables people to do things they would not otherwise be able to do. In terms of Drupal and the Drupal association, I'd like to be a voice for the 'small voices'. Small drupal shops, amateurs, hobbyists, non-profits, students and tinkers. Sometimes we get caught up in the commercial opportunities, and forget that Drupal has been an enabler for many people that aren't using it to make a living. It's important the Drupal Association develops a more global perspective, and that we work together to invite and embrace more people into the Drupal community. I just helped run Drupal Downunder in Melbourne a couple of weeks back, it was a great success, and like many other camps around the world was driven by the local community to fulfil a need that can't be filled by DrupalCon, because DrupalCon happens on the other side of the world. The DA has already expressed an interest in seeing DrupalCon South America and DrupalCon Asia Pacific - which is fantastic, but I have concerns. Response to Questions Harley (Hyperglide) Regarding emerging markets in asia. Wants to know if any of the candidates have an idea on how to handle outreach to those markets to solve the talent shortage? Emerging markets are really important for Drupal's growth. There's a pretty critical Drupal skills shortage. Everyone is hitting that. China and India are both huge countries with lots of developers - finding a way to encourage them to participate in the community could help with the global skills shortage. But we also have to acknowledge the economic reality that participating in an open source project as a volunteer doesn't pay the bills. We need to connect with other open source communities in the region, and encourage and support local groups to create and grow their own events, meetups, mentoring, and community learning programs. The DA can help with some of that, but we're also going to run into some issues. We're going to have address the tension between commercial interests in training and certification with the broad based need for more people to learn Drupal.   tsvenson: What do you see as the biggest obstacles for new Drupal users, especially non coders with small or no budgets, often leading to them quickly going elsewhere? And what will you do to change that? We need to tackle the issues identified by the documentation team. They are the front line for new users. Our online help and support is where new users and new developers go to learn. Infrastructure bottle necks are a real issue holding us back. That is definitely something the DA should address. Even better, it's on the roadmap for 2012 - which is great. I'd support and champion that element of the 2012 roadmap. We also need to find how to support documentation translations, and better multi-lingual support, on drupal.org   webchick: For those who want to promote international diversity, explain how a position on the DA helps you do that more effectively. Actually, this is the core of my platform. International diversity has been identified as a key goal for the DA. Yet the makeup of the current board is largely homogenous. With one exception, all 8 of the current board members lives in North America. One is in Europe. No doubt these people have an international perspective, but it's one thing to think about, it's another thing to live it. The heated discussion about the need to travel was educational to say the least. As an example, the 2nd candidates meeting was scheduled at 4am Melb/Sydney time. We weren't expected to be there, but I wondered how failing to show up would hurt our candidacy? I decided to bite the bullet, get up early to be on the call. If elected, I'll be noisy, opinionated and irritating. I'll reach out to communities in Oceania, Asia and Africa, and encourage them to engage in the community, participate on groups.drupal.org, share their experiences of running local camps, and national associations - as I've started to try and do so with a BoF at London DrupalCon, and International Drupal Associations on G.D.O   Crell: Currently Drupal's face in the world is a mix of face-less Drupal.org and Acquia. Acquia is the face of Drupal, rightly or wrongly, in many eyes, moreso with the new Office of the CTO. Drupal of course is far far more than Acquia. What if anything do you feel the DA can or should do to counter-balance that, or is that even an appropriate role for the DA? I think the DA needs to look at the apache and gnome foundations. Acquia is incredibly important and powerful - but as far as the DA concerned - Acquia should just be one of many ddrupal companies. The DA needs to focus on the community and the infrastructure the community needs to make drupal better.   tsvenson: We just had a live usability test that showed we have still very much to do. How do you propose we can put more efforts into making Drupal, including contib projects, more user friendly and intuitive? Continue to improve the infrastrucuture... and invest in the tools we use... eg D.O Conduct further public live streamed usability sessions just like that. Very useful. But the next step is spreading knowledge of what to do with that information amongst the developer community, and ignite their passion to focus on usability challenges.   Slurpee: How many candidates have been to Drupal events outside of their own continent? And can you speak more than 1 language fluently? I have been to drupalcon sanfrancisco and london - I can't speak another language fluently... but I speak a little bit of Dutch.   Crell: Several of you listed things yo want to do or accomplish. The DA, however, has shifted from a staff board to a policy board, so board members are not directly doing anything, but managing, strategizing, coordinating, etc. Those of you who want to "do", isn't the board the wrong place for what you're describing? This is exactly why I want to get involved and be a voice for under represented parts of the Drupal community because all too often the policy gets driven without those things being considered. If you're not loud and you don't put your voice in when the policies being formed, it's much harder to move in that direction afterwards.   rfay: In 30 seconds or less, what are the roles of the DA and what are not the roles? The DA can amplify the work of local communities and also support and give credibility to them! The DA has no involvement in driving the Drupal project itself. It is primarily and administrative entity to manage the affairs of a series of large international conferences. Potentially taking over some of the legal intellectual property issues around the trademark which belongs to Dries Buytaert, and employing staff to help ensure DrupalCons happen, and the hardware and Drupal infrastructure keeps working.   Crell: Several candidates said they want to better represent or be a voice for "small shops" and independents. In what way does the DA currently not adequately serve small shops, and what would a better service for small players mean in practice? Be as specific as possible. I don't know that the DA is failing small shops, I just don't see those voices represented in the current makeup of the board. most are from NA and large organizations so it's not necessarily that there's a huge gap, but there is potentially a huge gap. I have a sense that this is a problem more than specific criticisms. But we're not just talking about small drupal shops... but people using Drupal who don't have a commercial interest in it... Hobbyists, non-profits staffed by volunteers, clubs and amateurs, and community groups. Tinkerers and students. Many of our contributors have come from this kind of background, it's a valuable proving ground for future Drupal talent.   tsvenson: When do you think the first Asian DrupalCon should be held? Also, should that mean 3 cons/year or should they alternate with 2/year? DrupalCon Asia? I was concerned about the idea of "drupalcon asia pacific" somehow being "the rest of the world" except Africa. The AsiaPacific region contains 3 of the 5 most populous nations on earth: India, China and Indonesia. They are all incredibly culturally and linguistically diverse. Trying to create a single event for both continents (ASIA and OCEANIA) is going to be an enormous challenge. DrupalCon Mumbai, DrupalCon Shanghai, DrupalCon Bali, DrupalCon Manila, DrupalCon Wellington might all happen one day. When? Yes, well that's a very good question. This year? unlikely. Next year? Maybe. And then 2 years after that. A DrupalCon in our region is going to happen pretty infrequently, I'm more interested in local communities building their own capacity to serve their needs with local events, than sit around waiting for the blessing of the Drupal Association. Perhaps the US Drupal community should adopt the North American DrupalCon as it's National event? And the Drupal Association should shift it's focus toward developing one International UberDrupalCongress which is on a different continent each year, more like the olympics, and focus all of its attention on that. I don't know. I just think we should question all our assumptions.   jredding: In 30 seconds or less, what would you say is the most important skillset, expertise, or experience that a board member should bring to the Association. One of the most important things is to bring a sense of collaboration and wilingness to work with the rest of the board on important topics. To try to reach consensus, and ensure we all bring our slightly different perspectives to the table when we're making decisions. People often think consensus is all happy families but you only get there considering many differnt perspectives and figuring out what you can agree on, rather than focussing on what you can't agree on.   carsonblack: Q: What are some (or one) way that DA can help the small user groups throughout the world better serve their local markets? Perhaps put together an info pack? How to build and grow your local community. How to engage with local businesses, authorities and educational institutions. Often what's holding people back, is just knowing where to begin.   jredding: When the DA board member is out n the community how would that member represent themselvs in the community? Would they have a title of board member and use that? I don't know. I think it's an interesting question and would be keen to explore ideas on how best to do this.   Crell: The DA is officially banned from "directing the development of Drupal". What does that mean to you? Are there ways the DA could "support" development without "directing" development? What would you want to do in that regard? Again, be specific as possible. I like the idea of funding sprints... not directing what happens at them, but helping them happen. Putting effort into the tools the project relies on is borderline... but it's something that needs doing....   tsvenson: Question: Should the DA take a more proactive role about the d.o infrastructure and its improvement needs. Especially in regards to for example content management tools for doumentation and giving better cred/visibility to all those that puts in amazing work that is not project/code related? If so how and what is needed? Yes! We expend effort and resources on ensuring DrupalCon happens, and that the servers keep running. We should be expending effort on the real heart of the community, drupal.org and groups.drupal.org. We urgently need to address bottle necks frustrating key community initiatives, such as documentation, support, prairie, some of these have lost momentum because of infrastructure bottlenecks, and the fact we can no longer really innovate on D.O.   Final Statement I'd like to finish off by saying Drupal is awesome. The community is what makes that true. I am desperate to give back to this project and this commnuity in the best way I can I'm not a coder, designer, documenter, but I am good at being committees, organising events. Following through. I will put in all my energy and efforts to be a useful productive, engaged member of the board. It's the first time the DA has run broad based elections like this. It is the beginning of a new chapter in terms of how org is structured. There's a a lot of work to do in the future around consolidating the work that's been done and becoming a more open/transparent organization. I'd love to be part of seeing that happen and working for the community by being on the board. I'd like to add, my fellow nominees are all awesome. Even if not elected, the DA should find a way to co-opt them onto other committees. They've all indicated a willingness to serve - let's harness their commitment, competence and energy. drupalplanetdrupal

---

Tree is a set of modules providing a framework for storing and manipulating hierarchical data.

---

This is a simple module provide the way to display the main-menu inside the block, when the user on any page which belong to main-menu. This will list all sub-menu with maximum depth/level. As per the screen-shot, we have main-menu "test" with the sub-menu "secondary test" and "secondary test !!", when the user on an of this three pages i.e. test, secondary test and secondary test !!, it will build the block content where it display parent menu from menu-menu and all it`s sub-menu(with maximum depth/level). Set title of the block equal to parent menu name from menu-menu. In this example "test" is parent menu so block title is "test" all the child of test menu, i.e. secondary test and secondary test !! are listed in the block. Link to project at Drupal git. http://drupalcode.org/sandbox/tusharbodke/1427008.git

---

user visit module for drupal 7 which is a combination of user visit and user visit advance

---

This module enables moneybookers payments via ubercart. This module was actually developed and available at http://www.ubercart.org/project/uc_moneybookers. We have converted it to Drupal 7.0.

---

Provides a field storage backend using SQL that does not create a revision table for each field

---

LeanZine is a Drupal 7 HTML5, CSS3 based magazine theme. Its a responsive theme, which will scale up to a large display and smoothly scale down to a mobile display.

---

git clone http://git.drupal.org/sandbox/Rory/1426848.git domain_access_login This module depends on the Domain Access module. It prevents users logging into domains that aren't assigned to them. Known issues This module does not currently prevent a user logging in with OpenID - using an OpenID identity to log in will bypass the form validation this module provides. Suggestions are welcome on how to address this.

---

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. About the Drupal Association elections 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! Where to find out about candidates Review their nomination profiles. Read the notes from the two all candidates' meetings at http://groups.drupal.org/node/207398. Who can vote? 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. How to vote 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! How does voting work? 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 Can I change my mind after I've voted? Yes! Before the close of voting, you can return to the voting form, cancel your previous vote, and submit a new vote. When will voting close? Voting will close at midnight UTC on Tuesday, February 7, 2012. How will results be determined and announced? 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. Why was voting delayed? 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. Wait. Only XXX eligible voters? What gives? 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. Problems and solutions 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. More about the elections The nominations announcement. The elections plan. All elections posts.

---

Introduction cache_warmer is a drush command that hits a set of URIs of a drupal site based on the freshness of the content. The main purpose is to offer a complete setup for running a mostly cached drupal site without having to deal with expiration logic and instead use microcaching. Dealing with the expiration logic is messy and inefficient it requires additional work, be it from the drupal side of things, be it from the external cache side. Microcaching can be used with any type of site. Be it your portfolio or personal blog or a high traffic news site. You have to tweak the cache validity (or Time To Live: TTL) for your site traffic profile. Although microcaching is particularly useful for the Nginx filesystem based cache it can be used with other caching systems like Varnish. It can be used also for priming any type of external cache Note that as is usual with drush although its tagged 7.x it works with both drupal 6 and drupal 7. How it works The drush command is quite light, it performs a drush bootstrap up toDRUSH_BOOTSTRAP_DRUPAL_DATABASE, which is equivalent to Drupal's BOOTSTRAP_DRUPAL_DATABASE, and queries the database for content that is fresh according to the given criteria. As example consider that we want to hit the lastest 300 nodes in the http://example.com site plus the URIs listed in hub pages file hub_pages.txt site in single threaded mode. drush cache-warmer --latest-n=300 --hub-pages-file=hub_pages.txt http://example.com If instead we wanted to hit the URIs for all the nodes updated in the last 2 days we do: drush cache-warmer --updated-last='-2 days' --hub-pages-file=hub_pages.txt http://example.com The --updated-last option accepts its argument as an integer representing the number of seconds ago the content was updated, e.g., --updated-last=3600 means the content updated in the last hour. It accepts also strings in strotime format. Hence the above -2 days (latest 48 hours). The only command argument is the base URI of the site to be hit. If you specify both a number of nodes through the - -latest-n option and a time range through the --updated-last option. The one returning the most number of items will be used. Note that this involves doing sub-queries hence is less efficient in SQL terms. Single threaded and Parallel operating modes You can run cache_warmer in single threaded (the default mode) or parallel. Parallel means that the requests are made in parallel, i.e., simultaneously. The single threaded mode uses PHP cURL extension only. Note that in order to use drupalhttprequest requires a higher level of boostrap than BOOTSTRAP_DRUPAL_DATABASE hence it would make cache_warmer less performant. Hence the option for cURL which is pretty much standard everywhere when we're considering a dependable standards observing HTTP client library. In single-threaded mode the request are made sequentially, i.e, the URIs are hit one after the other. Hence in each request cURL blocks up until it either times out or it gets a response. You can specify the timeout that cURL uses through the --timeout option. To specify a timeout of 15 seconds specify --timeout=15. Re-using the above example: drush cache-warmer --updated-last='-2 days' --timeout=15 --hub pages-file=hub_pages.txt http://example.com In parallel mode the requests are made in parallel in a specified size batch. To perform the above with 20 requests in parallel batches do: drush cache-warmer --updated-last='-2 days' --parallel=20 --crawler-service-uri=http://crawl.example.com/cache-warmer --timeout=15 --hub-pages-file=hub_pages.txt http://example.com As you can see there's a new option --crawler-service-uri that specifies the URI if the crawler to be used for hitting the list of URIs in batches of 20, i.e., making 20 parallel requests. The parallel crawler is implemented as a web service allowing for the crawler to be pluggable. There's a default crawler provided relying on Nginx Embedded Lua module ngx.location.capture_multi directive, that allows to make an arbitrary number of requests in a non-blocking way using Nginx event driven architecture coupled with Lua speed. The focus is on speed and simplicity. The limit of the parallelism will be at the OS and network level and not in any way inherent to this command. You can make 1000 requests in parallel if you wish. The limiting factors will be the either at the network level (the network gets saturated) or your drupal site cannot cope with such a number of simultaneous requests. Requirements Single threaded mode To use the single threaded mode just the cURL PHP extension and PHP 5 are required. Parallel mode This requires to either code your own parallel crawler or to have Nginx with the Embedded Lua module. In Debian, for example, this module is available in the nginx-extras. I provide a bleeding edge Nginx debian package that includes this module and a few less common ones while not including mail related modules. Other option is for you to build your own nginx package or binary. It requires the Lua Socket library. Hub pages Hub pages are pages in your site that function as a hub for accessing content. For example if you have a page for each taxonomy term you may specify some taxonomyterm pages in the hub pages file. Here's a simple hub pages file. It's a text file with a URI relative to the base URI of the site to be hit by the crawler on each line. The sole exception to that rule is the front page which is denoted by foobar/term1foobar/term2featured/users Besides the front page, , we're also hitting the hub pages with URIs /foobar/term1, /foobar/term2 and /featured/users. Note that each URI is always relative to the base URI of the site and is specified always without leading slash. Aliases and Pathauto By default the crawler assumes that you're using clean URIs with aliases. Usually you run something like pathauto on your drupal site. If your site doesn't use aliases you can disable the crawler default behavior with the option --no-aliases. Installation and Usage: Single threaded mode Download the command and install it in a drush aware location. The easiest option is to put it in your ~/.drush directory. Create your hub pages file. Specify the necessary options and you're done, if just testing or priming a cache. For using microcaching in a consistent manner. Create a cronjob with a schedule adapted to your site traffic profile and cache validity. Consider the above example. The cache TTL is 5 minutes and we want to keep the last 24 hours worth of content in cache and also all the hub pages. We specify a cronjob that runs every 8 minutes. */8 * * * * drush cache-warmer --updated-last='-24 hours' --timeout=15 --hub-pages-file=hub_pages.txt http://example.com Processing the replies. The command returns a structure of the response status, timestamp, time spent in request for each URI hit in JSON encoded format. You can pipe this output to a file for further processing and analysis of the way the cache warmer is interacting with the site. With the above example. */8 * * * * drush cache-warmer --updated-last='-24 hours' --timeout=15 --hub-pages-file=hub_pages.txt http://example.com >> /path/to/cache_warmer.log Installation and Usage: Parallel mode Download the command and install it in a drush aware location. The easiest option is to put it in your ~/.drush directory. Create your hub pages file. Create your custom parallel crawler web service or install Nginx and setup a host for functioning as the parallel crawler web service. There's a suggested config in the config subdirectory. Adapt it to your liking. Specify the necessary options and you're done, if just testing or priming a cache. For using microcaching in a consistent manner. Create a cronjob with a schedule adapted to your site traffic profile and cache validity. Consider the above example. The cache TTL is 5 minutes and we want to keep the last 24 hours worth of content in cache and also all the hub pages. We specify a cronjob that runs every 8 minutes. */8 * * * * drush cache-warmer --updated-last='-24 hours' --timeout=15 --parallel=20 --crawler-service-uri=http://crawler.example.com/cache-warmer--hub-pages-file=hub_pages.txt http://example.com Processing the replies. The command returns a structure of the response status, timestamp, time spent in request for each URI hit in JSON encoded format. You can pipe this output to a file for further processing and analysis of the way the cache warmer is interacting with the site. With the above example. */8 * * * * drush cache-warmer --updated-last='-24 hours' --timeout=15 --hub-pages-file=hub_pages.txt http://example.com >>/path/to/cache_warmer.log 100-continue responses The parallel mode works by POSTing the URIs to be hit in a form. cURL obeys the standards and sends a Expect: 100-continue header to the server when the POST data has a size above 1024 bytes. The server should reply with a 100 status code thus instructing cURL to go ahead and send the POST data. Therefore you could see a bunch of 100 status in the JSON array containing the responses of the crawler. That's how it should be. If you want to force cURL to POST immediately and thus avoid this additional round trip to the server then send an empty Expect header. Here's a gist with the option you need to add to the command. I might consider making it an option to the command in the future. Scheduling the cache warmer with precision Vixie's cron is the default cron on most UNIX flavours. Unfortunately not happy with only having an abstruse syntax it's also very imprecise. The smallest time unit is one minute and there's no certainty that a job will be triggered precisely in the exact second of the minute, i.e., if now the job is triggered at the 10 second mark of the current minute, there's no garantuee that the next minute trigger will happen also at the 10 second mark. For greater precision and an expressive language for scheduling jobs there's the Scheme (Guile) based scheduler mcron, that has second precision. You can even use the abstruse Vixie's cron syntax with it if you prefer. Microcaching configuration for Drupal Configuring Nginx for microcaching is a little beyond the scope of this documentation. I maintain a generic Nginx configuration that includes microcaching for both anonymous and authenticated users. TODO Add support for using Nginx embedded Lua module cosocket and thus create non-blocking sockets from within Nginx and thus avoid the Lua Socket library dependence. Integrate with httprl to provide a purely drupal (PHP) based parallel crawler. Add mcron configuration example. Add a script for doing graphical analysis of the crawler responses. Benchmark this approach against more usual approaches to caching like using Boost for example

---

TAC Redirect 403 extends the Taxonomy Access Control module by allowing you to specify a redirect URL for each taxonomy term. When a site visitor navigates to a content page that is restricted by a taxonomy access control rule, instead of Drupal's standard 403 (Access Denied) page being displayed, the visitor is redirected to the URL entered for the restricting term. This can be used to send people to custom "upsell" pages. For example, if your site has the taxonomy terms Basic and Premium, and these are used to designate content as only available to members at the corresponding membership tier, this module lets you redirect visitors attempting to access restricted content to a signup form for purchasing the necessary membership level. Dependencies Taxonomy Access Control Link (the redirect URL is added as a link field to the taxonomy term entities) ModuleField (lets modules define uninstantiated fields) This project also includes an add-on module that simplifies the administration UI when used in conjunction with the experimental TAC Alt UI interface. Credits This project was sponsored by Acquia as part of the Drupal Gardens project.

---

Site builders This module provides no direct functionality, so only download it if another module lists it as a dependency, or if you want to write your own module that uses its API. Developers Field UI and API are designed with the assumption that modules define field types, and administrators create fields and instantiate them within bundles. As part of this assumption, Field API automatically deletes fields when they're no longer in use by any bundles, and Field UI populates the add existing field dropdown only with fields that are in use by at least one bundle. This presents an annoyance for modules that want to define a field and make it available for adding to bundles, but without requiring any particular bundle to use it. ModuleField compensates for this: simply implement hook_modulefield_info() with your field definition and default instance definition, and ModuleField exposes this field within Field UI's add existing field dropdown even if the field has not yet been instantiated in any bundle. If you're interested in seeing this capability added to Drupal 8 core, please see #1426804: Provide a declarative API for modules to define fields, not just field types. Examples This module is used by TAC Redirect 403, so you can inspect that module's code for a real-world example. If you know of any other modules that use ModuleField, please submit an issue for that module to be referenced from here. Credits This project was sponsored by Acquia as part of the Drupal Gardens project.

---

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. About the Drupal Association elections 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! Where to find out about candidates Review their nomination profiles. read more

---

Image gallery with javascript slideshow.

---

What is the infusionsoft API module? This module acts as a layer between Drupal and infusionsoft, which makes the process of talking between the two much easier. Why is this module needed? Infusionsoft is a proprietary CRM, and highly available email auto responder system. This module, makes things such as adding a user to infusionsoft, or manipulating user information being sent to infusionsoft easier, by providing default functions for common actions. Also, this module is faster than using the Infusionsoft SDK because it uses the built in drupal version of XML-RPC instead of using it twice. This module also includes drupal specific functions for things like adding a drupal user to infusionsoft. Default Integrations These integrations work if you have the modules turned on. These still have to be configured before anything will happen. Ubercart conditional actions - provides configurable conditional actions for use within ubercart Drupal actions - provides configurable actions which can be used by drupal triggers module, and other modules which leverage the drupal actions system. Rules - works with the rules module to provide a tags condition, rules can also leverage drupal actions to perform various functions. Submodules infusionsoft_log_email - a small module when enabled will log all outgoing drupal email to the receiving contact's infusionsoft correspondence record.infusionsoft_oneway_sync - synching an email address to infusionsoft when someone updates their profile.infusionsoft_uc_access - conditional action and api function to sync contact data from uc_adresses to infusionsoft Install To get started using the API, you will need to go through an initial set-up process. The result of the setup process will be an encrypted key that you will need for authentication. 1. Log in to your Infusionsoft application with Admin privileges. 2. Hover over Setup and select Misc Settings. 3. Click Application Settings on the left navigation menu. 4. Select the Miscellaneous tab 5. Scroll down to the bottom of the page, where you will see the API section. 6. Enter a passphrase in the API passphrase field. 7. (optional) enter the Enter IP addresses of servers you want to talk to infusionsoft (this is an additional security parameter that you can use to limit access to the API from certain IP addresses. It is highly recommended that you use this field to help protected your data) 8. Click the Save button at the bottom of the screen. 9. The Encrypted Key will be automatically generated. 10. Write down this key – it will be essential to getting the API to work 11. On your drupal site fill out the information on admin/settings/infusionsoft. Use This module provides the following actions for use in the system through the built in trigger module, or through the rules module * Add current user to infusionsoft database * Add tag to drupal user in the infusionsoft database * Remove tag from a drupal user in the infusionsoft database * Run an action set on a user in the infusionsoft database * Add user to a campaign in the infusionsoft database * Remove user from a campaign in the infusionsoft database * Pause a campaign for a user in the infusionsoft database * Resume a campaign for a user in the infusionsoft database Rules only: Condition: User has a specific infusionsoft tag. Developers This module allows developers to leverage infusionsoft without reinventing the wheel. Do this by using the services and methods found here:http://help.infusionsoft.com/developers/services-methods and encapsulating them by calling the service and method as the first variable passed to infusionsoft_send_request(). All subsequent variables should be passed following this first request. You should not include the API key in this request. Also There is an infusionsoft api built especially for drupal. It is documented inside the module in the infusionsoft.api.inc file. You need to know which service to use. method calls look like this: Service.method (as documented http://help.infusionsoft.com/developers/services-methods) The code in the infusionsoft module is thoroughly documented to make it easy to use, just look through infusionsoft.api.inc to find more descriptive functions to use in your own application. How does this differ than the 'infusionlink' module? This module takes some of the ideas from this module, and makes it much more extensible. It is much more robust, because you can actually set up a site without any coding by using drupal actions or ubercart. Special thanks to this thread (and its contributors)http://drupal.org/node/922964

---

A Tao subtheme which will integrate twitter bootstrap elements

---

With a new Drupal Core release out, it's worth reminding people just how easy it is to pull an update if you're using Pantheon: One click and you're done! This is the beauty of starting a project off the canonical git history. Also, of note - updating the stone-age way (unpacking a tarball from Drupal.org and overwriting all your core files) won't give good results. This will stop on the PRESSFLOW_SETTINGS auto-configuration system we use to connect to databases and other external services. Take the path of least resistance: it's also the best practice!

---

Tony is a proof of concept demonstrating the absolute minimum necessary to build responsive Drupal themes from the ground up with a custom layout and break points for display on all sizes. Like Core's Stark theme, Tony consists only of a .info file and a layout.css file (along with the .sass source file used to generate it). This theme is called Tony in tribute to my favorite Stark (and for the nerds). You can read much more about it in the blog post.

---

This one-day event is for business leaders of Drupal businesses (CEO, Partner, President, CMO, etc.) and it provides networking, business training and collaborative problem solving for common business challenges that Drupal-related companies face. There will be sessions on how to retain staff and build teams, plus a half-day moderated forum. The event fee is $150 and will conclude with a cocktail mixer. Register now, limited seats are available. Read more about CxO Day

---

In late 2011, Twitter launched some new tools that allows users to embedd tweets. You can grab the code from a specific tweet from the tweet's detail page OR you can use the Twitter's oEmbed endpoint (https://dev.twitter.com/docs/embedded-tweets). This module uses the oEmbed endpoint call to generate static pre-formatted blocks to your site to be used via blocks where ever you like. The oEmbed api can go and request the information about the tweet and generate the embedded block. NOTE: This is not a live updating block of tweets, this leverages the twitter oEmbed using the tweetid you specified in the admin settings. The block is static unless you update the ID in the settings. This module generates 3 blocks Block 1 - The proper response from the twitter API formatter by twitter. The twitter JS is required and is an option in the admin for this block. Block 2 - A single line representation of the tweet. Block 3 - A stylized version of the tweet that you can skin yourself. There is a limit to # of API request you can do per hour. This module stashes the response in the db and only makes requests when you save the settings form. Content is not written into the block unless an ID is specified.

---

The Search Query Exclude module, allows site administrators to easily control the search results by providing a query to exclude nodes from the search result. Use Cases: 1) Exclude nodes with php code using the default query providedselect nid from node_revisions where body like '%

---

Bash scripts to manage development and deployment of Drupal distributions using drush_make

---

commerce feeds processor for commerce price table

---

Well, it's been a few weeks since the 1st of the year, so of course most of us are either dreading or hoping for the question: "How are you doing with your New Year's resolution?" Today, I'm excited to report on one of mine!

---

This is the Drupal 7 version of the features module and sub-theme from my presentation on 02/01/2012 at the DrupalNYC Meetup. I formulated this features module with the broadest audience in mind and have included all the dependencies. When the module in enabled on a fresh Drupal installation, the user will have immediate access to Views UI and so forth. I previously included a sub-theme with this module which wasn't necessary. I've now added a hook_init() to the module file which facilitates adding mymunsters.css. The result is this widget is even easier to implement. The colorbox module for Drupal 7 requires a patch to its views/colorbox_handler_field_colorbox.inc in order to display the Replacement Patterns. I've included the patch with the module although you can easily download it at http://drupal.org/node/1280456. The patch is by the developer and it worked immediately after I applied it. Otherwise, after enabling the module in a sandbox of your own, add one or more nodes of type 'basic page', and then go to the home page.

---

Private files are great but they are a huge resource hog. In certain scenarios, lower-resolution versions of the pictures are absolutely fine to be public, only high resolution originals need to be protected. In this case you can use Drupal's private file handling as it is and the following simple trick to make a style public. read more

---

Provides a series of field-types for storing NLM-DTD based data. Currently supports - NLM Contributor -- stores information about an author or contributor Will soon support - NLM Copyright -- stores information about copyright For more information about the NLM-DTD see:http://dtd.nlm.nih.gov/http://dtd.nlm.nih.gov/publishing/tag-library/3.0/index.html This module is under active development and is not ready for production. It will eat your data, ruin the carpets, and run off with your SO. This module exists thanks to the generous support of HighWire Press and Stanford University

---

General Overview The Drupal 8 Mobile initiative’s goal aims to make Drupal the leading mobile CMS platform. Certainly, there are some fantastic contributed modules that already make Drupal a great starting point for mobile solutions; modules like Mobile Tools, Domain Access, Responsive Images, as well as a whole slew of new ones that have been released in the past few months. But in order for a CMS to earn the moniker "mobile-friendly", setting it all up needs to be easy. Right now, Web development experts are building mobile apps and websites while looking for integration with existing CMSs. And they are having to build a lot of the tools themselves because there are very few mature tools. The Web development industry as a whole is still trying to figure out the best way to build mobile sites and Drupal needs to engage and become a leader as that work continues. There are currently at least five different ways to provide mobile solutions: Native apps (code compiled to run natively on iPhones, Androids, etc.) Web apps (HTML5 and JavaScript-based apps running on mobile browsers) Mobile/desktop domain switching (parallel websites: one for desktop and one for mobile, with device detection to switch between the two.) Responsive design (a single HTML source that uses CSS3 media queries to respond to different device capabilities) RESS: Responsive Design + Server-side Components (a hybrid approach that uses Responsive Design techniques combined with a light amount of device detection to alter the markup before being sent to the user.) Drupal, whether in core or contrib, should support all of them. Now that’s a pretty broad spectrum of things to cover and they can’t all be included in core. But, to reach that “mobile-friendly CMS” status, what are the top issues Drupal 8 core should provide? Web services for native app integration HTML5 elements necessary for HTML5 Web apps Ability to use Drupal’s administrative forms in mobile devices All of Drupal 8’s core themes should be responsive Front-end performance improvements Fortunately, the first two points are already covered by the Web Services and Context Core Initiative and the HTML5 Initiative. That just leaves the last three items for the Drupal 8 Mobile Initiative to focus on.   Objectives Responsive Web design Responsive design is the hottest technique in producing mobile friendly websites because, relative to traditional mobile building techniques, it lowers the development cost for including mobile device support. Websites that only support large screens will become an anachronism, so converting all of core’s current themes to have mobile-first responsive designs is essential for Drupal to remain relevant. (Incidentally, the Drupal 8 Design Initiative, which is focusing on building new themes for Drupal 8, will also ensure its themes are responsive.) Mobile-friendly forms If users can’t create content or administer a Drupal site while on a mobile device, we have a serious problem. Those are the first tasks attempted by users on new Drupal websites. Much as the “ugly themes in Drupal 6” made a bad first impression of Drupal to Web designers, not providing mobile administrative solutions will leave a sour taste in the mouths of mobile developers evaluating CMS solutions. To complete this task, we’ll have to look at the complete stack for administrative tasks, including form definitions, form submit handlers, the Toolbar, the Overlay, and the Seven theme. The target is 100% mobile-friendly administration via responsive design, but we recognize that certain pages, e.g., the permissions page, may require a dedicated mobile presentation. Front-end performance Lastly, performance has always been a priority for websites, but with mobile it becomes critical. Some studies show up to 97% of a page’s render time takes place in the front-end. There are a laundry list of best practices for front-end performance that will help mobile and desktop users. And I’ve seen several members of the Drupal community speak about these issues multiple times this past year. However, when dealing with responsive design, the single biggest performance concern is image handling. The first demo of responsive design had over-large images being sent to mobile devices. While no single best solution has yet been found, we intend to leverage Drupal 7’s image styles to solve this issue.   Program tasks Program tasks are defined in the following way: Must have (essential to success) Should have (significant impact to success) Could have (should be done, but are not essential) Won’t have (future functionality) Must have / Critical Responsive Web design Seven converted: http://drupal.org/node/1088792 Stark converted: http://drupal.org/node/1322794 Bartik converted: http://drupal.org/node/1192044 Mobile-friendly administration For all content editing and workflow related pages (adding users, taxonomy terms, menu items, new content, moderating content, etc.) Review of the Toolbar Review of the Overlay Front-end performance Responsive images: As the layout is resized, the browser will serve the proper image size (“real” size, not height/width attributes) See Responsive image discussion for current status. Optimized images Sprites used wherever appropriate Optimized css: Evaluate the css aggregation process and adjust where improvements can be made. One of the first issues that needs tackling is determining a dependencies list so the critical tasks can be done as quickly as possible. For example, all mobile-friendly admin tasks are dependent on Seven being responsive. Should have / Major Front end performance Documentation of the use cases that css aggregation serves. Documentation for how to optimize for other use cases. Documentation for how to make contributed projects mobile friendly. http://drupal.org/node/1341310 Mobile-friendly administration Configuration pages converted (creating a new content type; adding fields to a user profile, etc.) Front-end performance Document the use cases that css aggregation serves. Document how to optimize for other use cases. Document how to make contributed projects mobile friendly. Could have / Normal & Minor TBD Won’t have Any impact on Drupal.org; See http://drupal.org/node/951114 Core

---

Rules are great for workflows. We have about 30 rules in place on our intranet to help almost every part of our daily workflow, and as with most offices communication between we mere mortals and our fearless leaders is critical. With the help of realname and realname user rereference we create a convenient user interface for data entry, Realname User Reference Widget After that we work with Rules and Tokens to create a more automated workflow.  For the Video types there’s a brief ~3 minute video. The important thing to remember when working with user references in rules is that you must load the user reference BEFORE those that user and the associated tokens become available.  Give your user reference a handy name to create your unique tokens and you’re ok.  Once you have loaded the referenced user into your rule, the tokens are available to use – any information stored in the referenced user’s profile is there too. Also used in this tutorial though not mentioned explicitly is html mail for sending prettier emails through rules. This is how our rule looked at the end Debugging: If you find yourself in trouble remember that in the settings page you may turn on the rules debugger (which, depending on the number of rules may churn out a rather lengthy list… ). In the settings there’s also an option to turn off token warnings.  This may tell you whether or not you’ve done your job with the use of tokens. Debugging Rules - tokens have options too

---

Did an deploy on one of the sites that we are working with, we did not get any errors on our staging server, but when we put it out on the production server we really had a big problem with caching. Suddenly cache would choke, display white screens of sadness, just caching part of the page, etc. Crisis. At least. I tracked it down, with beads of sweat running down my face (the problem were on the production server for gods sake), and the problem were that Panels were in legacy mode and our custom layouts did not work. I found a couple of discussion on drupal.org on the subject. I updated the Skinr module to make panels running normal. Updated the database, cleared the cache a couple of times. And then, finally, everything worked ok again. I could wash my face, and make a phone call to the client to say that everything now was ok.Lessons learned from this are several, but the most important was - never let panels work in legacy mode PanelsCacheSkinrLegacy

---

A client of ours recently had a major business announcement and needed to update their site's theme and publish a node to coincide with the announcement. Had the announcement been scheduled for regular business hours I probably would have made the changes manually, but because it was scheduled for 5:30 am I needed a better solution. read more

---

As the Drupal Core accessibility maintainer, I from time to time have people ask me about the accessibility of different contributed modules. Several times in the past I've been asked about the accessibility of Panels (where I assume the person means cTools Page Manager as well). Only this week have I had the need to use Panels and Page Manager. This is by no means a thorough review, but my observations as a screen-reader user. I was definitely able to get around Page Manager, to clone and modify some node_view variants. The experience wasn't something that made me super happy, indeed I yelled (quite literally) at my computer several times. The first major problem I observed was that the 'gear' icons (used to modify regions, to add content, and to modify panels) were read as 'link #'. I didn't go looking into the DOM, but this is generally symptom of an anchor without any text. Screen-reader users should know that the 'link #' prior to a region or panel is the gear that will expose the options for the proceeding object. The second problem was that I wasn't able to rearrange panels by dragging and dropping. This is pretty obvious, as screen-reader users don't tend to use a mouse. In Drupal Core we mitigated the accessibility barrier caused by tabledrag UIs by implementing 'row weights'. The same thing wouldn't necessarily work here, but it might be possible to expose a weight for each panel in a region through the UI. Perhaps this already exists and I'm just not finding it. I've filed the following bugs, and will work with the cTools module maintainer to improve the accessibility of the module. #1425310: Configuration 'gears' missing anchor text #1425314: Cannot reorder panels with keyboard Tags: AccessibilityDrupalPlanet

---

It can take a while when you're new, but once you start to wrap your head around Views, that is when Drupal gets really fun. In this tutorial, I'll go over how to use Contextual Filters in Views to alter your content dynamically based on information in the URL. If you're a visual learner, you can skip to the video at the end of this post for a detailed walk through of the process. Read more

---

In this episode of Drupal Yarns we talk with Donna Benjamin (KatteKrab) about the success of Drupal Downunder and various other Australian Drupal issues.

---

Drupal is one of the most SEO-friendly CMS's on the market. This session will review some of Drupal's core modules and features that can ...youtube.com

---

This is part two of my talk with Mike Carper about his Drupal performance modules. If speed and performance are essential to your work, listen to these episodes! Modules discussed in this episode: Boost DB Tuner Cache Expiration HTTP Parallel Request Library Files Proxy ImageField Zip/HTML5 Bulk Upload

---

Anyone with an idea and a desire to build is welcome to join in this year's Hackathon at DrupalCon Denver on Monday, March 19 from 3pm - 9pm (dinner included). Sponsored by Tropo, prizes will be awarded to the best Tropo API application for this year's theme, "Apps for Good" and the event is free to participate and open to all registered attendees! See more details on our Hackathon page.

---

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

---

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. Download Drupal 7.12 Download Drupal 6.24 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. Security information 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. Bug reports 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. Changelog 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. Security vulnerabilities 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. What is included with each release? 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. Update notes 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. Known issues # Drupal 7 Bug fixes in 7.12 release cause problems with the Internationalization (i18n) module, and there are reports of the same about Menu Block: #1425342: Drupal core upgrade from 7.10 to 7.12 causes menu block to fail. Users of these modules are encouraged to update to 7.11 to get the security fixes, and hold off on the 7.12 upgrade until #1351678: Follow menu_link_get_preferred active trail handling for custom menus and #1050466: The taxonomy index should be maintained in a node hook, not a field hook are resolved. (Note: Help here would be greatly appreciated!) Drupal 6 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

---

DoxygenIt's been a few years, now, since I gave up using PHPDocumentor to document my PHP projects. I switched to Doxygen, an automated documentation tool that supports a wide variety of languages, including PHP. While PHPDocumentor enjoys broad support in the PHP community, Doxygen, too, is well entrenched. (Drupal uses it.) I recently began a new project from scratch, and it gave me an opportunity to once again turn a hard gaze upon Doxygen. After some careful reflection on my experiences developing this new medium-sized library and documenting it with Doxygen, here are what I see as Doxygen's strong and weak points when it comes to PHP API documentation. read more

---

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. read more

---

CKEditor is the WYSIWYG (What You See Is What You Get) editor of choice around the Digett office. While some may bemoan the use of a WYSIWYG editor at all, even an experienced developer can usually save a lot of time during content entry by using one. Drupal does not come with a built-in editor but there are many excellent options; CKEditor is the cream of the crop. read more

---

Whether you're on Drupal 7 with it's clean administration theme, or still on Drupal 6, there're ways to make interface more userfriendly and improve the workflow. Administration menu Administration Menu module is a must for Drupal 6, but it's still helpful on Drupal 7 as a replacement for the built in admin toolbar. It's main feature is a toolbar with dropdown menus where you can drill down the entire menu tree (you can even add local tasks such as tabs to it). It also integrates with Devel module and VBO (see below) and has more nice features. Related stories:  If you liked it this story, you might like the following: Redirect 403 to User Login (r4032login module).Drupal Intranets with Open Atrium Giveaway - Comment to Win a New Drupal BookCustom contact form with conditional fields using webform and webform conditionalDrush Site Aliases and Interactive ShellInstall Drupal 7 site with Drush read more

---

Tags: drupalplanet drupalOn Vejle Idrætshøjskoles site I needed to make pdf's of all the lectures, so I could create a small booklet. I created a lecture content type with a title, body and an image. I made a simple pdf of each lecture, but wanted to include a barcode, so people seeing the pdf could just scan it on their smartphones and go directly to the page and registration to participate in the lecture. First I installed and enabled chart and libraries and put the external PHP library TCPDF in the libraries folder. Using TCPDF it is fairly easy to create a PDF, so I just needed to figure out how to use chart to create the barcode. So basically this is what I did. $pdf = new TCPDF(); $chart = array( '#chart_id' => 'lectures_chart', '#type' => CHART_TYPE_QR, '#size' => chart_size(200, 200) ); $chart['#data'][] = ''; $chart['#labels'][] = $link; $qr_file = chart_copy($chart, 'my_chart_' . uniqid(), '/home/username/www/sites/default/files/charts/'); if ($qr_file !== false) { $pdf->Image($qr_file, 4, 250, 35, 0, ''); } If you want to see the full approach on how I created this pdf, you can see my small custom module on github. There is many ways to improve the module, and it needs cleanup. However, it works, and you can easily include the barcode. Tweak it and try it (it is a custom module so it will not work directly on your website before changing it). Maybe you can even improve it? P.S. To make the function chart_copy() work in the above example, you need to apply the patch from issue #1303706.

---

If you own a mac, you use spotlight daily. Or even better, use Alfred. A great way to navigate faster with a keyboard towards the app or data you need. A very long time ago a Boy Wonder made something like this for Drupal 5, navigating through the /admin pages using a simple spotlight alike interface, see the menuscout module. Unfortunately, Boy Wonder, he wandered off and the module gained dust. Then some time ago co-worker Michael Mol showed me a module he has been working on. Since he was doing D6 and D7 development at the same time and since the URL's changed and developers use URL's as well for navigation, he decided to d a spotlight alike search on the admin pages so he could remember the name, not the URL. It ended up being coffee, for now a sandbox project but anyday now a real project in d.o. To see it in action, take a look at this screencast. Think of coffee as spotlight for the admin interface. And if you want an easter egg like the do a barrel roll, get active in this issue.

---

Tags: drupalplanet drupalOn Vejle Idrætshøjskoles website I wanted a small teaser slideshow with a picture, title and a link to the actual content. To accomplish that I used Views 3, Views Slideshow, Nodequeue and a little bit of custom css. When all the modules were installed and enabled, I first created my nodequeue under admin/structure/nodequeue. I just called it frontpage and started adding some pages to it. When I was satisfied with the nodequeue, I went to the views ui at admin/structure/views. A view for my nodequeue was already created, so I went ahead and edited that view. A page and a block was already setup. I went ahead and cloned the block, so I could make my modifications. 1) Under format I choose Slideshow. 2) Under fields I put in my picture and the title (in that order). 3) Under advanced and css class, I put in my custom css class sidebar-slide. The preview in views already shows a nice slideshow with the pictures and titles changing regularly. Making the teaser slideshow look like I wanted with css .sidebar-slide { position: relative; top: 0; height: 208px; } .sidebar-slide div.views-field-title a { position: absolute; top: 100px; display: block; font-size: 1.1em; text-decoration: none; font-weight: bold; background: black; padding: 5px 10px; color: white; opacity:0.7; filter:alpha(opacity=70); }That way I had the simple teaser slideshow on the frontpage of vih.dk. That was both easy and enjoyable and why Drupal i great. To make it more userfriendly I added links to the inline links section of the content. See "Tilføj forside" on the screenshot above. Caveats Now I wanted to make the same kind of block on "Korte højskolekurser" and "Lange højskolekurser". I followed the same steps as above. However, now this approach seems to have found its limitations. Nodequeue creates one view pr. nodequeue, so I had to manually recreate the same steps to make another block. And now I have one link pr. nodequeue in the bottom of the content area, quickly making the GUI less userfriendly.  Did any of you take this approach, and how did you solve the problem when you wanted more teaser blocks with slightly different content?

---

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.

---

A clean, contemporary theme by ThemeShark.com It was sponsored by Desponder.com, a culture magazine/blog. It's based on ThemeShark's own simple starter that we use internally for all of our drupal themes. View a live demo If you want to take advantage of the slideshow, it requires Views Slideshow and a Views export found on Tharkshark.com. The instructions for setting it up are included there too. Features: Additional CSS for a Slideshow (using the Views Slideshow module) Tableless design Strict XHTML and CSS validation Two resizable sidebars Resizable page width Switch between fonts/sizes in Theme Settings Set up Twitter/Facebook links in Theme Settings Eight additional and fully collapsible regions Superfish dropdowns

---

Ingrained is a two column responsive design with narrow (sidebar) content on the left and using the Omega base theme. Original design by Jozef Toth (www.mogdesign.eu), theme by Emma Jane and Design to Theme for the Responsive Web Design workshop. Detailed installation instructions are included in the theme's README file. You will need to download the base theme Omega and Omega Tools and may optionally choose to use the helper module Block Class.

---

A simple responsive subtheme for the base theme Fusion. Uses all of Fusion's default regions and adds a few extra CSS3-enhanced skins for blocks. Detailed README file includes instructions for flyout menus with Superfish, and older IE support with the polyfill css3-mediaqueries.js via Fusion Accelerator. Originally created for the students of the Responsive Web Design Guild by Emma Jane and Design to Theme.

---

Business is a great looking Drupal 7 theme. The theme is not dependent on any core theme. Its very light weight with modern look and feel. Business's clean layout and light weight code make it a great theme for small or medium-sized business to get up and running quickly. Features Simple and clean design Fixed width (980px) Drupal standards compliant Custom front-page with 4 block regions Implementation of a JS Slideshow Multi-level drop-down menus Use of Google Web Fonts Custom front-page with 4 block regions Footer with 4 regions A total of 12 regions Compatible and tested on IE7, IE8, IE9+, Opera, Firefox, Chrome browsers Live Demo Help and Support Us Please consider a small donation. Documentation Detailed documentation and a guide on how to reproduce our demo installation.

---

The Bay is a sub-theme that will run using the Clean theme as a base theme. This theme was built for use on the 2011 BADCamp (Bay Area Drupal Camp) website, and will probably be useful to only a few who want a similar look and feel. If there is enough interest, I'll refactor the theme for Drupal 7.

---

Thème sur le jeu Battlefield 3

---

This is what tey want

---

Want to learn more about Acquia's products, services, and happenings in the Drupal Community? Visit our site: bit.ly How do I get the most out ...youtube.com

---

A base theme based off of Boilerstrap (http://www.github.com/desmondmorris/boilerstrap). Boilerstrap is a project that brings together the HTML5 Boilerplate and the Twitter Bootstrap projects.

---

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.

---

adaptIC is a very simple responsive theme. The ultimate goal for this theme is to create a clean starting point for someone to create their own responsive website. There is still plenty of work to be done but the beginnings are here. adaptIC has a max size of 960px and is fluid down to devices with a screen size of 480px. Once below 480px the right sidebar drops below the main content. I have built this theme with personal blogs in mind, it will suit this purpose best out of the box but could suit any other purpose with some customization.

---

In the spirit of ideas worth spreading, TEDx is a program of local, self-organized events that bring people together to share a TED-like experience. At a TEDx event, TEDTalks video and live speakers combine to spark deep discussion and connection in a small group. These local, self-organized events are branded TEDx, where x = independently organized TED event. The TED Conference provides general guidance for the TEDx program, but individual TEDx events are self-organized (subject to certain rules and regulations). Betawerk is one of the fouding partners of TEDxEutropolis. Eutropolis is an everchanging utopian vision for the Euregion Meuse-Rhine (border region of Netherlands, Belgium and Germany). It connects more than 10 middle sized cities in this international region by imagining a crossborder subway system. This vision is not about transport. The website of TEDxEutropolis is made in Drupal 7. Since we're big fans of Drupal we would like to contribute the template of our TEDx website to the community, so it can be used by other TEDx organizations around the world. We hope you like it!

---

For DrupalCon sites hosted on Drupal.org. Depends on Drupal.org's configuration. Not recommended for use elsewhere.

---

hGarden is a theme originally developed for Kashmir The Paradise [dot] com and was ported to Drupal along-with the site in 2010. As the website was ported to Drupal 6.x, the theme is also for the same Drupal Installations.

---

Introduction 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. Methodology 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. Profile of the respondents Prairie Survey 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. Getting Involved Survey 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. Executive Summary 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 The contributing experience 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”. What do people want to contribute? 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%). What areas need the most contributions? The respondents thought documentation (12 respondents), Drupal.org. (7 respondents) and Design/UX/Usability (6 respondents) needed the most attention from other contributors. What areas of Drupal community do you think need the most contributions? 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. Other Findings 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. Roadblocks to contributing 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%) ‘Get Involved’ pages and Drupal.org 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%). How could we improve the experience? 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) Other noteworthy things 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. What do you think about the existing community structure? Conclusion 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. Next steps 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).

---

Moderna is clean and slick theme for drupal 7.x good for presentation and others site Features fixed width (960px) 3 column Support 1 / 2 / 3 column Image style Font embeded Support custom logo and favicon the theme are currently in development process. it will be available after test

---

Splendio is a great looking Drupal 7 theme. The theme is not dependent on any core theme. Its very light weight with modern look and feel. Features Simple and clean design. Drupal standards compliant. Fixed width (980px). 1 or 2 column layout. Post thumbnail. Facebook, Twitter integration. Multilevel CSS drop down menus. 10+ collapsible blocks region. Tableless. Use of Google Web Fonts. Compatible and tested on IE7, IE8, IE9+, Opera, Firefox, Chrome browsers. Extensive CSS rules for: 'Read more' and Comment buttons Images into content Comments, Polls User profiles Blocks, Search block Footer with 4 regions Configurable Mega Footer Menu Live Demo Documentation Detailed documentation and a guide on how to reproduce our demo installation. Help and Support Us Please consider a small donation.

---

The goal of the theme is to create a Drupal 7 theme as the base for websites related to the University of Wisconsin - Madison. Omega is used as the base theme to give users the option of a responsive web experience. Required Modules Omega base theme installed, but not enabled Recommended Modules Admin Menu - To have a dropdown admin menu, but disable the Toolbar Module if you do this. Module Filter - Allows you to quickly make order of the modules you have enabled. Menu Attributes - can add classes to menu items. This is used to create a menu accordion (see below). Block Class - can add a class to a block. Used to skin the blocks (see below). Superfish - Install/Enable if you want dropdowns or MegaMenus. (This is currently in development.) Omega Tools (for Development) -- Can subtheme Omega fast, and export your theme's updated settings to the .info file. Menu Breadcrumb or Custom Breadcrumbs -- Drupal 7 uses the Main Menu to determine the breadcrumbs, but this module allows you to use the menu the current page belongs to. You will have more fine grain control of the breadcrumb settings. Modules for Production with Omega Context -- Allows you to have conditions & reactions to determine block placement & delta (don't have to use the Block interface). Delta -- Allows you to save a Omega Zone & Region Configuration and then can set it for different Conditions using the Context Module. Videos that Explain how to use Omega DrupalCon London 2011 by Jake Strawn (he made Omega) Drupal DownUnder 2012 Atlanta Drupal Users Group (bad sound, but they have a bunch of videos) Theme Walkthrough Install Omega & the UW_Madison_Omega themes Enable and Set UW_Madison_Omega as the default theme Add a Menu Block to the User Bar Second (make sure the title is set to ) Make sure the site slogan is set to what you want (if you want one) Add the Search Block to the Branding Region (change permissions to let anonymous users use the search) add a block to a region in the footer zone to get the background color working (Structure > Blocks) By default there are 4 regions in the footer zone. You can remove regions or resize them by going into the uw_madison_omega theme settings. add a custom block with the copyright links (title = ) to the footer_postscript region and it will center automatically resize your browser and see how it will resize to have a responsive look for different page widths (mobile phones, tablets, etc) Menu Accordion if you want to have a menu accordion like Vanderbilt does on http://www.vanderbilt.edu/chancellor/ when you click on NAVIGATE VU, a menu appears above. Install and enable the Menu_Attributes Module Make sure you already have a menu in the upper right corner, User Bar Second (we'll call it "Top Right Menu") Create a new menu (I called it "Nate's Accordion Menu", but name it whatever you want) and order the links with the links that should go to the right at the top. set title => for both menu blocks add the menu (Nate's Accordion Menu) to one of the 3 accordion regions (I added it to the first accordion region) In the "Top Right Menu" there is a link called "open menu", that when you click on it, the menu you placed in the accordion ("Nate's Accordion Menu") will appear This link must go somewhere for accessibility reasons. If javascript is disabled the Accordion won't work so this could link to wisc.edu, or somewhere. Add a class to the "open menu" link of "accordion-first". (or "accordion-second" if you placed it in the second accordion region, or "accordion-third"...) Done. Personal Opinion. This would be a great way of linking back to the wisc.edu site. You could have the Main Nav & upper right toolbar menu as accorion menus. Skining Blocks You will need to install/enable the Block Class module. When you edit/create a block you can now add a class to it. I have created 4 different skins "quick-facts" "red-links" "quick-links" "sidebar-menu" (see http://www.wisc.edu/academics/ for an example) so if you want create a quick-facts block, just add "quick-facts" class (no quotes) in the configure block settings. The CSS for the skins is in content-zone.css. *** If you create more skins let me know so I can add them to the theme. *** Extend Theme by Subtheming it Install and Enable Omega_Tools Module. Go to appearance/omega-tools/add Add name and choose UW Madison Omega. Keep Defaults (install auto, dest all...) Add a Description & a version # Save and then you can enable your theme! Future Devolopment for the UW_Madison_Omega Theme: Add some CSS to the Content Region (nothing there right now) Create more skins for blocks & the content region. Should the Skins have some default padding??? --**update** .block {margin-top:40px; } was used, but now removed. Should a Sidebar be Yellow? How should the breadcrumbs be styled? --**used red & grey** Should a Menu in the Sidebar be themed like on http://uc.wisc.edu/brand/templates-and-downloads/web/index-no-top-nav/in... ? --**update** added sidebar-menu skin Search Block. Should I try to match wisc.edu exactly or make it better? Focus/Blur currently. Theme the MegaMenu using the SuperFish module. Demo this at a Meetup (doing so 2/7/12) Drink beer Any thoughts/ideas???

---

*There are never in nature two beings which are exactly alike. -G.W. Leibniz *Statistical thinking will one day be as necessary for efficient citizenship as the ability to read and write. -H.G. Wells *People who don’t count won’t count. -Anatole France *It is the mark of a truly intelligent person to be moved by statistics. -George Bernard Shaw *Statistics, as applied to products and services, is not an end in itself,but exists principally to illuminate the way to progress in other fields that require the proper handling of uncertainty. -Antonio Possolo

---

This is new theme which i have send to drupal.

---

This tutorial show you how to quickly connect your Drupal website with popular social media sites such as Twitter and Facebook. It is a demo of ...youtube.com

---

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. Who can vote? 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. How to run 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 process 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.

---

Start:  2012-01-18 22:30 - 2012-01-26 00:00 UTC Online meeting (eg. IRC meeting) Organizers:  nedjo webchick highermath In case you missed the announcement on Drupal Planet, Drupal Association 2012 elections are on! We're currently accepting nominations from now until January 26 at 00:00 UTC. If you're interested in being part of the Drupal Association leadership and helping to represent your fellow community members, please apply! Nominees will be vetted publicly starting January 26, with voting finishing up February 7. Stay tuned for further announcements, and hope to see your nomination in the list. :) Drupal Association

---

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. September - December Events 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: 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. 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! 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!). Documentation Infrastructure Updates 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! Next Steps 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.

---

Busby is a clean personal blogging theme with it’s own options panel built with the UpThemes framework. This is Drupal port of the original wordpress built using HTML5. Soon to become a subtheme of fusion with all its wonderful theme settings and options. The wordpress theme was originally developed by http://wplift.com and released under GPLv2. Installation: Copy the files of the theme into your themes directory. Go to admin/build/themes and enable the theme. If you want to have the subscribers field automated, look into this modulehttp://drupal.org/project/subscounter To Do: 1.) Make busby a subtheme of Fusion enabling all the wonderful options that carry on from Fusion Core 2.) D7 port of Busby (High Priority)

---

Quite often we build websites for companies or organizations and then when finished we hand them off to a marketing person or department and let ...youtube.com

---

Configurable 24 column grid system at your fingertips! Mayumi is a girlie HTML5 sub-theme of Groundwork. "Mayumi" is an adjective in the Filipino language which describes someone who is shy, demure and soft. It is often used to describe what an ideal single Filipina should be. Key features of Mayumi: Google Web Font CSS3 Inherited from Groundwork: HTML 5 Web accessibility optimized with ARIA roles 24-column grid system based on 960.gs Supports one, two, and three-column layouts 15 regions with a special "Aside" region visible only in nodes. Optimized typography for all standard elements Advanced Theme Settings Powerful layout engine provides unlimited layout possibilities CSS Reset Collection of preset CSS classes HTML5 polyfill to support older browsers Formalize: HTML5 ready, progressively enhanced, cross-browser forms Icons for common Drupal form fields such as search, username, and password fields. and many more. Requirements See Groundwork's requirements

---

€79SKU: st-dev-resList price: €79Price: €79

---

€49SKU: adtprt14List price: €49Price: €49 respondrShortDesc: The ultimate Drupal 7 theme! Responsive + Touch optimized.Demo Site: http://www.sooperthemes.com/respondrdevpack: 869Drupal Core Version: 7Framework: Arctica+Tundraunique:  Respondr Design Concept Respondr visualizes your web content in the style of the digital age: Clean, minimal, content-focused and tastefully detailed. Respondr has all the features you need to wow your clients and woo your customers. Built on Arctica+Tundra, Flexslider support. Respondr is built on our new Arctica + Tundra framework. The base themes can be downloaded for free from Drupal contrib: Arctica and Tundra. Respondrs slideshows have touch/swipe support with the newly added Flexslider integration. popularity: 5Theme Type: All purpose Using Arctica base theme: Tundra Features: SlideshowKitDropdownKitFontKitColorPickerBackgroundImageKit

---

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!

---

Get Skeleton is a responsive and mobile friendly base theme, based on the Skeleton boilerplate. The goals of this theme are: Responsive Mobile Friendly Grid layout Light weight Easy to extend and subtheme SEO friendly Remain consistent and track closely with the Get Skeleton system. Many thanks to Dave Gamache for developing the original Skeleton boilerplate.

---

This colorfull theme was made specialy for blogging.Features: Three columns design 5 regions for blocks Has 4 variations of colors: gray, blue, orange and green Tested with Firefox, Chrome, Opera and Safari

---

Cast: Lullabot Tags: drupalvimeo.com

---

Base theme for sites by Bartlett Interactive.

---

Configurable 24-column grid system at your fingertips! Negosyante is a blue and grey HTML5 sub-theme of Groundwork. "Negosyante" is a word in the Filipino language meaning a person of affairs, engaged in business. An entrepreneur. Key features of Negosyante: Configurable block backgrounds CSS3 Superfish support Inherited from Groundwork: HTML 5 Web accessibility optimized with ARIA roles 24-column grid system based on 960.gs Supports one, two, and three-column layouts 15 regions with a special "Aside" region visible only in nodes. Optimized typography for all standard elements Advanced Theme Settings Powerful layout engine provides unlimited layout possibilities CSS Reset Collection of preset CSS classes HTML5 polyfill to support older browsers Formalize: HTML5 ready, progressively enhanced, cross-browser forms Icons for common Drupal form fields such as search, username, and password fields. and many more. (Demo) Requirements See Groundwork's requirements. Installation 1. Install Skinr and Groundwork (if you have not done so already) 2.. Download Negosyante below. 3. Extract the downloaded file and place the negosyante folder in your Drupal installation under one of the following locations: sites/all/themes sites/default/themes sites/example.com/themes (See http://drupal.org/getting-started/install-contrib/themes for more information on folders.) 4. Enable Negosyante. Log in as admin in your Drupal installation and go to Administration > Appearance > List (http://example.com/admin/appearance/list). Click the "Enable and set default" link below the theme's description. Note: You do not need to enable Groundwork to use Negosyante. Recommended modules Extend Negosyante with the following modules: SuperfishThe navigation bar of Negosyante has support for the "space" styles included with the Superfish module Credits Development of the Groundwork project is sponsored by Noceda Media Lab.

---

Ice Clean is a fixed width (980px), clean, simple, elegant, and beautiful theme for Drupal 7.x. The theme is not dependent on any core theme or module. Its very light weight with modern look. Features of Ice Clean The theme support one / two / three column. Drop Down menu. 11+ collapsible blocks region Tableless Use of Google Web Fonts Compatible and tested on IE7, IE8, IE9+, Opera, Firefox, Chrome Support custom logo and favicon Live Demo Ice Clean theme live demo Author: Designed and developed By DrupalNetworks.com

---

This is a Facebook Base theme build with Zen. It has 2 subthemes: Canvas and Tab. It's the normal Zen theme with a different typography and colorschema. It's meant to use in conjunction with Drupal for Facebook module, where this theme serves you the Facebook 'look & feel' right out of the box. Currently I am working on forms/webforms & sidebar css. I am open for improvements or ideas.

---

The groundwork has already been laid. Reduce your custom theming time by using a theme framework with a powerful layout engine and sensible generic style defaults. Use it as is, as a theme with simplistic/minimalistic design, or as a base theme for faster theme development. Here are the key features of Groundwork: HTML 5 Web accessibility optimized with ARIA roles 24-column grid system based on 960.gs Supports one, two, and three-column layouts 15 regions with a special "Aside" region visible only in nodes. Optimized typography for all standard elements Advanced Theme Settings Block source ordering per region Powerful layout engine provides unlimited layout possibilities CSS Reset Collection of preset CSS classes HTML5 polyfill to support older browsers Formalize: HTML5 ready, progressively enhanced, cross-browser forms Icons for common Drupal form fields such as search, username, and password fields. and many more. What is Groundwork? Groundwork is a theme framework. It was built to help you design beautiful Drupal websites faster and more efficient. As its name implies, it's a groundwork which comes already with sensible generic style defaults, CSS browser hacks, collection of preset CSS classes and more. Because of Groundwork's basic generic style, you may also wish to use it as is, as a structured minimalistic theme. Groundwork uses a 24-column grid system based on the 960.gs. Efficient layout options available give endless possibilities, which makes the Groundwork suite of themes extremely versatile. Customizing a website to specific layout and design is very easy. Requirement The Skinr 7.x-2.x module is required. Blocks in most regions will all be 940px wide if you opted not to use Skinr. Skinr module for Drupal 7.x, at present, has not released a stable version yet and is still in the process of ironing out some things. A known problem affecting Groundwork: When updating a module and running DB update, Skinr seems to lose all your Skinr settings, but they're not. Flushing the cache will apply your settings back. Backing up (Exporting) your Skinr settings is recommended if you will be doing major changes in your site, Sub-Themes It only takes 3 steps to create a sub-theme of Groundwork. Copy the subwork folder Rename the 3 instances of the name subwork. the folder name "subwork"; the filename of the .info file "subwork.info"; the name of the theme inside the .info file "name = Subwork" Design away with the well-commented local.css. Creating a sub-theme of Groundwork is a breeze! If you wish to use a ready-made sub-theme instead, here are some: Negosyante "Negosyante" is a word in the Filipino language meaning a person of affairs, engaged in business. An entrepreneur. Demo: http://negosyante.noceda.no Project Page: http://drupal.org/project/negosyante Mayumi "Mayumi" is an adjective in the Filipino language which describes someone who is shy, demure and soft. It's often used to describe what an ideal Filipina should be. Demo: http://mayumi.noceda.no Project Page: http://drupal.org/project/mayumi more coming very soon... Live Support Feel free to chat with me on IRC channel #drupal-support whenever I'm there. More info on Drupal IRC at http://drupal.org/irc Suggestions? After using Groundwork on your sites, what do you want to see included in Groundwork core. Write a feature request. Collaboration Are you interested in co-maintaining Groundwork? Let's make Groundwork better all together and provide ourselves and others an awesome theme framework. Contact me: http://drupal.org/user/70994/contact Credits Development of the Groundwork project is sponsored by Noceda Media Lab.

---

By changing settings in the included Adobe Fireworks document, users can easily change theme settings (e.g. colors, backgrounds, etc.) and export the images to be used in the site.

---

Register Now to learn and network for Florida DrupalCamp February 11 and 12 2012! The Drupal content management system is one of the most popular CMS's in the world, and is used to power sites like WhiteHouse.gov, PGA.com, Grammy.com, Standford.edu, and more! Learn this powerful content management system at the 4th annual Florida Drupal Camp in Winter Park! The Florida Drupalcamp is the annual regional gathering of Drupal developers, decision makers, end users, and site administrators. The event is friendly and open; provides hands on learning; and active networking. Drupalcamp Florida Features a Multi-Track Learning Experience: Beginner Track - Enthusiasts, first-timers, non-programmers, webmasters, and marketing people, as well as anyone tasked with updating sites will benefit from this practical overview of Drupal. Learn the basics, get practical tips, tap into great resources and gain insight as a real site is built before your eyes. Dedicated Drupal Hands-On tracks for programmers, webmasters, themers and others seeking to get insight and best practices from the brightest Drupallers we know. A non-profit track for non-technical people, decision makers, and those who need to get a better understanding of what Drupal can do. You'll learn the basic principals, benefits, challenges and advantages to using Drupal. Birds of a Feather sessions will be presented in a dedicated room throughout the day where you can get help, get some work done, or create your own unconference. Oh yes, and networking! After the last screen goes dark, the Florida DrupalCamp social scene lights up with an evening designed for fun and fellowship in Winter Park. It's a chance to get to know the experts, meet the newbies, and develop a few new friendships. 3rd Annual "Coding for a Cause" - We will be building a site for a 501(c)3 organization based on an open selection process. The chosen organization will receive a customized Drupal website built by dozens of volunteers in an all-day marathon Drupal coding event on February12th. Get more details on our website about how you can help! The cost of this event is only $25 and include lunch, a t-shirt and swag. Register at http://FLDrupalCamp.org today! AttachmentSize FL_Drupalcamp_Flyer_2012.pdf491.3 KB Gainesville

---

Jess (Drupal.org username xjm) is a Drupal developer, core contributor, module maintainer, and mentor, and just plain all-around awesome! She is a web developer for the University of Wisconsin's Department of Family Medicine. She also volunteers at the University of Wisconsin-Madison Arboretum. Jess has made many contributions to Drupal, including roles as: maintainer of the Taxonomy Access Control and Taxonomy Lineage modules, among others. co-maintainer of the Taxonomy module in Drupal core. active participant in the API documentation clean-up sprint happening in Drupal 8, as well as efforts to clean up the entity system. co-lead of the Clean Up Core community initaitive. friendly and knowledgeable mentor to new contributors. organizer of the twice-weekly core office hours to help get new core contributors involved. inventor of the Issue summary initiative to give new contributors something very valuable but approachable as their first core contribution: reading through and summarizing long, difficult issues to help speed along their review and commit. Sites she's built with Drupal include the UW Department of Family Medicine's public and intranet websites, an organizational knowledge base, and various small sites. Jess attended her first DrupalCon in Chicago, and is coming to DrupalCon Denver as well, where she is planning to run an in-person core office hours sprint! We asked Jess a few questions: Tell us a bit about yourself! What is your background, or things that interest you outside Drupal? I love the outdoors. I often bike 30 miles a day in the summer (that's 50 km for those of you using reasonable systems of measurement). I camp, hike, and do ecological restoration, and I probably can identify more plant species than you. ;) I also have other crunchy pastimes like gardening, cooking, and making candles. (I have not yet attempted to weave my own yogurt.) I read a ridiculous number of books, and I speak bits of five foreign-to-me languages (though I can only carry on a conversation of any substance in French). I think General Relativity is awesome and I love mathematics and statistics. I'm also a nerd. You probably got that already. How and why did you start contributing to Drupal core? I opened the 7.x-1.x branch of TAC with no knowledge of Drupal 7. 80% of TAC's upgrade from D6 was straightforward, but then I crashed headlong into the Field API and D7's entity form handling. I started asking a lot of questions, and catch was incredibly patient and helpful. I connected with someone in IRC who had a similar issue with entity forms, and we came to the conclusion that we needed a hook_field_widget_form_alter(), which did not yet exist in the API. We posted an issue for that, and before I'd finished my lunch, sun had written a patch for it. Around then two things happened. First, the issue summary functionality was deployed on Drupal.org, and I saw a way that I could actually do something useful in the core queue in exchange for all the help I was getting. My hope was that issue summaries would widen the "review bottleneck" by saving reviewers and core committers time. I started writing an issue summary every day for major and critical core issues. Every summary I wrote also taught me something about Drupal. A few days later, chx asked in IRC for someone to reroll a patch with a couple of minor fixes. I thought, hey, I can do that, and it ended up being my first core commit credit. For chx, who has written more of core than pretty much anyone, it would have been a triviality, but for me, it was the realization that I was actually capable of contributing, at least in a small way. That opened a door for me. In the process of writing my once-a-day issue summaries, I came across some issues in subject areas I already understood well, so I worked on the patches as well as the summaries. Then I learned how to write automated tests for TAC, and consequently I was able to start contributing automated tests for core as well. The more issues I worked on, the more I understood, and the more I could do. Kind of an avalanche set off by a pebble, by the fact that people like catch and sun and chx took the time to be supportive and encouraging. So that's why I have my Drupal.org profile tagged with "full frontal nicety" (cr. webchick). Be nice. Go out of your way to be helpful and kind, because it can make all the difference to a budding contributor. Can you explain some of the benefits of getting involved with the community and what you get out of it? The best part is having co-ownership in the software that I use every day in my job. Being able to help resolve problems I encounter is very empowering, as is knowing where I can turn when I get stumped by something. It's also wonderful to collaborate with talented, engaging people from all over the world. Now, if I were talking to my boss (hi Justin!), I'd emphasize that being actively involved in the project is good business strategy: Filing and participating in issues helps resolve real, production problems for our sites in maintainable ways. Contributing code back to the community means that there are thousands of other sites to help debug and test that code. Participating in discussions about Drupal core and contributed projects helps us make informed decisions. What motivates you to help out others to get involved? Two things: For years, I was active in contributed module queues, but terrified of core. It took meeting a couple of friendly Acquianauts at DrupalCon Chicago to show me that core developers were actually completely approachable human beings. ;) So I'd like to extend that same realization to everyone else who might be in the same place I was. Drupal 7's fantastic success also means that there are a lot more people using Drupal and filing issues. There's also a chronic shortage of experienced patch reviewers, which means issues that could well be fixed by an existing patch get stuck and languish. We as a community need to invest in connecting new contributors with the work they can do now. What's your advice to new would-be contributors? Join Drupal IRC channels. Lurk in #drupal-contribute. Check out core office hours or the Novice queue. Try your hand at contributing an issue summary. If you take the time to carefully read and understand an issue, you'll likely learn a lot about a particular topic, and also get a feel for how the community resolves issues and makes decisions. Code is not the only way to contribute--not even for core. (Just today, a self-proclaimed "not a PHP nerd" unblocked a 4+ year old core issue by doing manual testing.) When someone gives you feedback, embrace it! If code is your thing, learn to love the patch reviews you get. Even if all someone says is that a code comment is unclear, they're helping your patch move forward. Pay attention to the feedback that experienced contributors give others, as well. You can learn a lot by watching what reviewers look for. Above all, be patient and don't get discouraged! Sometimes it can take a long time and a lot of iterations for issues to be resolved. And, if you are unsure about anything, ask the nice folks in IRC. What do you do with Drupal these days? Well, it looks like I'm finally going to get to upgrade my department's sites to D7, which is a huge relief. I'm looking forward to experimenting with responsive frontend design and all the cool stuff I missed out on during a decade of supporting pixel-perfect IE6. (We finally decided to drop support this year.) How did you get started in Drupal? What were your stumbling blocks, and what were the moments that things started to click? The full version of that story requires a couple drinks, or possibly a therapist. However, I'll say that cowboy-coding a CMS with 2-3 others back in 2003 taught me the comparative value of open source projects, and that I picked Drupal for a client in 2006 primarily because the Drupal community seemed to be active and thriving. The thing that stumped me the most in those first few months with Drupal 4.7 was probably access control; I spent weeks of testing and hacking trying to implement the permission scheme I wanted. (I installed TAC very briefly in D4.7... and uninstalled it as fast as I possibly could. I'm not sure if it's irony or fate that led to me maintaining it.) A few turning points for me were learning firsthand the bad things that could happen if I hacked core; the release of the Zen theme, which brightened my relationship with Drupal's frontend considerably; and my discovery of hook_nodeapi() and hook_form_alter(). Oh, and when I got over the idea that "I was a developer and knew how to write SQL" and realized that Views was pretty powerful. ;) What's your favorite restaurant in Madison? That might be the toughest question here, because we have a lot of amazing restaurants! In this context, I think the honor must go to Bradbury's, where I've written a whole lot of code, issue summaries, and so on; not to mention papers on topics ranging from the ecological history of Cherokee Marsh to the sociolinguistics of the distinction between Hindi and Urdu. (This is what happens when you go to college for over a decade.) Bradbury's has the best coffee in town, plus a rotating, seasonal menu of sweet and savory crêpes featuring local produce. What would Linnaeus do? Well, I'd love it if he could help me out with the Cyperaceae. If you think Drupal can be confusing, try identifying sedges sometime. Anything else to add? :) t5'''''''''''''''/ (This last contribution is from my cat Auri, who wisely considers my laptop to be her primary competitor for my attention.) Know of anyone else doing awesome things in the community? Nominate them for Community Spotlight!

---

This planning document produced a plan for the 2012 Drupal Association elections of at large directors that was approved by the DA board. The Drupal Association is holding its first round of elections for board members under its new governance structure. See the the elections announcement for background and details. To invite community input on how best to run the elections, we've outlined below some possible suggestions, along with their pros and cons. Please tell us what you think by posting comments, or add your ideas! What aims should a voting system meet? To clarify our best options in an election system, it may help to capture goals. What are we trying to achieve? Meet the requirements as set out in the DA bylaws and Election Committee charter. Provide a basis to evaluate the success of this initial round of elections and provide feedback and recommendations. Note: We are electing two community members "At Large" to sit on the board of directors of the Drupal Association. We are not voting for a governing body of Drupal. The Board does not "make law" for the Drupal project. The Board is a legal entity set up to administer an organisation whose mission is to "foster and support the Drupal software project, the community and its growth." See https://association.drupal.org/about for the specific ways it does this. Timeline In order to get new board members ramped up in time for DrupalCon Denver, the first in-person board meeting of 2012, we need to adhere to the following schedule: Have an open nomination period of 1 week. Potential board candidates submit a form with a description of their qualifications and motivations for applying. Voting period of 1 week. (see below for who gets to vote). 2 candidates are presented to the board for ratification. December 30- January 6 (2 weeks): Voting proposal open for public comment (this post). January 9 - January 13 (1 week): Drupal Association's Election Committee takes community feedback and prepares final voting proposal for Board of Directors, sets up whatever tools are required for election process. January 18: Voting proposal submitted to BoD for ratification (cross-posted to g.d.o). Assuming this is accepted.... January 19 - January 27 (10 days): Nomination process. January 29 - February 7 (10 days): Election process. February 8: Elected at-large members submitted to board for ratification. That means we need feedback as soon as possible! Issues to address Indirect elections It's important to understand that these elections are indirect. The DA bylaws read: There shall be two At-Large Directors, who are elected by the community and ratified by the rest of the Board to serve one-year terms. In other words, the community is electing what are essentially candidates for the board, who are then voted on by the other current board members. The process is similar in this way to the selection of "class directors" by the nominating committee. No formal criteria have been developed that the board might use in voting on either class or at large directors. In the case of the 2011-12 nominating committee's recommendations, two of the recommended candidates were declined (voted down) by the board. It's entirely possible that one or both of the two community-selected candidates will be similarly voted down. In this sense, it may be misleading to refer to this process as "elections", or at least to refer to it as community elections. It may be more accurate to describe it as a nominating process, to be followed by elections in which the board are the only voters. TBD: Can/should the DA clarify in advance criteria by which community-"elected" board candidates would be rejected? Doing so might provide greater certainty for community members participating in the process. What will occur in the case that one or more of the suggested candidates is not accepted by the board? Will the candidates with the next most support be put forward? Will there be new elections? Name recognition Vote-based electoral systems are sometimes criticized for favouring candidates who are better known, whatever their merits might be. Name recognition alone is said to be a significant factor influencing voting. In the Drupal community, certain types of community members and contributors may be more prominent than others, giving them a relative advantage going into elections. For example, someone who contributes significantly to Drupal documentation or to local or regional Drupal community organizing may be relatively invisible to the broader Drupal community. In contrast, a Drupal developer who maintains a widely used module or contributes prominently to Drupal core may have a very high profile and broad name recognition among Drupal community members. Some Drupal community processes exist that may influence name recognition of individuals. These include: * Syndication on Drupal planet. An individual with a syndicated blog may have higher name recognition than one without. * Profiling in the Drupal community spotlight. The factor of name recognition may increase the relative importance of providing means for candidates to become known to the electorate, through e.g. debates, forums, and candidate profiles. What should be required for nomination? One facet of the election process that needs to be decided is how nominations happen. Should prospective board members nominate themselves, or should they be nominated by the community? Or some combination thereof? Criteria for evaluating options The DA bylaws state: At-Large Directors shall reflect and represent the Drupal community at large. Criteria to evaluate nomination requirements might include: * is likely to identify candidates with the ability to reflect and represent the Drupal community * is not overly restrictive--does not pose a major hurdle to Drupal community members wishing to run * can be easily confirmed Note that existing Drupal Association board members or members of the DA's advisory board are not eligible for election to at-large seats. Here are some options, as well as advantages and disadvantages: Self nomination only Details: Nominations come from individuals willing to run themselves Advantages This eliminates the possibility of adding someone to the ballot who has popular support of the community, but who is unwilling or unable to serve on the board of the Drupal Association. Disadvantages May lead to candidates that do not have support of the larger community Nomination by others Advantages Would help identify people the community would like to see on the board. Disadvantages Could end up nominating people who do not want to serve. Requires a vetting process of nominees so votes do not get cast for invalid candidates. May lead to many candidates. Nomination by defined Drupal community entities Entities could include: * Drupal User Groups * Teams such as security, documentation, infrastructure Advantages Would help identify people the community would like to see on the board. Disadvantages Drupal entities may not be set up to make such decisions, especially to do so quickly. Could end up nominating people who do not want to serve. Requires a vetting process of nominees so votes do not get cast for invalid candidates. Nomination by self AND/OR others Candidate can nominate themselves, but must be seconded by someone else. Candidate, if nominated by others, must accept nomination. Advantages eliminates the possibility of adding someone to the ballot who has popular support of the community, but who is unwilling or unable to serve on the board of the Drupal Association. help identify people the community would like to see on the board. Disadvantages None. Combines the advantages of two of the other options, and mitigates against the disadvantages of self nomination only or nomination by others. Qualification to vote Obviously, one of the most important aspects to elections is who has the right to vote on these members. There are many facets that could be used to determine whether someone is a member of the community or not; some easier to check than others. Criteria for evaluating options A key question to consider options against is: who are we aiming to identify by our voting eligibility criteria? The DA bylaws say that the at large directors shall be "elected by the community", presumably the Drupal community. So who is the Drupal community we're trying to capture in our voting eligibility criteria? This is difficult to define, and not necessarily needed at the moment, but should be recognized that this needs to be defined at a later date. Note that there will be additional elections. It's ok to make decisions that apply for the 2012 election and work out better in future elections. (Agile FTW :P) We just need to be very clear about it. Constituents of the Drupal community might include: NOTE: decent consensus that the decision for this election will be an interim decision for the sake of time, and that we will continue to define voting elegibility further for next year. Primary * Participants in Drupal sites like drupal.org and groups.drupal.org. (ie. anyone with a D.o account) * Drupal users - who are these? (difficult to define in a tecnical sense) * DA members (ie. anyone with a indiv or org membership) Secondary * Participants in Drupal conferences or events. * Organizers of Drupal events. (redundant to g.d.o membership) * Owners of Drupal shops and consultancies. * Members of Drupal user groups. (redundant to g.d.o membership) * Contributors of Drupal documentation. (redundant to d.o account) * Contributors of Drupal translations. (redundant to d.o account) * Volunteers with the Drupal Association. * Contributors to Drupal code--Drupal core and contributed modules, themes, etc. (redundant to d.o account) * Financial contributors to the Drupal Association or other Drupal-related projects. * Drupal contractors, site builders, and Drupal shop staff. * Drupal user interface designers. Additional criteria for eligibility tests: Lend themselves to programmatic determination, rather than requiring a lot of manual confirmation. For example, can be used to construct a site with accounts for eligible voters based on available data on *.d.o sites. Here are some possible ideas we could use to identify voters, as well as their pros and cons. Other ideas welcome! Is an individual member of the Drupal Association by a certain date. Advantages Guarantees that the person is real Cost for becoming an individual member is relatively inexpensive (inexpensive for developed countries, but expensive for members in developing countries such as China or India) is not overly exclusive Disadvantages DA membership has yet to have any defined rights and, to this point, has only been cast as a way to support the work of the Association. There may be significant pushback from the community along the lines of pay-to-play. Is a member of drupal.org Advantages Broadly inclusive Disadvantages it's very hard to verify that these are "real people" and not fake accounts. Possible to tarnish the election results by bulk-registering accounts. Though one option could perhaps be to put a minimum time on the accounts, e.g. must be a d.o user for >= 1 year. Has a "Certified to Rock" rating that exceeds a given threshold The Certified to Rock algorithm to assign a numerical score from 1 to 11 "based on the strength of contributions to the Drupal community". Advantages Considers numerous criteria in identifying Drupal contributors Highly refined methodology Broadly recognized in the Drupal community Provides readily processed data Disadvantages May favour certain types of contributions over others Exact criteria are not visible to Drupal community Has attended a DrupalCon in the last year Advantages shows active involvement and interest in Drupal Disadvantages would exclude people whose input we value who were busy in the last year and/or cannot afford the travel and entry to the event. Has attended a Drupal meetup Advantages shows active involvement and interest in Drupal Disadvantages very hard to track unless we go by self-reporting in which case it's hard to tell they are not fake accounts Has made commits to Git Advantages Rewards people who help make our software awesome with a say in the board of the Drupal Association Disadvantages Leaves out significant portion of non-developer community members from the voting process. Leaves out important contributors to other aspects of the project, e.g. Documentation, User Experience. Not all commits are equal Has contributed to drupal.org Criteria could include: Has contributed documentation (link to page contributed prior to a given date). Is a manager of a group on groups.drupal.org (link to group). Maintains a project (link to project page). Advantages Recognizes various ways to contribute to Drupal. Disadvantages Relatively difficult to verify--would require either custom data processing or individual confirmation of each voter. How should the eligibility of voters be determined? This depends on what criteria we decide to use, but for now here are some ideas. * On the voting site, programmatically construct a list of accounts for eligible voters based on data available at *.d.o. Assign these accounts a role, "voter", that includes permissions relevant to * During the elections, provide a means - e.g., an issue queue on drupal.org - for anyone who believes themselves to meet eligibility criteria but has not already been assigned an account to apply for account creation. How should the community interview candidates? Once we have the list of nominees, the community needs to be given a chance to ask them questions, find out more about their stances on various issues and particular initiatives they wish to spear-head as part of the board. Criteria for evaluating options Allows Drupal community members with a relatively low profile to gain exposure. Enables electors to gain information from candidates on areas of concern to electors. Here are some ideas. Of course, these are not mutually exclusive and - time and resources allowing - we could use any or all. Comments enabled on candidate submission forms (e.g. "Nomination" node form with comments turned on) Advantages Allows drilling in to one candidate to learn more about them. Disadvantages questions (accusations, recriminations, etc.) are directed toward a single candidates. questions should be asked of all candidates and be open to response from all candidates Advantages having an open forum will, if nothing else, give a measure of a candidate's willingness and ability to express theirself Disadvantages Might get uneven coverge of candidates, depending on availability. All candidates meeting Have a meeting on IRC/phone that allows for "real time" questioning of candidates by community. Advantages More immediate feedback on questions Better chance to "get to know" prospective candidates. Disadvantages Leaves out people who cannot be there a given time. Technology may leave some members of the community out entirely. Where should the elections take place? Criteria for evaluating options Access to potentially sensitive data is subject to stringent access control. Work required is feasible within the time and resource constraints. Elector accounts can be programmatically created if/as required. drupal.org Advantages Easily accessible Disadvantages Requires vetting a new module for deployment on Drupal.org, will delay election process About 100 people, likely some of whom will be on the candidates list, have administrative access association.drupal.org Advantages Already has webform module deployed Fits well, since the elections are for the Drupal Association Easily accessible Disadvantages Off the "main" site About 25 people have administrative access (though likely none who are eligible for candidacy) A subsite for atlarge.association.drupal.org? Advantages Single purpose site with the functionality and security required to run the election. Can install relevant modules without worrying about impact on the functioning of D.O or A.D.O Becomes an historical record of board elections and outcomes. Potentially could be used for other democratic and transparency activities such as plebiscites, referendums, committee elections. Disadvantages We have to build and maintain a whole site. Who should carry out the elections, e.g., count votes? Criteria for evaluating options Only a small handful of extremely trusted people should be able to view who voted for whom. This preserves the ability for people to vote their conscience, even if that means voting against their boss or a co-worker/friend. d.o infrastructure team Advantages Disadvantages DA election committee Advantages Disadvantages HERE How should voting work? Then, finally, on the voting process itself. Here's some ideas, but we welcome others as well. Edit: Please discuss specifics in this new thread How should voting work for electing the "At Large" board members of the Drupal Association? http://groups.drupal.org/node/200143 Criteria for evaluating options Input is maximized from voters--the more voters whose preferences are considered, the better. The vote outcome is clear and unambiguous. The electoral system is comprehensible to those participating in the elections. There are available solutions (Drupal modules) to provide the solutions. The voting system can identify additional runner up candidates, in case this is needed if elected candidates are declined by the board. First past the post (FPTP) Every qualified voter gets up to two votes of equal weight. They are not permitted to cast more than one vote for a single candidate. The two candidates with the most votes (simple majority) are elected. For more information on this voting system see http://en.wikipedia.org/wiki/First-past-the-post_voting Advantages No need to sift through votes and perform calculations on first vs. second choices or similar voting mechanisms, a simple, anonymized count would be sufficient. Everyone universally understands how this works Disadvantages A candidate with the MOST votes doesn't necessarily represent the MAJORITY of voters. People tend to vote for candidates most likely to win to prevent wasting their vote. FPTP is a widely criticised voting system. Instant Run Off Vote / Preferential Voters rank all candidates in order of preference. The candidate with the least number of votes is eliminated, and the 2nd preference of those votes is transferred to the other candidates, and so on, until one candidate receives an absolute majority - or 50% +1 of all votes. For more information on this voting system see http://en.wikipedia.org/wiki/Instant-runoff_voting Advantages Ensures the outcome is more representative of the will of more voters. Disadvantages It is more complex to calculate the outcome (Note: Decisions module has implemented an instant run off algorithm) Questions for candidates What information should we ask of candidates? This might form the basis e.g. of an information sheet that all candidates are asked to fill in, with their responses being publicly accessible as a basis for evaluating them as candidates. * Name * Where located (e.g., city and country) * drupal.org user name, if applicable * Resource needs For the elections it looks like we'll need a range of web elements that may include some or all of the following: * A questionnaire for candidates and a publicly visible display of results. * Likely solution: Webform module. * A forum for for candidate questions. * Core forum module? * One or more real time meetings. * Video conferencing? * A voting system * If first past the post, ? * If instant runoff/preferential perhaps the Decisions module? TL;DR (aka, The Short Version) We welcome community thoughts on the following questions as they pertain to filling two community-elected board positions for the Drupal Association: How should nominations work? Should interested parties self-nominate for an at-large position, or should we take suggestions from the larger community? Other? Who should be able to vote during elections? Anyone with a Drupal.org account? Anyone who's a paid Individual Member of the Drupal Association? Or some other criteria? What should the community "vetting" process of prospective candidates look like? Comments on individuals' applications? A forum of some kind for the community to raise questions/issues and offer all candidates an opportunity to respond? Some kind of "real-time" meeting? Where and how should the actual elections themselves take place? Webform module, locked down to only a select set of members to view results? A public voting process on Twitter or IRC? What are your ideas? Thanks very much for your participation in a very important step for the Drupal Association's community accountability! Drupal Association

---

New hands-on trainings are now open for registration when you register for DrupalCon Denver 2012. A full listing has been added online where you can read more about the trainings going on Monday, March 19, 2012 before the conference kicks off. Training is offered at a much reduced rate compared to standard full day training offerings and it's a great opportunity to save on travel costs if you are attending DrupalCon already. All trainings will be held in the Convention Center, the venue for the conference March 20 - 22, 2012. What Trainings Are Available? Deploying Drupal at Scale on Microsoft Platform Drupal 7 Module Development Site Building and More - A Mentored Training from Build a Module.com From PSD to Drupal Theme: A step-by-step approach to creating your first Drupal theme Rules Mastery Responsive First: Design and build a site for all devices Absolute Beginners Guide to Drupal Making the Switch to Drupal: The Developer's View Security: Process, Code & Hands-on Training Code-driven Development: Use Features Effectively Awesome UX Deliverables and Process This array of professional trainings offers something to all levels of experience. You can register for trainings at the same time you register for the conference, or if you have already registered, it's easy to get the discounted package rate, too. DrupalCon is a great way to get so much of the community in the same place at the same time; if you haven't already, register today and sign up for a training. In the spirit of giving, a special promotion is now available to anyone who registers or has already registered: purchase your tickets by Dec. 31, 2011* and receive a special edition DrupalCon T-shirt (*23:59:59 UTC/GMT -7).

---

€49SKU: adtprt12List price: €49Price: €49 deviantShortDesc: Core values of this design are confidence and corporate efficiencyDemo Site: http://www.sooperthemes.com/deviantdevpack: 805Drupal Core Version: 7Framework: Arctica+Tundraunique:  Deviant Design Concept Deviant communicates on a professional and efficient level. The design features sharp edges and a strong focus on content to communicate a proficient personality. Built on Arctica and Tundra base themes Deviant is built on our new Arctica + Tundra framework. The base themes can be downloaded for free from Drupal contrib: Arctica and Tundra. starterkit: popularity: 5Theme Type: Enterprise Using Arctica base theme: Tundra Features: SlideshowKitDropdownKitFontKitColorPickerBackgroundImageKit

---

€79SKU: st-dev-helList price: €79Price: €79

---

€0SKU: touchproList price: €0Price: €0 touchproShortDesc: Touch optimized magazine theme. Demo content included.Demo Site: http://www.sooperthemes.com/touchprodevpack: 0Drupal Core Version: 7Framework: Arctica+Tundraunique: Download TouchPro for free on Drupal.org TouchPro Design Concept TouchPro is a touchscreen optimized responsive design, suitable for publishing any content on any device. It's a playfully colored design with lots of CSS3 features Built on Arctica and Tundra base themes HelloFolio is built on our new Arctica + Tundra framework. The base themes can be downloaded for free from Drupal contrib: Arctica and Tundra. starterkit: popularity: 4Theme Type: Community, Magazine Using Arctica base theme: Tundra Features: SlideshowKitDropdownKitFontKitColorPickerBackgroundImageKit

---

€49SKU: adtprt13List price: €49Price: €49 hellofolioShortDesc: The portfolio theme with a friendly attitude. Demo content included.Demo Site: http://www.sooperthemes.com/hellofoliodevpack: 809Drupal Core Version: 7Framework: Arctica+Tundraunique:  HelloFolio Design Concept HelloFolio talks your visitors into viewing your portfolio and making contact. The beautifully paired Lobster and Cabin fonts take turns to draw attention and inform. Built on Arctica and Tundra base themes HelloFolio is built on our new Arctica + Tundra framework. The base themes can be downloaded for free from Drupal contrib: Arctica and Tundra. starterkit: popularity: 4Theme Type: Portfolio, Informal Using Arctica base theme: Tundra Features: SlideshowKitDropdownKitFontKitColorPickerBackgroundImageKit

---

Deviant theme + PSD source files €79SKU: st-dev-devList price: €79Price: €79

---

Drupal 7.10, a maintenance release with numerous bug fixes (no security fixes) is now available for download. Several major bugs, including one causing errors with the 5.x branch of Drush, have been fixed this release. See the Drupal 7.10 release notes for a full listing. Download Drupal 7.10 Upgrading your existing Drupal 7 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. Security information 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 includes the built-in Update status module, which informs you about important updates to your modules and themes. There are no security fixes in this release of Drupal core. Bug reports Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of January (January 25). Changelog Drupal 7.10 is mainly a bug fix release. The full list of changes between the 7.9 and 7.10 releases can be found by reading the 7.10 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log. Update notes - None at this time. Known issues - None at this time.

---

Start:  2012-01-19 09:00 - 2012-01-21 15:00 America/Mexico_City Drupalcamp or Regional Summit Organizers:  jackbravo koffer develCuy Joyita KarimB Español Toda América Latina celebra el mayor encuentro Drupal del año 2012! Por fin podemos anunciar oficialmente el lanzamiento del mayor evento Drupal del año 2012: "Drupal Summit Latino – Guadalajara 2012". Guadalajara (Jalisco - México) será la sede del segundo evento a nivel latinoamericano dedicado a Drupal los días 19, 20 y 21 de Enero de 2012, en el CUECA de la Universidad de Guadalajara. Tendremos un sin fin de conferencias dictadas por reconocidos y experimentados drupaleros provenientes de varios países de América Latina, Estados Unidos y Europa. Se espera la presencia de más de 400 participantes lo que será sin duda alguna, a nivel continental, la mayor concentración jamás vista de experiencia y conocimiento sobre el software de publicación de sitios Web más exitoso del momento: Drupal por supuesto! ¡ Te invitamos a proponer una sesión para Drupal Summit Latino 2012 ! Por favor ten en cuenta que la fecha límite para las propuestas es el 14 de diciembre 2011. ¡ Te invitamos también a patrocinar el evento tenemos distintos planes. Convertirse en un patrocinador de Drupal Summit Latino - Guadalajara 2012 es una gran oportunidad para apoyar el proyecto Drupal y para promover tu organización dentro de la comunidad de Drupal. Es una oportunidad única para conectar con los clientes, socios y proveedores de servicios de México y Latinoamérica. El evento está siendo co-organizado entre la comunidad de Drupal Latino y la Universidad de Guadalajara. Regístrate ya en la página web: http://gdl2012.drupal-latino.org English We've been preparing this for some time now, and are very excited to announce the second Drupal Summit Latino, to be held in Guadalajara, México. Mark your calendars for 19, 20 and 21 of January 2012. Drupal Summit Latino, Guadalajara 2012 will take place on the "Universidad de Guadalajara". Drupal Summit Latino aims at being an event to unite and bring together all the Drupal communities, companies and people around the Latin American and Brazil. Conferences, workshops and coding/documentation/translation sprint are being planned so it will be a great opportunity to learn and share with distinguished members from the Drupal community in the whole continent. Need help with a problem, looking for a Drupal related job, or looking to hire Drupal talent? Come to Drupal Summit Latino GDL 2012. The event is being co-organized between the Drupal latino community and the University of Guadalajara. Registration is open at http://gdl2012.drupal-latino.org Uruguay

---

Drupal 8 development has been underway for some time now and we're seeing increased activity around issues that aim to improve Drupal usability. What's been missing is an overview of where we should focus our time and energy when tackling Drupal user experience challenges. This post provides an outline of the topics we want to focus on to make Drupal 8 great. In a nutshell, we want to: Kick off some essential core UX design projects in the next months. We will work on the content creation experience, fields UI and extending Drupal. And last, we want to position the default profile(s) of Drupal core, and define a community-driven framework for making decisions on their directions. Read full article: Thoughts on D8UX Strategy. We are looking for feedback on the overall focus and specific topics. Web Experience Management

---

Harrah's--New Orleans, LA Thursday, December 8, 2011 at 9:00am until Friday, December 9, 2011 at 5:00pm.. Are you Drupal-curious or a die-hard Drupal fan? The best and brightest web developers, designers and those smart business owners, corporate and enterprise execs will gather to see how Drupal can bring the heat like Frank’s Louisiana Red Hot Sauce and enjoy the warm weather and charm of The Big Easy, New Orleans. If you are a web developers or website designer who wants to spice up your Drupal experience, you will benefit from the informative and interactive workshops, sessions and panels from some of the most influential people in the Drupal Community. Register for now for the Drupal on the Bayou Summit and be there training, workshops and sessions that will help you to take your Drupal skills to the next level. *Group discounts and student discounts available. Register at: http://www.drupalonthebayou.com/ Central Alabama

---

DrupalCon Denver is just 5 months away. While the organizing team is committed to keeping the event affordable - with a low ticket price of $350 and affordable hotel options - there are even lower cost options for some members of the Drupal community. DrupalCon Denver Scholarships The deadline to apply for scholarships for DrupalCon in Denver is tomorrow -- anyone who has not yet applied can do so online until November 18, 2011 midnight Mountain Time. The DrupalCon Denver scholarship program allows community members who would otherwise not be able to attend DrupalCon to benefit from the DrupalCon experience as the Drupal Community benefits from each scholar's attendance. Read about the eligibility requirements and get the link to the online form by visiting DrupalCon Denver's Scholarship webpage. Sprints at DrupalCon: More glorious than ever DrupalCon Denver will better highlight and accommodate contribution and code sprints throughout the conference. To support sprints, we're offering a limited number of free attendance tickets. Sprint leads can now register with their proposed focus, and should have a group of at least 3 sprinters together at the time of application. Applicants should be ready to describe in detail the goal (what you plan to improve) and desired outcome (what will be accomplished during the sprint). Sprints can take place at anytime during the conference; they need not happen only on the Friday following the scheduled sessions. Preference is given to sprints that plan for a full day's amount of work, even if it's spread out over several days. Preference is also given to sprints that align with the conference theme or the following categories: Documentation Drupal.org improvements Drupal Core (Drupal 8 Initiatives or Drupal 7 bug fixes) Top contrib projects or community improvements Applications have already started to roll in. You can apply online as a Sprint Lead. Sprint Lead selections will be announced in January. Check the official DrupalCon Denver website for the latest information. We are excited that DrupalCon Denver is still very affordable and also able to include even more programs to keep it affordable for the people in our diverse community who need and deserve a little more help. Correction: Previous posting of this said the deadline is November 17th, which is incorrect. The deadline is November 18th.

---

The Drupal Security Team was originally created in 2005. Though we handled security issues before that, we didn't have a team with proper infrastructure until then. At that time, Károly Négyesi (chx) was the team leader. In July 2006 chx changed his role in the team and I promoted Heine Deelstra to be the security team lead. Heine recently stepped down as the security team lead, and I'm pleased to announce that Greg Knaddison (or greggles on drupal.org) will be filling this role. Greg has been a consistent member of the security team and both Heine Deelstra, the security team members, and myself unanimously agreed that Greg is the logical person to head the Drupal Security Team. For those who don't know Greg, Greg helped write our free handbooks on security and wrote a book about Drupal Security. He has also talked about security and Drupal at many DrupalCons. Greg believes in my idea to automate where possible and empower project maintainers. In the coming weeks he will write blog posts to detail some changes made in the last year toward that vision and some tasks that still remain. As the Drupal Security Team lead, Greg will be the point person for the team. He'll be responsible for coordinating the security team's activities and for making decisions when consensus doesn't arise. Greg and I agreed on a target of 2 years for him to be in this role. If appropriate, he may continue in this role longer or be replaced before then, but this target helps to set an expectation about the time period. Setting this expectation should help Greg maintain enthusiasm for this role and increase the likelihood that our community will have continuity when that time is up. Greg works at Acquia and will be given 20% of his time to dedicate to the security team (in addition to using his own spare time). Please join me in thanking Heine for all the great work he did, and in welcoming Greg.

---

git.drupal.org, drupal.org and our sub-sites have a scheduled maintenance window on Tuesday November 15th from 5PM PST to 7PM PST (UTC-8). Note that this is not a downtime window for drupal.org, but a period of possible instability. git.drupal.org and git.drupalcode.org will have an actual downtime during this window. Watch drupal_infra on Twitter for real-time status updates. This maintenance window is to re-rack and re-VLAN our servers. Thank you for your patience.

---

DrupalCampNYC 10 will be the largest New York City Camp to date, with 500 anticipated attendees and over 30 high-quality sessions across a spectrum of Drupal-related disciplines. It's all happening on Saturday, December 10, 2011 at John Jay College in Manhattan, for the bargain price of $20. Your registration fee will not only cover a full day of top-notch Drupal content from some of the finest minds in our community, but breakfast and lunch as well. DrupalCamp sessions are created and presented by camp participants. For this camp, sessions will be organized into the following tracks: Development sessions might talk about topics including module development, security, tools and environments, best practices, etc. Site building sessions address topics around the Drupal admin, community-contributed modules and tools, and more. If it's not Development, and it's not Presentation, and it's part of the site creation process, it's probably here. Presentation encompasses design, front-end development, and theming. Business and end users is more geared toward the non-technical facets of Drupal. This might include project management, team dynamics, tips for content managers and editors, agency issues, marketing, and so forth. Sysadmin and performance is the track for things like hosting, database optimization, testing tools and protocols, CDNs, and various other topics. Within each of the tracks listed, there will be content suitable for Beginner, Intermediate, and Advanced Drupal professionals. Additionally, there will be New/Newish to Drupal sessions early in the day, to help bring up to speed those who do not yet have a deep knowledge of Drupal; birds of a feather sessions will allow participants to engage in open discussion around specific topics. Finally, each time slot will feature a Community Spotlight speaker. This speaker, drawn from the NYC Drupal community, is a recognized expert in his or her area of Drupal and will speak on a high-impact topic of his or her choice. Also of note: there are a few sponsorship opportunities still available. Benefits and levels are available here: http://drupalcampnyc.org/sponsors/how-sponsor The New York City Drupal community is a collection of friendly people that are eager to accept newcomers, who are always welcome to any event. Regardless of your experience with Drupal, or lack thereof, we warmly invite you to join us for DrupalCampNYC 10. Get know Drupal, grow your skills, share your wisdom, or just make some Drupally new friends. Tickets will sell out quickly, so register ASAP. See http://drupalcampnyc.org for full information and to reserve your seat! New York City

---

Klaus Purer is a member of the Drupal community who has been recently been extremely active with project applications. How active? In the last 30 days he has commented on almost twice as many projects as the next most prolific commenter. Even though he just got involved in the last month, he's tied for most reviews of the most projects in the last 6 months! How did you get involved with Drupal? I started to work with Drupal during my involvement with the students union at the Vienna University of Technology (Fachschaft Informatik) back in 2006. I was just a user at that time, posting articles and keeping the web site up to date. In 2008 I was looking for some work besides my computer science studies and ran into a job advertisement by jpetso. I found it very appealing because it mentioned “actively taking part in an open source project” and since I at least knew Drupal a little it was a great match. So I started at Pro.Karriere (now known as epiqo) as part time Drupal developer, I think I did my first patch for Comment CCK (porting it to Drupal 6). Another boost for my involvement was the Google Summer of Code program in 2009, where I did a project for the Rules module. Fago was a great mentor (and still is today). What do you do with Drupal these days? I finished my master thesis this year, which talks about the Web Service Client module. I’m working on eRecruiter, a Drupal 7 distribution for online job boards. I help fago to maintain Rules and sometimes Entity API, I really like to work with RESTWS and I sometimes have to do hackish, pure Drupal-work-around modules like Role Export. I am a Google Summer of Code mentor and I am proud what my student sepgil accomplished this year (Rules Link). I have some Drupal core patches here and there waiting for your review. You can find me on meetups of the Drupal Austria local user group. What got you started in the project application review process? I saw people whining online about the project applications issue queue and the huge backlog. I was curious how hard it could be to do a review, and I saw that it actually is pretty easy. Then I wondered how many reviews one person could do in 24 hours. I took some time in the weekend and slayed down around 130 issues. I got motivated by the progress and continued my work, now with the challenge to reach zero "needs review" issues. Haven't succeeded yet, but will go for it when I have time. I think it is crucial for the Drupal community to get more developers on board, so that not only the Drupal user base grows but also the developer base. What are some of your favorite moments from that process? I like it how fast projects can evolve from a crappy code base to a clean and polished version. It is great to see how people care about their work, want to learn and want to get it right. They are excited when they get approved and spread their motivation to others, even to myself.Another aspect is that I myself learn a lot being a reviewer. The most valuable things are the security reviews by greggles, that point out weaknesses in the code that could be exploited by an attacker. It really hurts when greggles shoots down an issue for security reasons that you RTBC’ed before, but I appreciate it as it grows my awareness about security issues and my knowledge how to identify them. Are there any cool projects you’ve learned about through that process? Yes, definitely. Of course people don’t do blockbuster modules like Views or Rules as their first Drupal module, but there are nice ideas like Fixed field, Guest, User Email Domain and many others that I have forgotten right now. What changes do you hope will come in the project review process? I would like to get more reviewers involved. We can automate the reviews a bit (I created a bash script to do some common checks, see PAReview.sh), but we need human approval anyway later in the process. There are plans to deploy some automation on drupal.org directly, but that long term effort does not solve the problem of lacking reviewers now. You can do a decent project review in 10-15 minutes, so if more people would just do one per day or one per week we would not have any problems. It looks like you’ve been to several Drupalcons. What is your favorite part of these events? The atmosphere of friendly human interaction. It amazes me how nice and welcoming all people are and how low the barriers of entry are. I like it that there are almost no hierarchies between the people and that you can talk to just anyone. Tell us a little about your background or things that interest you outside Drupal? I’m living in Vienna, Austria, and I’m a free and open source software enthusiast. I like to compare programming languages, so I hate PHP (if only Drupal were written in Python!). I’m interested in politics, ethics, philosophy and gender studies. I am a vegetarian and I support attac. Where to find Klaus: http://twitter.com/_klausi_ http://klau.si/ http://drupal.org/user/262198

---

Earlier this year the Drupal Association began a process to elect and build a new board. In July a call for nominations was made and the community responded with over 50 submissions. The nomination committee spent many weeks reviewing the nominations, following up with potential candidates, until finally submitting a slate of nominees, which was confirmed by the board. I'm happy to announce the new Board of Directors: Jeff Walpole (until 2014) Vesa Palmu (until 2014) Tiffany Farriss (until 2014) Cary Gordon (until 2013) Danese Cooper (until 2013) Mike Woster (until 2013) Angela Byron (until 2012) Mitchell Toomy (2012) Unknown - one open seat, to be filled The Board also approved Dries Buytaert (me) to fill the "founder role" in this year's Board of Directors. The Board's term will begin on November 1, 2011. The first meeting of the new Board of Directors will be on November 16, 2011. This will be followed by the Drupal Association Board Retreat in Chicago, December 9 - 11, 2011. Selection process A nomination committee consisting of over eight community members considered over 100 candidates before settling on the great groups of individuals that we're proud to welcome to the Drupal Association. We believe this Board brings a lot of expertise to the Drupal Association, as well as more diversity in terms of industry representation, agency size, skill sets, gender, and geographic location. As the Association has grown so has the extent of financial and community responsibility and this board represents a shift to better address those needs in order to build a strong Association to support our community. At-large / Community board seats To ensure solid community representation we will also begin the process of electing two "At-large Board Members". At large board members are nominated and selected by the community at-large with no prerequisites for nomination. We are currently looking at the best method to get community involvement and will begin the process very soon. Advisory Board The Board of Directors is a guiding force for the Association and helps to set strategic direction. However, we recognize that the board members do not have all of the answers. To advise the board we have sought out talented individuals with a wide breadth of experience and expertise to serve as the Association's advisers. Our advisory board is designed to grow and expand with the needs of the organization and the community. One of the many ways the Association is working to stay strongly connected to the community is by seeking out community leaders, influencers, and talented individuals that can lend insight into the direction of the Drupal to be advisers to the Association. The Association's advisers currently include: Kristof Van Tomme David Strauss Larry Garfield Kieran Lal George DeMet Bevan Rudge Greg Knaddison Laura Scott Khalid Baheyeldin Fernando Paredes García Moshe Weitzman Bill Fitzgerald We're growing One year ago the Drupal Association hired its first employees to strengthen our conference and our volunteer community. In that year Drupal.org surpassed a million nodes and hosts over 12,000 developer accounts. DrupalCon welcomed nearly 5,000 attendees and over 1,000 people have been trained at the past four conferences. Membership in the Association has also doubled in the past year and we are still growing. We are on target to have 2,000 individual members and over 750 organization members by the end of this year. This is an exciting time to be involved with the Drupal project and the Drupal Association, and I believe the new Board of Directors will help the Drupal Association get to the next level. So please join me in welcoming all the Board of Directors for the Drupal Association. Here are bios of each Board Member and a short introduction as to why each member was selected: Angela Byron The Drupal Association needs to make sure it doesn't lose connection with the developer community that made Drupal into what it is today. Angie with her self-made success and long time contributor is someone who personalizes the values of our community. Angie also provides continuity in the Drupal Association board. Danese Cooper Danese has a very strong track record in open source governance: the experience she gained beating the drums of Open Source at Sun, Intel, Wikimedia foundation and now the Gates Foundation makes her a strong Board Member. Tiffany Farriss Having served not only on the Drupal Association board but on the governance committee, Tiffany provides important continuity in the Drupal Association board. She brings experience in a mid-sized Drupal business active in the Drupal community, events (DrupalCon production), and financial skills, having served as the Drupal Association treasurer. Cary Gordon Cary played an important role in the professionalization process of DrupalCon and was member of the governance committee. Cary is the owner of a small Drupal business and as such is representing smaller Drupal shops. As a member of the previous Drupal Association board, Cary is also important for continuity. Vesa Palmu As a serial entrepreneur and owner of Mearra, Vesa represents the European Drupal business ecosystem. His company, a medium sized Drupal shop in Finland that is expanding outside of it's borders, is similar to many Drupal shops in the European market. Vesa has been one of the organizers in the Finnish Drupal community and he's the informal national representative for Finland on the Drupal Association's European community dinners. Next to his professional experience Vesa brings affinity with the world of NGO's through his involvement in several smaller not for profits and the Finnish Red Cross. Mitchell Toomey We chose Mitchell because as a senior employee of the UNDP he brings insights in Drupal's role at big Drupal customers and at international governmental organizations more specifically. Mitchell leads an international team using the Teamworks Drupal-based intranet application and active in six regional hubs throughout the developing world with a current focus on Africa. He has an MBA in Organizational Behavior and Information Technology. Jeff Walpole Jeff was selected because on top of his business experience, he brings key insights on the use of Drupal in government and the Drupal distributions/products ecosystem. As the CEO and co-founder of Phase2 Technology, Jeff is a business leader in the Drupal community. He knows what it takes to build a multi-million dollar services company, and to invest in and market Drupal products. Mike Woster Drawing from his experience as the COO of the Linux Foundation and holder of an MBA, Mike has strong experience in running a tech non-profit. His knowledge of the tech non-profit world should give the Drupal Association insight into what financial and organizational models the Drupal Association might consider and how those would impact the community. His MBA from Kellogg School at Northwestern University has been put to immediate use in his role at the Linux Foundation interacting with lawyers, reading financial reports, and managing a distributed staff. His undergraduate degree in Computer Science from Texas A&M University and industry experience as a developer ensures he understands the “tech” side of a tech non-profit. Dries Buytaert Dries Buytaert is the original creator and project lead for Drupal. Dries also co-founded the Drupal Association and served as president of the Drupal Association since its start. He is also co-founder and chief technology officer of Acquia, a venture-backed Drupal company with 160 employees. Dries is also a co-founder of Mollom, a small web start-up that helps you stop website spam. Dries holds a PhD in computer science and engineering. In 2008, Buytaert was elected Young Entrepreneurs of Tech by BusinessWeek as well as MIT TR 35 Young Innovator. Dries brings community experience, business experience and continuity to the Drupal Association. As native of Belgium that moved to the US less than two years ago, and that travels extensively, Dries is able to represent the international ecosystem.

---

English / Castellano DrupalCamp Foz 2011 Foz do Iguaçu, Brazil October 19-21, 2011 Written by Nick Vidal Photo Credits: Saulo Amui. I bet Dries never saw so many water drops in his life! Introduction The Drupal Latin community has been trying to convince the Drupal Association to organize a DrupalCon outside of the North America / Europe axis since 2009 without much success. One of the last attemps was the Drupal Association planning to hold a DrupalCon together with Latinoware, one of the largest open-source events in Brazil, but it didn't work out and, with 50 days left to Latinoware, the Drupal Association passed the buck to whoever would take up the challenge of organizing a DrupalCamp instead. Obviously 50 days is not a lot of time to organize an event of this magnitude. Nevertheless, I thought it was important to give my best try to prove that we, as a community, can organize a DrupalCon in Latin America! Why is that so important? Because it breaks the long overdue pattern of holding DrupalCons only in North America and Europe. Because it expands Drupal to new horizons and fosters new opportunities in places where it's most needed! If the Latin community can organize a DrupalCon, so can Asia. If Asia can do it, so can Australia. If Australia can do it, so can Africa! The Venue DrupalCamp Foz 2011 took place in conjunction with Latinoware 2011 in Foz do Iguassu, Brazil on October 19-21, 2011. Over 4.000 people were part of the eighth edition of Latinoware. The Latinoware venue was Itaipu's Technology Park, situated inside the Itaipu Dam. The Itaipu Dam is the world's largest generator of renewable clean energy. Considered to be one of the seven modern wonders of the world, this magnificent structure is located on the border of Brazil, Paraguay, and Argentina. Besides the Itaipu Dam, Foz do Iguassu is also known for the Iguassu Falls, considered to be one of the seven natural wonders of the world. The Venue provided by Latinoware was really beautiful, and Latinoware took care of the audio/video equipment, video recording, Internet access, receptionists, translators, security guards, transportation, coffee-break, lunch, and even a Rock concert! The Organizers The main organizers of Latinoware were Cesar Brod and Joice Käfer. They both did a fantastic job organizing the event and offered a tremendous support for DrupalCamp Foz during the whole period. They were the ones responsible for convincing Dries Buytaert to come to Brazil for the first time. Also, they negotiated with Latinoware to pay the expenses of two DrupalCamp Foz organizers from Brazil and two DrupalCamp Foz organizers from Latin America. I was the main organizer of DrupalCamp Foz, and I chose Pedro Faria, a Drupal and PHP member from Rio de Janeiro, to help me. From Latin America, I chose Fernando Paredes Garcia, the previous organizer of the Drupal Summit Latino (that took place in Lima, Peru in January 2011), and Joaquin Contreras, the next organizer of the Drupal Summit Latino (which will take place in Guadalajara, Mexico in February 2012). I wanted to use this DrupalCamp as a meeting point to create a bridge between the Drupal Summits. These Drupal Summits are a demonstration of the power of the Drupal Latin community to organize events. The Sponsors Most sponsors need at least 3 months to allocate resources for a sponsorship, but we didn't have that much time, so we mostly had to rely on our own social network to find sponsors and speak directly with CEOs to speed the process. Fabiano Sant'Ana provided our first Gold Sponsorship by putting us in touch with José San Martin, from Chuva Inc (Brazil). Later, Pedro Faria put us in touch with Saulo Amui, from HostSH (Brazil), who offered a Bronze Sponsorship. Next, Leandro Nunes and Alex Weber from Webdrop (Brazil) got in touch with us and offered a Silver Sponsorship. Franz Glauber put us in touch with Bob White from Trellon (U.S.), who kindly offered a Gold Sponsorship. I was able to negotiate a Gold Sponsorship with Jeffrey McGuire from Acquia (U.S.). And finally, Fernando Paredes Garcia put us in touch with Juan Santiago from Santex America (Argentina) for a Diamond Sponsorship. Each CEO had to personally look into this matter and make it happen really fast, so we are very grateful for their amazing support of the Drupal Latin community. The Speakers We didn't have much time to make a call for participation neither. We only gave a 2-week time-frame for speakers all over Brazil and Latin America to submit their talks, but the feedback was amazing and we even had to cut some talks in the end. The selected speakers were from Argentina, Bolivia, Brazil, Mexico, and Peru (as well as Belgium and Greenland). They were: Alex Piaz, Capi Etheriel, Diego Teixeira, Dries Buytaert, Everton Pasqual, Fabiano Sant'Ana, Fernando Paredes Garcia, Franz Glauber, Henrique Recidive, Javier Reartes, Joaquin Contreras, José San Martin, Karim Boudjema, Leandro Nunes, Nancy Contreras, Nick Vidal, Pedro Faria, Rasmus Lerdorf, and Tiago Palacios. Thanks to our sponsors, we were able to offer free accommodation to all speakers. The Audience With DrupalCamp Foz 2011 being held at the main auditorium, with a capacity for 1000 people, we had really high expectations. But Cesar Brod, an experienced organizer, warned us that he wasn't expecting us to fill the auditorium, specially with only 50 days to organize the event. And in the end, he was right. This just proves that you can't organize a huge event in 50 days! The Drupal community needs time to organize themselves, to talk with employers, to buy plane tickets, to make hotel reservations, and to gather together. We had everything ready to receive those 1000 people, but we didn't give the Drupal community enough time to come. Perhaps we could have pulled it off on such a short-time frame if the event were to take place in Sao Paulo city over the week-end. But this was Foz do Iguassu, a small city 1000 Km (650 miles) away from Brazil's financial hub, and the event occurred in the middle of the week. Nevertheless, the Drupalers that came were really great, and we also had many newbies attending Latinoware interested in open-source, and this was the audience that we tried to reach. The Magazine Perhaps one of the biggest successes of DrupalCamp Foz 2011 was the launch of a Magazine to promote Drupal in Latin America. This was a 20-page full-color magazine with many articles and an interview with Dries Buytaert translated into 3 languages: English, Spanish, and Portuguese. Thanks to our sponsors, we were able to print 5000 copies. In Latinoware, we were able to spread 3000 magazines. Just a few days ago, we were awarded a 2500 USD grant from the Drupal Association to print more magazines and spread them in DrupalCamps all over Latin America! We are already in touch with Drupalers from Argentina, Bolivia, Colombia, Costa Rica, Ecuador, Guatemala, Mexico, Nicaragua, Panama, and Peru to spread these magazines. Also, in Brazil, we'll be spreading the magazines in the states of Sao Paulo, Rio de Janeiro, Santa Catarina, Parana, Minas Gerais, Bahia, Goias and the Federal District (Brasilia). So this has been and will be, without a doubt, a big boost in disseminating Drupal in the whole continent. The DRUP4AL But the whole continent is not enough for us. We want to help spread Drupal everywhere, specially in places that have so far received little attention from the Drupal community. This is why we also created a new initiative called DRUP4AL, pronounced "Drup for All", with the mission of promoting Drupal in Africa, Asia, Australia, and America Latina. We want to expand Drupal to new horizons and foster new opportunities in places where it's most needed! But is Drupal mature enough in these places to deserve our attention? We believe that this is a classic chicken-and-egg problem. The more we concentrate our attention in promoting Drupal in North America and Europe, the bigger will the gap get between Drupal adoption in North America and Europe when compared to the rest of the world. Also, there is a tendency for undervaluing the importance of Africa, Asia, Australia, and Latin America. The reality is that, despite the challenges, there are huge markets in these regions. For example, we have Brazil, Russia, India, and China. Furthermore, and most importantly, it's a matter of social responsibility promoting Drupal in these regions, since these are the regions where Drupal has the biggest potential for truly changing people's lives and making the world a better place. We've just launched this initiative, but within a few days, we have already received support from the whole Drupal Latin Community, as well as the Drupal Community from India, Singapore, and Australia. Final Remarks DrupalCamp Foz 2011 was a great event with many initiatives. We only had 50 days to organize this event, but for us this was just a small drop towards making a strong Drupal presence everywhere. We are currently organizing the 2nd Drupal Summit Latino, in Guadalajara, Mexico, and we are preparing to launch a new Magazine during this event. We also look forward to working together with other communities from around the world. There is just so much potential, and we believe that these initiatives will help change the perspective that the core Drupal community has towards the community around them. If we all work together, we can truly change the world and create a better equilibrium in society. I believe that there is no better place to represent this change of attitude than Foz do Iguassu, with the beautiful waterfalls symbolizing the coming together of small water drops from everywhere into this one splendid oeuvre d'art from mother nature. Let's spread Drupal everywhere, and most importantly, let's spread opportunities for all! Website: http://foz2011.drupal-latino.org/en Castellano / English DrupalCamp Foz 2011: Difundiendo Drupal en América Latina y más allá! DrupalCamp Foz 2011 Foz do Iguaçu, Brazil Octubre 19-21, 2011 Escrito por Nick Vidal Traducido al Castellano por @develCuy Foto por: Saulo Amui. Apuesto a que Dries nunca vio tantas gotas de agua en su vida! Introducción La comunidad Latina de Drupal ha estado intentando convencer a la Asociación Drupal de organizar un Drupalcon fuera del axis Norte América / Europa desde 2009 sin mucho éxito. Uno de los últimos intentos fue el plan de Drupal Association de hacer un Drupalcon junto a Latinoware, uno de los más grandes eventos de open-source en Brasil, pero eso no funcionó y, con 50 días faltantes para Latinoware, la Drupal Association pasó la pelota a cualquiera que tome el reto de organizar un DrupalCamp en reemplazo. Obviamente 50 días no es mucho tiempo para organizar un evento de esta magnitud. Sin embargo, pensé que era importante hacer mi mejor intento para probar, como comunidad, que es posible organizar un DrupalCon en América Latina! ¿Por qué es tan importante? Porque esto rompe el antiguo patrón de organizar DrupalCons solamente en Norteamérica y Europa. Porque esto expande Drupal a nuevos horizontes y fomenta nuevas oportunidades en lugares donde es más necesitado! Si la comunidad Latina puede organizar un DrupalCon, entonces Asia puede. Si Asia puede hacerlo, entonces Australia puede. Si Australia puede hacerlo, entonces África puede! El Lugar DrupalCamp Foz 2011 ocurrió junto con Latinoware 2011 en Foz de Iguazú, Brazil del 19 al 21 de Octubre de 2011. Más de 4.000 personas fueron parte de la octava edición de Latinoware. El lugar de Latinoware fue el Parque Tecnológico de Itaipú, situado dentro de la Represa de Itaipú. La Represa de Itaipú es en el planeta el más grande generador de energía limpia renovable. Considerada una de las siete maravillas del mundo moderno, esta magnífica estructura está ubicada en el límite de Brazil, Paraguay, y Argentina. Aparte de la Represa de Itaipú, Foz de Iguazú es también conocido por las Cataratas de Iguazú, consideradas a ser una las siete maravillas naturales del mundo. El lugar provisto por Latinoware fue realmente hermoso, y Latinoware se encargó del equipo de audio/video, grabación de video, acceso a Internet, recepcionistas, traductores, guardias de seguridad, transporte, coffee-break, almuerzo, y hasta un concierto de Rock! Los Organizadores Los organizadores principales de Latiware fueron Cesar Brod y Joice Käfer. Ambos hicieron un trabajo fantástico organizando el evento y todo el tiempo ofrecieron un soporte tremendo para DrupalCamp Foz. Ellos fueron los responsables de convencer a Dries Buytaert de venir a Brazil por primera vez. También, ellos negociaron con Latinoware el pago de los gastos de dos organizadores Brasileños de DrupalCamp Foz y dos organizadores de DrupalCamp Foz de América Latina. Yo fui el organizador principal de DrupalCamp Foz y escogí Pedro Faria, un miembro de la comunidad de Drupal y PHP de Rio de Janeiro, para que me ayude. De América Latina, escogí a Fernando Paredes Garcia, el anterior organizador de Drupal Summit Latino (ocurrido en Lima, Perú en Enero 2011), y Joaquin Contreras, el próximo organizador de Drupal Summit Latino (que ocurrirá en Guadalajara, México en Febrero 2012). Quise aprovechar este DrupalCamp como un punto de encuentro para crear un puente entre los Drupal Summits. Estos Drupal Summits son una demostración del poder de la comunidad Latina de Drupal para organizar eventos. Los Patrocinadores La mayoría de patrocinadores necesita por lo menos 3 meses para preparar sus recursos de patrocinio, pero no tuvimos mucho tiempo, así que nos apoyamos mayormente en nuestra propia red social para encontrar patrocinadores y hablar directamente con los CEOs para acelerar el proceso. Fabiano Sant'Ana proveyó nuestro primer Patrocinador Oro al contactarnos con José San Martin, de Chuva Inc (Brasil). Después, Pedro Faria nos puso en contacto con Saulo Amui, de HostSH (Brasil), quien ofreció un Patrocinio Bronce. El siguiente, Leandro Nunes y Alex Weber de Webdrop (Brasil) se pusieron en contacto con nosotros para ofrecer un Patrocinio Plata. Franz Glauber nos puso en contacto con Bob White de Trellon (U.S.), quien gentilmente ofreció un Patrocinio Oro. Yo pude negociar un Patrocinio Oro con Jeffrey McGuire de Acquia (U.S.). Y finalmente, Fernando Paredes Garcia nos puso en contacto con Juan Santiago de Santex America (Argentina) para un Patrocinio Diamond. Cada CEO tuvo que ocuparse personalmente de este asunto y hacer que ocurra rápido, así que estamos muy agradecidos por su maravilloso soporte a la comunidad Latina de Drupal. Los Ponentes Tampoco tuvimos mucho tiempo para hacer una llamado para participar. Solamente dimos una rango de tiempo de 2 semanas a los ponentes de todo Brasil y América Latina para envíen sus sesiones, pero la respuesta fue maravillosa e incluso tuvimos que quitar algunas charlas al final. Los ponentes escogidos fueron de Argentina, Bolivia, Brasil, México, y Perú (así como Bélgica y Groenlandia). Ellos fueron: Alex Piaz, Capi Etheriel, Diego Teixeira, Dries Buytaert, Everton Pasqual, Fabiano Sant'Ana, Fernando Paredes Garcia, Franz Glauber, Henrique Recidive, Javier Reartes, Joaquin Contreras, José San Martin, Karim Boudjema, Leandro Nunes, Nancy Contreras, Nick Vidal, Pedro Faria, Rasmus Lerdorf, y Tiago Palacios. Gracias a nuestros patrocinadores, nosotros pudimos ofrecer hospedaje gratuito a todos nuestros ponentes. La Audiencia Con el DrupalCamp Foz 2011 ocurriendo en el auditorio principal, con una capacidad para 1000 personas, tuvimos expectativas realmente altas. Pero Cesar Brod, un organizador experimentado, nos advirtió que el no espera que llenemos el auditorio, especialmente con solo 50 días para organizar el evento. Y al final, el tuvo razón. Esto solamente prueba que ¡no puedes organizar un gran evento en solo 50 días! La Comunidad de Drupal necesita tiempo para poder organizarse, hablar con los empleados, comprar los boletos de avión, hacer las reservaciones de Hotel, y poder juntarse. Tuvimos todo listo para recibir a esas 1000 personas, pero no le dimos suficiente tiempo a la comunidad de Drupal para venir. Tal vez pudimos haberlo logrado en tan poco tiempo si el evento se hubiera realizado en la ciudad de Sao Paulo durante un fin de semana. Pero esto era Foz de Iguazú, una pequeña ciudad a 1000 Km (650 millas) lejos del centro financiero de Brasil, y el evento ocurrió en el medio de la semana. Sin embargo, los Drupaleros que vinieron fueron realmente grandiosos, y también tuvimos muchos novatos que asistieron a Latinoware interesados en open-source, y esa fue la audiencia que intentamos alcanzar. La Revista Tal vez uno de los mayores éxitos de DrupalCamp Foz 2011 fue el lanzamiento de una Revista para promover Drupal en América Latina. Esta fue una revista de 20 páginas a full-color con muchos artículos y una entrevista a Dries Buytaert traducida en 3 idiomas: Inglés, Castellano, y Portugués. Gracias a nuestros patrocinadores, pudimos imprimir 5000 copias. En Latinoware pudimos distribuir 3000 revistas. Hace solo unos días fuimos premiados con 2500 USD de la Drupal Association para imprimir más revistas y distribuirlas en las DrupalCamps DrupalCamps por toda América Latina! Ya estamos en contacto con Drupaleros de Argentina, Bolivia, Colombia, Costa Rica, Ecuador, Guatemala, Mexico, Nicaragua, Panama, y Perú para distribuir estas revistas. También, en Brasil, estaremos las revistas en los estados de Sao Paulo, Rio de Janeiro, Santa Catarina, Parana, Minas Gerais, Bahia, Goias y el Distrito Federal (Brasilia). Así que esto ha sido y será, sin lugar a dudas, un gran acelerador para promocionar Drupal en todo el continente. La DRUP4AL Pero todo el continente no es suficiente para nosotros. Queremos ayudar a difundir Drupal en todas partes, especialmente en lugares que hasta el momento solo han recibido poca atención de la comunidad de Drupal. Esa es la razón por la que también creamos una nueva iniciativa llamada DRUP4AL, pronunciada "Drup for All" (Drup para todos), con la misión de promover Drupal en Africa, Asia, Australia, y América Latina. Queremos expandir Drupal a nuevos horizontes y fomentar nuevas oportunidades en lugares donde es más necesitado! Pero, ¿És acaso Drupal lo suficientemente maduro en esos lugares como para merecer atención? Creemos que este es el clásico problema del huevo y la gallina. Cuanto más concentremos nuestra atención en promover Drupal en Norteamérica y Europa, mayor va ha ser el nivel de adopción en Norteamérica y Europa cuando se le compare con el resto del mundo. También, hay una tendencia a menospreciar la importancia de Africa, Asia, Australia, y América Latina. La realidad es que, a pesar de los retos, hay enormes mercados en esas regiones. Por ejemplo, tenemos Brasil, Rusia, India y China. Finalmente, y más importante, es un asunto de responsabilidad social el promover Drupal en esas regiones, ya que esas son regiones donde Drupal tiene el mayor potencial para realmente cambiar la vida de las personas y hacer del mundo un mejor lugar. Recién acabamos de lanzar la iniciativa, pero en pocos días, ya hemos recibido soporte de toda la Comunidad Latina de Drupal, así como de la Comunidad de Drupal en India, Singapore y Australia. Observaciones Finales DrupalCamp Foz 2011 fue un gran evento con muchas iniciativas. Solamente tuvimos 50 días para organizar este evento, pero para nosotros esto fue solo una pequeña gota en el esfuerzo de construir una fuerte presencia de Drupal en todas partes. Actualmente estamos organizando el 2do Drupal Summit Latino, en Guadalajara, México, y estamos preparando el lanzamiento de una nueva Revista durante este evento. También estamos buscando trabajar junto a otras comunidades de todo el mundo. Hay mucho potencial, y creemos que esas iniciativas van a ayudar a cambiar la perspectiva que el núcleo de la comunidad de Drupal tiene respecto de la comunidad a su alrededor. Si todos trabajamos juntos, podemos realmente cambiar el mundo y crear un mejor equilibrio en la sociedad. Creo que no hay mejor lugar para representar este cambio de actitud que Foz de Iguazú, con las hermosas cataratas simbolizando a pequeñas gotas de agua que vienen juntas desde todas partes en este esplendido oeuvre d'art de la madre naturaleza. Difundamos Drupal en todas partes, y más importante, ¡promovamos oportunidades para todos! Sitio web: http://foz2011.drupal-latino.org/es AttachmentSize Libre_DrupalCamp_Foz_2011.pdf1.25 MB DRUP4AL

---

Drupal 7.9, a maintenance release with numerous bug fixes (no security fixes) is now available for download. Several critical bugs with the OpenID have been addressed in this release, among other critical and major bugs, and a few new API features. See the Drupal 7.9 release notes for a full listing. Download Drupal 7.9 Upgrading your existing Drupal 7 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. Security information 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 includes the built-in Update status module, which informs you about important updates to your modules and themes. There are no security fixes in this release of Drupal core. Bug reports Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of next month (November 30). Changelog Drupal 7.9 is mainly a bug fix release. The full list of changes between the 7.8 and 7.9 releases can be found by reading the 7.9 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log. Update notes - Upon first upgrading to 7.9, there are reports of Panels Pages going missing at #1323162: Panels disappear after updating core to 7.9. Solution is to clear the cache. Known issues - Using drush si in Drush 5.x causes error #1314392: drush site-install on Drupal 7.9 fails with a fatal error "Call to undefined function cache_get()". The fix is to apply the patch at http://drupal.org/node/673020#comment-5106306 or update to the latest -dev release of D7.

---

Start:  2011-12-10 09:00 America/Chicago Drupalcamp or Regional Summit Organizers:  Slurpee Register @ DrupalCampChicago.org Your invited to our 4th annual DrupalCamp Chicago Saturday December 10th 2011. Why DrupalCamp: For more than five years the Chicago Drupal Meet Up Group has highlighted the benefits of an open source initiative. We have helped build bridges from nonprofits and entrepreneurs looking to deploy Drupal to resourceful Drupal development companies, independent consultants and hobbyists in the Chicago area and across the midwest. The day-long DrupalCamp allows for a more intensive hands-on focus than the monthly evening Meet Ups, and while there are separate beginner and advanced Meetups, DrupalCamp brings everyone of all skill levels together for open communication, education, fun, and a relaxed forum for industry networking. Not Just for Experts: An attendee-driven format with advanced resources available makes this event unique. Multiple presentations will run simultaneously—geared to everyone from beginners to advanced developers. People of all skill levels are welcome, and laptops are encouraged. Need help with a problem, looking for work, or looking to hire Drupal talent? Find someone with a solution at DrupalCamp Chicago. Seating is limited, so register now. Date and Location: UBS Tower Conference Center One North Wacker Drive Chicago, IL Google Map Saturday, December 10, 2011 9:00am - 5:00pm Pricing: Cost: $40 Includes coffee, tea, soda, snacks, and lunch Scholarships: Contact us to explain circumstances Sponsorships Available: Gold - $1500 (sold out!) Silver - $1000 Bronze - $500 Community - $100 Sponsorship details here Presentations: Interested in presenting? Submit a session proposal after registration Highlight your Drupal knowledge to other midwest developers and users Share your experience and contribute to the growth of Drupal Tell Your Friends! Let others know you're attending DrupalCamp Chicago by putting one of our lovely badges on your site, and ping hashtag #drupalcampchicago on Twitter when you register. We look forward to seeing you December 10th at One North Wacker Drive for DrupalCamp Chicago 2011! Register Today! Or contact us if you have any questions. Chicago

---

Session proposals are still being accepted for the next DrupalCon, being held at the Colorado Convention Center in Denver, March 19 -23, 2012. The conference theme is "Collaborative Publishing for Every Device" and the deadline to submit sessions is October 26, 2011 23:59:59 UTC/GMT -7. DrupalCon Denver will be focusing on 8 significant areas of expertise and of particular interest to Drupal users and developers alike. Preference will be given to session ideas that examine the following tracks and how they relate to the conference theme: Site Building Coding and Development Design and User Experience Drupal Community Business Strategy Mobile Commerce Nonprofit, Government and Education These session tracks descriptions are available online, so make sure to visit the official DrupalCon Denver website to learn more. Session ideas are posted online as they are submitted - see the list of sessions proposed so far. The final selections picked from all session submissions will be announced on November 16, 2011 and the final DrupalCon Denver schedule will be live on December 7, 2011. Any and all proposals are welcome -- help keep DrupalCon 100% powered by You! Follow @drupalcon on Twitter or find us on Facebook.

---

The best science and technology news, discoveries, product reviews, and geek culture. Videos from National Geographic, Revision 3, PBS, Diagonal ...dailymotion.com

---

It is with great excitement that I can announce "subscribe" comments on Drupal.org issues are now dead! Long live issue following! Issue e-mail notifications are also improved. Almost exactly 6 years after #34496: [meta] Add Flag module to allow users to subscribe/unsubscribe without posting a comment was originally posted, this feature is finally done and deployed on Drupal.org. If you notice any problems, please go to #1306554: QA for issue following on Drupal.org and comment there. Summary of changes In the past, you had to comment on an issue in order to keep track of it, commonly done by posting "subscribe" (or variations thereof). Popular issues gained plenty of such comments, making it hard for contributors to distill the important and useful information in an issue. You are now able to "follow" issues by clicking a button, without commenting on them. You can also "unfollow" issues, even ones you had to comment on but you are not really interested in. Lastly, you can now configure for which projects and issues you want to get e-mail notifications. Sponsors First, I'd like to thank the sponsors that made this possible: The 88 members of the community that contributed to the 2 chip-ins to raise a total of $2777.27 towards the original goal of $7,000. This sponsorship allowed 3281d Consulting to focus on this project and get it deployed ASAP. Changes to how we work in the issue queues There are two big inter-related changes as part of this effort: how we interact with issues on Drupal.org, and changes to the issue e-mail notification functionality. Working with issues on Drupal.org The most obvious change is that when you're viewing an issue on Drupal.org, you will now see a large green "Follow" button in the upper right corner: Clicking the "Follow" button will use AJAX to flag the issue as one you are following. This will trigger two things: 1) the issue appears in the "Your Posts" and "Your Issues" lists (both on your dashboard and the separate tabs on your profile), and 2), the "Follow" button will be replaced with "Following", to indicate you're now following the issue. If you hover over or put the keyboard focus on this "Following" link, it will turn into an "Unfollow" button: You can even unfollow issues if you wrote them or commented on them. Whenever you click the "Unfollow" button the issue will disappear from your tracker and you will stop getting e-mail notifications about it (if you get e-mail notifications at all). Issue e-mail notifications You can optionally configure Drupal.org to send you an e-mail notification about updates to issues you care about. In the past, this functionality has been somewhat hidden, so a lot of users do not make use of this feature. Now, there is a centralized page to manage all of your issue e-mail notification settings, on the new "Notifications" tab on your account profile page: This page lets you opt-in to e-mail notifications for issues on Drupal.org. By default, you get no e-mail at all. You can define both a site-wide default and per-project overrides. A very common configuration would be to just set the Default notification to "Issues you follow": If you maintain some projects on Drupal.org or are otherwise particularly interested in their issue queues, you can also specify per-project overrides of the site-wide default. So for example, another common configuration might be to get notifications for all issues you follow, but to also get notifications about "All issues" in a few specific projects you most care about: In the past, there was no way to define a site-wide setting, so users often had to configure e-mail notifications across a large number of projects. If you used to be subscribed to 50 or more projects with the "Own issues" setting, that was converted as part of the deployment into a single site-wide default. The final change to the e-mail notification functionality is that you can now customize the contents of the e-mails themselves. Previously, you always got the entire issue history included in each notification. If you expand the "Configure e-mail contents" fieldset, you'll see the ability to only get the new content in each notification and some checkboxes to control what appears in the subject line of the messages: There are more ideas to further improve the issue e-mail notification experience, so be sure to read the "Future work" section below. Thanks While the financial sponsorship was critical to allowing me to spend the time I needed to drive this home, tons of other people contributed to help make this a reality. Daniel F. Kudwien (sun) and Chad Phillips (hunmonk) wrote and reviewed many patches related to this effort. Leisa Reichelt (leisareichelt) started the Prairie Initiative which has been instrumental in raising awareness about the need to fix the collaboration tools on Drupal.org. She also provided lots of extremely helpful user experience (UX) and user interface (UI) feedback. Roy Scholten (yoroy) and Bojhan Somers (Bojhan) provided extensive usability, user interface and user experience reviews and suggestions. Everett Zufelt (Everett Zufelt) provided accessibility reviews and feedback. Angela Byron (webchick) helped herding cats, reviewing things, testing, giving feedback, and generally was awesome (as always). Narayan Newton (nnewton), Gerhard Killesreiter (killes) and Neil Drumm (drumm) did performance reviews, got the staging site up, and provided general Infrastructure Team goodness. Nathan Haug (quicksketch) answered a lot of questions about the internals of the Flag module for the data migration, and helped trying to get the new follow UI working smoothly. Jerad Bitner (sirkitree) and Moshe Weitzman (moshe weitzman) wrote the initial patches for a couple of the key issues. dereine, amateescu, eliza411, ksenzee, Caligan, xjm, Crell, jhodgdon, pillarsdotnet, timplunkett, naught101, kathyh__, wizonesolutions, techninja, hefox, jwalling, joshuabud, otseld, and torthu helped test the upgrade-while-live data migration code. Lisa Rex (lisarex) helped edit this post. Everyone else who contributed reviews, testing or implementation suggestions for all the issues related to getting this done. Future work As exciting as all of this is, of course there's always more work to do. Generally, we've been using the flag integration issue tag to keep track of things related to this effort. See also the drupal.org notifications tag. You can also check out the Expand "follow" functionality on Drupal.org community initiative page. Unfortunately, I'm going to have to return to other commitments, so I can't just continue to pour unlimited time into getting all of these issues done, UX reviews, code reviews, etc. So, if anyone wants to step up and claim any of these issues to drive them to completion, that would be greatly appreciated. Thanks! -Derek Wright (dww) p.s. Additional history is available at The history of how we killed "subscribe" comments on Drupal.org for the interested reader...

---

Drupal.org is our home. It's where we solve tough problems, it's where we innovate on creative solutions, and it's where we meet and interact with others in our community. It only makes sense then that our community should be able to actively participate in making improvements happen on Drupal.org, but the process to do so has traditionally been seen as a bit confusing and opaque. This post attempts to outline the process of making changes to Drupal.org, and highlight some recent successes we've had putting this process into practice. This information is compiled from the Make Drupal.org awesome guide! Step 1: Think it up Have a great new idea for improving Drupal.org? Great! Search first, to see if someone else has already had your amazing idea and maybe started work on it. If not, begin by creating an issue in the webmasters issue queue to discuss, unless you happen to know the appropriate issue queue for it. Prefer to collaborate on some ongoing efforts that other passionate people are working on? Check out the Drupal.org improvements community initiatives page, and its various sub-pages, to join up with others on their big ideas. :) Step 2: Talk it out (Note that if you're participating in an existing issue that the Drupal.org maintainers have already signed off on, you can skip this step!) At this stage, what you want to do is gather feedback from the rest of the community about your idea. Since Drupal.org is a shared resource, it's important that there be buy-in for any given change from multiple people, particularly given the performance challenges of Drupal.org (1,000 people logged in at any given time hitting refresh repeatedly on "My issues"... egad!). Start by asking for some initial, informal feedback from folks in IRC, Twitter, or a local Drupal user meetup. If that goes well, consider cross-posting your issue to Planet Drupal or potentially interested groups on http://groups.drupal.org to get wider exposure for your idea and broader discussion (but please don't be obnoxious about it :P). If it looks like the community thinks your idea is a good idea, the final step is to run it past the appropriate members of the Drupal.org infrastructure team. The Drupal.org infrastructure team "org chart" (click for big version) Run the idea past the person who's "in charge" of that particular area. For example, if your idea was to make improvements to the themes listing on Drupal.org, you'd want to talk with one of the folks in the "Issue tracker and downloads" section (dww or mikey_p) about that. If it's a larger-scale change with major new functionality, the Drupal.org infrastructure manager (killes) should also be pinged. Got sign-off from the infrastructure maintainer(s)? Perfect! Now you're ready to... Step 3: Code it up There are two ways to develop improvements against Drupal.org: Get a drupal.org development sandbox (preferred) Drupal.org sandboxes are hosted on a domain like http://issue-summaries-drupal.redesign.devdrupal.org/ and contain a sanitized/trimmed copy of a real Drupal.org database. These work really well for allowing others to test your changes in a "real" environment. Develop locally with Drupal.org testing profile Ideal for smaller tweaks, or self-contained features that doesn't require "real" Drupal.org data. The Drupal.org testing installation profile will hook you up with an installation of Drupal with all of the various modules that Drupal.org uses, plus some basic configuration. It's definitely not perfect, but good enough for a lot of smaller things. Now. Remember all of those people who supported your idea back in step 2? Tell 'em to turn out and help with development, UI feedback, and reviewing. :D It's really helpful to have a single "meta" issue tracking any sub-tasks, as well as an up-to-date issue summary at the top of that issue, outlining the remaining tasks before your initiative is ready to be deployed. This helps new people coming in to know where to be the most effective. Before moving onto the next step, it's a good idea to make sure that any dependent patches have been committed upstream (if at all possible), and a clear list of deployment tasks (e.g. new modules to be added, what settings to change, etc.) are added to the issue summary. This will make deployment as easy as possible. Step 4: Get 'er done Once the change gets to "reviewed & tested by the community," it's time to prepare for deployment: Tag your issue as needs drupal.org deployment. Post an issue to the infrastructure issue queue which points to the issue where the change has been implemented, point to the deployment steps, the dev site, and request a final review of the changes. If it's a big enough change, its deployment might need to be scheduled if it will incur any drupal.org downtime. You should be a good Drupal citizen and make yourself available to the infrastructure team if they have any questions during deployment in #drupal-infrastructure on IRC. Assuming your change passes a final review from the infrastructure team on things like performance and maintenance considerations, your brilliant idea should now be up singing and dancing in front of everyone on Drupal.org. WOOHOO!! Sounds good, but does it actually work? In a word, absolutely! Here is a list of recent improvements that have been pushed out through this process: Better system for tracking API changes During Drupal 7's release cycle (and before), making an API change to Drupal core involved editing this gigantic page of horror and tears. It was cumbersome, and therefore it was very difficult to get developers to do this, and there are probably still API changes today, ten months after Drupal 7's release, which are not tracked here. :( Jennifer "jhodgdon" Hodgdon spear-headed the initiative to turn these API changes into nodes, with a view that can filter by version, who it affects, and so on. It can also track whether or not Coder Upgrade rules were written, whether or not relevant documentation was updated, etc. for each change. YAY! Issue summaries A huge barrier to entry to core development and other places where large sections of the community have a lot of things to say about things is long, sprawling, complicated discussions. Take a typical critical bug report in Drupal 7 like #228818: IE: Stylesheets ignored after 31 link/style tags and watch it grow from 20 to 50 to 100 to 400 comments over time. Coming in fresh to these types of issues is almost impossible; it can require hours' worth of reading, and entire code sprints intended to focus on fixing critical issues have been taken up doing just that. :( This issue resulted in making issue bodies themselves editable, so that in these types of complex issues all a new person (or a busy core maintainer) has to do is read the first post and then be caught up with major happenings. All issues on Drupal.org now have an "Edit" tab, which refers to an issue summary template to highlight what's going on in this issue, what the proposed solution is, and what remains to be done about it. This has collectively shaved hundreds of hours off of collaboration on tricky issues already, and has even started an "Issue summary initiative" led by xjm to specifically seek out these complex issues and write up summaries for them. A great way to dive in for people new to core development! Images for all on Drupal.org The ability to post inline images on Drupal.org has been traditionally locked down to only privileged users (the "documentation team" role or higher) in order to prevent possible Cross-site request forgery attacks, and also to prevent mixed content errors when Drupal.org moves to HTTPS. While great from a security POV, this is absolutely terrible from a collaboration POV. :\ Designers, usability folks, bug reporters, casual documentation editors, and others are prevented from participating unless they ask for and receive elevated permissions on the site. sun and chx worked together on a new general-use module called Local image input filter to meet Drupal.org's needs. It restricts tags to the local site only, and also verifies that what's being linked to is actually an image. No chance of linking to something nefarious on evilh4x0r.com, and no chance of mixed content errors either since all URLs are re-written as relative. NICE! So not only was a useful problem solved for Drupal.org, but others who need the same capability can take advantage of it as well. The key thing about these patches? They were all developed by people not in the infrastructure team org chart! Just regular ol' Drupal contributors like you and me. :) So, let's make Drupal.org awesome! Come along and join us!

---

Hello from Jennifer and Ariane, your friendly Drupal Documentation Team co-leads! It’s time for a quarterly update on what’s happening in the Documentation Team—we've been working on some major restructuring of documentation and the Docs Team since our last update (June 28, 2011), and we'd like to get you up to date on our plans, and other events and news. Docs restructuring The big news for this quarter is that we are in the midst of some restructuring of the online Drupal documentation, as well as of the Documentation Team itself. Nothing has been completely settled yet, but here is an outline of our plans, reasoning, and links to more information and where you can get involved in the discussion. Community documentation The main issue we need to resolve is that the current online documentation on Drupal.org is way too overwhelming for one coordinator to manage. Having one coordinator is a single point of failure, and has led to several past Docs Team leaders getting burned out and leaving the post. The current documentation has many features of a wiki: anyone can edit most of the pages, and anyone can add new pages... Yet we have found that potential documentation contributors are timid about actually editing and adding pages. So what we would like to do is turn responsibility over to the community as a whole, and make it abundantly clear that everyone can edit and contribute. The plans have been solidified on this issue: #1278256: Develop a plan to make it more clear that the current Documentation on drupal.org is community maintained., and if you'd like to help with the infrastructure changes (site building and module development), we are currently coordinating docs infrastructure work on http://groups.drupal.org/node/174499 . Follow-up changes to the infrastructure are being discussed on #1287784: Follow-ups to improve the community docs. Curated documentation Once we have those changes deployed, the next idea is to start a new section of documentation that will be more directly curated and maintained by the official Documentation Team leadership—and therefore, more limited in scope. The idea here is that careful decisions will be made about what are the "essentials" that belong in this documentation (which might be called "official documentation" or "user manual" or "curated documentation" or "essentials" or ...), and a small team will be responsible for maintaining the documentation. This idea has not been completely fleshed out yet; it's being discussed on issue #1291058: Make a curated docs section if you'd like to join the discussion. Outside documentation Another idea that's in development is to make it possible to search external documentation—for instance, Drupal tutorials on blogs, and curriculum on Drupal company web sites. Lin Clark is currently exploring ideas for automatic collection of posts involving RDFa/microdata and SPARQL, and there will hopefully be more ideas and discussion about this in the next few months. Watch the Documentation Team on groups.drupal.org for updates! API reference We don't expect anything to change in the process, maintenance, or location of the API reference site on api.drupal.org. That process is actually working fine, and Jennifer is pleased to report that there have been many new contributors stepping up to submit patches lately. (Note: sprint coming up—see below!) July - September events Here are some events that the Documentation Team participated in during the third quarter of 2011: At the end of August, many from the Docs Team were at DrupalCon London. We had BoFs ("Birds of a Feather" informal discussions) about DITA (a standard for documentation), the proposed new Help system for Drupal 8, and Lin Clark's ideas about using RDFa or microdata to build an index to documentation from Drupal Planet (see above). At DrupalCon, there was also a Core Conversation session about DITA and the new help system. And of course we also had a very successful Documentation Sprint on the last day of the conference, with three tables of participants helping each other become knowledgeable documentation contributors. Thanks to all who participated! We are 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 find us on IRC, and we plan to continue with this schedule for the foreseeable future. Upcoming API docs sprint The API documentation on api.drupal.org has been improving slowly but surely over the past couple of years (I think/hope). But there are still quite a few areas where the documentation does not conform to the API documentation standards. Unfortunately, patches that do wholesale changes to documentation headers are disruptive to the ongoing improvements of the Drupal code, since they often require that many patches be "re-rolled" so that they will apply to the new code-base. So, we've been told several times that we needed to postpone these types of large-scale updates. However, in early November, a patch is scheduled to go into Drupal 8 that will move all of the core Drupal files into a "core" directory. This will be a huge disruption, as every patch for Drupal 8 will need to be re-rolled. Because of this, it's a great time do other disruptive work, and we plan to have an API Documentation sprint just after that patch goes in, where we'll do a defined set of wholesale improvements to the in-code docs for Drupal 8. Mark your calendar—I'm hoping that we have lots of participants (including new API docs contributors) so the work for each person will be manageable! Process, communication, and infrastructure milestones Aside from the infrastructure and team reorganization mentioned above, there were some smaller initiatives in the Documentation Team this quarter: In July, Neil Drumm (drumm), with help from a few others, deployed a new feature to your Drupal.org user profile and Drupal.org company profile, aimed at recognizing documentation contributions: there is now a line in the History section of user profiles and the right sidebar of the new Marketplace company profile that says something like “Over 100 edits”, reflecting how many documentation page revisions you have made since joining Drupal.org. This is a small way of recognizing documentation contributions to the Drupal project. At DrupalCon Chicago, Dries suggested that in Drupal 8 development, each change would have to pass through a series of "gates" in order to be accepted, and Documentation was listed as one of his "gates", but it wasn’t defined what the gates really meant. So, a conversation was started with Jennifer, Angela Byron, and other members of the community, and in July, the Documentation gate standards were adopted. The adopted gates are listed on the gates page. In July, Angela Byron and Jennifer (along with many others) finalized two changes to the Drupal issue workflow: Issue Summaries and Change Notification nodes. With issue summaries, anyone can now edit the node body of any issue, to use the body as an Issue Summary, and we have a suggested issue summary template to use when filing or updating issues. With change notification nodes: for Drupal Core (and any other project that chooses to use them), after an issue is fixed, if the committed fix involves changes to the user interface or programming interface, a Change Notice node should be created to document the change. Then the Documentation Team, Coder module team, Examples module team, module developers, and theme developers can all visit http://drupal.org/list-changes (simple view) and http://drupal.org/list-change-updates (maintainer view) to find relevant changes that affect them or that need to be acted upon. Jennifer mentored Google Summer of Code student Tamás Demeter-Haludka (Yorirou) over the summer, who created the Conditional Text module. We expect to use this for the new Help system and probably the curated docs as well. Next steps If you're interested in helping with Drupal documentation: Watch http://groups.drupal.org/documentation-team and/or Twitter (@drupaldocs) for updates on what the Documentation Team is up to, and to participate in discussions. New contributors: start at http://drupal.org/contribute/documentation to learn all about contributing to documentation. You can also check the Current Priorities http://drupal.org/node/1005304 page to keep up to date with current short-term priorities, http://drupal.org/community-initiatives/documentation for longer-term projects, and http://drupal.org/node/1006924 for Drupal.org improvement projects (some of which impact documentation), and filter for criticals in the documentation issue queues (now handily accessible through the Docs Contributors Drupal.org dashboard block!). That's all for now—we hope that your fall (or spring, if you're in the Southern Hemisphere) goes well, and we'll be in touch!

---

It's official, and now is the time to register for not just a noteworthy event, but your opportunity to connect with a world-wide community using Drupal to collaborate, connect and improve our online experience. Go ahead: register now! Drupal Elevated! DrupalCon is exciting - there is something for everyone, whether you are already using Drupal or considering it for your online needs and want to know more. Expect to learn about the future of open-source content management; to see what unique tools and features developers are using for fields such as commerce and mobile development; to talk with and hear about high-profile operations using Drupal; and most of all, expect to be surprised by how much fun you will have in the process! Drupal is coming to Denver, and the Colorado Convention Center is officially home to DrupalCon Denver on March 20 to 22, 2012. This conference is your chance to engage the community, learn from others, and share your experiences. Training sessions will be available before the conference on March 19th and a code and contribution sprint on March 23rd. Get your tickets early. Pricing for registration starts at $350 per person, and late pricing begins February 21, 2012 at $400. Volume tickets are available - just use the "Purchase Vouchers" link found on the registration form. Discount pricing is available for students, non-profit employees, and "Sprint Leads" - to register with a discount, you will need to visit denver2012.drupal.org and apply for the specific discount you wish to receive separately. Discount registration applications will be available starting September 15, 2011. Keep DrupalCon 100% powered by You and Submit Sessions Online! We want to hear your ideas for interesting topics and timely discussions for DrupalCon Denver - session proposals are still being accepted until October 26, 2011 23:59:59 UTC/GMT -7. Don't wait - use our online form to submit your session, and see what sessions have already been proposed. This year's theme is "Collaboration for All Devices" and you can read more about the different tracks that will be represented at DrupalCon Denver on our website. Keynotes and Featured Speakers We are confirming new speakers regularly, and your one-stop resource for the latest on who is stopping in Denver is denver2012.drupal.org/featured-speakers. See the new faces just added this week, and don't forget to follow @drupalcon or find us on Facebook.

---

git.drupal.org is scheduled for downtime, Thursday September 8th at 3PM PDT (2200 UTC). We will be performing standard maintenance on git.drupal.org and its associated services. We expect 20 to 30 minutes of downtime, but are reserving an hour for the maintenance window. Thank you for your patience.

---

Drupal 7.8, a maintenance release with numerous bug fixes (no security fixes) is now available for download. A critical bug with the upgrade path, #1164852: Inconsistencies in field language handling has been addressed in this release, among other critical and major bugs. See the Drupal 7.8 release notes for a full listing. Download Drupal 7.8 Upgrading your existing Drupal 7 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. Security information 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 includes the built-in Update status module, which informs you about important updates to your modules and themes. There are no security fixes in this release of Drupal core. Bug reports Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of next month (September 28). Changelog Drupal 7.8 is a bug fix only release. The full list of changes between the 7.7 and 7.8 releases can be found by reading the 7.8 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log. Update notes Addresses critical upgrade path issue #1164852: Inconsistencies in field language handling. The 7.8 release notes have more information for site builders who hit this issue in Drupal 7.7. Known issues Due to stricter error handling in Drupal 7.8 around entities, users of the Media module are experiencing EntityMalformedException errors. A workaround is posted at http://drupal.org/node/1266620#comment-4941950 and engineers are actively working on a new release.

---

Denver, CO is hosting the next North American DrupalCon happening on March 19-23, 2012 at the massive, well-appointed Colorado Convention Center. The worldwide Drupal Community is what makes DrupalCon so fun and exciting, and Colorado's community is thrilled to be the home of "Drupal Elevated" -- tickets go on sale soon, so be sure to follow us on twitter and we'll tell you what's going on, @drupalcondenver. DrupalCon is a world-class conference with a world-wide audience. If you or your organization actively use Drupal, or even if you never have but want to learn, DrupalCon is your chance to engage the community, learn from others, and share your experiences. DrupalCon Denver is now accepting session submissions -- go to http://denver2012.drupal.org/ to submit your idea today! If you want to present in Denver, now is the time to start thinking about what this year's theme, "Collaborative Publishing for Every Device," means to you, and we're accepting sessions in the following tracks: Site building Coding and development Design and user experience Drupal community Business and strategy Mobile Commerce Nonprofit, Government and Education Read descriptions of each track at http://denver2012.drupal.org/about Sponsoring DrupalCon is a great way to get your message before a targeted audience of Drupal users, developers, businesspeople, and other Web professionals. And, you earn karma points because your investment helps make DrupalCon passes affordable so more community members can attend. Sponsor packages provide various levels of lead generation, branding, networking and recruitment opportunities. Contact megan@association.drupal.org with questions or go to http://denver2012.drupal.org/ Follow Drupalcon Denver on Twitter @drupalcondenver, to stay informed on the latest details!

---

Drupal core needs more eyes and more contributors to decrease the very high amount of unresolved issues. We hold the first core "office hours" each week in #drupal on freenode: Tuesday, 04:00 - 06:00 UTC (convert this to my timezone) Wednesday, 16:00 - 18:00 UTC (convert this to my timezone) Why office hours? There are currently a large number of unresolved issues in the core queue, and we want to get more organised dealing with the backlog, and encourage new people to help out. Current numbers: Over 2200 open bug reports against Drupal 8 and 7. Over 1750 open bug reports against Drupal 6. Over 500 patches needing review for Drupal 8 and 7. Nearly 200 bug reports against Drupal 6/7/8 have 0 replies. How will office hours help? If you've been wanting to get involved in Drupal core development, but aren't sure where to start, coming to the office hours. You will find experienced contributors who will help you find something to work on. If you have patches or bug reports against Drupal core, and want to get your patch reviewed or figure out where to take the issue next, this should be a good time of the week to trade reviews on IRC. Things we will do Office hours are for both experienced contributors and developers as well as newcomers, expect some of the following: Triaging the core queue - understanding status, priority of issues, closing duplicates etc. Co-writing issue summaries. Co-writing change notifications for needs work issues tagged with "Needs change notification". Writing SimpleTests for bug reports that don't have them. Swapping patch reviews. New contributors should already be prepared to do the following: Have a local environment to review and test core patches. Get familiar with the documentation at http://drupal.org/patch Mentors/co-ordinators possibly available We'll try to make sure at least one person is online during each slot. catch sun linclark Dave Reid marcingy cweagans xjm beejeebus See you there! See the original proposal for more discussion, and to volunteer for helping out with office hours on a regular basis. Comments have been disabled on this post to keep discussion in one place.

---

The last time I organized a State of Drupal survey was in 2008. The results of the 2008 survey were instrumental in shaping Drupal 7 as well as directing the work of the Drupal Association on drupal.org. Now three years later, I created a new survey. The results of this survey will guide thousands of people in the Drupal community over the next two years. Take the State of Drupal 2011 survey now. It shouldn't take more than ten minutes to fill out. Don't worry if you're new to Drupal: every voice counts! I'll present the results during my DrupalCon keynote in London; the video and the presentation slides will be downloadable after. Please do tell us what you think these days about Drupal: your views will shape Drupal 8 and beyond. Thanks!

---

Drupal 7.5, a maintenance release which fixes security vulnerabilities is now available for download. Drupal 7.6 7.7 also fixes other issues reported through the bug tracking system. Note: Drupal 7.7 is just Drupal 7.6 with a fixed VERSION string (7.6 was reporting itself as 7.5). No other changes. Download Drupal 7.7 Upgrading your existing Drupal 7 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. Security information 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 includes the built-in Update status module, which informs you about important updates to your modules and themes. Bug reports Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of next month (August 31). Changelog Drupal 7.5 only includes fixes for security issues. Drupal 7.6 also includes bugfixes. The full list of changes between the 7.4 and 7.7 releases can be found by reading the 7.6 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log. Security vulnerabilities Drupal 7.5 was released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory: SA-CORE-2011-003 To fix the security problem, please upgrade Drupal. What is included with each release? We make two versions of Drupal core available, so you can choose to only include security fixes (Drupal 7.5) or security fixes and bugfixes (Drupal 7.7). 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. Update notes (#634616) AJAX now responds to 'click' instead of 'mousedown'. Testing was performed to make sure this doesn't affect major contributed modules, but could cause issues. (#1164852) The 'translatable' flag on fields added via the UI now defaults to FALSE, same as fields added via the API do. Contrib modules such as Entity Translation can allow toggling this back for sites that need it. An upgrade path will be included in a future release to bring all legacy fields into compliance. (#1083982) Remote streamwrappers are now supported, because of fixes to where drupal_realpath() is called. Known issues Drupal 7.6 and 7.7 introduced an issue in node data migration in the Drupal 6 upgrade path for foreign language sites that migrates node bodies as untranslatable but assigns language to the data which makes nodes appear in an unsupported state. If you are looking to upgrade a foreign language Drupal 6 site, use Drupal 7.5 for now, and track progress on the issue at http://drupal.org/node/1164852#comment-4807524

---

Drupal 7.3, a maintenance release which fixes security vulnerabilities is now available for download. Drupal 7.4 also fixes other issues reported through the bug tracking system. Download Drupal 7.4 Upgrading your existing Drupal 7 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. Security information 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 includes the built-in Update status module, which informs you about important updates to your modules and themes. Bug reports Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of next month (July 27). Changelog Drupal 7.3 only includes fixes for security issues. Drupal 7.4 also includes bugfixes. The full list of changes between the 7.2 and 7.4 releases can be found by reading the 7.4 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log. Security vulnerabilities Drupal 7.3 was released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory: SA-CORE-2011-002 To fix the security problem, please upgrade Drupal. What is included with each release? We make two versions of Drupal core available, so you can choose to only include security fixes (Drupal 7.3) or security fixes and bugfixes (Drupal 7.4). 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. Update notes The robots.txt file was changed in Drupal 7 to disallow crawlers from the filter tips pages. Known issues #1204648: Tests added for SA-2011-CORE-002 broke testbot causes node access tests to fail, for people running the full core test suite in the Testing module. Fixed in 7.x-dev, and will be included in the 7.5 release.

---

Hello from Jennifer and Ariane, your friendly Drupal Documentation Team co-leads! It’s time for a quarterly update on what’s happening in the Documentation team—we've been trying out some new initiatives and working on infrastructure since our last update (April 5, 2011), and we'd like to get you up to date. April - June events In April and May, Ariane tried out a new concept: picking out a few online Drupal.org documentation projects for the docs team to focus on, in the spirit of an agile "sprint" (not to be confused with a day-long let's-all-document "sprint"). April's sprint focused on 5 key Drupal 7 documentation updates, and it was quite successful: many people participated; four of the five documentation goals were completed, and lots of progress was made on the 5th (updating the core module documentation for Drupal 7). May's sprint had a bit less momentum, but many of the April contributors continued on, and some progress was made. Jennifer also made a developer-doc priority for April and May—to finish the theme and module Drupal 6 to 7 migration guides. This task was completed in June. We named June “Bring a Friend to Docs” month, and outlined an easy procedure to ease new contributors into contributing to documentation. If you missed it in June, you’re still welcome to follow the steps on that page—we can always use more contributors! Upcoming events Jennifer and Ariane will both be at DrupalCon London (thanks to the Drupal Association for funding Jennifer's trip!). Keep an eye on the BOF (Birds of a Feather - informal sessions) schedule, and join us for a Documentation sprint on Friday, August 26 (if you can't make it to London, you can join us in IRC on #drupal-docs, probably about 9 AM to 5 PM London time). Jennifer's also (hopefully) co-presenting a Core Conversation about improving the Drupal Help system with Kristof Van Tomme, if it gets accepted. Hope to see you there! Ariane's online documentation sprints will take a vacation for the summer, and are planned to resume after DrupalCon London. It will be business as usual in the Docs issue queue in the interim. To keep up on future Documentation Team events, follow @drupaldocs on Twitter, and join http://groups.drupal.org/documentation-team If you'd like to host a documentation sprint at your regional camp, local LinuxFest, etc., we have a newly updated guide to hosting a sprint available. Other Docs Team milestones and news There have been several new contributors this quarter making patches for API documentation, which is much appreciated! We’ve managed to get quite a few API doc issues fixed, and are really improving the quality of the documentation. Keep up the good work, team! We have been 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 find us on IRC, and we plan to continue with this schedule for the foreseeable future. The Documentation Contributors block is back, and available for your Dashboard, with handy links relevant to Docs contributors. See http://groups.drupal.org/node/154024 for more details. Jennifer has been working on an infrastructure initiative: to announce Drupal code changes as “Change notification” nodes on Drupal.org, using Views and a content type with CCK fields (issue). This will act as a replacement for and enhancement of the current (very cumbersome and hard-to-maintain) Module and Theme update guides, and hopefully help the process of making sure that as Drupal evolves, the documentation evolves with it, as well as making it easier for module and theme developers to keep up with changes. Jennifer is also working with Angela Byron and others to change some other documentation-related aspects of the core Drupal development process. We’ll be announcing the process changes, the Change notification nodes, and other updates as they go live. Jennifer is also hoping to get to some of the other infrastructure and communication issues identified in our December 2010 docs meeting this summer, once the change notification nodes project is launched, so hopefully we'll have some more Docs infrastructure news next quarter! Jennifer is mentoring a Google Summer of Code student this summer, Tamás Demeter-Haludka (Yorirou), who is building a module to do Conditional Text in Drupal, as part of the initiative to make a better help system in Drupal 8. We’ll be having some BOF gatherings and hopefully a Core Conversation at DrupalCon London on this initiative, if you would like to get involved. Next Steps 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. Monthly Drupal Documentation sprint priorities, announcements, and events are posted on http://groups.drupal.org/documentation-team and on Twitter (@drupaldocs). You can also check the Current Priorities http://drupal.org/node/1005304 page to keep up to date with current short-term priorities, http://drupal.org/community-initiatives/documentation for longer-term projects, and http://drupal.org/node/1006924 for Drupal.org improvement projects (some of which impact documentation), and filter for criticals in the documentation issue queues (now handily accessible through the Docs Contributors Drupal.org dashboard block!). That's all for now, hope you're having a fantastic summer and that we'll see you in London!

---

www.beginlearningdrupal.com - Drupal is not as hard as it looks. I'm a Drupal Design Developer that currently teaches Drupal in my spare time ...youtube.com

---

ProPhoto theme + PSD source files €79SKU: st-dev-proList price: €79Price: €79

---

€49SKU: adtprt11List price: €49Price: €49Taxonomy upgrade extras: 6.x sooper_prophotoShortDesc: Showcase your work! ProProphoto puts the focus on your photosDemo Site: http://demo.sooperthemes.com/prophotodevpack: 546Drupal Core Version: 6,7Framework: Tundraunique:  ProPhoto Design Concept ProPhoto: The Blogfolio Edition. ProPhoto is a portfolio in the popular blogfolio format. It's a captivating showcase of your photography, art or graphic designs. Who should use ProPhoto? ProPhoto is designed for people who want to showcase their work. This includes photographers, artists, graphic designers, type designers, film makers etc. etc. starterkit: st_features: 0123456popularity: 3Theme Type: Portfolio, Blogfolio Using Arctica base theme: 

---

Beau theme + PSD source files €79SKU: st-dev-beaList price: €79Price: €79

---

Technorati and Ingboo have partnered together to provide an all new kind of subscription experience for Technorati content, including tagged posts. Look for a blue Ingboo icon for a full range of subscription options. Feeds are also available for: Hottest Blogosphere Posts Latest Original Articles from Technorati The Technorati Blog We also have channel feeds, writer feeds, and editorial tag feeds, which can be found on their respective pages.

---

Once you have your site installed, you can update your site title and logo, change the way your site looks with themes, and add content.youtube.com

---

Is Drupal a CMS? Or is Drupal an Application Framework? Yes! This is a brief introduction to Drupal. UPDATE: This video won 6 Telly Awards.youtube.com

---

What is Drupal and what can you do with it? In this video I hope to show the basics by building a website in minutes using Drupal. To see more ...youtube.com

---