Removing the remaining stubs as previously discussed (Tor cloud, ExperimenTor,
Chutney, and Torperf). I'm also dropping bridge-guard, see my unanswered
tor-assistants@ email on 12/28 for why. :)
Peter's r25976 reversion was done in the name of expedience rather than making
the page better. Restoring what I had minus the removal of the stubs (which I
gather was the only objectionable bit). As mentioned on tor-assistants@ I plan
to remove those stubs later next week after the CCC crowd has passed.
Besides this made a few small fixes...
* You were labeling bridge-guard as being "Flash Proxy", likely a paste error.
* I've removed the empty links from the stubs. No links are better than broken
links.
* Integrated the new Thandy links with the summary and switched it to use past
tense. The project has been inactive for a long while.
This reverts commit 681ab33b165e9c427401f19f3453fb6ba002eb7f.
Please leave them as Roger made them at least for now. Future updates
deleting lots of content should probably be discussed in advance.
General update for the volunteer page's projects table. This reverts quite a
bit of Roger's additions in r25973 which added a bunch of projects without
summaries or links (please don't do that!). Kept the good bits, though. :P
* Merged Obfsproxy and PyObfsproxy. They both have the same project page, same
bug tracker, and same description. Doing a joint listing is what we did for
Onionoo too which has both a java and python implementation.
* Dropping Anonbib. I asked arma about it on irc but he didn't reply. It's not
a substantial coding project and the summary he wrote is essentially nothing.
* Dropping "tor-ramdisk", "Tor cloud", "bridge-guard", "ExperimenTor",
"Chutney", and "Torperf". They all had no summary and code/bug tracker links.
If the author doesn't care enough about having their project listed to send
those then we shouldn't list it. :)
* Added missing link for torouter's code and Onionoo's bug tracker.
* Removed the flag that Ooni Probe was in alpha. I'm not positive that it's in
production, but it's been under highly active development long enough that I
suspect it's ready.
* Changed arm's description. It's definitely not still under active
development, and the summary didn't really say what it *did*.
* Adjust activity...
* Flash Proxy: Moderate => Heavy
ye god he's doing a ton of work!
* Shadow: Moderate => Heavy
again, almost daily improvements - I'm jealous
* Txtorcon: Moderate => Heavy
not as much as Flash Proxy or Shadow, but still unusually active
* Ooni Probe: Moderate => Heavy
not surprising, with multiple people dedicated to it
* Tor2web: Light => Heavy
lots 'o commits
* Vidalia: Light => None
chiiph has been gone for four months
* Orbot: Moderate => Light
no commits since October and I didn't find much activity on their github
page... though things are so spread out it's hard to tell
* Torouter: Light => None
basically no activity since August
* Torsocks: Heavy => Moderate
no activity since October
* Thandy: Light => None
no commits since 2011
* Atlas: Moderate => Light
essentially nothing since September
* Compass: Heavy => Light
nothing since September
It has always irked me that we had a task 'priority'. Who decides these
priorities? Against what? Sure I think that stem projects are the most
important thing since the discovery of pepperjack cheese but does that really
mean I should label my projects as 'ultra super omega-purple level important'?
Dropping the priority from task ideas and sorting everything alphabetically.
Couple of revsions suggested by Marina including...
* Noting the application deadline date.
* Saying that the ideas listing is for OPW in addition to GSoC.
As theatened on tor-assistants@ I'm trimming our volunteer page's task listing
to only include things with an engaged mentor.
The listing has grown stale which is confusing to newcomers. Some projects are
done, and others reflect plans that are a year out of date. My devious scheme
was that if I required some effort from mentors to keep task ideas around then
we'd only get buy in for those that were really still relevant. Looks like it
worked - we're down to three.
As Ravi discovered during the last GSoC application phase our PathSupport idea
is too poorly defined to make a good GSoC (or GSoC-like) project. Replacing it
with far better defined tasks for improving stem's usability.
Dropping the 'torbutton for thunderbird' project idea since it is now... well,
implemented. Replacing the entry with a project that Sukhbir would like to
mentor.
Stem is far enough along that it's useful to users, and should have a spot on
the projects page. Also revising the volunteer page links to point to its
readthedocs page, which is presently our homepage.
As I understand it Aaron has adopted the torctl/torflow codebases. They also
haven't been touched in months so noting both.
Ravi's still working on stem and Sathyanarayanan is working on Onionoo's python
counterpart (it should probably be listed as a separate project, but he hasn't
provided an entry for it yet).
