Request to expunge project 'torsocks' on Google Code
Sitting with David Goulet, it's problematic that when I search for "torsocks" I get the old Google Code page instead of the up-to-date page on http://gitweb.torproject.org This is problematic because people report bugs to the Google Code repository instead of the torproject repository. Jake/Robert: You are the project owners on Google Code. Could you please remove the project? Much love, -Virgil
On Sun, Feb 23, 2014 at 6:11 AM, Virgil Griffith <i@virgil.gr> wrote:
Sitting with David Goulet, it's problematic that when I search for "torsocks" I get the old Google Code page instead of the up-to-date page on http://gitweb.torproject.org
This is problematic because people report bugs to the Google Code repository instead of the torproject repository.
Jake/Robert: You are the project owners on Google Code. Could you please remove the project?
I'm +1 on removing the google code project, and +1 on replacing the torsocks that's at https://gitweb.torproject.org/ with David Goulet's version once one more smart person has audited it. (Though at this point, I am pretty sure that David's version is a strict improvement over the old version.) peace, -- Nick
I think this is a fine idea - if no one objects, I'll purge it. On 2/23/14, Virgil Griffith <i@virgil.gr> wrote:
Sitting with David Goulet, it's problematic that when I search for "torsocks" I get the old Google Code page instead of the up-to-date page on http://gitweb.torproject.org
This is problematic because people report bugs to the Google Code repository instead of the torproject repository.
Jake/Robert: You are the project owners on Google Code. Could you please remove the project?
Much love, -Virgil
On 2014-02-26 13:46, Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
No objection per-se, but a recommendation/check-up: check how google handles removal and if it allows a new project of the same name to be created there. This as it would otherwise be easy to start 'stealing' traffic and such (though then reporting it to google abuse might resolve that). As such, either they do not allow recreation for at least a few months till all links expire, or likely better: empty the repo, disable most features and put a big "we are not at X" thing on the main page, even changing the project title etc to reference the same. Greets, Jeroen
On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
On 2014-02-26 13:46, Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
No objection per-se, but a recommendation/check-up:
Sounds great to me -- disabling it seems like the best option, along with (if doable) marking it as "moved to the new url". As Jeroen says, we don't want somebody showing up and starting a google code project called torsocks. (I just found myself trying to help somebody on #tor with torsocks, and it was totally not clear to me where torsocks actually lives today.) Thanks! --Roger
On 28 Feb (22:19:39), Roger Dingledine wrote:
On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
On 2014-02-26 13:46, Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
No objection per-se, but a recommendation/check-up:
Sounds great to me -- disabling it seems like the best option, along with (if doable) marking it as "moved to the new url". As Jeroen says, we don't want somebody showing up and starting a google code project called torsocks.
(I just found myself trying to help somebody on #tor with torsocks, and it was totally not clear to me where torsocks actually lives today.)
Just to follow up this. The current code (1.3) is at git.tpo.org/torsocks.git. The 2.x version is at https://github.com/dgoulet/torsocks. Hopefully, we get the new one soon upstream and that would mean one central point for the code. I'll join #tor so I can help with torsocks questions. Thanks! David
Thanks! --Roger
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On 28 Feb (22:19:39), Roger Dingledine wrote:
On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
On 2014-02-26 13:46, Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
No objection per-se, but a recommendation/check-up:
Sounds great to me -- disabling it seems like the best option, along with (if doable) marking it as "moved to the new url". As Jeroen says, we don't want somebody showing up and starting a google code project called torsocks.
(I just found myself trying to help somebody on #tor with torsocks, and it was totally not clear to me where torsocks actually lives today.)
With the release of the 2.0 stable version, this should be closed *ASAP*. Thanks! David
Thanks! --Roger
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hello again! I want to reiterate very strongly that this page needs to be closed OR at the very least should point to the official git.tpo code. Please, who ever has admin right to the Google code torsocks page, manifest yourself. This is important, the 1.3 code is not safe and unmaintained. Thanks! David On 16 Aug (10:25:55), David Goulet wrote:
On 28 Feb (22:19:39), Roger Dingledine wrote:
On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
On 2014-02-26 13:46, Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
No objection per-se, but a recommendation/check-up:
Sounds great to me -- disabling it seems like the best option, along with (if doable) marking it as "moved to the new url". As Jeroen says, we don't want somebody showing up and starting a google code project called torsocks.
(I just found myself trying to help somebody on #tor with torsocks, and it was totally not clear to me where torsocks actually lives today.)
With the release of the 2.0 stable version, this should be closed *ASAP*.
Thanks! David
Thanks! --Roger
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On 26 Feb (12:46:09), Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
Everything is on Torproject now (git and trac). I closed the trackers on github after moving open issues on trac.tpo. So, go for me to close the Google code. Cheers! David
On 2/23/14, Virgil Griffith <i@virgil.gr> wrote:
Sitting with David Goulet, it's problematic that when I search for "torsocks" I get the old Google Code page instead of the up-to-date page on http://gitweb.torproject.org
This is problematic because people report bugs to the Google Code repository instead of the torproject repository.
Jake/Robert: You are the project owners on Google Code. Could you please remove the project?
Much love, -Virgil
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
participants (6)
-
David Goulet -
Jacob Appelbaum -
Jeroen Massar -
Nick Mathewson -
Roger Dingledine -
Virgil Griffith