Badges [ 5 ] [-]
Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 3 ] [+]
The Component property of an issue is a single value currently. Often times, however, an issue spans over multiple components/topics, in which you have to figure out the primary component and usually assign the other ones as issue tags. Especially for Drupal core, an issue might be related to Node module, but is also changing plethora of CSS, JS, and markup. And oh, that very same issue might even try to "fix" an oddity ...more »
D7 no longer runs on crappy shared hosts. D8 bumped requirements even more. A curated list of Drupal-compatible hosting providers would allow users, site builders, and developers to find a suitable service provider. I'm not talking crappy free-text node bodies à la d.o marketplace. Instead, detailed structured fields for individual functionality/versions/compatibility per provider, which can be shown in a matrix view. ...more »
It's hard for new contributors to find a suitable issue to get involved. Starting with a "Novice" issue always makes sense to understand how the process works, but what do you do after you crossed that line?
Let's add a new, optional "Difficulty" property to all d.o issues: