Outreachy/2015/December to March

From MozillaWiki
< Outreachy‎ | 2015
Revision as of 08:21, 24 September 2015 by Ametaireau (talk | contribs) (Fix bullet points syntax)
Jump to navigation Jump to search
Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

Overview

APPLICATIONS ARE NOW CLOSED However, if you have an application submitted you can still continue to contribute. Mentors will make their decisions on October 25 and finalize it on October 31 which means you can still contribute and/or finish something you started but didn't have time to finish.


This is the landing page for the December 9, 2014 to March 9, 2015 round of FOSS OPW, organized by GNOME Foundation.

This page contains all the information about the opportunity with Mozilla for the Outreach Program for Women internship that will take place from December 9, 2014 to March 9, 2015. Please see the main program page for the general information about the program, such as timeline, background information, eligibility, requirements, and the application form.

Important Dates

  • Application deadline: 22 October 2014 at 19:00 UTC.
  • Announcement of accepted applicants: 12 November 2014 at 19:00 UTC via the main program page.

Projects

(Mentors: add your projects below.


SUMO/Input Web Designer/Developer (SUMO/Input Engineering Team)

Mentor: Will Kahn-Greene

Details

SUMO is the support site for Mozilla products. It helps millions of users every week through a knowledge base and support forum. It also provides collaboration and localization tools for the contributors. It uses technology like Python, Django, MySQL, Redis, Memcached, Elasticsearch and more.

Input is one of several tools the Mozilla community uses to gather user sentiment on Mozilla products. This data helps us track down problems, guide new development and generally make Mozilla products better for users using them.

Work with the engineering team of both sites to make them better which in turn helps us serve Mozilla product users and contributors in the best way possible.

The two sites have similar architectures. They're both written primarily in Python/Django on the backend and JavaScript/HTML/CSS on the front end. We use MySQL and Elasticsearch for data storage. They both use GitHub for code management and version control and Bugzilla for issue tracking. They both use a variety of libraries which we contribute to as well.

You'll be working with Will, the primary developer on Input and one of the developers on SUMO to work on SUMO and Input. You'll be contributing code, reviewing pull requests, and working with developers. You'll be involved in our regular meetings and development cycle.

To get started on Input:

Kinto — Make instances discoverable

Mentor: Alexis Métaireau

Details

The Kinto project aims to bring storage instances to everyone, attached to their Firefox Accounts. It actually supports multiple authentication schemes, but FxA is integrated with it, and that is part of the solution we want to deliver.

Currently, Kinto is thought as a centralized server: there is one instance, and everyone authenticates on this instance. Items are shared between users of a same instance.

This doesn't resonates well with multiple goals we have: scalability is harder when there is one endpoint, and it's also not interoperable.

For instance, imagine Alice and Bob. Bob is using Mozilla's servers to store his data, whereas Alice deployed her own Kinto instance.

There are different use cases:

  • Alice wants to use Routina, an application that stores its data inside a Kinto instance. As such, Routina needs a way to discover where it should store its data, and send the requests to this server;
  • Bob and Alice want to collaborate on a set of data (think about a shared expense webapp). There should be a way for Alice to host everything and grant access to Bob to her data. The webapp should be able to use the correct server.

Here are the different steps that could allow these scenarios:

  • At the moment they authenticate, the client detects the email address used, and relies on the domain part to do a Web Finger request on the domain (*) and for the specified user.
  • In case the identified server doesn't support WebFinger, it uses a central repository to lookup where the Kinto server is located.
  • Once the Kinto server located, all requests should be issued against this server.

(*) It is also possible to use the same mechanism to discover the FxA endpoints. But as FxA isn't a federated protocol, users from one FxA realm would need to be accepted explicitely by the Kinto server, in its configuration.

In terms of code changes, here is what it looks like (rough step by step):

  • Update the Kinto.js client to find the server location. It should first rely on WebFinger;
  • Create a central repository of server locations. This could be contained in the FxA profile server or in a central Kinto collection;
  • Update the Kinto.js client to fall-back to this central repository in case no Web Finger exists;
  • Investigate on ways to store this information directly in the web browser. It could also be configurable by the JavaScript client (with

an UX that looks like what Remote Storage proposes).

  • Work on the first user experience: how can client learn they can chose which server to use?
  • Ship it!

To get started on Kinto:

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Outreachy/2015/December_to_March&oldid=1097172"