RE: [Pyatcron-devel-list] Plugins and classes

[Childers, Matthew]

> -----Original Message-----
> From: Julien Olivier [mailto:address@hidden
> Sent: Thursday, November 27, 2003 3:58 AM
> To: address@hidden
> Subject: RE: [Pyatcron-devel-list] Plugins and classes
> 
> > All, this demonstrate that before coding we should document what to
do.
> In software development project, coding represent 20% of the time, not
> more. And 40% is spent on documeting (requirements, specs, class
> definitions). The rest is reserved for testing and packaging.
> >
> 
> Of course you're right.
> 
> > So, what I would really suggest is spend some time on the PyAtCron
> documentation first. I'm currentl working on documenting Cron and At
> daemon to understand how they work and what could be the issues for
our
> project. Someone should document the class definitions (name, fields,
> methods) and what they are expected to do. This would avoid questions
like
> Brain has.
> > If nobody wants to take over this job, then I'll do it ;-)
> >
> 
> I think you're the best for that. At least, you seem better than me
for
> that sort of tasks. I replied to Brian in an email about the plugin
> architecture. Maybe you could use my answer to write a better
> documentation ?
> 

I don't mind doing it (if you all don't mind correcting my mistakes), I
was planning on doing it this week, but with Thanksgiving and all, I got
a little busy.  I will try and start on it by Tuesday or Wednesday, but
I have one question.  Are we using DocBook for documentation?  I have
never used it before, so I will have to get familiar with it first.

Thanks,
Matt


> --
> Julien Olivier <address@hidden>
> 
> 
> _______________________________________________
> Pyatcron-devel-list mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/pyatcron-devel-list