Automating Team Reports (was Re: Coming up with another term for Approved LoCo Teams - Discussion)
Craig Maloney
craig at decafbad.net
Fri Feb 8 21:56:03 UTC 2013
On 02/08/2013 04:26 PM, Elizabeth Krumbach wrote:
>
> I would really like to see this too, the current bug to add this
> functionality is here:
>
> https://bugs.launchpad.net/loco-team-portal/+bug/605651
I'm familiar with this ticket. I'm not sure how it relates with a
currently established process of generating redundant reports in a wiki?
I think surfacing statistics in a nice graphical way would be awesome,
but I think there's a procedural change that can be made now without
waiting on a feature enhancement.
>
> Unfortunately community member Adnane Belmadiaf is pretty much the
> sole developer of the LTP at this point and while he does have another
> release on the horizon (yay!) it doesn't handle a large number of
> wishlist items. He's mostly working hard on bug fixes and other things
> essential to keeping it running well.
No doubt. The work on the LTP has been amazing.
>
> So as a completely community-driven effort, I would encourage people
> who would like to see this functionality to reach out to their teams
> to see if there is anyone with Django skills and time to assist Adnane
> in this work. I wrote a blog post a few months back about how to get a
> development environment set up in a VM:
> http://princessleia.com/journal/?p=6662 (and folks in #ubuntu-website
> can help if there is anything about these instructions that are
> out-dated).
Again, I'd like to know why this bug in particular is keeping us from
being more efficient in our team reporting? Are we throwing technology
at something that can be solved procedurally?
--
--------------------------------------------------------------------
Craig Maloney (craig at decafbad.net) http://decafbad.net
"Work hard, rock hard, eat hard, sleep hard, grow big,
wear glasses if you need 'em." -- The Webb Wilder Credo
More information about the loco-contacts
mailing list