[8381] in athena10
Monday, 9:30 PM, categorizing open tasks / bug triage
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Sun Sep 4 05:13:44 2011
Date: Sun, 4 Sep 2011 05:13:31 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: scripts-team@mit.edu, sql-team@mit.edu, debathena@mit.edu, xvm@mit.edu,
linerva@mit.edu, barnowl-dev@mit.edu, gutenbach@mit.edu,
sipb-macathena@mit.edu
Message-ID: <alpine.DEB.2.00.1109040119240.31067@tyger.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Hi all,
It occurs to me that none of our bugtrackers make it easy for new people
(from freshmen to existing SIPB members) to get of what's worth working
on. I found it useful when planning the Debian hackathon two weeks ago to
spend a night reading all the open RC bugs and summarizing what's to be
done in my own words. It would be useful to do something similar for our
own projects.
It would be great if I could get project maintainers (by which I mean
"folks active on the bugtracker", not solely -root) to meet me after most
of the frosh dissipate on Monday. (It's important that we do this early in
term, and Monday seemed like a good time when we should all try to be at
the meeting anyway.) I'd like to go through all of the open bugs in all of
SIPB projects and make sure the bugtracker description is up to date, make
sure priorities, blocking tickets, etc. are correctly listed, and so
forth.
In particular it would be nice to have a good list of tasks that are
visibly useful for people who are new to the project to work on, versus
tasks that would just make the sysadmins happy. I think we also have a
bunch of open tasks/ponies in all of our projects that aren't really
talked about in our bug trackers either. If we come up with those, it'd be
nice to write those down too.
I don't expect attendance at this session to be directly useful to folks
looking to get involved in the projects and not currently involved, since
this is mainly intended at teasing out things that are in people's heads
and not recorded. The intent, of course, is to publicize the resulting
writeups.
If I missed any projects with bugtrackers or open development tasks, feel
free to forward this mail on.
--
Geoffrey Thomas
geofft@mit.edu
