Re: [Zope-dev] Two visions?
Or Zed is the part of Zope that can be used without Zope. Yes, it's always been the Zed Object Publishing Environment. Now the Zed can get a job :-](I'm neutral regarding the suggestion.) -- jean ___ 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] Re: [Z3lab] Zope 3 / Z3ECM April sprint in Paris at Nuxeo
Stefane Fermigier wrote: Nuxeo, with the kind help of the Zope team of Chalmers University, plans to organise a Zope 3 sprint on April 3-7 in our premises in Paris. I'm afraid we'll have to change the dates, to accomodate for several schedule contraints (including room availability). So the sprint date is now: 17-21 April 2006. S. The focus of the sprint, like last year's successful sprint, will be ECM (Enterprise Content Management). Last year's Paris sprint was a turning point for the Zope roadmap, when it was decided to include Five in Zope 2.8, a decision which led to the current state of the Zope landscape (CMF 2.0 / CPS 3.4 / Plone 2.5 / Silva 1.5 - all full of Zope 3 components, etc.) We hope to make similar significant advances this year. Program: The current state of Z3ECM is currently best described in these slides: http://www.z3lab.org/sections/news/z3ecm-roadmap-september8593/ as well as on the www.z3lab.org website itself. 4 main themes for the sprint are currently emerging: - Repository: there is some unfinished conceptual and preliminary implementation work to be done regarding document repository design (including relations between documents, ORM-based storage, etc.) Ref: http://www.nuxeo.com/publications/slides/versioning-and-relation/downloadFile/file/versioning-ep-2005.pdf http://www.z3lab.org/sections/front-page/design-features/ecm-platform-concept/ - CPSSkins v3: Jean-Marc Orliaguet already has a very advanced implementation, that currently is Zope 3 only. We plan to bridge it with Zope 2 using Five to make it available on the current CMF-based platforms (at least CPS 3.4). Ref: http://www.z3lab.org/sections/blogs/jean-marc-orliaguet/archive_view?category=cpsskins http://svn.z3lab.org/trac/z3lab/browser/cpsskins/branches/jmo-perspectives/ - AJAX: we plan to generalize the current approach of CPSSkins v3, which is to use a JavaScript MVC library that exchanges JSON data structures with the server, to all the AJAX interactions. Ref: http://blogs.nuxeo.com/sections/blogs/tarek_ziade/archive_view?category=AJAX http://www.z3lab.org/sections/blogs/jean-marc-orliaguet/archive_view?category=AJAX - XForms: we intend to make XML Schemas and XForms the new model for documents and their representation in Z3ECM. This is specially important for interoperability with the Apogee project (http://apogee.nuxeo.org/). Ref: http://blogs.nuxeo.com/sections/blogs/eric_barroca/2005_09_05_ajax-does-not-compete/ At Nuxeo, we intend to make all these developments available either on top on CPS 3.4, or for the next iteration of CPS (CPS 3.6). But we'd also like to share these developments with the rest of the Zope 3 / CMF / Plone / etc. communities, if they are interested. Participation: The sprint is open to experimented Zope 3 / CMF / CPS / Plone developers. We already have booked 4-5 developers from Nuxeo, and Jean-Marc Orliaguet and Dario Lopez-Kärsten from Chalmers. Please join the discussion on the z3lab mailing list (http://lists.nuxeo.com/mailman/listinfo/z3lab) or contact me ([EMAIL PROTECTED]) if you would like to participate. The sprint is free (but you have to pay for your own travel and accomodation). We (Nuxeo) will modestly provide free pizzas / sandwiches / diet Coke, etc. NB: the dates (3-7 April) have been chosen so that long distance travelers can go to the Swiss sprint afterwards (8-13 April). If this is inconvenient for a majority of sprinters, we may change to the week after the Swiss sprint (17-21 April) but this change has to be decided quickly. I will confirm the date in a later announcement (next week). So, once again, let's followup on the z3lab list. S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ 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: [Zope3-dev] Re: [Zope-dev] Two visions
Jim Fulton wrote: [snip] I wasn't trying to define app server. I was describing the Zope app server. As long as you realize you do risk confusion even by saying 'Zope app server'. To me, Zope 3 is an app server, so when you say 'the Zope app server' will include its functionalities too. Regards, Martijn ___ 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] http access to svn repos?
Hi All, Would anyone be averse to making anonymous http checkouts possible from zope.org? Some of us are behind annoying proxies that won't let svn through :-/ cheers, Chris PS: https write access would be nice, but I guess that's out of the question? -- 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 )
[Zope-dev] Re: http access to svn repos?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Would anyone be averse to making anonymous http checkouts possible from zope.org? Some of us are behind annoying proxies that won't let svn through :-/ At one point, enabling the 'http:' checkout gateway was a sure-fire recipe for getting SVN's knickers in a twist, which is why we disabled it. Or maybe that was ViewCSV. In any case, I would guess that you might persuade folks to allow DAV-based checkout (which is what svn-over-http is), but you are likely to have to write it up as a proposal, including specific information about the Apache / SVN configuration changes required. PS: https write access would be nice, but I guess that's out of the question? Yes, definitely. The answer is the same as when you asked for it two years ago (: the WebDAV stuff is slow (which may be a reason not to allow annonymous http: checkouts, too), and the credentials mechanism is built entirely around the contributor's SSH key.. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEDFIO+gerLs4ltQ4RAkwfAKCYaDo9lObM0Ye3+2T7x4NPdF7ntwCgnVvO GOYCPxQvM2C7+UZEtMvyHcg= =UJXD -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 )
[Zope-dev] Windows Binary for 2.8.6?
Hi All, I notice 2.8.6 doesn't have a Windows binary either. What's the build process for that? I have a feeling I won't be able to help with that one since it probably need CV++ 6.0 which I don't have access to :-/ Can someone else pick this one up? 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 )
[Zope-dev] Re: [Zope3-dev] Principles
On Sun, Mar 05, 2006 at 10:09:14AM -0500, Geoff Davis wrote: One of the things that GTY recommends is to establish a set of agreed upon principles for evaluating proposals. I think that having such a set of principles would help us better focus our current discussion. Good idea. Let's take a step back from the particulars of the various proposals floating around and see if we can nail down some principles. Here is a very rough, very incomplete start: 1. Zope should have a clear message about where we are going. I'm sure we all agree on this, but this is so broad that it is not very useful. Here's a stab at refining it: 1.1 We should have a clear message about where Zope 2 is going. The message should give existing and prospective Zope 2 users an idea of how long their code will continue to work on releases in the Zope 2 path and what kind of upgrade process they will face as the Zope 2 line evolves. +1 1.2 Ditto for Zope 3. +1 2. Zope should try to expand its developer base. Again, I am sure we all agree, but this is too broad to be useful. 2.1 Zope should leverage the work of others by moving toward an architecture that allows one to easily use code from outside Zope. This effectively increases the developer base by letting us leverage the work of others outside the immediate Zope community. I assume that this (and integration) are the primary motivations driving the CA. 2.2 Zope should be useful for developers not using the full application server stack. Again, this serves to increase our developer base by drawing in people outside our traditional core audience. +1 We probably need some principles about the Zope brand, and so on, That seems like the most contentious part, and a lot of Jim's suggestions and the ensuing discussion have focused on this. There are several possible principles here, which may pull in different directions because they target different audiences. I started writing some suggested principles but I don't want to start another cycle of repetitious debate on that topic; I'd first rather see some more feedback on the principles you suggested so far. -- Paul Winkler http://www.slinkp.com ___ 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] Windows Binary for 2.8.6?
[Chris Withers] I notice 2.8.6 doesn't have a Windows binary either. What's the build process for that? Try to detect the pattern between this and previous answers ;-): http://svn.zope.org/Zope/branches/Zope-2_8-branch/inst/WinBuilders/README.txt I have a feeling I won't be able to help with that one since it probably need CV++ 6.0 Correct. which I don't have access to :-/ Can someone else pick this one up? If nobody beats me to it, I will, eventually. ___ 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] Windows Binary for 2.8.6?
Tim Peters wrote: Try to detect the pattern between this and previous answers ;-): http://svn.zope.org/Zope/branches/Zope-2_8-branch/inst/WinBuilders/README.txt Hehe, okay, touché :-P I have a feeling I won't be able to help with that one since it probably need CV++ 6.0 Correct. which I don't have access to :-/ Can someone else pick this one up? If nobody beats me to it, I will, eventually. I suspect that'll be fairly easy in this instance ;-) 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 )
[Zope-dev] Re: http access to svn repos?
Tres Seaver wrote: At one point, enabling the 'http:' checkout gateway was a sure-fire recipe for getting SVN's knickers in a twist, which is why we disabled it. Or maybe that was ViewCSV. It was ViewCSV, in particular, the tarball download... In any case, I would guess that you might persuade folks to allow DAV-based checkout (which is what svn-over-http is), but you are likely to have to write it up as a proposal, including specific information about the Apache / SVN configuration changes required. Where should I write the proposal? Who is going to review it? I'm all for just doing it and reverting it if there are problems... Yes, definitely. The answer is the same as when you asked for it two years ago (: the WebDAV stuff is slow (which may be a reason not to allow annonymous http: checkouts, too), I'm fairly sure SourceForge uses https for it's writeable svn service. I might be mistaken on that, but if I'm not, I doubt there are issues... and the credentials mechanism is built entirely around the contributor's SSH key.. yes, this sucks :-/ 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 )
[Zope-dev] Re: http access to svn repos?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Tres Seaver wrote: At one point, enabling the 'http:' checkout gateway was a sure-fire recipe for getting SVN's knickers in a twist, which is why we disabled it. Or maybe that was ViewCSV. It was ViewCSV, in particular, the tarball download... In any case, I would guess that you might persuade folks to allow DAV-based checkout (which is what svn-over-http is), but you are likely to have to write it up as a proposal, including specific information about the Apache / SVN configuration changes required. Where should I write the proposal? Who is going to review it? http://www.zope.org/Wikis/DevSite/Proposals ; post here and zope3-dev for review. I'm all for just doing it and reverting it if there are problems... You need to identify potential issues, document any changes needed to the Apache config (to enable the DAV verbs, for instance), and spell out how to revert it; then get the rest of the community to accept it, at least tacitly. Yes, definitely. The answer is the same as when you asked for it two years ago (: the WebDAV stuff is slow (which may be a reason not to allow annonymous http: checkouts, too), I'm fairly sure SourceForge uses https for it's writeable svn service. I might be mistaken on that, but if I'm not, I doubt there are issues... - -1 on using https for writable checkouts. The issues aren't so much technical feasibility as social / legal: a checkin done using somebody's private key is way less deniable than one done with a password. Unless you plan to set up a system for issuing client certificates to contributors, I don't think https is superior to svn+ssh at all. and the credentials mechanism is built entirely around the contributor's SSH key.. yes, this sucks :-/ It's *by design*. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEDMc9+gerLs4ltQ4RAnGXAKDQFNkxsqRV+W82SZh5yLlbeJIYdgCglCV5 7rizxM8sF3bXk0P+9yDNnIU= =9yuP -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 )
Re: [Zope-dev] Re: http access to svn repos?
Tres Seaver schrieb: Chris Withers wrote: ... Where should I write the proposal? Who is going to review it? http://www.zope.org/Wikis/DevSite/Proposals ; post here and zope3-dev for review. +1 for http anon checkouts at least :-) ... -1 on using https for writable checkouts. The issues aren't so much technical feasibility as social / legal: a checkin done using somebody's private key is way less deniable than one done with a password. Unless you plan to set up a system for issuing client certificates to contributors, I don't think https is superior to svn+ssh at all. I think a possible solution would be client certificate on request and downloadable with ssh from users account - maybe even automatically generation of client cert via ssh for acredited contributors. At least this would be equaly secure/insecure as current ssh-pubkey only. Otoh, if you want to make it right [tm] you need a fairly complicated CA-setup. Including isolated box, sneakers-net or at least some solution with serial interface... really a lot of work. (But this would be more secure then we have now with the simple publickey) Regards Tino ___ 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] Question about manage_afterAdd in 2.9.1
Hi All, I've started seeing warnings like this with an instance I'm moving from Zope 2.7 to 2.9: C:\Zope\2.9.1\lib\python\OFS\subscribers.py:74: DeprecationWarning: Products.CookieCrumbler.CookieCrumbler.CookieCrumbler.manage_afterAdd is deprecated and will be removed in Zope 2.11, you should use event subscribers instead, and meanwhile mark the class with five:deprecatedManageAddDelete/ DeprecationWarning) Is there an example of exactly what I need to add and where? 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 )
