Google Summer of Code 2009 Ideas

Welcome to the Oregon State University Open Source Lab Google Summer of Code Ideas page.

One of the things we learned in the past three Summer of Code programs is that the more time spent on collecting and refining the proposed project ideas, the better the summer goes. So with that in mind … ta-dah! A new SoC ideas page.

Student and Prospective Applicant Information

Thank you for your interest in the Open Source Lab's Summer of Code proposals. Here at the OSL we feel we have a two-part goal. First, we are a strong supporter of the open source community and want to help as many projects as we can. Second, we are an educational institution that tries to incorporate teaching and learning into as much of what we do as possible. The Google Summer of Code helps us to do both.

Project proposals

Proposals that are written poorly or in an unprofessional manner, use improper grammar or spelling, or do not answer all the questions in our application template completely will be rejected.

It is important to note that none of these projects are cast in stone. We very much want to work with our students on developing and shaping the project. Think of this page as a general outline of some of the things we want to do. Don't be afraid to propose something that does not exactly match what we have below. If you have a great idea for a project that's not listed here, please feel free to submit it. If it is a very well thought-out proposal with realistic goals, is in some way related to one of the projects we work with and something one of our mentors would be interested in working on, we may consider accepting it.

There's more to a good proposal than just a good project idea. When we evaluate proposals, we don't just look at the idea itself. We also look at how much thought and effort has gone into the proposal. Does it have a roadmap or a timeline with milestones? Are the milestones reasonable? Is there time built in for documentation and bug-squashing? Has something like this been done before? If so, how is this proposal different?

Expectations

It's important when starting a new relationship like this that both sides are aware of the expectations involved. We're a pretty easygoing bunch here at the OSL - we're far more interested in building neat stuff than we are about rigidly following some policies and procedures manual. However, we do have some pretty simple expectations:

  1. Good communication is vital. If we accept your proposal, we expect you to be talking to your mentor on at least a weekly basis. The method of communication - phone, e-mail, IRC, carrier pigeon - is up to you and your mentor, but the weekly contact is absolutely mandatory. Exceptions are possible, but only if pre-arranged. If we haven't heard from you in a week, your mentor will attempt to contact you with a friendly reminder. If we don't hear from you after the reminder, we'll send you a formal warning. If you don't respond to the formal warning, it is likely we will be submitting a negative evaluation to Google recommending you be dropped from the program. It sounds dire, but it's easy to avoid: just keep in touch.
  2. Commit early and commit often. As mentors, we need to see the code you're working on. It's really difficult to help someone if we can't see what you're doing. We won't require anything as rigid as scheduled code check-ins, but the more often you share what you're working on with the rest of us, the better things will go. There is one caveat: we absolutely have to have some code from you before the mid-term evaluation. We need something upon which to base our evaluation.
  3. You're part of the team. We're very egalitarian here at the OSL - see The Rules for more on our internal philosophy. We firmly believe that once someone is a member of the OSL you are always a member, regardless of whether you are with us as an SoC student, a community volunteer, or as an employee of the Lab. Before, during, or after the Summer of Code. Much of what we do is driven by consensus and we're not strong on hierarchy, so please don't hesitate to jump right in and express your opinions!

Contact Us

Questions? Concerns? Want ask us if we'd be interested in an application?

  • IRC - Drop in and visit us in #osuosl on irc.freenode.net. If you're not sure who to talk to ping gchaix or kreneskyp in #osuosl or #gsoc.
  • Email - gsoc@osuosl.org

Hint: if we've already talked to you about your proposal, it helps your chances for acceptance. We're happy to give feedback and suggestions on proposals, so it's a good idea talk to us before you submit it.

Project List

AndroidIRC(name?)

AndroidIRC(name?) is a completely open source IRC client for Google's Android mobile platform (http://code.google.com/android/).

Planned Features for AndroidIRC(name?)

  • Allow direct connection to any IRC server and provide all the functionality a client should have. (see RFC1459 - http://www.ietf.org/rfc/rfc1459.txt?number=1459).
  • Multi-server and multi-channel support.
  • Develop a sane way of dealing with several servers and channels on very low amounts of screen real estate.
  • Follow all user interface guidelines and match usability/functionality standards of other included “IM” applications for the Android platform.
  • Develop an external, and optional, message-queuing service that works with our client. The idea is to devise a way to allow persistent connections to IRC channels so that users can idle, send, and receive messages via the mobile client but minimize the time that the network stack is active, thus saving battery life and network traffic. (This can be accomplished by writing our own “server”, or leveraging already existing open source technology)
  • Use encrypted connections/data whenever possible.

Projects

There are 3 logical divisions of labor for this project:

  • IRC client communication backend: Handle connections and sending and receiving messages.
  • GUI: Use the exposed backend functions to craft an aesthetically pleasing and easy to use interface.
  • External message-queuing service: Write/implement a simple message-queuing server for our client, allowing us to “idle” and receive/send messages when the application is in the foreground or on a specific time interval without wasting battery life or network traffic.

Pydra

Pydra is an open source parallel and clustered computing solution written in python using Twisted.Python and Django. Pydra is a new project that is working towards it's first public release.

Read more about pydra

Project Ideas

Contribute to Pydra

There are a lot of features on the wishlist for pydra. Pick and choose from these ideas, or check out the task tracker:

Write Applications Using Pydra

Develop an application that uses Pydra to reduce its run time. Here are some suggestions, feel free to come up with your own ideas.

  • Web Crawler
  • Document Indexer

Touchscreen 2.0

Touchscreen is software for running interactive slideshows/demos. Touchscreen allows standalone slideshows or interactive displays using controls such as a touchscreen interface. It is primarily used at the OSL on the large flatscreen+touchscreen directly outside our server room. It displays various statistics and realtime data about the lab.

We are in the process of rewriting touchscreen to use Django, Jquery, javascript, HTML, and CSS.

Learn more about Touchscreen

Project Ideas

Write a Screen Plugin(s)

Write new plugin(s) that showcases things happening at the osl. We'll supply the data, you supply an exciting representation of it.

Here are some screens we have already produced:

Suggestions for new screens:

  • rewrite ftp user's map using google maps.

Work on Touchscreen Core

Protein Geometry Database

The Protein Geometry Database is a tool for searching and correlating geometric structures within proteins. It is used to derive empirical information about protein geometry which will produce improved modeling techniques. Highly detailed protein models will ultimately result in knowledge of how diseases function, and what drugs will inhibit them. The software is being developed by the OSL for the Oregon State University Department of Biochemistry & Biophysics

PGD is in an early beta state. We have a usable version there are many features planned for 1.0 that have not been implemented yet

Check out the demo

Project Ideas

Here are some example tasks to choose from, or take a look at the Task Tracker and suggest your own idea.

Unify

Unify is a unifed package building system using gentoo ebuilds as the “build scripts”. Its primary purpose is to create proper binary packages for deb, rpm, and Solaris package types. The basics of the application was created last year in the previous SoC. Check out the project here.

Project Ideas

Package Dependency

Currently Unify has no concept of package build dependencies. Each package format has their own naming scheme for package dependencies. Gentoo also has no concept of sub-packages like most binary packages have (i.e. -devel, -libs, etc). The logic and concept for this needs to be created and implemented.

Solaris Support

The original goal for the project was creating a sane system for building solaris packages using gentoo ebuilds. Implementing support for at least Solaris 9 and 10 would be great. It would require knowledge of Solaris and its packaging sytem (which is mostly closed sourced). It also has no real package manager, so that would need to be accounted for possibly.

VirtAdmin

VirtAdmin is a project at the OSL to create a web interface for managing virtual infrastructure. The goals are to simplify management and eventually to be able to give projects limited access to virtualized infrastructure we host for them (for example allowing them to get on the console or reboot a virtual machine).

Project Ideas

Here are a few of the ideas we have for the project:

  • Console access from the web interface
  • Monitoring/Graphing
  • Storage Management
  • Design and Integrate an extensible plugin system
  • Provisioning of virtual machines from the web interface

BeaverSource

Beaversource (http://beaversource.oregonstate.edu) is a collaborative effort among many different departments on campus to create a code community for open source development at OSU. It attempts to provide a constructive and positive environment for FOSS software developers on campus.

Project Ideas

  • Expand the BeaverSource framework to be useful for other schools that want to set up their own OSS-based curriculum around a education based hosting framework.

OSWALD

OSWALD (http://beaversource.oregonstate.edu/projects/cspfl) is a student-developed Ultra-mobile PC, made for undergraduate students to explore CS concepts hands-on. To do this, the OSWALD is powerful, flexible, and incorporating some of the latest technology available, while keeping the cost to a minimum.

Project Ideas

  • Port android to the OSWALD device to open up more opportunities for teaching and projects with the device (especially in the mobile area).

Trust the Vote - Open Source Digital Voting

The Open Source Digital Voting (OSDV) Foundation serves as a supporting organization for a collection of open source digital voting technology projects. The purpose of the Foundation is to provide support and protection for the development of the specifications, draft standards, and reference implementations of high assurance, high veracity digital voting technology

We propose that one or more Google Summer of Code students work with OSL staff on the design and development of a demonstration digital voting service that uses high assurance voting system “reference implementations” which meet the draft standard guidelines, specifications, and potential assessment standards.

Project Ideas

Please note that some of these ideas may be too large or too small for a Summer of Code project. Please keep that in mind while formulating your proposal.

Building a reduced kernel platform for high-integrity embedded applications

Goal: create a substantially minimized Linux distro and build process for simple embedded applications. This distro will be the basis for voting systems designed by OSDV. The reasoning for a reduced distro is to reduce the amount of source code in the distro. Both the build system and all source code must be certified by an independent test lab prior to use in U.S. elections. Less source code simplifies and speeds up the certification process.

  1. Start with a bare Linux kernel add only the features required for a working kernel that can support a simple embedded application that does no networking, no IPC, requires only the basic sequential file system, and uses the most generic devices and drivers for keyboard, video, and one form of removable media for both reading and writing.
  2. kernel must include hardened kernel patches
  3. Create a LiveCD image that runs a hello-world++ program on reduced kernel, doing some reading from a removable medium, and some appending to a removable medium.
  4. Build Process for the LiveCD must be automated.

Build a Minimal Distribution of Python

Goal: Build a distribution of Python that has the minimal set of functionality needed for voting systems.

  1. Determine what is the minimum set of Linux packages that is needed to support a python application execution environment. By itself this would be a big achievement. Some technical support from python.org folks maybe available.
  2. Experiment with changes to the standard python distribution to reduce it in order to eliminate some package dependencies. Using Ka Ping Yee's definition of a thin python subset (“pthin” see www.pvote.org), modify the python interpreter to implement only pthin rather than the full python.
  3. Using Yee's pvote sample application in pthin as a guide, determine what parts of the python runtime can be exised as unneeded for pthin applications. Eliminate these from the python build, and determine whether more package dependencies have been eliminated.
  4. Demonstrate pvote running on your reduced distribution.
  5. Assess the difficulty of the task of developing custom-build software that automates the modification of the standard python distribution.

Highly auditable ballot tabulation

Goal: create a first version of the BCCS component that creates the final election results by totaling up partial election results.

Background:

  1. Election Markup Language (EML) includes schema for both a ballot format (sequence of contests, candidates in each contest, etc.) and tallies in a format (for each item in the format, a number of votes cast for that item).
  2. A highly auditable program is one that is relatively easy for independent readers to audit (read, understand, develop test plans) due in part to the care with which the program is written, in part to low inherent complexity, and in part by using a high-level language that was designed for readability and comprehensibility.

In such a language (python preferred), develop a program to meet these functional requirements:

  • Consume an input schema in EML that defines a ballot format
  • Choose a subset of EML's ballot definition schema if needed to reduce the scope of the programming task
  • Consume an input dataset of multiple EML tally datasets in the input schema
  • Create an output dataset in EML's schema for ballots tallies, recording the total number of votes for each contest/candidate or measure /choice.
  • In computing the ballot totals, use a vote-for-at-most-one voting model, and detect (and not count) overvotes
  • Create an output dataset in ad hoc format that records numbers of undervotes and overvotes for each contest.

Auditable high-integrity transaction-secure Web browser appliance

Goal: The end result is a LiveCD image that boots a system that runs exactly one program, which is a customized Web browser in which security configurations (including certificates) are unchangable. Some assitance from mozilla,org folks may be available.

  1. As a starting point, use a standard Linux distro, and the XULrunner toolkit for building embedded browsing into other applications.
  2. The application to be embedded in is simply part of the Linux system initialization software.
  3. Along the way from this starting point, you will excise the parts of XUL runner that are not needed in order to support simple forms-based Web applications, e.g., no active content. (A specific example Web application will be provided.)
  4. Time permitting, determine what packages of the Linux distro can be eliminated because the browser does not depend on them.

Background: The eventual objective is to create a browser appliance that is more auditable than the standard alternative (full browser distro running on full OS distro) by virtue of lower size and complexity. Auditability, in turn, is central to developing assurance of the embedded security properties of the browser appliance.

Basic ballot marking extension of pvote

Goal: enhance pvote (a balloting software package, see pvote.org) to print a paper artifact that resembles an official ballot

  1. Record each pvote-captured ballot as an e-ballot in EML, for a specific ballot definition (to be supplied)
  2. Using pre-created paper ballot format (which will be supplied) to create a paper ballot image corresponding to the e-ballot
  3. Print the ballot image
  4. Create a liveCD image for testing of this electronic ballot marking software, including the audio ballot function

High-fidelity electronic ballot marking

Goal: create ballot marking software with a presentation layer that closely mimics the presentation of a paper ballot

Electronic ballot marking devices present an unusual challenge in high-assurance system development and user interface design: an EBM system must present ballot information a choice that are exactly the same as that presented by a paper ballot; and ensure that users have the same progress tracking information as offered in a paper ballot; and select the proper ballot that captures the user's choices, with a minimum of software complexity and a maximum of software auditability. Using as an example a real election paper ballot, and building on previous work in pre-rendered user interfaces, implement a visual navigation scheme that shows the whole ballot, selection and zooming to particular contests, selection and marking of each contest, progress tracking showing completed sections of the ballot, and selection of a pre-rendered ballot image to be printed. Demonstrate strong software separation between UI functions, ballot-data storage functions, and ballot image prep and printing functions.

Optical scan/tally device presentation layer

Background: Ballot browser is an existing open source software package that consumes a set of ballot image files, performing image processing to extract marks representing votes, and to record ballot, vote, and tally information in a local database.

Goal: augment Ballot Browser with functions for creating pre-defined reports, and for simple user-user-driven ad hoc queries.

  1. Using standard Linux and Python distros, build an embedded system for running Ballot Browser on a fixed set of ballots (to be provided), and package as a liveCD image.
  2. Create additional software, and associated UI, for the creation of pre-defined reports derived from the database after the ballot scanning is complete
  3. Create additional software, and associated UI, some simple ad hoc queries against the database
  4. Package extended system as a liveCD image

Voter Registration System and Election Management System

OSDV is building an open source Voter Registration System and Election Management System, using ruby/rails. Contributions range from joining the ongoing implementation team for voter registration, to finishing the design and starting the development for election management. An extensive set of functional requirements is available at http://www.sos.ca.gov/elections/bidders_library/final-rfp-changes-accepted/add8-section-VI-2008-changes-accepted.pdf pages 12 to 95.

OpenOffice.org

Project Ideas

Migrate Extensions site to Drupal 6 modules

The OSL hosts Openoffice.org's Extensions website which is powered by Drupal 5. Unfortunately most of the modifications that were made to the site were done directly to the core Drupal code which makes upgrading it nearly impossible. This project would entail going through the existing code base, proposing a plan for how it could be implemented as one or more modules in Drupal 6, writing the modules, and finally testing the modules. We're currently working on a detailed list of changes that were made which should be posted soon.

 
soc/ideas2009.txt · Last modified: 2009/03/27 17:10 by gchaix
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki