[IMC-Tech] PROPOSAL for simple, two-tier PROJECT TRACKING

[toni --]

PROPOSAL for simple PROJECT TRACKING on imc-tech

in short, the idea is to ask people to come clear
with the work they intend to do, currently are doing, and to do regular
summaries of progress so that all of us involved in this chaos of
imc-tech have some sense about what is actually being done by whome
and how are projects progressing.

this could help a lot with  coordinating imc-tech. writing overal
imc-tech summaries would become easier since projects and it's progress
would be regulary reported on. as well it would be easier for new people
and lurkers to know what projects can they join to.

i guess that for some people that are already overworked this can look
like additional burden, but i have no other idea how to tackle the fact
that we are badly organized with demanding tasks and limited resources.

writing a email about the work that can span over weeks/months/years
to start with and then reporting monthly with short notices is 
a small overhead for many that do a lot, but everyone gains a immensly.
here are the practical examples of it in action used by few of us in 
london working group (under examples) http://uk.indymedia.org/lwg.html

here's example of what i would write for what i'm working on currently,
if we agree on this protocol:

--------------------------------
* general project announcement *
--------------------------------

  name:        multiplacer.pl

  description: tool to help manage distributed serving
               (placing) of different media types:
               images, audio, video

  goals:       to be able to manage mirroring of uploaded files
               across multiple servers better that we can now

  measurable terms: to have it running and performing what it's 
               designed to do

  phases:      1. release on dev server (kropotkin) & put in CVS
	       2. test with dummy DB
               3. implement on stallman for a single IMC
               4. if ok with single IMC, implement further
  	       5. work with other code bases (active-sf, norway,
                  mir,IMCslash) to make it usable for them as well
     
  language:    Perl - Object Orientated

  time frame:   a year

  notice period: 2 months

--------------------------
* end example announcment *
--------------------------

-- on TWO-TIER system --

my basic idea is that we use above protocol FIRST.
before single tasks go into the RT (todo.indymedia.org)
this way we have two-tier system * email<>RT *

* email is used for anouncements and updates/summaries on status.

* RT is used for lower level work, for single tasks - dayTOday running

as well, this will allow us to have clear overview of current
projects within imc-tech (collection of emails with announcments)
and it's status (summaries/update emails).

if we go ahead and try this protocol, i would help to chris
coordinate imc-tech.

as an exaple: there were 3 projects already in tech meeting
2 weeks ago  that would be helped a lot by this kind of protocol: 
(since we know wo little about it since then, that's how projects
fail sometimes, through lack of coordination)

- deanna's features password separation
- thallara's proposal for globaly admined server
- deanna's idea to handle accounts on servers

let's talk more about it tonight while we're in the meeting.

later,

toni