On Mon, Sep 27, 2010 at 09:28:45PM +0100, Jamie Bennett wrote:
Sure. The pillar name is passed in when calling the script so could be any project. Getting a list of these projects is a good idea but will need to be maintained.
Here's a stab at a first set:
* ubuntu * linaro * linaro-toolchain * linaro-toolchain-wg * linaro-kernel * linaro-kernel-wg * linaro-middleware-wg * linaro-pm-wg * linaro-seeds * linaro-image-configs * linaro-image-tools
I think there are a bunch missing here that are related to infrastructure.
I can just keep these in the description for the Linaro project. Do you think that's sensible enough?
BTW, should we be somehow merging linaro-toolchain-wg and linaro-toolchain? Same for the kernel projects? One of each seem to be stubs just holding blueprints anyway, right
BTW2: Should we create a linaro-tools or linaro-infrastructure group that we use to collect our various projects and include -seeds, -image-configs and -image-tools there?
I have another script called from a cron job which just calls 'bug-track ubuntu' and 'bug-track linaro', this of course could be anything. Currently each project is presented separately on the wiki page but I could combine that information.
Yeah, I think you should combine it into a single list. You could optionally present the projects affected as a list similar to your tags list -- but it may be irrelevant and just narrow the columns out unnecessarily.