[Zope3-dev] Add zope.deferredimport to svn toplevel
Hi, Can I commit zope.deferredimport to the toplevel of svn, like zope.interface,zope.proxy etc. I have added README.txt, setup.py, test.py etc. see this: http://zissue.berlios.de/z3/zope.deferredimport.tar.bz2 Please confirm these steps: $ svn mkdir svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ svn co svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ cd zope.deferredimport $ mkdir trunk $ mkdir branches $ mkdir tags $ svn add trunk branches tags $ cd trunk (Now add package here, then set svn:external to (in src/zope) deferredimport svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deferredimport Also set svn:ignore in / and src/) Then commit. Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Grrr. zope.org wikis are evil.
Fred Drake wrote: I've mostly learned to stay away from the wikis on zope.org, but some days, I just forget. I use a lot of wikis. And I like them, really. They're good for many applications, and the Zope 3 development wiki, while disorganized and somewhat dated, isn't really any worse than others. Until you want to update it. The edit form provides no link to help on markup, and there really aren't many wikis I use that use StructuredText, so I forget the details of syntax. There's also no way to preview changes before committing. That's a big problem. I think the zope.org wikis are the only public wikis I use that don't support previews. So whatever the ZF's plans for dealing with zope.org, I think there's no way to go wrong with the wikis except by keeping what we have now. While it's nice to use a Zope-based solution, I think we need to just get a solution that works. That could be a Zope 2 installation with a recent version of ZWiki, or something else (MoinMoin would make me happy as well, and has good reStructuredText support these days). So has anyone released a nice Zope 3 wiki yet? I might be interested. :-) There's a Zope 3 port of zwiki. Yeah, I'm grumbling. It's Friday night, and I've had it with the archaic StructuredText. If we end up using Trac, we'll be using that wiki. I have some wiki desires of my own that I'll probably never realize: - HTML WYSIWYG Wikis that don't use any form os structures text (small s) and just use an HTML editor. I think that structured text of any kind is an obstacle to Wiki use. Moin moin's markup rules drive me as batty as old Structured Text drives other people. ZWiki supports EPOZ editing and I'd love to see that used. Of course, this sort of experience avoids the need for preview or structured-text documentation. - Off-line editing. zsync provides a huge opportunity here. I wish someone had time to work on it. It would be totally cool to be able to check out a wiki onto a local hard disk, work on it, and merge my changes back. Oh well. I absolutely agree that we need to replace the existing wikis. One other thing we'll need to consider is anti-spam capabilities. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Add zope.deferredimport to svn toplevel
Baiju M wrote: Hi, Can I commit zope.deferredimport to the toplevel of svn, like zope.interface,zope.proxy etc. That would be great. Will you also release an egg to pypi? :) I have added README.txt, setup.py, test.py etc. see this: http://zissue.berlios.de/z3/zope.deferredimport.tar.bz2 Please confirm these steps: $ svn mkdir svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ svn co svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ cd zope.deferredimport $ mkdir trunk $ mkdir branches $ mkdir tags $ svn add trunk branches tags Minor note: I typically set up the full tree in the original transaction that sets up the project. You can give multiple directories on the mkdir line. I have a script named z that echos the repo url, so I'd do: svn mkdir `z`/zope.deferredimport `z`/zope.deferredimport/trunk `z`/zope.deferredimport/branches `z`/zope.deferredimport/tags $ cd trunk (Now add package here, then set svn:external to (in src/zope) deferredimport svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deferredimport Also set svn:ignore in / and src/) It would be nice to also turn it into a buildout so that you could run it's tests in a project checkout. See for example: http://www.python.org/pypi/zc.buildout#work-on-a-package Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grrr. zope.org wikis are evil.
Hi Jim, I have some wiki desires of my own that I'll probably never realize: - HTML WYSIWYG Wikis that don't use any form os structures text (small s) and just use an HTML editor. I think that structured text of any kind is an obstacle to Wiki use. Moin moin's markup rules drive me as batty as old Structured Text drives other people. ZWiki supports EPOZ editing and I'd love to see that used. Of course, this sort of experience avoids the need for preview or structured-text documentation. Wicked can do this, I believe, and it will likely (pending voting) be in Plone 3.0. You write ((foo)) and you get a wiki link to foo, regardless of text format. wicked is a bit AT specific, but whit is working to make it be more general, and factor out the re-usable bits. I'm sure he can chime in. - Off-line editing. zsync provides a huge opportunity here. I wish someone had time to work on it. It would be totally cool to be able to check out a wiki onto a local hard disk, work on it, and merge my changes back. I think this is a more general problem - doing proper online/offline sync of content. I'd love to have offline capabilities in Plone, for example. :) Martin ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Grrr. zope.org wikis are evil.
+1, they are an embarrassment. I am available to migrate them into the modern era, fix the broken configuration, etc. I would also support someone who wants to extract the content to moinmoin/mediawiki/svn if that were decided, though I think that would be sad :) (or not! better than moldering along for another few years). I can see why trac is also attractive. Jim, I'm about to oversimplify and sound ungrateful and hopefully out of date. Here it is: I honestly do not understand why you have not at some point made it your business to do something about zope.org ? My thinking goes like this: you invented zope, you are a principal of ZC, you have the root password on that server; we out here can do a lot, but without that power we essentially can't cure zope's crufty web presence. Specifically, I'm talking (in this thread) about getting one of the key tools used to publish Zope documentation upgraded or replaced. I've almost lost interest at this point. Not that I matter so much, but I'm at least somewhat representative. Forgive me for ranting to you of all people, who has given us such beautiful work. I'd like to understand better. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
