0
Licensed under Creative Commons Attribution-ShareAlike 4.0 International License
How to “Hack” the
DSpace Community
Tim Do...
Hacking any OS Community
• How do things get done?
• Who are the “do-ers”?
• What is their motivation? Why do
they care?
•...
How things get done
• Releases just
happen!
• One person /
organization
decides it all!
• Ummm… no.
The Primary “Do-ers”
• Committers Team
• DSpace Community Advisory Team
(DCAT)
• “The Community” (i.e. YOU)
Committers
• Meritocracy and democracy
• 24 volunteers from around the globe
• Roles:
– Reviewers / approvers of code
– Wr...
DCAT
• Open membership
• 22 volunteers from around the globe
• Roles:
– Voice of the repository manager/admin
– Champions ...
The Community /
Contributors
• Everyone, literally (includes YOU)
• Roles:
– Answerers of questions (on mailing lists)
– P...
What about this new
Governance model?
Goals of Governance Model
• Really about increasing efficiency
and organization of our resources
• Help us to better prior...
Who writes the code?
• Committers (and developers at their
institutions)
• The Community
– submit code for review (via Git...
Code Commits to DSpace
Committers (non-DuraSpace)
DuraSpace
Community Members
* - Moved to GitHub post-1.8.0
(NOTE: Not al...
So, why should ISo, why should I
contributecontribute
(code)?(code)?
Motivations to contribute
• “Greater Good” motivations, e.g.
– Betterment of product for all
– Help your colleagues, earn ...
OK, I have (code)OK, I have (code)
to contribute!to contribute!
How do I contribute code?
1. Open a ticket in JIRA (anyone can)
– Attach or link to code change
1. Code change is reviewed...
Why may delay a ticket?
• Committers are volunteers!
• Sometimes…
– we overlook things / forget
– we have questions / conc...
How can I help speed it up?
• Be responsive, please
• Remind us
(seriously, we don’t mind)
• Use JIRA & GitHub
• Share you...
Oh, I need thisOh, I need this
feature!feature!
How do I request a feature?
1. Open up a ticket to describe feature
and sample use cases
2. Ticket & idea are reviewed
– B...
How can I help speed it up?
• Be responsive, please
• Help gather info / use
cases
• Help locate developer
– Hire service ...
I think I justI think I just
found a bug!found a bug!
How do I get it fixed?
1. Open a ticket (if one doesn’t exist)
2. Ticket is reviewed (by Committers)
– We attempt to verif...
How can I help speed it up?
• Be responsive, please
• Provide as much info
as you can about
reproducing the bug
• Help loc...
Look, I already
knew all of this…
Get (more) involved!
• Help answer questions on lists
• Help improve documentation on wiki
• Join DCAT
• Help verify bugs ...
Questions / Comments?
Contact Info & Slides
• Email: tdonohue@duraspace.org
• Slides: http://www.slideshare.net/tdonohue/
...
Upcoming SlideShare
Loading in...5
×

How to "Hack" the DSpace Community

2,181

Published on

Presented during the DSpace Interest/User Group sessions at the Open Repositories 2014 conference in Helsinki, Finland on June 13, 2014

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

No Downloads
Views
Total Views
2,181
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "How to "Hack" the DSpace Community"

  1. 1. Licensed under Creative Commons Attribution-ShareAlike 4.0 International License How to “Hack” the DSpace Community Tim Donohue, DuraSpace DSpace Tech Lead tdonohue@duraspace.org
  2. 2. Hacking any OS Community • How do things get done? • Who are the “do-ers”? • What is their motivation? Why do they care? • What is your own motivation? What do you want to achieve?
  3. 3. How things get done • Releases just happen! • One person / organization decides it all! • Ummm… no.
  4. 4. The Primary “Do-ers” • Committers Team • DSpace Community Advisory Team (DCAT) • “The Community” (i.e. YOU)
  5. 5. Committers • Meritocracy and democracy • 24 volunteers from around the globe • Roles: – Reviewers / approvers of code – Writers of (some, but not all) code – Fixers of bugs / maintainers of software – Release planners – Technology support http://tinyurl.com/dspace-committers
  6. 6. DCAT • Open membership • 22 volunteers from around the globe • Roles: – Voice of the repository manager/admin – Champions of feature requests/bug fixes – Surveyors of community / Networkers – Gatherers of use cases – Repository Admin support http://tinyurl.com/dspace-dcat
  7. 7. The Community / Contributors • Everyone, literally (includes YOU) • Roles: – Answerers of questions (on mailing lists) – Providers of feedback – Requesters of features – Reporters of bugs / issues – Contributors of features / bug fixes – Contributors to documentation
  8. 8. What about this new Governance model?
  9. 9. Goals of Governance Model • Really about increasing efficiency and organization of our resources • Help us to better prioritize what gets done • Helps try to locate more resources / funding (add more “do-ers”) You can have more opportunities & influence. Become a DuraSpace Member! Support DSpace!
  10. 10. Who writes the code? • Committers (and developers at their institutions) • The Community – submit code for review (via GitHub) • Recent Major Releases: – 4.0 : 59 contributors (19 Committers) – 3.0 : 43 contributors (14 Committers) – 1.8 : 44 contributors (14 Committers)
  11. 11. Code Commits to DSpace Committers (non-DuraSpace) DuraSpace Community Members * - Moved to GitHub post-1.8.0 (NOTE: Not all “Committer” code is actually written by Committers) Data based on commits between release dates, from: https://github.com/DSpace/DSpace/graphs/contributors Data based on commits between release dates, from: https://github.com/DSpace/DSpace/graphs/contributors
  12. 12. So, why should ISo, why should I contributecontribute (code)?(code)?
  13. 13. Motivations to contribute • “Greater Good” motivations, e.g. – Betterment of product for all – Help your colleagues, earn “merit” • “Local” motivations, e.g. – This tiny fix needs to be maintained! – Upgrade difficulty increases as you make more locally-specific changes – Are you *CERTAIN* your local change is really only interesting to you? Ask.
  14. 14. OK, I have (code)OK, I have (code) to contribute!to contribute!
  15. 15. How do I contribute code? 1. Open a ticket in JIRA (anyone can) – Attach or link to code change 1. Code change is reviewed by Committers – Majority vote wins. But, veto power. 1. Response is either: – Accepted -> it’s in! – Changes requested -> it needs fixes – Rejected -> it’s out?
  16. 16. Why may delay a ticket? • Committers are volunteers! • Sometimes… – we overlook things / forget – we have questions / concerns – we don’t have enough background info / details – we cannot find a volunteer developer http://tinyurl.com/dspace-code
  17. 17. How can I help speed it up? • Be responsive, please • Remind us (seriously, we don’t mind) • Use JIRA & GitHub • Share your code early – Esp. large changes http://tinyurl.com/dspace-code
  18. 18. Oh, I need thisOh, I need this feature!feature!
  19. 19. How do I request a feature? 1. Open up a ticket to describe feature and sample use cases 2. Ticket & idea are reviewed – By both Committers and DCAT – DCAT may add use cases / promote 1. Volunteer developer(s) sought 2. Feature built/developed 3. Feature code reviewed / approved http://tinyurl.com/dspace-contribute
  20. 20. How can I help speed it up? • Be responsive, please • Help gather info / use cases • Help locate developer – Hire service provider? • ‘Vote’ or comment on features of interest in JIRA http://tinyurl.com/dspace-contribute
  21. 21. I think I justI think I just found a bug!found a bug!
  22. 22. How do I get it fixed? 1. Open a ticket (if one doesn’t exist) 2. Ticket is reviewed (by Committers) – We attempt to verify the bug 1. Volunteer developer(s) sought 2. The fix is determined/developed 3. Bug fix code is reviewed / approved
  23. 23. How can I help speed it up? • Be responsive, please • Provide as much info as you can about reproducing the bug • Help locate a developer and/or fix • You can also help us verify bugs! – In JIRA, add a verification comment
  24. 24. Look, I already knew all of this…
  25. 25. Get (more) involved! • Help answer questions on lists • Help improve documentation on wiki • Join DCAT • Help verify bugs or send in fixes • Opportunities abound, get in touch
  26. 26. Questions / Comments? Contact Info & Slides • Email: tdonohue@duraspace.org • Slides: http://www.slideshare.net/tdonohue/ Image Credits • Hacker: https://flic.kr/p/bEy1pi • Magic ball: https://flic.kr/p/tYTwd • ToDo’s: https://flic.kr/p/9Lcbki • Give: https://flic.kr/p/KBY6e • Share: https://flic.kr/p/5NAgHs • Checkmark: https://flic.kr/p/6aYF5x • Snail: https://flic.kr/p/6nv5sA • Speed of Light: https://flic.kr/p/2ojA8h • Penny: https://flic.kr/p/7XvhFR • Bug: https://flic.kr/p/2Bow • Learn, Teach, Help, Enjoy: https://flic.kr/p/bk7tHV
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×