Design team ticket tackling tools

This page is a stub.
It is being filled in for a class of students at Allegheny college who will be working on tickets with us.

Be bold.
Feel free to edit this page; there is an "undo" button, which is the "history" tab at the top of this page; if you click there you'll go to a page where you can roll back any edits you've made). Add new sections. Edit old ones. Take these notes out. Clean it up and make it useful. This page is yours to create - it's everyone's to create.

So here's the problem:

The Design team has a bunch of tickets.

They need to be done.

They also need to be made more possible to work through - right now the pile is large and daunting, assumes a lot of background knowledge, uses acronyms, may not have a clear workflow... and so forth. Can you, as a newcomer, figure out what the Design Team does and how to help it? If not, this is a bug - and it's a bug that is our fault, and you will be helping us by pointing out how we can fix it. What resources do we need to provide to new Design contributors in order to smoothly get them started?

Your mission: close tickets. (Contact Mel Chua if you're not exactly sure what that means.)

Remember, the goal is to be "productively lost" - this is all the information we have right now, and you will probably have questions right away - we don't know what questions you need answers to, though, so once you find them we'll be pulling up (or making up!) the information for those answers. You should feel free to make up answers, too.

If you spend more than 5 minutes trying to figure out the answer to a question, you should probably pop on IRC and ask that question. #fedora-design is the main Design channel.

If you spend more than 15 minutes asking the question on IRC and don't think you're getting a good response, you should ask the mailing list. There's already a bit of a conversation going on there about this page.

It starts now.

Good luck!