Summer coding ideas for 2012

From FedoraProject

Revision as of 21:36, 2 March 2012 by Mmorsi (Talk | contribs)

Jump to: navigation, search
Idea.png
Please feel free to add your idea here.

Find an idea you like? Want to propose your own? See the Getting Started Guide with GSoC:

http://groups.google.com/group/redhat-summer/web/gsoc-getting-started

You may be interested in ideas from 2011, 2010, 2009 and 2008.

Further, last year accepted ideas from the Fedora Project can be found at GSoC 2011 web site

Contents

Supporting Mentors

Following contributors are also willing to support the GSoC 2012 program. (please feel free to add your self, attach the user page). Sometimes there should be some backing up mentors to mentor if the original mentor get busy with something for a short time period. In such case we need help.

  1. Buddhike Kurera(Bckurera)
  2. Karsten Wade(Quaid)
  3. Susmit Shannigrahi(Susmit)
  4. Mo Duffy (Duffy)
  5. Mo Morsi

Project name

Status:

Summary of idea:

Contacts:

Mentor(s):

Notes:


Web hosting control panel

Status: Proposed - Draft

Summary of idea: develop a free alternative of cpanel / plesk control panels, 100% compatible with fedora, and redhat enterprise Linux. written in python.

Contacts: itamarjp [AT] fedoraproject [DOT] org

Mentor(s): Dennis Gilmore Toshio kuratomi

Notes:


Infrastructure for Fedora contributors and users

Implement a survey infrastructure for the Fedora Project

Status: Proposed - Draft

Summary of idea: Surveys are important to increase the quality of a service, and it is true for the Fedora project as well.(discussions [1]) In this project it is supposed to implement a survey infrastructure facility so that the contributors can use for various activities as per the need.

The concern is to develop a simple web base survey system OR implement a existing survey project and customized as required, so that contributors can easily create surveys and dig for results as well. Linking with the [FAS|FAS] is required. Further it should be compatible with anonymous and open ID so that if the creator set for those authentication the survey should allow those authentications. Statistics and other required reports can be obtained. So that it is easy to analyse.

Contacts: kevin [AT]scrye [DOT] com , bckurera [AT] fedoraproject [DOT] org

Mentor(s): User:Kevin - Mentor, User:Bckurera Co-mentor.

Notes: This idea is improving, please contact for upto-date details.


Design Hub: FLOSS Collaboration for FLOSS Designers

Status: Proposed - Draft

Summary of idea: Free software designers don't have a great set of tools to work with to collaborate with each other and with the community on their design work. With this project, we'd like to make progress towards fixing that. We have some disparate ideas / tools that we'd like to be integrated:

  • Sparkleshare - a git-backed, Dropbox like system that will automatically check in and push files in project directly to a shared git repo
  • Magic Mockup - a coffeescript/javascript you can insert into an SVG of mockups to enable interactive, click-through mockups (see a demo here
  • Design Hub - an idea and a ruby on rails prototype of a web front end that could potentially serve as a front end to git repos with design assets *and* serve as well as a front end to magic mockup mockups in said repos
  • Inkscape is our preferred design tool of choice; it would be great if it had some GUI integration with Magic Mockup, Sparkleshare, and Design Hub

Contacts: duffy at fedoraproject [dot] org

Mentor(s): Mo Duffy, Emily Dirsh

Notes: We can provide a development platform for the web UI at openshift.redhat.com. Also, note this project doesn't just benefit Fedora designers, but it benefits all FLOSS designers.

Implement a unit test framework for fedpkg and rpkg

Status: Proposed - Draft

Summary of idea: Unit tests are good. Testing is good. fedpkg and it's backend rpkg is a growing code base, gaining more and more contributors. It lacks a unit test framework which would be very beneficial to the code base for making sure contributions don't break the code in subtle ways.

Contacts: jkeating [AT]redhat [DOT] com

Mentor(s): User:jkeating - Mentor

Notes: This project is in python.


mw enhancements

Status: Proposed

Summary of idea: mw is a command-line program that pretends to be a version control system for MediaWiki-based sites. It should eventually help people who are console nuts (like me) edit MediaWiki-based wikis without having to shout at their web browser.

Contacts: Ian Weller

Mentor(s): Ian Weller

Notes: Here are some ideas for students: User:Ianweller/mw thoughts


Applications for desktop end users

These are coding projects that benefit end users of the Linux desktop.

Integrate Proxy Settings and Network Connections(Locations)

Status: Proposed

Summary of idea: The system should use an appropriate networking profile (e.g. Proxy settings) for each network connection.

Gnome 2 had a concept of network locations in its Network Proxy configuration window. However, user should selected the appropriate location whenever he moves between networks. This idea is about providing an integration between NetworkManager and Desktop environments so that a user can create network profiles for each network location(connection) providing appropriate settings like proxy settings which is the main proposed setting here. NetworkManager can have a "Network Location" concept: for wireless networks, usually the name of the network (ESSID) is usually enough. For wired connections, DHCP servers can and usually do provide network's domain name, which can be used as the name of the location. It is nice if a user can associate each network location with a network settings profile which will be used whenever the user is connected to that network automatically. So, when you connect to a network, a corresponding network settings profile is activated automatically.

Contacts: Hedayat Vatankhah

Mentor(s):

Notes: There is an entry with some description in NetworkManager TODO which should be considered for the implementation

Bringing the Fedora Desktop to the Cloud

Status: Proposed

Summary of idea: Aeolus is an umbrella project that provides an open source API which to control any number of backend proprietary cloud providers. It allows us to write tooling that is able to deploy, monitor, and manager instances to any cloud provider such as EC2 or OpenStack in a Free and Open Manner. We need more tooling to interface with the various Aeolus components from the Fedora desktop (or any other) in novel ways such as command-line and gtk-based applications to deploy instances to the cheapest cloud provider or the one with the fastest response time, to monitor running instances using various visualizations, and more closely integrate local data and code w/ that on the cloud.

Contacts: Mo Morsi

Mentor(s): Mo Morsi

Notes: Ping me (mmorsi on freenode) for more info about the Aeolus project. All the components which to build images for the cloud and control instances is in place and ready to go, just drop various bits (they are interoperable and interchangable) into an environment to be able to interact with the cloud, avoiding proprietary interfaces and vendor lockin