On 9 February 2011 13:51, Yuval Levy <[email protected]> wrote: > On February 9, 2011 07:00:45 am Lukáš Jirkovský wrote: >> from the descriptions when registering new blueprint it >> seems to me that it's supposed only to be a list of proposed ideas >> with short description of each. > > Yes. The entry there is a summary of the use case, relatively immutable. Not > the place to work on the specs. > > The field "specs URL" points to a wiki page where others can collaborate with > you on the specs. > > >> Should I add the complete proposal to >> blueprint summary no mater what is in it's description or should I >> rather create a page in panotools wiki with more detailed description >> and link to it? > > I would suggest you articulate the (immutable) idea in the Summary, leaving > the details for a linked wiki page where others can add their ideas to yours > in the detailed specs. > > When the specs have achieved a milestone update the Whiteboard of the > Blueprint (not visible on registration, but visible and editable on the > blueprint's page itself). See an example at [0]. > > If I understand you correctly, you have already an initial specs. Very good. > Put it on the Whiteboard, so that it shows that the Blueprint is at a more > advanced staged than the simple idea. > > The wiki is for drafting, the Whiteboard is for approving. You will approve > into your Whiteboard specs only those suggestions from the wiki that make > sense to you. > > Here are some links to excellent specs [1]. All in wikis, but if you wrote > yours as a set of screen mockups in Inkscape or present them as a youtube > video, feel free to link that instead. > > And here is a good text on how to write good specs [2]. > > HTH > Yuv > > [0] https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-gnome > [1] https://help.launchpad.net/GreatSpecifications > [2] https://help.launchpad.net/WritingGoodSpecifications >
Hi Yuv, Thank you for giving me insight into how blueprints are used. For now I've registered blueprint [1] and a wiki page [2] with complete proposal. The proposal is open for suggestions. I already included some from the hugin-ptx thread referenced in the wiki page. If nobody objects I'd like to add a link to the http://wiki.panotools.org/GSOC_2011 Lukas [1] https://blueprints.launchpad.net/hugin/+spec/straight-line-ui [2] http://wiki.panotools.org/Straight_Line_UI_proposal -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
