Newsfeeds

AddToAny DX8 integration

New Drupal Modules - 11 April 2018 - 3:41am

This module makes the social sharing block functionality from the
AddToAny module available as a custom element within Cohesion DX8.

Enable the module and the "AddToAny" element will become available in
the DX8 element sidebar.

Select a combination of universal and specific social sites, placement
and icon size.

The title and URL of the page are detected automatically.

This module requires a DX8 subscription.

Categories: Drupal

Matomo Api

New Drupal Modules - 11 April 2018 - 2:30am
Categories: Drupal

Specbee: How to configure views REST export in Drupal 8

Planet Drupal - 10 April 2018 - 11:34pm

As all know, Drupal 8 is API driven first and keeps on adding in new API's which can be altered, extended for different decoupled Applications. When we talk about of decoupled Drupal, developers are allowed to use any technology frontend to bring in better User experiences. The actual UI experience is met when we present contents which fulfill the needs and requirements of the user.

Categories: Drupal

İletimerkezi SMS API

New Drupal Modules - 10 April 2018 - 11:12pm

Enables modules to use Iletimerkezi API, and integrates with SMS Framework.

Installation

You can use composer require 'drupal/sms_iletimerkezi:^1.0' or follow the path.

1. Download [SMS Framework][sms-framework] and its dependencies.
2. Install module as per [standard procedure][drupal-module-install].
3. This module has composer dependencies, see [instructions][composer-dependencies]
for information on how to resolve these dependencies.

Create a Iletimerkezi API Keys

Categories: Drupal

Agiledrop.com Blog: AGILEDROP: What got us here, won't get us there.

Planet Drupal - 10 April 2018 - 9:46pm
Day one at DrupalCon Nashville started with the traditional keynote by Drupal's founder Dries Buytaert. Dries talked about what is new and where are we heading. One of the main announcements was the Promote Drupal Initiative. The goal of this initiative is to start a promotional campaign that will enable to make Drupal known and loved by new decision makers. The same evening I happen to see a tweet from a formal active Drupal contributor that was questioning the director of Drupal. The tweet that got deleted very quickly said that we are compromising quality with marketing bulls**t. My first… READ MORE
Categories: Drupal

Rate Limits

New Drupal Modules - 10 April 2018 - 5:42pm

Rate Limits allows you to create configurations to limit access in a given window. It is currently built on top of core's flood service to provide protection against DoS attacks. By limiting the rate that a particular user or a particular IP can access your Drupal site you can prevent these types of attacks.

Usage

In order to configure the rate limits you will need to tag the routes where you want them to apply. You can use the Tagged Routes module to manually tag routes, or you can tag them programmatically in the route configuration like this:

Categories: Drupal

SHUX ’18 tickets are now on sale

Tabletop Gaming News - 10 April 2018 - 3:00pm
The convention season is packed with great shows. Just about every weekend, you can find someone getting together somewhere. Making sure to plan early and pick up tickets for shows is important. That’s why you should go and grab yours for SHUX 2018, put on by Shut Up & Sit Down. From the announcement: Oh […]
Categories: Game Theory & Design

Lazy-load

New Drupal Modules - 10 April 2018 - 2:52pm

This is a simple Drupal module to lazy-load all inline images and/or iframes defined by content authors in entity content, usually the text-format-enabled version of textarea fields. i.e. Node and Block body content.

The module currently depends on the bLazy image script.

There is another contributed module utilizing its namesake, Blazy. Make sure to check it out, especially if you need more advanced features and support for many features out of the box.

Categories: Drupal

Drinking Buddies Party Card Game Coming To Kickstarter

Tabletop Gaming News - 10 April 2018 - 2:00pm
Despite being a teetotaler, myself, I don’t mind if other people imbibe safely and responsibly. And as a gamer, I certainly know that gamers tend to like to get their booze on. Well, a new party drinking card game will be making its way to Kickstarter soon. It’s called Drinking Buddies. From the website: Drinking […]
Categories: Game Theory & Design

Git LFS File Storage

New Drupal Modules - 10 April 2018 - 1:18pm
Categories: Drupal

Drupal Association blog: We asked, you answered. DrupalCon North America Location Survey Results

Planet Drupal - 10 April 2018 - 1:17pm

Over the past few years, we’ve been listening to the community ask for explanation as to why we haven’t had any DrupalCon North America locations outside of the United States - after all it’s called DrupalCon North America, not DrupalCon U.S.A. This isn’t something we’ve taken lightly or ignored. DrupalCon North America is a major funding source for the Drupal Association, and in that regard, a major funding source of Drupal.org and the engineering work that keeps the code accessible and available for everyone.

We’ve looked at many North American cities over the years - a lot in the United States, but some outside the U.S. also. For our 2019 and 2020 location search we directly asked several cities in Canada to bid on this event, so that we could do financial and accomodation comparisons against U.S. options. I will give you the spoiler up front: 2019 and 2020 will not be in Canada or Mexico, they will be in the United States. The cities that bid were competitive, but in the end did not prevail due to things like dates overlapping with Passover and simply not being the most effective bid in comparison to the winners.

But with these cities in mind, and the voices of the community in our ears, we decided to go deeper and explore what a Canadian or Mexican DrupalCon would look like, based on survey feedback from the community and hard numbers from our history and bids. Here is that deeper look.

First, let me say that Drupal Association staff does not think solely about finances in making these decisions. We spend a lot of time getting to know the city, the vibe, the culture and the openness to a community that celebrates diversity and has a plethora of unique needs. It’s important to you, and it’s important to us.

Let’s also acknowledge that DrupalCon North America greatly underwrites the Drupal Association work and Drupal.org infrastructure to help keep the project going. So while money is not the only thing - it is very important.

So, let’s talk about finances. There are a lot of things that go into making a DrupalCon financially viable, and we did a pretty thorough job of outlining them all in our blog series last fall dedicated to the finances of DrupalCon Europe. I suggest you take a look at those, specifically the one on Solving The Financial Problem to get a good understanding on what it takes to make DrupalCon happen. A truncated look shows that there are three (3) main aspects and goals to DrupalCon finances:

  • Expenses: everything we have to spend to make it happen
    • Goal: produce show on a tight budget
  • Revenue, attendee tickets: how many people will show up
    • Goal: people show up
  • Revenue, sponsorship commitment: how much sponsors will spend to support the event
    • Goal: sponsorships have value and continue to support us
Expenses

In a look at expenses there are a vast array of things that we spend money on - from facilities and catering to program guides and paying the person who watches coat check while you’re sprinting on Friday. And overall, the proposals we’ve received from cities within the United States and outside of the United States have been fairly competitive for expenses directly related to the venue and infrastructure. That’s awesome!

There are some other indirect expenses we consider too like cost of hotel rooms, which can greatly affect whether people can afford to stay in the city, and generally Canadian cities - for example - tend to be a bit more expensive than some of our U.S. options. Other considerations include: whether the city is a airport hub for enough domestic and international flights to get people there easily; ease of setting up foreign bank accounts or legal business statuses in specific countries in order for us to operate there (including increased staff time to do this); cost of import/export for our production gear (this applies to sponsors as well). There are workarounds for some of these, and that's what we explore during an RFP process. Based on estimates, a DrupalCon outside the United States tends to pen out to be at least 10% more expensive than one within the United States - that’s around $100,000 - $150,000.

In general, the expenses section is a place where we can explore more work-arounds and potentially find a way to make a non-U.S. DrupalCon happen. However, because of DrupalCon team capacity during 2017 (the timeframe while we were contracting 2019 - 2020 cities) this is not something we could do for the immediately upcoming DrupalCons.

Revenue

As I mentioned above, revenue from DrupalCon North America is a driving force for the Drupal Association and Drupal.org. Ensuring attendee ticket sales and sponsorship revenue remain consistent from year to year (or grow) is extremely important to helping ensure our staff are funded and Drupal.org is kept running. In order to make certain that funding holds consistent and we’re able to keep Drupal.org healthy we need to keep DrupalCon North America profit margins around roughly 30-35% per event.

Here is where things start to fall apart for non-U.S. cities in the immediate future.

To better evaluate our current and potential revenue, we created 2 surveys and put them out to the public/community to participate.

Survey targets:

  • Past and potential attendees
  • Past and existing sponsors
Revenue, Attendee Ticket Sales

DrupalCon attendees are the main audience where we hear the cry for a DrupalCon outside of the United States. Individual ticket sales make up 62% of our event revenue.

Our survey to attendees had 1258 respondents. 92% of those people have attended DrupalCon North America in the past, and 99% have attended a DrupalCon somewhere in the world. So this sample represents people who are likely to attend in the future.

Since we’re talking about Revenue, it’s important to know who is paying for these people to attend. 79% of these attendees are funded by their employers. That’s a significant number and important to think about as we move into a business case for companies to attend DrupalCon.

Next, we followed up on that. “If your employer funds your trip to DrupalCon, are they willing to pay for you to travel outside the U.S.?” Of our 79% - 38% answered “No” (this number is adjusted from the chart percentages below because the question was “IF your employer pays”, and 120 people answered that they pay for themselves). That means, of our original sample size, now only 71% of attendees are still eligible to attend (22% self-funded + (62% of 79%) = roughly 71%).

Based on the responses, our projected revenue would decrease by roughly 29%.

Revenue, Sponsorships

Sponsors provide 38% of DrupalCon revenue, their sponsorships currently underwrite the cost of early bird tickets (that’s a whole other problem), and the event would simply not happen without them. They provide the foundation for the event in financing, they are the exhibit hall, and a large portion of our attendees are sponsor company employees. If sponsors don't come, we lose money and don't achieve a key purpose of our event: connecting new business decision makers with agency owners to grow adoption.

In our survey to them, we presented a hypothetical scenario in which DrupalCon takes place in Canada.

Our leading question for sponsors was “Do you do business in Canada?” and 70% of 44 responses said “No”. This doesn’t eliminate possibility, but it is the trend for the questions that followed.

We also asked “Would you sponsor a DrupalCon in Canada at same levels as you have in the past?” and only 39% of respondents answered “Yes”.

Of these sponsors, many wrote anecdotally that they simply could not support a business case for having an event in Canada.

To Sum it Up

While we’ve had advanced talks with Canadian cities, and two were finalists for 2019 and 2020 making it past initial RFP rounds, as of now we haven’t found solutions to enough of these issues to fit a DrupalCon North America within our required profit margin.

The numbers presented by the surveys would put profit margin for a DrupalCon North America outside the U.S. at an estimated 6% profit margin and would risk actually losing money for the Drupal Association. A situation and risk we cannot allow the Association to bear.

This is disappointing for many of us - and we know it is for many of you as well. We would love to see DrupalCon North America move beyond the U.S. borders, however it will not happen until at least 2021.

In between now and our next location RFP, we will continue to look at models that might make this possible. As we explore these challenges and talk more with sponsors and cities, we will share with the community any progress or new challenges as they become relevant. We appreciate your passion on this topic and understand the concerns with hosting DrupalCon in the United States for another two (2) years, especially based in our current climate of travel restraints in to the U.S. We wish it were not difficult for our community to come together.

We appreciate everyone who took the time to participate in our surveys and were honest about their desires, motivations and realities of their travel to and participation in DrupalCon. We're excited seeing many of you in Nashville this week, and hope many of you will join us in 2019 for DrupalCon Gedfyuikemndjfkioiujhtrj - sorry, something has happened to my keyboard. ¯\_(ツ)_/¯

_________________________

We invite you to share thoughts in the comments section below on how you think DrupalCon 2019 and 2020 can help provide more opportunity for community members outside the United States to participate in the event - either through direct attendance or through virtual participation of some kind. What are your ideas?

File attachments:  Business in Canada.png Employer Fund International Travel.png WhoFunds.png Would you Sponsor.png
Categories: Drupal

Making computer animation more agile, acrobatic -- and realistic

Virtual Reality - Science Daily - 10 April 2018 - 1:11pm
Animation in film and video games is hard to make realistic: each action typically requires creating a separate controller, while deep reinforcement learning has yet to generate realistic human or animal motion. Computer scientists have now developed an algorithm that uses reinforcement learning to generate realistic simulations that can even recover realistically, after tripping, for example. The same algorithm works for 25 acrobatic and dance tricks, with one month of learning per skill.
Categories: Virtual Reality

Mobomo: Mobomo Speaks at the Government Summit

Planet Drupal - 10 April 2018 - 1:08pm

The post Mobomo Speaks at the Government Summit appeared first on .

Categories: Drupal

Gioconomicon Interviews Makers of Battlestar Galactica – Starship Battles

Tabletop Gaming News - 10 April 2018 - 1:00pm
There are several great sci-fi series out there. One of those that’s been around the longest is Battlestar Galactica. There’s been a few games based on the series over the year, but a new one’s coming in the form of Battlestar Galactica Starship Battles. Gioconomicon sat down with the games’ designers for a quick chat […]
Categories: Game Theory & Design

Late Backing Open for Into the Black: Boarding Party

Tabletop Gaming News - 10 April 2018 - 12:00pm
With all the Kickstarter campaigns going on, its easy for one to slip by you. Maybe you just missed it. Maybe you were short that month. Whatever the reason, the end of the Kickstarter doesn’t always mean you’ve missed out on all the goodies. Take, for example, I Will Never Grow Up’s Into the Black: […]
Categories: Game Theory & Design

Podcast Radio

Tabletop Gaming News - 10 April 2018 - 11:00am
Monday’s gone. That brings us to Tuesday. Mine’s starting off pretty good. I got new dice and a new shirt delivered in the mail. And, I mean, who doesn’t love dice? Nobody who I call my friend, anyway. Also, my Monday seemed to go by quickly. Here’s to hoping the rest of the week speeds […]
Categories: Game Theory & Design

Yndaros: The Darkest Star Adventure For Symbaroum Up On Kickstarter

Tabletop Gaming News - 10 April 2018 - 10:00am
Just looking at movie series, you know people are always excited about the next installment of a beloved property. In the case of tabletop RPGs, that’s no different. In this case, it’s the next part of the Throne of Thorns campaign for Symbaroum. It’s called Yndaros: The Darkest Star and it’s up on Kickstarter now. […]
Categories: Game Theory & Design

Renegade Game Studio Taking Pre-Orders For Junk Orbit

Tabletop Gaming News - 10 April 2018 - 9:00am
Humans are pretty bad about leaving a trail wherever we go. Even well-meaning people leave stuff behind. And that penchant for being a bit messy can follow us even out into space. But one man’s trash is another man’s treasure, and that’s where you find yourself in Junk Orbit. Your job is to collect this […]
Categories: Game Theory & Design

Dries Buytaert: Defining Drupal's values and principles

Planet Drupal - 10 April 2018 - 8:47am

Since its founding, Drupal has grown a great deal, and today there are thousands of contributors and organizations that make up our community. Over the course of seventeen years, we have spent a great amount of time and effort scaling our community. As a result, Drupal has evolved into one of the largest open source projects in the world.

Today, the Drupal project serves as a role model to many other open source projects; from our governance and funding models, to how we work together globally with thousands of contributors, to our 3,000+ person conferences. However, the work required to scale our community is a continuous process.

Prompted by feedback from the Drupal community, scaling Drupal will be a key focus for me throughout 2018. I have heard a lot of great ideas about how we can scale our community, in addition to improving how we all work together. Today, I wanted to start by better establishing Drupal's values and principles, as it is at the core of everything we do.

Remarkably, after all these years, our values (what guides these behaviors) and our principles (our most important behaviors) are still primarily communicated through word of mouth.

In recent years, various market trends and challenging community events have inspired a variety of changes in the Drupal community. It's in times like these that we need to rely on our values and principles the most. However, that is very difficult to do when our values and principles aren't properly documented.

Over the course of the last five months, I have tried to capture our fundamental values and 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 and 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.

I shared both the values and the principles on Drupal.org as version 1.0-alpha. I labeled it alpha, because the principles and values aren't necessarily complete. While I have strong conviction in each of the Drupal principles and corresponding values, some of our values and principles are hard to capture in words, and by no means will I have described them perfectly. However, I arrived at a point where I wanted to share what I have drafted, open it up to the community for feedback, and move the draft forward more collaboratively.

While this may be the first time I've tried to articulate our values and principles in one document, many of these principles have guided the project for a very long time. If communicated well, these principles and values should inspire us to be our best selves, enable us to make good decisions fast, and guide us to work as one unified community.

I also believe this document is an important starting point and framework to help address additional (and potentially unidentified) needs. For example, some have asked for clearer principles about what behavior will and will not be tolerated in addition to defining community values surrounding justice and equity. I hope that this document lays the groundwork for that.

Throughout the writing process, I consulted the work of the Community Governance Group and the feedback that was collected in discussions with the community last fall. The 1.0-alpha version was also reviewed by the following people: Tiffany Farriss, George DeMet, Megan Sanicki, Adam Goodman, Gigi Anderson, Mark Winberry, Angie Byron, ASH Heath, Steve Francia, Rachel Lawson, Helena McCabe, Adam Bergstein, Paul Johnson, Michael Anello, Donna Benjamin, Neil Drumm, Fatima Khalid, Sally Young, Daniel Wehner and Ryan Szrama. I'd like to thank everyone for their input.

As a next step, I invite you to provide feedback. The best way to provide feedback is in the issue queue of the Drupal governance project, but there will also be opportunities to provide feedback at upcoming Drupal events, including DrupalCon Nashville.

Categories: Drupal

Defining Drupal's values and principles

Dries Buytaert - 10 April 2018 - 8:47am

Since its founding, Drupal has grown a great deal, and today there are thousands of contributors and organizations that make up our community. Over the course of seventeen years, we have spent a great amount of time and effort scaling our community. As a result, Drupal has evolved into one of the largest open source projects in the world.

Today, the Drupal project serves as a role model to many other open source projects; from our governance and funding models, to how we work together globally with thousands of contributors, to our 3,000+ person conferences. However, the work required to scale our community is a continuous process.

Prompted by feedback from the Drupal community, scaling Drupal will be a key focus for me throughout 2018. I have heard a lot of great ideas about how we can scale our community, in addition to improving how we all work together. Today, I wanted to start by better establishing Drupal's values and principles, as it is at the core of everything we do.

Remarkably, after all these years, our values (what guides these behaviors) and our principles (our most important behaviors) are still primarily communicated through word of mouth.

In recent years, various market trends and challenging community events have inspired a variety of changes in the Drupal community. It's in times like these that we need to rely on our values and principles the most. However, that is very difficult to do when our values and principles aren't properly documented.

Over the course of the last five months, I have tried to capture our fundamental values and 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 and 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.

I shared both the values and the principles on Drupal.org as version 1.0-alpha. I labeled it alpha, because the principles and values aren't necessarily complete. While I have strong conviction in each of the Drupal principles and corresponding values, some of our values and principles are hard to capture in words, and by no means will I have described them perfectly. However, I arrived at a point where I wanted to share what I have drafted, open it up to the community for feedback, and move the draft forward more collaboratively.

While this may be the first time I've tried to articulate our values and principles in one document, many of these principles have guided the project for a very long time. If communicated well, these principles and values should inspire us to be our best selves, enable us to make good decisions fast, and guide us to work as one unified community.

I also believe this document is an important starting point and framework to help address additional (and potentially unidentified) needs. For example, some have asked for clearer principles about what behavior will and will not be tolerated in addition to defining community values surrounding justice and equity. I hope that this document lays the groundwork for that.

Throughout the writing process, I consulted the work of the Community Governance Group and the feedback that was collected in discussions with the community last fall. The 1.0-alpha version was also reviewed by the following people: Tiffany Farriss, George DeMet, Megan Sanicki, Adam Goodman, Gigi Anderson, Mark Winberry, Angie Byron, ASH Heath, Steve Francia, Rachel Lawson, Helena McCabe, Adam Bergstein, Paul Johnson, Michael Anello, Donna Benjamin, Neil Drumm, Fatima Khalid, Sally Young, Daniel Wehner and Ryan Szrama. I'd like to thank everyone for their input.

As a next step, I invite you to provide feedback. The best way to provide feedback is in the issue queue of the Drupal governance project, but there will also be opportunities to provide feedback at upcoming Drupal events, including DrupalCon Nashville.

Categories: Drupal

Pages

Subscribe to As If Productions aggregator