After discussion tonight in #drupal, we came up with a new tag "novice" which can be applied to issues that are good "starters" for people new to the project.

Drupal core "novice" issues: http://drupal.org/project/issues/3060/term/772
All "novice" issues: http://drupal.org/project/issues-term/772

Problem is, those URLs are not very novice-friendly. ;)

Here are some options:

a) /novice-issues-core, /novice-issues-all
b) Just /novice-issues (for the "all" list, let them filter down to Drupal -- difficult because there are no issue filters on that list)
c) project/issues/drupal/term/novice, project/issues-term/novice (still long and hard to remember, but less ugly than the numbers)
d) Other?

Begin! I'd like to get this finished up by Sunday night, so whatever one has the most traction by then gets a path. ;P

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Oh, incidentally, regardless of the outcome of this bikeshed argument, if you could start tagging "easy" issues you find in the queue (like they would take you a few minutes to solve, but you are too busy), please feel free to use this tag to identify them! We chose this term because it will work across all projects (Documentation, themes, etc.)

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

c) might be ugly today, but might also be future-proof. Supporting term names built-in would be an easy step for PI. So, +1 for c) for forward compatibility.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

The thing I don't like about c) is until ALL issue paths use "real names" rather than term IDs, it creates a usability issue because people try and replace "novice" with "performance" and it doesn't work. I forsee this leading to support requests and bug reports.

The other thing is I'd like this to be a short, memorable path. Ideally, I'd love it to be something like just /novice but I don't think that's descriptive enough, and I'm not sure to which queue that would point.

dmitrig01’s picture

dmitrig01 commented

novice-issues which is an alias to project/issues/drupal/term/novice
[Edit: I didn't know what i was talking about sorry. I like a) and it can be aliased.]

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

catch suggested patch/novice and patch/novice/core, which Dave Reid gave the thumbs-up to. Sounds good to me!

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Active » Fixed

Ok, since there are obviously not that many people with too strong of an opinion on this, apart from sun's which sounds like it needs to be either a patch to comment_alter_taxonomy or fixed in views when we upgrade drupal.org to D6, I made the change and have marked this fixed.

add1sun’s picture

add1sun commented

I know you fixed this but I just wanted to say from the docs perspective "issues" is much more broad than "patch." Patch is the kind of term that scares off non-coders, but it is just URL so I'm not pressed.

Status: Fixed » Closed (fixed)
Issue tags: -Bikeshed

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +Bikeshed

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.