61
edits
(WebSocket Monitor - project description updated) |
Abdelrhman (talk | contribs) (→2019 Proposed Project List: Update mentors for Matrix Chat in Thunderbird) Tags: Mobile edit Mobile web edit |
||
(39 intermediate revisions by 22 users not shown) | |||
Line 23: | Line 23: | ||
[[SummerOfCode|Here are the ideas lists from previous years]]. | [[SummerOfCode|Here are the ideas lists from previous years]]. | ||
Proposals can be in almost any part of the Mozilla project, though they do need to be mostly focused on code. | Proposals can be in almost any part of the Mozilla project, though they do need to be mostly focused on code. | ||
Here | Here are the proposals. Feel free to add a new one. | ||
== 2019 Proposed Project List == | == 2019 Proposed Project List == | ||
Line 60: | Line 60: | ||
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre] | | [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre] | ||
| https://bugzilla.mozilla.org/show_bug.cgi?id=1083971 | | https://bugzilla.mozilla.org/show_bug.cgi?id=1083971 | ||
|- | |- | ||
| [https://github.com/marco-c/bugbug bugbug] | | [https://github.com/marco-c/bugbug bugbug] | ||
Line 79: | Line 72: | ||
iii) improving accuracy/precision/recall by implementing additional feature extraction steps or making the already existing ones better. | iii) improving accuracy/precision/recall by implementing additional feature extraction steps or making the already existing ones better. | ||
|- | |- | ||
| WebSocket Monitor | | WebSocket Monitor | ||
| | | Support for WebSocket monitoring and inspection in Firefox DevTools. | ||
| JavaScript/React | | JavaScript/React | ||
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko] | | [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko] | ||
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko] | | [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko] | ||
| [https://docs.google.com/document/d/1ruHk-BA3cqzU7VHoVltnAwWt_2OXKOOAI4nTHwYllzk/edit# Project Description] | | This project aims at providing support for WebSocket monitoring and inspection in Firefox DevTools. The feature should be built on top of the existing Network panel UI and responsible for visualizing data sent through WebSocket connection (i.e. WS frames). The user should be able to use the UI to see as well as analyse the data (search, filter, etc.). | ||
* [https://docs.google.com/document/d/1ruHk-BA3cqzU7VHoVltnAwWt_2OXKOOAI4nTHwYllzk/edit# Detailed Project Description] | |||
|- | |- | ||
| Helpful crash reporter | | Helpful crash reporter | ||
Line 125: | Line 91: | ||
* Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers | * Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers | ||
* For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla | * For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla | ||
|- | |||
| Debugger Inline Variable Preview | |||
| When the Firefox DevTools debugger is paused, users can hover over variables to get a useful tooltip that details the variable's value at that time. While this popup is very informative, one valuable enhancement would be displaying relevant contextual variables values alongside the variable inline, alleviating the need for tooltips and allowing the user to more quickly get the information they need. The applicant will work alongside the Debugger's team to implement this feature based on UX mockups and be given space to share and implement ideas of their own. | |||
| Javascript | |||
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] | |||
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] | |||
| | |||
|- | |||
| GitHub Checks Support Improvements | |||
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports reporting results to the [https://github.com/taskcluster/taskcluster/pull/129/checks?check_run_id=54327344 GitHub Checks API], but only reports success or failure. Let's add support for showing [https://developer.github.com/v3/checks/runs/ annotations] - snippets of log output, more detailed results, images, and so on. We can even add support for additional "actions" on the task, such as re-running with debugging enabled. | |||
| Server-side JS | |||
| [https://mozillians.org/en-US/u/djmitche/ :dustin] | |||
| [https://mozillians.org/en-US/u/ireneOwl/ :owlish], [https://mozillians.org/en-US/u/djmitche/ :dustin] | |||
| | |||
|- | |||
| Support GitHub Logins in Taskcluster | |||
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports logging in with Auth0, the Mozilla login system. We would like to make it useful outside of Mozilla, and most other users do their development on GitHub, making GitHub logins a good solution. This project would involve adding support for signing in with GitHub, as well as the more challenging task of assigning appropriate permissions to users based on the setup of their GitHub account. | |||
| Server-side JS | |||
| [https://mozillians.org/en-US/u/djmitche/ :dustin] | |||
| [https://mozillians.org/en-US/u/ireneOwl/ :owlish], [https://mozillians.org/en-US/u/djmitche/ :dustin] | |||
| | |||
|- | |||
| Improve Webdriver support in Servo | |||
| [https://github.com/servo/servo/ Servo] currently supports a minimal subset of the [https://w3c.github.io/webdriver/ Webdriver standard]. We would like to improve Servo's support, and verify its correctness by passing a [https://github.com/web-platform-tests/wpt/tree/master/webdriver set of automated tests]. This project would involve writing Rust code to extend the webdriver server inside of Servo, as well as JavaScript and Python to support the [https://web-platform-tests.org/writing-tests/testdriver.html testdriver.js] testharness. | |||
| Familiarity with Python & JavaScript; interest in learning Rust | |||
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews] | |||
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews] | |||
| [https://github.com/servo/servo/wiki/Support-Webdriver-based-tests-project Project description] | |||
|- | |||
| Support importing Instruments profiles in perf.html | |||
| [https://github.com/devtools-html/perf.html/ perf.html] visualizes performance data recorded from various performance analysis tools. It is a tool designed to consume performance profiles from Gecko Profiler but can visualize any profiler able to output JSON. It currently supports Gecko, Chrome and perf profile formats. Instruments is a performance analyzer that comes with Xcode. This project would involve adding support for Instruments profile import in perf.html. | |||
| Familiarity with JavaScript & React | |||
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova] | |||
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova] | |||
| https://github.com/devtools-html/perf.html/issues/1138 | |||
|- | |||
| Common Voice - WebAssembly MP3 Encoding | |||
| Currently Common Voice doesn’t support Safari, which is also why we have an iOS app. The only reason being the missing MediaRecorder API. It could be polyfilled (rebuilt in “userspace”) by compiling an MP3 encoder to WebAssembly. I’ve tried that a couple of times, but never had enough time to fix the opaque bugs happening in Safari. This could also be turned into its own library and would be a nice story overall of how WASM can help with WebCompat and missing APIs. | |||
| JavaScript | |||
| [https://mozillians.org/u/gweber/ Gregor Weber] | |||
| [https://mozillians.org/u/gweber/ Gregor Weber] | |||
| [https://github.com/mozilla/voice-web/issues/469 This GitHub issue] lines out some thoughts around how to implement it and you can find references to closed PRs which tried implementing it in various ways. | |||
|- | |||
| Common Voice - Voice Wave Avatar | |||
| We’d like our users to have unique(ish) avatars based either on the characteristics of their voice or a visualization of how their name (or an utterance of their choosing) is pronounced. It could also be a combination of the two ideas. We’re very open to explore this space together, though the a candidate should have some knowledge in sound theory. | |||
| JavaScript, Some knowledge of sound theory | |||
| [https://mozillians.org/u/gweber/ Gregor Weber] | |||
| [https://mozillians.org/u/gweber/ Gregor Weber] | |||
|- | |||
| Tab Manager menu in Firefox | |||
| This project will extend the tab overflow menu - which shows tabs not visible in the browser's tab strip - to allow management of all open tabs across all browser windows. The selected student will be working directly in the Firefox codebase to add functionality and new menu structures to make this easily accessible for end users. | |||
| JavaScript, CSS, and web experience | |||
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster], [https://mozillians.org/en-US/u/bbell/ Bryan Bell] | |||
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster] | |||
| We have [https://mozilla.invisionapp.com/share/4SNCEPDUEZ6#/screens UX mockups] for this feature, which could be broken into two phases. We also have a [https://bugzilla.mozilla.org/show_bug.cgi?id=1480542 bug on file], where discussion has begun. While working on this you will become very familiar with the Browser Toolbox, our own "Inspector" tool for the browser user-interface, as well as writing automated tests for the new feature you're adding. The existing tab overflow code lives in our [https://searchfox.org/mozilla-central/source/browser/base/content/browser-allTabsMenu.js browser-allTabsMenu.js] file, which will be the starting point for the new tab manager. You can look at this and the existing tab code to get an idea of how this currently works. | |||
- | |||
|- | |||
|- | |||
| Firefox Reader Redesign | |||
| The design of Firefox’s Reader Mode has languished behind as Quantum has implemented the new Photon Design System. The interface needs to be rebuilt using new visual and interaction styles to match the Photon Design System. | |||
| JavaScript, CSS, and web experience | |||
| [https://mozillians.org/en-US/u/awallin/ Abraham Wallin] | |||
| [https://mozillians.org/en-US/u/eeejay/ Eitan Isaacson] | |||
| [https://mozilla.invisionapp.com/share/87N9YQYCTJZ#/315073983_Reader_View_Redesign UX Mockups] for this feature are available with visual bugs have been reported [https://bugzilla.mozilla.org/show_bug.cgi?id=1187696 here] and [https://github.com/devtools-html/ux/issues/5 here]. Functional bugs and feature enhancements have been documented [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Areader-mode-has-issues here], [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Ashould-be-readerable here], [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Areadability-algorithm&list_id=14539703 here], and [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Aisreadable&list_id=14539704 finally here]. The request is for an engineering student to implement the designs and tackle the queue of bugs/enhancements within the Firefox code base. Mentors will support with prioritization, design direction/assets, and technical guidance. | |||
|- | |||
| An Android file downloader designed for Emerging Markets | |||
| A lesson learned thanks to our UX team is in Emerging Markets the data plan is dynamic: in late nights we have the most affordable bandwidth. Here's the question: Why not schedule big files and videos and have them downloaded when you're sleeping? The mvp would be an App which we can send urls to. After receiving these urls the App either downloads it directly or defer it to late night. As there are more and more background restrictions enforced on new Android APIs, this should be a fun and challenging journey. | |||
A stretch goal would be to embed this downloader in our browser for Emerging Markets, Firefox Lite. Firefox Lite is not satisfied with the current Android Download Manager in several ways: We'd like to give users the ability to pause/resume a download, we'd like to download a file directly to SDcard (opposed to download it to the main storage and move it into SDcard). | |||
We've also prepared an even more ambitious mission for those who want tough challenges: Design the app and make it dynamic deliverable. With aabs we can satisfy both light and heavy users by defaulting Android Download Manager as the download tool and prepare the aforementioned downloader dynamically so that Firefox Lite itself is still minimized in terms of disk size. Nevin and mTwTm are Android developers who can provide assistance to Android App design. | |||
| Android Java/Kotlin | |||
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] | |||
| [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] (mTwTm@mozilla.com), [https://github.com/cnevinc/ Nevin Chen] (nevin@mozilla.com) | |||
| | |||
|- | |||
| Toolkit for sandboxing third-parties libraries in Firefox | |||
| Firefox supports a long tail of infrequently used image and audio formats to | |||
support the occasional website that uses them. Each such format requires the | |||
Firefox decoder to use a new open source library for parsing and decoding. | |||
This, unfortunately, increases the attack surface of Firefox and as we saw in | |||
Pwn2Own 2018, Firefox was successfully exploited via a bugs in such libraries | |||
(libogg in this case). | |||
This project proposes to sandbox third-party libraries in Firefox by building a | |||
new software-fault isolation toolkit. Our tookit will build on the WebAssembly | |||
compiler to isolate libraries in Firefox. But, as part of this toolkit we will | |||
also develop and apply a library for safely interfacing with sandboxed libraries (and | |||
sanitizing data coming from them). with this toolkit we can ensure that any | |||
vulnerability in third-party libraries (e.g., libogg or libpng) cannot be used | |||
to be used to compromise Firefox. | |||
| C/C++, experience with WebAssembly | |||
| [https://mozillians.org/en-US/u/erahm/ Eric Rahm] | |||
| [https://mozillians.org/en-US/u/froydnj/ Nathan Froyd] | |||
| | |||
|- | |||
| Test automation our linting tools | |||
| We have a several linting tools running on Firefox code base, they currently don't have a test suite. | |||
The goal of this project is to make sure that tests are executed. We currently have a similar [https://bugzilla.mozilla.org/show_bug.cgi?id=1432410 test automation for static analyzer jobs]. The idea would be to extend (or replicate) this model for [https://searchfox.org/mozilla-central/source/tools/lint/ ./mach lint] (which run flake8, eslint, etc) and [https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/mach_commands.py#2327 ./mach clang-format] | |||
The bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1448008 | |||
| Python | |||
| [https://github.com/sylvestre Sylvestre] (s@mozilla.com) | |||
| [https://github.com/abpostelnicu Andi Postelnicu] (andi@mozilla.com) | |||
| | |||
|- | |||
| Firefox Account Security Dashboard | |||
| Firefox Account administrators and users need an easily digestible view into the important events that have occurred on an account, providing a way to audit for irregularities. | |||
| JavaScript, HTML, CSS, MySQL | |||
| [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson] | |||
| [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson] | |||
| The Firefox Account platform tracks security information about an account, but does not surface this information in an easily consumable format. Users and administrators should be able to see a timeline of an account’s security related events, such as connecting devices, signing into services, changing or resetting passwords, and adding or removing 2FA. Each event in the timeline should include a timestamp, IP address, and location information when they occurred. | |||
This project would entail updating our security event API to ensure we track and expose the required data. The first phase is to build a script that consumes the API and pretty prints the timeline. The second phase is to provide a web interface for the security timeline. | |||
|- | |||
| Improving FastParquet | |||
| FastParquet is a Python library that needs improvement to how it writes the parquet file format | |||
| Python | |||
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski] | |||
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski] | |||
| [https://github.com/klahnakoski/mo-parquet/blob/dev/docs/StudentProject%202019.md Read more] | |||
|- | |||
| Faster Pyparsing | |||
| Pyparsing is a Python library that provides a DSL for language specification. It could use some optimization. | |||
| Python | |||
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski] | |||
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski] | |||
| [https://github.com/mozilla/moz-sql-parser/blob/dev/docs/Student%20Project%202019.md Read more] | |||
|- | |||
| <s>Regression Detection</s> | |||
| <s>Use machine learning to guide statistical model selection, then use the model(s) to detect regressions in future data. </s> | |||
| <s>Machine Learning, Statistics, Python</s> | |||
| <s>[https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]</s> | |||
| <s>[https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]</s> | |||
| <s>[https://github.com/mozilla/ActiveData/blob/dev/docs/Student%20Project%20190121.md Read more]</s> | |||
|- | |||
| <s>Bugzilla Kanban Board</s> | |||
| <s>Show bugs like [https://en.wikipedia.org/wiki/Post-it_Note post-it notes] on a [https://en.wikipedia.org/wiki/Whiteboard whiteboard]. Much like a [https://en.wikipedia.org/wiki/Kanban_board Kanban board]</s> | |||
| <s>JSX/React</s> | |||
| <s>[https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]</s> | |||
| <s>[https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]</s> | |||
| <s>[https://github.com/mozilla/bugzilla-tiles Read more]</s> | |||
|- | |||
| <s>More ActiveData Recipes</s> | |||
| <s>Build out the user interface of the [https://github.com/mozilla/active-data-recipes active-data-recipes] project so that making new recipes is even easier</s> | |||
| <s>JSX/React some Python</s> | |||
| <s>[https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]</s> | |||
| <s>[https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]</s> | |||
| <s>[https://github.com/mozilla/active-data-recipes/pull/112/files#diff-0f126940e57c54541662345b499622f1 PR with proposal] or [https://github.com/mozilla/active-data-recipes/tree/master/docs/Student%20Project%20190130.md Read more]</s> | |||
|- | |||
| TUID service improvments | |||
| The TUID service handles millions of requests daily from hundreds of machines. It must go faster, and be stabilized. | |||
| Python/Flask/Sqlite | |||
| [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski] | |||
| [mailto:gmierzwinski@mozilla.com Gregory Mierzwinski] | |||
| [https://github.com/mozilla/TUID/blob/dev/docs/Student%20Project%20190204.md Read more] | |||
|- | |||
| Firefox Source Docs Infrastructure | |||
| Improve the infrastructure underpinning Firefox's [https://firefox-source-docs.mozilla.org/ in-tree documentation]. | |||
| Python, Sphinx, Rst | |||
| [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt] | |||
| [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt] | |||
| Writing docs for Firefox's in-tree [https://firefox-source-docs.mozilla.org/ source docs] is time consuming and difficult and the end result is difficult to navigate. | |||
With [https://developer.mozilla.org/en-US/ MDN] de-prioritizing build and workflow docs, we need a suitable replacement for all of Firefox's contribution and workflow documentation. The great advantage of documentation living in-tree, is that it can be updated along with the source. Unfortunately the current system to build and generate docs is difficult to write for, slow to build and generates poorly organized documentation. These factors discourage developers from creating or updating docs. | |||
This project aims to improve the documentation experience via static analysis tools (e.g hint when docs might need to be updated), enabling linters, faster build times, additional language support and well structured hierarchies. Help make documentation a bigger part of our developer's day to day workflow. | |||
|- | |||
| Improve FixMe | |||
| [http://fixme.ossn.club/ Improve FixMe], a tool for surfacing meaningful contribution opportunities to new contributors. This project started two years ago as a GSoC project and we are looking into adding more capabilities. The tool currently fetches issues only from GitHub and relays a lot into the tags project maintainers use in their repositories. We want to add gitlab support and come up with a more sophisticated way of identifying technologies and skills needed for new contributors | |||
| - Backend: Go, Buffalo, Postgresql. - Front-end: React, typescript, Redux | |||
| [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis] | |||
| [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis] | |||
| [https://github.com/ossn/fixme Link to] front-end source code, [https://github.com/ossn/fixme_backend link to backend] source code. [http://fixme.ossn.club/ FixMe tool in action] | |||
|- | |||
| Rust AV1 Encoder (rav1e) Project | |||
| Mozilla's rav1e Project [http://github.com/xiph/rav1e] is a clean room AV1 encoder implementation written in Rust. The goal is to create a production ready AV1 encoder for use with common internet use cases: Video-On-Demand (high latency), Live Streaming (some latency), Interactive Video Conferencing (low latency). | |||
| | |||
* C/C++ | |||
* Rust | |||
* SIMD | |||
| [mailto:negge@mozilla.com Nathan Egge] | |||
| [mailto:negge@mozilla.com Nathan Egge] | |||
| We are looking for GSoC students to help us research and implement advanced encoding algorithms in rav1e. Areas of interest are: | |||
* Scene detection | |||
* Frame type assignment and ordering | |||
* Encoder complexity analysis and design of speed levels | |||
* Rate-distortion optimization algorithms | |||
* Parallelized encoding using Rust fearless concurrency | |||
* Chunked encoding | |||
|- | |||
| Evangelizing best practices for coding the web | |||
| There’s a team inside Developer Outreach focused on making useful projects for today’s web developers and designers. We are launching a series of small gifts to the world: micro-sites, demos, videos, courses, articles, tools, etc — that teach topics like CSS, accessibility, layout design, understanding the web stack, etc. This project would be a chance for you to join us, and help with an ongoing project, or make one of your own. We are looking for someone with the empathy of a teacher, who studies what other people need, and does their best to provide that. Perhaps you will bring the perspective of a CodeNewbie, a fresh generation or community to our team. | |||
| | |||
* HTML, CSS. | |||
* Maybe ARIA or JavaScript. | |||
* Experience with creating content to teach people stuff (writing, code demos, video, etc). | |||
* Knowing how to build and launch a website. | |||
| [https://mozillians.org/en-US/u/jensimmons/ Jen Simmons] | |||
| [https://mozillians.org/en-US/u/jensimmons/ Jen Simmons] | |||
| We don’t expect you to be an expert. We want someone who is passionate about web design / development, and is passionate about teaching others. Someone who cares about strengthening the technical health of the web by evangelizing best practices. Someone who understands the pain of trying to learn, and wants to ease that pain for others. | |||
Also, this project is about knowing how to use CSS, HTML, etc, and wanting to teach web developers how to build websites. It’s not for someone with a more traditional Computer Science background who hates CSS and wishes the web would transform into a JavaScript application runtime environment. We’ll be creating educational projects, using code to do so, not engineering Mozilla software. We are especially interested in someone who loves CSS and has done a lot of interesting experiments with it, or has the capacity to learn more about CSS quickly. | |||
|- | |||
| Firefox Sync for Chrome | |||
| The idea is to build a platform-agnostic library in JS that will work as a Sync client. Then it will be used to make a Chrome extension that allows using Firefox Sync in Chrome. The goal is to make Firefox Sync the default way to synchronize browsers stuff. | |||
| Javascript | |||
| [mailto:driva95@protonmail.com Davide Riva] | |||
| Mentor to be found | |||
|- | |||
| Matrix Chat in Thunderbird | |||
| [http://matrix.org/ Matrix] is an open, decentralized protocol for instant messaging (and more!) It has bridges to many other networks and protocol, e.g. IRC, Slack, and more. Initial support for Matrix was added in {{bug|1199855}}, but there's a lot to do still: | |||
* Update and re-integrate the Matrix SDK | |||
* Support more features from the Matrix SDK (room topics, typing notifications, read receipts, etc.) | |||
* Support one-on-one conversations. | |||
* Add tests specific to Matrix. | |||
* Improve the Matrix JS-SDK that Instantbird and Thunderbird depend on. | |||
* Improving and expanding shared code and APIs used by all JavaScript protocol plugins (IRC, XMPP, Yahoo and Twitter). | |||
* Improving documentation of the process for adding a protocol to Instantbird/Thunderbird. | |||
* Using the Matrix protocol on a day-to-day basis to dog-food the code and see what else is missing. | |||
| JavaScript, XPCOM, experience using HTTP APIs | |||
| [mailto:ryan@thunderbird.net ryanleesipes] | |||
| [mailto:clokep@gmail.com clokep], [mailto:a.ahmed1026@gmail.com Abdelrhman Ahmed] | |||
| We don't expect you to know how to deal with Thunderbird's XPCOM. We're looking for someone who is interested in Chat and will help you get familiar with hacking on Thunderbird and can connect you with developers on the Matrix project as well. | |||
|- | |- | ||
| ..your next idea here! | | ..your next idea here! | ||
| | | some details | ||
| | | skills/language | ||
| | | reporter | ||
| | | mentor | ||
| | | comments | ||
edits