Feed aggregator

Microsoft Delays Windows 10 Spring Creators Update Because of 'Higher Percentage of BSODs'

Slashdot -

Microsoft has admitted that it had to postpone the release of Spring Creators Update, the upcoming major update to its Windows 10 desktop operating system due to technical issues. BleepingComputer notes: More precisely, Microsoft says it encountered a higher percentage of Blue Screen of Death (BSOD) errors on PCs, the company's Insiders Program managers said in a blog post yesterday. Microsoft says that instead of shipping the Springs Creators Update faulty as it was, and then delivering an update later to fix the issues, it decided to hold off on deploying the defective build altogether. The OS maker says it will create and test a new Windows 10 build that also includes the BSOD fixes, and ship that one instead of Windows 10 Insider Preview Build 17134, the build that was initially scheduled to be launched as the Spring Creators Update on April 10, last week.

Read more of this story at Slashdot.

Security updates for Tuesday

LWN Headlines -

Security updates have been issued by Debian (corosync, linux-tools, qemu, qemu-kvm, and r-cran-readxl), openSUSE (evince, memcached, nodejs4, ntp, pdns-recursor, python-gunicorn, python3-gunicorn, and python3), and Ubuntu (ruby1.9.1, ruby2.0, ruby2.3).

Web Wash: Differentiate Websites using Environment Indicator in Drupal 8

Drupal Planet -

As a web developer, you probably build your sites first in a local environment (aka localhost), then you commit all your changes to a staging server (i.e. an online server to which only you or the development team has access) and if everything works fine in the staging server, you’ll commit these changes to a production or live server (that’s your online site).

However, you don’t have a way to differentiate between your local, your staging and your production environments apart from the address box of your browser, so it’s very easy to mix up everything and that could lead to complications. The worst case scenario is making changes directly to your live site without testing and breaking it. In order to prevent this, you can use the Environment Indicator module.

The Environment Indicator module adds a visual hint to your site, that way you’ll always be aware of the environment you’re working on. We’re going to cover installation and usage of this module in this tutorial.

Let’s start!

Cybersecurity Tech Accord: More Than 30 Tech Firms Pledge Not to Assist Governments in Cyberattacks

Slashdot -

Over 30 major technology companies, led by Microsoft and Facebook, on Tuesday announced what they are calling the Cybersecurity Tech Accord, a set of principles that include a declaration that they will not help any government -- including that of the United States -- mount cyberattacks against "innocent civilians and enterprises from anywhere." The companies that are participating in the initiative are: ABB, Arm, Avast, Bitdefender, BT, CA Technologies, Cisco, Cloudflare, DataStax, Dell, DocuSign, Facebook, Fastly, FireEye, F-Secure, GitHub, Guardtime, HP Inc., HPE, Intuit, Juniper Networks, LinkedIn, Microsoft, Nielsen, Nokia, Oracle, RSA, SAP, Stripe, Symantec, Telefonica, Tenable, Trend Micro, and VMware. The announcement comes at the backdrop of a growing momentum in political and industry circles to create a sort of Digital Geneva Convention that commits the entire tech industry and governments to supporting a free and secure internet. The effort comes after attacks such as WannaCry and NotPetya hobbled businesses around the world last year, and just a day after the U.S. and U.K. issued an unprecedented joint alert citing the threat of cyberattacks from Russian state-sponsored actors. The Pentagon has said Russian "trolling" activity increased 2,000 percent after missile strikes in Syria. Interestingly, Amazon, Apple, Google, and Twitter are not participating in the program, though the Tech Accord says it "remains open to consideration of new private sector signatories, large or small and regardless of sector."

Read more of this story at Slashdot.

Apple Is Planning To Launch a News Subscription Service

Slashdot -

An anonymous reader shares a report: Apple plans to integrate recently acquired magazine app Texture into Apple News and debut its own premium subscription offering, according to people familiar with the matter. The move is part of a broader push by the iPhone maker to generate more revenue from online content and services. The Cupertino, California company agreed last month to buy Texture, which lets users subscribe to more than 200 magazines for $9.99 a month. Apple cut about 20 Texture staff soon after, according to one of the people. The world's largest technology company is integrating Texture technology and the remaining employees into its Apple News team, which is building the premium service. An upgraded Apple News app with the subscription offering is expected to launch within the next year, and a slice of the subscription revenue will go to magazine publishers that are part of the program, the people said.

Read more of this story at Slashdot.

Introducing Microsoft Azure Sphere

LWN Headlines -

Microsoft has issued a press release describing the security dangers involved with the Internet of things ("a weaponized stove, baby monitors that spy, the contents of your refrigerator being held for ransom") and introducing "Microsoft Azure Sphere" as a combination of hardware and software to address the problem. "Unlike the RTOSes common to MCUs today, our defense-in-depth IoT OS offers multiple layers of security. It combines security innovations pioneered in Windows, a security monitor, and a custom Linux kernel to create a highly-secured software environment and a trustworthy platform for new IoT experiences."

Tesla Temporarily Stops Model 3 Production Line

Slashdot -

An anonymous reader quotes a report from The Verge: Tesla is temporarily stopping production of its Model 3 electric car, amid a long waiting list and several missed targets. The company, however, says the shutdown is intended to resolve some of the problems that have contributed to the numerous delays in getting the cars to hundreds of thousands of reservation holders. The automaker said Monday it would halt production of the Model 3 sedan for 4-5 days at its Fremont, California assembly plant, BuzzFeed reported. Tesla, however, says this is part of a planned period of downtime that was similar to another shutdown in February, and it isn't intended to have an affect on the company's current production targets for the car. "Our Model 3 production plan includes periods of planned downtime in both Fremont and Gigafactory 1," a Tesla spokesperson told The Verge. "These periods are used to improve automation and systematically address bottlenecks in order to increase production rates. This is not unusual and is in fact common in production ramps like this."

Read more of this story at Slashdot.

Electric Citizen: Electric Citizen and DrupalCon Nashville

Drupal Planet -

Nashville Music City Center, a world-class venue

DrupalCon Nashville is in the history books and it was a doozy. The whole team was able to attend a stellar week of learning, sharing our hard-earned knowledge, and networking–interspersed with plenty of fun social events.

Seasoned Drupalers know that DrupalCon is a lot more than a tech conference. It is the community event of the year; a place to meet old friends and new, a celebration, and a barometer of the health of the Drupal platform itself–something we are collectively invested in. Attendees converged from far and wide to be part of it, to contribute, to engage, to learn and share, and to support our chosen technology.

As attendees, sponsors and presenters, Electric Citizen was fully in the mix this year. Read more in this blog post, or on our Twitter, LinkedIn and Facebook channels.

CodeSOD: Breaking Changes

The Daily WTF -

We talk a lot about the sort of wheels one shouldn’t reinvent. Loads of bad code stumbles down that path. Today, Mary sends us some code from their home-grown unit testing framework.

Mary doesn’t have much to say about whatever case of Not Invented Here Syndrome brought things to this point. It’s especially notable that this is Python, which comes, out of the box, with a perfectly serviceable unittest module built in. Apparently not serviceable enough for their team, however, as Burt, the Lead Developer, wrote his own.

His was Object Oriented. Each test case received a TestStepOutcome object as a parameter, and was expected to return that object. This meant you didn’t have to use those pesky, readable, and easily comprehensible assert… methods. Instead, you just did your test steps and called something like:

outcome.setPassed()

Or

outcome.setPassed(False)

Now, no one particularly liked the calling convention of setPassed(False), so after some complaints, Burt added a setFailed method. Developers started using it, and everyone’s tests passed. Everyone was happy.

At least, everyone was happy up until Mary wrote a test she expected to see fail. There was a production bug, and she could replicate it, step by step, at the Python REPL. So that she could “catch” the bug and “prove” it was dead, she wanted a unit test.

The unit test passed.

The bug was still there, and she continued to be able to replicate it manually.

She tried outcome.setFailed() and outcome.setFailed(True) and outcome.setFailed("OH FFS THIS SHOULD FAIL"), but the test passed. outcome.setPassed(False), however… worked just like it was supposed to.

Mary checked the implementation of the TestStepOutcome class, and found this:

class TestStepOutcome(object): def setPassed(self, flag=True): self.result = flag def setFailed(self, flag=True): self.result = flag

Yes, in Burt’s reluctance to have a setFailed message, he just copy/pasted the setPassed, thinking, “They basically do the same thing.” No one checked his work or reviewed the code. They all just started using setFailed, saw their tests pass, which is what they wanted to see, and moved on about their lives.

Fixing Burt’s bug was no small task- changing the setFailed behavior broke a few hundred unit tests, proving that every change breaks someone’s workflow.

hljs.initHighlightingOnLoad(); [Advertisement] ProGet can centralize your organization's software applications and components to provide uniform access to developers and servers. Check it out!

MPAA Silently Shut Down Its Legal Movies Search Engine

Slashdot -

Back in 2015, the Motion Picture Association of America (MPAA) released its own search engine to combat the argument that people pirate films because there are too few legal alternatives. According to TorrentFreak, the search engine, WhereToWatch.com, has since been quietly shut down by the movie industry group, stating that there are plenty of other search options available today. From the report: The MPAA pulled the plug on the service a few months ago. And where the mainstream media covered its launch in detail, the shutdown received zero mentions. So why did the site fold? According to MPAA Vice President of Corporate Communications, Chris Ortman, it was no longer needed as there are many similar search engines out there. "Given the many search options commercially available today, which can be found on the MPAA website, WheretoWatch.com was discontinued at the conclusion of 2017," Ortman informs TF. "There are more than 140 lawful online platforms in the United States for accessing film and television content, and more than 460 around the world," he adds. "That is all absolutely true today, though it was also true three years ago when the site was launched," adds Techdirt. "The simple fact of the matter is that the site did little to serve any real public customer base. Yes, legal alternatives to piracy exist. Everyone knows that, just as they know that there are far too many hoops and restrictions around which to jump that have nothing to do with price. The MPAA and its client organizations have long asserted strict control over their product to the contrary of public demand. That is, and has always been, the problem. On top of all that, the MPAA showed its no better at promoting its site than it was at promoting the legal alternatives to pirating movies."

Read more of this story at Slashdot.

OPTASY: Artificial Intelligence Consulting: What Are the Typical Activities?

Drupal Planet -

Artificial Intelligence Consulting: What Are the Typical Activities? adriana.cacoveanu Tue, 04/17/2018 - 09:44

So, you've (finally) overcome your skepticism regarding it: artificial intelligence does have the potential to propel your business right into the future! To drive productivity, enhance efficiency and flexibility and, overall, to transform your brand from the ground up. But how do you know what AI technology to go with? What are the AI use cases perfectly suited for your own business? And this is where artificial intelligence consulting comes in!

An AI consultant/AI consulting company's role is precisely that of answering all your questions and pointing out to you the right AI approach, the AI-powered solution(s) suitable for your own business:
 

Sooper Drupal Themes: How To Use Blocks And Custom Blocks In Drupal 8 | 8 Days To Drupal 8 | Day 2

Drupal Planet -

We're counting down the days to the official SooperThemes Drupal 8 Release! Count with us as we're writing a Drupal 8 related blog post every day for the next 8 days.

Drupal 8 block management and drag and drop block video tutorial

view on sooperthemes.com if you can't see the video

Block Administration And Placement In Drupal 8

Same as in Drupal 7, Drupal 8 blocks are placed in regions from the blocks administration page, which is located at Structure > Block layout. A notable improvement in Drupal 8 is that you can now place the same block in different regions. For example: previously it was impossible to put a block in the sidebar on the blog section of your website and at the top of the masthead in another section of your website.

When placing a block in Drupal 8 you're offered block visibility settings that are familiar to people who have experience with Drupal 7. You limit visibility based on content type, paths, and user roles. Third party modules can extend this in Drupal 8, in the video below you see that the Webform module lets you place blocks whenever specific webfoms are showing. 

The Drupal 8 Blocks Administration Page

view on sooperthemes.com if you can't see the video

Custom Content Blocks In Drupal 8

To those familiar with Drupal 7: Drupal 8 lets you make new blocks and enter custom text or HTML. Except it's better. In the old system custom blocks were neutered content, without support for revisions, permissions, or custom block types.

In Drupal 8 blocks are proper first class citizens and support revisioning and custom block types. Basically Drupal 8 does with blocks what we did with the BEAN module in our Drupal 7 theme installation profiles. That's one less contrib module you'll need in Drupal 8! In our Drupal themes' demo installation profiles we offer "Basic Blocks" and "Drag and drop blocks" The latter option will let you design blocks with our front-end visual page builder.

Placing Blocks With Our Visual Page Builder Glazed Builder  Glazed Builder lets you place any Drupal block with our visual drag and drop module. The only blocks that will be missing from the blocks tab are views blocks. This is because we treat all views displays equally and put them under the Views tab. Here you will find every single views display, including Master displays. Moreover we allow you to override some useful views parameters, like pager settings, pager offset, exposed filters, and contextual filters. This is very powerful and you can use Glazed Builder to make news portal layouts, magazine layouts, and even personalized user dashboards. Creating A Footer Block In Drupal 8 I made a little video showing the complete process of creating a footer block in Drupal 8, you probably already found it at the top of this page. We start by adding a simple Copyright notice block using Drupal's native CKEditor. Then we show how you can build a 3 column footer easily with our frontend visual page builder. With Glazed Builder you can add any Drupal blocks and views in the footer, as well as all the standard drag and drop elements, and the extendable suite of HTML snippets in the Glazed Builder sidebar. If you add a drag and drop block to any region in your theme, you can view, edit, and save the block on any page where the blocks shows. It's very convenient and easy to get used to. Glazed Builder handles multiple blocks per page, automatically saves new revisions, and is also language aware.

Deeson: Warden release 1.3.0

Drupal Planet -

At the end of March we released the next version of Warden, our open source solution that allows in-house development teams and agencies to keep track of the status of multiple Drupal sites hosted on different platforms. Release 1.3.0 contained the following changes:

  • Added Slack notification for sites on the dashboard
  • Logging request information from Drupal sites
  • Sorting the list of modules
Slack notifications.

This new feature provides a notification command which enables Warden to send details of the sites that need updating (those that are shown in the dashboard) to Slack.

In order to use this, a webhook needs to be set up within your Slack account to send notifications to a specific channel of your choice. Once this has been set up, the webhook URL can be added to the parameters settings within the Warden application (which will be asked for when running composer install after updating the application or can manually be added to the app/config/parameters.yml file to add it post install).

The notification can then be triggered using cron to generate the details and send them to the relevant Slack channel using the following command:

php app/console deeson:warden:dashboard-send-notification --type=slack Logging requests from Drupal sites.

This new feature shows a list of log requests that Warden makes to your Drupal sites. This enables users to be able to see when requests started failing, and will report on a relevant reason (depending upon what is returned from the request).

When viewing a site, there is an additional item in the ‘Actions’ list as well as a link next to the last successful request date time.

This provides a list in reverse chronological order of the requests that have been made to the site, highlighting which ones have failed. This helps users to be able to see when a sites started failing and potentially why.

Sorting the list of modules.

This update adds some additional functionality to the module listing page. By default, this page is sorted by the most used modules first, which is great for understanding how the modules are used, but not so great if you are trying to find a particular module.

With this update, this list can be sorted by module name as well as the number of sites that are using a module. This can be done by clicking on the table header to change the type of sorting that the table is displayed in.

Are you using Warden successfully? What else does the tool need? Come and let us know on our GitHub issues listing page.

Valuebound: Drupal highly critical vulnerability SA-CORE-2018–002 - We've got you covered

Drupal Planet -

This blog post attempts to focus on the highly critical vulnerability that was announced by Drupal on 28th March tagged as SA-CORE-2018–002, Drupalgeddon 2.

Recently, Drupal core announced a security advisory rated as highly vulnerable - dubbed DrupalGeddon 2 (SA-CORE-2018-002 / CVE-2018-7600) - that has the potential to affect the vast majority of Drupal 6, 7 and 8 websites.

According to BuiltWith, around 9% of websites are running on Drupal and hence had a high probability of being affected by the vulnerability as the score is 24/25.

Valuebound: Drupal highly critical vulnerability SA-CORE-2018–002 - We've got your back

Drupal Planet -

This blog post attempts to focus on the highly critical vulnerability that was announced by Drupal on 28th March tagged as SA-CORE-2018–002, Drupalgeddon 2.

Recently, Drupal core announced a security advisory rated as highly vulnerable - dubbed DrupalGeddon 2 (SA-CORE-2018-002 / CVE-2018-7600) - that has the potential to affect the vast majority of Drupal 6, 7 and 8 websites.

According to BuiltWith, around 9% of websites are running on Drupal and hence had a high probability of being affected by the vulnerability as the score is 24/25.

19-Year-Old Archivist Charged For Downloading Freedom-of-Information Releases

Slashdot -

Ichijo writes: According to CBC News, a Canadian teen "has been charged with 'unauthorized use of a computer,' which carries a possible 10-year prison sentence, for downloading approximately 7,000 freedom-of-information releases. The provincial government says about 250 of those contain Nova Scotians' sensitive personal information." "When he was around eight [...] his Grade 3 class adopted an animal at a shelter, receiving an electronic adoption certificate," reports CBC. "That lead to a discovery on the classroom computer. 'The website had a number at the end, and I was able to change the last digit of the number to a different number and was able to see a certificate for someone else's animal that they adopted,' he said. 'I thought that was interesting.' The teenager's current troubles arose because he used the same trick on Nova Scotia's freedom-of-information portal, downloading about 7,000 freedom-of-information requests." The teen is estimated to have around 30 terabytes of online data on his hard drives, which equates to "millions" of webpages. "He usually copies online forums such as 4chan and Reddit, where posts are either quickly erased or can become difficult to locate."

Read more of this story at Slashdot.

Supreme Court Set To Hear Landmark Online Sales Tax Case

Slashdot -

An anonymous reader quotes a report from Gizmodo: On Tuesday, the U.S. Supreme Court will hear arguments in a case that could at least somewhat clarify Donald Trump's complaints about Amazon "not paying internet taxes." It will also decide if those cheap deals on NewEgg are going to be less of a steal. The case concerns the state of South Dakota versus online retailers Wayfront, NewEgg, and Overstock.com in a battle over whether or not state sales tax should apply to all online transactions in the U.S., regardless of where the customer or retailer is located. It promises to have an impact on the internet's competition with brick-and-mortar retailers, as well as continue to address the ongoing legal questions surrounding real-world borders in the borderless world of online.

Read more of this story at Slashdot.

Facebook Must Face Class-Action Lawsuit Over Facial Recognition, Says Judge

Slashdot -

U.S. District Judge James Donato ruled on Monday that Facebook must face a class-action lawsuit alleging that the social network unlawfully used a facial recognition process on photos without user permission. Donato ruled that a class-action was the most efficient way to resolve the dispute over facial templates. KFGO reports: Facebook said it was reviewing the ruling. "We continue to believe the case has no merit and will defend ourselves vigorously," the company said in a statement. Lawyers for the plaintiffs could not immediately be reached for comment. Facebook users sued in 2015, alleging violations of an Illinois state law about the privacy of biometric information. The class will consist of Facebook users in Illinois for whom Facebook created and stored facial recognition algorithms after June 7, 2011, Donato ruled. That is the date when Facebook launched "Tag Suggestions," a feature that suggests people to tag after a Facebook user uploads a photo. In the U.S. court system, certification of a class is typically a major hurdle that plaintiffs in proposed class actions need to overcome before reaching a possible settlement or trial.

Read more of this story at Slashdot.

Dries Buytaert: State of Drupal presentation (April 2018)

Drupal Planet -

© Yes Moon

Last week, I shared my State of Drupal presentation at Drupalcon Nashville. In addition to sharing my slides, I wanted to provide more information on how you can participate in the various initiatives presented in my keynote, such as growing Drupal adoption or evolving our community values and principles.

Drupal 8 update

During the first portion of my presentation, I provided an overview of Drupal 8 updates. Last month, the Drupal community celebrated an important milestone with the successful release of Drupal 8.5, which ships with improved features for content creators, site builders, and developers.

Drupal 8 continues to gain momentum, as the number of Drupal 8 sites has grown 51 percent year-over-year:

This graph depicts the number of Drupal 8 sites built since April 2015. Last year there were 159,000 sites and this year there are 241,000 sites, representing a 51% increase year-over-year.

Drupal 8's module ecosystem is also maturing quickly, as 81 percent more Drupal 8 modules have become stable in the past year:

This graph depicts the number of modules now stable since January 2016. This time last year there were 1,028 stable projects and this year there are 1,860 stable projects, representing an 81% increase year-over-year.

As you can see from the Drupal 8 roadmap, improving the ease of use for content creators remains our top priority:

This roadmap depicts Drupal 8.5, 8.6, and 8.7+, along with a column for "wishlist" items that are not yet formally slotted. The contents of this roadmap can be found at https://www.drupal.org/core/roadmap.
Four ways to grow Drupal adoption

Drupal 8 was released at the end of 2015, which means our community has had over two years of real-world experience with Drupal 8. It was time to take a step back and assess additional growth initiatives based on what we have learned so far.

In an effort to better understand the biggest hurdles facing Drupal adoption, we interviewed over 150 individuals around the world that hold different roles within the community. We talked to Drupal front-end and back-end developers, contributors, trainers, agency owners, vendors that sell Drupal to customers, end users, and more. Based on their feedback, we established four goals to help accelerate Drupal adoption.

Goal 1: Improve the technical evaluation process

Matthew Grasmick recently completed an exercise in which he assessed the technical evaluator experience of four different PHP frameworks, and discovered that Drupal required the most steps to install. Having a good technical evaluator experience is critical, as it has a direct impact on adoption rates.

To improve the Drupal evaluation process, we've proposed the following initiatives:

Initiative Issue link Stakeholders Initiative coordinator Status Better discovery experience on Drupal.org Drupal.org roadmap Drupal Association hestenet Under active development Better "getting started" documentation #2956879 Documentation Working Group grasmash In planning More modern administration experience #2957457 Core contributors ckrina and yoroy Under active development

To become involved with one of these initiatives, click on its "Issue link" in the table above. This will take you to Drupal.org, where you can contribute by sharing your ideas or lending your expertise to move an initiative forward.

Goal 2: Improve the content creator experience

Throughout the interview process, it became clear that ease of use is a feature now expected of all technology. For Drupal, this means improving the content creator experience through a modern administration user interface, drag-and-drop media management and page building, and improved site preview functionality.

The good news is that all of these features are already under development through the Media, Workflow, Layout and JavaScript Modernization initiatives.

Most of these initiative teams meet weekly on Drupal Slack (see the meetings calendar), which gives community members an opportunity to meet team members, receive information on current goals and priorities, and volunteer to contribute code, testing, design, communications, and more.

Goal 3: Improve the site builder experience

Our research also showed that to improve the site builder experience, we should focus on improving the three following areas:

  • The configuration management capabilities in core need to support more common use cases out-of-the-box.
  • Composer and Drupal core should be better integrated to empower site builders to manage dependencies and keep Drupal sites up-to-date.
  • We should provide a longer grace period between required core updates so development teams have more time to prepare, test, and upgrade their Drupal sites after each new minor Drupal release.

We plan to make all of these aspects easier for site builders through the following initiatives:

Initiative Issue link Stakeholders Initiative coordinator Status Composer & Core #2958021 Core contributors + Drupal Association Coordinator needed! Proposed Config Management 2.0 #2957423 Core contributors Coordinator needed! Proposed Security LTS 2909665 Core committers + Drupal Security Team + Drupal Association Core committers and Security team Proposed, under discussion Goal 4: Promote Drupal to non-technical decision makers

The fourth initiative is unique as it will help our community to better communicate the value of Drupal to the non-technical decision makers. Today, marketing executives and content creators often influence the decision behind what CMS an organization will use. However, many of these individuals are not familiar with Drupal or are discouraged by the misconception that Drupal is primarily for developers.

With these challenges in mind, the Drupal Association has launched the Promote Drupal Initiative. This initiative will include building stronger marketing and branding, demos, events, and public relations resources that digital agencies and local associations can use to promote Drupal. The Drupal Association has set a goal of fundraising $100,000 to support this initiative, including the hiring of a marketing coordinator.

Megan Sanicki and her team have already raised $54,000 from over 30 agencies and 5 individual sponsors in only 4 days. Clearly this initiative resonates with Drupal agencies. Please consider how you or your organization can contribute.

Fostering community with values and principles

This year at DrupalCon Nashville, over 3,000 people traveled to the Music City to collaborate, learn, and connect with one another. It's at events like DrupalCon where the impact of our community becomes tangible for many. It also serves as an important reminder that while Drupal has grown a great deal since the early days, the work needed to scale our community is never done.

Prompted by feedback from our community, I have spent the past five months trying to better establish the Drupal community's principles and values. I have shared an "alpha" version of Drupal's values and principles at https://www.drupal.org/about/values-and-principles. As a next step, I will be drafting a charter for a new working group that will be responsible for maintaining and improving our values and principles. In the meantime, I invite every community member to provide feedback in the issue queue of the Drupal governance project.

An overview of Drupal's values with supporting principles.

I believe that taking time to highlight community members that exemplify each principle can make the proposed framework more accessible. That is why it was very meaningful for me to spotlight three Drupal community members that demonstrate these principles.

Principle 1: Optimize for Impact - Rebecca Pilcher

Rebecca shares a remarkable story about Drupal's impact on her Type 1 diabetes diagnosis:

Principle 5: Everyone has something to contribute - Mike Lamb

Mike explains why Pfizer contributes millions to Drupal:

Principle 6: Choose to Lead - Mark Conroy

Mark tells the story of his own Drupal journey, and how his experience inspired him to help other community members:

Watch the keynote or download my slides

In addition to the community spotlights, you can also watch a recording of my keynote (starting at 19:25), or you can download a copy of my slides (164 MB).

Pages

Subscribe to Heydon Consulting aggregator