Development News

Mass.gov Digital Services: Why we write at a 6th grade level

Main Drupal Feed - Thu, 10/04/2018 - 10:31
Variety of content and the need for empathy drive our effort to simplify language across Mass.gov

Nearly 7 million people live in Massachusetts, and millions more visit the state each year. These people come from different backgrounds and interact with the Commonwealth for various reasons.

Graphic showing more than 3 million visitors go to Mass.gov each month.

We need to write for everyone while empathizing with each individual. That’s why we write at a 6th grade reading level. Let’s dig into the reasons why.

Education isn’t the main factor

The Commonwealth has a high literacy rate and a world-renowned education network. From elementary school to college and beyond, you can get a great education here.

We’re proud of our education environment, but it doesn’t affect our readability standards. Navigating the Women, Infants, and Children (WIC) Nutrition Program might be challenging for everyone.

Complexity demands simplicity

People searching for nutrition services are doing so out of necessity. They’re probably frustrated, worried, and scared. That affects how people read and retain information.

Learn about our content strategy. Read the 2017 content team review.

This is the case for many other scenarios. Government services can be complicated to navigate. Our job is to simplify language. We get rid of the white noise and focus on essential details.

Time is not on our side

You don’t browse Mass.gov in your free time. It’s a resource you use when you have to. Think of it as a speedboat, not a cruise ship. They’ll both get you across the water, just at different speeds.

Graphic showing desktop visitors to Mass.gov look at more pages and have longer sessions than mobile and tablet visitors.

Mass.gov visitors on mobile devices spend less time on the site and read fewer pages. The 44% share of mobile and tablet traffic will only increase over time. These visitors need information boiled down to essential details. Simplifying language is key here.

Exception to the rule

A 6th-grade reading level doesn’t work all the time. We noticed this when we conducted power-user testing. Lawyers, accountants, and other groups who frequently use Mass.gov were involved in the tests.

These groups want jargon and industry language. It taught us that readability is relative.

Where we are today

We use the Flesch-Kincaid model to determine reading level in our dashboards. It accounts for factors like sentence length and the number of syllables in words.

This is a good foundation to ensure we consistently hit the mark. However, time is the most important tool we have. The more content we write, the better we’ll get.

Writing is a skill refined over time, and adjusting writing styles isn’t simple. Even so, we’re making progress. In fact, this post is written at a 6th grade reading level.

Interested in a career in civic tech? Find job openings at Digital Services.

Follow us on Twitter | Collaborate with us on GitHub | Visit our site

Why we write at a 6th grade level was originally published in MA Digital Services on Medium, where people are continuing the conversation by highlighting and responding to this story.

OSTraining: Should I Re-use Existing Drupal Fields?

Main Drupal Feed - Thu, 10/04/2018 - 04:08
Sometimes we're able to give really clear advice: "Do this!" or "Don't do that!"

This is not going to be one of those blog posts.

Drupal gives you the ability to re-use fields. If you have an "Image" field, you could choose to use that same field on every content type on your site. However, it's not always clear whether re-using fields is a good idea. Sometimes it is, sometimes it isn't.

Here's an overview of the advantages and disadvantages to consider before re-using Drupal fields.

OSTraining: Should I Re-use Existing Drupal Fields?

Main Drupal Feed - Thu, 10/04/2018 - 04:08
Sometimes we're able to give really clear advice: "Do this!" or "Don't do that!"

This is not going to be one of those blog posts.

Drupal gives you the ability to re-use fields. If you have an "Image" field, you could choose to use that same field on every content type on your site. However, it's not always clear whether re-using fields is a good idea. Sometimes it is, sometimes it isn't.

Here's an overview of the advantages and disadvantages to consider before re-using Drupal fields.

OSTraining: Should I Re-use Existing Drupal Fields?

Main Drupal Feed - Thu, 10/04/2018 - 04:08
Sometimes we're able to give really clear advice: "Do this!" or "Don't do that!"

This is not going to be one of those blog posts.

Drupal gives you the ability to re-use fields. If you have an "Image" field, you could choose to use that same field on every content type on your site. However, it's not always clear whether re-using fields is a good idea. Sometimes it is, sometimes it isn't.

Here's an overview of the advantages and disadvantages to consider before re-using Drupal fields.

lakshminp.com: Continuous delivery of Drupal using Ansible and Gitlab

Main Drupal Feed - Thu, 10/04/2018 - 02:37
Continuous delivery of Drupal using Ansible and Gitlab lakshminp Wed, 10/03/2018 - 22:37

Now that we have automated our deployment, it wouldn't be too hard to wire it with our code management setup. In this post, we will hook the Ansible scripts with our Git hosting setup so that a deployment gets triggered when you do a "git push". The idea is, deployment shouldn't be a chore, so that developers don't even think of it and only focus on the business logic of their application.

lakshminp.com: Continuous delivery of Drupal using Ansible and Gitlab

Main Drupal Feed - Thu, 10/04/2018 - 02:37
Continuous delivery of Drupal using Ansible and Gitlab lakshminp Wed, 10/03/2018 - 22:37

Now that we have automated our deployment, it wouldn't be too hard to wire it with our code management setup. In this post, we will hook the Ansible scripts with our Git hosting setup so that a deployment gets triggered when you do a "git push". The idea is, deployment shouldn't be a chore, so that developers don't even think of it and only focus on the business logic of their application.

lakshminp.com: Continuous delivery of Drupal using Ansible and Gitlab

Main Drupal Feed - Thu, 10/04/2018 - 02:37
Continuous delivery of Drupal using Ansible and Gitlab lakshminp Wed, 10/03/2018 - 22:37

Now that we have automated our deployment, it wouldn't be too hard to wire it with our code management setup. In this post, we will hook the Ansible scripts with our Git hosting setup so that a deployment gets triggered when you do a "git push". The idea is, deployment shouldn't be a chore, so that developers don't even think of it and only focus on the business logic of their application.

Community: Governance Task Force Community Update, October 2018

Main Drupal Feed - Thu, 10/04/2018 - 01:14

This is a public update on the work of the Governance Task Force.

The Governance Task Force has been working hard to prepare the proposal. We currently have a completed draft that we are actively refining for editorial improvement. As part of the review, we believe it is important to get initial feedback from some key stakeholders to ensure there are no major issues identified. We'll consider making changes to the proposal at our discretion. The proposal will then be delivered to the community and we’re very excited to soon share this. While things may change, we believe we are on time to deliver the proposal before the end of October.

Our team is actively discussing the handoff and next steps that follow from our work. We recognize that there may be ongoing support needed and want to do what we can to help follow-up efforts. It is imperative that momentum is maintained after our proposal is delivered.

We will be recommending a public commentary period before any recommendations move forward for the community to share their thoughts. This commentary period will likely outlast the task force. The task force will officially disband at the end of October, as we have stated in our charter. This does not mean that the work is complete, as there may be discussion and, most importantly, approved recommendations will need support to move forward. The task force wants to do what we can to enable the next steps and we are actively discussing how this might happen, even if we, as individuals, participate without an official charter.

We continue to be committed to serving the community and operating in a transparent way. If you wish to reach us, please fill out this Google form and we will respond as soon as we’re able.

Community: Governance Task Force Community Update, October 2018

Main Drupal Feed - Thu, 10/04/2018 - 01:14

This is a public update on the work of the Governance Task Force.

The Governance Task Force has been working hard to prepare the proposal. We currently have a completed draft that we are actively refining for editorial improvement. As part of the review, we believe it is important to get initial feedback from some key stakeholders to ensure there are no major issues identified. We'll consider making changes to the proposal at our discretion. The proposal will then be delivered to the community and we’re very excited to soon share this. While things may change, we believe we are on time to deliver the proposal before the end of October.

Our team is actively discussing the handoff and next steps that follow from our work. We recognize that there may be ongoing support needed and want to do what we can to help follow-up efforts. It is imperative that momentum is maintained after our proposal is delivered.

We will be recommending a public commentary period before any recommendations move forward for the community to share their thoughts. This commentary period will likely outlast the task force. The task force will officially disband at the end of October, as we have stated in our charter. This does not mean that the work is complete, as there may be discussion and, most importantly, approved recommendations will need support to move forward. The task force wants to do what we can to enable the next steps and we are actively discussing how this might happen, even if we, as individuals, participate without an official charter.

We continue to be committed to serving the community and operating in a transparent way. If you wish to reach us, please fill out this Google form and we will respond as soon as we’re able.

Community: Governance Task Force Community Update, October 2018

Main Drupal Feed - Thu, 10/04/2018 - 01:14

This is a public update on the work of the Governance Task Force.

The Governance Task Force has been working hard to prepare the proposal. We currently have a completed draft that we are actively refining for editorial improvement. As part of the review, we believe it is important to get initial feedback from some key stakeholders to ensure there are no major issues identified. We'll consider making changes to the proposal at our discretion. The proposal will then be delivered to the community and we’re very excited to soon share this. While things may change, we believe we are on time to deliver the proposal before the end of October.

Our team is actively discussing the handoff and next steps that follow from our work. We recognize that there may be ongoing support needed and want to do what we can to help follow-up efforts. It is imperative that momentum is maintained after our proposal is delivered.

We will be recommending a public commentary period before any recommendations move forward for the community to share their thoughts. This commentary period will likely outlast the task force. The task force will officially disband at the end of October, as we have stated in our charter. This does not mean that the work is complete, as there may be discussion and, most importantly, approved recommendations will need support to move forward. The task force wants to do what we can to enable the next steps and we are actively discussing how this might happen, even if we, as individuals, participate without an official charter.

We continue to be committed to serving the community and operating in a transparent way. If you wish to reach us, please fill out this Google form and we will respond as soon as we’re able.

myDropWizard.com: Drupal 6 security update for Print module (CRITICAL!)

Main Drupal Feed - Wed, 10/03/2018 - 21:30

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Critical security release for the Print module to fix a Remote Code Execution (RCE) vulnerability.

The Print module provides printer-friendly versions of content, including send by e-mail and PDF versions.

The module doesn't sufficiently sanitize the arguments passed to the wkhtmltopdf executable, or HTML passed to dompdf or other PDF generation tools.

See the security advisory for Drupal 7 for more information.

NOTE: This vulnerability has a lower risk in Drupal 6 than in Drupal 7 (where it's Highly Critical). This is because you can't pass shell commands to execute using the HTTP basic auth user/pass, like you can in Drupal 7.

Here you can download the Drupal 6 patch.

If you have a Drupal 6 site using the Print module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

myDropWizard.com: Drupal 6 security update for Print module (CRITICAL!)

Main Drupal Feed - Wed, 10/03/2018 - 21:30

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Critical security release for the Print module to fix a Remote Code Execution (RCE) vulnerability.

The Print module provides printer-friendly versions of content, including send by e-mail and PDF versions.

The module doesn't sufficiently sanitize the arguments passed to the wkhtmltopdf executable, or HTML passed to dompdf or other PDF generation tools.

See the security advisory for Drupal 7 for more information.

NOTE: This vulnerability has a lower risk in Drupal 6 than in Drupal 7 (where it's Highly Critical). This is because you can't pass shell commands to execute using the HTTP basic auth user/pass, like you can in Drupal 7.

Here you can download the Drupal 6 patch.

If you have a Drupal 6 site using the Print module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

myDropWizard.com: Drupal 6 security update for Print module (CRITICAL!)

Main Drupal Feed - Wed, 10/03/2018 - 21:30

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Critical security release for the Print module to fix a Remote Code Execution (RCE) vulnerability.

The Print module provides printer-friendly versions of content, including send by e-mail and PDF versions.

The module doesn't sufficiently sanitize the arguments passed to the wkhtmltopdf executable, or HTML passed to dompdf or other PDF generation tools.

See the security advisory for Drupal 7 for more information.

NOTE: This vulnerability has a lower risk in Drupal 6 than in Drupal 7 (where it's Highly Critical). This is because you can't pass shell commands to execute using the HTTP basic auth user/pass, like you can in Drupal 7.

Here you can download the Drupal 6 patch.

If you have a Drupal 6 site using the Print module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

Ashday's Digital Ecosystem and Development Tips: Drupal Module Spotlight: Pathauto

Main Drupal Feed - Wed, 10/03/2018 - 20:00

Although it can sometimes be easy to forget about that little URL bar at the top of your browser, what it contains for each page can be surprisingly important. Creating good paths (the part of the URL after the domain name) for your site content can have numerous benefits, especially for SEO, but doing so can be a bit frustrating. Usually, you end up needing to re-type most of the page title into Drupal's URL alias field, which isn't necessarily too bad on its own, but it's still an extra step whenever you create content. And what about when you update the page and change the title? This is where it gets very easy to forget to change the path, which can lead not only to worse SEO but also to your site's visitors not ending up on a page with the content they expected it to have.

Ashday's Digital Ecosystem and Development Tips: Drupal Module Spotlight: Pathauto

Main Drupal Feed - Wed, 10/03/2018 - 20:00

Although it can sometimes be easy to forget about that little URL bar at the top of your browser, what it contains for each page can be surprisingly important. Creating good paths (the part of the URL after the domain name) for your site content can have numerous benefits, especially for SEO, but doing so can be a bit frustrating. Usually, you end up needing to re-type most of the page title into Drupal's URL alias field, which isn't necessarily too bad on its own, but it's still an extra step whenever you create content. And what about when you update the page and change the title? This is where it gets very easy to forget to change the path, which can lead not only to worse SEO but also to your site's visitors not ending up on a page with the content they expected it to have.

Ashday's Digital Ecosystem and Development Tips: Drupal Module Spotlight: Pathauto

Main Drupal Feed - Wed, 10/03/2018 - 20:00

Although it can sometimes be easy to forget about that little URL bar at the top of your browser, what it contains for each page can be surprisingly important. Creating good paths (the part of the URL after the domain name) for your site content can have numerous benefits, especially for SEO, but doing so can be a bit frustrating. Usually, you end up needing to re-type most of the page title into Drupal's URL alias field, which isn't necessarily too bad on its own, but it's still an extra step whenever you create content. And what about when you update the page and change the title? This is where it gets very easy to forget to change the path, which can lead not only to worse SEO but also to your site's visitors not ending up on a page with the content they expected it to have.

Drupal Association blog: Overcoming challenges faced by Drupal events organizers

Main Drupal Feed - Wed, 10/03/2018 - 17:35

This is a guest blog by Marina Paych (paych) with tips for coordinating Drupal training events.

Organizing a Drupal Global Training Days event is a great way to spread the word about Drupal, engage more novice developers, and increase adoption. If you haven’t heard about Drupal GTD, typically, these events are a one- or two-day training where experienced developers deliver sessions about Drupal and teach attendees how to create their first Drupal website or module.

Why is this event called global? It’s because it is held globally on or around a certain date every quarter. Organizers in the North and South Americas, Europe, Africa, Asia, and Australia come together to create the GTD movement and show the power of community-organized events worldwide.


Introducing Drupal 8 in Riyadh. Photo by @EssamAlQaie.

However, Drupal event organizers face challenges while running trainings and conferences. The Drupal Global Training Days Working Group conducted a survey to find out common difficulties for organizers and how the working group can offer support. We came up with an online questionnaire first, and then held several in-depth interviews with organizers to validate gathered quantitative data.

In this article, I've collected the most widespread challenges of Drupal Global Training Days organizers and brainstormed possible ways to overcome them based on my personal event organizing experience and good practices of other organizers. Let's dive in.


Group photo at GTD in Omsk. Photo by @ADCISolutions.

Issue 1: a lack of speaker resources (documentation/PPTs of other organizers)

What do we teach? A lack of ready-made resources is the most common concern of organizers worldwide. And I admit that it is an issue. There is no special folder with all the up-to-date and ready to deliver presentations for everyone to use.

There are two main reasons for this:

  1. Most organizers hold GTD events on their local language: Spanish, Russian, etc., and that makes such PPTs hardly usable for other countries.

  2. All the organizers have different event programs due to different profiles of attendees: in some countries, the attendees are mostly beginners, in other countries - experts.

These barriers make it harder (if not impossible) to have PPTs for all types of sessions and all types of audiences.

However, there’s a way that you can overcome this problem: ask other organizers for help! Join the group at Drupal.org. There, you can create a new discussion and ask people to share their documents or at least their events programs, so you will be able to adapt the materials to your audience and goals. Also, there is a Slack channel, where you can do the same thing; ask other organizers for help.

I did this when we decided to add a workshop to our GTD. Previously, we only had theoretical sessions, but then we wanted to deliver a practical workshop. Since we had never run a workshop before, I asked other organizers if anyone already delivered workshops. And Mauricio replied to me and shared lots of materials they've used in Nicaragua.

We discussed his materials together with our team of speakers and we adapted some related to our agenda and goals. What was also very useful:a technology stack Mauricio uses on his events. We didn’t know what to choose to use in our workshop, so we also used tools that were suggested by Mauricio, which were helpful.

Incorporating the experience of Nicaraguan GTD events allowed us to avoid starting from scratch, and we delivered a quality event.

Also, there is a global initiative aimed to translate the Drupal 8 User Guide to different languages. If your local language is one of the following: Català, Magyar, Español, Українська, 简体中文, Français, Deutsch, فارسی,  Bahasa Indonesia, 日本語 — you can use these materials for your training. If your language is not on the list yet, you can help translate it.

Issue 2: a lack of unified promotional materials

The second widespread problem is the lack of promotional materials. The situation is similar to the first issue. Different languages and different profiles of attendees make it difficult to have a single set of materials to promote all GTD events. We have discussed what we can do during some of our GTD Working Group calls, and we realized that it is best for each organizer to create local promotional materials because they know their audience better and can transmit the GTD main goal -- Drupal Adoption -- in plain comprehensive language.

But again, feel free to ask for help or advice in the group or Slack channel from organizers who have had success in promoting their events.

Issue 3: a lack of speakers

Some organizers mentioned that they often don’t have people to deliver sessions due to different reasons: developers are busy with work, or are too shy to speak, or there is no one at all to deliver sessions.

Scenario #1

If your potential speakers agree to prepare and deliver sessions but are too busy to really engage, then schedule an event in advance and help them plan the timeline of preparation in a way that does not take many hours per week. Show them that if they start preparing in advance and they take it slow, they will be able to do everything simultaneously. But, of course, it will require your time to remind and check in for good results.

Scenario #2

If your potential speakers are too shy to speak, try to involve them gradually. Ask them to prepare a short internal report on something simple for the session topic. Then provide them with quality feedback and highlight the strong sides of their presentation. And then, when they are ready, invite them to a bigger event. It will take some time, but your efforts will pay off when your event achieves your goals.

Scenario #3

You are a solo organizer or there is no one available to speak in your company. There are two possible ways to overcome this problem:

  1. Find speakers from other Drupal companies in your region. They will get their company's promotional support and you will get speakers with experience. The other option can be applied if you have a strong community in your city or region. Then you can invite people from the community to speak at the event.

  2. If the first way can’t be implemented, find remote speakers and make video calls or even make an online event. The Global Drupal Community is HUGE. I’m sure you will find amazing and motivated speakers for your event within the community.

Issue 4: low conversion rates (many people sign up, few attend)

If this is a one-time thing, it might be just random low attendance. For example, the weather suddenly became terrible and people didn’t want to go outside at all. That is not specific to your event.

But if this constantly happens, you need to carefully assess your promotional efforts. Possible reasons:

  • Promotional materials are misleading: the expectations attendees had were not justified. Check that you deliver what you promise and improve your promotional materials and texts according to it. To identify the gap between the expectations and reality, organize a couple of in-depth interviews with the representatives of your target audience or add a question about expectations to the application form.

  • Attendees servicing issues: usually, it is a couple of weeks between the date when a person sends an event application form and an actual event date. A person can forget about the event, can lose interest, or even change their plans. In order to avoid that, plan some touch points with people who have already registered. Shoot emails, tell about the sessions and programs, send reminders.

  • Not exactly your target audience: if your promotional materials are distributed to channels that are popular among a wider audience (not only tech students but all students, for instance), you might receive many sign-ups but only tech people will attend. Be mindful when choosing channels for promotion; make sure your target audience is there.

There may be other reasons why you have a low conversion rate: it's difficult to get to your venue, the price (if an event is paid) is too high, the agenda is not that interesting, etc. But you need to find the reasons for your particular case. Talk to attendees, ask them what would improve their experience, and your conversion rate will increase when you implement their feedback. Just don't forget to mention your improvements in your promotional materials so people know that you really listened to them.

Issue 5: a lack of money for a venue, coffee breaks

How great is it when you come to an event and there is free coffee there? To ensure your attendees will come to a comfortable venue and enjoy sessions after a welcome coffee break, you can take simple steps:

  • Organize the event in the office of an IT company: it is great if your office is good for events, but if it isn’t, you can approach bigger companies and offer a collaboration: you will organize the event and they provide a venue. Perhaps they can distribute their promotional materials during the event. Of course, it doesn't necessarily need to be an IT company office; you can find any comfortable and beautiful venue, but IT offices are often cool and prepared for IT events.

  • Organize the event in the University: you can try to negotiate with Universities to let you organize your event there without a fee. The Universities have two main advantages: they usually have all the necessary equipment for events and they also have tech students who can possibly attend your event.

  • Find in-kind partners for your event: Drupal GTD is a globally supported event that attracts many people. You can use this to your benefit and find partners for your event who will provide you with goods or services in exchange for promotion. You can put their banner in the event venue. It won’t hurt your event to have a few banners, and you will be able to offer your attendees a more pleasant experience without any monetary investment.

Issue 6: no sponsors

Usually, most of the event's needs can be covered with the help of in-kind partners. It is much easier to find in-kind partners than sponsors. So, I would recommend you start with in-kind partners, especially if you have never sold event sponsorships before.

If, however, you need sponsorship:

  1. Create a pool of companies who might be interested in your event.

  2. Find contacts for decision-makers from these companies.

  3. Come up with a list of benefits you can offer to them (promotion, employer branding, speaking at the event, etc.) and set a price.

  4. Create a customized proposal for each company.

It’s best to set up a meeting with a company because it will allow you to talk with a person and see which of your benefits are more relevant for them, and provide more information.

If some companies support your local Drupal or IT community, it is likely that they could support your event.

Issue #7: a lack of awareness

The GTD events are not well-known in some regions, which creates additional challenges for organizers. It becomes harder to find sponsors, speakers, and attract attendees. If this is your case, the action that can help is for you to inform Drupal companies in your region about the benefits of participating in the GTD movement. Benefits like promotion of a company within the Drupal Community, with a possibility to be featured in blog posts and tweets, spotting on a Drupal events map, and even credits on Drupal.org!

In order to promote your event and attract more attendees, you can focus on the fact that the same events are being organized on the same day all over the world. It usually inspires people and makes them curious to attend. Feel free to use the videos from GTD organizers (video #1, video #2) during your promotion or on-site at your event.


Mr. Thomas speaks at GTD in Kerala. Photo by @zyxware.

Conclusion

Event management is a complex and sometimes complicated process. But it is interesting and allows a huge amount of opportunities for improvement and experimentation. I’ve been organizing events of different scale for years, and I still find something interesting in the work.

That is why I wish all the GTD organizers to be proactive, creative, and consistent. These qualities will help you make wonderful events and engage hundreds of people with Drupal!

And the Drupal GTD Working Group (paych, lizzjoy, dinarcon, rgs, rachit_gupta, pendashteh, solomonkitumba) is always here to lend you a hand and help with advice.

Feel free to contact me with any questions about this article or event management in general.

Join the Drupal GTD Group and Slack Channel, and follow us on Twitter :)

Happy GTD!

Pages