Canmove, confirm
1,394
edits
Changes
→Azure Blob Storage client library
[https://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-how-to-use-blobs/ Blob Storage API]. We specifically would like to have the following:
1. All Rest API endpoints [https://msdn.microsoft.com/library/dd135733.aspx implemented] using input validation to ensure that only valid data makes it to the API. [http://json-schema.org/ JSON Schema] is a great tool for this2. Ability to specify a JSON Schema to validate objects that we'll store or append to blobs, and also that we read out from them
3. Ability to use [https://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-1/ Shared Access Secrets (SAS)] as authentication
4. Stretch goal of adding SAS for Blob storage to our [https://github.com/taskcluster/taskcluster-auth authorization service]
but you should be willing to learn. You should be available to have meetings
at some point in the time window of 9.00h CEST/CET through 17.00h CEST/CET
==== Improve Template Logic for Taskcluster-Github ====
Mentor: Brian Stack (bstack on IRC), [https://mozillians.org/en-US/u/dustin/ Dustin Mitchell] (dustin on IRC)
Background:
The Taskcluster team at Mozilla builds an automation platform, similar in scope
to Buildbot and Jenkins. The project is built to support the continuous
integration testing of Mozilla projects like Firefox and Rust as well as
projects that Mozilla participates in like Rust and NSS. Many of these projects
are developed on Github, and the Taskcluster-Github service acts as
the interface
between the two systems, creating tasks in response to Github events and
posting status updates back to Github. As other Mozillians have started using
Taskcluster-Github, they have identified some issues and missing features
in the service. With those fixed, more Mozillians can use TaskCluster
to improve
the web.
Project:
This project involves addressing some of the more pressing
user-identified issues
with TaskCluster. It is a collection of smaller projects:
1. Add support for creating tasks in response to new Git tags. This
would allow users to run "release" tasks when they push a new version
tag, for example.
2. Make the repository enrollment process "self-serve". Currently, if
a team wants to use Taskcluster-Github, they must ask a person on the
Taskcluster team to set that up for them. That can be slow and
discourages experimentation. With this project completed, users can
set up a new repository with a few clicks.
3. Add "build shields", similar to http://shields.io/ that will show
the latest status of a Taskcluster-Github build or test run.
As a collection of smaller projects, there is plenty of flexibility to
add or remove projects during the internship. You are encouraged to
talk to other teams in Mozilla and, if you find a feature that will
help them use Taskcluster more effectively, implement that feature
instead.
What you'll learn and use:
* Javascript (mostly server-side, using node)
* Github Webhooks and APIs
* Taskcluster APIs
Previous Experience:
You should be familiar with Javascript, although it is OK if that is
limited to scripts that run in the browser. You should be familiar
with Github, including making pull requests and using continuous
integration tools like Travis-CI or CircleCI. Ideally, you would have
some experience working with other people on an open-source project,
modifying existing code and getting feedback in reviews.
==Outreachy Program Cohort: Round 12 (May-August 2016)==
