Re: Status Reports

["Viron, Michael" <mviron@wsdo.sao.uwf.edu>]

I've started very early conversion of the existing pages on devel to the
new format that I proposed.  This week, I plan to finalize the e-mail to
send to potential developers for the devel site.  The devel site, although
not critical to go-live, facilitates the perusal of documentation (by
developers) concerning the LinuxKB project.  "Quality Open Source Sites
need quality documentation."

Towards the goal of adding developers to the "Internal Documentation
Development" Project, I've invited Chris Ayers to work with me--I hope to
bring additional developers on board this week (initial plans were to do so
over the weekend--explaination follows below).

As most of you probably know by now, Wal*Mart decided to let me go, as I
couldn't increase my availability to meet their needs.  That's fine--it'll
allow me to pursue jobs in my field in the local area as a part-time employee.

Questions, comments, or suggestions are always welcome,

Michael Viron
Project Coordinator, Internal Documentation Development
Linux Knowledge Base Organization
http://devel.linuxkb.org    http://linuxkb.sao.uwf.edu

At 09:29 PM 11/02/1999 -0500, you wrote:
>I've discussed this before with different people at different times on
#seul.  We all
>have different opinions, but I think it's time to say we need to start
doing this.
>
>It's pretty tough for me, as fearless leader of the project, to do any
kind of
>coordination of efforts with the severe lack of communication going on
between our
>developers.  This is not any one person's fault... it's just the way this
project has
>gone - we're all partly to blame, including myself.  When I get to doing
something... I
>usually don't talk about it until it's done.  
>
>While that's a good marketing practice... and perhaps M$ could learn a
thing or two from
>us... it's really not a good practice for us as developers to get into.
Communication
>between members of this team is crucial.
>
>So to facilitate that, enough of us have agreed that we need some kind of
formal reports
>of status.  In no way is this meant to replace endless banter of issues on
the list at
>all times day and night... it is simply meant to facilitate it - as well
as give me the
>information I need on a regular basis, in a single email, to understand
what each
>developr is doing, and what they need to keep doing what they are doing.  
>
>Popular opinion has deemed every two weeks would be good.  I think this is
a great
>idea... and we'll move towards that... but for the next month, I am
pushing for weekly
>status reports.  We've all expressed the desire to have something by
year's end.  That
>isn't too far off.  Weekly reports will get us moving... at least those of
us serious
>about this project.
>
>If yopu haven't done anything, your status report will simply read: "I've
done Nothing".
>And then your welcome to provide some type of explanation if it will make
yourself feel
>better.  :).
>
>Seriously though... I don't think it's too harsh to say that if we get too
many of those
>types of mails in a row, we will no longer consider you a serious
developer... and will
>be making important decisions with or without your input.
>
>I'll be adament (sp) about getting my reports in at twice the normal rate.
 It's gotta
>happen.  Our sponsers and supporters will not go on forever seeing no
results.  So lets
>go.  Aaron and I are on IRC almost all the time, just waiting for
questions to roll in.
>I probe email on a VERY regular basis.  If something needs done, or you
need a feature...
>I WILL drop what I'm doing to fulfill your need if it warrants.
>
>Let the banter begin. 
>
>-- 
>Jason
>http://vodka.linuxkb.org/~chardros
>