New "Novice issues" link in Contributors links looks like its only core issues

Just wanted to point out that I made the same assumption when I first saw the new link.

Seems like a sane and good improvement to me.

Maybe we should also get rid of the separate sections for patch and bug bingo and fold those into the bottoms of the core and all projects sections? Something like this:

Core issues
10 Critical bugs (D8 + D7)
100 Major bugs (D8 + D7)
6 Critical tasks (D8 + D7)
92 Major tasks (D8 + D7)
2221 Pending bugs (D8 + D7)
1618 Patch queue (D8)
Core patch bingo
Core bug bingo

All projects
147 Novice issues
Issues needing triage
Contribution patch bingo
Contribution bug bingo

Mailing list archives
...

I didn't want to just edit the summary with this suggestion, but if folks agree, feel free to fold it into the summary... I know technically "contributions" != "all projects" so it's slightly misleading headings, but I think it's fine.

Cheers,
-Derek

p.s. The actual code for this lives in drupalorg module, so this should probably move issue queues once someone's ready to work on a patch.

If we're going to have a core-specific Novice count and link, then I think we should call the other section "Other projects" or "Contributed projects" and fix all the links to be contrib-specific (maybe adding a core-specific "Issues needing triage" link). Otherwise, the new layout would be basically just as confusing as we have now.

Cross referencing for interested parties. ;) #1093206: Re-think the patch/bug bingo links from the contributor block

I'd like the see the suggestions in #4 applied. I'm a novice contributor and I have found some tickets that are for relatively new modules with few users on old versions of drupal. Example #1284584: Server setting should be radio buttons. It's unclear whether the module maintainer is just trying to be helpful by throwing out an easy task for someone to learn how to contribute... or if they are trying to get some free labor on a module! :)

I like the idea of the novice queue being for core issues so that the contributions are definitely used/needed and impact the community at large. It's not to say that novice issues can't fall into contrib. But if the goal is to give core developers more time to focus on big issues and novices some experience rolling patches, then it's best to keep that focus for the novice issue queue.

Anyway, just my 2 cents.

The goal is to provide new contributors with a targeted list of some easier stuff to work on. To that end, I think the wider we can cast the net, the better, though I can understand working on Drupal core Novice issues to feel more impactful. I still think it makes sense to list all projects since you can always filter that list to just core issues, but I acknowledge I am not the target audience for this page so I might be mistaken.

Hey @webchick. It was nice meeting you at Drupal camp colorado :)

I see your point in #8. If the goal is primarily a way for people to put on training wheels, the wider the net the better. I just know that I lost a lot of motivation to help earlier on when I saw a bunch of submitted patches get no response for a while... or the maintainer simply didn't merge them.

With core, it's an established problem and thus a fix is almost always going to get accepted IF it's the correct solution. Helps keep the motivation up for newbies that love a little recognition (I'm just as guilty as anyone here).

In short, I agree we should probably just leave the nets wide so that we get a lot more options for newbies to participate... and as long as this new help is welcomed/accepted, I think my concerns regarding filtering out contrib are no longer applicable.

How about putting novice just below major?

Agree, this needs to be fixed since it confuses a lot of people. It should be divided into separate groups and listed under appropriate title as stated

The Novice link now includes more than just Core so marking this old issue as closed:
https://drupal.org/project/issues/search?status[0]=1&status[1]=8&status[...