Monthly Reports

[Jesper Jarlskov]

I agree with what I believe was the essence of Martin's initial post.
I don't believe that filling out the reports should be
automated/aggregated, but I really think that most of the
point'n'click'n'edit'n'save that goes on an awfull lot of times (at
least once per report made) of creating a new wiki page, and updating
archive lists and so on, would be possible to automate. It's a simple
repeated process, which is done in exactly the same way by a lot of
people.
It should be possible to make team reportings a "fill-in-the-blanks"
issue, instead of the current chore.

Jesper Jarlskov
Ubuntu-dk

On Tue, 2010-07-27 at 13:14 -0400, Martin Owens wrote:
> Hey Everyone,
> 
> Having had a thought about what I was trying to say and how it came
> across. I wanted to apologise, what I meant was for a constructive
> dialog on improving the situation and I'm aware that what I wrote was
> not a primer for that. Instead I feel I may have put communicated doubt
> in the good work of the loco council and it's members and that was not
> my intention.
> 
> Sorry.
> 
> On a more positive note, I think I could attend some of ideas directly
> to the loco directory and perhaps after consultation, give a way to
> report on events contextually.
> 
> Martin,
> 
> 
> On Tue, 2010-07-27 at 10:30 -0400, Martin Owens wrote:
> > Dear LoCo Council,
> > 
> > Monthly reports would be much better automatically generated by a
> > combination of the event organiser on the loco directory and a simple
> > blog system that did not have to be manually tied into the greater
> > blog
> > network of planets.
> > 
> > We fail at making things easy and instead insist upon the manual and
> > monotonous. A re-instance of monthly reports do not make them more
> > appealing, they make running a LoCo a chore rather than good fun.
> > 
> > I would rather have the LoCo council focusing on how to recruit and
> > organise developers effectively to put these problems to rest instead
> > of
> > focusing solely on social solutions.
> > 
> > Regards, Martin Owens
> > 
> > 
> 
>