All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
We released Drupal Commerce 2.0-beta1 at DrupalCon Dublin one year ago. Over the next 9 months we tagged 6 more beta releases comprising over 500 commits by 70 different contributors working for at least 10 different companies. Now, just in time for DrupalCon Vienna, we have tagged the full 2.0 release, celebrating the achievement with Drupal contributors around the world on September 20th and 21st.
Celebrating Commerce 2.0 with Circle WF in Pancevo, Serbia.
Our release candidate phase was refreshingly uneventful (as you want it to be), giving us confidence to recommend developers begin using Drupal 8 and Commerce 2.x more broadly to develop their new eCommerce sites. Our team has contributed to a dozen projects directly, including architectural consulting and development. We also continue to see more case studies demonstrating how the new version is performing well at scale, making development teams more productive.
Additionally, not only has Commerce 2.x eliminated the need for half of the top 60 contributed modules in Commerce 1.x, many of the major contributed modules still required have seen their own releases or very active development to address important use cases. For example, we released a third beta of Commerce Shipping for Drupal 8 to support stores selling physical products with multiple shipments, flat rate, calculated rates and more. We continue to work on those feature modules ourselves (e.g. Commerce License / Recurring) and in partnership with other Drupal contributors (e.g. Commerce Stock) to make Commerce 2.x ready for more and more use cases.
Drupal Commerce deserves cake!
We're believe in Dries Buytaert's vision for Drupal as empowering ambitious digital experiences. For us that means continuing to improve Drupal Commerce to better support any company aspiring to grow their online sales. While our work on the project will never be "done", at this milestone, we couldn't help but pause to celebrate with a bit of cake.
If you'd like to join us in celebrating this achievement, we're hosting a release party with our whole team and our friends from Commerce Guys by Actualys on Tuesday, September 26th, at DrupalCon Vienna a short walk away from the venue. We've timed it for dinner between the opening reception at the venue and the party later in the evening, with drinks and food on us until the tab dries up. Stop by our booth to get your ticket / directions, and come find the dozens of contributors here at DrupalCon to share your Drupal Commerce story with them in turn.
This module removes standard meta tags such as "canonical, short link, delete form, editing, version history, revision, development, development, development, token-devel", as well as the specified attributes from the link, for example "data-drupal-link- system-path »
Computer Vision API Module extracts rich information from images to categorize and process visual data – and machine-assisted moderation of images to help curate your services.
Following API methods are available in the current release.
Face API Module integrates with Microsoft Face API, a cloud-based service that provides the most advanced face algorithms. Face API has two main functions: face detection with attributes and face recognition.
The Emotion API beta takes an image as an input, and returns the confidence across a set of emotions for each face in the image, as well as bounding box for the face, from the Face API.
Following API methods are available in the current release.
Although the most likely cause of the massive Equifax data breach was the firm’s own failure to patch a two-month-old bug, the inherent security of open source software has become a trending topic in tech news.
Mediacurrent’s resident expert, Open Source Security Lead Mark Shropshire, is well-informed to join the conversation. We asked him a few questions to get his take on recent events.
As GDC 2018 draws closer, organizers want to quickly remind you that they're still accepting UX Summit talk submissions -- but only until this Friday, September 29th at 11:59 pm Pacific! ...
These results and analysis were initially presented at the DrupalCon Vienna community summit on September 25, 2017.
Following numerous blog posts, official statements, community discussions, social media interactions, and Slack and IRC conversations over the last few months, there is a clear consensus that it is time for Drupal's community governance to evolve. We need to not only define what governance means to us as a community, but also clarify the roles and responsibilities of those within our community leadership and governance structures. We also need to draw clearer distinctions between the different forms of community, project, and technical governance, and make sure that everyone understands how they interact with and support each other.
Ultimately, this will need to be a collaborative process that involves all stakeholders, including Dries and the Drupal Association (especially where matters of legal and financial responsibility are concerned), but the first step is to create a framework so that the community can participate productively in the process. The question that remains to be answered is what that process will look like.Results of the Governance Summit Survey
The Drupal Association, with help from Whitney Hess, conducted a Community Governance Summit survey in an effort to gain insight into how the community would like to proceed. 568 people responded to the survey, with most questions receiving between 200-250 responses. The Community Working Group (CWG) was given access to the raw results, which it in turn shared with David Hernandez, Nikki Stevens, and Adam Bergstein, who assisted with the writing of this blog post. We all agreed to keep any personally identifiable information from respondents confidential.
While none of the authors of this blog post were responsible for developing the survey or are trained statisticians, we did our best to analyze the results, which reflected a wide range of opinions and feelings about how the Drupal project and community is governed. While we did not feel the survey results pointed to any clear and actionable next steps, they were consistent with the feedback from the community discussions that were held this spring, which was that the process, in whatever form it takes, needs to be driven by the community.
To that end, we have worked with the Drupal Association to publish the survey data and, most importantly, make this call to action for a truly community-driven process. We are also making a sanitized version of the raw data available for download in OpenDocument format for anyone else to review and perform their own analysis. All comments and other free responses have been removed.Selected Survey Highlights
62% agreed that a governance summit is needed. Only 8% said definitely “no.”
63% want the summit to be held online, so that members from all regions of our global community could participate.
59% believe the summit should be overseen or facilitated by a professional governance expert, with the majority of write-ins requesting a neutral third-party facilitator not affiliated with the Drupal project or community.
Nearly 80% wanted the Drupal Association to provide financial support for the summit, with 36% indicating they would contribute to a crowdfunding campaign to help fund the summit.
About ¾ said that clarification of leadership roles and separation of project versus community governance roles should be prioritized at the summit. All of the options listed received the support of more than half of those who provided a response to this question:
Clarification of leadership roles in the Drupal project (76%)
Separation of project vs. community governance roles (73%)
Update codes of conduct (63%)
Overall community management (63%)
More community-elected leadership positions throughout Drupal (60%)
Clarify and update Community Working Group processes and policies (56%)
Create core values statement (53%)
Percentages listed are of those who provided a response to that question, not of the total number of people who responded to the survey.What’s Next: Getting Involved
Now is the time for people to get involved and drive the next steps in the process. We feel that as an open-source project, the governance of our community should be designed and implemented by members of that community in the most transparent and fair manner possible.
To that end, we feel that the best path forward is to create a volunteer working group that is representative of our global community, and for that group to take the lead in the process of evolving Drupal community governance, rather than any existing group or individual. While the Drupal Association, Community Working Group, and others in the project’s current governance structure are committed to providing whatever support they can to ensure the success of this working group, we feel that the community itself needs to own the process as much as possible.
We, the authors of this blog post, are not the leaders of the process, but as members of the community with interest and experience in various aspects of community governance, we are willing and able to help provide a framework for the group to self-organize and begin work to help improve the governance of our community. We stand ready to participate and help as needed, understanding that while this work will not be quick or easy, it is important and necessary for the long term sustainability of our project and community.
The next step for this is for you to get involved. Here's how to get started:
Join the #governance channel on Drupal Slack.
Attend a governance meeting in the #governance channel. Once a schedule has been determined we will publicize that information and pin it to the Slack channel. Each of the authors of this post will host at least one meeting and the entire meeting transcript will be made available after the meeting.
The goals of these meetings are to connect people who are interested in governance with each other, provide a forum for people to share their thoughts, and empower the community to determine the next steps.
We are committed to this being a community-driven process and will be present to facilitate, but not to dictate.
If there is interest, we can also host meetings in other forums. (IRC, video chat, etc.)
Other ways to get involved:
Write a blog post and share your ideas.
We know that people don’t always feel safe sharing their comments and feedback and we don’t yet have a long-term solution for this. In the interim, feel free to directly contact any of the writers of this post, or any member of the Community Working Group to share your thoughts.
We are at a unique inflection point in the history of the Drupal community. We have the opportunity to (once again) provide a shining example to other open source communities demonstrating our forward thinking; not only in technical decisions, but also community ones. Please join us.
Authors (listed alphabetically by Drupal.org username)
- davidhernandez - David Hernandez
- drnikki - Nikki Stevens
- gdemet - George DeMet (CWG)
- nerdstein - Adam Bergstein
- ultimike - Michael Anello (CWG)
AbuseIPDB is a project dedicated to helping combat the spread of hackers, spammers, and abusive activity on the internet.
Our mission is to help make Web safer by providing a central blacklist for webmasters, system administrators, and other interested parties to report and find IP addresses that have been associated with malicious activity online.