Google's summer of code is now in its 7th year, funding student positions over the summer, working with various open source development projects producing code that benefits everyone. GSoC will put up $5000 US to cover the wage of a student during the period between the end of May and the end of August. Students who are interested in participating should scan through the GSoC FAQ for information about the program and how to apply, and scan through the "Project Ideas" listed below for potential projects they might participate in. Or, propose a project of your own and attach it to your application.
Students applying to work with the IDI should , along with a 1 or 2 page proposal mentioning the project they wish to participate in, with a plan describing how they would go about developing or coding the software, and . We'll offer suggestions you can use to enhance the proposal you submit when you register with GSoC.
Mentoring Organisation Applications February 28 to March 11
Google Summer of Code is a very competitive process at IDI. Many more students apply than we have spots available to offer. Students should keep this in mind and plan accordingly. Students can apply for up to two projects at the IDI.
When selecting students there are a number of qualities we look for:
The overarching goal of the Inclusive Design Institute is to help ensure that emerging information technology and practices are designed inclusively from the very beginning. We define inclusive design as design that enables and supports the participation of individuals and groups representing the full range of human diversity. We see disability as a mismatch between the needs of the individual and the service, education, tools or environment provided and accessibility as the adaptability of the system to the needs of each individual. Our research, development, education and service are all grounded in this principle.
The IDI supports open standards - as well as open access and open source wherever possible - to distribute our work as widely as possible and to encourage broad participation in our initiatives. All our work is collaborative.
We are strong advocates of the overlooked principle that people with disabilities should be producers and not only consumers of information, knowledge and culture. Society as a whole is impoverished and deprived if we exclude through action or omission. Inclusion benefits everyone, it should be everyone's concern and, in this digitally transformed reality that we live and work in - where consumption does not consume and space has no limits - there is no downside to inclusion and it is possible to make room for us all.
The following is a list of potential GSoC projects for students. These are only suggested projects, outlining the types of things the ATutor community has been asking for. Students are welcome to suggest their own projects if they have other ideas.
To communicate directly with the ATutor development team, open an IRC session at irc://irc.oftc.net and join the #atutor channel. The core developers are generally around 9:00 to 5:00 Monday to Friday Eastern Standard Time (UTC+5). Though not a requirement, students are advised to login to IRC and interact with the developers. Generally students developers get to know, are the ones chosen to fill the limited number of spots available.
(1 position available)
This project will involve developing an OpenSocial gadget for AChecker, an open source Web content accessibility checker. AChecker evaluates Web content for conformance with various international accessibility standards, to ensure that content will be accessible to everyone, including people with disabilities. With an AChecker Gadget available, users of social networks like iGoogle, MySpace, LinkedIn, Hi5 etc, will be able to evaluate their Web content, and ensure it is not creating barriers for potential visitors to their sites.
In Google Summer of Code 2010, a mobile theme was created for the student view in ATutor. That theme has become part of the ATutor public distribution. For GSoC 2011 we would like to see a student pickup on the existing theme and extend it to include the instructor and administrator views.
In this project the candidate will design and develop a series of mobile templates for ATutor, and a series of stylesheets that adapt these templates to different mobile platforms (Android, iPhone, Blackberry).
The theme will be based on the Savant open source PHP templating system, also used to develop desktop themes for ATutor. Savant allows theme designers to separate the presentation from the data that gets rendered when a Web page is generated.
The candidate students must have a strong grasp of HTML and CSS, have familiarity with PHP, WebKit and Fluid Infusion, and have a good eye for aesthetics, able to create an eye catching design, and able to implement that design as a set of HTML/CSS templates. The template set will adapt to various mobile devices through a device detector built into ATutor.
Work will involve adapting the ATutor course management screens and the ATutor system managements screens, allowing course instructors and ATutor administrators to manage ATutor through their mobile device.
(3 positions available)
In this project the student will develop a mobile version of ATutor Social for one of the three supported mobile platforms (iPhone, Android, Blackberry). Each App will be based upon Web services to be added to ATutor Social as part of this project, extending current Web services in ATutor, so network activity, contacts, individual and group communications, and social gadgets can be accessed through a mobile device.
This project can potentially provide work for several students, each developing for a different mobile platform, potentially working with the candidate for project 2
The candidate will design an App that will communicate with the Web services of a user's home ATutor Social network, much along the lines of the Facebook mobile app. The app will potentially be made up of five panels:
With the rise of Facebook, MySpace, and iGoogle, to name a few popular social networks, it is becoming increasingly more desirable to be able to integrate networks so users can monitor activities across them from a single location. Users of ATutor Social are able to link their other social networks into their ATutor network, and potentially manage them all from within ATutor, but it is not currently possible to access ATutor Social from these other networks. For instance, linking ATutor Social into Facebook or iGoogle.
This project will have a student design and develop the Open Social equivalent to the mobile Apps described in Project 3, allowing ATutor Social users to access their network from other social networks, much like a person can link Facebook into ATutor Social. If time permits, the gadget settings may be extended with the ability to add multiple ATutor Social Web service URLs, making it possible to link multiple ATutor social networks together. The six panels should include:
ATutor Social users can link into the central social.atutor.ca Shindig Open Social server, and link to the larger ATutor Social network, able to search out friends and communicate with them on other ATutor Social networks. The student may also consider investigating the possibility of using Shindig as a hub for linking networks together.
(1 position available)
Universal Subtitles, created by the Participatory Culture Foundation, is a free open source tool that makes it easy to subtitle, caption, and translate video in an open collaborative environment . It can be used along with Flowplayer, ATutor's primary video player, to extend its functionality with captioning and subtitle capabilities. It can also be used to caption or subtitle Vimeo or Youtube video that might be linked into ATutor content.
A Universal Subtitles module will add to a wide range of accessibility features and enhancement already found in ATutor. This project will offer a student the opportunity to expand his or her knowledge of Web accessibility, working with some of the world's premier accessibility experts, and with two high profile open source communities that have accessibility as a primary guiding principle in their development practices.
This project will have a student create a module that extends the ATutor content editor, and the Flowplayer video player, making it possible for elearning content authors to caption and subtitle video while they develop content in ATutor. If time permits, the current Vimeo and Youtube modules in ATutor will also be extended to include captioning and subtitling capabilities.
(1 position available)
Working together with another student participating in GSoC with the BigBlueButton developers (blindsidenetworks.com), the candidate for this project will integrate BBB with ATutor as a module that allows instructors to add learning activities to course content. The work being carried out at Blindside Networks will focus on improving the accessibility of BBB, leading toward conformance with US Section 508 requirements, and WCAG 2 AA requirements.
The candidate should have good PHP programming skills, have familiarity with ATutor module development, and understand how to use a third party API to integrate applications into ATutor. Candidates who are familiar with accessibility guidelines (e.g. WCAG, Section 508) and screen reader technology (e.g. JAWS, Window Eyes, NVDA), will be preferred, though this is not a requirement.
See the documentation below for information about the BBB API and ATutor module development.
(1 position available)
1. A module_date.php file for each module that requires its dates to be exposed to the calendar. (Tests & Surveys, Assignments, Content)
A challenging aspect of this project will be developing a calendar interface that is both accessible and usable by screen reader users. The candidate should be able to describe strategies that might used to improve the usability of each screen within the calendar, so it is navigable without the use of a mouse, and understandable when output as audio from a screen reader.
This first implementation of the calendar will focus on gathering dates from within ATutor. The candidate should develop the calendar with foresight of extending the module in future versions, adding in such features as a personal calendar component for recording personal events, a calendar integration feature for combining information from the ATutor calendar with other calendars via iCal for example, and an export component so calendar information can be packaged and imported into other systems.
(1 position available)
The Open University has had the foresight to adopt a number of content interoperability standards to ensure their open content will be usable across a broad range of learning technologies. As a result, ATutor, also designed with standards in mind, is in a position to take full advantage of the hundreds of prefabricated courses vailable through OpenLearn.
This GSoC project will involve creating a OpenLearn search module that allows ATutor users to search the OpenLearn content repository and import content in Common Cartridge or Content Package formats for use in ATutor courses.
The candidate for this project will start with the ATutor template module, and build into it search and retrieve functionality, similar to the way content is searched and retrieve from an AContent repository. Like AContent, OpenLearn provides APIs that make this possible.
In this project the candidate will re-design and develop the AChecker interface.
The new interface will be based on AJAX technologies (http://www.adaptivepath.com/ideas/essays/archives/000385.php) and it should be compliant to W3C WAI‑ARIA specification (http://www.w3.org/WAI/intro/aria.php).
The candidate students must have a good knowledge of HTML and CSS, have familiarity with PHP, AJAX and W3C WAI-ARIA specification. AChecker interface and layout will be renovated with new AJAX technologies. Compliance to W3C WAI-ARIA specification guarantees the system accessibility.
The final work will be included in AChecker distributions.
In this project the candidate will design and develop a new AChecker feature with the aim of exporting evaluation report in different formats. Such a system will allow users locally downloading evaluation reports in one or more of the following formats: CVS, PDF, XML, Excel and Calc compliant formats.
The candidate students must have a good knowledge of XML and PHP, have familiarity with HTML and CSS.
We're looking for students to collaborate with us on the Google Summer of Code 2011 program. Working with Fluid gives you a chance to learn more about accessibility and usability while writing code with cutting-edge open web technologies like HTML5 Canvas and Video. Create cool stuff and make a real impact on users at the same time!
To communicate directly with the Fluid development team, open an IRC session at irc://irc.freenode.net and join the #fluid-work channel. The core developers are generally around 9:00 to 5:00 Monday to Friday Eastern Standard Time (UTC+5). Though not a requirement, students are advised to login to IRC and interact with the developers. Generally students developers get to know, are the ones chosen to fill the limited number of spots available.
1 position available
This project involves adding support for synchronized media such as captions, transcripts, and audio descriptions to Infusion's proof-of-concept VideoPlayer component. HTML5 Audio and Video are exciting new standards available in most browsers, which enable the playback of media without proprietary third-party plugins such as Flash. At the moment, accessibility features aren't widely supported by most HTML5 video players. This project is an opportunity to show the world how new open web technologies can be made more usable for all.
Create a component for accessible image editing with HTML5 Canvas and Infusion.
1 position available
This project is an opportunity to create an image editing tool entirely with open web technologies, especially HTML5 Canvas. The goal for this component is to provide familiar image processing features such as cropping, resizing, and tagging, all within a standard web page. The contributor is free to experiment with other, more complex image processing algorithms and implement them as desired. The component will support accessibility features such as use of the keyboard instead of the mouse.
1 position available
For this project, contributors will create a new theme for one or more content management systems of their choice using Infusion's Fluid Skinning System (FSS) and UI Options. A few potential CMSes you might want to consider: WordPress, Drupal, or MediaWiki. This Fluid Skinning System-based theme will enable users to easily customize the appearance and layout of the CMS using the UI Options component. For example, UI Options provides high contrast, large print, and simplified layouts that help improve usability with assistive technologies such as a screen magnifier or mobile device.
Students should have a firm knowledge of HTML and CSS, as well as familiarity with one or more content management systems such as WordPress or Drupal. PHP chops are a plus. Familiarity with Fluid Infusion or the Fluid Skinning System is not required; we'll show you the ropes.
1 position available
Data visualizations and audiozations transform raw data into visual and audio landscapes. These alternate data mediums take advantage of the different ways human cognition understands and interprets data. In this project, the student will: 1. learn principles for designing inclusive data representations, and 2. choose a data set and develop interactive visualizations and audiozations using existing techniques (e.g., charts & graphs, treemaps, arc diagrams), or a novel student-designed one.
This year the IDI is working with Komodo OpenLab in the ongoing development of two projects that originated at IDI: Tekla (started with GSoC 2010) & tagin! . Komodo OpenLab is a research and development lab specializing in the creation, adaptation and support of open and inclusive technologies that facilitate the daily lives of people with disabilities, while also benefiting everybody else.
For additional information on these projects, see the Komodo GSoC 2011 ideas page .