Jun 20 2018
Jun 20

At the end of June 2018, the third edition of the Drupal Business Survey will be launched by One Shoe and Exove in collaboration with the Drupal Association. You can read the results of the 2017 survey in this previous blog post.

With this worldwide survey, new insights into key issues that Drupal company owners and business leaders face, can be discovered. The purpose of the survey is to provide information on how Drupal agencies are doing worldwide and how Drupal fits in business-wise.

Seeking your input

Therefore, the initiators of the Drupal Business Survey 2018, call for input from the Drupal Community. Any Drupal business related topics, ideas or suggestions you wish to see investigated, are more than welcome.

This year’s Drupal Business Survey will focus on the health of Drupal companies and the obstacles and enablers for Drupal’s business success. The initiators also hope to gain information on how to further improve the demand for Drupal projects.

You can send your questions to Janne Kalliola ([email protected]) or Michel van Velde ([email protected]) before the end of June. The Drupal Business Survey will become available for participants soon after. The results of the survey will be officially published at this year’s Drupal Europe in Darmstadt, Germany.

Jun 20 2018
Jun 20

Drupal Association logo with added Pride

You may have noticed today that we have added a little color to our Drupal Association logo on social media. The changed logo will be around until the end of June, which is traditionally Pride Month.

The Drupal Association is an educational non-profit and does not advocate policy. I personally wanted to make this happen simply to say thank you to everyone at the Drupal Association who have made this LGBTQIA woman feel extraordinarily welcome and empowered this year.

For all LGBTQIA people and their allies, I’d also like to take the opportunity to draw their attention to the Drupal Rainbow Group on groups.drupal.org.

Could we, as a community, do more for Pride Month next year? Let me know - and let’s organise ourselves in the Drupal Rainbow Group.

Rachel

Jun 13 2018
Jun 13

Did you know you have a say in who is on the Drupal Association Board? Each year, the Drupal community votes in a member who serves two years on the board. It’s your chance to decide which community voice you want to represent you in discussions that set the strategic direction for the Drupal Association. Go here for more details.

Voting takes place from July 2 until July 13. Anyone who has a Drupal.org profile page and has logged in to their account in the last year is eligible to vote. This year, there are candidates from around the world. Now it’s time for you to meet them.

Meet The Candidates

We just concluded the phase where nine candidates nominated themselves from six different continents for the board seat. From now through July 2, we encourage you to check out each person’s candidate profile, where they explain which board discussion topics they are most passionate about and what perspectives they will bring to the board.

This year, we asked candidates to include a short video - a statement of candidacy - that summarizes why you should vote for them. Be sure to check them out. Videos are found in the candidate’s profile as well as here:

What To Consider

When reviewing the candidates, it is helpful to know what the board is focusing on over the next year or two, so you can decide who can best represent you.

Here are the key topics the board will focus on.

  • Strengthening Drupal Association’s sustainability. The board discusses how the Association can improve its financial health while expanding its mission work.

  • Understanding what the Project needs to move forward and determine how the Association can help meet those needs through Drupal.org and DrupalCon.

  • Growing Drupal adoption through our own channels and partner channels.

  • Developing the strategic direction for DrupalCon and Drupal.org.

There are certain duties that a candidate must be able to perform as a board member. The three legal obligations are duty of care, duty of loyalty, and duty of obedience. In addition to these legal obligations, there is a lot of practical work that the board undertakes. These generally fall under the fiduciary responsibilities and include:

  • overseeing Financial Performance

  • setting Strategy

  • setting and Reviewing Legal Policies

  • fundraising

  • managing the Executive Director

Hopefully providing this context gives you a helpful way to assess the candidates as you decide how to vote From July 2 until July 13.

We encourage you to ask the candidates questions. Use comments to leave a question on their candidate profile page.

May 29 2018
May 29

Donate today

The Promote Drupal Initiative is your opportunity to make Drupal - and your business - known and loved by new decision makers. Donate to the Promote Drupal Fund today. Help us help you grow your business.

Together, let's show the world just how amazing Drupal is for organizations.

We are 70% to the $100,000 goal. Help us reach the goal.

Donate to the Promote Drupal Fund today. Invest $1,000 or more and be highlighted in:

  • Dries’ blog post once we reach 75% of goal

  • Dries’ presentation at Frontend United

Invest today!

To learn more go to: https://www.drupal.org/promotedrupal or watch the Driesnote.

Donate today

May 14 2018
May 14

Too long?

One of the things I love the most about my new role as Community Liaison at the Drupal Association is being able to facilitate discussion amongst all the different parts of our Drupal Community. I have extraordinary privilege of access to bring people together and help work through difficult problems.

The governance of the Drupal project has evolved along with the project itself for the last 17 years. I’m determined in 2018 to help facilitate the next steps in evolving the governance for our growing, active community.

2017 - A Year of Listening

Since DrupalCon Baltimore, the Drupal Community has:

  • Held a number of in-person consultations at DrupalCon Baltimore around the general subject of project governance

  • Ran a series of online video conversations, facilitated by the Drupal Association

  • Ran a series of text-based online conversations, facilitated by members of our community across a number of time zones

  • Gathered for a Governance Round Table at DrupalCon Nashville.

This has all led to a significant amount of feedback.

Whilst I highly recommend reading the original blog post about online governance feedback sessions for a full analysis, there was clearly a need for better clarity, communications, distributing leadership, and evolving governance.

2018 - A Year of Taking Action

There are many things happening in 2018 but I want to concentrate for now on two important activities; how we continue to develop our Values and how we can continue to develop Governance of our community.

So, why am I separating “Values” and “Governance”, surely they are connected? Well, they are connected, but they are also quite different and it is clear we need to define the difference within our community.

In the context of the Drupal Community:

  • “Values” describe the culture and behaviors expected of members of the Drupal community to uphold.

  • “Governance” describes the processes and structure of interaction and decision-making that help deliver the Project’s purpose whilst upholding the Values we agree to work by.

Values

What’s happened?

Quoting Dries:

Over the course of the last five months, I have tried to capture our fundamental Values & Principles. Based on more than seventeen years of leading and growing the Drupal project, I tried to articulate what I know are "fundamental truths": the culture and behaviors members of our community uphold, how we optimize technical and non-technical decision making, and the attributes shared by successful contributors and leaders in the Drupal project. 

Capturing our Values & Principles as accurately as I could was challenging work. I spent many hours writing, rewriting, and discarding them, and I consulted numerous people in the process. After a lot of consideration, I ended up with five value statements, supported by eleven detailed principles.”

The first draft of the Values & Principles was announced to the community at DrupalCon Nashville.

What’s next?

Now that we have the first release of the Values & Principles, we need a process to assist and advise Dries as he updates the Values & Principles. After hearing community feedback, Dries will charter a committee to serve this role. A forthcoming blog post will describe the committee and its charter in more detail.

Community Governance

What’s happened?

At DrupalCon Nashville, many useful discussions happened on governance structure and processes.

  • A Drupal Association Board Meeting, with invited community members, met to talk with existing governance groups to find out what is working and not working. We realized that governance of the Drupal Community is large and it is difficult to understand all of the parts. We began to see here a possibility for further action.

  • The Community Conversation, “Governance Retrospective”, helped us to see that improving communications throughout the community is hugely important.

  • The Round Table Discussion, around community governance, brought together Dries, staff of the Drupal Association and Drupal Association Board, representatives of many of our current community working groups, representatives of other interested groups in the community and other community members. This group looked at both Values & Principles but also looked into how we are currently governed as a community and how can improve that.

All these things lead to one of the very best things of the DrupalCon experience; the “hallway track”. More and more throughout DrupalCon Nashville, ideas were formed and people stepped forward to communicate with each other, about how we can improve our governance. This happens all the time when we discuss the code of Drupal; I’m very excited to see it happening in other aspects of our project, too.

What’s next?

A structured approach is needed to ensure all in our community understand how decisions are being made and could have input. Speaking with a number of those involved in many of the discussions above, a consensus developed that we can start putting something into action to address the issues raised. Dries, as Project Lead, has agreed that:

  • A small Governance Task Force would be created for a fixed period of time to work on and propose the following:

    • What groups form the governance of the Drupal community right now?

    • What changes could be made to governance of the Drupal community?

    • How we could improve communication and issue escalation between groups in the community?

  • Task Force membership would be made up of a small group consisting of:

    • Adam Bergstein

    • David Hernandez

    • Megan Sanicki

    • Rachel Lawson

  • This Task Force would discuss whether or not it is beneficial to form a more permanent Governance Working Group, to handle escalated issues from other Working Groups that can be handled without escalation to the Project Lead.

  • This Task Force will propose a structure, processes needed to run this new structure, charters, etc. by end of July 2018 to the Project Lead for approval.

The Governance Task Force begins work immediately. The Charter under which we will work is attached.

I will help to facilitate reporting back regularly as we progress. I look forward to 2018 showing progress on both of these initiatives.

I am, as always, very happy to chat through things - please say hello!

tl;dr

We are going to create two new committees:

  1. A Values Committee
    • to continue work on the Values & Principles
    • Still to be created and chartered - more soon in a later blog post.
  2. A Governance Taskforce
    • To look at the mechanisms of governance - how groups communicate activity, escalate issues etc
    • Will propose mechanisms of governance changes to Project Lead
    • Has a fixed lifetime of approx two months
    • Membership formed and chartered.
May 01 2018
May 01

Now that Drupal 8 is maturing, it is an exciting time to be on the Drupal Association Board. With Drupal always evolving, the Association must evolve with it so we can continue providing the right kind of support. And, it is the Drupal Association Board who develops the Association’s strategic direction by engaging in discussions around a number of strategic topics throughout their term. As a community member, you can be part of this important process by becoming an At-large Board Member.

We have two At-large positions on the Association Board of Directors. These positions are self-nominated and then elected by the community. Simply put, the At-large Director position is designed to ensure there is community representation on the Drupal Association Board. If you are interested in helping shape the future of the Drupal Association, we encourage you to read this post and nominate yourself between 1-11 June, 2018.

What are the Important Dates

Self nominations: 1-11 June, 2018

Meet the candidates: 12-29 June 2018

Voting: 2-13 July, 2018

Votes ratified, Winner announced: 25 July, 2018

How do nominations and elections work?

Specifics of the election mechanics were decided through a community-based process in 2012 with participation by dozens of Drupal community members. More details can be found in the proposal that was approved by the Drupal Association Board in 2012 and adapted for use this year.

What does the Drupal Association Board do?

The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction for serving the Drupal Association’s mission, which we achieve through Drupal.org and DrupalCon. Our mission is: Drupal powers the best of the Web.  The Drupal Association unites a global open source community to build and promote Drupal.

New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day-to-day operations of the Drupal Association, including program execution, staffing, etc.

Directors are expected to contribute around five hours per month and attend three in-person meetings per year (financial assistance is available if required).

Association board members, like all board members for US-based organizations, have three legal obligations: duty of care, duty of loyalty, and duty of obedience. In addition to these legal obligations, there is a lot of practical work that the board undertakes. These generally fall under the fiduciary responsibilities and include:

  • Overseeing Financial Performance

  • Setting Strategy

  • Setting and Reviewing Legal Policies

  • Fundraising

  • Managing the Executive Director

To accomplish all this, the board comes together three times a year during two-day retreats. These usually coincide with the North American and major European Drupal Conferences as well as one February meeting. As a board member, you should expect to spend a minimum of five hours a month on board activities.

Some of the topics that will be discussed over the next year or two are:

  • Strengthen sustainability

  • Grow Drupal adoption through our channels and partner channels

  • Evolve drupal.org and DrupalCon goals and strategies.

Please watch this video to learn more.

Who can run?

There are no restrictions on who can run, and only self-nominations are accepted.

Before self-nominating, we want candidates to understand what is expected of board members and what types of topics they will discuss during their term. That is why we now require candidates to:

What will I need to do during the elections?

During the elections, members of the Drupal community will ask questions of candidates. You can post comments on candidate profiles here on assoc.drupal.org.

In the past, we held group “meet the candidate” interviews. With many candidates the last few years, group videos didn’t allow each candidate to properly express themselves. We replaced the group interview and allow candidates to create their own 3 minute video and add it to their candidate profile page. These videos must be posted by 11 June, the Association will promote the videos to the community from 12 -29 June. Hint - Great candidates would be those that exemplify the Drupal Values & Principles. That might provide structure for a candidate video?

How do I run?

From 1-11 June, go here to nominate yourself.  If you are considering running, please read the entirety of this post, and then be prepared to complete the self-nomination form. This form will be open on 1 June, 2018 through 11 June, 2018 at midnight UTC. You'll be asked for some information about yourself and your interest in the Drupal Association Board. 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. We will announce the new board member at the 25 July, 2018 public board meeting and via our blog and social channels.

Reminder, you must review the following materials before completing your candidate profile:

Who can vote?

Voting is open to all individuals who have a Drupal.org account by the time nominations open and who have logged in at least once in the past year. If you meet this criteria, your account will be added to the voters list on association.drupal.org and you 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.

Elections process

Voting will be held from 2-13 July, 2018. During this period, you can review and comment on candidate profiles on assoc.drupal.org.

Finally, the Drupal Association Board will ratify the election and announce the winner on 25 July.

Have questions? Please contact Drupal Association Community Liaison, Rachel Lawson.

Many thanks to nedjo for pioneering this process and documenting it so well!

Feb 07 2018
Feb 07

DrupalCon has long had a Code of Conduct that we all agree to as part of participating in the event. It was originally derived from the Drupal Code of Conduct and added sections specific to in-person events.

We are constantly striving to improve all that we offer to make DrupalCon a great event for all Drupal professionals and it is now time to make a change to our DrupalCon Code of Conduct.

Making a positive change

When I first started at the Drupal Association at the beginning of the year, I was very pleased to discover that the Association staff had already made significant progress on an updated version of the DrupalCon Code of Conduct that included clearer description of what is expected of participants at DrupalCon, where various responsibilities were held for enforcement and what consequences should be expected for falling foul of the code. As the new Community Liaison, though, it was important that I took this work to the Drupal and wider web professional community and gained further insight into producing something that worked for us all.

Consulting the community

Having spent time on the Community Working Group, I was aware that consulting the community at large is hugely important but can be a huge undertaking that can potentially become never ending. Indeed, when the original Drupal Code of Conduct was in development, the process took many months to reach a result. Whilst we wanted to involve people, we also wanted to deliver something better than the current Code in time for DrupalCon Nashville 2018.

So, my methodology was to choose eight people from different parts of our community to comment on the draft Code of Conduct, plus ask them to nominate two extra people who I should also ask to make comment. I requested that they nominate someone who they felt would have a similar outlook to themselves and someone they thought might have a different outlook. This meant we had a focused team of people from the community that could work on this over a very short period, but one that I knew wouldn’t be overly influenced by my personal choices. I was also careful to choose people from several continents.

The vast majority of suggestions and comments they proposed were accepted, either directly or with some adjustment by either Association staff or our lawyers. At the end of the day, the code has to be legal, enforceable and protect both conference participants and the project’s legal entities.

The New Code

The draft has now been reviewed by Drupal Association staff, Drupal Community members and the Drupal Association Lawyers. It is ready to go and will now be applied to DrupalCon Nashville 2018.

I do want to talk about a few of the improvements we have made, though.

Clarity

One of the challenges of the old Code was that, whilst being very positive, it failed to make it clear to all DrupalCon participants exactly what was expected of them. We have taken the time to write about what behaviors are and are not acceptable in the context of DrupalCon. You will also see that we clearly state that the expectations of leaders at DrupalCon are expected to uphold even higher standards.

Our actions have consequences

We have also added sections that detail exactly what is expected of people and how failing those requirements will be dealt with.

One of the significant changes here is we separated the responsibilities for dealing with unacceptable behavior from that of supporting participants in resolving conflicts. Who to contact in the case of each is more clearly displayed, along with exactly who will be initially handling reported incidents.

Best practices

We didn’t just make all this up. We spoke with many organisations and used well-known best practice where it was available. We have detailed where much of the best practice was found at the end of the Code of Conduct.

We are also sharing the new DrupalCon Code of Conduct under a Creative Commons license, as before. If you are organising a Drupal event, you are very welcome to make use of this and add in your own contact information.

Release early, release often

Finally, I want to talk about the future. As mentioned earlier, whilst we consulted members of the Drupal Community, we were not able to incorporate all their comments at this time. Some comments would simply not have met our objectives to protect the Community and the Project but others, whilst beneficial, require further development that would mean we would not be ready for Nashville. There are also other initiatives taking place within the overall Drupal Project, like the refreshing of the Drupal Project’s value statement and a Drupal Community Code of Conduct, that we would want to incorporate back into the DrupalCon Code of Conduct. I’m sure the aforementioned best practices will evolve over time, too, and I want a mechanism where we can take advantage of that.

Well, we already have an established (and, I feel, successful!) process in Drupal Core; which now makes releases on a regular schedule. I propose that we make an annual DrupalCon Code of Conduct release, at this time each year. I will be setting up a project to manage this. So, if you believe there are ways we can still improve our Code of Conduct, there will be a mechanism to achieve it.

Nov 30 2017
Nov 30

It seems strange to me that the very first thing I need to do as the Drupal Association’s new Community Liaison is say something; given that the primary focus of the role is to listen to you, the Drupal Community.

Rachel speaking in Chișinău, Moldova. Used with permission of Drupal Moldova
Speaking at MoldCamp in Chișinău, Moldova. Used with permission of Drupal Moldova.

I’ve had the privilege of getting to know the Drupal Community over many years; from my first DrupalCamp in Leeds back in 2011, through volunteering at DrupalCon London, co-organising Drupal ScienceCamp in Cambridge and now being part of the team that organises the Mentored Sprints at DrupalCon and spending time as a member of the Community Working Group. It is a Community of wonderfully diverse and interesting individuals who I love working with.

Our hope with my role as Community Liaison is to continually improve both the Community’s understanding of the Drupal Association’s purpose and mission and especially the Drupal Association’s understanding of this diverse Community. We are here to support the Drupal Community and we do that best when we understand the Drupal Community, in all its forms.

In Antwerp, helping work on the future of DrupalCon Europe
In Antwerp for DupalCampBE, helping work on the future of DrupalCon Europe

I will be trying to get involved with as many groups that work with the Drupal Association as possible over the next few months, in an effort to help support their activities and our mutual understanding. I will also be a “go to person”, both online and in-person to find out things about the Drupal Association.

Of course, there is only one of me and the Drupal Association’s mission is quite tightly defined so there are things I won’t be doing in this role:

  • I won’t be affecting the future technical direction of Drupal (other than through my continuing desire to keep up occasionally contributing to Drupal Core!).
  • I’m here to facilitate and support, not enact change myself. I won’t be managing the Community, I’ll be helping the Community manage itself.
  • I won’t be able to visit every Drupal event - it’s just not possible!
  • Finally, I will be making a phased withdrawal from being a full member of the Community Working Group between now and the end of the year. While several Association board members have served on the CWG in the past without issue, we agreed that in this case, it made sense to avoid any conflicts that might arise because I was aware of incidents that had not been shared with other Association staff members. In my new role, I will meet regularly with CWG members to discuss different ways that the Association can support the Drupal Community; however, I will not be not be privy to any incident reports unless they are escalated to the Association by the CWG.

I will continue to find any excuse to ride my motorbike to Drupal events, though - I just can’t help that! (Current wish-list is to ride a Harley-Davidson to BADCamp - happy to hear about places to visit on the way!)

Idris at Buzludzha, on the way back to Drupalaton
Idris (my motorbike) at Buzludzha, on the way to Drupalaton

I’m sure that the things I get involved in will evolve over time and I hope that you will help me to ensure we’re always giving the best support to the Drupal Community.

I know I will make mistakes along the way. I hope you can help me recognise them, own them and learn from them.

Anyway, until we do meet face to face at a Drupal event, I’m always available either on Twitter, on IRC as rachel_norfolk, drupal.slack.com or via my Drupal Contact Form.

I’m here, and I’m listening. Let’s talk!

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