Tag Archives: code sprints

Code Sprinting for Fedora 4

Dan Coughlin, Director of Software Development in ITS, blogs about Penn State migrating ScholarSphere to Fedora 4 Рa leading contribution for the Hydra software community.

As we closed out January, the ScholarSphere development team was hard at work for a two-week code sprint. What’s a code sprint? All developers clear their calendars and work collectively on a common project or, in this case, a specific feature within a project to create a big push towards completion. Usually a sprint lasts for a week or two–where developers share a conference room, chocolate, coffee, and goldfish.

Photo of cheese-flavored goldfish crackers inside their package.

Goldfish by Cindy Stuntz at Flickr, CC BY 2.0

The goal for this sprint was to integrate the latest and greatest version of Fedora (Fedora 4) into our ScholarSphere testing environment. We want to make sure it works on our testing environment before releasing it on the live site to help minimize inconveniences to you, the user. ScholarSphere currently runs on Fedora 3; Fedora 3 handles most of the preservation functionality for our files (checksums, storage of technical metadata, versioning, etc.).

Penn State is likely to have the first Hydra application running Fedora 4 later this spring. Great! What does this mean to you? The two biggest areas of focus for improvement on Fedora 4 are file size and speed. ScholarSphere will be able to handle larger files and process those files more quickly than before. Unfortunately, the web isn’t the greatest method for uploading files of multiple gigabytes, so we will be exploring other ways (besides via the ScholarSphere web page) for our users to deposit large files into the service. In fact, if you have large files (1-10 GB) we would love to hear from you and discuss your ideas about how to deposit these files in a way that best meets your needs. Thanks for reading, and we look forward to hearing from you!