Hi all,
Paul and I are meeting on Tuesday, May 5 @ 3:00 pm PST to decide what
aspects of the List Reorderer design we'd like to see make it into the
component at some point. From there, we'll create jiras based on the
current storycards that can later be prioritized as time and interest
permits. The storycards represent gaps between what is on build and
what is in the design now so this exercise will likely be a gut check
of them.
References:
List Reorderer on build:
http://build.fluidproject.org/infusion/standalone-demos/quick-start-examples/reorderer/html/Reorderer.html
Wireframes of current design thinking:
http://wiki.fluidproject.org/display/fluid/List+Reorderer+Wireframes
Storycards:
http://wiki.fluidproject.org/display/fluid/List+Reorderer+Storycards
We'd love to have you join us if you're interested!
- Daphne
Begin forwarded message:
From: Paul Zablosky <[email protected]>
Date: March 16, 2009 9:36:14 AM PDT
To: Daphne Ogle <[email protected]>
Cc: Fluid Work <[email protected]>
Subject: Re: List Reorderer storyboard walkthrough
Hi Daphne,
Sounds great. I'd like to participate. Paul
Daphne Ogle wrote:
Great! Are there any volunteers interested in walking through the
List Reorderer storyboard with me to finalize which aspects belong
in the component and which we just want to show as a customization?
-Daphne
On Mar 13, 2009, at 6:23 AM, Anastasia Cheetham wrote:
On 12-Mar-09, at 2:57 PM, Daphne Ogle wrote:
I .. came up with some additional design enhancements that could
be made to the list reorderer component: http://wiki.fluidproject.org/display/fluid/List+Reorderer+Wireframes
.
I believe those enhancements would be considered "Carrot
enhancements" for post March since the core team is already
booked for the 1.0 release. Has there been any thought as to how
we identify these yummy carrots? Perhaps we just need a
dashboard-style confluence page that lists and briefly describes
these carrots? Actually, how about adding them to the "Current
needs" page, http://wiki.fluidproject.org/display/fluid/Current+Needs?
A first step is to file JIRA tasks for the specific work to be
done, but you raise the excellent question of how do we foster
more active contributions from the wider community?
It think the Current Needs wiki page is a probably a good start.
Right now, it looks a bit sparse, and has an "Under Construction"
warning that would probably deter people. I think it's time we put
a bit of effort into this page, make it more inviting. We could
also link directly to its parent "Get Involved" page from the
website.
What do other people think?
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[email protected]
cell (510)847-0308
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[email protected]
cell (510)847-0308
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
