Beyond Sharing: Open Source Design

1,470 views

Published on

Graphic and interaction design are two fields critical to software development that — unlike code have — have not yet nourished a successful collaboration model. What can we learn from the Wordpress community’s latest attempts to involve designers in the open source process? Can we simply apply the same collaboration methods from code to design? And what other examples and models are available for us to borrow from? What are the challenges of networked collaboration in the creative process? Can they and how might they be solved? Or is it just that designers don’t like to work together? Mushon will be presenting and leading a discussion on the subject with examples from the Wordpress community, his own work, and the research done in his Open Source Design class taught in Parsons’ AAS Program in Graphic Design. Speaker: Mushon Zer-Aviv.
More on http://mushon.com

Published in: Design, Technology
  • Be the first to comment

  • Be the first to like this

Beyond Sharing: Open Source Design

  1. 1. Hi, I’m Mushon @Mushon.com Nov 09
  2. 2. Shual.com @Mushon.com Oct 09
  3. 3. Beyond Sharing: “Open Source Design” Wordcamp NYC 2009 @Mushon.com Nov 09
  4. 4. Open source is great! But does it really exist beyond code?
  5. 5. -
  6. 6. -
  7. 7. -
  8. 8. -
  9. 9. e happe ns here Ope n Sourc } -
  10. 10. 1. Getting on the Wagon
  11. 11. 1. Getting on the Wagon • OS motivation - personal interest in (and low costs for) collaboration
  12. 12. 1. Getting on the Wagon • OS motivation - personal interest in (and low costs for) collaboration • OSD motivation - not so straight-forward
  13. 13. 1. Getting on the Wagon • OS motivation - personal interest in (and low costs for) collaboration • OSD motivation - not so straight-forward • Chicken & Egg - Designers don’t use OSS
  14. 14. 2. Granularity
  15. 15. 2. Granularity • In coding (software) and writing (wikis) the building block is granular - a character
  16. 16. 2. Granularity • In coding (software) and writing (wikis) the building block is granular - a character • Allows for varied contribution:
  17. 17. 2. Granularity • In coding (software) and writing (wikis) the building block is granular - a character • Allows for varied contribution: • Accessible ladder of contribution
  18. 18. 2. Granularity • In coding (software) and writing (wikis) the building block is granular - a character • Allows for varied contribution: • Accessible ladder of contribution • History
  19. 19. 2. Granularity • In coding (software) and writing (wikis) the building block is granular - a character • Allows for varied contribution: • Accessible ladder of contribution • History • Moderation
  20. 20. 2. Granularity • In coding (software) and writing (wikis) the building block is granular - a character • Allows for varied contribution: • Accessible ladder of contribution • History • Moderation • Transparency
  21. 21. 3. Language Encoding/Decoding Stuart Hall 1980
  22. 22. Encoding framework of knowledge A
  23. 23. Mutual Language
  24. 24. framework Decoding of knowledge B
  25. 25. Encoding A A Decoding
  26. 26. Encoding B A ERROR Decoding
  27. 27. A A A
  28. 28. A A A A A
  29. 29. Encoding
  30. 30. Encoding • Defining a language (code) is key in design (graphic, color, layout, animation, interaction...)
  31. 31. Encoding • Defining a language (code) is key in design (graphic, color, layout, animation, interaction...) • Coding without a shared language (code) is impossible
  32. 32. Encoding • Defining a language (code) is key in design (graphic, color, layout, animation, interaction...) • Coding without a shared language (code) is impossible • Setting collaboration standards is essential
  33. 33. Encoding • Defining a language (code) is key in design (graphic, color, layout, animation, interaction...) • Coding without a shared language (code) is impossible • Setting collaboration standards is essential • Standardization VS. Innovation
  34. 34. Decoding
  35. 35. Decoding • Code either executes or it doesn’t, but a message interpretation isn’t binary
  36. 36. Decoding • Code either executes or it doesn’t, but a message interpretation isn’t binary • Inconsistent design fragments the message (our brains can’t really multitask)
  37. 37. Decoding • Code either executes or it doesn’t, but a message interpretation isn’t binary • Inconsistent design fragments the message (our brains can’t really multitask) • Wikipedia’s has a largely rational guidelines for decision making, design’s doesn’t
  38. 38. So is it simply undoable? (would I be wasting your time if I thought so?)
  39. 39. Resource sharing / Open Culture
  40. 40. Wordpress 2.5 admin by HappyCog Wordpress 2.7 Modified by the Wordpress team
  41. 41. Fixing it: 1. Getting on the Wagon
  42. 42. Fixing it: 1. Getting on the Wagon • Price is always itching, but it’s not enough
  43. 43. Fixing it: 1. Getting on the Wagon • Price is always itching, but it’s not enough • We can’t force the use of bad tools as an ideologic statement
  44. 44. Fixing it: 1. Getting on the Wagon • Price is always itching, but it’s not enough • We can’t force the use of bad tools as an ideologic statement • Some success in webdesign / Wordpress
  45. 45. Fixing it: 1. Getting on the Wagon • Price is always itching, but it’s not enough • We can’t force the use of bad tools as an ideologic statement • Some success in webdesign / Wordpress • Still very code-based
  46. 46. Fixing it: 2. Granularity
  47. 47. Fixing it: 2. Granularity • When possible, use granular building blocks - namely: use code
  48. 48. Fixing it: 2. Granularity • When possible, use granular building blocks - namely: use code • Get designers on version control systems
  49. 49. Fixing it: 2. Granularity • When possible, use granular building blocks - namely: use code • Get designers on version control systems • Put all master files online
  50. 50. Fixing it: 2. Granularity • When possible, use granular building blocks - namely: use code • Get designers on version control systems • Put all master files online • Explore file non-code versioning (Dropbox?, Alienbrain?)
  51. 51. Fixing it: 3. Language
  52. 52. Fixing it: 3. Language Collaborative Encoding:
  53. 53. Fixing it: 3. Language Collaborative Encoding: • 1st step: Conduct a networked research (we already have collaborative tools for that)
  54. 54. Fixing it: 3. Language Collaborative Encoding: • 1st step: Conduct a networked research (we already have collaborative tools for that) • 2nd step: Define a modular and extensible language * Support simple inheritance (like in CSS)
  55. 55. Fixing it: 3. Language Collaborative Encoding: • 1st step: Conduct a networked research (we already have collaborative tools for that) • 2nd step: Define a modular and extensible language * Support simple inheritance (like in CSS) • 3rd step: Document the language (style guides)
  56. 56. Fixing it: 3. Language
  57. 57. Fixing it: 3. Language Collaborative Decoding:
  58. 58. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational, and can achieve consensus, like:
  59. 59. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational, and can achieve consensus, like: • UX research
  60. 60. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational, and can achieve consensus, like: • UX research • Technical aspects of design
  61. 61. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational, and can achieve consensus, like: • UX research • Technical aspects of design • Design best practices (in typography, use of icons, interaction paradigms...)
  62. 62. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational, and can achieve consensus, like: • UX research • Technical aspects of design • Design best practices (in typography, use of icons, interaction paradigms...) • Blogs share resources and documentation
  63. 63. -
  64. 64. A nuanced analysis of OS: Openness + Leadership -
  65. 65. We can’t just sprinkle design with the magic pixie dust of “Open Source”
  66. 66. Collaboration is hard! Let’s make it easier. Suggestions?
  67. 67. @Mushon.com Nov 09

×