From Fedora Project Wiki

Line 71: Line 71:
== FSoC - Four Seasons of Code ==
== FSoC - Four Seasons of Code ==
{{:Summer Coding 2010 ideas - FSoC - shortinfo}}
{{:Summer Coding 2010 ideas - FSoC}}
[[Category:Summer Coding 2010]]
[[Category:Summer Coding 2010]]

Revision as of 08:41, 13 April 2010

This page holds all the ideas suggested by community members for the Fedora Summer Coding 2010 program.

Scroll to the bottom of this page for all the pages in the 2010 ideas category.

Other ideas that were incomplete or worth considering from the past are found at Summer coding ideas for 2009.

Looking for ideas?


  1. Think in terms of use cases.
    If you provide a use case and some ideas of how to solve, you give more room for students to put in their own ideas and passion.
    Consider if that is possible for each of your project ideas.
  2. Prepare a project idea page, part of which is included on this page.
    To learn how to add an idea to this page, read How to create an idea page for Summer Coding.
  3. Use talk page to discuss ideas and proposals.
    Use the discussion tab (Talk:Name of idea) page for all discussion about an idea.
    Idea pages should be renamed as proposals when accepted, and all discussion about the proposal should also go in the talk page.

Idea page sample

The main page for this idea is Summer Coding 2010 ideas - Idea page sample.


Summary of idea:





The main page for this idea is Summer Coding 2010 ideas - RHQ.

Status: Proposed

Summary of idea: Various ideas related to RHQ:

Contacts: Heiko W. Rupp <hwr @ >, pilhuhn on

Mentor(s): Heiko W. Rupp

Notes: Ideas are e.g. better visual representation of the inventory (graphical forests), new graphing code for metrics (as DOM+CSS+JS versions), allowing different availability check interval for 'important' resources, separating agent heart beat from availability messages or combining data from different resources and types to trigger alerts on this combined data ("Correlation units"). Other ideas are very welcome. Also check the Ideas wiki page at

KDE Netbook Spin

The main page for this proposal is Summer Coding 2010 ideas - KDE Netbook Spin.

Status: Accepting Applications

Summary of idea: The creation of an official KDE Netbook Edition Spin for Fedora 14

Contacts: Ryan Rix < rrix >, rrix on

Mentor(s): Ryan Rix rrix on, Jaroslav Reznik jreznik on

Welcome Wizard

The main page for Summer Coding 2010 ideas is Summer Coding 2010 ideas - Welcome Wizard.

Status: Idea

Summary of idea: A step by step process of joining the Fedora Project.

Contacts: Mike McGrath

Mentor(s): Mike McGrath

Notes: Right now when new users sign up for an account, they have NO idea what to do next. One common thing is applying for a bunch of seemingly random groups, then trying to ssh to fedorapeople. Then just having your applications sit there... forever never getting approved.

I'd like for the account system to have a simple wizard interface (via a plugin), welcomes users, explains how Fedora works and explains how to apply for groups and what to expect. We may have to come up with a standard way to apply for groups, to be discussed.

PackageDB Enhancements

The main page for this idea is Summer Coding 2010 ideas - PackageDB Enhancements.

Status: Proposed

Summary of idea: The Fedora PackageDB contains information that both developers and end users would find useful about the applications and packages in Fedora. There are a large variety of changes that could be useful for it ranging from the mundane (example: porting to TurboGears2, adjusting the way we link between the Application and Package interfaces) to redesigning the database model, or including new features.

Contacts: Toshio Kuratomi

Mentor(s): Toshio Kuratomi

Notes: Some ideas are listed on


The main page for this idea is Summer Coding 2010 ideas - Copr.

Status: Proposed

Summary of idea: Copr (Cool Other Package Repo) is a Fedora project to help make building and managing third party package repositories easy. Copr is being implemented this summer by Seth Vidal and Toshio Kuratomi. They would welcome help from interested students.

Contacts: Toshio Kuratomi(abadger1999)

Mentor(s): Toshio Kuratomi(abadger1999)

Notes: More information about Copr

Gnome - Nautilus Search dialog

The main page for this idea is Summer Coding 2010 ideas - Gnome - Nautilus search.

Status: Idea

Summary of idea: Nautilus is the default file manager for Gnome desktop. The current state of the search dialog is suboptimal, our goal is to make it more rich and provide more options. For example, when we had set Tracker as the primary search engine, we also committed users to use their fulltext search by default. An option switching between filename-based matching and fulltext search would be great addition. Additional filters would also be a great asset.

Contacts: Tomáš Bžatek

Mentor(s): Tomáš Bžatek

Notes: See upstream bug for details


The main page for this idea is Summer Coding 2010 ideas - CHASM.

Status: Idea

Summary of idea: Various ideas related to CHASM

Contacts: Rob Escriva, Ben Boeckel (mathstuf)

Mentor(s): Rob Escriva, Ben Boeckel (mathstuf)

Notes: CHASM, the Cryptographic-Hash-Algorithm-Secured Mirroring solution, is a project that is to help alleviate a lot of the pains that mirrors have in organizing and verifying their content. The project can be thought of as a stateful rsync daemon in some respects, and solves a problem that and a number of other large mirroring infrastructures have been looking into for several years now. This is ultimately a project that will be used by a greater portion of the larger mirroring infrastructures and as such has a lot of need for high performance and good design.


The main page for this Summer Coding 2010 ideas is Summer Coding 2010 ideas - DGC GTK GUI.

Status: Proposed

Summary of idea: The proposed work is to write the GTK GUI for Digital Gate Compiler (DGC) to use the latest GTK+ 2.0 API. This is Fedora Electronic Lab ticket #73:

Contact: Shakthi Kannan , "mbuf" at

Mentor(s): Shakthi Kannan , "mbuf" at



The main page for this idea is

Status: Proposed

Summary of idea: Improvements to Infinispan project (

Contacts: Manik Surtani <manik @>

Mentor(s): Manik Surtani

Notes: Ideas are

  • ISPN-272 Recover from transaction failures
  • ISPN-127 Ability to bring up/take down nodes based on SLAs
  • ISPN-374 Add event handling to HotRod
  • ISPN-57 Support Google App Engine
  • ISPN-200 Distributed queries
  • ISPN-262 Geographically distributed data grid
  • ISPN-263 Handle MERGE events to deal with split brains

Please check details at the Student/Contributor Projects with Infinispan wiki page at

Seam Framework

The main page for this idea is

Status: Proposed

Summary of idea: Improvements and new features to seam Framework (

Contacts: Pete Muir <pmuir @>

Mentor(s): Pete Muir

Notes: Ideas are

  • JBoss ESB integration with CDI
  • Errai (GWT) integration with CDI
  • Errai (GWT) integration with CDI events
  • Errai (GWT) integration with Seam Security
  • Extensible project management tooling environment (based on Maven and Maven Archetypes)
  • Conversations with remote EJBs

Please check details at the Student Projects wiki page at

FSoC - Four Seasons of Code

The main page for Summer Coding 2010 ideas is Summer Coding 2010 ideas.

Status: Accepted

Summary of idea: Student Project Management System

Contacts: Shreyank Gupta <shreyankg @ >, Shrink on

Mentor(s): Shreyank Gupta


The idea is to develop a web-based application which would allow Mentors and Students to collaborate effectively and get the process of mentoring automated.

The Idea

The idea Student Project Management System that would probably turn out to be a good idea should include the following:

  [a] accept and flag proposals
  [b] allow milestones from multiple projects to be included in a calendar
  [c] allow automated reminders to be generated against milestones
  [d] allow projects to be signed-off by mentors to denote completion
  [e] allow link to repositories of code to be mapped with the project
  [f] allow creation of a Project Dashboard with proposed mentors

The following aspects be considered for inclusion as part of the process flow:

  [a] Students receive a rigid time-frame of 15 days from the date of registration to propose a project
  [b] Any student / student group that fails to meet condition [a] above, receives an automated notification from the system providing a 3 day period post which their account would be flagged inactive
  [c] For any proposal / project a student / student group desires to undertake, provide a set of qualifying tasks to assess the capability of the student / student group to
  [d] Allow Certificate of Participation to be generated only if the project has a sign-off from the mentor

To ensure that the mentors feel part of the system, the following could come in handy :

Request all interested mentors to propose at least a single project for which they would like a student / student group to be working on. The proposal for the project should ideally include the following properties:

  [i] Project Definition
  [ii] Project Scope
  [iii] Estimated Time
  [iv] Project Description (including toolkits, frameworks)
  [v] A rating of complexity (initially arbitrary)
  [vi] Project Deliverables (including artifacts, documentation)

In short, the system should allow mentors and students to:

  • create accounts
  • have individual and project centric dashboards
  • act as a repository for formal documentation
  • allow calendaring for automated reminders
  • include a version control system
  • include a ticketing system

(the last two can be optionally tweaked for projects with existing upstreams)

The Prototype

The development snapshot can be accessed at

Existing Features:

User Management:

  • Authentication of three different types of users:
0. Guest user (unauthenticated user)
1. Admin
2. Mentors
3. Students
  • Project listing.
  • User listing.
  • User profile with information about project activities.

Projects Ideas:

  • Mentors and Students able to add project ideas.
  • Mentors can volunteer to mentor a project of their choice.
  • Project proposers and mentors can edit project ideas.
  • Project proposers can delete project ideas without any mentor.
  • Admin can add/edit/delete all projects.

Proposals from students:

  • Students able to submit proposals for all projects.
  • Students able to edit proposals.
  • Mentors can accept/reject proposals.
  • Only one proposal per student gets accepted.

Project Tasks:

  • Project has many atomic tasks with ETA.
  • While accepting a proposal, mentor allocates tasks to students with deadlines.


  • A user dashboard having current logged-in users project activities.

The Task

  • Improving User and Projects Dashboard
  • Admin Panel
  • Projects Calender
  • Task Journal
  • Mail reminders
  • FAS Integration
  • Modes (Year-round mode/Summer coding mode)
  • Integration with a code repository.
  • Certificate of Participation.


Ruby on Rails


Experience of programming the web.


This category has only the following subcategory.

Pages in category "Summer Coding 2010 ideas"

The following 52 pages are in this category, out of 52 total.