This was the third hackathon run by the worldwide Library Carpentry community. As ever, it was a great success, pulling in a number of people new to this community. Sprint participants from Melbourne had attended their first ever Library Carpentry workshop only a week before.
There were 3,138 views of those repositories during the sprint, with 341 unique visitors.
More than 150 pull requests and issues were raised against the lessons, with the
lessons getting some much-needed attention. Thanks to François Michonneau for his help in wrangling these numbers.
Broken down by the individual lessons, these numbers were:
- data intro (31)
- git (27)
- python intro (23)
- sql (20)
- spreadsheets (14)
- shell (13)
- open refine (12)
- web scraping (11)
Chris Erdmann led the charge in the northern hemisphere from the UCLA sprint site where he joined Tim Dennis and others. A number of the UC libraries contributed to the sprint with dedicated sites at San Diego, Berkeley, and San Francisco. There were also sites in New Haven, New York, Florida, Arizona and Kansas, while a number of people worked remotely.
Led by Peter Neish and Jaye Weatherburn, a team at the University of Melbourne’s site in Australia drew up plans for a new digital preservation lesson, while others in Australia worked with the UCLA team to create new materials around the FAIR principles. (FAIR is an acronym for Findable, Accessible, Interoperable, Reusable).
Belinda Weaver in Brisbane worked flat out on preparing the new Library Carpentry website for launch, lodging more than 230 commits to get the repository ready. See it at http://librarycarpentry.org/.
Cam Macdonell updated all the lessons to the new style.
Non-technological sweeteners included Belinda’s hazelnut torte in Brisbane along with scrumptious-looking cakes from the Melbourne team and the UCLA team (adorned with hashtag!).
Library Carpentry has pretty much singlehandedly made the Twitter hashtag #mozcake a thing!
Want to get involved in Library Carpentry? Check out all the ways you can get in touch.
Dialogue & Discussion
Comments must follow our Code of Conduct.