Tools and templates for patch tracking

[Amit Kucheria]

Something the kernel team might be interested in.

Linaro is going to invest in creating tools to track what patches we carry,
why, their age, etc.

Regards,
Amit

----- Forwarded message from Michael Hope <michael.hope at linaro.org> -----

Date: Fri, 30 Jul 2010 15:44:14 +1200
From: Michael Hope <michael.hope at linaro.org>
To: linaro-dev at lists.linaro.org
Subject: Tools and templates

What tools and libraries should I use when writing
infrastructure-style projects?  Do we have a preferred technology
list?  Is there a style guide or standard templates that I can use?

This came about in writing a little web application for tracking the
changes in Linaro GCC vs upstream:
 http://ex.seabright.co.nz/patchtrack/

The code is at https://code.launchpad.net/~michaelh1/+junk/patchtrack.
 It uses web.py for the app engine, web.py's built-in template engine,
and a hacked up version of the wiki template.  I'd love to use tools
that somebody else knows as well though :)

Canonical have a preferred technology list but it's a bit heavy - zope
or django are an overkill for something like this.

Any thoughts?

-- Michael

_______________________________________________
linaro-dev mailing list
linaro-dev at lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

----- End forwarded message -----