On Mon, Oct 1, 2012 at 10:08 AM, Alexander Sack <[email protected]> wrote: > +1 for killing the status.linaro.org external use-case (we still may > need it to map cards to blueprints for internal convenience use) > > So: > * let's internalize status.linaro.org by making it > cards2blueprints.linaro.org without a redirect > * ensure we have have sharp monthly reports that reflect reality for > TSC/mgmt/stakeholders
Would this monthly reports be based on the output of this new cards2blueprints.l.o? If so, that would basically mean we'd need try to keep the system updated again. Ideally I'd also like to see it working as an easy way to find out what is happening across the organization, but the reality proved otherwise. >From a tech lead point of view, we just got too many reports and places to put status, and before moving this forward we'd probably want to clean that up as well. One example from my side: - Weekly update at blueprints - Weekly update for cards - Release specific updates (highlights) - Post-mortem updates - Platform monthly report (mostly the same release highlights) - Engineering exec report (highlights and future work) Besides the normal monthly planning and engineering :-) It seems it'd make sense if we could mostly shift entirely to cards directly, and use blueprints to track work not directly involved there. From the weekly cards update, we could mostly automatically generated all the other reports. Cheers, -- Ricardo Salveti de Araujo _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
