Confirmed users
3,376
edits
Community:SummerOfCode16:Brainstorming: Difference between revisions
Community:SummerOfCode16:Brainstorming (view source)
Revision as of 17:28, 22 March 2016
, 22 March 2016→Automation & Tools: - new project
(→Automation & Tools: Move project to main page) |
(→Automation & Tools: - new project) |
||
| (13 intermediate revisions by 8 users not shown) | |||
| 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 172: | Line 180: | ||
|- | |- | ||
| Redesign libpurple integration | | 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: | ||
| C++, XPCOM, JavaScript | |||
* 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 | | Patrick Cloke | ||
| | | | ||
| Line 201: | Line 222: | ||
== SeaMonkey == | == SeaMonkey == | ||
{| class="standard-table" border="1" style="border-collapse: collapse" | {| class="standard-table" border="1" style="border-collapse: collapse" | ||
| Line 271: | 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 413: | 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 477: | 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 | |||
| | |||
|- | |- | ||
|} | |} | ||