$30 off During Our Annual Pro Sale. View Details »

Designing Your Open Source Project (DjangoCon)

Bryan Veloso
September 04, 2012

Designing Your Open Source Project (DjangoCon)

There is an ever present rift between designers and developers and it is one that has existed since our paths started crossing. While it has almost become a requirement for designers to be able to grok the code they work with on a daily basis, that has unfortunately had no effect on the willingness of designers to work on open source projects.

Fortunately, if your project is in need of a designer, there are ways that you can make your project more appealing to our “special breed” of personality. In this quick talk, we’ll jump into the mind of your typical designer, show you just how many similarities we share and then apply that knowledge to make your project easy and appealing for designers to jump into.

Bryan Veloso

September 04, 2012
Tweet

More Decks by Bryan Veloso

Other Decks in Design

Transcript

  1. designopen source project
    your
    DjangoCon United States • September , Presented by Bryan Veloso.

    View Slide

  2. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    so, let’s begin.

    View Slide

  3. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    potentially abrasive & unforgiving.

    View Slide

  4. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    the problem.
    step : denial.

    View Slide

  5. @bryanveloso
    you have an amazing oss project.
    the problem.
    http://thelastshuttle.com

    View Slide

  6. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    but you need a designer.
    the problem.

    View Slide

  7. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    the “real” problem.
    hubot image me trollface

    View Slide

  8. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    designers are picky.
    the real problem.

    View Slide

  9. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    designers are stubborn.
    the real problem.

    View Slide

  10. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    designers have no time.
    NO TIME TO EXPLAIN. GET IN THE TRUCK.
    the real problem.

    View Slide

  11. @bryanveloso
    designers are just like you.
    http://flickr.com/photos/peterjlambert/ /
    the real problem.

    View Slide

  12. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    the real problem.

    View Slide

  13. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.

    View Slide

  14. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    srsly guys... let me explain myself.

    View Slide

  15. @bryanveloso
    first, time to hug it out.
    http://flickr.com/photos/meesterdickey/ /

    View Slide

  16. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    we’re really quite similar.
    neckbeardcat.

    View Slide

  17. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    the pursuit of perfection.™
    designers: pixel perfection.
    developers: pep .
    we’re really quite similar.

    View Slide

  18. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    ""
    This is the "example" module.
    The example module supplies one function, factorial(). For example
    >>> factorial(5)
    120
    """
    respecting clarity.
    designers: clarity through user interface.
    developers: clarity through documentation.
    we’re really quite similar.

    View Slide

  19. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    designers: a designer’s ability to code.
    developers: nosql.
    useless bickering.
    inb4
    we’re really quite similar.

    View Slide

  20. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    general misunderstandings.
    we’re really quite similar.
    designers-to-developers: “make it work.”
    developers-to-designers: “make it pretty.”

    View Slide

  21. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    we’re really quite similar.
    developers-to-designers: “make it pretty.”
    ಠ_ಠ

    View Slide

  22. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    we’re really quite similar.
    developers-to-designers: “make it pretty.”
    ಠ_ಠ

    View Slide

  23. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    recruiting a designer.
    “draw me like your french girls.”

    View Slide

  24. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    from cloud import designer
    recruiting a designer.

    View Slide

  25. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    requirements in your README.
    recruiting a designer.

    View Slide

  26. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    find us on dribbble.
    recruiting a designer.

    View Slide

  27. @bryanveloso
    the hallway track.
    recruiting a designer.
    Photo by @zerok.

    View Slide

  28. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    pitch to us.
    recruiting a designer.

    View Slide

  29. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    bryanveloso: you super busy over the next few months?
    I really want to start working on pythonforhumans.org
    and i'd LOVE to have you help with the design, if you have the time :)
    it'll be a really simple site
    but i want it to set a standard
    ruby-level design :)
    ARE YOU UP FOR THE CHALLENGE
    i'll harass idan too
    recruiting a designer.

    View Slide

  30. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    recruiting a designer.
    bryanveloso: you super busy over the next few months?
    I really want to start working on pythonforhumans.org
    and i'd LOVE to have you help with the design, if you have the time :)
    it'll be a really simple site
    but i want it to set a standard
    ruby-level design :)
    ARE YOU UP FOR THE CHALLENGE
    i'll harass idan too
    pretty good pitch.

    View Slide

  31. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    recruiting a designer.
    bryanveloso: you super busy over the next few months?
    I really want to start working on pythonforhumans.org
    and i'd LOVE to have you help with the design, if you have the time :)
    it'll be a really simple site
    but i want it to set a standard
    ruby-level design :)
    ARE YOU UP FOR THE CHALLENGE
    i'll harass idan too ಠ_ಠ

    View Slide

  32. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.

    View Slide

  33. @bryanveloso
    Photo by @kennethreitz.

    View Slide

  34. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.

    View Slide

  35. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    to my fellow designers.
    recruiting a designer.

    View Slide

  36. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    open source is experiential.
    recruiting a designer.

    View Slide

  37. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    open source is long lasting.
    recruiting a designer.

    View Slide

  38. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    open source is crucial.
    recruiting a designer.

    View Slide

  39. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    make yourself known.
    recruiting a designer.

    View Slide

  40. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    so, hybrids.
    PSDs/liter of beer.

    View Slide

  41. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    i know a lot
    about python.
    i know a lot
    about design.
    ^_^;

    View Slide

  42. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    i don’t care
    much about design.
    i don’t care much
    about development.
    o_o;

    View Slide

  43. @bryanveloso
    the universal translators™.
    so, hybrids.
    http://johnmartz.com/

    View Slide

  44. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    knowledge exchanges.
    so, hybrids.

    View Slide

  45. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    find hybrids.
    so, hybrids.

    View Slide

  46. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    train hybrids.
    so, hybrids.

    View Slide

  47. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    learn from hybrids.
    so, hybrids.

    View Slide

  48. @bryanveloso
    pair with us.
    http://weilu.github.com/reddot /#
    so, hybrids.

    View Slide

  49. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    help us replicate.
    so, hybrids.

    View Slide

  50. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    working with designers.
    “make it pretty?” did you just tell me to go @$*! myself?

    View Slide

  51. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    time investment.
    working with designers.

    View Slide

  52. @bryanveloso
    space.
    working with designers.
    http://johnmartz.com/

    View Slide

  53. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    restriction & boundaries.
    working with designers.

    View Slide

  54. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    respect.
    working with designers.

    View Slide

  55. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    working with designers.
    death to spec work.

    View Slide

  56. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.

    View Slide

  57. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    working with designers.
    This  takes
    work.
    You,
    developer.

    View Slide

  58. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    where’s django in all of this?
    inb the pony joke.

    View Slide

  59. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    where’s django in all of this?
    ponies!

    View Slide

  60. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    fostering a community of...
    where’s django in all of this?

    View Slide

  61. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    respect.
    where’s django in all of this?

    View Slide

  62. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    shared purpose.
    where’s django in all of this?

    View Slide

  63. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    but django already does this.
    where’s django in all of this?

    View Slide

  64. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    four words.
    where’s django in all of this?

    View Slide

  65. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    benevolent designer for life.
    where’s django in all of this?

    View Slide

  66. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    idan gazit.
    @idangazit
    where’s django in all of this?

    View Slide

  67. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    where’s django in all of this?
    design matters to django.

    View Slide

  68. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    where’s django in all of this?
    designers should matter to you.

    View Slide

  69. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    your moment of zen.
    epic whitespace time.

    View Slide

  70. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    this may be heavy-handed.
    your moment of zen.

    View Slide

  71. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    the opinion of one designer.
    your moment of zen.

    View Slide

  72. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    your mileage may vary.
    your moment of zen.

    View Slide

  73. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    distill where needed.
    your moment of zen.

    View Slide

  74. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    how to perpetuate?
    your moment of zen.

    View Slide

  75. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    your  users.
    you.
    your moment of zen.

    View Slide

  76. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    together we can make the web...
    your moment of zen.

    View Slide

  77. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    your moment of zen.

    View Slide

  78. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    do we still have time?

    View Slide

  79. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    hi, i’m bryan.

    View Slide

  80. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    designer + developer = hybrid.

    View Slide

  81. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    i help maintain django-imagekit.

    View Slide

  82. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    father of the django pony.

    View Slide

  83. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.

    View Slide

  84. @bryanveloso
    for the benefit of those who like to sit in the back row,
    i’ve refrained from putting anything important here.
    facebook.com/bryanveloso
    twitter.com/bryanveloso
    github.com/bryanveloso
    twitch.tv/vlogalonstar
    and if you’re into gaming...

    View Slide

  85. designopen source project
    your
    DjangoCon United States • September , Presented by Bryan Veloso.

    View Slide