Voting Disabled

Rank15

Idea#25

Active
Drupal.org »

Add a "Difficulty" field to all d.o issues

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:

- novice

- beginner

- intermediate

- advanced

- expert

- ninjutsu

Submitted by sun 2 years ago

Comments [15]

  1. xjm

    Hmm. This is a really neat/interesting idea, but seems like it might be kind of arbitrary. I've seen enough of chx's novice issues to know that. :)

    2 years ago
    2 Agreed
    0 Disagreed
    1. xjm

      On the other hand, I guess maybe a field would be more visible than a Novice tag. I might reduce sun's list of 30 options to "Novice," "Intermediate," and "Here be dragons."

      2 years ago
      2 Agreed
      0 Disagreed
    2. xjm

      On the other other hand, it adds yet another field for people to fill out, and filing issues is time-consuming enough already.

      2 years ago
      0 Agreed
      0 Disagreed
    3. +1 to a Novice tag. Should help triage and make sprints easier.

      2 years ago
      0 Agreed
      0 Disagreed
  2. I think this is too subjective. What is "difficult" depends on your skill level as well as your ability to put yourself in the place of someone with a different skill level. Trying to break it down this much I don't think will be valuable and could end up with people disagreeing over what it should be set to and wasting time.

    2 years ago
    1 Agreed
    0 Disagreed
    1. Raf

      It is indeed subjective, up to a point. This suggestion's been discussed plenty of times before, and if I recall correctly, what would be concidered as "easy" would be things like fixing a typo or such. It'd be a great way for people to have a look at the code, so it's not as intimidating anymore.

      After that, it's true that it might be subjective. I guess some serious guidelines'd have to take care of that. And that's a nasty point: rules and regulations. It's just more stuff contributors have to keep in mind. It would avoid assigning something as "novice" because it seems like half an hour fixing an algorithm, turning out to be a three-day trial of debugging several obscure functions in common.inc to find out why it all breaks in this one particular case.

      2 years ago
      1 Agreed
      0 Disagreed
  3. 3 levels seems fine (easy, intermediate, difficult)

    2 years ago
    0 Agreed
    0 Disagreed
  4. xjm

    Another reason I'm not sure this could work as intended is that it attempts to apply a flat rating across the issue. An issue can be really difficult to solve and still have easy tasks associated with it (writing tests, testing the patch, etc.). I wouldn't want to filter out those tasks for people looking for approachable issues.

    2 years ago
    1 Agreed
    0 Disagreed
  5. I'd rather have a 'skills involved' field. It would help me see quickly whether an issue is within my skillset — it might be hard for someone else, but easy for me :)

    If there were skill-based feeds, we would probably get them done faster.

    2 years ago
    7 Agreed
    0 Disagreed
    1. Good idea. Now boil down 'skills' into a tag cloud ? single/multi select drop down?. :)

      -PHP

      -Javascript

      -jQuery

      2 years ago
      2 Agreed
      0 Disagreed
    2. This is really good idea to have skill level on issues for new contributors like me. It will help newbies because many times other people want to contribute but having skill level on issue is going to motivate many people look at the issue and take a stab at it.

      2 years ago
      0 Agreed
      0 Disagreed
  6. Great idea. "It's hard for new contributors to find a suitable issue to get involved." Very true statement. I think adding this and the skill level will not overwhelm new users and challenge those on or reaching intermediate level by contributing to issues on based on skill sets.

    This feature may also serve as a statistic. e.g. what level skill set is the community having more issues in and how can we improve it.

    2 years ago
    0 Agreed
    0 Disagreed
  7. It's a nice idea, but the proposed nomenclature offers little insight. Does this speak to required knowledge? Amount of time involved? Amount of brain power needed for the problem solving?

    A very low-tech issue could require quite a lot of thinking and consideration, or problem solving -- things anyone would want to take on only when feeling fresh and most alert. A very high-tech issue involving deep Drupal API stuff could be rather straightforward from a problem-solving standpoint, and take someone who has the appropriate knowledge just a few minutes to solve.

    So what terms would be most descriptive?

    2 years ago
    1 Agreed
    0 Disagreed
    1. Good point. No person's competence to contribute cannot be adequately reduced to a single, unqualified ranking. For example, someone may be an expert themer but a novice developer. Some of our best programmers would be completely incapable of doing "novice" translation. Some of our top project managers couldn't roll a patch to save their lives. And some of our best designers wouldn't know an alter hook if they saw it. I like the idea, but it would require a thoughtful implementation to be of more value than the tags we already have.

      On a side note, PLEASE don't use ninjitsu, kung fu, ninja, cowboy, or el dorado superfly as difficulty options. They just make us sound goofy. ;)

      2 years ago
      0 Agreed
      0 Disagreed
  8. I vote for a category 'unknown' as well.

    2 years ago
    0 Agreed
    0 Disagreed

Vote Activity [ 20 ] [+]

(latest 20 votes)

Events [ 1 ] [+]