Hi
Short summary if you just want to report a bug, wishlist item, feedback,
whatever, related to DebConf:
Write a mail to rt@debconf.org and describe whatever you think. Someone
of us, whoever fits with the request, then has the work to
reply/fix/whatever, and you will get a notice.
Simple.
Now, for those that want more and are in the organisation team:
We now have rt.debconf.org running (Needs logins). For now we have some
basic groups and queues[1] and a few users created. The intent is to
have a single system containing feature requests for any DebConf-related
technical issues we have (such as website, mailing lists, etc), buglists for
it, a todo list of things that need to be done, and the ability to
assign those to people who want to do that work.
Working with it is relatively simple, after you got the basics. There is
a nice introduction in a wiki[2], but feel free to ask me on IRC if you
have trouble.
Basic workflow:
Someone writes a mail to our RT, describing a problem.[3]
The mail will land in a queue named "Unsorted". Lets say this ticket (the
mail gets turned into a ticket, as everything is a ticket in RT)
describes a problem on the website, where our webteam wrote that
DebConf7 is on mars, but it should be on the moon. Clearly a problem, its
much more expensive to get to mars...
So, a bit later someone from the webteam logs into our RT, sees that
there is a ticket in queue "Unsorted" and also sees (thanks to the
clear subject. If the subject is unclear he can look at the full mail text)
that it is for the webteam. So the first thing he does is to "open" the
request, so it changes its status from NEW to OPEN. The window changes
and shows details, where our webmaster looks at "Basics"[4] and changes
the queue to "Webteam". In the same window he can change the owner, and
as he can fix it he changes the Owner to be himself. So, due to changing
the queue to that of the webteam he marked the webteam to be
responsible, and with setting himself to the owner our fictive webmaster
said he himself is the one fixing this problem. After saving that,
so state information is now in the database and goes to fix the problem.[5]
While our webmaster is working on the fix for the ticket someone else
can log into the system, see the ticket, but also sees that $foo is
working on it. He can add a comment, he can add himself to a watcher
list - which means he sees when $foo closes this ticket. This is useful
because you can see if a ticket that you depend on changes state.
A while later, after he fixed the problem (and had some milk), our
webmaster logs back into the system and sees the ticket he took is still
marked as open. Clicking on the ticket gives him more detailed information,
and finally also the possibility/link to resolve this ticket.
Resolving the ticket asks you to enter a reason, and you can also select
if its a comment or a reply. If you select reply then the reporter gets
informed that his report was worked on, and why you closed it. (Comments
do not inform the reporter.)
Creating a new ticket is simple, just mail rt@debconf.org. If you have a
login you can also create tickets directly in the system. You can select
the queue in which to create the ticket, but as you do not see queues of
Groups you are not in - just create it in "Unsorted" then.
So much for the basic workflow. It's really simple to deal with it after you
have done it once or twice.
For now I created a few teams in this request tracker, together with
some queues. The queues are:
* Admin Every global administration request that doesnt fit in
other queues. Ie a package to be installed on foo, a broken
and non-responding machine, mail not sent, etc.
* LocalAdmin Those people who are local admin of machines used directly
at DebConf. Not used outside a running DebConf
* Localteam queue for the localteam of a DebConf.
* Orga Anything that has no queue of its and doesnt fit in Admin goes here
* Press Press related tickets here
* Sponsorship Sponsorship related queue (no private data from sponsorees)
* Talks Talk related queue
* Unsorted Not yet assigned to any group/person. As written above new
tickets always start here.
* Video Anything related to video@debconf
* Website Anything about our Website
* gallery.debconf.org gallery.debconf.org queue
* lists.debconf.org Any problems or whishes with/for lists go here
The groups are:
# Adminteam
# Galleryadmins
# Listadmins
# Localadmin
# Localteam
# Organisationsteam
# Pressteam
# Sponsorshipteam
# Talkteam
# Videoteam
# Webteam
If you think i missed a group or a queue, which is possible as my mind
is blowing up after the install, open a ticket (by writing mail to
rt@debconf.org) :)
I also created a few accounts already, to have something to play
with. Those people should get a mail together with this one, giving out
passwords. If you haven't got such a mail - its all my fault. You can
either open a ticket or ping me on IRC, and you get your account. (And
tell me in which groups you want to belong.)
Of course you need to use this system to make it useful, so please dont
ignore it. USE IT. :)
Anything I missed for now?
[1] One could name the queues as category or area too, queue is just how
RT calls it.
[2] http://wiki.bestpractical.com/index.cgi?ManualUsingWebInterface
[3] Alternatively one of us with an account creates a ticket in the
webinterface.
[4] RT is translated into many languages, so he looks at "However its
called in his language" really. :)
[5] Of course you have a lot of more ways to modify the ticket, for
example you can enter time information, but we do not need all of
that. For more information about all possible ways of playing with a
ticket see [2]. Fell free to create your own ticket by mailing
rt@debconf.org and then play with it.
--
bye Joerg
[2.6.15.4 direkt nach 2.6.15.3]
<HE> Linus muss Gentooler hassen.
<formorer> wieso?
<HE> Naja, die dürften ihre optimierten Kernel gerade fertig gebaut
haben und müssen jetzt aus prompter Versionitis auf das
Ausprobieren verzichten und den neuen kompilieren...
Attachment:
pgpx8aYK9OMHI.pgp
Description: PGP signature