Category:Summer Coding 2010 ideas
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 JBoss.org ideas? http://community.jboss.org/wiki/GoogleSummerofCode2010
- 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.
- 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.
- 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.
Summary of idea: Various ideas related to RHQ: http://rhq-project.org
Contacts: Heiko W. Rupp <hwr @ redhat.com >, pilhuhn on irc.freenode.net/#rhq
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 http://rhq-project.org/display/RHQ/Ideas
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 fedoraproject.org >, rrix on irc.freenode.net/#fedora-kde
Mentor(s): Ryan Rix rrix on irc.freenode.net/#fedora-kde, Jaroslav Reznik jreznik on irc.freenode.net/#fedora-kde
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.
The main page for this idea is Summer Coding 2010 ideas - PackageDB Enhancements.
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 https://fedorahosted.org/packagedb/wiki/ToDo
The main page for this idea is Summer Coding 2010 ideas - Copr.
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.
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 https://bugzilla.gnome.org/show_bug.cgi?id=612725#c6 for details
The main page for this idea is Summer Coding 2010 ideas - CHASM.
Summary of idea: Various ideas related to CHASM
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 kernel.org 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.
DGC GTK GUI
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: https://fedorahosted.org/fedora-electronic-lab/ticket/73
Contact: Shakthi Kannan , "mbuf" at irc.freenode.net/#fedora-india
Mentor(s): Shakthi Kannan , "mbuf" at irc.freenode.net/#fedora-india
The main page for this idea is http://community.jboss.org/wiki/StudentContributorProjectswithInfinispan.
Summary of idea: Improvements to Infinispan project (http://www.jboss.org/infinispan)
Contacts: Manik Surtani <manik @ jboss.org>
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 http://community.jboss.org/wiki/StudentContributorProjectswithInfinispan
The main page for this idea is http://seamframework.org/Community/StudentProjects.
Summary of idea: Improvements and new features to seam Framework (http://seamframework.org/)
Contacts: Pete Muir <pmuir @ redhat.com>
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 http://seamframework.org/Community/StudentProjects
FSoC - Four Seasons of Code
The main page for this idea is Summer Coding 2010 ideas - FSoC.
Summary of idea: Student Project Management System
Contacts: Shreyank Gupta <shreyankg @ fedoraproject.org >, Shrink on irc.freenode.net/#fedora-india
Mentor(s): Shreyank Gupta
Notes: The idea is to develop an application which would allow Mentors and Students to collaborate effectively and get the process of mentoring automated.
Kronikarz - Simple Tool for Desktop Backup / Restore
The main page for this idea is Summer Coding 2010 ideas - Kronikarz - shortinfo.
The main page for Summer Coding 2010 ideas is Category:Summer Coding 2010 ideas.
Summary of idea: Handy graphical tool for archiving settings of desktop applications. This tool will be useful for users who:
- want to simply backup / restore look-and-feel and settings of desktop applications;
- frequently migrate from one distribution to another;
- have more then one device and want to sync settings.
Contacts: Alexei Panov
Mentor(s): Alexei Panov
Notes: Tool can be written to work with plugins (preferrable) or just bunch of configuration files to describe backup / restore / sync methods and enable support for certain application.
- Easy search and select installed applications for backup / restore / sync
- Can work as application or as daemon
- Has scheduler and backup / restore / sync settings (archive type, passwords, compression rate, additive/solid, etc.)
- Custom selection of applications for archiving (one, group, all, etc.)
- Restoring data from archive with tracking of current application, nonexistent on target machine applications should be reinstalled from PackageKit
- Including user selected files in archive for restoring on target machine (possibly searching and automatic including configuration files or files of specified types).
Unified Mobile Sync
The main page for this idea is Summer Coding 2010 ideas - Unified Mobile Sync - shortinfo.
The main page for Summer Coding 2010 ideas is Category:Summer Coding 2010 ideas.
Summary of idea: Synchronization tool for mobile devices. The creation of tool for data synchronization between mobile devices and desktop, such as contacts, calendar, schedule, tasks, messages. Today mobility is a major trend, so enabling synchronization between mobile and desktop is important for Linux desktop adoption.
Contacts: Alexey Vasyukov
Mentor(s): For the moment Alexey Vasyukov
Notes: Proposed features:
- Synchronization of contacts and calendar (required), tasks and messages (desired)
- Support for popular mobile devices, simple extensibility for new gadgets via plugins
- Support for popular desktop applications, simple extensibility for other via plugins
- Simple graphical synchronization tuning tool – what to synchronize, scheduling, rules (filters, conflict resolution, etc.)
- Enabling mobile device backup and restore
- Desirably running not only on Linux, but also on Windows and MacOS (TBD)
- Think about future integration with open source collaboration suites and unified communication systems.
The current stage (stage 1) is about research and architecture design. It can not be stuck to certain technologies. You need a broad vision of different technologies to be successful at this stage.
Current stage will take at least 2-3 months. After it we will determine coding tasks and timeline and proceed to stage 2 - prototype implementation.
The tasks for current stage:
- Find out how to upload/download to/from popular mobile devices (Android, iPhone, Symbian, PalmOS, Win Mobile, BB, etc) contacts, messages, calendars, todos, media content, etc. It includes studying what data is accessible, in what format we are to process it, what protocols-libraries-APIs should be used. As a result we should get clear understanding what and how can be synced for different devices. This task will require gathering and reading tons of technical documentation and writing code to check if documentation is really true. I can not predict what programming languages, libraries, standards and protocols you will encounter.
- Find out how to upload/download to/from popular desktop apps (Evolution, Thunderbird, KDE PIM, Outlook, etc) contacts, messages, calendars, todos, media content, etc. Once again, it includes studing what is accessible, in what format, via which channels. As a result we should get clear understanding what and how can be synced with different apps. This task will require, similarly with the previous one, reading documentation and writing tests. Once again, I can not predict what programming languages, libraries, standards and protocols you will encounter.
- Find out how to integrate mobile sync into current system infrastructure for Linux desktop (dbus, udev, PackageKit, etc) and, probably, Windows desktop (???). This task will require very good knowledge of system design.
- Prepare concept of GUI application and implement the first version (with placeholders instead of real sync plugins). This task will require knowledge of cross-platform programming with Python or C/C++ and GTK/Qt/etc. Knowledge of GUI design and usability will be a big advantage.
- Prepare the architecture based on the results of tasks #1-4. The architecture should meet the requirements . Determine tasks for complete UMS implementation.
From my point of view each of the tasks #1-4 will require few person-months. Task #5 will be solved collaboratively.
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.