My TA3M presentation covers most of the volunteer page's projects. Placing it
here will give visitors an easier method to learn about our projects (rather
than digging into a wall of text).
This has the right proportions on my screen, but I'm not sure about other
resolutions. Fingers crossed it looks ok elsewhere...
Dreamhost just added SSL support via SNI (Server Name Indication), no longer
requiring a unique IP. As such, the only fee is the cert itself so finally
adding SSL support for my site. I've added a http->https redirect, but still
good to update these links...
Changes include...
HTTPS Everywhere
* Changed activity (Moderate => Heavy) - Damn this is getting a lot of commits.
TAILS
* Fixed links for the code and bug tracker.
tor-ramdisk
* Changed activity (Light => None) - Just one commit in the last eight months.
* Fixed the link for the code.
TorBirdy
* Changed contributor to just list Sukhbir. He's the sole active contributor
and clearly doing a fantastic job leading the project.
Obfsproxy
* Changed contributor to asn (again, he's clearly the sole contributor and
project lead).
* Changed the language to just list Python
* Fixed the link for the code.
Txtorcon
* Changed activity (Heavy => Moderate) - Meejah is certainly still improving
it, but activity looks to be a little slower than it previously was.
* Added a link for its bug tracker.
Metrics
* Changed activity (Heavy => Moderate) - Huh. The aggregated activity of the
three repositories we list is lower than I recall. Probably more time being
put into research questions rather than metrics infrastructure.
* Removed bug tracker link. It was broken due to the 'Metrics' component being
split into three different ones.
Onionoo
* Changed activity (Light => Moderate) - Karsten's sinking quite a bit of work
into the java codebase.
BridgeDB
* Changed activity (None => Light) - Isis has been making improvements.
Ooni Probe
* Changed activity (Heavy => Moderate) - Commits seem to come in bursts. Last
touched four weeks ago, though.
We're past the application phases for both GSoC and OPW so there's no reason
for them to remain on our site. I kinda doubt that we'll participate in OPW
again so removing that section. As for GSoC, just commenting it out.
We now have a spiffy jenkins testing environment and ticket 8261 has been
resolved. Revising the project idea to keep the html output idea but drop
continuous testing.
Bruce and velope requested for it to be raised. I'm tempted to say 'heavy'
based on the number of commits, but prior to March there was no activity at all
for two years so I'm gonna hold off on doing that until we see if this is
maintained or a flash in the pan.
Someone showed up on irc confused, thinking that we were primarily mentoring
through OPW. The two programs have different requirements and GSoC is a far,
far larger program for us.
Andrew reported during the dev meeting that we still have a slot so adding the
OPW section back in, updated for the program running in parallel with GSoC.
This section was removed in r25974.
Spoke with Nick and got both confirmation that they're still relevant and
prereqs for applying. Hopefully this'll ensure a decent quality for
applications and warn away students for whom it's a bad idea.
Tweaking the 'Stem Usability and Porting' idea to include tackling the
remaining issues that prevent us from deploying TorBEL. Thanks to Sebastian for
the list of tickets!
Cross metrics/stem project from Karsten for rewriting Doctor in python, using
stem for the descriptor support and expanding it to be able to remotely fetch
descriptors.
Why are we still bundling dozens of commented out tasks with the page? If we
want to add these back in later then we should... well, add them back in later.
That's what SCMs are for (even if svn sucks at it). :P
This is slowing down page loads, and most ideas are getting to be pretty old
anyway.
When I've spoken with Sukhbir he mentioned that he doesn't think there's enough
torbirdy tasks remaining to fill a summer. We can add this back in if he
changes his mind.
Noting that Google hasn't yet selected orgs (hell, the org application phase
hasn't even *started* yet). I'm not interested in repeatedly saying this to
prospective students so hopefully these notices will be sufficient.
This is a project that I have been batting around with Nick for a bit. It
doesn't include the 'grand vision' he wants for covering inter-network
components, but it would provide dedicated tests for a very substantial portion
of Tor's codebase.
While I think a more complicated network simulator and testing suite would
yield greater benefits, I also think it would be *vastly* harder to make and
hence quite likely to never happen. Presently our automated testing of Tor is
pretty poor and there's no need to let the perfect be the enemy of the good on
this.
