Plays Well With Others

May 18th, 2010 |

Over the last year, the Scholars’ Lab has undertaken a project to build a tool for creating interlinked timelines and maps for interpretive expressions of the literary and historical contents of archival collections which we are calling Neatline. When the project was first envisioned, it was seen as a stand-alone tool scholars would use to produce geo-temporal visualizations of textual content. However, as we began the planning process, we thought this effort might not only reach a larger audience, but also contribute back to the larger community effort, if the tools were thought of as a suite of Omeka plugins. This follows a general turn the Scholars’ Lab has taken in how it approaches new projects, from the boutique, or one-off projects of the last decade, toward a more concerted effort to useĀ  frameworks in which we build additional functionality as needed.

Having worked on several open-source projects, I know one the most difficult aspects of this style of code development is building a community of support around the software development effort. Perhaps one of the most engaging of the community efforts I’ve experienced has been in the Rails community with their Bug Mashes as new versions of the framework are being developed. The idea revolves around four general ways in which participants can participate:

  • Confirm a bug can be reproduced
  • If it cannot be reproduced, try to figure out what information would make it possible to reproduce
  • If can be reproduced, add the missing pieces: better instructions, a failing patch, and/or a patch that applies cleanly to the current source
  • Bring promising tickets to the attention of the Core team

Generally locations (usually programming shops that use Rails) sponsor a day where community members can gather and participate in the bug mashing, sometimes there’s even pizza and highly-caffeinated drinks. The goal beyond getting some good code written is to get more people introduced to some of the new features, encourage people to talk about the experience, and just have a day to geek out for a good cause.

So here’s the pitch, knowing there’s a concentration of software developers, users, and enthusiasts, could we organize a series of bug mashes that promote community involvement through documentation, patches, blog posts on usage, thoughts, etc. on some projects that are commonly used by digital humanists (not specifically this weekend, but some time in the future)? Chief on my mind lately has been some enhancements to Omeka since several of our current projects are tied to that framework, but are there projects that could benefit from this type of planned community involvement? Are there any perplexing coding issues we could could hack on while at THATCamp?

Comments Feed

Comments are closed.

Search

  • Recent Comments

    THATCampers can use the blog and comments to talk about session ideas. Follow along by subscribing to the comments feed and to the blog feed!

    • thuyanh: A friend and I have actually made a video response that defends the “dumbest generation” and we...
    • Steven Hayes: Hi, just read your “project retrain” description as part of my background reading for...
    • Peter: Just curious: Is there a version of the National Register Nomination Form in some kind of database format,...
    • Samuel Teshale Derbe: This is excactly what I have been looking for.I have been recently invited to contribute to a...
    • plr articles: Just added more knowledge to my “library-head” :D
  • Twitter

    Here's what others are saying about THATCamp on Twitter

    • No items

    All Posts

  • THATCamp Prime Collaborative Documents
  • THATCamp Prime evaluation
  • New session: The THATCamp Movement
  • THATCamp on Flickr
  • Visualizing Subjectivity
  • More Twitter Visualizations
  • Remixing Academia
  • What THATCampers have been tweeting about (pre-camp)
  • Late to the Stage: Performing Queries
  • Humanist Readable Documentation
  • Zen Scavenger Hunt
  • The (in)adequacies of markup
  • One Week, One Book: Hacking the Academy
  • Analogizing the Sciences
  • Digital Literacy for the Dumbest Generation
  • Teaching Students Transferable Skills
  • Modest Proposals from a Digital Novice
  • Creative data visualizations
  • OpenStreetMap for Mapping of Historical Sites
  • soft circuits
  • Mostly Hack…
  • A Contextual Engagement
  • ARGs, Archives, and Digital Scholarship
  • Playing With the Past: Pick One of Three
  • DH centers as hackerspaces
  • All Courseware Sucks
  • HTML5
  • Dude, I Just Colleagued My Dean
  • The Future of Interdisciplinary Digital Cultural Heritage Curriculum (oh yeah, and games as well)
  • Project "Develop Self-Paced Open Access DH Curriculum for Mid-Career Scholars Otherwise Untrained"
  • what have you done for us lately?
  • Digital Storytelling: Balancing Content and Skill
  • Visualizing text: theory and practice
  • Plays Well With Others
  • Citing a geospatial hootenanny
  • Reimagining the National Register Nomination Form
  • documentation: what's in it for us?
  • Sharing the work
  • Digital Humanities Now 2.0 and New Models for Journals
  • Finding a Successor to Paper and Print
  • "Writing Space"
  • From Scratch
  • Cultivating Digital Skills and New Learning Spaces
  • Surveying the Digital Landscape Once Again
  • Building and designing projects for long term preservation
  • Collecting the Digital Story: Omeka and the New Media Narrative
  • Design Patterns for DH Projects
  • Chronicling America: They gave us an API. What do we do now?
  • Social Media and the History Non-Profit
  • THATCamp-in-a-Box
  • Teaching Collaboration
  • Geolocation, Archives, and Emulators (not all at once)
  • The Sound of Drafting
  • The Schlegel Blitz ("Only connect…")
  • Text Mining Scarce Sources
  • Applying open source methodology and economics to academia
  • What I'd Most Like to Do or Discuss
  • Hacking ethics for edupunks
  • Mobile technology and the humanities
  • Audiences and Arguments for Digital History
  • Open Peer Review
  • Who Wants To Be A Hacker?
  • Please advise
  • Greetings from the new Regional THATCamp Coordinator!
  • 2010 Applications Open!