Preview:
DESCRIPTION
Citation preview
- 1. LITA Drupal Interest GroupChairs: Nina McHale &
Christopher Evjy ALA Midwinter Meeting January 21 2012 S
- 2. Drupal IG Renewal/ChargeS IG formed in 2009; renews in 2012S
Explore and promote the use of Drupal among libraries and
librarians, facilitating communication and establishing best
practices.
- 3. Survey SaysS 12 question survey ran from 12/27/11 1/6/12S
Sent to drupal4lib, web4lib, lita-l, code4libS Posted to Twitter,
Facebook, and the Libraries group on Drupal.orgS 79 responses!
- 4. Survey SaysS Content of the survey was based on Dale Askeys
We Love Open Source Software. No, You Cant Have Our Code column S
http://journal.code4lib.org/articles/527S Questions asked
respondents what barriers might keep them from contributing code
back to the Drupal community
- 5. Respondent Data: Type of EmploymentS I have a permanent,
full-time position working in a library environment: 82%S I am a
web development consultant with one or more clients: 10%S Other: 8%
S Library vendor, combination permanent/consultant, part-time
library employment
- 6. Respondent Data: Library TypeS Public: 44%S Academic: 54%S
School: 4%S Special: 10%S Other: 10% S vendor, government,
nonprofit, consortium
- 7. Respondent Data: Contributed Code?S Yes, I have: 15%S No,
but Id like to: 68%S No, but I cant: 13%S No, and I dont want to:
4%
- 8. Askeys Reasons for No ParticipatingS PerfectionismS
DependencyS QuirkinessS RedundancyS CompetitivenessS
Misunderstanding
- 9. Unless the code is perfect, we dont want anyone to see it.S
Very likely: 14%S Likely: 37%S Neither likely/unlikely: 17%S
Unlikely: 28%S Completely unlikely: 4%
- 10. If we share this with you, you will never leave us alone.S
Very likely: 12%S Likely: 24%S Neither likely/unlikely: 15%S
Unlikely: 24%S Completely unlikely: 11%
- 11. Well gladly share, but we cant since were so weird.S Very
likely: 12%S Likely: 19%S Neither likely/unlikely: 15%S Unlikely:
40%S Completely unlikely: 14%
- 12. We think your project is neat, but we can do better.S Very
likely: 3%S Likely: 12%S Neither likely/unlikely: 23%S Unlikely:
55%S Completely unlikely: 8%
- 13. We want to be the acknowledged leader.S Very likely: 0%S
Likely: 10%S Neither likely/unlikely: 21%S Unlikely: 21%S
Completely unlikely: 49%
- 14. A fundamental [misunderstanding] of how an open source
community works.S Very likely: 0%S Likely: 14%S Neither
likely/unlikely: 21%S Unlikely: 40%S Completely unlikely: 25%
- 15. What could the IG do to support code contribution back to
Drupal.org?S Education/training: ALL levels S Programming (PHP) S
Process of submission (contrib standards)S Showcasing colleagues
workS Communication: S With vendors S Meet-ups S Foster
collaboration among developers
- 16. Select ResponsesS Perhaps eliminate any FUD surrounding
issues of oss.S Maybe focus on getting library-specific vendors to
support product integrationS it would be great to have a match
making service to find co-maintainersS Provide space to share ideas
and develop a developer group for a module of interest.
- 17. Select Responses, contdS We [are] all out there, were just
not connecting.S Ive developed a couple of very small modules. I
dont both to contribute via official Drupal channels because it
would require learning the contrib standardsS More library-specific
meetups and events to showcase others work and possibly foster
better collaboration.
- 18. Proposal for IG DirectionS Increase communication
venues/opportunitiesS Develop a wish list of modulesS Establish a
formal/official relationship with the Drupal.org libraries group S
Drupal.org is THE venue for Drupal community S Removes possibility
of redundancy