All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Hello! You've arrived at part 2 of a series of 3 blog posts about the Mentored Core Sprint, which traditionally takes place every Friday at Drupalcon.
If you haven't already, please go back and read part 1.You may think sprinting is not for you ...
So, you may be the kind of person who usually stays away from the Sprint Room at Drupal events. We understand. You would like to find something to work on, but when you step in the room, you get the feeling you're interrupting something really important that you don't understand.
It's okay. We've all been there.
That's why the Drupal Community invented the Mentored Core Sprint. If you stay for this sprint day, you will be among friends. You can ask any question you like. The venue is packed with people who want to make it a useful experience for you.Come as you are
All you need in order to take part in the first-time mentored sprint are two things:
- Your self, a human who is interested in Drupal
- Your laptop
To get productive, your laptop needs a local installation of Drupal. Don't have one yet? Well, it's your lucky day because you can your Windows or Mac laptop set up at the first-time setup workshop!Need a local Drupal installation? Come to the first-time setup workshop
After about half an hour, your laptop is now ready, and you can go to the sprint room to work on Drupal Core issues ...You do not need to be a coder ...
You do not need to be a coder to work on Drupal Core. Let's say, you're a project manager. You have skills in clarifying issues, deciding what needs to be done next, managing developers, and herding cats. You're great at taking large problems and breaking them down into smaller problems that designers or developers can solve. This is what you do all day when you're at work.
Well, that's also what happens here at the Major Issue Triage table!
But - you could just as easily join any other table, because your skills will be needed there, as well!Never Drupal alone
At this sprint, no-one works on their own. You work collaboratively in a small group (maybe 3-4 people). So, if you don't have coding or design skills, you will have someone alongside you who does, just like at work.
Collaborating together, you will learn how the Drupal issue queue works. You will, most likely, not fix any large issues during the sprint.Learn the process of contributing
Instead, you will learn the process of contributing to Drupal. You will learn how to use the issue queue so you can stay in touch with the friends you made today, so that you fix the issue over the coming weeks after Drupalcon.It's never too late
Even if you've been in the Drupal community for over a decade, just come along. Jump in. You'll enjoy it.
A very welcoming place to start contributing is to work on Drupal documentation. This is how I made my first contribution, at Drupalcon London in 2011. In Vienna, this table was mentored by Amber Matz from Drupalize.Me.
This is one of the most experienced mentors, Valery Lourie (valthebald). We'll meet him again in part 3, when we come to the Drupalcon Vienna live commit.
Here's Dries. He comes along and walks around, no one takes any notice because they are too engaged and too busy. And so he gets to talk to people without being interrupted.
This is what Drupal is about. It's not about the code. It's about the people.
Next time. Just come. As a sprinter or a mentor. EVERYONE is welcome, we mean that.
This is a three-part blog post series:
Part one is here
You've just finished reading part two
Part three is coming soon
Let's see how to update your Drupal site between 8.x.x minor and patch versions. For example, from 8.1.2 to 8.1.3, or from 8.3.5 to 8.4.0. I hope this will help you.
If you are upgrading to Drupal version x.y.z
x -> is known as the major version number
y -> is known as the minor version number
z -> is known as the patch version number.rajamohamed Sat, 03/24/2018 - 10:31
This module is especially useful for developers working on sites where there are configuration overrides in place depending on the environment. It prevents confusion that arise when changing a form setting, but appears to not take effect.
Provides an easy way to add AJAX validation on forms on per field basis.
TODO: Add more documentation.
Many of my longest friendships were born in the Drupal community. I’ve been attending DrupalCons, Drupal Camps, and other events since DrupalCon Barcelona 2007 and centered most of my professional life around contributing to the project as a developer and a teacher. In 2010 that included serving as a mentor in the Google Summer of Code program for a new contributor who wanted to work on Drupal Commerce’s affiliate module, bojanz.
Bojan Živanović and I got to know each other that summer through many IRC chats and coding sessions. After he completed his project successfully, we met at DrupalCon Copenhagen and celebrated at McDonald's. I sure knew how to treat a friend!
I later convinced him to join Commerce Guys’s development team based in Paris. He served on our client services team before diving head first into Commerce Kickstart 2.x development and then creating a whole suite of modules to support usage based billing for subscription services like Platform.sh.
Around DrupalCon Austin in 2014, it appeared Bojan's mission with Commerce Guys might be complete. However, I saw an opportunity for him to develop further as a leader in our company and community. I was already busy leading client services with our U.S. team and then with acquiring and refocusing Commerce Guys around Drupal Commerce. It made perfect sense to me to appoint him to be project lead for Commerce 2.x.
That decision has served Commerce Guys and Drupal Commerce well over the last several years. Bojan brought renewed vigor to the project and discipline around competitive research and automated test coverage that far exceeded my own. He's also proven to be an able mentor in his own right, helping dozens of contributors and whole agency teams learn Drupal 8 development in general and Commerce 2.x development in particular.
Today is Bojan's birthday, and reflecting on our almost 8 years of friendship has obviously made me sentimental. At our first meeting in Copenhagen, my daughter Éowyn was just taking her first steps and wouldn't ever remember meeting Bojan. Today she sees him regularly during company Zoom calls and his occasional visit to our home in Greenville, SC. He's not just some random person from daddy's work, he's Uncle Bojan and a trusted friend.
We're all wishing you a happy birthday, Bojan, and we're grateful for your years of contribution and leadership in our midst. I'll have to hit the 2.x queue this evening to send you a birthday present disguised as a patch.
This module uses AJAX to count file downloads. It's optimized for medium to large sites (such as my own site, OpenGameArt.org) where the total number of file downloads might be in the hundreds of thousands or even millions. Using this module has some advantages and some limitations versus other methods of counting downloads:
Provide a way to switch HTML Tag from Frontpage to other pages.
The native block-system-branding-block display site_logo, site_name and site_slogan in div HTML Tag.
This module add h1 tag in frontpage for branding-block and keep the native display for the others pages.
Matt Grasmick: Stranger in a familiar land: Comparing the novice's first impression of Drupal to other PHP frameworks
Drupal 8 adoption is flagging. Why? I tried to lay my biases and assumptions aside and set out to find the answer. What I found suprised me.
I decided to perform an experiment. Placing myself (as much as possible) in the shoes of a senior developer without any Drupal experience, I attempted to get a new "Hello World" site up and running in four different PHP frameworks: Wordpress, Laravel, Symfony, and Drupal.
I set a few ground rules for myself:
- Start at square 1. Google "Drupal" (or Wordpress, etc.).
- Use only information found organically via my Google search and subsequent clicks.
- Take the path of least resistance. In other words, choose the easy way when more than one option exists.
- Avoid the command line when possible.
- Time required.
- Number of clicks in web browser.
- Number of CLI commands run.
I do not claim that this…more
A module for those who need to allow free text in autocomplete fields that matches to a field on either the same entity or a field within a referenced entity. Module falls back to standard autocomplete functionality.
Field types available are Entity Reference, Field collection, or Paragraphs, though it may work on other referenced entities. File an issue in the queue if needed. Note that this module currently only matches to a referenced entity one level deep. (i.e. it will not match a field on a referenced entity of a referenced entity.)
Creates a page which displays a different, random node of a selected type every time it's accessed.
Commerce add to cart matrix allows you to configure a new way of displaying the add to cart form.
All the possible variation combinations can be displayed in a table and allow instant add to cart for all of those.
The variation combination can be configured from the field formatter.
This module does nothing on its own other than provide an API that
allows modules a way to specify any dependency, based on a list.
This is, in part, due to the vast Drupal ecosystem where there are tons of "similar" projects that do almost the same thing but just "slightly" different. To compensate for a site that may use one variety of "popular" module over another, this allows a module to support multiple projects.
This module provides simple entity forms as blocks like Ctools provides Entity view (Content) block and others. It supports contexts and different form modes.
Janos Pasztor built his own Content Delivery Network. While I wouldn't want to operate my own personal CDN, it does sounds like a fun project for those interested in web performance.