Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Whiteboard design process
Some design issues are complicated and need a formal process.
1. Get idea or post bug report.
2. Send email about it to design@mail.com.
3. Weekly meeting: if design group approves - create whiteboard page. Set
status to Analysis.
For an idea to make it to the whiteboard it has to be complex enough to
reqiure reviewing, discussions lots of coffee. Just because something does
not make it to the whiteboard does not mean you should not work on it.
4. Work on idea by: clarifying the idea.
Post links to discussions/mockups/resouces on the whiteboard page.Do not
write analysis text and mockups directly to the whiteboard. Do that on your
own wiki-page or other web location.
5. Weekly meeting: If design group approves - Set status to "Call for
Proposals". Else discard idea and move whiteboard page to Archive.
6. Work on idea by: create proposal.
create a proposal and publish it on the whiteboard according to "Proposal
Template" (png with screenshot and link to description).
7. Weekly meeting: design group chooses a tentative design. Else discard
idea and move whiteboard page to Archive.
8. Work on idea by: refining the tentative design.
9. Weekly meeting: if design group agrees on final design, set status to
Blueprint. Else discard idea and move whiteboard page to Archive.
10. Work on idea by: defining a blueprint for a programmer.
11. Weekly meeting: design group agrees on blueprint quality and moves
whiteboard from whiteboards tab to Blueprints tab. Else discard idea and
move whiteboard page to Archive.
12. Wait for programmer to implement. When this happens move whiteboard to
Implementation in Progress.
  When programmer has completed task then set status to Implemented and
move Whiteboard to "Implemented".

Suggestions
§1 Add a reviewed version of the list above to the whiteboard page.
§2 Waiting to be adressed -> Abandoned whiteboards "Whiteboards which have
been archived due to lack of attention and interest".
§3 Implemented -> Implemented Whiteboards
§4 Abandoned -> Discarded whiteboards
§5 Proposed GoSoC -> Suggested Google Summer of Code projects
§6 Proposed easyhacks -> Design related Easyhacks
§7 Development blueprints -> Blueprints for developers
§8 Waiting Que -> Blueprints ready for implementation
§9 Implementation in progress -> Blueprints under implementation
§10 Add a tab to the menu row for the "Archive" page.


2013/7/2 Oskar Olsson <osol84@gmail.com>

As a newcomer I've been a little confused about how the work is done. Here
is a outline of the whiteboard process as I understand it as well as some
suggestions for improvments:



-- 
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.