On 24 May 2011 15:21, Alexandros Frantzis <alexandros.frant...@linaro.org> wrote: > in some of the blueprints I am following, I have noticed that many work > items updates (e.g. to DONE/POSTPONED/BLOCKED) are not accompanied by > any additional information. Of course, not all work items need > more information, but some are meaningless to an external viewer > without it.
Perhaps we could improve the tools to encourage this/make it easier? For instance, the work item format could be improved to let you add accompanying commentary to items rather than insisting on a strict one-line-only approach. As you say, you can add stuff at the top of the whiteboard, but that gets a bit messy and hard to cross-reference. If work items were officially supported as a launchpad/blueprint feature then you could design the UI to encourage the addition of a little commentary when a work item is ticked off. Proper support for named and timestamped comments (like bug reports have) might also help. > In conclusion, I would like to encourage more verbosity in our updates, > so that others can easily follow and appreciate all the great work that > we are doing. Do many people find blueprints a useful method for following the detailed progress of a feature? (as opposed to general "65% complete" level progress tracking.) I have to say if I wanted to find out the current status of something I'd use IRC or email, as being much more likely to actually get me an answer that's usefully detailed and focused on the particular aspect I care about (and with forward-looking info like "we think we'll get that done next week"). -- PMM _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
