Redesigning the Drupal Issue Queue (Codename Prairie: a Social Architecture Project)

  • 3,223 views
Uploaded on

Looking at the architecture of participation and our collaboration tools on Drupal.org

Looking at the architecture of participation and our collaboration tools on Drupal.org

More in: Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,223
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
1
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Redesigning the Issue QueueLeisa Reichelt, Randy Fay
  • 2. as you are, so are your buildings;and as your buildings are, so are you Louis H Sullivan ‘father of skyscrapers’
  • 3. ‘The behavior you’re seeing is the behavior you’ve designed for’ Joshua Porterhttp://www.flickr.com/photos/jesper
  • 4. designing for behaviour as a firstclass object... change the context and you get different behaviour - Clay Shirky
  • 5. what is drupal.org?(the issue queue’s home)
  • 6. our home?
  • 7. our office?
  • 8. our playground?
  • 9. our social network?
  • 10. as a place to be a community, to make drupal, it’s a bit of a bloody mess.
  • 11. redesigning the issue queuea social architecture project
  • 12. we need to be more effective- allow us to make good decisions, quickly- involve the right people at the right time- encourage us to follow good processes fordesigning and implementing solutions
  • 13. we need to be more findableand more joined up- how do new people find the issue queue?- you do you find issues you need/want to know about?- why are there three different initiatives going on atonce to solve the same problem (this is ok, except thatthey don’t know about each other)
  • 14. we need to know about thingseven if we can’t be on IRC or in theissue queue for hours every day- smart notifications!- let me know when I should know something.- don’t bug me all the time...
  • 15. we need understand & supportmodes of participation better- 1:9:90- easier to be a power user/leader- easier to dip in and add value
  • 16. we need a better way to planinitiatives together- planning something big is different to gettingwork on a project done- a place to plan complex, multi-stage projects- a place to plan projects that don’t involve code
  • 17. we need to be more inclusive- a welcoming environment for noobs- a way to efficiently provide friendly support- an environment that supports all disciplines.
  • 18. we should behave online like we doin the hallways at Drupalcon- an environment that encourages friendliness,politeness, constructiveness, proactivity.- a way to channel passion positively- ‘the shadow of the future’?
  • 19. We don’t have a choice about whether we havea reputation system or not.We need to choose if/how we write it down .- what’s measured matters- a way to show influencewhilst remaining egalitarian- a way to show expertisewithout being a show off
  • 20. some inspiration:
  • 21. be considerate be respectful be collaborativewhen we disagree, we consult otherswhen we are unsure, we ask for help step down considerately http://drupal.org/dcoc
  • 22. the right way to explore complex problems in a collaborative way.generate synthesis & evaluate & collaboratively capture & share ideas explore ideas prioritise ideas make a agreed decision decision
  • 23. openideo
  • 24. openideo
  • 25. openideo
  • 26. openideo
  • 27. openideo
  • 28. UXexchange
  • 29. UXexchange
  • 30. quora
  • 31. quora
  • 32. quora
  • 33. quora
  • 34. quora
  • 35. quora
  • 36. quora
  • 37. quora
  • 38. quora
  • 39. quora
  • 40. quora
  • 41. quora
  • 42. quora
  • 43. quora endorse for topic?
  • 44. quora
  • 45. quora
  • 46. facebook
  • 47. ning
  • 48. ning
  • 49. stackexchange
  • 50. stack exchange
  • 51. stack exchange
  • 52. the right way to explore complex problems in a collaborative way.generate synthesis & evaluate & collaboratively capture & share ideas explore ideas prioritise ideas make a agreed decision decision
  • 53. the right way to explore complex problems in a collaborative way.generate synthesis & evaluate & collaboratively capture & share ideas explore ideas prioritise ideas make a agreed decision decision
  • 54. social architecture project codename: prairie
  • 55. proposed next steps: - benchmark (baseline) - define the problem space - explore solutions- design a system approach that allows for rapid but thoughtful implementation - plan implementation - open, collaborative
  • 56. work out what we need to measure. what does success look like? - aggregate pain points - site analytics- community (satisfaction) survey? - quick wins
  • 57. Make no little plans.They have no magic to stir men’s blood Daniel Burnham, Chicago architect. (1846-1912)
  • 58. prairie schoolorganic architecture
  • 59. louis h sullivan‘as you are, so are your buildings;and as your buildings are, so are you’‘form ever follows function’
  • 60. Frank Lloyd Wright‘Form follows function - that hasbeen misunderstood. Form andfunction should be one, joined in aspiritual union.’‘All fine architectural values arehuman values, else not valuable’