So, here's what I've been up to my first couple weeks with Tor:
* Interviewed and got hired
* Getting up to speed with everything, setting up git repository, etc.
* Met ioerror for coffee and key-signing
* Got my first patch merged! (bug 5235)
* Fixed several other bugs:
* 5452
* 5
Thanks for the heads up.
I got it working on my mipsel box.
First of all I switched to 2.3.18-rc git.
I build the latest zlib 1.2.7 with -fPIC and -DPIC (seems to be required
for mipsel).
I recompiled and reinstalled OpenSSL 1.0.1 with "shared no-ssl2
enable-tlsext"
"shared" also seems to build
> Should we wait for Ravi to implement this, or can we go ahead and do it
> ourselves as needed?
Feel free, Ravi will be busy with other controller functionality for
quite a while.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torpr
(Sorry, wasn't subscribed to tor-dev@, so these last couple of messages
didn't go there...)
On 6/29/12 4:09 PM, Damian Johnson wrote:
I think the question here is that it seems like one should be able to get
all the descriptors from the running Tor process via
GETINFO desc/all-recent
June was a pretty decent month!
With help from Mike Perry, I finished a couple of rounds of job
interviews, so we could select a new core developer. Let's welcome
Andrea Shepard to the Tor project; she's already off to a great
start, even though she's only part-time for her first couple of
months
> Keep in mind that metrics tarballs can be huge. stem's tests probably
> shouldn't download one or more of these tarballs in an automatic integ
> test run.
Oops yup. Should have mentioned that. We're just picking out a
descriptor that seems to exercise most of the parsing. This is just
for a san
Hi all,
below's what I did in June. Yes, there's still one more day left in
June, but I don't expect to do anything useful tomorrow other than
packing for Italy and pretending to have a half weekend.
Best,
Karsten
Fixed a few problems with the metrics website: bridge usage statistics
graphs we
2012/6/28 Damian Johnson :
>> Erik and I have finished the proc.py integration tests
>
> Great! I'm looking forward to checking them out.
>
>> Tomorrow, we will be starting the next Stem task regarding the Tor Export
>> project. Do you have any recommendations on where we should start exploring
>
On 6/28/12 11:37 PM, Damian Johnson wrote:
> - integ tests are pretty short, and just run the parser against some
> test data from the metrics archive and the cached consensus
Keep in mind that metrics tarballs can be huge. stem's tests probably
shouldn't download one or more of these tarballs
