Last year we started a discussion about contributing to Drupal. In a blog article called Contributing to Open Source, what's your math? we layed out out how much and how we contribute. The goal was to bring the importance of contribution to attention, because Drupal heavily depends on it.
Dries and many companies participated in the discussion with own blogposts:
- Contributing to Open Source, what's your math? by Nick Veenhof from DropSolid
- Balancing Makers and Takers to scale and sustain Open Source by Dries Buytaert, the founder of Drupal
- PreviousNext's Open Source Contribution Policies and Initiatives for the Drupal Community by Owen Lansbury from PreviousNext
- and many more
As a result a lot of companies focused more on contribution, then on other activities in last year's European DrupalCon in Amsterdam.
We were one of those companies and sponsored the contribution area and invited everybody to contribute with us. For every person who participated we committed to contributing time work on the Drupal project. You can read about this here.
Almost our full team attended DrupalCon Amsterdam and besides attending sessions we spent a lot of time in the contribution room.
We have spent a significant amount of time on development and testing, two weeks ago the module is feature complete, covered by the Drupal Security Team, and we have started adding it to all our projects.
The benefit of the new version of reCAPTCHA over previous versions is that an interaction window (I am not a robot) only appears, if the observed interaction with the website containing the test, does not fullfill a configurable security score. Only if the score is too low, different tests (e.g. reCAPTCHA v2) are shown.
Since we have integrated the Drupal module reCAPTCHA v3 in our internal Drupal distribution 1xDx it will be installed in all future projects and we will continue to support it.