So there has been alot of discussion lately about bringing some more
structured project management into the edge server development. One
thing that other open source projects rely heavily on is their ticketing
system. We have collectively decided to make better use of trac. Here
are some general guidelines:
1) Think of trac not just as a "bug tracking" program, but more as a
"task management" program. Everyone (including myself) should make a
better effort to use trac to keep up with all the work they do on the
edge server. Use this as a rule of thumb: If you are submitting
something back to svn, you should be able to type in a ticket in the
comments of the submission (If you use mylyn correctly, it will do this
for you automatically!). If there isn't a ticket, spend the time to
create one before you submit the code back.
2) I have added several "ticket types". Most everything you do will
hopefully fall into one of these ticket types. If you are doing alot of
work that doesn't fall into one of these categories, then we should add
another type.
* concept - an idea for a broad or general enhancement. Should be
broken up into features later.
* feature - A specific enhancement. Should be specific enough to
code.
* task - Something to be done to the code that does not
necessarily add a new feature and does not necessarily fix a
bug, such as refactoring.
* defect - a bug.
* reminder - A note to future developers about something important
that might be forgotten
3) Use Mylyn as an "inbox". Set up mylyn in eclipse and add a query
that displays tickets assigned to you. If you need help setting up
mylyn, go here: http://wiki.rifidi.org/index.php/Mylyn
4) Make an effort to "activate tasks" in mylyn when you are working on
them. This will help keep track how much time you spend on tasks. Also
you can attach the context to the task that you are working on and
submit it back, which is a really cool feature. If you get really good
with mylyn, you can actually schedule tasks.
I know this seems like its going to be a pain in the ass, but let's all
give it a try. It seems like enough other projects are using tracking
programs that I think it will pay off for us too. If you have any
comments or concerns, reply back to this email.
--
Kyle Neumeier
Technical Lead
Pramari, LLC
Manchester, CT
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Rifidi-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rifidi-developers
