-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/23/2014 10:15 AM, Georg Koppen wrote: [...] > Okay, sounds reasonable. What is the fallback plan for the case the > code is not getting open-sourced during the time you are working on > the topic? Do you have an "internal" deadline like: "If I/we don't > have the code by XXX I'll start an implementation from scratch"?
Peter kindly confirmed that I'll be able to access the code (even if it doesn't get published by then.) But, assuming the worst case, I'd start worrying on mid-July. > >> Also what is missing in the timeplan is my intention to >> implement ~everything except the backend a part of the QA >> process, and then reuse the code in the ultimate website (your >> suggestion). In addition to the new tests, I'll be working on the >> machine readable output, entropy calculation and submitting test >> machine fingerprints to a central database as a part of (2). >> >> Let me know if that makes sense or I can revise the timeplan >> (e.g. leave (3) to the end). > > Sounds good to me. > > Georg > > > > _______________________________________________ tor-dev mailing > list tor-dev@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTWABKAAoJEPb7JcMmVt4gXIYIAJdKJoC3h6rj9mTMkejzuzns 9PO/cxZ3ZB3tvX6CIYrfglgdfnh2SmdlId+kXv0eNhfN3Rz9pAp2QpLBH5CUcQGp ETZIj3/WzlCZNqTcNZv7qge0uL3yiLynEgnqwY2P4TQRnpjC7heVgWD0f2y+IR5s 6H3/NDnK5dGXXl+T+xKqPswPrtgkgYXTl4pkG5YPL52vrGLPRsLYXizovryT3aJ5 LC7ozLjGLCuV1ToAu1/JVON1Qla66UBGGwuiD39+/A6sIJSptSRT6epkOJaWPy7D pClD2whSggnl4nLg2hOPzxpnX/tM08vyPRCSPx4xNezm0KO0BY0kUs3k3E21cYM= =x2jO -----END PGP SIGNATURE----- _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev