db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <Ken.C...@Golux.Com>
Subject Re: Podling status report
Date Wed, 22 Jun 2005 08:49:15 GMT

Jean T. Anderson wrote:

> Who should prepare this report -- you :-) ? and by when?

The developers should prepare it.  Each project provides a
report to the board quarterly, so at the very least the habit
should be formed of rolling things up every three months.  If
the habit is made of doing it monthly, then all that's necessary
when the report comes due is to hand over the current contents
and empty the file to start for the next cycle.  For this I'm
envisioning a cumulative file in which accomplishments are
collected and challenges/problems/issues are listed (until they
are addressed, at which point they get removed).

The report should probably be kept in svn so multiple people can
contribute to it.  The STATUS file is a good place to collect the
salient points.

As for when..  Reports are due a few days before the board meeting
so the directors have a chance to read them.  While Derby is in the
incubator, Noel will give a few days notice (on general@i.a.o) so
the podlings can give *him* their reports so he can roll them up
into the incubator report.

If the report file is maintained on a pretty regular basis, then
very little work should be necessary when the 'reports due in a
few days' alert comes out.
- --
#ken	P-)}

Ken Coar, Sanagendamgagwedweinini  http://Ken.Coar.Org/
Author, developer, opinionist      http://Apache-Server.Com/

"Millennium hand and shrimp!"
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


View raw message