This blog includes two statements. One from Dries Buytaert, as Drupal Project Lead, and another from Megan Sanicki, as the Executive Director of the Drupal Association and the Drupal Association Board.
We recognize that events and conversations earlier this year surfaced many concerns and needs within the community. One in particular is related to Larry Garfield’s role within Drupal. After several conversations with Larry, and careful consideration, we can now provide an update to this situation, our decisions, and Larry’s role moving forward.
We thank you for your patience while we spent many hours meeting with Larry and outside experts to resolve this matter. We recognize that actions were taken quickly before, which resulted in poor communication, and we wanted to avoid this happening again. We made sure to provide the proper time and attention these conversations needed before releasing this follow-up post.
We know our poor communication in the past led to frustration with us and pain for others. For that, we are sorry. We want to learn from this and improve. We listened to the community’s request to provide more streamlined, clear, and easy-to-follow communication. So, this post includes a statement from Dries Buytaert, as Project Lead, followed by a statement from Megan Sanicki, Executive Director of the Drupal Association.Statement from Dries Buytaert, as Drupal Project Lead
I know there are many people out there still uneasy about where things were left off with regards to Larry's status and uncertainty around why he was asked to leave. I would like to personally clear up these things.
The actions that led me to ask Larry to resign involve a woman who attended Drupal community events with Larry, and was "allowed" to contribute by him. I originally characterized these actions as 'beliefs,' which was inaccurate on my part. To be clear, potential legal and ethical questions were raised by various people, including the Drupal Association lawyers, that this person could be vulnerable and may have been subject to exploitation, which raised the risk of substantial damage to the project.
Based on the legal and ethical risks to the Drupal project caused by Larry’s actions, both the Drupal Association and I needed to take action.
In balancing these questions and this risk, with Larry’s stated desire for privacy, the most obvious solution at the time was to ask him to resign. This was difficult. Larry has been a longtime contributor and colleague, and given the gravity of this situation, I did not communicate as clearly as I should have. When Larry chose not to resign, I took no immediate action with Larry’s role in the community in order to allow more time to better understand the situation and for mediation to occur.
Instead of continuing a dialogue and working towards a solution, Larry chose to end our discussion and share parts of the information surrounding this situation publicly. I understand why Larry blogged, and I support Larry’s — and every community member’s — right to speak out constructively when they disagree with those of us in leadership roles. However Larry’s blogs led people to think that I, and the Drupal Association, doxxed, bullied, and discriminated against him, which we did not. His blog posts led many to think that people who are into kink are not welcome in our community, which is not true. Larry's posts created material disruption to the project and the Association based on incomplete and inaccurate information. Even though Larry saw the negative impact he further inflamed the situation with additional blog posts.
Our current governance model lays out numerous positions that can be held within the project and who has the ability to appoint or remove people from them. Larry’s various roles and who governs them are listed in the table below. Most of Larry’s leadership roles are associated with the Drupal Association, but as project lead, I am responsible for assigning technical leadership positions within the project. Part of my job is to appoint and replace maintainers, to make sure the team functions well; and to make sure the leadership team is effective setting the technical direction of the project as well as collaborating with other members of the Drupal community to achieve our technical vision.
After talking to Larry and consulting other key contributors, I remain steadfast in my decision that it is best for Drupal that Larry should not continue to hold a technical leadership role. I've therefore decided to remove Larry as a core subsystem maintainer and as the PHP-FIG representative for Drupal. Larry will maintain his individual contributor roles which means he can participate in the development of Drupal as a regular member of the community.Statement from Megan Sanicki, Executive Director of the Drupal Association and the Drupal Association Board
As the Executive Director of the Drupal Association a key part of my job is to protect the Drupal Association and the project from risk and harm. The Drupal Association is the steward of two critical drivers for Drupal’s longevity: Drupal.org and DrupalCon. And we are charged with caring for those spaces. Should the sustainability of the Drupal Association’s be impacted, we would no longer be able to maintain Drupal.org, which would have devastating implications for the project.
As Larry stated in his blog post, he was in a relationship with a woman he describes as “acutely autistic” and “mentally handicapped”. They attended Drupal events together where, in Larry’s own words, he “allowed” her to contribute to Drupal. The Drupal Association Board and I learned about this information from other sources as well as from Larry himself before Larry’s blog post was issued.
I was concerned not only about this person’s well-being, but I also had legal concerns about her ability to give informed consent or whether she was being exploited. The Drupal Association recognizes that Larry did not use the accurate medical terms to describe this person and we also recognize that most vulnerable people have the ability to consent. However, in this case, given the information we received about this person, we were concerned that it was possible that she could not consent. I sought input from board members and from professional experts, including legal counsel, who expressed concern that Larry’s action in his leadership roles created possible legal risk to the organization.
I learned about these issues just as the DrupalCon Baltimore sessions were about to be announced, and in order to give myself time to evaluate the risks, I ended Larry’s role as track chair and removed his session for only DrupalCon Baltimore. Making a decision for just one event provided me the time to better understand the situation and how to address the risks and concerns with appropriate counsel and authorities. The Drupal Association can not and should not investigate or adjudicate legal matters. We referred the situation to our legal counsel and followed their advice by removing Larry from leadership roles and we referred the matter to authorities.
Larry's subsequent blog posts harmed the community and had a material impact on the Drupal Association. including membership cancellations from those who believed we doxed, bullied, and discriminated against Larry as well as significant staff disruption. Due to the harm caused, the Drupal Association is removing Larry Garfield from leadership roles that we are responsible for, effective today.
These roles include being a DrupalCon track chair, DrupalCon speaker, member of the Drupal Association Advisory Board, and a member of the Licensing Working Group. Larry will maintain his individual contributor roles that the Drupal Association governs, which includes attending DrupalCon and contributing on Drupal.org using his Drupal.org user profile. It is important to note that Dries recused himself from the Drupal Association board decisions on this matter to avoid as many conflicts of interests as possible.
As long as Larry does not harm or disrupt the project, he will continue to be a member of the community as an individual contributor. However, we reserve the right to remove Larry's individual contributor roles if that is not the case. Also, we recognize that situations can change over time, so the Drupal Association will revisit these decisions in two years.
I recognize that my communication to Larry and with the community did not provide transparency into this situation and I apologize for the pain and confusion that caused. Our advisors told us not to share these details in order to protect all parties pending evaluation from authorities. Also, when Larry shared these details during the appeal process, he asked us to keep them confidential. It is my hope that this statement provides the clarity that many have been requesting.What We Have Learned
Dries, Megan, and the Drupal Association Board of Directors hope that the community can stay focused on healing and the needed discussions about ways we can improve our community.
It is clear that we were unprepared for a challenge of this complexity. We struggled to move forward in a careful, timely, and clear fashion. We need to provide the community with clarity and understanding whenever possible. Many ideas are surfacing from the recent community discussions and we are looking at them to identify other ways to be better prepared for future challenges.
Another key take-away from this incident is that everyone in our community needs to be able to understand the answers to these questions:
- What is expected of me by the community?
- What can I expect from the community?
- How is Drupal governed?
- How can I participate in governance?
The best way for the community to get these answers is by working together to refine our community governance model. We support this work and we are eager to help the community achieve its vision.
We believe this community is a role model for the world on how to be a great open source community. Even at its messiest, we believe this community is strong and has much to share with other projects and communities. We consistently come together to solve hard problems. Even now, we are coming together to redefine our community governance and we are confident Drupal will become stronger because of it.
If you want to be part of creating a stronger and healthier community for the future, we encourage you to get involved in the discussions taking place on Drupal.org. Plus, you can go here to learn about the findings from the recent Community Discussions that were mediated by Whitney Hess along with the next steps that the community wants to take in evolving governance. We hope you will join this effort.Governance of Roles
As mentioned in Dries' statement, these are Larry's roles and who governs each one.Larry Garfield’s Role Role Type Who governs this role Technical Leader (Core Maintainer & PHP FIG) Leadership Role Project Lead DrupalCon Presenter Leadership Role Drupal Association DrupalCon Program Team / Track Chair Leadership Role Drupal Association Licensing Working Group Leadership Role Drupal Association Drupal Association Advisory Board Leadership Role Drupal Association DrupalCon Attendee Individual Contributor - subject to DrupalCon Code of Conduct Drupal Association Drupal.org user profile Individual Contributor - subject to Terms of Service Drupal Association
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!
Himanshu Dixit | Blog: Week 6 : Creating Social Auth Implementers Using The Base Library Of TheLeagueoAuth
Drupal 8 chose a way of involving popular technologies, applying object-oriented methodologies, and adding the Symfony components to Drupal 8 had a huge impact on its development. Thus in this article we will focus on discussing the changes of the common core functionality which were caused by adding the Symfony components.
You will find the simplified code examples that would help you feel the difference between “clear” Symfony and Drupal 8 solutions. We will discuss in details three components which are the basis of Drupal core: DependencyInjection, EventDispatcher and Routing.
Maybe for some of you this will be the key point to a better understanding of the internal structure of Drupal 8 and its architecture.
If you visit Acquia's homepage today, you will be greeted by this banner:
We've published this banner in solidarity with the hundreds of companies who are voicing their support of net neutrality.
Net neutrality regulations ensure that web users are free to enjoy whatever sites they choose without interference from Internet Service Providers (ISPs). These protections establish an open web where people can explore and express their ideas. Under the current administration, the U.S. Federal Communications Commision favors less-strict regulation of net neutrality, which could drastically alter the way that people experience and access the web. Today, Acquia is joining the ranks of companies like Amazon, Atlassian, Netflix and Vimeo to advocate for strong net neutrality regulations.Why the FCC wants to soften net neutrality regulations
In 2015, the United States implemented strong protections favoring net neutrality after ISPs were classified as common carriers under Title II of the Communications Act of 1934. This classification catalogs broadband as an "essential communication service", which means that services are to be delivered equitably and costs kept reasonable. Title II was the same classification granted to telcos decades ago to ensure consumers had fair access to phone service. Today, the Title II classification of ISPs protects the open internet by making paid prioritization, blocking or throttling of traffic unlawful.
The issue of net neutrality is coming under scrutiny since to the appointment of Ajit Pai as the Chairman of the Federal Communications Commission. Pai favors less regulation and has suggested that the net neutrality laws of 2015 impede the ISP market. He argues that while people may support net neutrality, the market requires more competition to establish faster and cheaper access to the Internet. Pai believes that net neutrality regulations have the potential to curb investment in innovation and could heighten the digital divide. As FCC Chairman, Pai wants to reclassify broadband services under less-restrictive regulations and to eliminate definitive protections for the open internet.
In May 2017, the three members of the Federal Communications Commission voted 2-1 to advance a plan to remove Title II classification from broadband services. That vote launched a public comment period, which is open until mid August. After this period the commission will take a final vote.Why net neutrality protections are good
I strongly disagree with Pai's proposed reclassification of net neutrality. Without net neutrality, ISPs can determine how users access websites, applications and other digital content. Today, both the free flow of information, and exchange of ideas benefit from 'open highways'. Net neutrality regulations ensure equal access at the point of delivery, and promote what I believe to be the fairest competition for content and service providers.
If the FCC rolls back net neutrality protections, ISPs would be free to charge site owners for priority service. This goes directly against the idea of an open web, which guarantees a unfettered and decentralized platform to share and access information. There are many challenges in maintaining an open web, including "walled gardens" like Facebook and Google.
We call them "walled gardens" because they control the applications, content and media on their platform. While these closed web providers have accelerated access and adoption of the web, they also raise concerns around content control and privacy. Issues of net neutrality contribute a similar challenge.
When certain websites have degraded performance because they can't afford the premiums asked by ISPs, it affects how we explore and express ideas online. Not only does it drive up the cost of maintaining a website, but it undermines the internet as an open space where people can explore and express their ideas. It creates a class system that puts smaller sites or less funded organizations at a disadvantage. Dismantling net neutrality regulations raises the barrier for entry when sharing information on the web as ISPs would control what we see and do online. Congruent with the challenge of "walled gardens", when too few organizations control the media and flow of information, we must be concerned.
In the end, net neutrality affects how people, including you and me, experience the web. The internet's vast growth is largely a result of its openness. Contrary to Pai's reasoning, the open web has cultivated creativity, spawned new industries, and protects the free expression of ideas. At Acquia, we believe in supporting choice, competition and free speech on the internet. The "light touch" regulations now proposed by the FCC may threaten that very foundation.What you can do today
If you're also concerned about the future of net neutrality, you can share your comments with the FCC and the U.S. Congress (it will only take you a minute!). You can do so through Fight for the Future, who organized today's day of action. The 2015 ruling that classified broadband service under Title II came after the FCC received more than 4 million comments on the topic, so let your voice be heard.
This blog post summarises my sixth week of working with Google Summer of Code 2017 with Drupal.tameeshb Wed, 07/12/2017 - 09:48 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog
Ted Bowman and Mike Anello take some time (less than an hour!) to talk about Reservoir, a new Drupal 8 distribution focused on decoupling.Interview
- Introducing Reservoir, a Distribution for Decoupling Drupal.
- https://github.com/acquia/reservoir - main repository.
- https://github.com/acquia/reservoir-project - Composer project to install.
- Setting up BLT with Reservoir.
- Registration now open for the Fall, 2017 semester of Drupal Career Online.
- Summer 2017 Mastering Professional Drupal Developer Workflows with Pantheon begins mid-August
- MyDropWizard.com - Long-term-support services for Drupal 6, 7, and 8 sites.
- WebEnabled.com - devPanel.
- Decoupled Developer Days - New York City, August 19-20, 2017.
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.
Sadly, this is not about how I made my first million dollars, but rather a short story about how a project, I poured my heart soul and time into, got to 1 million downloads and helped thousands of people, all over the world, learn and build Drupal applications.
Most of the time, we ask ourselves what our purpose in life is, we feel the need to create something new while trying to chase after the infamous concept of ‘making an impact’ through innovation, often forgetting that we can achieve the same impact faster and better through collaboration and community driven initiatives.
My personal experience with the Drupal Console can be summarized in two words: Collaborator and Location.Collaborator
Often times being a good collaborator is as impactful as being an innovator. I didn’t come up with the Drupal Console, but I saw the potential to make an impact from very early on. So I joined the team to learn and contribute my two cents. Despite the high pressure to come up with a high quality technology solution, you always felt the satisfaction of contributing to something bigger than yourself. This solution was going to help a community, and you could feel it in every line of code, conversation, and fix.Location
With the focus and spotlights aimed at Silicon Valley and all the other major tech hubs, developers located outside feel alienated and look at location as a barrier to make technological breakthroughs. Sure, being located in these technology hubs can facilitate a lot of things, and the concentration of talent is a boost. However, personally the Drupal Console project eliminated that mental barrier. Creating and leading the project from Latin America proved that your location does not determine the quality of the job; we live in the same world, same internet and most importantly, opportunities to innovate and make an impact are open to everybody.
Today I look back and I’m happy with all the time and effort I poured into the Drupal Console. I take solace in the fact that so many people's lives are easier because they chose to use the Drupal Console.
Personally, I feel overwhelmed looking at the ocean of metatags presented on the node edit page when the metatag module is installed.
How much more overwhelmed would a regular ol' user feel?
I created a small modules to hide the extra form elements from the metatag module:
Drupal 8 natively allows to insert images within a body field, of course if the format text used allows this functionality. But can we do the same and easily insert documents, attachments, within a body text ? We have many solutions with Drupal 8 to associate documents with content.
Join in the fun during the Drupal Association membership campaign happening now through August 4. We're providing personalized certificates of membership to individual and organization members who join or renew during the campaign and we need your help spreading the word.
The campaign has two goals: help us deliver 500 certificates and raise $18,250 during July 10-August 4. By sharing and encouraging Drupal users and people in the community to join us, you'll help us meet these goals. If we are told by 5 or more members that you referred them to us during this campaign, we'll thank you on social media.
Grab words and graphics from this post and share away. If you are a member who would like your own certificate let us know and we'll send one your way. Post your selfie or hang your certificate on the wall. Thanks for sharing!Social
Share why you are a member.
Use these with https://www.drupal.org/association/campaign/certificate-2017
300 x 250px
440 x 220px (good for Twitter)
300 x 140px
Thank you for supporting the Drupal Association and for being part of our community.File attachments: mem_campaign_2017_q3_300x140.jpg mem_campaign_2017_q3_300x250.jpg mem_campaign_2017_q3_twitter_1.jpg
DrupalCon Baltimore was my 14th DrupalCon and it was a very interesting and eye-opening experience. The Drupal community is maturing just as Drupal as a content management system is maturing. I saw a lot of the same people that I’ve seen for years and I met a lot of new people, too. Though I haven’t seen the actual numbers, I felt like it was a bit smaller than last year. It could be that the layout of the Baltimore Convention Center is more compact than previous venues making it harder to gauge. Still, I had hoped to see continued growth of the community and Drupal as a whole so it was a bit disappointing.
In addition to walking around the tradeshow and attending some great sessions, I presented a two-hour training session on Drupal 8 SEO. The purpose of this session was to teach marketing people how to achieve SEO results with minimal need for developer help. Based on this, I came away with these lessons learned from DrupalCon 2017.1. The Drupal community is growing with marketers.
The marketing vibe was strong at DrupalCon last month. Since the first DrupalCon that I attended, I’ve seen it move from a group of developers wanting to build and support an exciting, new open source CMS, to a strong presence of marketing people who are looking for ways to maximize their website lead generation efforts. Websites are an important part of any marketing strategy and Drupal 8 supports marketing efforts better than any previous version.
And that feels great! While I’m a pro in a very particular niche in marketing, I have been pounding the “Drupal for marketers” drum for 12 years in this community. Often alone but more often with a few great people like Amy Cham, Kenna Poulos, and Danita Bowman. The Drupal agencies are finally getting the message, too.
While Drupalcon is still very much about developers, it’s maturing into a marketing powerhouse and it’s great to finally see it!2. There is a need for more SEO education in the Drupal community.
The growth of Drupal 8 as a viable platform for marketing has meant that people are more and more interested in SEO. In my Drupal 8 SEO session, I found a wide range of Drupal knowledge and skills. For example, some people were still installing modules manually. (Dirty secret: so do I sometimes.) One session reviewer said, “I am a marketer just starting Drupal and have a good grasp on SEO, but that said, I was too busy installing modules and could not keep up.” For others, the pace was just right: “This was by far my favorite session at DrupalCon. Ben had the talk set up perfectly and walked us through helpful steps that we needed to take for SEO.” In spite of the skills gap, 15 out of 15 attendees said that they learned something in this session.
People are looking for more Drupal 8 SEO education. Said one reviewer, “This topic area is huge, so even in a two-hour seminar, there was well more than could be covered.” Another wrote, “Grateful that this was a hands-on workshop, wish there were more of these.” The new hands-on session format was a big hit. I was thrilled that one attendee said, “Worth the price of the admission for the whole conference!”3. The Drupal community will survive and thrive.
If you are familiar with the undercurrents going on in the Drupal community, you may question its long-term health. Families fight. The Drupal community is a big family--so fighting is natural. But families also overcome differences and continue to live and work together. While there have been a lot of negative online communications, at DrupalCon, people were more interested in solving the problems and focusing on the Drupal product. Discussions of Drupal governance is a good thing. It enables conversations on how this big, open system can be better than ever. My time at DrupalCon has convinced me that this Drupal community will solve the existing problems and thrive as it works together to provide a cutting-edge product for the future.4. The Baltimore Raven comes from Edgar Allan Poe.
So it’s not related to Drupal, but I never made this connection until I visited Poe’s grave and memorial. The name of the NFL football franchise, the Baltimore Ravens, comes from one of Poe’s most famous poems, “The Raven,”. Well, duh, says all of the people from Baltimore. The rest of us are just getting it. In fact, with a little research, I found out that the team’s three mascots are named Edgar, Allan, and Poe.
Alright, Baltimore! I’m all for using literary allusion in pop culture. It makes me like the Ravens that much more. Still a Cowboys fan, tho.Drupal 8 SEO fills an important need in the community.
When Drupal 8 came out with so many great changes for SEO, I recognized a need for a new informational book. While I wrote Drupal 6 Search Engine Optimization several years ago, Drupal 8 really needed its own new topics. That’s where Drupal 8 SEO comes in. This book provides detailed instructions that marketers can use to set up SEO for their Drupal 8 website.
Session attendees walked out with a free electronic copy of Drupal 8 SEO. But you can get your own printed or electronic copy. Click here for more information.Drupal Marketing is Hot and so is Drupal 8 SEOdrupal 8, drupal 8 seo book, Planet Drupal