Apr 10 2018
Apr 10

Over the past few years, we’ve been listening to the community ask for explanation as to why we haven’t had any DrupalCon North America locations outside of the United States - after all it’s called DrupalCon North America, not DrupalCon U.S.A. This isn’t something we’ve taken lightly or ignored. DrupalCon North America is a major funding source for the Drupal Association, and in that regard, a major funding source of Drupal.org and the engineering work that keeps the code accessible and available for everyone.

We’ve looked at many North American cities over the years - a lot in the United States, but some outside the U.S. also. For our 2019 and 2020 location search we directly asked several cities in Canada to bid on this event, so that we could do financial and accomodation comparisons against U.S. options. I will give you the spoiler up front: 2019 and 2020 will not be in Canada or Mexico, they will be in the United States. The cities that bid were competitive, but in the end did not prevail due to things like dates overlapping with Passover and simply not being the most effective bid in comparison to the winners.

But with these cities in mind, and the voices of the community in our ears, we decided to go deeper and explore what a Canadian or Mexican DrupalCon would look like, based on survey feedback from the community and hard numbers from our history and bids. Here is that deeper look.

First, let me say that Drupal Association staff does not think solely about finances in making these decisions. We spend a lot of time getting to know the city, the vibe, the culture and the openness to a community that celebrates diversity and has a plethora of unique needs. It’s important to you, and it’s important to us.

Let’s also acknowledge that DrupalCon North America greatly underwrites the Drupal Association work and Drupal.org infrastructure to help keep the project going. So while money is not the only thing - it is very important.

So, let’s talk about finances. There are a lot of things that go into making a DrupalCon financially viable, and we did a pretty thorough job of outlining them all in our blog series last fall dedicated to the finances of DrupalCon Europe. I suggest you take a look at those, specifically the one on Solving The Financial Problem to get a good understanding on what it takes to make DrupalCon happen. A truncated look shows that there are three (3) main aspects and goals to DrupalCon finances:

  • Expenses: everything we have to spend to make it happen
    • Goal: produce show on a tight budget
  • Revenue, attendee tickets: how many people will show up
    • Goal: people show up
  • Revenue, sponsorship commitment: how much sponsors will spend to support the event
    • Goal: sponsorships have value and continue to support us

Expenses

In a look at expenses there are a vast array of things that we spend money on - from facilities and catering to program guides and paying the person who watches coat check while you’re sprinting on Friday. And overall, the proposals we’ve received from cities within the United States and outside of the United States have been fairly competitive for expenses directly related to the venue and infrastructure. That’s awesome!

There are some other indirect expenses we consider too like cost of hotel rooms, which can greatly affect whether people can afford to stay in the city, and generally Canadian cities - for example - tend to be a bit more expensive than some of our U.S. options. Other considerations include: whether the city is a airport hub for enough domestic and international flights to get people there easily; ease of setting up foreign bank accounts or legal business statuses in specific countries in order for us to operate there (including increased staff time to do this); cost of import/export for our production gear (this applies to sponsors as well). There are workarounds for some of these, and that's what we explore during an RFP process. Based on estimates, a DrupalCon outside the United States tends to pen out to be at least 10% more expensive than one within the United States - that’s around $100,000 - $150,000.

In general, the expenses section is a place where we can explore more work-arounds and potentially find a way to make a non-U.S. DrupalCon happen. However, because of DrupalCon team capacity during 2017 (the timeframe while we were contracting 2019 - 2020 cities) this is not something we could do for the immediately upcoming DrupalCons.

Revenue

As I mentioned above, revenue from DrupalCon North America is a driving force for the Drupal Association and Drupal.org. Ensuring attendee ticket sales and sponsorship revenue remain consistent from year to year (or grow) is extremely important to helping ensure our staff are funded and Drupal.org is kept running. In order to make certain that funding holds consistent and we’re able to keep Drupal.org healthy we need to keep DrupalCon North America profit margins around roughly 30-35% per event.

Here is where things start to fall apart for non-U.S. cities in the immediate future.

To better evaluate our current and potential revenue, we created 2 surveys and put them out to the public/community to participate.

Survey targets:

  • Past and potential attendees
  • Past and existing sponsors

Revenue, Attendee Ticket Sales

DrupalCon attendees are the main audience where we hear the cry for a DrupalCon outside of the United States. Individual ticket sales make up 62% of our event revenue.

Our survey to attendees had 1258 respondents. 92% of those people have attended DrupalCon North America in the past, and 99% have attended a DrupalCon somewhere in the world. So this sample represents people who are likely to attend in the future.

Since we’re talking about Revenue, it’s important to know who is paying for these people to attend. 79% of these attendees are funded by their employers. That’s a significant number and important to think about as we move into a business case for companies to attend DrupalCon.

Who funds your trip

Next, we followed up on that. “If your employer funds your trip to DrupalCon, are they willing to pay for you to travel outside the U.S.?” Of our 79% - 38% answered “No” (this number is adjusted from the chart percentages below because the question was “IF your employer pays”, and 120 people answered that they pay for themselves). That means, of our original sample size, now only 71% of attendees are still eligible to attend (22% self-funded + (62% of 79%) = roughly 71%).

Fund trips outside U.S.

Based on the responses, our projected revenue would decrease by roughly 29%.

Revenue, Sponsorships

Sponsors provide 38% of DrupalCon revenue, their sponsorships currently underwrite the cost of early bird tickets (that’s a whole other problem), and the event would simply not happen without them. They provide the foundation for the event in financing, they are the exhibit hall, and a large portion of our attendees are sponsor company employees. If sponsors don't come, we lose money and don't achieve a key purpose of our event: connecting new business decision makers with agency owners to grow adoption.

In our survey to them, we presented a hypothetical scenario in which DrupalCon takes place in Canada.

Our leading question for sponsors was “Do you do business in Canada?” and 70% of 44 responses said “No”. This doesn’t eliminate possibility, but it is the trend for the questions that followed.

Do business in Canada

We also asked “Would you sponsor a DrupalCon in Canada at same levels as you have in the past?” and only 39% of respondents answered “Yes”.

Would you sponsor

Of these sponsors, many wrote anecdotally that they simply could not support a business case for having an event in Canada.

To Sum it Up

While we’ve had advanced talks with Canadian cities, and two were finalists for 2019 and 2020 making it past initial RFP rounds, as of now we haven’t found solutions to enough of these issues to fit a DrupalCon North America within our required profit margin.

The numbers presented by the surveys would put profit margin for a DrupalCon North America outside the U.S. at an estimated 6% profit margin and would risk actually losing money for the Drupal Association. A situation and risk we cannot allow the Association to bear.

This is disappointing for many of us - and we know it is for many of you as well. We would love to see DrupalCon North America move beyond the U.S. borders, however it will not happen until at least 2021.

In between now and our next location RFP, we will continue to look at models that might make this possible. As we explore these challenges and talk more with sponsors and cities, we will share with the community any progress or new challenges as they become relevant. We appreciate your passion on this topic and understand the concerns with hosting DrupalCon in the United States for another two (2) years, especially based in our current climate of travel restraints in to the U.S. We wish it were not difficult for our community to come together.

We appreciate everyone who took the time to participate in our surveys and were honest about their desires, motivations and realities of their travel to and participation in DrupalCon. We're excited seeing many of you in Nashville this week, and hope many of you will join us in 2019 for DrupalCon Gedfyuikemndjfkioiujhtrj - sorry, something has happened to my keyboard. ¯\_(ツ)_/¯

_________________________

We invite you to share thoughts in the comments section below on how you think DrupalCon 2019 and 2020 can help provide more opportunity for community members outside the United States to participate in the event - either through direct attendance or through virtual participation of some kind. What are your ideas?

Mar 23 2018
Mar 23

We're excited to welcome back the DrupalCon Developer Contest - our first since Los Angeles.

Over the next 2 weeks, we invite DrupalCon Nashville attendees to participate in this fun and creative competition - writing a Drupal module, inspired by Johnny Cash. It's Nashville - how could it not be music inspired?!   

Read the details and join the fun. 

Entries are due Tuesday, April 10, 2018

Winners will be announced Wednesday, April 11, 2018 in the DrupalCon Exhibit Hall during the 10:30 - 10:45 a.m. coffee break.  

Rewards:

1st prize receives a Johnny Cash record and $100 gift card to Etch (a top rated Nashville restaurant).

2nd place - $50 Amazon gift card

3rd place - $25 Amazon gift card

Thanks to our sponsor

Digital Bridge Solutions

Feb 09 2018
Feb 09

The hotels we chose are a perfect hub connecting you to a rewarding DrupalCon experience. It’s also a great way to show up for the community.

Here are some reasons why staying at a DrupalCon partner hotel is great for you and the community:

It’s close. Our hotels are located close to the convention center, a few minutes walk. We choose hotels at various price points within close range of the conference center to make it easy for you to move between your hotel space and the conference space. It’s where we are. Our team and a lot of Drupalers stay at the partner hotels, which means you can catch up with fellow Drupalers at any hour of the day. You’re likely to run into an old friend, meet the person who can answer your Drupal questions, or collaborate on your project over breakfast. Discounts and benefits from the city. Cities structure financial incentives for events based on how many people stay at the host hotel. By staying with us in the host hotels - you financially support the current DrupalCon and future DrupalCons. City incentives help us keep production costs and conference ticket prices low – keeping DrupalCon one of the most affordable technology conferences around. It's another way to give back to the community.

Our strength comes from our great numbers. During the site selection process, we work with a variety of hotels to negotiate the best deals for our attendees. Using past DrupalCon hotel reservations as a baseline, Drupal Association guarantees to the hotels that we’ll fill a minimum percentage of the contracted space. If we meet that target then we can keep our production costs low and provide more benefits to the community. That means keeping the perks you are used to as we plan future locations. With collective bargaining power we are often able to offer perks like these:

We know it’s tempting to find an Airbnb, and it’s fun to have your own space, we get it. But it’s pretty awesome to be in the heart of DrupalCon too. In fact we’d argue that it’s more awesome. And it’s an easy way to contribute back to the community through your stay at DrupalCon. We thank you!

Feb 06 2018
Feb 06

We’re still a few weeks away from announcing our full speaker line-up for DrupalCon Nashville.

Our track chairs are working hard behind the scenes - reviewing session submissions and deciding what topics are going to resonate best with the track themes in Nashville. And guess what? With a record number of session submissions, there are SO many amazing sessions to choose from.

Our full session list will be announced on February 21 - but we're excited to share a few that have already been accepted.

Check out our speakers sneak peek, and then head over to register so you won’t miss a thing.

Jan 25 2018
Jan 25

As many already know, DrupalCon North America 2018 will be held in Nashville, TN. The Drupal Association puts a lot of time and effort into choosing a site for DrupalCon North America - a two to three year process that involves request for proposals, several rounds of interviews, site visits and contract negotiations. We do not take this lightly and we include both logistically important and socially relevant questions for review.

Unfortunately, sometimes things happen outside of our control, despite our great lengths of planning. In April 2016, after a 5-month RFP and interview process, we signed a contract with the City of Nashville to host DrupalCon North America 2018. A few weeks later, the State of Tennessee introduced and passed a new law that Drupal Association does not support, and as many community members have pointed out - prevents public employees from the State of California from attending DrupalCon if sponsored by their employer.

For those who have asked, the timeline of events transpired as follows:

  • April 2016: Drupal Association contracted with Nashville, TN to host DrupalCon North America 2018
  • Early May 2016: Tennessee enacted the Amendment Senate Bill No. 1556 House Bill No. 1840
  • January 2017: California enacted restrictions banning state sponsored travel to TN in response to SB1556/HB1840.

Specifically, May 2, 2016. SB1556/HB1840 as enacted, declares that no person providing counseling or therapy services will be required to counsel or serve a client as to goals, outcomes, or behaviors that conflict with the sincerely held principles of the counselor or therapist; requires such counselor or therapist to refer the client to another counselor or therapist; creates immunity for such action; maintains liability for counselors who will not counsel a client based on the counselor's religious beliefs when the individual seeking or undergoing the counseling is in imminent danger of harming themselves or others.

It is unfortunate that this bill became law. The Nashville Convention & Visitors Corporation, who we worked with to contract DrupalCon Nashville, and the greater Nashville business community including the Nashville Mayor’s office believe discrimination has no place in their home state.

In response to this bill and in anticipation of other potential discrimination bills in the future, Nashville Convention & Visitors Corporation became a founding and leading member of Tennessee Thrives, a business coalition of now more than 400 companies across Tennessee who believe that in order for Tennessee businesses and communities to thrive they must be diverse and welcoming for all people, regardless of race, sex, national origin, ethnicity, religion, age, disability, sexual orientation or gender identity. You can read more here about Tennessee Thrives and the Nashville Metro area’s history of social advancements, as well as a statement from the Nashville Convention and Visitors Corporation.

Here is the Tennessee Thrives pledge:

We believe that equal treatment of all Tennesseans and visitors is essential to maintaining Tennessee’s strong brand as a growing and exciting home for business innovation, economic development, a best-in-class workforce, and dynamic entertainment, travel and tourism industries.

In order for Tennessee businesses to compete for top talent, we believe our workplaces and communities must be diverse and welcoming for all people, regardless of race, sex, national origin, ethnicity, religion, age, disability, sexual orientation or gender identity.

As signers of the Tennessee Thrives pledge, we are committed to promoting an attractive, prosperous, and economically vibrant Tennessee. A united Tennessee is a thriving Tennessee.

Tennessee Thrives identified 12 discriminatory bills that were filed in the General Assembly in 2017, and with their efforts only two were approved.

As a further measure of welcome for our Drupal community, the Mayor of Nashville, has extended a Statement of Welcome to the DrupalCon community. They are very excited that DrupalCon has chosen Nashville as their 2018 North American location, and hope we can see past the politics of the larger state to see the welcoming intent of the City of Nashville.

In response to the Drupal community concerns with Nashville as a DrupalCon city, the Nashville Convention & Visitors Corporation offered this statement:

Nashville is an open, welcoming city that respects and embraces the differences among us. We believe that our differences make our community stronger. A sampling of Nashville’s social advancements in contradiction to the actions of TN legislature include:

  • In 2016, the Metro Nashville Council unanimously voted to approve a resolution asking the state legislature to oppose bills opposing the U.S. Supreme Court’s decision on marriage equality. The resolution’s lead co-sponsor was Councilwoman Nancy Van Reese, who is openly gay.
  • On March 21, 2016, Mayor Megan Barry issued an executive order requiring training of all employees of the Metropolitan Government in diversity issues and sexual harassment awareness and prevention.
  • In May, 2016, Nashville hosted the International Gay Rugby Bingham Cup. Mayor Megan Barry served on the Host Committee to bring the Bingham Cup to Nashville.
  • While a mayoral candidate, Mayor Megan Barry officiated the first same-sex marriage in Nashville just hours after the Supreme Court ruled that same-sex marriage is allowed in all 50 states. (During her inauguration in September, 2015, Mayor Barry invited Nashville in Harmony to perform. The group is Tennessee’s first and only musical arts organization specifically created for gay, lesbian, bisexual, and transgender people – and their straight allies. The group performed at events hosted by the previous Nashville Mayor, as well.)
  • While a mayoral candidate, Mayor Megan Barry received the Ally Award from the Nashville LGBT Chamber of Commerce in 2015.
  • In 2011, Nashville extended nondiscrimination protections to employees of the city and contractors.  (Unfortunately, state government nullified the local decision.)
  • In 2009, the Metro Nashville Council passed an ordinance that protects Metro employees from discrimination based on their sexual orientation or gender identity. (Sponsored by then Council Member-At-Large Megan Barry, who now serves as Mayor of Nashville)
  • In 2008, the Metro Nashville School Board approved sexual orientation and gender identity protections for students and staff.

For those concerned about a Tennessee Bathroom Bill, please know that Tennessee has never passed the bathroom bill, it gets killed in process every time it comes up for a vote, including this past March. There is no “Bathroom Bill” in the state of Tennessee. There are also all-gender restrooms offered at the Nashville Music City Center for use during DrupalCon. We understand people's concern with a state that submits this kind of law for consideration. We can possibly all relate to the idea that the actions of lawmakers are not always representative of the greater population, particularly in the greater population of a metro area, and Nashville shares this same concern.

At our core, the Drupal Association believes in community, collaboration, and openness. We work hard throughout the process of DrupalCon planning to be sure that not only the complicated logistics are addressed, but also an accessible space for everyone in our community to feel safe, welcome and comfortable.

In addition to our core DrupalCon programming, we also include the following services at DrupalCon for those who need it.

  • Our Code of Conduct
  • Registration grants and scholarships
  • Interpreters (for the hard of hearing)
  • Special meals: Kosher, Halal, vegan, vegetarian, gluten-free, etc
  • New mother’s room
  • Quiet room and prayer space
  • Venue accessibility and mobility assistance
  • Local AA Meeting information
  • Speaker inclusion fund
  • No-photograph lanyards and communication preference stickers
  • All-gender restrooms
  • Women in Drupal events
  • Inclusion BOFs
  • On-site contacts for incident reporting

You can learn more about all of these services on our DrupalCon Nashville website under On-site Resources.

We believe, despite the current legislative challenges that the City of Nashville is working to overcome at a state level, that we will have a safe, diverse, celebratory space for our community in Nashville this spring. We’re excited to bring DrupalCon to the city of Nashville, and we’re confident it will be an amazing event.

We want to hear about your experiences at DrupalCon and in the cities we visit. Please participate in our post-Con surveys so that we can follow with both our internal teams and host cities if there are areas where the events can be improved for attendees.

Nov 28 2017
Nov 28

We want to hear your voice at DrupalCon. 

We've launched our call for papers and look forward to seeing the proposals coming in. If you haven't yet seen the line-up of session tracks, take a look - the track teams have been busy building a fresh approach to topics. 

Last year in Baltimore, training courses were packed with eager learners. If you have a training proposal, we want to hear from you, too. Like Joe says, "everyone has something to share". So what's your thing? 

Make sure to check out our key dates and deadlines so you don't miss the submission deadlines. But don't worry, we'll email you before things close, to give you a reminder. Just make sure you're signed up for the DrupalCon News emails, so you don't miss out. 

Nov 27 2017
Nov 27

Looking for the perfect way to celebrate Cyber Monday - you could be one of the first to buy tickets to DrupalCon Nashville!

Did you see our new site? Have you clicked through the pages? Did you read the headline of this story? If you have, then you’ve heard: DrupalCon Nashville 2018 registration is OPEN - and it’s music to our ears.

We’re expecting DrupalCon Nashville to be hotter than their famous chicken. With new session tracks, added Monday summits, and everyone’s favourite - sprints, how could you miss it?

Register today

- and we’ll see you there!

Nov 27 2017
Nov 27

Thank you to the 1,670 people who joined us at DrupalCon Vienna!

So many volunteers! So many sandwiches! We had a wonderful time in Vienna and can't wait to see you all for DrupalCon Europe 2019.

Until then - we hope to see you in Nashville 2018.

Oct 19 2017
Oct 19
Posted by RyeBurd on 19 October 2017

Our community does amazing things together and they deserve to have the best working environment for collaboration. At the Drupal Association, we strive to create these open and collaborative environments at DrupalCon and on Drupal.org.

We recently became aware that a community member violated our speaker agreement at DrupalCon. The Drupal Association removed the video from the DrupalCon event site and the Drupal Association YouTube channel and we are determining additional actions. The community member acknowledged that they broke the speaker agreement and is cooperating with the Drupal Association as we take action.

We apologize that this content was shared. It didn’t create the best environment for our community to thrive and we will do better. We are looking at ways to enhance our process to avoid situations like this from happening again.

We also heard from the community discussion findings that were provided this summer, that the community needs a better understanding of the roles and responsibilities for volunteers that work on Drupal Association programs. The Drupal Association is working to define what is expected of each role and policies for managing situations when expectations are not met. We are working on developing a clear outline of these and you can expect to see them finalized by February 2018.

Sep 15 2017
Sep 15

Everyone is welcome (including you!)

With just about two weeks to go until DrupalCon Vienna we are anticipating an amazing week of learning and collaborating ahead! There will be code sprints all week, but Friday is our dedicated sprint day when anyone and everyone can come contribute to Drupal core and participate together in guided sprints. Add your name to the sprint signup sheet and join us.

First-time sprinters might spend their sprint day working on just a single issue, and that's okay. Some issues take weeks, months, or even years to solve! We all build on each other's work to improve Drupal for everyone.

Sprint topics at the mentored core sprint

First-time sprinter workshop

This hands-on workshop will cover the basics of contribution essentials like the Drupal.org issue queues and IRC, setting up Drupal 8 for local development on your laptop, and optionally git training. If you want to try setting up a development environment ahead of time, try the tools installer.

After attending the first-time sprinter workshop you will be prepared to participate in the Friday afternoon core sprints in Vienna, which will include plenty of tasks for contributors of all skill levels. There is no need to be a coder to participate in the sprints. There will be tasks like testing issues manually, adding documentation, and updating issue summaries that do not require writing a single line of code. Sometimes, not being a seasoned Drupal contributor is a positive advantage as you can ask the questions others neglect to ask.

Major issue triage

If you're already familiar with Drupal, but haven't contributed much before, the major triage sprint is a good way to get more involved. It's also a good fit for project managers, on-and-off-contributors, QA engineers, contributors coming from the first-time sprinter workshop, anyone interested in how Drupal core is made, or anyone concerned about Drupal 8 bugs.

In the Drupal core issue queue we assign priorities to each bug to streamline the resolution process. In this sprint, we will attack issues tagged "Major" and simply make sure the information in each issue is accurate and actionable.

Contributors will work in pairs to evaluate major issues for Drupal 8.x, update the information in the issue, and determine whether or not the issue is still relevant. The most important thing to keep in mind is forward movement through the process - this sprint is not for solving issues, only for helping maintainers and making it easier for others (possibly you!) to step in and understand what needs to be done at a glance.

You can read the steps for triaging major issues to prepare ahead of time.

This sprint will give you the skills to more successfully navigate the issue queue, comment and contribute constructively on issues, work with other contributors, and understand the process code goes through in becoming part of Drupal core. It takes a lot of contributors with varied skills and perspectives to bring all the pieces together.

Make upgrade paths easier with @deprecated documentation

Drupal 8's release process has been changed to make Drupal upgrades easy forever. We improve Drupal's APIs in scheduled six-month minor releases, but also leave the old ways of doing things in place and mark them as deprecated until Drupal 9. This huge shift for Drupal allows module and theme maintainers to adapt to changes gradually, on their own schedule, instead of needing a massive push all at once on some later release date.

To help maintainers make updates, we are adding documentation references directly in the code. In most cases the update documentation is already written so we merely need to add a link to it! Most existing deprecations are in PHP code, so this is a good task for new contributors with a basic knowledge of PHP. Itc is also a good fit for contributors who are interested in API documentation or who want to learn about API changes in Drupal 8.

How to add change records to all @deprecated code

Clearly define Drupal's public APIs by adding @internal tags

Drupal 8 has 6-month minor releases that improve APIs (as well as adding new features).  In order to make this safe, clear, and maintainable, we defined which parts of Drupal's APIs are internal (not covered by the backwards compatibility promise and allowed to change between minor versions) through a documented policy, but that is not very explicit for developers. Adding explicit @internal tags in code documentation is more clear and effective for anyone reading the code or developing with an IDE.  By helping with this effort, you can learn a lot about Drupal 8 APIs and help with the upgrade path through documenting a better-defined API surface. This sprint is a good fit for programmers who want to learn more about Drupal 8's APIs.

JavaScript and theme new contributor sprints

For new frontend contributors, JavaScript maintainer drpal and theme system maintainer joelpittet will each have a mentor table to help you contribute in either of these areas. Drupal core is always in need of more frontend contributors and we welcome your help! Come and meet the maintainers and see how you can improve Drupal's frontend.

And more!

In addition to the mentored sprints, experienced contributors can join a variety of sprint topics in the main sprint room.There are sprints on porting contributed Media plugin modules to the new core Media API, redesigning the core admin UI for better usability, the Search API family of modules, the Open Social distribution, and much more. Sign up now to let us know you're interested in participating!

Mentors and reviewers welcome

If you are an experienced contributor, we can use your help at the mentored sprint too! Sign up to mentor. Mentors should be familiar with Drupal core and the issue queue so that you can explain the process as well as how sprinting benefits the community and the project. The best way to prepare as a mentor for the Major Issue Triage sprint, for example, is to read the meta and try walking through the steps on your own or explaining them to a co-worker or friend.

We are also looking for reviewers on sprint day. Join us in the mentored sprint room at the dedicated review table to give sprinters feedback in Drupal's peer-review process. This is a great way to participate even if you are remote, as there will be many contributors seeking reviews of their patches on sprint day. Let mentors know you are available as a reviewer and they can ping you on slack/IRC when an issue is ready for review.

See you all soon in Vienna (or online)!

Jul 12 2017
Jul 12

We are excited to share the news that we have a new addition to the Drupal Association team - thanks to Srijan.

Last year, we announced the reduction of our team size in order to make the Drupal Association more sustainable. In response, Srijan, a long time Drupal Association Supporter, hired Piyush Jain to work on marketing initiatives and has donated 100% of his time to the Drupal Association.

It’s an incredibly generous contribution and we are extremely grateful for Srijan’s support.

Welcome Piyush

So, please meet Piyush. (In all honesty, he’s been on our team since January, but we’ve been a little slow in our introduction.) He has several years experience in the Drupal community from working at Srijan as well as helping organize Drupal Camp Delhi. We are fortunate to have someone talented, who understands the Drupal culture and is familiar with our programs.

Piyush hit the ground running, helping us promote DrupalCon Baltimore. Now he is working on DrupalCon Vienna, Drupal.org case studies, and Drupal Jobs. Piyush offers a great new perspective and is a valuable addition to the team.

Thank you Srijan and welcome Piyush!

Jun 02 2017
Jun 02

DrupalCon Vienna T-shirts

Remember how we are making changes to DrupalCon Europe? These were hard decisions and some things we love we found just weren’t financially viable. Like free t-shirts. But one thing we heard a lot was “please don’t take away the t-shirts!”  

We heard you. And while it doesn’t make financial sense to give free t-shirts to all attendees, we still want to be able to continue to offer them. So we’ve come up with a plan.   

At DrupalCon Vienna, t-shirts will be offered to the following groups:

  • Individual Drupal Association members who register for DrupalCon Vienna between 5 - 16 June 2017. You must register in this two week window AND be an individual member of the Drupal Association.

  • Volunteers who work at least four (4) hours onsite in Vienna 26 - 29 September. You must check the volunteer box during registration and must show up on site to volunteer for four (4) hours or until released by event staff.

  • Volunteers part of the DrupalCon Program Team

  • Sprint Mentors

The fine print FAQ

I’m already a member, how do I make sure that I'll get a shirt?

If you are already an individual member, you get a t-shirt! BUT you MUST register in the first two weeks of ticket sales. Registrations after 16 June will not receive a t-shirt, member or not.

I’m not a member, can I do that during registration and still get a shirt?

Yes. If you are not a member you can become an individual member during your conference registration. You will be presented with a page during check-out that gives you the option to become a member.

I already registered but JUST saw this post! What do I do?

If you are a true early bird and register in the two weeks, but somehow missed this news post until after registering - that’s ok. As long as you become a member before the end of 16 June and you’ll still get a t-shirt.

The registration didn’t say anything about t-shirts or ask for my t-shirt size? What’s up?

After the 16 June cut-off date, eligible registrants will receive an email confirming their t-shirt along with a link to select their t-shirt size.

You got a session selected? Great!

We’ll refund your registration amount (but not your membership) and you get to keep the t-shirt. Our regular no-refund policy applies to all other sales.

You’re part of an organization that is buying a bulk amount of tickets for employees? Lucky you.

Your organization should provide you with an individual redemption code. You’ll need to redeem your individual registration before 16 June AND also be an individual member of the Drupal Association in order to get a t-shirt.

--

This news story is cross-posted on the Drupal Association Blog. To leave a comment, please do so on that post

Jun 02 2017
Jun 02

DrupalCon Vienna T-shirts

Remember how we are making changes to DrupalCon Europe? These were hard decisions and some things we love we found just weren’t financially viable. Like free t-shirts. But one thing we heard a lot was “please don’t take away the t-shirts!”  

We heard you. And while it doesn’t make financial sense to give free t-shirts to all attendees, we still want to be able to continue to offer them. So we’ve come up with a plan.   

At DrupalCon Vienna, t-shirts will be offered to the following groups:

  • Individual Drupal Association members who register for DrupalCon Vienna between 5 - 16 June 2017. You must register in this two week window AND be an individual member of the Drupal Association.

  • Volunteers who work at least four (4) hours onsite in Vienna 26 - 29 September. You must check the volunteer box during registration and must show up on site to volunteer for four (4) hours or until released by event staff.

  • Volunteers as part of the DrupalCon Program Team

  • Sprint Mentors

The fine print FAQ

I’m already a member, how do I make sure that I'll get a shirt?

If you are already an individual member, you get a t-shirt! BUT you MUST register in the first two weeks of ticket sales. Registrations after 16 June will not receive a t-shirt, member or not.

I’m not a member, can I do that during registration and still get a shirt?

Yes. If you are not a member you can become an individual member during your conference registration. You will be presented with a page during check-out that gives you the option to become a member.

I already registered but JUST saw this post! What do I do?

If you are a true early bird and register in the two weeks, but somehow missed this news post until after registering - that’s ok. As long as you become a member before the end of 16 June and you’ll still get a t-shirt.

The registration didn’t say anything about t-shirts or ask for my t-shirt size? What’s up?

After the 16 June cut-off date, eligible registrants will receive an email confirming their t-shirt along with a link to select their t-shirt size.

You got a session selected? Great!

We’ll refund your registration amount (but not your membership) and you get to keep the t-shirt. Our regular no-refund policy applies to all other sales.

You’re part of an organization that is buying a bulk amount of tickets for employees? Lucky you.

Your organization should provide you with an individual redemption code. You’ll need to redeem your individual registration before 16 June AND also be an individual member of the Drupal Association in order to get a t-shirt.

Mar 08 2017
Mar 08

DrupalCon is brought to you by the Drupal Association with support from an amazing team of volunteers. Powered by COD, the open source conference and event management solution. Creative design and implementation by Cheeky Monkey Media.

DrupalCon Baltimore is copyright 2016. Drupal is a registered trademark of Dries Buytaert.

Mar 06 2017
Mar 06

DrupalCon is brought to you by the Drupal Association with support from an amazing team of volunteers. Powered by COD, the open source conference and event management solution. Creative design and implementation by Cheeky Monkey Media.

DrupalCon Baltimore is copyright 2016. Drupal is a registered trademark of Dries Buytaert.

Feb 08 2017
Feb 08
Posted by RyeBurd on February 8, 2017 at 11:33pm

The Drupal Association is seeking a design partner for creative, graphic and website design services for a new DrupalCon brand. We're looking for people who understand the Drupal community, Drupal the project, software innovation, and our extreme nerdiness - and know how to turn these things into compelling designs that are functional, fun, and make people look twice. 

Main Deliverables

  • Overall conference branding
  • Content hierarchy and IA for the DrupalCon website
  • Design and theming
  • Digital and print graphics design

Scope of Work

The design partner's work will reinforce a positive brand image of DrupalCon to attendees and within the Drupal community year-round. The design should reflect DrupalCon's position as a major international software conference and the community connections that make DrupalCon a unique event. The SOW may include, but is not limited to, the following:

  • Overall creative design of DrupalCon brand
  • Digital outreach: newsletter templates, social media profiles (theme/icons), badges, ads
  • Signage: venue signage, banners, sponsor signs
  • Materials: slide decks, volunteer/staff clothing, giveaway items
  • Print: letterhead/templates, badgelettes, sponsorship guide
  • Style guide: production and use guides
  • Theming for the DrupalCon website

Commitments

The design partner will coordinate final design deliverables and production schedule with Drupal Association staff, and will actively participate in weekly planning meetings. 

Proposal Process

Please download the complete RFP which outlines the proposal process and requirements, and provides specific instructions on submission and question and answer processes. 

Timing

Proposals are due February 22, 2017 23:49 EST (UTC-5). Please refer to the RFP for a full award timeline. 

Selection Criteria

The respondent whole proposal best meets the needs of the project will be selected according to the following criteria:

  • Thoroughness of proposal
  • Demonstrated understanding of the project
  • Quality of work samples provided
  • Outcome of phone/video interview
  • Availability and responsiveness of the project team

Compensation

The Drupal Association's budget for DrupalCon design work is $30,000. The designer or company will also receive public recognition on the site via footer credits for 3 years and volunteer credits, and will receive a Bronze Sponsorship for the 2018 North America DrupalCon. 

Jan 25 2017
Jan 25

DrupalCon is brought to you by the Drupal Association with support from an amazing team of volunteers. Powered by COD, the open source conference and event management solution. Creative design and implementation by Cheeky Monkey Media.

DrupalCon Baltimore is copyright 2016. Drupal is a registered trademark of Dries Buytaert.

Jan 23 2017
Jan 23

DrupalCon is brought to you by the Drupal Association with support from an amazing team of volunteers. Powered by COD, the open source conference and event management solution. Creative design and implementation by Cheeky Monkey Media.

DrupalCon Baltimore is copyright 2016. Drupal is a registered trademark of Dries Buytaert.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web