I'm curious, I've contributed a very occasional patch to core and I've never realized that JS patches should be tagged as such.
Did I miss something? Or do we need to change the guidelines around posting issues to Drupal core so that JS issues don't languish?
Not sure about the guidelines, I mean now you know it and the wording does prevent some level of abuse. It's just that JS is a very special case in the core queue. I don't think we should impact the majority of issues just for this. After all JS is not even 10% of the Drupal code.
Now that I'm on the Drupal planet it'll be easier for people to fill in their issues properly, hopefully :)
Yeah I saw the reply from Crell AMA, I still like being in the trenches though. I don't think being as detached would work for me but something more meta is needed for the things I want to do. Hopefully I won't take to much time to find the sweet spot.
Yes, I'm glad your blog is on DP! That's how I can across it and now I know. I'll look to see if there is some new contributor documentation that can be amended to include this information. Considering the number of jQuery devs vs. Drupal devs, I see JS patches as a great way more folks involved with core. (Not to mention improving Drupal's JS code quality!)
And, yes, I'll post a 8.x patch in that issue, as requested. :)