Editing GSoC 2010/Project ideas
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 40: | Line 40: | ||
| Chirematic || View the world around you as if color blind or various other vision impairments || Maemo SDK, packaging, GStreamer || epage || epage || Possibly beneficial to desktop Linux as well | | Chirematic || View the world around you as if color blind or various other vision impairments || Maemo SDK, packaging, GStreamer || epage || epage || Possibly beneficial to desktop Linux as well | ||
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
- | | ''Google Reader Offline'' || Creating an application synchronize with Google Reader to enable offline-reading of Google Reader's contents. || maemo SDK, packaging an installer || bob || Frederico Schardong ([[User:frede|frede]]) || | + | | ''Google Reader Offline'' || Creating an application synchronize with Google Reader to enable offline-reading of Google Reader's contents. || maemo SDK, packaging an installer || bob || Frederico Schardong ([[User:frede|frede]]) || |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
|-style="background:" | |-style="background:" | ||
- | + | | || || || || || | |
- | + | ||
- | | || || || || || | + | |
|} | |} | ||
Line 57: | Line 49: | ||
|- style="background-color: #eef" | |- style="background-color: #eef" | ||
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments | ! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments | ||
- | |||
- | |||
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
| ''RetroShare Messenger'' || Porting RetroShare Messenger || maemo SDK, packaging an installer || http://retroshare.sf.net - http://retromessenger.sf.net || || There has been talk about it on the [[http://lists.freedesktop.org/archives/telepathy/2010-March/004361.html telepathy mailing list]]. | | ''RetroShare Messenger'' || Porting RetroShare Messenger || maemo SDK, packaging an installer || http://retroshare.sf.net - http://retromessenger.sf.net || || There has been talk about it on the [[http://lists.freedesktop.org/archives/telepathy/2010-March/004361.html telepathy mailing list]]. | ||
Line 70: | Line 60: | ||
| ''OTR Support for Telepathy'' || Integrate libotr support in the existing protocol stack || maemo SDK, packaging, telepathy, some crypto || || || This will require supporting it in Telepathy, the spec is being worked on. (but its doable) | | ''OTR Support for Telepathy'' || Integrate libotr support in the existing protocol stack || maemo SDK, packaging, telepathy, some crypto || || || This will require supporting it in Telepathy, the spec is being worked on. (but its doable) | ||
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
- | | Answering Machine/Call Rejector || Answering machine and call rejector based on black lists and white lists. [http://maemo.org/community/brainstorm/view/answering_machine_on_n900/ Brainstorm entry], [http://maemo.org/community/brainstorm/view/call_rejector-developers_needed/ Brainstorm entry] || Maemo, Qt, GStreamer || [http://maemo.org/community/brainstorm/view/answering_machine_on_n900/ Brainstorm entry], [http://maemo.org/community/brainstorm/view/call_rejector-developers_needed/ Brainstorm entry] || | + | | Answering Machine/Call Rejector || Answering machine and call rejector based on black lists and white lists. [http://maemo.org/community/brainstorm/view/answering_machine_on_n900/ Brainstorm entry], [http://maemo.org/community/brainstorm/view/call_rejector-developers_needed/ Brainstorm entry] || Maemo, Qt, GStreamer || [http://maemo.org/community/brainstorm/view/answering_machine_on_n900/ Brainstorm entry], [http://maemo.org/community/brainstorm/view/call_rejector-developers_needed/ Brainstorm entry] || || An answering machine (with sound and possibly video) is a mildly complex gstreamer application |
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
| sharing-service-telepathy || Integrate IM file transfer support with Maemo through the Sharing plugin system || Maemo SDK, packaging, Telepathy, Maemo Sharing Plugin system || epage || epage || I think this is feasible but the fact it hasn't been done yet makes me a bit hesitant. Jonny Lamb (who did the file transfer UI) already tried it. | | sharing-service-telepathy || Integrate IM file transfer support with Maemo through the Sharing plugin system || Maemo SDK, packaging, Telepathy, Maemo Sharing Plugin system || epage || epage || I think this is feasible but the fact it hasn't been done yet makes me a bit hesitant. Jonny Lamb (who did the file transfer UI) already tried it. | ||
Line 78: | Line 68: | ||
| ''Canola UPNP plugin'' || Creating a plugin for Canola to deal with UPNP, possibly using the eupnp library || python, upnp || lfelipe || lfelipe || | | ''Canola UPNP plugin'' || Creating a plugin for Canola to deal with UPNP, possibly using the eupnp library || python, upnp || lfelipe || lfelipe || | ||
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
- | | | + | | ''Porting Canola to Maemo5 and beyond'' || This task involves making sure that Canola works on Maemo5 and also making changes to integrate it better, possibly switching from LMS to Tracker, etc. Taking Meego under consideration is a big plus. || python, C || lfelipe || lfelipe || |
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
| aGLESory || Adapt or implement a flexible OpenGL wrapper for Maemo. || OpenGL, libraries and gcc, packaging, documentation, maemo SDK || Flandry || [[User:thp|thp]] || This really needs no introduction...we all know how huge it would be to have a painless wrapper for at least basic OpenGL functionality. This project would be about getting someone to blaze the path and mark it clearly. | | aGLESory || Adapt or implement a flexible OpenGL wrapper for Maemo. || OpenGL, libraries and gcc, packaging, documentation, maemo SDK || Flandry || [[User:thp|thp]] || This really needs no introduction...we all know how huge it would be to have a painless wrapper for at least basic OpenGL functionality. This project would be about getting someone to blaze the path and mark it clearly. | ||
|-style="background:Orange" | |-style="background:Orange" | ||
- | | Desktop Couch || Port | + | | Desktop Couch || Port Desktop Couch to the maemo platform and integrate it with various applications (contacts, calender, etc) http://www.freedesktop.org/wiki/Specifications/desktopcouch/Documentation || Desktop Couch, python packaging, documentation, maemo SDK || || || |
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
| Locality || An Android [http://the-gadgeteer.com/2009/05/29/locale-for-android-review/ Locale] clone to automate various aspects of the OS and life || Maemo SDK, packaging, UI, possibly DBus || epage || epage, [[User:thp|thp]] || Beneficial to desktop Linux as well. Shepherd sounds like it might fill a similar role and is currently in development. | | Locality || An Android [http://the-gadgeteer.com/2009/05/29/locale-for-android-review/ Locale] clone to automate various aspects of the OS and life || Maemo SDK, packaging, UI, possibly DBus || epage || epage, [[User:thp|thp]] || Beneficial to desktop Linux as well. Shepherd sounds like it might fill a similar role and is currently in development. | ||
Line 91: | Line 81: | ||
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
| MeeGo: power usage tuning || Linux is far from being power-optimal, not to say the complex and bulky desktop components. There are so many things can be done in this area for the vast collection of free software running on MeeGo that I don't know which is most important yet. Do you know it? || OS, profiler || Yan Li ([[User:yanli|yanli]]) || Yan Li ([[User:yanli|yanli]]) || [http://www.lesswatts.org/projects/powertop/ PowerTOP] is a good start. The hard part in this idea is the participant has to have a power meter to measure the real-time power usage, or you have no way to know your progress. Some computer science or EE labs in universities have that meter. But there are still tasks can be done even without a power meter, like running major software parts within a profiler to identify and optimize hot spots. | | MeeGo: power usage tuning || Linux is far from being power-optimal, not to say the complex and bulky desktop components. There are so many things can be done in this area for the vast collection of free software running on MeeGo that I don't know which is most important yet. Do you know it? || OS, profiler || Yan Li ([[User:yanli|yanli]]) || Yan Li ([[User:yanli|yanli]]) || [http://www.lesswatts.org/projects/powertop/ PowerTOP] is a good start. The hard part in this idea is the participant has to have a power meter to measure the real-time power usage, or you have no way to know your progress. Some computer science or EE labs in universities have that meter. But there are still tasks can be done even without a power meter, like running major software parts within a profiler to identify and optimize hot spots. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
|-style="background:" | |-style="background:" | ||
| || || || || || | | || || || || || | ||
Line 125: | Line 102: | ||
| MeeGo: Better handling of X failures || X should be running well and unknown to end user for most time, but it does fail, sometimes. When it fails, MeeGo should handle it gracefully. Currently MeeGo's uxlauncher just keeps fingers crossed and restarts X, but sometimes things go really wrong and X can't start at all, and the users are faced a dead-loop with screen flickrs every 10 seconds. We may need a safe-mode, or learn from Ubuntu's [https://wiki.ubuntu.com/BulletProofX BulletProofX] || MeeGo uxlaunch, C, X || Yan Li ([[User:yanli|yanli]]) || Yan Li ([[User:yanli|yanli]])|| We should start simple with a graphical notification, stating X can't start, when detected X has 2 failures in a row. Then add a safe mode, in which users can configure X accordingly | | MeeGo: Better handling of X failures || X should be running well and unknown to end user for most time, but it does fail, sometimes. When it fails, MeeGo should handle it gracefully. Currently MeeGo's uxlauncher just keeps fingers crossed and restarts X, but sometimes things go really wrong and X can't start at all, and the users are faced a dead-loop with screen flickrs every 10 seconds. We may need a safe-mode, or learn from Ubuntu's [https://wiki.ubuntu.com/BulletProofX BulletProofX] || MeeGo uxlaunch, C, X || Yan Li ([[User:yanli|yanli]]) || Yan Li ([[User:yanli|yanli]])|| We should start simple with a graphical notification, stating X can't start, when detected X has 2 failures in a row. Then add a safe mode, in which users can configure X accordingly | ||
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
- | | MeeGo: online music services support || It's convenient and fun to have direct access to online music services from the media player, as you can see in Amarok and GNOME Rhythmbox. But MeeGo Media Player lacks this support for now and we should address it.|| C, Clutter || Yan Li ([[User:yanli|yanli]]) || Yan Li ([[User:yanli|yanli]]) | + | | MeeGo: online music services support || It's convenient and fun to have direct access to online music services from the media player, as you can see in Amarok and GNOME Rhythmbox. But MeeGo Media Player lacks this support for now and we should address it.|| C, Clutter || Yan Li ([[User:yanli|yanli]]) || Yan Li ([[User:yanli|yanli]]) || You have to read through MeeGo Media Player's code and write patches to add this new function. |
|-style="background:LightGreen" | |-style="background:LightGreen" | ||
| UPnP Remote Access || [https://upnp.org UPnP] was originally designed for (private) home networks but recently UPnP forum came-up with a [http://upnp.org/specs/ra/ra1.asp specification] to bridge home networks securely across the globe. Since Maemo has a nice UPnP frameworks on it, implementing a service that implements this spec in question will be a very exciting and enjoyable project. || C or Vala || Zeeshan Ali ([[User:zeenix|zeenix]]) || Zeeshan Ali ([[User:zeenix|zeenix]])|| This is very similar to [http://coherence-project.org/wiki/MirabeauHowTo?redirectedfrom=Mirabeau Mirabeau] project but the difference is that this project will not be specific to XMPP and will use existing frameworks/libs on Maemo. | | UPnP Remote Access || [https://upnp.org UPnP] was originally designed for (private) home networks but recently UPnP forum came-up with a [http://upnp.org/specs/ra/ra1.asp specification] to bridge home networks securely across the globe. Since Maemo has a nice UPnP frameworks on it, implementing a service that implements this spec in question will be a very exciting and enjoyable project. || C or Vala || Zeeshan Ali ([[User:zeenix|zeenix]]) || Zeeshan Ali ([[User:zeenix|zeenix]])|| This is very similar to [http://coherence-project.org/wiki/MirabeauHowTo?redirectedfrom=Mirabeau Mirabeau] project but the difference is that this project will not be specific to XMPP and will use existing frameworks/libs on Maemo. | ||
|-style="background:" | |-style="background:" | ||
| mAuth (pronounced moth) || The N900 is a very powerful device, however we can't shake away the fact that many of us still use desktops on a daily basis. Using username/password authentication is highly insecure, because it forces the repeated typing of the same credentials in the same room, roughly at the same time every day. One option for this are smart cards. However they are expensive and the concepts behind them are extremely complicated for anyone who doesn't work in the industry, and as such implementing them at home would be a nightmare. One solution around this would be to have the N900 (or any other NIT for that matter) emulate being a smart card, and use bluetooth to connect to the computer. The authentication and encryption certificates are stored on the N900 and provided to the computer when in bluetooth range, however as soon as the N900 is taken away, the session is locked as the computer believes the "smart card" has been removed. || - Maemo SDK to create the smart card emulator daemon - Bluetooth networking or bluetooth bi-directional communication - PC/SC driver for Windows - Excellent documentation - great packaging || [[User:crashanddie|crashanddie]] 07:46, 20 February 2010 (UTC) || || | | mAuth (pronounced moth) || The N900 is a very powerful device, however we can't shake away the fact that many of us still use desktops on a daily basis. Using username/password authentication is highly insecure, because it forces the repeated typing of the same credentials in the same room, roughly at the same time every day. One option for this are smart cards. However they are expensive and the concepts behind them are extremely complicated for anyone who doesn't work in the industry, and as such implementing them at home would be a nightmare. One solution around this would be to have the N900 (or any other NIT for that matter) emulate being a smart card, and use bluetooth to connect to the computer. The authentication and encryption certificates are stored on the N900 and provided to the computer when in bluetooth range, however as soon as the N900 is taken away, the session is locked as the computer believes the "smart card" has been removed. || - Maemo SDK to create the smart card emulator daemon - Bluetooth networking or bluetooth bi-directional communication - PC/SC driver for Windows - Excellent documentation - great packaging || [[User:crashanddie|crashanddie]] 07:46, 20 February 2010 (UTC) || || | ||
- | |-style="background: | + | |-style="background:" |
| Robotics Simulator || Bring a full-blown robotics simulator to Maemo/MeeGo. For the start, the 2.5D simulator Player/Stage (http://playerstage.sf.net) would be ported and a simple GUI be written. Later integration with Fawkes (http://www.fawkesrobotics.org) can provide some nice demos and scripting environment to start into robotics. If there is interest in this project some studies are needed to check whether the device is generally computationally powerful enough for simple scenarios. Although not a classic Maemo application, this can be seen as an educational effort to get students interested and start playing with (virtual) robots. || Maemo SDK, packaging, Player/Stage, Fawkes, background in robotics software strongly recommended || timn || || Given a mentor I would like to pursue this project over the summer. It can be an eye catcher for the N900, if you can have a simulated robot on the device and instruct it to accomplish tasks. | | Robotics Simulator || Bring a full-blown robotics simulator to Maemo/MeeGo. For the start, the 2.5D simulator Player/Stage (http://playerstage.sf.net) would be ported and a simple GUI be written. Later integration with Fawkes (http://www.fawkesrobotics.org) can provide some nice demos and scripting environment to start into robotics. If there is interest in this project some studies are needed to check whether the device is generally computationally powerful enough for simple scenarios. Although not a classic Maemo application, this can be seen as an educational effort to get students interested and start playing with (virtual) robots. || Maemo SDK, packaging, Player/Stage, Fawkes, background in robotics software strongly recommended || timn || || Given a mentor I would like to pursue this project over the summer. It can be an eye catcher for the N900, if you can have a simulated robot on the device and instruct it to accomplish tasks. | ||
|-style="background:" | |-style="background:" | ||
- | |Radiator: Podcasting + conferencing + Twitter||The premise here is an audio conferencing app that supports 2 or more co-hosts collaborating in the same session. Audio can be saved for podcasts. For live events, audiences could "call" in or comment via twitter. QT is the preferred development platform, with hope for a mobile client. More info plus discussion: [http://tabulacrypticum.wordpress.com/2010/03/14/qt-podcasting-conferencing-twitter/ Blog article]||Qt, audio, networking, APIs||Randall Arnold ([[User:texrat|texrat]])||Randall Arnold | + | |Radiator: Podcasting + conferencing + Twitter||The premise here is an audio conferencing app that supports 2 or more co-hosts collaborating in the same session. Audio can be saved for podcasts. For live events, audiences could "call" in or comment via twitter. QT is the preferred development platform, with hope for a mobile client. More info plus discussion: [http://tabulacrypticum.wordpress.com/2010/03/14/qt-podcasting-conferencing-twitter/ Blog article]||Qt, audio, networking, APIs||Randall Arnold ([[User:texrat|texrat]])||Randall Arnold||Expectation is that live and saved sessions would both be possible. There has been concern that audio quality from a multi-sourced event would be poor, but I challenge developers to test that. Otherwise a live option is not practical |
|-style="background:" | |-style="background:" | ||
| || || || || || | | || || || || || |
Learn more about Contributing to the wiki.