We need project ideas for GSoC 2017!
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
On Sun, 29 Jan 2017 13:57:38 -0800 Damian Johnson <atagar@torproject.org> wrote:
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.
Does google still require a google account to be a mentor? I had a google account for this, but accessing it over Tor apparently causes the account to end up being permanently locked and inaccessible. Regards, -- Yawning Angel
Does google still require a google account to be a mentor? I had a google account for this, but accessing it over Tor apparently causes the account to end up being permanently locked and inaccessible.
Hi Yawning. I'd be surprised if it didn't. They've required a google account every year I can remember. Anonym ran into issues around this too and mentored last year by proxy. You can do the same if you'd care to insist on google not having information about ya.
On 29 January 2017 at 15:57, Damian Johnson <atagar@torproject.org> wrote:
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.
Anyone want to mentor this with me? Maybe someone who knows Atlas? Improve bwauth debugging and resources Langauge: HTML/JavaScript/CSS; C; Python; Java The bwauth system has been limping along for a while, and it would be helpful to track how broken it really is, and output more detailed information for relays to debug. We would like to do some or all of the following: - Draft (and implement) a core-tor a proposal to expose bwauth vote documents on DirAuths (Proposal, C) - Draft a plan to enable detection of relays falling between scanners in torflow (Proposal) - Enhance torflow to expose scanner information for relays (which scanner the relay ran on and similar information) (Python) - Implement the analysis tools to detect when relays do fall between scanners (Python?) - Enhance Collector to download and archive these documents (Java) - Enhance OnionOO to expose bwauth data (Java) - Enhance Atlas to expose bwauth voting information per-relay to show historical measurements and scanning status (HTML/JavaScript/CSS) -tom
On 31 Jan 2017, at 02:46, Tom Ritter <tom@ritter.vg> wrote:
On 29 January 2017 at 15:57, Damian Johnson <atagar@torproject.org> wrote:
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.
Anyone want to mentor this with me? Maybe someone who knows Atlas?
Improve bwauth debugging and resources Langauge: HTML/JavaScript/CSS; C; Python; Java
The bwauth system has been limping along for a while, and it would be helpful to track how broken it really is, and output more detailed information for relays to debug. We would like to do some or all of the following:
- Draft (and implement) a core-tor a proposal to expose bwauth vote documents on DirAuths (Proposal, C) - Draft a plan to enable detection of relays falling between scanners in torflow (Proposal) - Enhance torflow to expose scanner information for relays (which scanner the relay ran on and similar information) (Python) - Implement the analysis tools to detect when relays do fall between scanners (Python?) - Enhance Collector to download and archive these documents (Java) - Enhance OnionOO to expose bwauth data (Java) - Enhance Atlas to expose bwauth voting information per-relay to show historical measurements and scanning status (HTML/JavaScript/CSS)
I might be able to help: at the very least I could provide comments and feedback, and we could run the code on the tor test network. But I'm not sure if I will consistently have enough time to be a co-mentor. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Hi,
On 31 Jan 2017, at 02:46, Tom Ritter <tom@ritter.vg> wrote: Anyone want to mentor this with me? Maybe someone who knows Atlas?
I'm the current maintainer for Atlas and have participated in GSoC before as a mentor with the Debian Project.
On Tue, Jan 31, 2017 at 09:12:47AM +1100, teor wrote: I might be able to help: at the very least I could provide comments and feedback, and we could run the code on the tor test network.
On the Atlas portion, I might be able to help with comments and reviewing patches.
But I'm not sure if I will consistently have enough time to be a co-mentor.
I would also potentially struggle to have enough time to be a co-mentor. Perhaps with three of us it would be more managable though, as long as me and teor can align to be unavailable alternately. Thanks, Iain.
Iain, teor, I think that's fine. I'm happy to be the primary POC and have you in the wings to help with your respective specialties and manage the calendar so things work out =) -tom On 30 January 2017 at 18:54, Iain R. Learmonth <irl@torproject.org> wrote:
Hi,
On 31 Jan 2017, at 02:46, Tom Ritter <tom@ritter.vg> wrote: Anyone want to mentor this with me? Maybe someone who knows Atlas?
I'm the current maintainer for Atlas and have participated in GSoC before as a mentor with the Debian Project.
On Tue, Jan 31, 2017 at 09:12:47AM +1100, teor wrote: I might be able to help: at the very least I could provide comments and feedback, and we could run the code on the tor test network.
On the Atlas portion, I might be able to help with comments and reviewing patches.
But I'm not sure if I will consistently have enough time to be a co-mentor.
I would also potentially struggle to have enough time to be a co-mentor. Perhaps with three of us it would be more managable though, as long as me and teor can align to be unavailable alternately.
Thanks, Iain.
_______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Hi, On Tue, Jan 31, 2017 at 10:09:33AM -0600, Tom Ritter wrote:
I think that's fine. I'm happy to be the primary POC and have you in the wings to help with your respective specialties and manage the calendar so things work out =)
This sounds good to me. I'm irl in IRC if you need details from me. Let me know if I'll need to sign up in the Google dashboard thingy. Thanks, Iain.
On 2 Feb 2017, at 14:02, Iain R. Learmonth <irl@torproject.org> wrote:
Hi,
On Tue, Jan 31, 2017 at 10:09:33AM -0600, Tom Ritter wrote:
I think that's fine. I'm happy to be the primary POC and have you in the wings to help with your respective specialties and manage the calendar so things work out =)
This sounds good to me. I'm irl in IRC if you need details from me. Let me know if I'll need to sign up in the Google dashboard thingy.
I could spend an hour or two on this some weeks, to comment on some parts of the project. Please see my comments below.
- Draft (and implement) a core-tor a proposal to expose bwauth vote documents on DirAuths (Proposal, C)
The bandwidths are already in the votes. Does this mean exposing the entire bwauth document at a DirPort URL?
- Draft a plan to enable detection of relays falling between scanners in torflow (Proposal) - Enhance torflow to expose scanner information for relays (which scanner the relay ran on and similar information) (Python) - Implement the analysis tools to detect when relays do fall between scanners (Python?)
I could comment on draft interfaces, but don't know enough to help with the implementation on:
- Enhance Collector to download and archive these documents (Java) - Enhance OnionOO to expose bwauth data (Java) - Enhance Atlas to expose bwauth voting information per-relay to show historical measurements and scanning status (HTML/JavaScript/CSS)
T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
On 2 February 2017 at 21:07, teor <teor2345@gmail.com> wrote:
On 2 Feb 2017, at 14:02, Iain R. Learmonth <irl@torproject.org> wrote:
Hi,
On Tue, Jan 31, 2017 at 10:09:33AM -0600, Tom Ritter wrote:
I think that's fine. I'm happy to be the primary POC and have you in the wings to help with your respective specialties and manage the calendar so things work out =)
This sounds good to me. I'm irl in IRC if you need details from me. Let me know if I'll need to sign up in the Google dashboard thingy.
I could spend an hour or two on this some weeks, to comment on some parts of the project. Please see my comments below.
- Draft (and implement) a core-tor a proposal to expose bwauth vote documents on DirAuths (Proposal, C)
The bandwidths are already in the votes. Does this mean exposing the entire bwauth document at a DirPort URL?
Yes.... Exposing this document (https://bwauth.ritter.vg/bwauth/bwscan.V3BandwidthsFile) at a URL like (http://171.25.193.9:443/tor/status-vote/current/authority)
- Draft a plan to enable detection of relays falling between scanners in torflow (Proposal) - Enhance torflow to expose scanner information for relays (which scanner the relay ran on and similar information) (Python) - Implement the analysis tools to detect when relays do fall between scanners (Python?)
I could comment on draft interfaces, but don't know enough to help with the implementation on:
- Enhance Collector to download and archive these documents (Java) - Enhance OnionOO to expose bwauth data (Java) - Enhance Atlas to expose bwauth voting information per-relay to show historical measurements and scanning status (HTML/JavaScript/CSS)
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
_______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Hi all. Would anybody else care to add a GSoC project idea? We need more! On 1/29/17, Damian Johnson <atagar@torproject.org> wrote:
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
On Sat, Feb 04, 2017 at 04:16:35PM -0800, Damian Johnson wrote:
Hi all. Would anybody else care to add a GSoC project idea? We need more!
Does somebody want to work on documenting or improving usability of (or integration of) OnionBalance? Does the metrics team have any items they'd love to have some help with? I am particularly interested in the clean-up and deployment of OnionPerf, and maybe we're scheduled to have that done before summer, but I bet there will always be more that can be done. Do we need more coverage on core-Tor fuzzing? Is there something useful to be done with streamlining the builds of Tor Browser for BSD? (https://github.com/torbsd/openbsd-ports/) Along those lines, how about automating QA testing for Tor Browser? Is it time to get Selenium integration working? Would it be productive to get an automated, consistent, and public 'exitmap' instance going, to test for obvious breakage on exits, even if we feel that we should keep the more subtle tests secret? Do the Snowflake folks have anything bite-sized and not-critical-path? For example, posting real-time feedback about broker statistics, or deploying a more flexible/configurable algorithm for how the broker should allocate snowflakes to users? Surely the OONI folks want some GSoCers? --Roger
Does the metrics team have any items they'd love to have some help with? I am particularly interested in the clean-up and deployment of OnionPerf, and maybe we're scheduled to have that done before summer, but I bet there will always be more that can be done.
...
Would it be productive to get an automated, consistent, and public 'exitmap' instance going, to test for obvious breakage on exits, even if we feel that we should keep the more subtle tests secret?
Hi Roger. For what it's worth I already reached out individually to the metrics folks and phw. Both replied that they don't have bandwidth to mentor this summer, though phw offered to be the backup mentor for a stem project I'm proposing. Cheers! -Damian
On Feb 4, 2017, at 6:36 PM, Roger Dingledine <arma@mit.edu> wrote:
Do the Snowflake folks have anything bite-sized and not-critical-path? For example, posting real-time feedback about broker statistics, or deploying a more flexible/configurable algorithm for how the broker should allocate snowflakes to users?
While there're most likely several that could be extracted, I'm working through some personal issues and won't have any cycles to devote to mentorship this summer. Sorry about that.
participants (7)
-
Arlo Breault -
Damian Johnson -
Iain R. Learmonth -
Roger Dingledine -
teor -
Tom Ritter -
Yawning Angel