Working on reporting, working on conference representation
Thu, 08-Dec-2005 by
Richard Dice
edit post
<![CDATA[
One of the things we're trying to improve over here is reporting. Not only do People Want To Know what it is that we're doing, but being a not-for-profit we have some regulatory needs to get our reporting act together. Over the past week I've been working on the reporting strategy for the Steering Committee.
Progress has been made on this front. I've created a draft reporting template that seems to have general acceptance within the Steering Committee and at the level of the Board. (I.e. the SC members seem happy to use it, and the Board people seem happy to accept it.) In case you're curious, here it is: <a href=http://news.perlfoundation.org/tpf_steering_committee_draft_2_report_template.pdf>http://news.perlfoundation.org/tpf_steering_committee_draft_2_report_template.pdf</a>
Something very like this will be used. We've also gotten a general agreement on the time-frame for this report. Dec. 31/2005 is the last day of the "current" reporting period (which goes back to... well, time immemorial in theory but probably 6 months in practice). On Jan. 1/2006 I will email the SC to ask people to start putting together their reports. I expect to receive completed reporting chunks from each working group head as of Jan. 15/2006. I then give myself 2 weeks to collate-and-otherwise-synthesize a finished report from that. So, the report will be ready for Jan. 28/2006.
The other thing that has my major attention right now is working on a policy regarding TPF representation conferences: which conferences we should send an "official" representative to, how to choose the right representative, and what he/she will do when there. There has been a lot of discussion on the SC mailing list on this point so fortunately I don't feel like I have to do all that much hard thinking along these lines. Mainly, I'll (once again) be synthesizing what so many of my SC colleagues have already said so well. I was hoping to have this out earlier this week, but now I'm looking more at, well, later this week.
]]>
Comments (0)
