Over the last week, many of you have submitted draft proposals and are eagerly awaiting feedback from the project mentors. We would like to assure you that we will be providing feedback in the next couple days, but you should know that some of the mentors have a lot on their plates at the moment, especially considering recent developments related to COVID-19. We ask that you please bear with us, and we thank you for your patience and understanding. To those of you who have yet to submit your draft proposals, please know that we cannot accept any proposals outside of the GSoC website, and that only students who submit a final proposal will be eligible for acceptance. If you have any questions about this part of the process, please feel free to reply to contact us using the methods detailed below. |
Table of Contents:
Don't panic! Please read through this page first, it has many answers! :)
TL;DR:
For feedback during North American business hours, please reach us on the #fluid-work IRC channel on Freenode. Please note that some mentors may appear online but may not be active or able to respond to messages immediately. Alternatively, you can reach us using the fluid-work mailing list. We tend to use the mailing list for asynchronous discussions that may not work so well in a chat room setting.
We encourage open and transparent communication within our community. With that in mind, please contact us in the #fluid-work channel and on the mailing list. As mentors have a number of other responsibilities, it may take us some time to reply. Please allow mentors the opportunity to get back to you in their own time. Please also try to keep questions specific to a particular project. We expect that GSoC applicants communicate with respect for everyone.
It is important to read and understand Inclusion in the Fluid Community. We follow this set of values that promotes inclusion, cooperation, mutual respect, openness and the sharing of ideas. We expect students to be helpful and supportive and to openly communicate their work process in a manner that aligns with our values.
To keep ourselves organized and consistent, we do our best to make sure our work follows these Contribution Guidelines. Some projects may have their own specific guidelines.
Try not to focus on existing issues with these projects — it is more valuable to invest into research, understanding possible solutions, and participating in the community. This will help you with your GSoC proposals.
Fluid is an open source community of designers, developers and researchers who help improve the usability and accessibility of the open web.
Working with Fluid gives you a chance to learn more about accessibility, usability, and inclusion while writing code with cutting-edge open web technologies in an international open source community. These project descriptions are flexible and give you room to make your own mark and propose your own approach.
User Interface Options Plus (UIO+) allows a user to customize websites to match their own personal needs and preferences. Settings for the adaptations can be set via the UIO+ adjuster panel or, if on a Morphic-enabled machine, from a keyed-in preference set. UIO+ currently supports a dozen or so adaptations, including contrast; line, word and character spacing; table of contents, text-to-speech and zoom.
The primary task of this project will be to port the extension to work in both the Firefox and Safari web browsers. Ideally the same codebase should be used to build the extensions for all browsers. Once the ports are successful, additional adaptations should be created to provide more user customization options. The specific adaptations should be decided on with the mentors.
Tag: uio+
Repository: https://github.com/GPII/gpii-chrome-extension
Issue tracker: https://issues.gpii.net/issues/?jql=project%20%3D%20GPII%20AND%20component%20%3D%20%22Web%20Personalization%20Browser%20Extension%22
Mentors and their IRC usernames: Justin (Justin_o), Cindy (cindyli)
Skills needed: JavaScript
How to get started:
Migrate the FLOE Project and Fluid Project websites to use a modern static site generator (like Hugo, Jekyll, etc.). The FLOE Project site is currently using static, hand-coded HTML, while the Fluid Project site is currently built using DocPad.
It is important that the new sites are accessible, work reliably and have well-defined processes for updating and adding new content. Fixes to the User Experience (UX) are not a priority, as we may redesign the site in the future.
Tag: websites
Repositories:
Mentors and IRC usernames: Jon (jhung), Gregor (gmoss), Colin (colinclark)
Skills needed: HTML, CSS, markup templating, JavaScript
How to get started:
Update the Infusion Documentation to be generated using Hugo or another actively-maintained site/documentation generator instead of DocPad, with the Infusion documentation content residing in a separate repository. The goal is to improve maintainability, functionality and flexibility (ability to move to a new site generator easily).
Any changes to documentation or creation of new tagged releases should trigger automation to build new documentation.
The project is required to support tagged versions of Infusion documentation — the technology will need to output and present these tagged versions. Currently there are 3 tags:
Tag: documentation automation
Repository: https://github.com/fluid-project/infusion-docs/
Mentors & IRC handles: Jon (jhung), Justin (Justin_o), Gregor (gmoss)
Skills needed: HTML, CSS, Markdown, markup templating, JavaScript
How to get started:
Project Description:
Projects like the Xbox Adaptive controller, the Logitech G Adaptive Gaming Kit, and various modified controllers strive to include a wider range of people in traditional PC and console gaming. The goal of this project is to extend the usefulness of adaptive controllers by making it possible to navigate using a game controller as an alternative to a keyboard or mouse.
As a proof of concept, we should at least be able to demonstrate support for keys commonly used for browser navigation, such as the arrow keys, tab, shift, space, enter, and escape. The ideal solution would also allow the user to select which actions to associate with which gamepad inputs, including key combinations, macros, and possibly simulated mouse input.
Tag: game controller
Mentors & IRC handles: Tony (the-t-in-rtf)
Skills: JavaScript, HTML
Is this a coding project? Yes
Additional Information:
How to get started: