Monthly Reports

Aloha, going through the approvals and re approvals it's evident some teams do use monthly reports to let their team and others know what they are up to, but a lot don't. Monthly reports are a really good habit to get into for all

Ubuntu Party Weekend…

… also known as Ubuntu Global Jam is coming up swiftly, so make sure you put 27th-29th August into your calendar and talk your local Ubuntu friends into participating. https://wiki.ubuntu.com/UbuntuGlobalJam Ok, so it’s Ubuntu Global Jam. What does that mean? What’s going to happen? Sim

Re: Monthly Reports

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 u

Re: Monthly Reports

On Tue, Jul 27, 2010 at 9:30 AM, Martin Owens wrote: > 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. Martin,

Re: Monthly Reports

On Tue, Jul 27, 2010 at 10:30 AM, 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 > netwo

Re: Monthly Reports

I'd also like that you keep in mind Martin that most teams are ot native english speaking. So I relly doubt that they will do a separate blog for filling the reports in nglish.. That would also be no fun... Christophe --- Christophe Sauthier   -  06 16 98 63 96 Objectif Libre  www.objectif-li

Re: Monthly Reports

Hi Martin, On 27 July 2010 15:30, Martin Owens wrote: > 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 completely agree that manual r

Re: Monthly Reports

On 27/07/10 15:30, Martin Owens wrote: > Dear LoCo Council, > > > 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. > > Regards, Martin Owens

Re: Monthly Reports

I believe the missing information in this conversation is "what happensto all these team reports?" do the wiki pages just sit there waiting forrandom readers to go hunting for them? Nop the reports are publish on the ubuntu weekly news letter at the end of the month. That way readers get inform

Re: Monthly Reports

Great reminder Laura. I usually get mine in, but a day or so late. Your reminder has prompted me to make July's report today -- I am ahead of schedule for the first time. Woot!! ~ cprofitt Laura Czajkowski wrote: > Aloha, going through the approvals and re approvals it's evident some

Re: Monthly Reports

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

Re: Monthly Reports

În data de Ma, 27-07-2010 la 09:36 -0500, Nathan Handler a scris: > On Tue, Jul 27, 2010 at 9:30 AM, Martin Owens wrote: > > 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

Re: Monthly Reports

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 wi

Re: Monthly Reports

I would love to see a single vehicle for announcing and after action reports for events (pictures, etc) that could also be leveraged for monthly team reports. It would certainly, due to format differences, need to be a well thought out data structure and application design. If it is possible to ma

Re: Monthly Reports

On Tue, 2010-07-27 at 16:12 +0100, Alan Pope wrote: > I completely agree that manual recurrent jobs are tedious. One > solution the UK loco has used is to delegate. We have a recurring item > on every meeting agenda which is used as a reminder to the team. No > one single individual is responsible

Re: Monthly Reports

> Having let's say an instance of status.net or a spider to fetch statuses > by hashtags, would be much easier compared to wiki edits. Our own instance, or a free community version of status.net is totally doable, btw. locoteams.status.net was set up as a test of this a while ago, but did not

Re: Monthly Reports

On Tue, Jul 27, 2010 at 8:04 PM, Greg Grossmeier wrote: > > >> Having let's say an instance of status.net or a spider to fetch statuses >> by hashtags, would be much easier compared to wiki edits. > > Our own instance, or a free community version of status.net is totally > doable, btw. locoteams.

Re: Monthly Reports

În data de Ma, 27-07-2010 la 20:04 -0400, Greg Grossmeier a scris: > > > > Having let's say an instance of status.net or a spider to fetch statuses > > by hashtags, would be much easier compared to wiki edits. > > Our own instance, or a free community version of status.net is totally > doable,

Re: Ubuntu Party Weekend…

Thanks. Vancouver is in. By the way, I've noticed that the Global Jam occurs fairly late in the dev cycle for bug fixes. Any thoughts about having it earlier next time round? Cheers, Randall Ubuntu Vancouver LoCo. -- Other ways to reach me: chat : rrnwe...@jabber.org sms : +16047713076 http:

Re: Ubuntu Party Weekend…

Am 28.07.2010 05:17, schrieb Randall Ross: > Thanks. Vancouver is in. Awesome! > By the way, I've noticed that the Global Jam occurs fairly late in the > dev cycle for bug fixes. Any thoughts about having it earlier next time > round? It's around Beta time which is awesome for testing and upgrad