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 make both the LoCo Council's job easy to track teams and the team's job to advertise and report on its activities it is a worthy target to pursue. I agree with doctormo and nhandler, so the question is how to bridge the issues and meet both. cprofitt On Tue, 2010-07-27 at 09:36 -0500, Nathan Handler wrote: > On Tue, Jul 27, 2010 at 9:30 AM, Martin Owens <docto...@gmail.com> 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, > > I agree that this would make them easier, and that currently they are > not the most enjoyable thing to do. However, your proposed method > would not work for most teams. For example, how would it know that we > has been discussed/planned/agreed on/announced via the mailing list? > How would it know what happens at IRC meetings? Blog posts also tend > to be rather long/lengthy. The Team Reports are generally just a few > bullets. Daniel Holbach had started working on a Django application > that would make it easier to construct the reports (however, it would > still be up to the teams to remember the events and write bullets > about them), but that appears to have stalled for various reasons. So > while I agree that we should make the process as easy as possible, I > do not think that this is the best way to go about doing so. > > Nathan > -- loco-contacts mailing list loco-contacts@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/loco-contacts
