Here are some ideas I'd be willing to mentor if anyone thinks they're good/bad:
- Creating a Crash Reporter and accompanying backend
- Privacy-preserving metrics gathering (RAPPOR + opt-in) - this might be too ambitious though...
- .onion, HTTP/2, Alt-Srv investigation - An idea of speeding up sites by serving them over a .onion with HTTP2 using the Alt-Srv header, probably with judicious use of server push
- Security Slider Enhancements (Putting more features in FF behind the slider) - this one is probably not ambitious enough
-tom
---------- Forwarded message ---------- From: Damian Johnson atagar@torproject.org Date: 29 January 2017 at 15:57 Subject: [tor-project] We need project ideas for GSoC 2017! To: tor-project@lists.torproject.org
Hi all! This week I'm getting our ducks in a row to apply for Google Summer of Code 2017...
https://summerofcode.withgoogle.com/
I just trimmed our volunteer page of projects that were done last year and sadly that doesn't leave us with much. We need mentors and project ideas!
Got anything you'd care to mentor this summer? If so please let me know! Just send me a description like the ones on the following and I'd be happy to add it to our site...
https://www.torproject.org/getinvolved/volunteer.html.en#Coding
Please note that all projects must have two mentors, one of which is an established tor person. If you're not part of our internal community that's fine, but please find a core developer to co-sponsor your project and act as a secondary mentor.
Thanks! -Damian _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Hi Tom. I'm not familiar with most of those but sound good to me. :P
When you feel confident in the project ideas if you shoot me something to paste into the site I'd be happy to add it.
Cheers! -Damian
On Sun, Jan 29, 2017 at 9:17 PM, Tom Ritter tom@ritter.vg wrote:
Here are some ideas I'd be willing to mentor if anyone thinks they're good/bad:
Creating a Crash Reporter and accompanying backend
Privacy-preserving metrics gathering (RAPPOR + opt-in) - this might
be too ambitious though...
- .onion, HTTP/2, Alt-Srv investigation - An idea of speeding up sites
by serving them over a .onion with HTTP2 using the Alt-Srv header, probably with judicious use of server push
- Security Slider Enhancements (Putting more features in FF behind the
slider) - this one is probably not ambitious enough
-tom
---------- Forwarded message ---------- From: Damian Johnson atagar@torproject.org Date: 29 January 2017 at 15:57 Subject: [tor-project] We need project ideas for GSoC 2017! To: tor-project@lists.torproject.org
Hi all! This week I'm getting our ducks in a row to apply for Google Summer of Code 2017...
https://summerofcode.withgoogle.com/
I just trimmed our volunteer page of projects that were done last year and sadly that doesn't leave us with much. We need mentors and project ideas!
Got anything you'd care to mentor this summer? If so please let me know! Just send me a description like the ones on the following and I'd be happy to add it to our site...
https://www.torproject.org/getinvolved/volunteer.html.en#Coding
Please note that all projects must have two mentors, one of which is an established tor person. If you're not part of our internal community that's fine, but please find a core developer to co-sponsor your project and act as a secondary mentor.
Thanks! -Damian _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Hey Damian, how's this:
-------
Crash Reporter for Tor Browser
Likely Mentors: Tom Ritter, Georg
Currently Tor Browser disables the Crash Reporter. We would like to build it reproducible, enable it, and configure it to report crashes containing non-detailed and impersonal information to Tor, on a .onion submission platform that would allow us to view and explore the crashes.
The project will entail enabling the Crash Report on Tor Browser and creating a backend to receive reports from it. Once created, the crash reporter data will be analyzed and modified to fit Tor's requirements for personal data collection. As time permits, we will update the build system to ensure the crash reporter is built reproducibly and add data analysis tools for the crash report database to visualize top crashers and similar statistics.
-------
Making Tor Browser Faster Likely Mentors: Tom Ritter, Georg
This project will enable and take advantage of HTTP/2, the Alt-Srv header, and tor's new single hop .onion mode to enable websites to transparently move their traffic to a .onion address. In addition to improvements in security, we will benchmark page load and paint times under normal HTTP/1.1, HTTP/2, and when taking advantage of features such as Server Push.
-------
-tom
On 30 January 2017 at 01:23, Damian Johnson atagar@torproject.org wrote:
Hi Tom. I'm not familiar with most of those but sound good to me. :P
When you feel confident in the project ideas if you shoot me something to paste into the site I'd be happy to add it.
Cheers! -Damian
On Sun, Jan 29, 2017 at 9:17 PM, Tom Ritter tom@ritter.vg wrote:
Here are some ideas I'd be willing to mentor if anyone thinks they're good/bad:
Creating a Crash Reporter and accompanying backend
Privacy-preserving metrics gathering (RAPPOR + opt-in) - this might
be too ambitious though...
- .onion, HTTP/2, Alt-Srv investigation - An idea of speeding up sites
by serving them over a .onion with HTTP2 using the Alt-Srv header, probably with judicious use of server push
- Security Slider Enhancements (Putting more features in FF behind the
slider) - this one is probably not ambitious enough
-tom
---------- Forwarded message ---------- From: Damian Johnson atagar@torproject.org Date: 29 January 2017 at 15:57 Subject: [tor-project] We need project ideas for GSoC 2017! To: tor-project@lists.torproject.org
Hi all! This week I'm getting our ducks in a row to apply for Google Summer of Code 2017...
https://summerofcode.withgoogle.com/
I just trimmed our volunteer page of projects that were done last year and sadly that doesn't leave us with much. We need mentors and project ideas!
Got anything you'd care to mentor this summer? If so please let me know! Just send me a description like the ones on the following and I'd be happy to add it to our site...
https://www.torproject.org/getinvolved/volunteer.html.en#Coding
Please note that all projects must have two mentors, one of which is an established tor person. If you're not part of our internal community that's fine, but please find a core developer to co-sponsor your project and act as a secondary mentor.
Thanks! -Damian _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Looks good to me! Tad uncertain about the scope of the first and if it's enough to occupy a student for the whole summer but I don't have a clear picture of what's involved.
I'll add these to the site tomorrow.
Cheers! -Damian
On Mon, Jan 30, 2017 at 12:29 PM, Tom Ritter tom@ritter.vg wrote:
Hey Damian, how's this:
Crash Reporter for Tor Browser
Likely Mentors: Tom Ritter, Georg
Currently Tor Browser disables the Crash Reporter. We would like to build it reproducible, enable it, and configure it to report crashes containing non-detailed and impersonal information to Tor, on a .onion submission platform that would allow us to view and explore the crashes.
The project will entail enabling the Crash Report on Tor Browser and creating a backend to receive reports from it. Once created, the crash reporter data will be analyzed and modified to fit Tor's requirements for personal data collection. As time permits, we will update the build system to ensure the crash reporter is built reproducibly and add data analysis tools for the crash report database to visualize top crashers and similar statistics.
Making Tor Browser Faster Likely Mentors: Tom Ritter, Georg
This project will enable and take advantage of HTTP/2, the Alt-Srv header, and tor's new single hop .onion mode to enable websites to transparently move their traffic to a .onion address. In addition to improvements in security, we will benchmark page load and paint times under normal HTTP/1.1, HTTP/2, and when taking advantage of features such as Server Push.
-tom
On 30 January 2017 at 01:23, Damian Johnson atagar@torproject.org wrote:
Hi Tom. I'm not familiar with most of those but sound good to me. :P
When you feel confident in the project ideas if you shoot me something to paste into the site I'd be happy to add it.
Cheers! -Damian
On Sun, Jan 29, 2017 at 9:17 PM, Tom Ritter tom@ritter.vg wrote:
Here are some ideas I'd be willing to mentor if anyone thinks they're good/bad:
Creating a Crash Reporter and accompanying backend
Privacy-preserving metrics gathering (RAPPOR + opt-in) - this might
be too ambitious though...
- .onion, HTTP/2, Alt-Srv investigation - An idea of speeding up sites
by serving them over a .onion with HTTP2 using the Alt-Srv header, probably with judicious use of server push
- Security Slider Enhancements (Putting more features in FF behind the
slider) - this one is probably not ambitious enough
-tom
---------- Forwarded message ---------- From: Damian Johnson atagar@torproject.org Date: 29 January 2017 at 15:57 Subject: [tor-project] We need project ideas for GSoC 2017! To: tor-project@lists.torproject.org
Hi all! This week I'm getting our ducks in a row to apply for Google Summer of Code 2017...
https://summerofcode.withgoogle.com/
I just trimmed our volunteer page of projects that were done last year and sadly that doesn't leave us with much. We need mentors and project ideas!
Got anything you'd care to mentor this summer? If so please let me know! Just send me a description like the ones on the following and I'd be happy to add it to our site...
https://www.torproject.org/getinvolved/volunteer.html.en#Coding
Please note that all projects must have two mentors, one of which is an established tor person. If you're not part of our internal community that's fine, but please find a core developer to co-sponsor your project and act as a secondary mentor.
Thanks! -Damian _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project