Re: [Zope-dev] Zope Source Code Repository
Gary Poster wrote: Where's the visual diff? Where's the interactive log of revisions? Where's the repository browser? FWIW, I don't know if TortoiseBzr has this. I'd be surprised if it didn't have these, especially the first two. TortoiseSVN's log is now *very* interactive. I'd be surprised if TortoiseBzr *did* haev that level of interactivity, given how many years it took tsvn to grow it ;-) Does it work the same on Windows, Ubuntu and Mac OS? (I assume you mean bzr vs.svn, rather than TortoiseBzr vs. TortoiseSvn; AFAICT, Tortoise* is Windows only.) No, I mean TortoiseBzr. As I said to Mark Hammond when chatting about Bzr, having a *great* gui tool equivalent to TortoiseSvn that worked *cross platform* would be a *major* reason to move to that rcs. Anything less is just interesting. Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Laurence Rowe wrote: Previously Marius Gedminas wrote: BTW I've yet to see a firewall that blocks SSH. Am I lucky? Yes. Blocking ssh is very common in larger companies in me experience. An ssh server running on port 443 (HTTPS) can come in very handy. ssh -D gives you a socks proxy, tsocks makes using this transparent (e.g. tsocks bin/buildout). Failing that, 3G modems are quite reasonable nowdays. I'd like to see you do either of these two tricks on a big corporate's network, particularly the latter, for any length of time and keep your job... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Hanno Schlichting wrote: Dieter Maurer wrote: Unless newer SVN versions improved on this: using different access protocols is hampered by svn:external as they were (still are?) required to be absolute urls (including the protocal). This way, the access protocol may change in between of a checkout (involving svn:externals). svn:externals can be relative in many ways since SVN 1.5. Just beware, 1.5 sucks: http://subversion.tigris.org/issues/show_bug.cgi?id=3242 http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019 http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525 Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
2009/4/6 Chris Withers ch...@simplistix.co.uk: Laurence Rowe wrote: Previously Marius Gedminas wrote: BTW I've yet to see a firewall that blocks SSH. Am I lucky? Yes. Blocking ssh is very common in larger companies in me experience. An ssh server running on port 443 (HTTPS) can come in very handy. ssh -D gives you a socks proxy, tsocks makes using this transparent (e.g. tsocks bin/buildout). Failing that, 3G modems are quite reasonable nowdays. I'd like to see you do either of these two tricks on a big corporate's network, particularly the latter, for any length of time and keep your job... Nah, this would only be a problem if you worked with the IT department, everyone else prefers that you get more work done. Obviously with the 3G card my laptop was not connected to the network. Laurence ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Mon, Apr 6, 2009 at 10:32, Chris Withers ch...@simplistix.co.uk wrote: Just beware, 1.5 sucks: http://subversion.tigris.org/issues/show_bug.cgi?id=3242 http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019 http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525 It sucks for very specific cases, namely tight access control on sub-paths. I don't see such cases, and I see speed improvements instead. Note that we are now up to svn 1.6. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Martijn Pieters wrote: On Mon, Apr 6, 2009 at 10:32, Chris Withers ch...@simplistix.co.uk wrote: Just beware, 1.5 sucks: http://subversion.tigris.org/issues/show_bug.cgi?id=3242 http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019 http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525 It sucks for very specific cases, namely tight access control on sub-paths. I'm more worried about the lack of merging working and random errors when adding files. Those are pretty serious failures from where I'm sitting... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Previously Martijn Pieters wrote: On Mon, Apr 6, 2009 at 10:32, Chris Withers ch...@simplistix.co.uk wrote: Just beware, 1.5 sucks: http://subversion.tigris.org/issues/show_bug.cgi?id=3242 http://thread.gmane.org/gmane.comp.version-control.subversion.user/84308/focus=84019 http://thread.gmane.org/gmane.comp.version-control.subversion.user/87346/focus=87525 It sucks for very specific cases, namely tight access control on sub-paths. I don't see such cases, and I see speed improvements instead. Note that we are now up to svn 1.6. Which still does not fix this, and is preventing people from upgrading to the 1.5 client, and thus from using checkouts using relative paths. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Mon, Apr 6, 2009 at 10:39, Chris Withers ch...@simplistix.co.uk wrote: I'm more worried about the lack of merging working and random errors when adding files. Those are pretty serious failures from where I'm sitting... The merging is due to lack of merging info when branching, the 'random errors' are not random but due to svn info being out-of-date after a commit. svn up has always solved that for me. Yes, the latter is a bug, but I suspect it is already solved in 1.6 (didn't test that yet though). -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Martijn Pieters wrote: On Mon, Apr 6, 2009 at 11:53, Wichert Akkerman wich...@wiggy.net wrote: Note that we are now up to svn 1.6. Which still does not fix this, and is preventing people from upgrading to the 1.5 client, and thus from using checkouts using relative paths. Bugger, that is indeed correct. I may not have any problems (and a workaround for svn bug 3119) but that doesn't mean we can ask other people that need access to more tightly ACL-ed repositories to put up with subversion 1.5 and 1.6. To be honest, the state of svn 1.5 is what's getting me to think about looking at mercurial. (bzr didn't take my fancy, and hg is gonna be used by the python-core folks, so I might as well learn that...) Sadly, I suspect none of the tools are as advanced as TortoiseSVN. Which is a real shame :-( Perforce maybe? ;-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Mon, Apr 6, 2009 at 11:53, Wichert Akkerman wich...@wiggy.net wrote: Note that we are now up to svn 1.6. Which still does not fix this, and is preventing people from upgrading to the 1.5 client, and thus from using checkouts using relative paths. Bugger, that is indeed correct. I may not have any problems (and a workaround for svn bug 3119) but that doesn't mean we can ask other people that need access to more tightly ACL-ed repositories to put up with subversion 1.5 and 1.6. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 6, 2009, at 9:28 AM, Chris Withers wrote: Gary Poster wrote: Sadly, I suspect none of the tools are as advanced as TortoiseSVN. Which is a real shame :-( Perforce maybe? ;-) Fair enough that bzr didn't take your fancy, but FWIW, did you try TortoiseBzr? That has received love relatively recently. I'm looking at this: http://bazaar-vcs.org/TortoiseBzr/Screenshots Where's the visual diff? Where's the interactive log of revisions? Where's the repository browser? FWIW, I don't know if TortoiseBzr has this. I'd be surprised if it didn't have these, especially the first two. It would be cool if someone with easy access to Windows were to check this out. Otherwise, I'll give it a try eventually and report back myself. (If it has these features, I'll try to figure out someone to ask to get that page updated.) Does it work the same on Windows, Ubuntu and Mac OS? (I assume you mean bzr vs.svn, rather than TortoiseBzr vs. TortoiseSvn; AFAICT, Tortoise* is Windows only.) Well, the EOL problem has been the only bzr kicker there. That was just addressed, spurred most recently in part because of the concerns from the Zope community; I don't know if it is in 1.13 or the upcoming 1.14. Other than that, I think bzr cares a fair amount about Windows (and certainly about Ubuntu and Mac). http://tortoisesvn.net/image/tid/13 gives a fair idea of the kinds of things I'd need to feel compelled to change... Right. Looks nice enough. Gary___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Marius Gedminas wrote at 2009-4-3 01:34 +0300: On Thu, Apr 02, 2009 at 07:31:00PM +0100, Chris Withers wrote: So, svn.zope.org causes me pain at the moment: - it uses the bizarre svn or svn+ssh protocols, which I find annoying (ports blocked on routers, can't check with a browser, etc) +10 for continuing to support svn+ssh, it's the best thing ever! * secure (passphrase-protected key) * convenient (ssh-agent means you only type the passphrase once) * convenient to use remotely (ssh agent forwarding means I ssh into a remote server and can use svn without having to store a key or a password anywhere on that remote server) The story may be different for Windows users (as usual). +0.5 for alternatively accepting authenticated https access (I'm not the admin, so it doesn't cost me, but I'm also not going to use it) Unless newer SVN versions improved on this: using different access protocols is hampered by svn:external as they were (still are?) required to be absolute urls (including the protocal). This way, the access protocol may change in between of a checkout (involving svn:externals). -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Dieter Maurer wrote: Unless newer SVN versions improved on this: using different access protocols is hampered by svn:external as they were (still are?) required to be absolute urls (including the protocal). This way, the access protocol may change in between of a checkout (involving svn:externals). svn:externals can be relative in many ways since SVN 1.5. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Sun, Apr 05, 2009 at 09:10:10AM +0200, Dieter Maurer wrote: Marius Gedminas wrote at 2009-4-3 01:34 +0300: On Thu, Apr 02, 2009 at 07:31:00PM +0100, Chris Withers wrote: So, svn.zope.org causes me pain at the moment: - it uses the bizarre svn or svn+ssh protocols, which I find annoying (ports blocked on routers, can't check with a browser, etc) +10 for continuing to support svn+ssh, it's the best thing ever! * secure (passphrase-protected key) * convenient (ssh-agent means you only type the passphrase once) * convenient to use remotely (ssh agent forwarding means I ssh into a remote server and can use svn without having to store a key or a password anywhere on that remote server) The story may be different for Windows users (as usual). +0.5 for alternatively accepting authenticated https access (I'm not the admin, so it doesn't cost me, but I'm also not going to use it) Unless newer SVN versions improved on this: using different access protocols is hampered by svn:external as they were (still are?) required to be absolute urls (including the protocal). This way, the access protocol may change in between of a checkout (involving svn:externals). This is a very good point I'd forgotten about. However, currently the existing svn:externals all point to read-only svn:// URLs, and switching them to http:// would not change anything substantially. Subversion 1.5 lets you use relative URLs in svn:external, if you're willing to forgo compatibility with Subversion 1.4 clients. See http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Sun, Apr 5, 2009 at 17:48, Marius Gedminas mar...@gedmin.as wrote: This is a very good point I'd forgotten about. However, currently the existing svn:externals all point to read-only svn:// URLs, and switching them to http:// would not change anything substantially. Nope, but switching then to https:// would. But switching to relative URLs would also solve them problem. -- Lennart Regebro: Pythonista, Barista, Notsotrista. http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Wichert Akkerman wrote: Previously Marius Gedminas wrote: BTW I've yet to see a firewall that blocks SSH. Am I lucky? Yes. Blocking ssh is very common in larger companies in me experience. An ssh server running on port 443 (HTTPS) can come in very handy. ssh -D gives you a socks proxy, tsocks makes using this transparent (e.g. tsocks bin/buildout). Failing that, 3G modems are quite reasonable nowdays. Laurence ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
My 2 cents: I like svn over https. It works reliably, and is easy to use, and externals work as expected, etcs. So I'm +1 on allowing https access. That said, svn+ssh tunnels svn over ssh, and if you are in a place where ssh doesn't work, you need to find the network admit and punch him in the face. -- Lennart Regebro: Pythonista, Barista, Notsotrista. http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 7:35 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: I'd like to report back on the progress that Bzr/Launchpad has made addressing concerns we heard since I last brought up Canonical's offer to host the code and contribute commercial support for the transition. [snip saying I'll do it later, and apology for misunderstanding of Foundation membership] The foundation members are a *subset* of all committers, with sponsoring companies added on. There are under 50 nominated members (formerly committer members, whereas there are something like 375 committers. Any decision to move the repository will need to be formally made by the foundation (via its board), but that would only happen if the consensus of the members and the wider community were clearly in favor of a move. Good to know, thank you. Off to write the email... Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 6:34 PM, Marius Gedminas wrote: - the web front end is ancient and not as good as other options (Trac, WebSVN) +1 for having trac as a subversion browser. In fact, see http://zope3.pov.lt/trac The svn repository mirror used by that trac instance is updated with svnsync every 5 minutes Should we all just use that? Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Fri, Apr 3, 2009 at 14:41, Jim Fulton j...@zope.com wrote: Should we all just use that? It's running trac 0.10. I'd love to see trac 0.11, which has additional features that I miss every time I use a 0.10 trac instance, such as the annotate view. Also, I'd include the subversion location plugin, which includes a link to the http:// or svn+ssh:// url for the currently viewed location, for easy checking out. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Fri, Apr 03, 2009 at 03:04:47PM +0200, Martijn Pieters wrote: On Fri, Apr 3, 2009 at 14:41, Jim Fulton j...@zope.com wrote: Should we all just use that? (that being http://zope3.pov.lt/trac) Sure, I don't mind. It sits behind an ADSL line with puny uplink (512 Kbit/s), but I don't think that will be a problem. It's running trac 0.10. I'd love to see trac 0.11, which has additional features that I miss every time I use a 0.10 trac instance, such as the annotate view. Trac 0.11 has annotate? *WANT* Also, I'd include the subversion location plugin, which includes a link to the http:// or svn+ssh:// url for the currently viewed location, for easy checking out. Sounds good. I'll look into this some time soon. Ping me in a week or so if I forget. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.04.2009 17:22 Uhr, Marius Gedminas wrote: On Fri, Apr 03, 2009 at 03:04:47PM +0200, Martijn Pieters wrote: On Fri, Apr 3, 2009 at 14:41, Jim Fulton j...@zope.com wrote: Should we all just use that? (that being http://zope3.pov.lt/trac) Sure, I don't mind. It sits behind an ADSL line with puny uplink (512 Kbit/s), but I don't think that will be a problem. Nothing against your generous offer but I think that trac belongs as a central service on the central repository server. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknWKqsACgkQCJIWIbr9KYzcDgCfaKnN7ogpElGw4JoaRENrlCi4 Kf0AnjeaWL88tkrB4taIzL4/KczpQc9U =8ugy -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Marius Gedminas wrote: The story may be different for Windows users (as usual). +0.5 for alternatively accepting authenticated https access (I'm not the admin, so it doesn't cost me, but I'm also not going to use it) BTW I've yet to see a firewall that blocks SSH. Am I lucky? Yup. In fact, see http://zope3.pov.lt/trac The svn repository mirror used by that trac instance is updated with svnsync every 5 minutes. Wouldn't it be great if you didn't have to do the mirroring (which must do a bit of pounding on svn.zope.org) I would not mind spending some time in a sprint writing a Zope 3 svn key management web app, but that's only a small part of the solution. Authentication and deployment are the other---bigger--two parts. Yes, this was why I was asking on the Foundation list: I want to know what's happening about what machines get used for this stuff... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Andreas Jung wrote: Sure, I don't mind. It sits behind an ADSL line with puny uplink (512 Kbit/s), but I don't think that will be a problem. Nothing against your generous offer but I think that trac belongs as a central service on the central repository server. +1, although if we were to give Marius access to the box, I'm sure he could set it up there and we'd all get what we want (including Marius desire to do the work ;-) ) cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Previously Marius Gedminas wrote: BTW I've yet to see a firewall that blocks SSH. Am I lucky? Yes. Blocking ssh is very common in larger companies in me experience. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Source Code Repository
Hey All, I got bitten by the current zope subversion setup at PyCon so thought I'd mail the appropriate groups about it. If this has been covered elsewhere and I've missed anything, please just point me in the right direction... So, svn.zope.org causes me pain at the moment: - it uses the bizarre svn or svn+ssh protocols, which I find annoying (ports blocked on routers, can't check with a browser, etc) - the web front end is ancient and not as good as other options (Trac, WebSVN) - the process for adding keys is baroque and managed by one person who is too busy to help with it (Jim) So I thought I'd ask what the plans are now that the foundation owns all the Zope IP (has this happened yet or am I imagining things?) Are we sticking with svn? Are we sticking with the current hosting? Are we sticking with the current key-based login and upload mechanism? For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I volunteer to help with any/all of the above. The other option would be to follow Python and move to Mercurial, but that has the same problems for me as with Bzr (no decent gui tools, less mature, etc) although it's a toolset I'll have to learn at some point anyway... cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I absolutely *hate* using https to access subversion. This involves storing a key in plane text in my home directory, which is terrible. I far prefer using ssh-based infrastructure for this sort of thing. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.04.2009 20:39 Uhr, Jim Fulton wrote: On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I absolutely *hate* using https to access subversion. This involves storing a key in plane text in my home directory, which is terrible. I far prefer using ssh-based infrastructure for this sort of thing. Really? I have never stored a plain text password for SVN over https within my home dir. I also can not find anything related within .subversion/ in my home dir. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknVB6MACgkQCJIWIbr9KYy/OwCgvp2OPXzv/VFF2N09/fza6092 wiAAnRujl2mx2SRiviWclhWfnpDpiCqQ =xYXr -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Jim Fulton wrote: On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I absolutely *hate* using https to access subversion. This involves storing a key in plane text in my home directory, which is terrible. I far prefer using ssh-based infrastructure for this sort of thing. For write access I completely agree. For read-only unauthenticated access it would be nice to be able to use http(s). It may be possible to have it all at the same time. - Jacob ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 2:44 PM, Chris Withers wrote: This involves storing a key in plane text in my home directory, which is terrible. How do you not have the same thing with ssh? ssh keys are pass-phrase protected and ssh-agent allows me to enter the pass phrase once in a session. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Jim Fulton wrote: On Apr 2, 2009, at 2:31 PM, Chris Withers wrote: For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I absolutely *hate* using https to access subversion. Well, I absolutely *hate* using ssh to access subversion. This involves storing a key in plane text in my home directory, which is terrible. How do you not have the same thing with ssh? Myself, I work from a variety of machines on a variety of different platforms, and trying to juggle multiple public keys with undocumented and unsupported upload facilities is painful. The alternative is to try and juggle one public key across multiple machines and ssh implementations which is just as painful, not to mention insecure. I far prefer using ssh-based infrastructure for this sort of thing. I prefer using password-protected (as opposed to key-protected) https. What do other people prefer? Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Chris Withers wrote at 2009-4-2 19:44 +0100: ... I prefer using password-protected (as opposed to key-protected) https. What do other people prefer? I am fine with the ssh access. True, the initial setup was a bit difficult (the key program did not like the . in d.maurer -- but forgot to tell so) but Jim spare enough time to help me overcome the problem. After I changed my username from d.maurer to dmaurer, everything worked immediately. I would not like to enter my password every time I call svn. If this can be arranged, I am content. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Dieter Maurer wrote: I would not like to enter my password every time I call svn. If this can be arranged, I am content. It can, and with svn 1.6 it's even secure :-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Jacob Holm wrote at 2009-4-2 20:44 +0200: ... For write access I completely agree. For read-only unauthenticated access it would be nice to be able to use http(s). It may be possible to have it all at the same time. I have been told that there are mirrors of the Zope SVN repository providing read access via http. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
Dieter Maurer wrote: I have been told that there are mirrors of the Zope SVN repository providing read access via http. Shame none of them is advertised anywhere... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Thu, Apr 02, 2009 at 07:31:00PM +0100, Chris Withers wrote: So, svn.zope.org causes me pain at the moment: - it uses the bizarre svn or svn+ssh protocols, which I find annoying (ports blocked on routers, can't check with a browser, etc) +10 for continuing to support svn+ssh, it's the best thing ever! * secure (passphrase-protected key) * convenient (ssh-agent means you only type the passphrase once) * convenient to use remotely (ssh agent forwarding means I ssh into a remote server and can use svn without having to store a key or a password anywhere on that remote server) The story may be different for Windows users (as usual). +0.5 for alternatively accepting authenticated https access (I'm not the admin, so it doesn't cost me, but I'm also not going to use it) BTW I've yet to see a firewall that blocks SSH. Am I lucky? - the web front end is ancient and not as good as other options (Trac, WebSVN) +1 for having trac as a subversion browser. In fact, see http://zope3.pov.lt/trac The svn repository mirror used by that trac instance is updated with svnsync every 5 minutes. - the process for adding keys is baroque and managed by one person who is too busy to help with it (Jim) I would not mind spending some time in a sprint writing a Zope 3 svn key management web app, but that's only a small part of the solution. Authentication and deployment are the other---bigger--two parts. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
On Apr 2, 2009, at 1:31 PM, Chris Withers wrote: Hey All, ... The other option would be to follow Python and move to Mercurial, but that has the same problems for me as with Bzr (no decent gui tools, less mature, etc) although it's a toolset I'll have to learn at some point anyway... I'd like to report back on the progress that Bzr/Launchpad has made addressing concerns we heard since I last brought up Canonical's offer to host the code and contribute commercial support for the transition. When I do that, I'll do it on zope-dev, assuming that Tres' statement in this thread that we should discuss there is authoritative. (I thought the people on Foundations were the superset of people who commit to the repo, but I guess I was mistaken. Sorry for my misunderstanding.) However, I just got back from a long trip, and I'm going to spend some time with my family. I'll write something up to zope-dev tomorrow. Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Source Code Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: I'd like to report back on the progress that Bzr/Launchpad has made addressing concerns we heard since I last brought up Canonical's offer to host the code and contribute commercial support for the transition. When I do that, I'll do it on zope-dev, assuming that Tres' statement in this thread that we should discuss there is authoritative. (I thought the people on Foundations were the superset of people who commit to the repo, but I guess I was mistaken. Sorry for my misunderstanding.) The foundation members are a *subset* of all committers, with sponsoring companies added on. There are under 50 nominated members (formerly committer members, whereas there are something like 375 committers. Any decision to move the repository will need to be formally made by the foundation (via its board), but that would only happen if the consensus of the members and the wider community were clearly in favor of a move. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ1VnB+gerLs4ltQ4RAtvVAJ4kPghyM3nlJGRNQN5vsJazrhR+6wCfZRui WwEbnYYd59eXJ9FOHYD9ZuM= =gtgH -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
