Fall2009/Course Project/Individual Projects

From OpenSourceSoftwarePractice

Jump to: navigation, search

Contents


What to do

  • Select an Open Source project (OSI approved license)
  • Join their community
    • Mailing list or forum
  • Contribute to the project
    • A bug fix
    • A new feature
  • Note that the CENTRAL PURPOSE of the project is not to "develop software", but for you to be exposed to the practices of an Open Source community.

Expected level of effort

  • 4 hours a week, for 4 weeks of class = 16 hours
  • In programming time, this is equivalent to any of the following (for the logic purist: these are exclusive ors (XOR) )
    • 500 lines of code for a project that started from scratch
    • 20 lines of code patch (bug fix or feature implementation) for a project of the caliber of ITK, VTK, CMake, ParaView
    • 10 lines of code patch (bug fix or feature implementation) for a project of the caliber of GCC or Apache.

These are guidelines of individual effort.


If you are working in a group, then the total level of effort for the group is expected to be the above, multiplied by the number of team members.

Evaluation

The amount of effort will be evaluated based on:

  • Number and size of messages posted to the project mailing list or forum
  • Edits (quality and size) made to the project Wiki (or equivalent community-coordination medium)
  • Lines of code of contributions (to be weighted by complexity of the code itself, and by the size of the project).
    • To clarify: it is understood that contributing to a large project is harder than contributing to a small project.

Candidate Projects

HFOSS Projects

What is HFOSS

Projects

  • Sahana
    • http://www.cs.trincoll.edu/hfoss/wiki/Project/SahanaVM
    • The Sahana Volunteer Management Project: "helps governments and non-governmental agencies coordinate relief work in a disaster situation. HFOSS contributions include a volunteer tracking system and a credential tracking system."
  • OpenMRS
    • http://openmrs.org/wiki/OpenMRS
    • Is an open source medical records system deployed in several developing countries. HFOSS contributions include a notes system and touchscreen keyboard support.
  • InSTEDD Evolve
    • http://instedd.org/
    • Uses machine learning to sift through news articles from around the world and identify disease outbreaks as they happen.
  • GNOME Accessibility Project

RCOS Projects


Kitware Projects

Other Projects

  • Epiar (ep-ee-are) is an open source computer game, in which the player navigates space from planet to planet, saving money to buy ship upgrades and new ships. The player can also join mercenary missions, attack other ships to steal their money and technology, and explore the universe. The game combines the action/arcade elements of aircraft dogfighting with the strategy of war games and the openness of role playing games to create this entertaining experience
  • Firmant (?) is an open source blog engine designed by coders, for coders. It provides a strong basis for a secure, efficient blog that uses an SCM for a backend. Firmant is currently looking for someone to write the administrative interface (with tests). The administrative interface should be either CLI or Curses (no web or gui).

GNOME Projects

  • See here http://live.gnome.org/GnomeLove, for all details and links to the following projects
  • Some projects also have a favorite entry point, or additionnal info for GNOME Lovers:
    • GTK+: See the GtkLove bug list and the GtkTasks page for volunteers.
    • GnomeKeyringManager - Project developed only by GNOME lovers. Go there to learn and contribute to it.
    • Lockdown Editor - A simple idea in need of developers.
    • GStreamer task list
    • GnomeApplets
    • GnomeGames
    • Gedit
  • The GNOME System Tools task list.
    • Totem: http://mail.gnome.org/archives/gnome-love/2004-April/msg00023.html.
    • Yelp
    • Metacity: The HACKING and code overview files orient you to the code, point out relevant standards, explain a lot of the specialized utilities for testing metacity, show how to debug your code (debuggers don't work well for Metacity), and provide a list of tasks you can work on.
    • Epiphany: There are lots of older, sometimes untargeted bugs for Epiphany that the development team doesn't get around to. Help would be most welcome!
    • GnomePanel
    • Beagle Roadmap/TODO
  • Other applications:
    • Glom (Easy database UIs) has a task list suitable for new contributors.
    • Silky - a graphical SILC client - is looking for more developers.
    • xchat-gnome has a list of tasks suitable for new developers.

Mozilla Projects

KDE Projects

Group Rules

  • You can work individually, or
  • Join groups up to three students

Deadlines

  • Joining project : October 30
  • Identifying feature/ bug : November 2
  • Implementation should be done by : December 1st
  • Presentations will take place on December

Projects

Retrieved from "http://public.kitware.com/OpenSourceSoftwarePractice/index.php/Fall2009/Course_Project/Individual_Projects"
Personal tools