Confirmed users
3,376
edits
(→WADI: Some more projects) |
(→Automation & Tools: - new project) |
||
(40 intermediate revisions by 17 users not shown) | |||
Line 53: | Line 53: | ||
|- | |- | ||
| File Watcher | | File Watcher | ||
| This is the bug topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=958280 :: Bugzilla 958280]]. Using pipes, create a XPCOM component for Mac file watching (Window and GTK are done) or and complete the js-ctypes version. For XPCOM: Windows topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992894 :: Bugzilla 992894]], this is the GTK topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992895 :: Bugzilla 992895]], this is the Mac topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992896 :: Bugzilla 992896]]. This is the preliminary js-ctypes file watcher, but it uses timeout instead of pipes to interrupt/cancel a watch | | This is the bug topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=958280 :: Bugzilla 958280]]. Using pipes, create a XPCOM component for Mac file watching (Window and GTK are done) or and complete the js-ctypes version. For XPCOM: Windows topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992894 :: Bugzilla 992894]], this is the GTK topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992895 :: Bugzilla 992895]], this is the Mac topic - [[https://bugzilla.mozilla.org/show_bug.cgi?id=992896 :: Bugzilla 992896]]. This is the preliminary js-ctypes file watcher, but it uses timeout instead of pipes to interrupt/cancel a watch: https://github.com/Noitidart/jscFileWatcher. | ||
| C/C++/Javascript | | C/C++/Javascript | ||
| [[https://mozillians.org/en-US/u/Noitidart/ :: Noit]] | | [[https://mozillians.org/en-US/u/Noitidart/ :: Noit]] | ||
Line 63: | Line 63: | ||
| Javascript | | Javascript | ||
| marco | | marco | ||
| | | | ||
| | |- | ||
| RFC7512 URI support (PKCS #11 URI) | |||
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1162897 bug 1162897] | |||
and | |||
[https://bugzilla.mozilla.org/show_bug.cgi?id=248722 bug 248722] | |||
| C | |||
| | |||
| rrelyea and dwmw2 | |||
| Already entered [[Community:SummerOfCode16]] | |||
|- | |- | ||
|} | |} | ||
Line 125: | Line 133: | ||
|- | |- | ||
| Update to mozmill 2.0 | | Update to mozmill 2.0 | ||
| [https://bugzilla.mozilla.org/show_bug.cgi?id=930732 bug 930732] | | We are currently using an older version of [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Mozmill Mozmill], a framework for automated UI tests similar to Selenium. In order to stay future proof we need to update to the latest version, which requires some API changes. You will get hands on experience in creating automated tests and your debugging skills will certainly imprve. See [https://bugzilla.mozilla.org/show_bug.cgi?id=930732 bug 930732] for additional details. | ||
| JS and python coding, debug mozmill tests | | JS and python coding, debug mozmill tests | ||
| aceman | | aceman | ||
Line 171: | Line 179: | ||
! Comments | ! Comments | ||
|- | |- | ||
| | | Redesign libpurple integration | ||
| Currently Thunderbird can have additional protocols added to them via libpurple. This is distributed separately because of licensing compatibilities. There is a shim later (called purplexpcom) which translates from Thunderbird's chat interfaces to libpurple's interfaces. Unfortunately this is: | |||
* Time consuming to maintain | |||
* Difficult to compile | |||
* Requires re-compilation for each Thunderbird version | |||
* Is not binary compatible with system libpurples | |||
It is desirable to experiment with different ways to interact with libpurple to redesign this interface. Potential experiments include: | |||
* Using js-ctypes to interact with the libpurple binary component (instead of C++ XPCOM code) | |||
* Spawn a separate sub-process and use IPC to communicate with libpurple | |||
* Compile libpurple to JavaScript with emscripten | |||
Requires understanding of: C, C++, XPCOM, JavaScript | |||
| C, C++, XPCOM, JavaScript | |||
| Patrick Cloke | |||
| | |||
| | |||
|- | |- | ||
| OTR (Off-the-Record) Integration | |||
| [https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger Tor Messenger], which is based on Instantbird, has support for end-to-end encrypted instant messaging using OTR ([https://github.com/arlolra/ctypes-otr via an extension]). The goal of this project would be to upstream these changes from Tor Messenger into Instantbird while incorporating UI changes designed by the Instantbird team. | |||
| c-types, XPCOM, JavaScript, XUL | |||
| arlolra | |||
| Patrick Cloke [:clokep] | |||
| | |||
|- | |- | ||
|} | |} | ||
== | == Calendar == | ||
{| class="standard-table" border="1" style="border-collapse: collapse" | {| class="standard-table" border="1" style="border-collapse: collapse" | ||
Line 196: | Line 218: | ||
! Mentor(s) | ! Mentor(s) | ||
! Comments | ! Comments | ||
|- | |||
|} | |} | ||
== | == SeaMonkey == | ||
{| class="standard-table" border="1" style="border-collapse: collapse" | {| class="standard-table" border="1" style="border-collapse: collapse" | ||
Line 257: | Line 280: | ||
! Mentor(s) | ! Mentor(s) | ||
! Comments | ! Comments | ||
|- | |||
! Debugging failures seen in CI Infrastructure | |||
! there are many things we can do to make the developer experience better when investigating a test job. From retriggering a job to collecting verbose logging or profiling data, to using a 1 click loaner to not only reproduce but to debug and fix issues, there are many parts of the CI system that we can make small improvements upon to simplify and make dealing with test jobs in CI more enjoyable. Full details available [https://docs.google.com/document/d/1kiTt79hnqP65UDYobm0ekYV27-0nRE9IDo9AB8NkSLQ/edit here] | |||
! python, javascript | |||
! Joel Maher | |||
! Joel Maher | |||
! | |||
|- | |- | ||
|} | |} | ||
Line 399: | Line 429: | ||
! Mentor(s) | ! Mentor(s) | ||
! Comments | ! Comments | ||
|- | |||
| SemVer policy checker | |||
| Rust's library ecosystem works with "semantic versioning" (semver), which allows the version numbers of libraries to signify backwards-compatibility constraints. Roughly speaking, if your code works with version `X.Y` of some library, it should work with `X.(Y+1)` -- a new "minor release" -- as well. | |||
In practice, actually ensuring compatibility is quite subtle, and in Rust, there are some library changes that could theoretically break client code, but which we want to allow anyway. Our full stance on semantic versioning is written up in an RFC: https://github.com/rust-lang/rfcs/pull/1105 | |||
The goal of this project is to build a tool that can tell whether a set of changes to a library is valid under Rust's semver rules. Building this tool will likely require some hacking on the compiler itself (to produce the necessary information), and will hopefully result in some reusable infrastructure that can be applied to other projects as well. | |||
| Familiarity with Rust | |||
| Aaron Turon | |||
| Brian Anderson, Aaron Turon | |||
| | |||
|- | |- | ||
|} | |} | ||
Line 463: | Line 504: | ||
! Mentor(s) | ! Mentor(s) | ||
! Comments | ! Comments | ||
|- | |||
| ZAP Bug tracker support | |||
| https://github.com/zaproxy/zaproxy/issues/440 | |||
| Java | |||
| Simon Bennetts | |||
| Simon Bennetts | |||
| | |||
|- | |||
| ZAP Auto login detection and configuration | |||
| https://github.com/zaproxy/zaproxy/issues/2251 | |||
| Java | |||
| Simon Bennetts | |||
| Simon Bennetts | |||
| | |||
|- | |||
| Zest text representation and parser | |||
| https://github.com/mozilla/zest/issues/23 | |||
| Java | |||
| Simon Bennetts | |||
| Simon Bennetts | |||
| | |||
|- | |- | ||
|} | |} | ||
Line 486: | Line 548: | ||
| Make Hatnote progressive | | Make Hatnote progressive | ||
| https://github.com/mozilla/wadi/issues/51 | | https://github.com/mozilla/wadi/issues/51 | ||
| HTML5, JavaScript | | HTML5, JavaScript | ||
| Salvador de la Puente | | Salvador de la Puente | ||
Line 509: | Line 564: | ||
| HTML5, JavaScript | | HTML5, JavaScript | ||
| Salvador de la Puente | | Salvador de la Puente | ||
| | | Salva | ||
| | | | ||
|- | |- | ||
| Add | | Add SW functionalities to Phaser (or other HTML5 game engine) | ||
| https://github.com/mozilla/wadi/issues/ | | https://github.com/mozilla/wadi/issues/32 | ||
| HTML5, JavaScript | |||
| Salvador de la Puente | |||
| Salva | |||
| | |||
|- | |||
| Use a service worker with Firefox Accounts | |||
| https://github.com/mozilla/wadi/issues/30 | |||
| HTML5, JavaScript | | HTML5, JavaScript | ||
| Salvador de la Puente | | Salvador de la Puente | ||
Line 519: | Line 581: | ||
| | | | ||
|- | |- | ||
| | | Implement Service Workers on the MDN | ||
| https://github.com/mozilla/wadi/issues/ | | https://github.com/mozilla/wadi/issues/21 | ||
| HTML5, JavaScript | |||
| Salvador de la Puente | |||
| David Walsh | |||
| | |||
|- | |||
| App for watching air.mozilla video podcasts | |||
| https://github.com/mozilla/wadi/issues/11 | |||
| HTML5, JavaScript | | HTML5, JavaScript | ||
| Salvador de la Puente | | Salvador de la Puente | ||
Line 526: | Line 595: | ||
| | | | ||
|- | |- | ||
| | | Add offlining to Shower | ||
| https://github.com/mozilla/wadi/issues/ | | https://github.com/mozilla/wadi/issues/3 | ||
| HTML5, JavaScript | | HTML5, JavaScript | ||
| Salvador de la Puente | | Salvador de la Puente | ||
Line 557: | Line 626: | ||
! Comments | ! Comments | ||
|- | |- | ||
|} | |} | ||
Line 579: | Line 638: | ||
! Comments | ! Comments | ||
|- | |- | ||
|} | |} |