I haven't gone and read those links yet and maybe the answer is there,
but I would be interested to hear about how interaction/user-
experience design can be worked into the open-source model.
I can't help feeling I'm being naive here, but the checking in and out
of code, branching and patching and the control of that process seems
to suit code way more than it does, say, wireframes or design concepts.
The latter are, by their nature, rougher than finished code would be,
yet would need to go through a typical open-source process of being
added to the 'build' in some way and good ideas, or too rough ideas
might get killed off in the process.
How have people gone about this workflow and process in existing open-
source projects? The Yahoo! pattern library process seems like it
could be a good model: http://tinyurl.com/by4bq
Best,
Andy
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Andy Polaine
Interaction & Experience Design
Research | Writing | Education
Twitter: apolaine
Skype: apolaine
http://playpen.polaine.com
http://www.designersreviewofbooks.com
http://www.omnium.net.au
http://www.antirom.com
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
