Update Documentation issue queue components

Dur, btw, yes we can change this ourselves (i.e. site admins can) so we don't need to move anywhere really, just figure it out and sepeck or myself can change it.

The more I think about the actual list as well, I am thinking that using books for components isn't the best move. Firstly, names and number of books morphs over time and secondly, it doesn't really help me narrow my list of tasks into anything meaningful. Project module's native way of doing things is not ideal for the handbook already so I think we should use what we have to make it as useful as we can. I'm thinking that if we used components for types of tasks, that would help people a) identify things more easily and b) find things they want to work on more easily.

I'm thinking along the lines of something more like this:
Draft review
Correction/Clarification
Page placement
Delete comments
Missing documentation
Archive
Vandalism/Spam
api.drupal.org
Misc

@aclight, yeah I am aware of that problem and yes, it would be a bit of a pain, but honestly it is worth it to me to make the docs queue more useful. It is confusing enough for people to use rather software specific things for docs and having components that make no sense is just more befuddling. I'm prepared to move ahead with changing the list once we find a good list that is a more long-term solid list and then deal with the changing of components on the issues until it gets all cleaned up and "righted."

If folks can give feedback on the list to use, that would be great because I do plan to move ahead with it and it would be peachy if we can do it once and not have to move it around in the future.

OK, I redid my list a touch and have thoughts on the others.

Correction/Clarification
Page placement
Delete comments
Missing documentation
Archive (maybe call this Outdated instead?)
Vandalism/Spam (= Delete pages. I prefer identifying what they are and then we can determine action.)
Join docs team
api.drupal.org
Misc (This is simply following what is the default on all issue queues. I'm open to changing it but if it stays the same that will help avoid *some* of the project validation squawking.)

# Doc team processes
Yeah, I like the idea of some sort of "meta" category where we can have procedures and high level documentation issues (like restructuring). Though I also sort of feel like these are not so common and so we could get by with Miscellaneous for those. I dunno.

# Edit Getting started 5 (and, presumably after a while) Getting started (ie. the PDF-docs)
I am expressly not adding anything about this since the current DocBook format/editing process of this section is untenable and can't continue as is. One of the major things on my list to address at the docs sprint in Szeged is how to come up with a workable situation for the "official docs." I'd rather not add a new category that may need to change/be removed a short while later since it will just cause extra project module squawking.

# Tasks that require fancy input formats (Hm, not sure how to keep that short in a way that people will understand. Most people don't really know it is about "input formats" - they just know images don't show up or whatnot. I also think this may happen infrequently enough that Misc works for it.)

# Small changes (typos, minor corrections, misplaced pages) - For when I have a few minutes, don't feel like tackling anything big
# Medium changes (rewrite of a single page)
# Major tasks (reorganisations, rewriting several pages) - Those issues which need a lot of thought, and input from a lot of people.
This seems like a very fuzzy area and doesn't seem like an easy thing to categorize or make clear without sentences explaining them, and that is just for docs team members. People not on the docs team will have zero idea what these mean nor a clear idea where something fits. They might think it is easy, when it is hard and vice versa. I'm -1 on these but open to discussion. We can use the minor priority for small changes.

"You suggested "Draft review" as one of the components, I suggest we use "Status: patch (code needs review)" instead, since people may want reviews for a lot of different doc issues."
Yeah, I removed that one.

Good point on the minor/small thing, but I do still feel that small, medium, and large are too fuzzy and are likely to generate more questions than provide clarity.

Page placement --> "Placement and navigation".
Agreed, good point.

Delete comments --> "Advanced docs permissions required"
Hrm, well these are really site admin perms. I do see where the "advanced" stuff would be a good group. I'd like to really *encourage* folks to clean up comments so I'm partial to that specific, clear, easy to find one, but I can also see just grouping it in. I basically think I'm swayed on that one. I'd like to play with the name though, maybe even just saying "Advanced permissions required."

The "Missing docs" one I did intend for people to report gaps in the docs and didn't really think of reviews for new stuff. Perhaps we could call this one "New documentation suggestions" or something? I'm kinda meh on "new pages" because sometimes it may not be a new page, it could be just adding more info to an existing page or adding a whole new section.

Outdated wfm.

zirvap, thanks a ton for talking this out and bouncing ideas around; so incredibly useful.

Here is a new list based on the above discussion:

Correction/Clarification
New documentation
Placement and navigation
Outdated
Vandalism/Spam
Join docs team
Advanced permissions required
api.drupal.org
Misc

Correction/Clarification
Not all corrections/clarifications are minor, nor easy. If we say that these are easy ones then where do big ones go? I don't know that folks will think new docs or outdated is exactly what they should put it in. I also still feel like asking folks to determine what is minor, average or major is hit or miss. I bet most people have no idea if it is minor or not. It might be minor if you know the subject but it might be major if you have to research the subject before you can correct it. Other than typos and bad links, I think degrees are fairly subjective and so a thing to avoid.

New documentation
Yeah, so I had this as Missing documentation but then zirvap brought up that this can be used not only for people reporting missing docs but also for issues where new documentation is being created. I suppose that if I wrote up some new docs that putting it under missing docs would be OK, but I agree that it isn't quite as intuitive for me to say "hey, I have new documentation" and then mark it as missing. So I dunno, I'm not wedded either way on this one. Anyone else have strong feelings or arguments? :-)

I prefer to keep the Outdated as its own category since that can end up being different stuff altogether, as in Archiving. We don't need to update all old docs.

Advanced permissions required
OK so if we reverse the Advanced perms (and that is a waffley one for me) then what are the main tasks folks need under that? It originally started as Delete comments and I feel that is the major use case. I also realize that the advanced perm of weighting is now also accounted for in the Placement and Navigation one. Do we have other specifics that we need? I'm fine with just adding Delete comments and letting other random site admin tasks getting shoved in to Misc.

api.drupal.org
Yeah, I am on board with that. That would mean getting that issue resolved before this one then. Not a problem per se, but I guess I'll need to beat the drum on that one hard to get this issue moving in a timely manner. ;-) We could technically make the other changes in this queue, leave the CVS component for now and then switch it later, depending on the outcome of the other issue.

Misc
OK, OK, I concede. ;-) Then I like being explicit with "Other Documentation Issues".

Getting Started
That is not even worthy of an issue right now as far as I'm concerned. This needs to be completely rethought and we need to come up with an actual workable plan through discussion. We need to hash this out on the docs list. This is one of the top issues I have that must be dealt with/kicked off during the DrupalCon docs sprint. So, let's not even go there in this thread. ;-)

OK, so here is the list we have:

Correction/Clarification
New documentation
Placement and navigation
Delete comments
Outdated
Vandalism/Spam
Join documentation team
Documentation in CVS
Other documentation issues

I'm going to implement this today and send an email out to the doc team list and make a forum post about it so everyone realizes we know about the validation error problem. One immediate task I'd like to work on once we change them, is to start at the beginning of the queue and reset as many of the issues as we can. I'd rather "front load" the change work than just do it as we work on the issues because while we may know what is going on it will likely scare off people who don't understand what's up.

Thanks to everyone for chiming in and getting it all hammered out. w00t!

The change is in and forum post/email done.