Re : [Zope3-Users] Re: Zope 3 SSL
Thanks all for your answers. When I use twisted ssl by commenting the 8080 server and uncommenting the ssl server it seems to work. But I can't seem to be able to use apache as a proxy. Thanks again, Stéphane - Message d'origine De : Philipp von Weitershausen [EMAIL PROTECTED] À : zope3-users@zope.org Envoyé le : Jeudi, 24 Août 2006, 8h30mn 15s Objet : [Zope3-Users] Re: Zope 3 SSL Stéphane Brault wrote: Hi, I need to run my site with SSL. I don't know how to use SSL with Zope 3 or if I should run zope behind apache 2, and if so how. Any hint ? Most people have suggestd to run Zope behind Apache. This is certainly a very common way of doing it. You can also use twisted's built-in SSL support and run Zope 3 directly with SSL support. See the comments in zope.conf. Philipp ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] New open-sourced Zope Corporation packages
Zope Corporation is happy to announce a number of newly open-sourced packages. All are in use, in development, or both. We release these packages in the strong hope that others will contribute to them, from maintenance through extension to refactoring. The maintainers are effectively zope3-dev@zope.org. Since we rely on them, ZC will generally do some of those tasks ourselves; and we will have a strong stake in making sure that their development continues to support our internal needs. These packages are tested two or more times a day against the Zope 3 trunk. We hope to make 3.3 branches when 3.3 is released. In several cases, these will need a newer version of zope.testing than the one shipped with Zope 3.3, but otherwise we expect them to work in Zope 3.3 without too much tweaking. As we move our internal projects to zc.buildout, these projects will gain eggs, PyPI registration, and thus better documentation of their dependencies over the next weeks and months. Here are quick lists of the new packages, with summaries and status notes. Each project can be found on http://svn.zope.org/ with the given name, such as http://svn.zope.org/zc.comment/;. The actual code is found in trunk/src/zc/[package], such as http://svn.zope.org/ zc.comment/trunk/src/zc/comment/. The current svn-only distribution means that the code is currently largely in the realm of experienced Zope developers. The egg and PyPI work mentioned above will hopefully lower the bar when it is done. First, here are the packages that are largely stable and that we are using in active projects. - zc.comment An annotations-based drop-in aspect (i.e, no change to a class is necessary) that gives objects a comments tab. In production; maintenance mode. - zc.copy A pluggable `copy` function, replacing the one in zope.location; and an ObjectCopier that uses it. This allows object copies to be cleansed efficiently. In use by active projects; maintenance mode. - zc.freeze A way to spell freeze requests, and a few implementations and approaches. In use by active projects; maintenance mode. - zc.index Text extraction for XML, HTML, Word, OO, PDF, and RTF files, for the purpose of indexing. In production; maintenance mode. - zc.notification Simple user notification framework. Currently includes email notification, with email templating. Somewhat unstable API (need to review for scalability). In use by active projects; maintenance mode, though we would like to have time to return to it. - zc.objectlog TTW log with automatic changesets. In production; maintenance mode. - zc.preview File previews based on zope.mimetype interfaces. Currently somewhat minimal. In production; maintenance mode, though we would like to have time to return to it. - zc.security Simple user search. Not a big release, but a dependency for some packages such as the previously released zc.sharing. (Already released, but this is the first announcement.) In production; maintenance mode. - zc.selenium A way to write selenium tests in Python rather than in HTML tables, including a way to push and pop ZODB state from within selenium. In use; maintenance mode. - zc.tokenpolicy A small variation on the zc.sharing policy that makes the security policy enforce zope.locking tokens. Useful on its own and as an example of enforcing the pure-policy zope.locking tokens. In use by active projects; maintenance mode. - zc.vault A subversion-like repository stored in the ZODB, complex but powerful and useful for many low-level tasks. In use by active projects; maintenance mode for core, with occasional development of add-ons. - zc.winauth A pluggable authentication plugin for interacting with Windows authentication. In production; maintenance mode. - zope.html A zope form widget for HTML, using FCKEditor (thanks to Roger Ineichen for his version, from which he graciously helped us learn). In production; maintenance mode. Second, the following three packages are newly added and under development. We will make additional announcements as they become more stable. - zc.async Heir to Zope 2 zasync, and learning from its successes and failures, this supports asynchronous application calls, particularly as driven by end users in real-time. Alpha, but working in tests. - zc.set A persistent object akin to the persistent list and persistent mapping classes in the persistent package, but with a standard Python set API. (Note this has the same limitations as the persistent mapping and list classes--changing the contents means the whole set needs to be rewritten to the database, not just buckets as with BTree sets.) Beta. - zc.twist A partial for making ZODB calls from a Twisted reactor. Beta, but currently relies on some ZODB internals. Also note that we have a new zc.site package that is broken
Re: [Zope3-Users] New open-sourced Zope Corporation packages
Gary Poster wrote: Zope Corporation is happy to announce a number of newly open-sourced packages. All are in use, in development, or both. [snip long list] Awesome! And thanks for this announcement! And here Infrae's with only 3 hurry packages last year - I feel totally inadequate. :) Echoing some of the recent discussions, we should really focus on getting a web presence for these. Just a web page with some minimal information would already be very valuable. Anyway, that's just a note to myself - it might be a next project to tackle after we get a better Zope Foundation website, we'll see. Regards, Martijn ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] New open-sourced Zope Corporation packages
On Aug 24, 2006, at 12:14 PM, Martijn Faassen wrote: Gary Poster wrote: Zope Corporation is happy to announce a number of newly open- sourced packages. All are in use, in development, or both. [snip long list] Awesome! And thanks for this announcement! And here Infrae's with only 3 hurry packages last year - I feel totally inadequate. :) I think your lxml work gets you a decent amount of credit ;-) Echoing some of the recent discussions, we should really focus on getting a web presence for these. Just a web page with some minimal information would already be very valuable. Anyway, that's just a note to myself - it might be a next project to tackle after we get a better Zope Foundation website, we'll see. Agreed generally. We're hopeful that PyPI registrations (as I mentioned we hope to provide soon) will provide some of this. Perhaps Stephan's initiative will also bear fruit. Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] String Encoding problems in Skin
Objects containing a string attribute that have been 'copied/pasted' from some other application such as MS Office suite or email will raise an encoding error when attempting to be viewed in a Skin. The encoding issue is not a problem however when being viewed in the ZMI. Does anyone have a suggestion on why viewing the string in the ZMI is different than viewing in the Skin? And more importantly how to prevent the encoding error in the Skin, without resorting to replacing the character or deleting it. Much appreciated everyone. Thank you, Keith Bolton : ) ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope3-dev] z3c vs. the zorg
On Thursday 24 August 2006 16:54, Benji York wrote: Stephan's ZSCP proposal suggests using the package name z3c for community packages. IOW, packages that aren't part of a larger collection like lovely.*, zc.*, etc.. There are currently several z3c packages in existence. The zope3.org packages currently use the package name zorg. I personally (and at least a couple other people feel the same way) like zorg better than z3c. I'd like to propose that zorg become the name space package for otherwise homeless modules/packages. (In fairness, I'll note that Stephan likes z3c better, and that name is already in semi-wide-spread use). Right, thus I am clearly -1. :-) (Wow, now I do not even have to argue myself anymore. ;-) Note that we spent a lot of time coming up with this name and pretty much all the contributors to the namespace were involved in the discussion. Also, z3c does not try to be the holy grail of community work. It is just another namespace and I think this should be accepted. Zope Corp decided to use zc, Lovely Systems lovely and a bunch of us not representing a company decided to use z3c. So what's wrong with that? Should I create a foundation called Z3C to have the right get this namespace? Other people can feel free to work on another namespace. (BTW, I would without a thought change the working in the ZSCP document to be less asserting and globalizing.) I wonder how Zope Corp. would feel if I would ask them to use zcorp, because zc stands for Zope Community? BTW, I am not aggravated about the mail; I am just very tired of those pointless namespace discussions. Regards. Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope3-dev] z3c vs. the zorg
On 8/24/06, Benji York [EMAIL PROTECTED] wrote: If zc were to become zope community, I'd be *totally* for it (but I don't speak for ZC here, so that may not be cool with others, like say Jim). We'd either keep using zc under the new meaning, or switch to something else. z3c clearly stands for the Zope Zoftware Zystems Consortium, so should be freely used by the Z3C's members according to the usage rules established by that august body. The rest of us shouldn't be wasting time worrying about it. I'm sorry. It's off my chest now, so if this (mercifully) peters out soon, we'll all be better off. Indeed. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: z3c vs. the zorg
Benji York wrote: Stephan's ZSCP proposal suggests using the package name z3c for community packages. IOW, packages that aren't part of a larger collection like lovely.*, zc.*, etc.. There are currently several z3c packages in existence. The zope3.org packages currently use the package name zorg. I personally (and at least a couple other people feel the same way) like zorg better than z3c. I'd like to propose that zorg become the name space package for otherwise homeless modules/packages. +1 z3c looks a bit like a retarded 'z3' or 'zc'. (In fairness, I'll note that Stephan likes z3c better, and that name is already in semi-wide-spread use). Afaik, nothing has been released yet. Plus, changing the namesapce shouldn't be that hard, simple search'n'replace should do it... Philipp ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope3-dev] Re: z3c vs. the zorg
On Thursday 24 August 2006 16:57, Philipp von Weitershausen wrote: (In fairness, I'll note that Stephan likes z3c better, and that name is already in semi-wide-spread use). Afaik, nothing has been released yet. Plus, changing the namesapce shouldn't be that hard, simple search'n'replace should do it... We have plenty of internal releases. Not every development is visible to the world. Just because an egg does not exist, does not mean it has not been informally released or used in a released form internally. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: z3c vs. the zorg
Stephan Richter wrote: On Thursday 24 August 2006 16:54, Benji York wrote: Stephan's ZSCP proposal suggests using the package name z3c for community packages. IOW, packages that aren't part of a larger collection like lovely.*, zc.*, etc.. There are currently several z3c packages in existence. The zope3.org packages currently use the package name zorg. I personally (and at least a couple other people feel the same way) like zorg better than z3c. I'd like to propose that zorg become the name space package for otherwise homeless modules/packages. (In fairness, I'll note that Stephan likes z3c better, and that name is already in semi-wide-spread use). Right, thus I am clearly -1. :-) (Wow, now I do not even have to argue myself anymore. ;-) Note that we spent a lot of time coming up with this name and pretty much all the contributors to the namespace were involved in the discussion. Also, z3c does not try to be the holy grail of community work. It is just another namespace and I think this should be accepted. Zope Corp decided to use zc, Lovely Systems lovely and a bunch of us not representing a company decided to use z3c. So what's wrong with that? Should I create a foundation called Z3C to have the right get this namespace? Other people can feel free to work on another namespace. (BTW, I would without a thought change the working in the ZSCP document to be less asserting and globalizing.) I wonder how Zope Corp. would feel if I would ask them to use zcorp, because zc stands for Zope Community? BTW, I am not aggravated about the mail; I am just very tired of those pointless namespace discussions. Yeah, I see your point. We can't make you choose a particular namespace. But it's always good to set good examples. I think Benji and I are not the only ones to find that z3c is disturbing to read next to zc, for example. One thing you have to acknowledge is that svn.zope.org is community territory. It's not just a playground. I think we eventually want to enforce *some* rules (e.g. adding stuff to the 'zope' namespace might need blessing, etc.). One thing that I'm definitely disappointed of is that some z3c packages just ignore svn.zope.org's common repository layout (sandbox vs. trunk). I've mentioned that before, but nobody who's active in z3c responded nor did anything. Philipp ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope3-dev] z3c vs. the zorg
Stephan Richter wrote: Right, thus I am clearly -1. :-) (Wow, now I do not even have to argue myself anymore. ;-) :) Note that we spent a lot of time coming up with this name and pretty much all the contributors to the namespace were involved in the discussion. Sorry. Zope Corp decided to use zc, Lovely Systems lovely and a bunch of us not representing a company decided to use z3c. So what's wrong with that? I totally support your prerogative to name your packages whatever you want (within reason). My main thought are about long-term aesthetics. A hard to defend cause, I admit. (BTW, I would without a thought change the working in the ZSCP document to be less asserting and globalizing.) I wouldn't mind that. I wonder how Zope Corp. would feel if I would ask them to use zcorp, because zc stands for Zope Community? If zc were to become zope community, I'd be *totally* for it (but I don't speak for ZC here, so that may not be cool with others, like say Jim). We'd either keep using zc under the new meaning, or switch to something else. BTW, I am not aggravated about the mail; I am just very tired of those pointless namespace discussions. I'm sorry. It's off my chest now, so if this (mercifully) peters out soon, we'll all be better off. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
