| *** niemeyer is now known as nie_away | 00:11 | |
| mp | you have to check whether pricipal provides interface | 00:13 |
|---|---|---|
| mp | roym: for example if user has logged in: not IUnauthenticatedPrincipal.providedBy(self.request.principal) | 00:13 |
| *** nie_away is now known as niemeyer | 00:21 | |
| roym | from reading the tests, it looks like principalRoleManager.getRolesForPrincipal(principal) | 00:49 |
| roym | should work; however in my tests, I am getting an empty list. | 00:49 |
| roym | where principalRoleManager is zope/app/securitypolicy/principalrole/principalRoleManager | 00:50 |
| roym | and principal is request/principal | 00:50 |
| *** vlado has quit IRC | 00:53 | |
| *** vlado has joined #zope3-dev | 00:54 | |
| *** ignas has quit IRC | 00:56 | |
| *** jinty has joined #zope3-dev | 01:19 | |
| *** vlado has quit IRC | 01:26 | |
| *** jinty has quit IRC | 01:43 | |
| *** bskahan has quit IRC | 01:55 | |
| *** bskahan has joined #zope3-dev | 02:06 | |
| *** yota_ has quit IRC | 02:48 | |
| *** MJ has quit IRC | 02:51 | |
| *** projekt01 has quit IRC | 02:52 | |
| *** MJ has joined #zope3-dev | 03:04 | |
| *** d2m has quit IRC | 03:20 | |
| *** stub has joined #zope3-dev | 03:57 | |
| *** fcorrea has joined #zope3-dev | 04:28 | |
| *** fcorrea has quit IRC | 04:44 | |
| *** tiredbones has left #zope3-dev | 05:11 | |
| *** niemeyer has quit IRC | 05:53 | |
| *** roym has quit IRC | 06:15 | |
| *** horizon5 has quit IRC | 08:10 | |
| *** tvon has quit IRC | 08:29 | |
| *** sashav has quit IRC | 08:31 | |
| *** MJ has quit IRC | 08:40 | |
| *** hdima has joined #zope3-dev | 09:16 | |
| *** stub has quit IRC | 09:22 | |
| *** Theuni has joined #zope3-dev | 09:22 | |
| *** j-w has joined #zope3-dev | 09:27 | |
| *** yota has joined #zope3-dev | 09:50 | |
| *** projekt01 has joined #zope3-dev | 09:53 | |
| *** sashav has joined #zope3-dev | 09:58 | |
| *** d2m has joined #zope3-dev | 10:06 | |
| *** sashav has quit IRC | 10:11 | |
| *** sashav has joined #zope3-dev | 10:11 | |
| *** MJ has joined #zope3-dev | 10:21 | |
| VladDrac | emjee | 10:33 |
| *** philiKON has joined #zope3-dev | 10:42 | |
| *** MrTopf has joined #zope3-dev | 10:50 | |
| MrTopf | HI | 10:50 |
| *** mgedmin has joined #zope3-dev | 10:54 | |
| *** tarek has joined #zope3-dev | 11:07 | |
| *** tarek has quit IRC | 11:10 | |
| *** tarek has joined #zope3-dev | 11:11 | |
| *** Theuni has quit IRC | 11:27 | |
| *** ignas has joined #zope3-dev | 11:55 | |
| *** dman13 has quit IRC | 12:07 | |
| *** dman13_ has joined #zope3-dev | 12:07 | |
| *** Theuni has joined #zope3-dev | 12:10 | |
| *** stub has joined #zope3-dev | 12:17 | |
| *** Theuni has quit IRC | 12:35 | |
| *** regebro has joined #zope3-dev | 12:56 | |
| *** J1m has joined #zope3-dev | 12:59 | |
| *** philiKON has quit IRC | 13:10 | |
| *** philiKON has joined #zope3-dev | 13:10 | |
| *** tarek has quit IRC | 13:20 | |
| *** tarek has joined #zope3-dev | 13:21 | |
| *** tarek has quit IRC | 13:24 | |
| *** tarek has joined #zope3-dev | 13:25 | |
| *** alga has joined #zope3-dev | 13:36 | |
| *** tarek has quit IRC | 13:42 | |
| *** tarek has joined #zope3-dev | 13:43 | |
| *** anguenot has joined #zope3-dev | 13:46 | |
| *** bskahan has quit IRC | 13:49 | |
| *** vlado has joined #zope3-dev | 13:53 | |
| *** Theuni has joined #zope3-dev | 13:59 | |
| *** Lewy has joined #zope3-dev | 14:04 | |
| *** MrTopf has quit IRC | 14:08 | |
| Lewy | hi, what product would you recommend as a clear example of a component architecture? I know TextIndexNG, ShoolBell, but maybe there are any simpler ;) | 14:09 |
| alga | zope.event is the simplest ;-) | 14:10 |
| Lewy | I see :) I would like to redesign my Plone Product's skeleton using Five to make it reusable when I will be more z3 guru ;) | 14:13 |
| *** J1m has quit IRC | 14:15 | |
| *** roym has joined #zope3-dev | 14:17 | |
| roym | how would I get the role(s) for a given principal? running principalRoleManager.getRolesForPrincipal(self.request.principal) returns an empty list. | 14:19 |
| regebro | roym: getRolesInContext is usually a good idea. | 14:42 |
| roym | regebro: where is this defined? (searched the entire trunk and couldn't find it). | 14:58 |
| *** mgedmin has quit IRC | 15:04 | |
| *** niemeyer has joined #zope3-dev | 15:25 | |
| *** povbot has joined #zope3-dev | 15:28 | |
| *** __gotcha__ has joined #zope3-dev | 15:28 | |
| projekt01 | roym, use principal id (there's a little mess in the security API method names, but the interface tells you the right attribute) | 15:29 |
| *** yota has quit IRC | 15:30 | |
| *** SteveA has quit IRC | 15:30 | |
| *** genconc has quit IRC | 15:30 | |
| *** ignas has quit IRC | 15:30 | |
| *** sashav has quit IRC | 15:30 | |
| *** __gotcha has quit IRC | 15:30 | |
| *** povbot` has quit IRC | 15:30 | |
| *** VladDrac has quit IRC | 15:30 | |
| *** lucia12345 has quit IRC | 15:30 | |
| *** tav has quit IRC | 15:30 | |
| *** Jim7J1AJH has quit IRC | 15:30 | |
| *** niemeyer has quit IRC | 15:30 | |
| *** roym has quit IRC | 15:30 | |
| *** anguenot has quit IRC | 15:30 | |
| *** alga has quit IRC | 15:30 | |
| *** dman13_ has quit IRC | 15:30 | |
| *** MJ has quit IRC | 15:30 | |
| *** hdima has quit IRC | 15:30 | |
| *** jack-e has quit IRC | 15:30 | |
| *** FarcePest has quit IRC | 15:30 | |
| *** andrew_m has quit IRC | 15:30 | |
| *** __gotcha__ is now known as __gotcha | 15:30 | |
| projekt01 | roym, getRolesForPrincipal(principal_id) | 15:31 |
| *** tav has joined #zope3-dev | 15:31 | |
| *** MrTopf has joined #zope3-dev | 15:31 | |
| *** niemeyer has joined #zope3-dev | 15:31 | |
| *** roym has joined #zope3-dev | 15:31 | |
| *** anguenot has joined #zope3-dev | 15:31 | |
| *** alga has joined #zope3-dev | 15:31 | |
| *** dman13_ has joined #zope3-dev | 15:31 | |
| *** ignas has joined #zope3-dev | 15:31 | |
| *** MJ has joined #zope3-dev | 15:31 | |
| *** sashav has joined #zope3-dev | 15:31 | |
| *** yota has joined #zope3-dev | 15:31 | |
| *** hdima has joined #zope3-dev | 15:31 | |
| *** __gotcha has joined #zope3-dev | 15:31 | |
| *** SteveA has joined #zope3-dev | 15:31 | |
| *** VladDrac has joined #zope3-dev | 15:31 | |
| *** jack-e has joined #zope3-dev | 15:31 | |
| *** Jim7J1AJH has joined #zope3-dev | 15:31 | |
| *** lucia12345 has joined #zope3-dev | 15:31 | |
| *** genconc has joined #zope3-dev | 15:31 | |
| *** FarcePest has joined #zope3-dev | 15:31 | |
| *** andrew_m has joined #zope3-dev | 15:31 | |
| *** irc.freenode.net sets mode: +o tav | 15:31 | |
| *** __gotcha__ has joined #zope3-dev | 15:31 | |
| regebro | roym: Pfah. Wrong channel. I was thinking Zope2. | 15:43 |
| *** __gotcha has quit IRC | 15:45 | |
| *** srichter has joined #zope3-dev | 15:46 | |
| *** ChanServ sets mode: +o srichter | 15:46 | |
| *** benji_york has joined #zope3-dev | 15:48 | |
| *** tiredbones has joined #zope3-dev | 15:53 | |
| *** regebro has quit IRC | 15:56 | |
| *** projekt01 has quit IRC | 15:58 | |
| *** bradb has joined #zope3-dev | 16:06 | |
| *** vlado has quit IRC | 16:16 | |
| *** vlado has joined #zope3-dev | 16:16 | |
| *** projekt01 has joined #zope3-dev | 16:23 | |
| *** efge has joined #zope3-dev | 16:28 | |
| srichter | some good words about Z3: http://griddlenoise.blogspot.com/2005/09/major-zope-3-client-project-finished.html | 16:38 |
| benji_york | yep, I saw that one. It made me think we couldn't write a better PR blurb :) | 16:51 |
| srichter | right :-) | 16:53 |
| srichter | people start coming out of the closet ;-) | 16:53 |
| projekt01 | Hm, this make me think about that I should send a showcase to srichter too ;-) | 16:56 |
| benji_york | srichter, :) | 16:56 |
| srichter | projekt01: yep, or even better put in on your site and send a link to zope3-dev | 16:56 |
| projekt01 | Ok, I'll write something and we can translate it at the sprint. | 16:57 |
| projekt01 | Hm, a xpdl workflow for a i18n implementation isn't that easy if you have to manage each language in a own process. | 17:00 |
| projekt01 | srichter, the use | 17:00 |
| projekt01 | case will contain xpdl workflow and i18n | 17:01 |
| projekt01 | use case/showcase | 17:01 |
| srichter | mmh, localizing a document does not have the same workflow as originally authoring it | 17:03 |
| *** Lewy has quit IRC | 17:03 | |
| projekt01 | srichter, what do you mean with; not the same? | 17:04 |
| *** hdima has quit IRC | 17:06 | |
| srichter | projekt01: authoring and translating are not necessarily the same process | 17:06 |
| srichter | authoring includes the approval of the correctness of the content | 17:06 |
| srichter | this correctness is usually verified by another subject-matter-expert. | 17:07 |
| srichter | or a chief-editor | 17:07 |
| projekt01 | Yes, this means we have to add a activity for translation. That's all I think. | 17:07 |
| srichter | translating is very different (trust me, my wife executes this workflow every day at work) | 17:08 |
| *** vlado has quit IRC | 17:08 | |
| srichter | content authoring is usually done by the company that provides a product | 17:08 |
| srichter | translation is commonly done by a localization provider | 17:08 |
| srichter | the company often just gets a verified translation from the provider | 17:08 |
| srichter | if you also want to model the provider's workflow, you need to work much harder | 17:09 |
| srichter | there is actually an ISO that most companies follow that describes this process | 17:09 |
| projekt01 | Do you know where I can find that? | 17:10 |
| srichter | also note that the roles of the involved parties are quite different | 17:10 |
| srichter | projekt01: I would have to ask my wife. | 17:10 |
| *** J1m has joined #zope3-dev | 17:13 | |
| *** __gotcha__ has quit IRC | 17:22 | |
| *** __gotcha__ has joined #zope3-dev | 17:23 | |
| *** __gotcha__ is now known as __gotcha | 17:23 | |
| *** tarek has quit IRC | 17:25 | |
| benji_york | more Z3 PR: http://faassen.n--tree.net/blog/view/weblog/2005/09/06/0 | 17:29 |
| srichter | benji_york: yeah, and he addresses the Python 2.4 issue | 17:33 |
| srichter | My opinion that Zope 3.2 should require Py 2.4 becomes stronger | 17:34 |
| benji_york | srichter, my opinion cannot become any stronger :) | 17:34 |
| srichter | I am almost at the point where I would say: If the Z2 developers don't get their act together and do a security review for Py 2.4 till November, then Zope 2.9 has to ship with Zope 3.1.x | 17:35 |
| srichter | benji_york: is it strong enough to take it up with Jim :-) | 17:35 |
| benji_york | been there, I wasn't successfull | 17:35 |
| srichter | you see, your opinion is not strong enough :-) | 17:35 |
| benji_york | I wish I knew more about the Z2 community, I don't know how important it is for them to go to 2.4 or how important Zope 3.1 is to them | 17:36 |
| srichter | right | 17:36 |
| benji_york | no, it's just that my desire for continued employment is stronger than my desire for 2.4 :) | 17:36 |
| J1m | It is important that the barrier between Z2 and X3 diminish. | 17:36 |
| J1m | It is important that the barrier between Z2 and Z3 diminish. | 17:37 |
| J1m | Five is a critical project. | 17:37 |
| J1m | We need to support Z3 in Z2 and we can't afford to support 2 versions of Z3. | 17:37 |
| srichter | however, currently we stagnate Z3's development because of it and this is unacceptable I think | 17:37 |
| srichter | unless supporting two Z3 releases is "cheaper" (in some sense of cheap) than stagnating the development | 17:38 |
| projekt01 | J1m, it's also important that we can make some steps forward. | 17:38 |
| * J1m bites his tongue | 17:38 | |
| J1m | Oh come on | 17:38 |
| J1m | we can make steps forward wo 2.4 | 17:39 |
| srichter | he he :-) | 17:39 |
| srichter | benji_york: btw, good point and LOL :-) | 17:39 |
| benji_york | even though I *really* want 2.4, I don't know that we're "stagnating" z3 dev, perhaps just a public commitment of supporting both 2.3 and 2.4 would be enough | 17:39 |
| *** regebro has joined #zope3-dev | 17:39 | |
| srichter | benji_york: but there is none, that's the problem | 17:40 |
| srichter | people hear about testbrowser and zc.formlib and want to use it, especially for commercial projects | 17:40 |
| srichter | so they switch to Python 2.4 | 17:40 |
| benji_york | right | 17:40 |
| J1m | I doubt significant effort is required to make them work w 2,4, | 17:41 |
| benji_york | for testbrowser srichter has already done the significant effort | 17:41 |
| srichter | J1m: what is "them"? or do you mean 2.3? | 17:41 |
| J1m | In fact, I would say that progress is being prevented by a stubborn refusal to make these work w 2.3. | 17:41 |
| J1m | formlib and testbrowser | 17:41 |
| benji_york | we should say that testbrowser and formlib *will* be in 3.2, and the requirement of 2.4 will be considered seperately | 17:42 |
| srichter | I made testbrowser work with 2.3, even so we decided later to switch to 2.4 for ST | 17:42 |
| J1m | absolutely | 17:42 |
| J1m | Inclusion of them is not contingent on 2.4. | 17:42 |
| srichter | benji_york: right | 17:42 |
| benji_york | but I still want 2.4! :| | 17:43 |
| J1m | We *need* Zope 2. | 17:43 |
| J1m | We need to start working on making Z2 and Z3 merge. | 17:43 |
| srichter | I personally just don't like the fact that the lack of Z2 development commitment hijacks Z3's development process | 17:43 |
| benji_york | like, I said, I understand the 2/3 synergy, but from a purely z3 world-view, the move to 2.4 is a no-brainer, but we unfortunately don't have that luxury | 17:44 |
| srichter | so we need to ask: who profits from this synergy and apply pressure on them? | 17:44 |
| J1m | srichter, so become more committed to Z2. | 17:44 |
| regebro | Are there problems with Py2.4 and Zope 2? | 17:45 |
| regebro | And in that case, what kind of pb? | 17:45 |
| srichter | J1m: why? I have been off of Zope 2 for 3-4 years and I only work on pure Z3 projects. | 17:45 |
| srichter | regebro: the problem is that noone knows and it needs to be verified that there are no problems | 17:45 |
| regebro | srichter: OK. How can that be verified (other than running unit tests, which I assume has been done, since it's trivial), | 17:46 |
| srichter | regebro: don't ask me; I have never done a security review | 17:47 |
| SteveA | i imagine the main concern is TTW code in zope 2. | 17:47 |
| benji_york | regebro, it requires a *careful* examination of the changes between 2.3 and 2.4 and how those interact with Z2 security | 17:47 |
| srichter | J1m: is there some sort of guideline for the review? | 17:47 |
| projekt01 | btw, we run our project in production on python 2.4. And our additional 2'200 tests run also well with python 2.4 | 17:47 |
| regebro | Ah. | 17:47 |
| benji_york | does anyone know if the Five folks (who presumably want 2.4 in Z2) could be persuaded to put some effort into this? | 17:48 |
| regebro | Not many people can do that review... | 17:48 |
| srichter | regebro: that's the problem | 17:48 |
| srichter | benji_york: I can only think of Martijn and Andreas being knowledgable and interested enough | 17:49 |
| J1m | Unfortunately, it requires knowledge if the Z2 security framework which %$#@! needs to be relaced. | 17:49 |
| J1m | Unfortunately, it requires knowledge if the Z2 security framework which %$#@! needs to be replaced. | 17:49 |
| srichter | who could do that type of work? | 17:50 |
| J1m | I think people familiar with the Z3 protection scheme (or who want to be) could contribute. | 17:50 |
| srichter | even if this work is done, it would not be the default for 2.9 | 17:50 |
| J1m | Yes, but until we take the first step, we'll be in the same position. | 17:51 |
| SteveA | i think "relaced" is a good description of what needs doing with the z2 security system. | 17:51 |
| J1m | Good point. :) | 17:51 |
| regebro | My suggestion here are strictly off the record: i did not say this: | 17:51 |
| regebro | *ahem* | 17:52 |
| regebro | Start using Python 2.4 if you need to. The Zope2 people will then HAVE to use Python 2.4 and will then HAVE to make the security review. | 17:52 |
| regebro | I wish I could do ot, but I don't know enough about the finer intricate details... | 17:53 |
| benji_york | regebro, as much as *I* would like that, it doesn't seem feasable in the larger picture | 17:53 |
| srichter | regebro: this only works if you do not have synchronized releases, which we do | 17:53 |
| *** faassen has joined #zope3-dev | 17:53 | |
| regebro | ok, if you say so, although I'm not sure I understand why. We then are a bit up shit creek... | 17:54 |
| benji_york | regebro, it's just not nice to say (in the context of one open source project to another), now that you include our code, we dictate what you will do | 17:55 |
| J1m | These are not two different projects. | 17:56 |
| srichter | benji_york: though we are having the inverse case of that right now :-) | 17:56 |
| SteveA | <contentious curmudgeon>i think zope3 is too big. the "default pseudo CMS" should be an entirely separate thing. if that were the case, then the smaller "core" could be distributed as depending on python 2.3, and common to zope3 and zope2. the UI parts can be considered a separate project, depend on python 2.4, and have no zope2 dependency.</contentious curmudgeon> | 17:57 |
| srichter | J1m: they are not two different projects, but they have a different developer base | 17:57 |
| benji_york | I didn't say unrelated, but I definately see them as distinct | 17:57 |
| benji_york | am I misunderstanding the dynamics? | 17:57 |
| srichter | and to make it even more complex | 17:57 |
| J1m | We have a single Zope Community. | 17:58 |
| projekt01 | J1m, do you really belive if we make a stop and get z2 to a state where it is working for z3, that would be the last time we have this problem? | 17:58 |
| J1m | We need to think about what's best for that community. | 17:58 |
| J1m | projekt01, I have no idea what you are talking about. | 17:58 |
| J1m | Zope, for people working on Five: | 17:59 |
| srichter | Z2 devs do not need to know Z3 to do work and Z3 people do not need Z2 to have projects; only sometimes (relatively small right now, but we hope to have an increase) Z2 devs care to know and use Z3 | 17:59 |
| J1m | how would *you* feel if: | 17:59 |
| J1m | - You were limited to Python 2.3 | 17:59 |
| J1m | - Nobody working on cool Z3 tools bothered to support Python 2.3 (bacase They can support newer versionf of Python and don't give a %$^& about your needs | 18:00 |
| J1m | - *You* had to support Zope 3.1 yourself (as you have 3.0). | 18:00 |
| projekt01 | I would do my development with z2 and it's following release or develop on the core migration. But I whould not except that someone else does this job now. | 18:01 |
| benji_york | I think I understand the "whole community" take on things... | 18:01 |
| J1m | Five developers, how would you like to live with the 3 points I made above? | 18:01 |
| SteveA | what in formlib actually depends on python 2.4? | 18:02 |
| regebro | I do feel that Zope2 stopping a move to a more current Python version is a very bad thing. | 18:02 |
| faassen | huh? | 18:02 |
| benji_york | I also think I understand that there may not be the will/desire/resources in the z2 community to do the work and I understand the secondary benefits to Z3 of having a healthy Z2 | 18:02 |
| faassen | regebro: I agree, Zope 2 should work with Python 2.4 | 18:02 |
| J1m | SteveA, nothing of significance. | 18:02 |
| *** jinty has joined #zope3-dev | 18:02 | |
| faassen | I missed the beginning of this discussion. | 18:02 |
| regebro | Well, essentially, moving to Py2.4 means Zope2 eeds a security review. | 18:03 |
| faassen | anyway, I think the best world would be if Zope 2.9 and Zope 3.2 needed Python 2.4 | 18:03 |
| faassen | yeah, I know that. | 18:03 |
| regebro | And few people know how to do that. | 18:03 |
| regebro | And fewer of them want to. | 18:03 |
| faassen | well, what if Jim just tells you and me to do it at the castle. | 18:03 |
| regebro | And none of those have the time. | 18:03 |
| faassen | and then you and I do it? | 18:03 |
| faassen | I mean, Jim tells us *how* to do it. | 18:03 |
| srichter | faassen: the problem is that there is noone that wants/can do that security review in time | 18:03 |
| regebro | I have nowhere near the insight into the security system to be able to do that. | 18:04 |
| faassen | is this because of my blog entry? :) | 18:04 |
| srichter | faassen: I also mentioned earlier that you are one of the few that I could think of that were qualified to do the review | 18:04 |
| faassen | today? | 18:04 |
| faassen | srichter: I don't know whether I'd be qualified, but I'd just need to learn what's going on. | 18:04 |
| faassen | srichter: right now I know as much as you do. | 18:04 |
| J1m | What I'd really like to see is someone to volunteer to port the Zope 3 protection system to Zope 2. | 18:04 |
| regebro | I can give you moral support at the castle entry. And fetch you coffee? :) | 18:04 |
| srichter | faassen: your blog entry made my opinion stronger so I brought it up one more time :-) | 18:05 |
| J1m | I'm willing to do the security review but I'm not willing to do it forever. | 18:05 |
| faassen | srichter: good. :) | 18:05 |
| faassen | J1m: yeah, and I'm willing to help with that port, but I don't want the Zope 2.9 release to depend on it. | 18:05 |
| J1m | Zope 2's protection scheme is a big pile of technical debt. | 18:05 |
| J1m | faassen, agrees | 18:05 |
| J1m | faassen, agreed | 18:05 |
| faassen | I know the Zope 3 security system better than the Zope 2 system already. :) | 18:05 |
| J1m | The security reviews are some of the interest on that debt. | 18:06 |
| SteveA | J1m: there's a change i want to make to the zope3 security system that i discussed with tres at europython that might make it easier to apply it to zope2. i want to talk with you about it sometime. | 18:06 |
| *** dman13_ is now known as dman13 | 18:06 | |
| faassen | anyway, what if we: | 18:06 |
| faassen | ..hm..do th following: | 18:06 |
| J1m | SteveA, k | 18:06 |
| *** niemeyer is now known as nie_lunch | 18:06 | |
| faassen | * I commit some resources to help Jim with porting the Z3 security to Z2. I hope other Five people will jump in. | 18:06 |
| srichter | J1m: faassen: I would be willing to come to another sprint to get the Z3 security system moved over to Z2 | 18:06 |
| faassen | * Jim does the security review for Zope 2.9 | 18:06 |
| * J1m jumps for joy! | 18:06 | |
| faassen | * we release 2.9 and Zope 3.2 with Zope 2.9, but for Zope 2.10 we plan the ported security system. | 18:07 |
| * benji_york is startled to see J1m *actually* jump for joy | 18:07 | |
| * faassen laughs. | 18:07 | |
| srichter | LOL | 18:07 |
| faassen | I mean, I do have some minor amount of experience in porting stuff to Zope 2 from Zope 3. :) | 18:07 |
| J1m | faassen, sound slike a great plan to me, | 18:08 |
| J1m | faassen, sounds like a great plan to me, | 18:08 |
| faassen | cool! we can work out the details at the castle. | 18:08 |
| regebro | Excellent. | 18:08 |
| J1m | Yay! | 18:09 |
| regebro | I'll listen in, and if I'll understand the plan for the porting of the security system, I'll help. | 18:09 |
| faassen | basically what I want to do at the castle is start porting over Five to 3.1 (well, 3.2, but that isn't there yet), and now we can also discuss the port of the security system. | 18:09 |
| regebro | (Currently I have no picture of how to do that, but if I get a picture...) | 18:09 |
| faassen | regebro: I have a somewhat comprehensive picture of Zope 3's system, though I'm sure I miss a lot of details. | 18:10 |
| srichter | Does this mean we can approve: http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/MigrationToPython24 | 18:10 |
| srichter | when is the Castle sprint? | 18:10 |
| faassen | srichter: also sneak in an approval of the lxml inclusion! *wink nudge* | 18:11 |
| srichter | I am +1 on that already | 18:11 |
| *** sashav has quit IRC | 18:11 | |
| projekt01 | J1m, fassen, if you have a free place at the castle sprint I'm willing to help too. | 18:11 |
| faassen | srichter: 22-24, if I recall correctly, this month. | 18:11 |
| srichter | faassen: only J1m has to say +1 on that | 18:11 |
| projekt01 | fassen, 1+ for the lxml | 18:11 |
| faassen | projekt01: hm, you should get Jim to tell the castle sprint people to get you over. :) | 18:12 |
| srichter | faassen: does lxml require Py 2.4? | 18:12 |
| faassen | srichter: nope, it works with 2.3. | 18:12 |
| faassen | srichter: I just thought I'd just sneak it in. :) | 18:12 |
| srichter | faassen: what was the think with PyRex? | 18:12 |
| faassen | srichter: Pyrex has some bug which makes it not work with gcc 4.0 unless you apply patches, is that what you mean? | 18:13 |
| faassen | srichter: but that's separate from the 2.3 issue. | 18:13 |
| faassen | srichter: and it's possible to distribute a version of lxml that doesn't depend on Pyrex, just has the pregenerated c sources. just nobody has done that yet. | 18:13 |
| srichter | faassen: no, I mean more the requirement of PyRex | 18:13 |
| J1m | faassen, what is your current thinking on whether lxml should be included vs being required (a prerequisite)? | 18:13 |
| faassen | srichter: but Julien volunteered for that I think. | 18:13 |
| faassen | J1m: what does 'included' mean? as a package that is there in the distribution but nobody else can use it? | 18:14 |
| J1m | +1 wrt not requiring pyrex | 18:14 |
| srichter | faassen: ok, I would really prefer to make the PyRex requirement optional | 18:14 |
| faassen | srichter: yeah, everybody does. I'll just prod Julien. :) | 18:14 |
| J1m | faassen, by "include" I mean, "Zope distro includes lxml". | 18:15 |
| faassen | J1m: ah, you mean you can require it as a dependency versus include it and then you don't need to require anyone to install anything.. | 18:15 |
| srichter | faassen: no, I think more the distinction between making it a vendor import versus a Zope 3 repos maintained package | 18:15 |
| J1m | Note that including or requiring lxml in Z3 aldo means the same for Z2, | 18:15 |
| faassen | J1m: inclusion would be better for the out of the box experience. | 18:15 |
| J1m | faassen, I agree. | 18:16 |
| faassen | J1m: but it also means work to ship libxml2 and so on along, which is a big bite. perhaps it's more sensible to do this in Zope 3.3. | 18:16 |
| srichter | I think that lxml should be at least part of the Zope 3 build and we should be able to rely on it in Zope 3 | 18:16 |
| J1m | BTW, I recently tried to install lxml with Fedora Core 2 and ran into difficulties because my libxml library was old. | 18:16 |
| faassen | J1m: yeah, there are some dependency issues. it tends to install pretty well on recent fedora's, though the most recent again uses gcc 4.0 which requires a pyrex patch. dependencies are a pain. :) | 18:17 |
| J1m | sorry, Fedora Core 1 | 18:17 |
| tiredbones | bookmark | 18:17 |
| SteveA | J1m: the ubuntu developers use zope3, so it ought to work pretty well on ubuntu ;-) | 18:17 |
| J1m | :) | 18:17 |
| * J1m needs to try ubuntu | 18:18 | |
| srichter | J1m: OT: are you working on the publisher branch right now? | 18:20 |
| J1m | srichter, no | 18:22 |
| srichter | ok | 18:22 |
| *** j-w has quit IRC | 18:31 | |
| *** MrTopf has quit IRC | 18:32 | |
| *** MJ has quit IRC | 18:43 | |
| efge | J1m, faassen: I can contribute some time to porting the Z3 security to Z2 too | 18:44 |
| J1m | Way cool | 18:45 |
| *** fdrake has joined #zope3-dev | 18:46 | |
| faassen | efge: great. :) | 18:50 |
| *** stub has quit IRC | 18:59 | |
| *** nie_lunch is now known as niemeyer | 19:05 | |
| fdrake | srichter, did you see what I had to do for ZEO.mkzeoinst? | 19:37 |
| *** MJ has joined #zope3-dev | 19:38 | |
| *** jinty has quit IRC | 19:58 | |
| *** mgedmin has joined #zope3-dev | 20:01 | |
| *** deo has joined #zope3-dev | 20:02 | |
| *** GaryPoster has joined #zope3-dev | 20:06 | |
| GaryPoster | yo srichter. :-) I've got an APIdoc bug: you want it in the collector or do you prefer some other mechanism? | 20:07 |
| *** tvon has joined #zope3-dev | 20:12 | |
| *** bradb is now known as bradb-lunch | 20:15 | |
| *** tvon has quit IRC | 20:17 | |
| *** tvon has joined #zope3-dev | 20:17 | |
| fdrake | GaryPoster, he looks in the collector eventually :-) | 20:19 |
| GaryPoster | fdrake: ok cool. So we just need the collector to work now. ;-) :-( | 20:21 |
| fdrake | yeah, minor details, huh? | 20:21 |
| *** tvon has quit IRC | 20:22 | |
| SteveA | GaryPoster: if you want to switch to using launchpad to track issues, i can get someone to write an importer of existing issues from the collector | 20:23 |
| *** tvon|x31 has joined #zope3-dev | 20:23 | |
| GaryPoster | SteveA: That's a reasonable and gracious idea. I just highlighted that to Jim: it's up to mgmt. The foundation plans are another part of the story, though. | 20:25 |
| benji_york | SteveA, I've been personally interested in Launchpad, any idea when a public release will happen (or did I miss it?) | 20:28 |
| SteveA | what does "public release" mean? | 20:29 |
| benji_york | is the code available? | 20:30 |
| SteveA | no, it's a propriatory application. some elements of it are being opened, but not the whole thing right now. | 20:30 |
| benji_york | ahh, ok, I must have mis-understood something | 20:30 |
| SteveA | management have stated publicly an intention to open it up at some point under an open source licence. | 20:31 |
| *** regebro has quit IRC | 20:32 | |
| benji_york | ok, that's probably what I was thinking about | 20:32 |
| benji_york | I'm personally interested, so +1 to opening it :) | 20:32 |
| *** bradb-lunch is now known as bradb | 20:33 | |
| SteveA | the webapp platform part can be open sourced, but it's a matter of finding the time to split it out from the rest of the domain-specific stuff and package it as a separate project. | 20:33 |
| *** faassen has quit IRC | 20:44 | |
| *** philiKON has quit IRC | 20:48 | |
| *** philiKON has joined #zope3-dev | 20:49 | |
| *** ignas has quit IRC | 20:55 | |
| *** tvon has joined #zope3-dev | 20:59 | |
| *** tarek_ has joined #zope3-dev | 21:11 | |
| *** sashav has joined #zope3-dev | 21:26 | |
| *** projekt01 has quit IRC | 21:40 | |
| *** anguenot has quit IRC | 21:46 | |
| *** efge has quit IRC | 21:59 | |
| *** vlado has joined #zope3-dev | 22:02 | |
| srichter | fdrake: no, I don't get ZODB checkins, so I really want to become more involved in it. | 22:15 |
| fdrake | ah, ok | 22:16 |
| fdrake | the email on the zope3-dev and zope3-checkins should clarify | 22:16 |
| fdrake | if not, let me know and I'll be glad to explain what we did | 22:16 |
| fdrake | whether you wanna cut a new RC is up to you | 22:16 |
| srichter | I think we need it | 22:17 |
| srichter | so I have to send out a message to zope3-dev | 22:17 |
| srichter | I think there were some other bugs discovered in the RC | 22:17 |
| fdrake | ok, then you know how to do that :-) | 22:17 |
| fdrake | ah, ok | 22:18 |
| fdrake | some docs for starting Z3 would be really good as well | 22:18 |
| fdrake | I've got some email to write about the pytz changes, then I can look at the docs issue. | 22:18 |
| srichter | thanks | 22:18 |
| fdrake | (likely not for long, though) | 22:18 |
| srichter | that's ok | 22:18 |
| benji_york | fdrake, are you fixing the pytz-induced test failure? | 22:19 |
| fdrake | benji_york, talked to Gary about it, and we're going to push it back to Stuart | 22:23 |
| benji_york | ahh, ok | 22:23 |
| fdrake | there are some open questions about what the right thing to do really is | 22:23 |
| benji_york | fdrake, buildbot.zope.org is already being crawled by spiders, and clue on whether buildbot has an easy way to add a robots.txt? | 22:26 |
| * fdrake chatting w/ Gary on the side channel again... | 22:26 | |
| *** d2m has quit IRC | 22:26 | |
| fdrake | benji_york, it shouldn't be too hard | 22:26 |
| *** d2m has joined #zope3-dev | 22:27 | |
| benji_york | srichter, does ST use a robots.txt for their buildbot? | 22:28 |
| srichter | benji_york: you have to ask someone from POV | 22:29 |
| srichter | I am not involved in this part | 22:29 |
| benji_york | anyone matching that description here? | 22:29 |
| srichter | alga, mgedmin | 22:29 |
| mgedmin | no, we don't | 22:32 |
| mgedmin | we use robots.txt to tell bots to ignore our subversion repository | 22:32 |
| mgedmin | 'cause that used to cause berkeley db related problems | 22:32 |
| benji_york | I just noticed Ask Jeves has already spidered buildbot.zope.org even though it's only been up a few hours | 22:32 |
| * mgedmin looks | 22:33 | |
| benji_york | I'll just wait until it becomes a problem before digging into it | 22:33 |
| mgedmin | it could use some nicer css | 22:33 |
| benji_york | yeah, I haven't worried about that much yet, I do like ST's CSS though | 22:33 |
| mgedmin | actually it's fluendo's | 22:34 |
| benji_york | yeah, I had noticed from the comment | 22:34 |
| mgedmin | simplest way to add robots.txt if buildbot is serving / directly would be an Apache rewrite rule, I think | 22:36 |
| mgedmin | although buildbot uses twisted and serves the CSS from the filesystem -- so it should be trivial to serve /robots.txt as well | 22:36 |
| benji_york | yep, I was thinking the latter | 22:36 |
| *** srichter has quit IRC | 22:37 | |
| fdrake | it should probably serve everything not recognized based on the filesystem | 22:42 |
| fdrake | but an apache re-write would serve just as well | 22:42 |
| benji_york | fdrake, hmm, I'll test that hypothesis | 22:42 |
| fdrake | i said *should*; i don't think it does | 22:42 |
| benji_york | nope, it doesn | 22:44 |
| benji_york | 't | 22:44 |
| fdrake | in buildbot.status.html, StatusResource special cases various names for special handling, and barfs on the rest | 22:44 |
| fdrake | it shouldn't be too hard to modify, though | 22:45 |
| fdrake | at least for simple files, which is all we care about | 22:45 |
| benji_york | yep, I see where to change it, but am not going to do it right now, if we have a problem we'll fix it and contribute it back | 22:46 |
| fdrake | sounds good | 22:46 |
| fdrake | we definately want to get a robots.txt in there quickly, though | 22:47 |
| *** alga has quit IRC | 22:47 | |
| benji_york | fdrake, oh... we do? | 22:47 |
| fdrake | don't we? if it gets spidered a lot, that means that contributors loose, since that's the svn machine as well | 22:50 |
| benji_york | I didn't think it would be too bad, but if you think so, I can make the changes, it should't be too hard | 22:52 |
| fdrake | do we have a candidate robots.txt yet? | 22:52 |
| benji_york | Interestingly, the only spider to know about it (Ask Jeeves) didn't bother to request robots.txt :( | 22:53 |
| mgedmin | User-agent: * | 22:53 |
| mgedmin | Disallow: / | 22:53 |
| fdrake | ah, very interesting | 22:53 |
| mgedmin | cheers! | 22:53 |
| *** mgedmin has quit IRC | 22:53 | |
| fdrake | seems like a reasonable robots.txt to me! | 22:53 |
| benji_york | as long as we add an allow for Opera so I can use the auto reload option :) | 22:54 |
| fdrake | does that consult robots.txt? it's hard to call that a robot in the same way | 22:54 |
| fdrake | though I guess it kinda is | 22:55 |
| benji_york | it does, the Opera people are nice like that | 22:55 |
| fdrake | (a robot; it's still not a spider) | 22:55 |
| *** tarek_ has quit IRC | 23:01 | |
| *** gintas has joined #zope3-dev | 23:18 | |
| *** niemeyer has quit IRC | 23:25 | |
| *** vlado has quit IRC | 23:26 | |
| *** srichter has joined #zope3-dev | 23:27 | |
| *** ChanServ sets mode: +o srichter | 23:27 | |
| *** gintas has quit IRC | 23:28 | |
| *** vinsci has quit IRC | 23:33 | |
| *** vinsci|2 has joined #zope3-dev | 23:33 | |
| *** vinsci|2 is now known as vinsci | 23:33 | |
| *** tiredbones has left #zope3-dev | 23:44 | |
| *** strichter has joined #zope3-dev | 23:56 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!