Social Sourcing:
The story of GetPaid, ideas for
 organizing software projects
       Christopher Johnson
      ifPeople |...
Outline
●   Who, What, Why?
●   What is Social Sourcing?
●   Why is it important for Free Software?
●   The Story of GetPa...
Who am I?
What is GetPaid?
●   eCommerce in Plone built on Zope3
    –   credit card processing
    –   order management
    –   shi...
Why am I here?
●   Voice for non-developers!
●   Make Plone better: software, community,
    marketing
●   Get feedback an...
What is Social Sourcing?


Def 1: Open Source Software for Civil
 Society Organizations (ie NGO/non-
               profit)
What is Social Sourcing?


Def. 2: A project organizing approach
  that gets diverse stakeholders to
  participate to the ...
Similar Process: Charrette
●   Charrettes bring together people from
    multiple perspectives at the design stage for
   ...
Charrette
●   Key: collaborative decision making in design
Data Center Charrette
●   People from hardware, software, security,
    energy, real estate and more
    –   Resulting des...
Why is this relevant?
●   Open Source Software projects are
    driven by developers

      ==> Many projects naturally us...
Why is this relevant?
●   Diverse perspectives enrich the product

     ==> Expectations from client clarified
    upfront...
Why is this relevant?
●   The quality of the process determines
    the quality of the outcome

     ==> How you get it do...
●   Plone:
    –   Flexible + very useful out of the box
●   2006 PloneConf ecommerce BOF
    –   Conclusion: Need state o...
●   To action! But...
    –   /me was new to community, not a developer, and
        with no ecommerce software experience...
Social Source v1.0 Alpha
●


    –   Study the market (benchmark)
    –   Put together a compelling plan
    –   Recruit t...
●   Step 1: Get oriented
    –   What is already out there?
    –   What do we know about those things?
    –   Why do we ...
●   Step 2: Make a plan
    –   What should we do?
    –   How can we do it?
    –   Who does it benefit and how?
    –   ...
●   Step 3: Recruit leaders and participants
    –   The project needs a qualified “sheperd”
    –   Variety of expertise ...
●   Step 4: Refine the requirements
    (participative)
    –   Get input of users, developers, user interface
        exp...
●   Step 5: Ask for money!
    –   If you don't ask, you won't get it...
    –   Tips for asking:
         ●   Connect nee...
●   Step 5: Don't forget...
    –   Be accountable and transparent
●   Step 6: Celebrate successes!
    –   Reward and recognize people and their
        contributions
         ●   Deployme...
●   Ongoing:
    –   Make it fun!
    –   Keep it organized!
    –   Keep people motivated!
●   Results:
    –   4 Sprints...
Social Source v1.0 Alpha
●


    –   Study the market (benchmark)
    –   Put together a compelling plan
    –   Recruit t...
What next?
●   Time for a new round of social sourcing for
    GetPaid!
●   Encourage flow back into product of
    custom...
Implications for Plone?
●   Plone is great!
●   Lots of work heading into the future...but
    towards what?
    –   Perha...
Plone Creation Process
●   Overall vision:
    –   Open process associated with vision?
         ●   How can users be more...
Getting Involved
●   Download it:
    http://code.google.com/p/getpaid
●   GetPaid mailing list:
    http://groups.google....
Thank you!
●   Special thanks:
    –   Kapil, Perrito, Lucie, Maurits, ChrisW
    –   OneNW, Contextual Corp, Totsie.com, ...
Social Sourcing as a Collaborative Design Process: Story of GetPaid (Plone Symposium NOLA 2008)
Social Sourcing as a Collaborative Design Process: Story of GetPaid (Plone Symposium NOLA 2008)
Social Sourcing as a Collaborative Design Process: Story of GetPaid (Plone Symposium NOLA 2008)
Social Sourcing as a Collaborative Design Process: Story of GetPaid (Plone Symposium NOLA 2008)
Upcoming SlideShare
Loading in …5
×

Social Sourcing as a Collaborative Design Process: Story of GetPaid (Plone Symposium NOLA 2008)

864 views

Published on

Open Source projects are normally developer-driven and tend to lack ways for non-developers to make meaningful contributions. GetPaid, an ecommerce framework for Plone, was organized with a collaborative design process known as "social sourcing". This talk provides an update on the community organizing, fundraising, and development of GetPaid. Updated and slightly shorter than the Naples version of the talk.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
864
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Social Sourcing as a Collaborative Design Process: Story of GetPaid (Plone Symposium NOLA 2008)

  1. 1. Social Sourcing: The story of GetPaid, ideas for organizing software projects Christopher Johnson ifPeople | www.ifpeople.net Plone Symposium 2008 New Orleans, LA June 3, 2008
  2. 2. Outline ● Who, What, Why? ● What is Social Sourcing? ● Why is it important for Free Software? ● The Story of GetPaid & Social Sourcing ● Implications for Plone
  3. 3. Who am I?
  4. 4. What is GetPaid? ● eCommerce in Plone built on Zope3 – credit card processing – order management – shipping, fulfillment, inventory management – 2 releases; 10,600+ lines of code ● Community – 105 members on mailing list – 34 contributors (15+ in 2008)
  5. 5. Why am I here? ● Voice for non-developers! ● Make Plone better: software, community, marketing ● Get feedback and ideas (time for another round of social sourcing for GetPaid!)
  6. 6. What is Social Sourcing? Def 1: Open Source Software for Civil Society Organizations (ie NGO/non- profit)
  7. 7. What is Social Sourcing? Def. 2: A project organizing approach that gets diverse stakeholders to participate to the software making process, focusing on the value of product.
  8. 8. Similar Process: Charrette ● Charrettes bring together people from multiple perspectives at the design stage for an intense collaboration. – Root: French for “cart” – More than just “crunch time”, it is also core to an Integrated Design Process
  9. 9. Charrette ● Key: collaborative decision making in design
  10. 10. Data Center Charrette ● People from hardware, software, security, energy, real estate and more – Resulting design: ● 89% energy use reduction ● Equivalent computing power ● Increased reliability – See rmi.org
  11. 11. Why is this relevant? ● Open Source Software projects are driven by developers ==> Many projects naturally use agile processes (sprints, pairing) ==> Developers, like architects, often reticent to get “human” input ==> Difficult for non-developers to participate in shaping outcome
  12. 12. Why is this relevant? ● Diverse perspectives enrich the product ==> Expectations from client clarified upfront ==> Opportunities and constraints explored fully
  13. 13. Why is this relevant? ● The quality of the process determines the quality of the outcome ==> How you get it done determines what you get done ==> Position product to have a strong community
  14. 14. ● Plone: – Flexible + very useful out of the box ● 2006 PloneConf ecommerce BOF – Conclusion: Need state of the art payment processing framework
  15. 15. ● To action! But... – /me was new to community, not a developer, and with no ecommerce software experience...but loves problem solving! – “Social sourcing” helped to be transparent, inclusive, and improve the product. ● <DOCTYPE FREESOFTWARE PUBLIC...> <div id=”entrepreneur”> ...don't be afraid!
  16. 16. Social Source v1.0 Alpha ● – Study the market (benchmark) – Put together a compelling plan – Recruit the right people – Engage a wide base in refining requirements – Ask for money – Celebrate successes – Sustain it: fun, organization, motivation – Regroup, review, and restart...
  17. 17. ● Step 1: Get oriented – What is already out there? – What do we know about those things? – Why do we need something else? ● Result: – Reference on Plone Commerce: http://plonegetpaid.com/why/plone-commerce-backgro – Need for the product: http://plonegetpaid.com/why/need-for-this-product
  18. 18. ● Step 2: Make a plan – What should we do? – How can we do it? – Who does it benefit and how? – Make it pretty to look at... ● Results: – Goal for GetPaid M1: Donation handling – Sponsorship plan: www.plonegetpaid.com/sponsor
  19. 19. ● Step 3: Recruit leaders and participants – The project needs a qualified “sheperd” – Variety of expertise are needed ● Result: – Lead architect: Kapil Thangavelu – Organizer: Christopher Johnson – NGO Liason: Jon Stahl – Several more have stepped up! – Developers and UI: various (see Credits)
  20. 20. ● Step 4: Refine the requirements (participative) – Get input of users, developers, user interface experts, consultants/supporters ● Results: – Architecture outline – User stories – Estimates and plan
  21. 21. ● Step 5: Ask for money! – If you don't ask, you won't get it... – Tips for asking: ● Connect needs with value ● Be transparent ● Be patient and persistent ● Result: – Raised over US$12,000 for first release – Contributions page
  22. 22. ● Step 5: Don't forget... – Be accountable and transparent
  23. 23. ● Step 6: Celebrate successes! – Reward and recognize people and their contributions ● Deployments, releases, fixes – Communication is important! ● Results: – Blog, mailing list – Celebrations...
  24. 24. ● Ongoing: – Make it fun! – Keep it organized! – Keep people motivated! ● Results: – 4 Sprints (UNC, Google, Argentina, Naples) – Google Code (wiki, issues, code) – Blog, mailing lists, channel (#getpaid)
  25. 25. Social Source v1.0 Alpha ● – Study the market (benchmark) – Put together a compelling plan – Recruit the right people – Engage a wide base in refining requirements – Ask for money – Celebrate successes – Sustain it: fun, organization, motivation – Regroup, review, and restart...
  26. 26. What next? ● Time for a new round of social sourcing for GetPaid! ● Encourage flow back into product of customizations and extensions ● Capture feedback from users, developers to improve project ● Need technical leaders in various areas
  27. 27. Implications for Plone? ● Plone is great! ● Lots of work heading into the future...but towards what? – Perhaps Plone could benefit from process improvements that would: ● Clarify direction and identity ● Provide more inclusive design process ● Improve the overall product ● Strengthen Plone community
  28. 28. Plone Creation Process ● Overall vision: – Open process associated with vision? ● How can users be more involved? – Place to document it? ● Features: – PLIPs process determines features...but you have to be a “core developer” to make a PLIP ● Something before PLIPs but more specific than vision? ● Way to involve non-developers?
  29. 29. Getting Involved ● Download it: http://code.google.com/p/getpaid ● GetPaid mailing list: http://groups.google.com/group/getpaid-dev ● IRC: #getpaid ● Features, Sponsorship etc: http://www.plonegetpaid.com
  30. 30. Thank you! ● Special thanks: – Kapil, Perrito, Lucie, Maurits, ChrisW – OneNW, Contextual Corp, Totsie.com, Trees for Life ● Contact info: – Christopher Johnson – cjj (at) ifpeople.net – www.ifpeople.net – irc: cjj

×