| *** aaronv has quit IRC | 00:07 | |
| *** TresEquis has joined #zope | 00:20 | |
| *** sunew has quit IRC | 00:22 | |
| *** maiky has quit IRC | 00:29 | |
| *** slackrunner has joined #zope | 00:30 | |
| *** olaf has quit IRC | 00:31 | |
| *** slackrunner has left #zope | 00:31 | |
| *** igbun has joined #zope | 00:32 | |
| *** regebro has joined #zope | 00:41 | |
| *** grahal_ has quit IRC | 00:42 | |
| *** regebro has quit IRC | 00:43 | |
| *** regebro has joined #zope | 00:43 | |
| *** webmaven has quit IRC | 00:45 | |
| *** Hypergraphe has quit IRC | 00:58 | |
| *** benji has quit IRC | 01:00 | |
| *** aaronv has joined #zope | 01:09 | |
| *** sidnei has quit IRC | 01:18 | |
| *** smita has quit IRC | 01:26 | |
| *** allisterb has joined #zope | 01:42 | |
| *** igbun has quit IRC | 01:42 | |
| *** hever has joined #zope | 02:03 | |
| *** ccomb has quit IRC | 02:09 | |
| *** MrTango has quit IRC | 02:17 | |
| *** hever has quit IRC | 02:21 | |
| *** dunny has joined #zope | 02:23 | |
| *** hever has joined #zope | 02:24 | |
| *** TresEquis has quit IRC | 02:25 | |
| *** aaronv has quit IRC | 02:31 | |
| *** hever has quit IRC | 02:51 | |
| *** hever has joined #zope | 03:05 | |
| *** dayne has quit IRC | 03:07 | |
| *** igbun has joined #zope | 03:11 | |
| *** igbun has quit IRC | 03:11 | |
| *** tiwula has quit IRC | 03:15 | |
| *** r0ver has left #zope | 03:19 | |
| *** MatthewWilkes has joined #zope | 03:24 | |
| *** hever has quit IRC | 03:30 | |
| *** tarek has quit IRC | 03:33 | |
| *** astoon has joined #zope | 03:54 | |
| *** Guest6405 has quit IRC | 04:05 | |
| *** pedahzur has joined #zope | 04:09 | |
| pedahzur | Zope 2.x trying to reset a password. ZOPE_HOME, according to the zopectl we use to start/stop is /opt/zope/custom_cms-dist/opt/Zope2. However, creating an 'access' file in that directory and trying to log in with that user pass does nothing (no error on the login form, just goes back to a blank login form). Ideas? | 04:10 |
|---|---|---|
| mcdonc | pedahzur: try doing bin/zopectl adduser admin2 admin2 | 04:12 |
| mcdonc | then you should be able to log in as admin2 and reset admin's password | 04:12 |
| pedahzur | mcdonc: I'll try that. This may point to part of our problem. zopectl is at /opt/zope/custom_cms-dist/bin/zopectl but that zopectl file says ZOPE_HOME is/opt/zope/custom_cms-dist/opt/Zope2 | 04:13 |
| mcdonc | that doesnt sound quite right | 04:14 |
| *** huajie has joined #zope | 04:14 | |
| pedahzur | mcdonc: the adduser call gives me: NotImplementedError: There are no plugins that can create users and assign roles to them. | 04:14 |
| mcdonc | ew | 04:15 |
| mcdonc | i'm out of my league | 04:15 |
| pedahzur | mcdonc: Well, thanks for trying. :) | 04:15 |
| mcdonc | what i think is happening is that the root user folder is a PAS user folder | 04:16 |
| MatthewWilkes | pedahzur: Have you been trying to change the ACL users at the root of the site? | 04:16 |
| mcdonc | which isnt a bad thing | 04:16 |
| mcdonc | its just misconfigured, effectively locking you out | 04:16 |
| pedahzur | MatthewWilkes: No. This is a site that hasn't been touched for a long time, and we've lost the admin password. :) | 04:16 |
| mcdonc | i smell plone | 04:17 |
| MatthewWilkes | pedahzur: How much experience do you have with debugging Zope stuff? I'd drop into zopectl debug and inspect the root ACL to see what plugins it has | 04:17 |
| MatthewWilkes | mcdonc: Plone sets up PAS correctly; ) | 04:18 |
| mcdonc | suuuure it does | 04:18 |
| mcdonc | by replacing the root user folder for no apparent reason | 04:18 |
| pedahzur | MatthewWilkes: You've just lost me. I have zero Zope experience. This is an old legacy Zope/Plone site...I think it was set up by Zope corp a long time ago. | 04:18 |
| mcdonc | access file doesnt work eh | 04:20 |
| mcdonc | damn | 04:20 |
| MatthewWilkes | I've never seen an access file work, personally | 04:20 |
| mcdonc | let's look at the code | 04:20 |
| mcdonc | crap, let's first get a zope checkout on our new computer | 04:21 |
| *** r0ver has joined #zope | 04:21 | |
| pedahzur | MatthewWilkes: OK, I'm in zopectl debug...what do I do now? :) | 04:23 |
| mcdonc | pedahzur: try this | 04:24 |
| mcdonc | import App.config | 04:25 |
| mcdonc | cfg = App.config.getConfiguration() | 04:25 |
| mcdonc | print cfg.instancehome | 04:25 |
| mcdonc | what prints? | 04:25 |
| pedahzur | mcdonc: /opt/zope/custom_cms-dist/var/zope | 04:26 |
| mcdonc | put an "access" file there | 04:26 |
| pedahzur | Wow...it's not either of the two previous path values we've found. :) | 04:26 |
| mcdonc | its filepath bingo | 04:26 |
| mcdonc | you'll need to restart zope for it to notice it | 04:27 |
| pedahzur | mcdonc: Hey, wadaya know! | 04:29 |
| pedahzur | I'm in. | 04:29 |
| mcdonc | alright! | 04:29 |
| *** sidnei has joined #zope | 04:31 | |
| *** baijum has joined #zope | 04:32 | |
| pedahzur | mcdonc, MatthewWilkes: Thank you so much! | 04:33 |
| mcdonc | pedahzur: are you related to hadar of zope corp? | 04:33 |
| mcdonc | (or are you he even? ;-) ) | 04:34 |
| pedahzur | Hmm...no. Why do you ask? | 04:34 |
| mcdonc | not a real common name.. hadar pedazhur is the main vc of zope corp | 04:34 |
| mcdonc | darn sorry for the misspelling | 04:35 |
| pedahzur | Ah, interesting. Pedahzur is my IRC handle. Joshua Kugler is my real name. :) | 04:36 |
| mcdonc | heh ok | 04:36 |
| pedahzur | Gotta run for now...thanks again! | 04:38 |
| *** pedahzur has quit IRC | 04:39 | |
| *** touff has quit IRC | 04:44 | |
| *** evilbungle has quit IRC | 04:55 | |
| *** astoon has quit IRC | 05:02 | |
| *** davisagli has quit IRC | 05:06 | |
| *** baijum has quit IRC | 05:39 | |
| *** baijum has joined #zope | 05:39 | |
| *** baijum has quit IRC | 05:43 | |
| *** MatthewWilkes has quit IRC | 05:44 | |
| *** davisagli_ has joined #zope | 06:26 | |
| *** huajie has quit IRC | 06:30 | |
| *** huajie has joined #zope | 06:45 | |
| *** davisagli_ has quit IRC | 06:46 | |
| *** redir has joined #zope | 06:51 | |
| *** zz_davisagli has joined #zope | 07:02 | |
| *** skt_ has joined #zope | 07:03 | |
| *** zz_davisagli is now known as davisagli | 07:04 | |
| *** davisagli has quit IRC | 07:22 | |
| *** zz_davisagli has joined #zope | 07:22 | |
| *** zz_davisagli is now known as davisagli | 07:23 | |
| *** davisagli has quit IRC | 07:35 | |
| *** davisagli has joined #zope | 07:35 | |
| *** davisagli is now known as zz_davisagli | 07:37 | |
| *** zz_davisagli is now known as davisagli | 07:39 | |
| *** huajie has quit IRC | 07:43 | |
| *** davisagli has quit IRC | 07:45 | |
| *** davisagli has joined #zope | 07:47 | |
| *** sm has quit IRC | 07:47 | |
| *** sm has joined #zope | 07:48 | |
| *** sm has quit IRC | 07:48 | |
| *** davisagli is now known as davisagli|away | 07:50 | |
| *** sm has joined #zope | 07:55 | |
| *** davisagli|away has quit IRC | 08:01 | |
| *** davisagli has joined #zope | 08:03 | |
| *** redir has quit IRC | 08:08 | |
| *** davisagli is now known as davisagli|away | 08:10 | |
| *** davisagli|away is now known as davisagli | 08:10 | |
| *** davisagli has quit IRC | 08:18 | |
| *** baijum has joined #zope | 08:35 | |
| *** rTheJeste has quit IRC | 08:42 | |
| *** __mac__ has joined #zope | 08:44 | |
| *** davisagli has joined #zope | 08:48 | |
| *** davisagli has quit IRC | 08:48 | |
| *** davisagli has joined #zope | 08:48 | |
| *** davisagli is now known as davisagli|away | 08:48 | |
| *** davisagli|away is now known as davisagli | 08:50 | |
| *** bigkevmcd has quit IRC | 08:51 | |
| *** slackrunner has joined #zope | 08:56 | |
| *** phimic has joined #zope | 08:59 | |
| *** Wu has quit IRC | 09:00 | |
| *** bigkevmcd has joined #zope | 09:00 | |
| *** slackrunner has quit IRC | 09:00 | |
| *** vasco has joined #zope | 09:08 | |
| *** Wu has joined #zope | 09:09 | |
| *** davisagli has quit IRC | 09:12 | |
| *** rTheJeste has joined #zope | 09:12 | |
| *** MatthewWilkes has joined #zope | 09:16 | |
| *** JaRoel|4D has quit IRC | 09:22 | |
| *** maiky has joined #zope | 09:27 | |
| *** davisagli has joined #zope | 09:37 | |
| *** Kabz|4D has joined #zope | 09:37 | |
| *** mr_jolly has joined #zope | 09:38 | |
| *** digitalmortician has joined #zope | 09:46 | |
| *** regebro has quit IRC | 09:53 | |
| *** regebro has joined #zope | 09:54 | |
| *** MatthewWilkes has quit IRC | 09:56 | |
| *** maiky has quit IRC | 09:57 | |
| *** vasco has quit IRC | 09:59 | |
| *** sunew has joined #zope | 10:07 | |
| *** neo|4D has joined #zope | 10:07 | |
| *** JaRoel|4D has joined #zope | 10:12 | |
| *** wosc has joined #zope | 10:13 | |
| *** MrTango has joined #zope | 10:20 | |
| *** MatthewWilkes has joined #zope | 10:23 | |
| *** MatthewWilkes is now known as mwilkes|govote | 10:24 | |
| *** goschtl has joined #zope | 10:26 | |
| *** davisagli is now known as davisagli|away | 10:26 | |
| *** planetzopebot has quit IRC | 10:33 | |
| *** planetzopebot has joined #zope | 10:34 | |
| *** sim_sim has joined #zope | 10:36 | |
| *** rTheJeste is now known as TheJester | 10:46 | |
| *** timte has joined #zope | 10:48 | |
| *** vigith has joined #zope | 10:48 | |
| *** tarek has joined #zope | 10:57 | |
| *** matleh has joined #zope | 11:15 | |
| *** ramonski has joined #zope | 11:20 | |
| *** tarek has quit IRC | 11:23 | |
| *** sunew has quit IRC | 11:26 | |
| *** seppo14 has joined #zope | 11:38 | |
| *** seppo14 has left #zope | 11:39 | |
| *** mwilkes|govote has quit IRC | 11:42 | |
| *** igbun has joined #zope | 11:45 | |
| *** tarek has joined #zope | 11:47 | |
| *** smita has joined #zope | 11:52 | |
| *** eperez has joined #zope | 12:01 | |
| *** fredvd has joined #zope | 12:01 | |
| *** redir has joined #zope | 12:11 | |
| *** evilbungle has joined #zope | 12:31 | |
| *** digitalmortician has quit IRC | 12:33 | |
| *** MJ has joined #zope | 12:41 | |
| *** emrojo has joined #zope | 12:42 | |
| *** teix has joined #zope | 12:53 | |
| *** digitalmortician has joined #zope | 13:02 | |
| *** agroszer has joined #zope | 13:06 | |
| *** regebro has quit IRC | 13:12 | |
| *** j-w has joined #zope | 13:12 | |
| *** regebro has joined #zope | 13:12 | |
| *** regebro has left #zope | 13:12 | |
| *** regebro has joined #zope | 13:13 | |
| *** regebro has left #zope | 13:17 | |
| *** regebro has joined #zope | 13:18 | |
| *** igbun has quit IRC | 13:18 | |
| *** MJ has quit IRC | 13:27 | |
| *** maiky has joined #zope | 13:38 | |
| *** dvschramm has joined #zope | 13:47 | |
| *** vigith has quit IRC | 14:03 | |
| *** aaronv has joined #zope | 14:10 | |
| *** hever has joined #zope | 14:12 | |
| *** dayne has joined #zope | 14:18 | |
| *** touff has joined #zope | 14:25 | |
| *** menesis has quit IRC | 14:31 | |
| *** thetet has joined #zope | 14:38 | |
| *** maiky has quit IRC | 14:39 | |
| *** MJ has joined #zope | 14:45 | |
| *** tisto has joined #zope | 14:49 | |
| *** ramonski_ has joined #zope | 14:59 | |
| *** smita has quit IRC | 14:59 | |
| *** ramonski_ has left #zope | 15:01 | |
| *** ramonski has quit IRC | 15:03 | |
| *** maiky has joined #zope | 15:03 | |
| *** hever has quit IRC | 15:07 | |
| *** hever has joined #zope | 15:11 | |
| *** benji has joined #zope | 15:14 | |
| *** hever has quit IRC | 15:15 | |
| *** hever has joined #zope | 15:16 | |
| *** hever has quit IRC | 15:17 | |
| *** maiky has quit IRC | 15:22 | |
| *** smita has joined #zope | 15:23 | |
| *** menesis has joined #zope | 15:24 | |
| *** agroszer has quit IRC | 15:37 | |
| *** j-w has quit IRC | 15:38 | |
| *** huajie has joined #zope | 15:44 | |
| *** evilbungle has quit IRC | 16:06 | |
| *** tiwula has joined #zope | 16:09 | |
| *** skt_ has quit IRC | 16:12 | |
| *** dayne has quit IRC | 16:28 | |
| *** nebo has joined #zope | 16:34 | |
| *** sunew has joined #zope | 16:48 | |
| *** dayne has joined #zope | 16:50 | |
| *** povbot has joined #zope | 16:56 | |
| *** povbot` has quit IRC | 16:57 | |
| *** fredvd has quit IRC | 16:58 | |
| *** baijum has quit IRC | 17:00 | |
| *** regebro has quit IRC | 17:08 | |
| *** regebro has joined #zope | 17:08 | |
| *** dunny has quit IRC | 17:10 | |
| *** tiwula has quit IRC | 17:17 | |
| *** mgedmin has joined #zope | 17:24 | |
| *** webmaven has joined #zope | 17:24 | |
| *** mr_jolly has left #zope | 17:26 | |
| *** jim_SFU has joined #zope | 17:36 | |
| *** allisterb has quit IRC | 17:37 | |
| *** timte has quit IRC | 17:42 | |
| *** allisterb has joined #zope | 17:51 | |
| *** phimic has quit IRC | 17:53 | |
| *** tisto has quit IRC | 17:53 | |
| *** r0ver has left #zope | 17:59 | |
| *** sim_sim has quit IRC | 18:06 | |
| *** fredvd has joined #zope | 18:17 | |
| *** fredvd is now known as fredvd|dinner | 18:20 | |
| *** TKtiddle has joined #zope | 18:30 | |
| *** MJ has quit IRC | 18:32 | |
| *** mgedmin has quit IRC | 18:41 | |
| *** redir has quit IRC | 18:41 | |
| *** goschtl has quit IRC | 18:45 | |
| *** digitalmortician has quit IRC | 18:48 | |
| *** neo|4D has quit IRC | 18:49 | |
| *** Kabz|4D has quit IRC | 18:51 | |
| *** daMaestro has joined #zope | 18:58 | |
| *** cbcunc has joined #zope | 19:00 | |
| *** axelix has joined #zope | 19:03 | |
| *** sunew has quit IRC | 19:10 | |
| *** agroszer has joined #zope | 19:13 | |
| *** Kabz|4D has joined #zope | 19:14 | |
| *** astoon has joined #zope | 19:18 | |
| *** davisagli|away is now known as davisagli | 19:24 | |
| *** davisagli is now known as davisagli|away | 19:27 | |
| *** fredvd|dinner has quit IRC | 19:29 | |
| *** r0ver has joined #zope | 19:30 | |
| *** huajie has quit IRC | 19:31 | |
| *** redir has joined #zope | 19:35 | |
| *** redir has quit IRC | 19:36 | |
| *** redir has joined #zope | 19:36 | |
| *** JaRoel|4D has quit IRC | 19:38 | |
| *** emrojo has quit IRC | 19:40 | |
| *** TKtiddle has quit IRC | 19:41 | |
| *** davisagli|away is now known as davisagli | 19:49 | |
| *** sunew has joined #zope | 19:58 | |
| *** tiwula has joined #zope | 20:00 | |
| *** Hypergraphe has joined #zope | 20:01 | |
| *** menesis has quit IRC | 20:02 | |
| *** prinzdezibel has joined #zope | 20:09 | |
| *** eperez has quit IRC | 20:09 | |
| prinzdezibel | What does a zcml like this imply <zodb><blobstorage> | 20:10 |
| prinzdezibel | blobdir mydir | 20:10 |
| prinzdezibel | <filestorage> | 20:10 |
| prinzdezibel | path a_path | 20:10 |
| prinzdezibel | </filestorage></blobstorage> ? | 20:10 |
| prinzdezibel | why is filestorage nested in blobstorage? | 20:11 |
| prinzdezibel | and what does this imply? | 20:11 |
| *** thetet has quit IRC | 20:14 | |
| benji | prinzdezibel: the blobstorage is wrapping the filestorage, adding blob functionality to it | 20:16 |
| benji | for modern versions of filestorage, I don't think that's needed any more | 20:16 |
| *** fruitwerks has quit IRC | 20:16 | |
| prinzdezibel | when is the blob functionality used, benji ? | 20:17 |
| benji | (and that's not ZCML) | 20:17 |
| benji | to store blobs :) | 20:17 |
| prinzdezibel | regarding ZCML, of course you're right. | 20:17 |
| benji | some apps/components store large data in blobs instead of in the underlying storage (like filestorage) | 20:17 |
| benji | common things to put in blobs are media and documents | 20:18 |
| prinzdezibel | benji: so the application needs to request the blob storage explicitely? | 20:18 |
| prinzdezibel | Or does ZODB decide: This content is file storage and this is media (blob) | 20:18 |
| benji | there are blob-specific operations the application can use | 20:18 |
| benji | the app decides | 20:19 |
| prinzdezibel | benji: Thank you! | 20:19 |
| benji | np | 20:19 |
| *** sarw has joined #zope | 20:20 | |
| *** RaFromBRC has joined #zope | 20:20 | |
| sarw | channel# how to download the latest zope documentation source from zope.org ? | 20:22 |
| benji | sarw: maybe here http://svn.zope.org/zope2docs/trunk/ | 20:28 |
| *** ccomb has joined #zope | 20:29 | |
| *** astoon has quit IRC | 20:30 | |
| sarw | benji svn http://svn.zope.org/zope2docs/trunk/ ? I don't have svn installed what I have to install can you suggest ? | 20:31 |
| betabug | why do you want the sources to the docs anyway? | 20:31 |
| benji | if you just want to browse it, you can use your web browser and visit http://svn.zope.org/zope2docs/trunk/ | 20:31 |
| sarw | benji, I want to create pdf version of 2.12 documentation I installed sphinx and latex | 20:32 |
| betabug | unless you have something to *add*, you can find all you want at docs.zope.org | 20:32 |
| betabug | install svn too then :-) | 20:33 |
| *** Kabz|4D has quit IRC | 20:33 | |
| sarw | but to do a check out of source code do I need to install svn or svn client ? | 20:34 |
| sarw | benji, ^^^ | 20:34 |
| *** wosc has left #zope | 20:34 | |
| *** giampaolo has joined #zope | 20:34 | |
| betabug | svn client | 20:34 |
| *** smita has quit IRC | 20:35 | |
| sarw | betabug, thanks | 20:35 |
| betabug | np :-) | 20:35 |
| *** agroszer_ has joined #zope | 20:38 | |
| *** agroszer has quit IRC | 20:39 | |
| *** slackrunner has joined #zope | 20:44 | |
| *** j-w_ has joined #zope | 20:49 | |
| *** aaronv has quit IRC | 20:55 | |
| *** aaronv has joined #zope | 20:57 | |
| *** hannosch has joined #zope | 20:57 | |
| *** astoon has joined #zope | 20:57 | |
| j-w_ | hi hannosch, ccomb | 21:02 |
| j-w_ | you there? | 21:02 |
| j-w_ | shall we start? | 21:02 |
| hannosch | in a minute | 21:02 |
| j-w_ | ok | 21:02 |
| ccomb | hi | 21:03 |
| j-w_ | btw, I couldn't find info on who can create new @zope.org mailinglists - is there a ml maintainer or something? | 21:04 |
| hannosch | here now | 21:05 |
| hannosch | j-w_: I'd ask Jens Vagelpohl | 21:05 |
| j-w_ | ok, thanks | 21:05 |
| hannosch | generally he knows this stuff | 21:05 |
| j-w_ | hannosch, ccomb where do we start? | 21:06 |
| hannosch | appoint a secretary? | 21:06 |
| hannosch | someone to take some notes and write a mail in the end | 21:06 |
| j-w_ | ok | 21:06 |
| j-w_ | good point | 21:07 |
| *** JaRoel|4D has joined #zope | 21:07 | |
| hannosch | I guess I'll volunteer for this time | 21:07 |
| *** __mac__ has quit IRC | 21:07 | |
| j-w_ | ok | 21:07 |
| hannosch | meeting time: maximum an hour? | 21:08 |
| j-w_ | i'll make some notes too for myself, so we can compare | 21:08 |
| j-w_ | yes, max | 21:09 |
| hannosch | ok. ccomb you listening? | 21:09 |
| j-w_ | i'd like to figure out what the three of us can do / want to do | 21:09 |
| * ccomb listening | 21:09 | |
| j-w_ | for the ZTK that is | 21:09 |
| hannosch | ok, so agenda items (what should we talk about)? | 21:09 |
| ccomb | the question is, what do we need to release | 21:10 |
| ccomb | or what are we missing | 21:10 |
| *** mcdonc has quit IRC | 21:10 | |
| ccomb | I've started creating a script to check versions | 21:10 |
| ccomb | probably z3c.checkversions or something | 21:10 |
| *** mcdonc has joined #zope | 21:10 | |
| hannosch | ok. so we have "what the hell should we do". should we just start with that and go from there? | 21:11 |
| j-w_ | we can also reiterate some of the thoughts we shared in private mails | 21:11 |
| j-w_ | to record them | 21:11 |
| ccomb | the current buildbots are green, but none is checking the current released packages | 21:12 |
| j-w_ | which was, uhm, let me see: "we see ourselves as representatives of communities that make use of the ZTK" | 21:12 |
| *** TresEquis has joined #zope | 21:13 | |
| j-w_ | ccomb: the zopetoolkit tests, test the released versions, right? | 21:13 |
| ccomb | no | 21:13 |
| ccomb | the development branches | 21:13 |
| *** teix has left #zope | 21:13 | |
| ccomb | that is, the next versions, not yet released | 21:13 |
| hannosch | I thought there tests for both? | 21:14 |
| hannosch | released and SVN | 21:14 |
| ccomb | I had another buildbot with released versions, but it is stopped | 21:14 |
| ccomb | I will reenable it | 21:14 |
| sarw | svn co http://svn.zope.org/zope2docs/trunk/ ZOPE-SOURCE/ giving message svn: Repository moved permanently to '/zope2docs/trunk/'; please relocate | 21:14 |
| ccomb | sarw: /repos/main/zope2docs, etc.... | 21:14 |
| j-w_ | if you run the zopetoolkit tests, you run tests in released packages | 21:14 |
| j-w_ | and yuo can selectively choose what packages to checkout and test with | 21:15 |
| *** matleh has quit IRC | 21:15 | |
| hannosch | there's a second config file, which will check out all the SVN branches (trunk's) | 21:15 |
| j-w_ | right | 21:16 |
| hannosch | that's the mr.developer stuff ([sources]) | 21:16 |
| ccomb | yes, I'm using bin/buildout -c development.cfg | 21:16 |
| j-w_ | ah, ok | 21:16 |
| ccomb | but we need both | 21:16 |
| ccomb | we really also need other platforms | 21:16 |
| TresEquis | anybody know Florian Schulze? | 21:16 |
| TresEquis | His IRC nick? | 21:17 |
| hannosch | TresEquis: that's fschulze. he's working for Jarn ;) | 21:17 |
| TresEquis | Ah, cool -- I'm hoping to bug him to merge my bzr-enabling branch for mr.developer | 21:17 |
| hannosch | ok. I'm happy with the current state of testing for the ZTK. anything else we need there? | 21:17 |
| j-w_ | well, if all ztk tests pass for released packages | 21:18 |
| ccomb | we need 64bit linux, and windows | 21:18 |
| j-w_ | does that mean we can release a ztk? | 21:18 |
| j-w_ | my collegue janjaap is working on a buildbot on windows | 21:18 |
| hannosch | j-w_: I have a lot more questions around, what should be in there, what is the actual technical outcome of a release, what "change policies" does a release have ... :) | 21:19 |
| j-w_ | there were some issue with 64bit, not sure what they were | 21:19 |
| j-w_ | hannosch: right | 21:19 |
| hannosch | so, for testing, we want more platforms. janjaap is working on that. who follows up and bugs him? | 21:19 |
| j-w_ | he is being bugged already | 21:20 |
| j-w_ | for example by me | 21:20 |
| j-w_ | :-) | 21:20 |
| hannosch | ok. I'll just note you as official janjapp bugger :) | 21:20 |
| ccomb | if someone can just provide slaves, I can add them to the adpy masters | 21:20 |
| ccomb | afpy masters | 21:20 |
| hannosch | janjaap is running a huge bunch of masters / slaves himself. he can just add those | 21:21 |
| hannosch | what matters to me are mails to the zope-tests list | 21:21 |
| j-w_ | ccomb: I'll tell him anyway | 21:22 |
| hannosch | so they show up in the daily report | 21:22 |
| j-w_ | hannosch: afaik his bb is sending mails now | 21:22 |
| j-w_ | since yesterday or so | 21:22 |
| hannosch | yep. that's what I've seen | 21:22 |
| j-w_ | at least he's working on it | 21:22 |
| j-w_ | ok | 21:22 |
| * ccomb is looking at securactive buiildbots | 21:22 | |
| j-w_ | so testing is being dealt with? with bugging from us? | 21:23 |
| hannosch | yep. +1 | 21:23 |
| *** sarw has quit IRC | 21:23 | |
| j-w_ | it still leaves us with the difficult questions of course :-) | 21:23 |
| ccomb | regarding the release policy, I would really like to implement the buildbot-based auto-release | 21:23 |
| j-w_ | what's the outcome of a release and what's the change policy | 21:23 |
| ccomb | at least for minor versions | 21:24 |
| hannosch | sure. what exactly does each of you want out of release? like a versions.cfg file at a specifc url or what? | 21:24 |
| j-w_ | the ztk is essentially that, right? | 21:24 |
| j-w_ | a set of versions that other projects can use, so yes | 21:24 |
| hannosch | I'd like to have at least something like http://download.zope.org/Zope2/index/2.12.5/ that is an index and a versions.cfg file for each release | 21:24 |
| j-w_ | a URL where we can find the "core" versions and the "zopeapp" versions etc. | 21:25 |
| hannosch | bonus points for some textual description of the changes in each release | 21:25 |
| j-w_ | why an index too? | 21:25 |
| hannosch | we don't really need one. it's just easy to create | 21:25 |
| hannosch | and makes the non-buildout folks happy | 21:25 |
| j-w_ | yes, we need some generated site of some sort per release, displaying the changes in the packages | 21:25 |
| j-w_ | ah, ok | 21:25 |
| hannosch | ok. so ccomb what would you like to have as a release outcome? | 21:26 |
| ccomb | maybe a ZTK release should be defined by x.y only | 21:26 |
| ccomb | not x.y.z | 21:26 |
| *** mcdonc has quit IRC | 21:27 | |
| *** mcdonc has joined #zope | 21:27 | |
| ccomb | so we can add minor bugfix versions each time there is a new release | 21:27 |
| ccomb | and the ZTK is always uptodate | 21:27 |
| ccomb | the generated versions.cfg should contain all the latest (minor) versions | 21:27 |
| j-w_ | what about: download.zope.org/ztk/release/1.1 with a ztk.cfg in it and a the zopeapp.cfg (for as long as it exists) in it, and an index directory in there as well? | 21:27 |
| ccomb | and the index can contain every previous versions | 21:27 |
| hannosch | j-w_: sounds good | 21:28 |
| j-w_ | ccomb: you mean the "ztk release 1.1" from yesterday can be different from that of today? | 21:28 |
| ccomb | yes | 21:28 |
| j-w_ | because minor versions have been updated? | 21:28 |
| j-w_ | rather not | 21:28 |
| j-w_ | once we fix a number, it should be fixed | 21:28 |
| hannosch | nah, I need something that is an exact specification | 21:29 |
| j-w_ | i'd rather have x.y.z. release than | 21:29 |
| hannosch | you can extend from SVN, which gives you an updated list | 21:29 |
| ccomb | yeah, the ZTK itself can have a minor versions | 21:29 |
| ccomb | we start with 1.1.0 | 21:29 |
| j-w_ | hannosch: right | 21:29 |
| hannosch | I'd like to say Zope 2.13.1 depends on ZTK 1.1.2 | 21:29 |
| j-w_ | me too | 21:29 |
| *** astoon has quit IRC | 21:30 | |
| ccomb | hannosch: that's what I mean | 21:30 |
| j-w_ | ow, ok! | 21:30 |
| j-w_ | :-) | 21:30 |
| hannosch | ok, applause for agreeing :) | 21:30 |
| j-w_ | I misunderstood you then | 21:30 |
| j-w_ | :-) | 21:30 |
| ccomb | not ZTK 1.1.2, but probably ZTK 1.1.23 | 21:30 |
| *** menesis has joined #zope | 21:30 | |
| ccomb | since everytime a new package is released, we have a new exact specification of the ZTK | 21:30 |
| *** dvschramm has quit IRC | 21:31 | |
| j-w_ | hannosch: how do you feel about the auto-generated minor releases? | 21:31 |
| hannosch | how often do you release bugfix releases for BB or Grok? | 21:31 |
| TresEquis | you classically need a "fixed" version *plus* one which can float | 21:31 |
| ccomb | we can also provide a generic 1.1 url which point to the latest | 21:31 |
| j-w_ | based on a green bb at a given time | 21:31 |
| hannosch | I think something like a new bugfix release each month is quite enough for Zope2 | 21:31 |
| j-w_ | hannosch: quite irregularly at the moment | 21:31 |
| hannosch | right. it's not really regular here either | 21:32 |
| j-w_ | hannosch: it would be quite enough for grok too | 21:32 |
| ccomb | BB has no release yet | 21:32 |
| j-w_ | so, we would not auto-generate it then? | 21:32 |
| hannosch | sure. we have a fixed rule of something like "every first Monday in a month" there's a new Plone 3.3.x release for example | 21:32 |
| ccomb | I would like the z3c.checkversions script I'm creating to be able to generate the new versions.cfg | 21:32 |
| ccomb | an give it to the buildbot | 21:32 |
| j-w_ | could the zopetoolkit package play that role? | 21:33 |
| j-w_ | of z3c.checkversions I mean? | 21:33 |
| hannosch | well. if it is fully automated, we could have lots of x.y.Z releases. but that's not required for me | 21:33 |
| ccomb | why not, but I would like the checkversions script to be reusable in any project | 21:33 |
| j-w_ | ccomb: ok, sure, we can always include it in zopetoolkit | 21:33 |
| hannosch | the release scripts for Zope2 are in some other package as well. we can concentrate all of them into something if we want to | 21:34 |
| j-w_ | hannosch: not required for grok either - maybe some eyeballs cannot hurt in the begining either | 21:34 |
| ccomb | hannosch: it would allow to update a project with latests ztk packages, without waiting for a new framework releasae | 21:34 |
| j-w_ | ok | 21:34 |
| hannosch | ccomb: sure. bit I'd see that as a nice-to-have, not a requirement | 21:35 |
| ccomb | of course | 21:35 |
| ccomb | a nice goal would be working so that we become unuseful a releasers :) | 21:35 |
| hannosch | right. I think there's some manual work when we switch major releases. like 1.0.x to 1.1.y | 21:36 |
| ccomb | yes, there is some branch management to handle | 21:37 |
| hannosch | someone needs to decide what should go in there and when something moves from 1.1.0 alpha to a final | 21:37 |
| j-w_ | right | 21:37 |
| j-w_ | how would this someone determine this? | 21:37 |
| hannosch | I think that is up to us to decide | 21:38 |
| j-w_ | e.g. when there's a new major version of one of the packages? | 21:38 |
| ccomb | we just need to freeze the major versions | 21:38 |
| ccomb | then look at the color of the buildbot | 21:38 |
| ccomb | freezing the major versions means creating maintenance branches for every package, isn"t it ? | 21:39 |
| hannosch | right. but we have lots of feature updates happening all the time. when there's a new zope.event 3.6 (from 3.5) I don't want to have an automatic ZTK 1.1 to 1.2 upgrade | 21:39 |
| j-w_ | hannosch: exaclty | 21:39 |
| j-w_ | but when *do* we? | 21:39 |
| ccomb | sure, no | 21:39 |
| ccomb | a given ZTK versions should always have the same major versions | 21:40 |
| hannosch | how often do you expect BB and Grok releases? every six month? every nine month? | 21:40 |
| ccomb | a 1.1 is already planned for BB | 21:40 |
| j-w_ | major grok releases? about 9 months I'd say - I would hope we could make that :) | 21:40 |
| j-w_ | 1.1 is Very Close Now | 21:41 |
| hannosch | right. I think we usually aim for six but end up with some more time | 21:41 |
| ccomb | probably every 6 to 12 months for BB | 21:41 |
| j-w_ | 1.2 should not follow too long after it - lot's of work has been done for it already, esp. getting rid of as much "old" zope.app packages as we can | 21:41 |
| ccomb | but BB is not much more from the ZTK, for now | 21:41 |
| hannosch | personally I'd be fine with releasing a new ZTK feature release whenever any of us wants one | 21:42 |
| j-w_ | but a Grok release does not imply in itself that is is based on a new ZTK release, right? | 21:42 |
| hannosch | if we keep a good backwards compatibility story, there shouldn't be much of a problem | 21:42 |
| j-w_ | hannosch: uhm, well, yes, I think I like that | 21:42 |
| j-w_ | hannosch: it just sounds too simple ;) | 21:43 |
| hannosch | oh. the hard question is ZTK 2.0 | 21:43 |
| hannosch | but we don't have to solve that right now ':) | 21:43 |
| j-w_ | hannosch: how backwards compatible should a x.2 be compared to x.1 ? | 21:43 |
| j-w_ | there's proably ideas about that written down somewhere | 21:43 |
| hannosch | I think we don't do deprecations and removal anymore (at least not recently) | 21:44 |
| *** nebo has quit IRC | 21:44 | |
| hannosch | so there's not much that can actually break | 21:44 |
| ccomb | backward compatibility breaking only happens in X.y.z | 21:44 |
| hannosch | +1 | 21:45 |
| TresEquis | hannosch: dropping support for Python 2.4, for instance | 21:45 |
| ccomb | that means, if we have a zope.component 4.0.0, it will be part of ZTK 2.0 or 3.0 | 21:45 |
| j-w_ | you mean, for example, leaving backwards compatibilty imports and such | 21:45 |
| j-w_ | ccomb:, hannosch, ok, agreed | 21:45 |
| hannosch | j-w_: indeed | 21:45 |
| TresEquis | j-w_: I would guess that a major bump might *drop* the BBB imports | 21:45 |
| hannosch | when do we allow packages to be added or removed from the set? in a x.Y ? | 21:46 |
| hannosch | I'd like to remove all zope.app stuff none of us needs anymore | 21:46 |
| ccomb | bb uses most of them | 21:47 |
| j-w_ | hannosch: which means we need to find out what of these packages are indeed not used anymore | 21:47 |
| j-w_ | right | 21:47 |
| j-w_ | grok uses some of them still | 21:47 |
| j-w_ | more so in 1.1, hopefully (way) less so in 1.2 | 21:47 |
| ccomb | but they will be slowly removed too | 21:47 |
| hannosch | right. but zope.app.wfmc ? or zope.app.xmlpickle ? | 21:47 |
| hannosch | I think there's some nobody ever used | 21:47 |
| j-w_ | so, the ztk team can determine from time to time what zope.app.* to remove? | 21:47 |
| hannosch | +1 | 21:48 |
| j-w_ | ok, and we back that decission up with our "own" communities | 21:48 |
| hannosch | we have some guidelines on that. but basically I'd say whatever at least two of us use | 21:48 |
| j-w_ | hannosch: zope2 isn't using any zope.app right? | 21:48 |
| ccomb | removing ok, but based on what? | 21:48 |
| hannosch | Zope2 trunk isn't anymore indeed | 21:48 |
| ccomb | do we need some poll on package usage? | 21:48 |
| ccomb | or some tool like debian package stats? | 21:49 |
| hannosch | the three of us need to find out for their project | 21:49 |
| j-w_ | so, we can remove packages when bb and grok are not using them anymore then? | 21:49 |
| hannosch | yes | 21:49 |
| j-w_ | I need to think about that a little | 21:49 |
| ccomb | it's more than grok or bb, but the real app people are creating | 21:49 |
| hannosch | but there's also some zope.* packages currently in the under-review section, I'd like to get rid ot | 21:49 |
| hannosch | ccomb: right. the "real app" people don't have any voice in this group | 21:50 |
| j-w_ | well, the whole "under review" is problematic -who does the reviewing I mean | 21:50 |
| hannosch | I don't feel like speaking for them | 21:50 |
| j-w_ | hannosch: well, how do we deal with developers building apps with grok, using a package zope.app.foo and then we drop it from the ztk | 21:50 |
| hannosch | j-w_: I think we need to do an initial cleanup round over those and just decide | 21:51 |
| ccomb | it most people are using certain packages, they should probably end up in the ztk if possible, isn't it? | 21:51 |
| TresEquis | I posted a list of packages being used by each f/w | 21:51 |
| hannosch | TresEquis: right. thx. we should have a look at that | 21:51 |
| j-w_ | TresEquis: yes, I saw that - very useful! | 21:51 |
| ccomb | we have to define a policy for adding and a policy for removing | 21:51 |
| hannosch | we have some rules at http://docs.zope.org/zopetoolkit/about/coreextra.html | 21:52 |
| hannosch | I think those make sense | 21:52 |
| hannosch | they cover the "we want to promote", "many people use it" cases | 21:52 |
| * j-w_ will re-read them | 21:52 | |
| hannosch | like z3c.form for example | 21:52 |
| ccomb | ok, have yet to create an extra.cfg | 21:52 |
| TresEquis | j-w_: you tell people that such packages can be depended on separately | 21:52 |
| *** maiky has joined #zope | 21:53 | |
| TresEquis | because the wider community lacks resources to support it within the "core" set | 21:53 |
| ccomb | extra.cfg would not be the core, and would not even need to have passing tests | 21:53 |
| * hannosch is back in two min, sorry | 21:53 | |
| *** agroszer_ has quit IRC | 21:53 | |
| TresEquis | individual projects are always going to have software which is outside any managed set, right? | 21:54 |
| j-w_ | TresEquis: I tend to agree, but I also do not want to scare away people from using a newer version of grok - so maybe this can be solved by having documentation that tells what changed/got removed in a particular ztk release | 21:54 |
| TresEquis | j-w_: exactly | 21:54 |
| j-w_ | maybe even with some notes on "why it got removed" | 21:54 |
| TresEquis | document very clearly what people need to do to add it back (e,g,. to their buildout.cfg or install_requires) | 21:55 |
| j-w_ | because that info actually helps developers with grok, bb, etc. tremendously | 21:55 |
| TresEquis | yes indeed | 21:55 |
| ccomb | we can have a movingout.cfg, to progressively move packages out of the core | 21:55 |
| TresEquis | deprecated.cfg? | 21:55 |
| *** mcdonc has quit IRC | 21:55 | |
| ccomb | yes :) | 21:55 |
| hannosch | back | 21:55 |
| *** mcdonc has joined #zope | 21:56 | |
| j-w_ | hannosch: ccomb we have a couple of minutes left - do you want to conclude for today or continue a bit more? | 21:56 |
| hannosch | sounds good. we are running out of time, should we agree on a next meeting? | 21:56 |
| ccomb | we could even rename zopeapp.cfg to deprecated.cfg | 21:56 |
| j-w_ | ccomb: not yet please | 21:57 |
| *** webmaven has quit IRC | 21:57 | |
| ccomb | or deprecating.cfg | 21:57 |
| j-w_ | but eventually maybe/probably | 21:57 |
| j-w_ | hannosch: we should definitley agree on a next meeting | 21:57 |
| j-w_ | shall we attempt at/arround the weekly #zope meeting? | 21:57 |
| hannosch | let's do that. I'm away for the next week. back on the 18th | 21:58 |
| j-w_ | ok, so the next meeting then will be, let's see... | 21:58 |
| j-w_ | the 18th? | 21:58 |
| hannosch | Tue, May 18th ? | 21:58 |
| j-w_ | ok | 21:58 |
| j-w_ | set | 21:58 |
| hannosch | before or after the #zope meeting | 21:58 |
| j-w_ | I'd prefer before | 21:58 |
| j-w_ | timing-wise | 21:59 |
| hannosch | so 16:00 to 17:00 ? | 21:59 |
| hannosch | ccomb: ? | 21:59 |
| j-w_ | fine with me | 21:59 |
| * ccomb checking | 21:59 | |
| ccomb | ok | 21:59 |
| hannosch | cool. I'll post some notes and we continue some discussion on the mailing list | 21:59 |
| j-w_ | hannosch: I took notes too | 21:59 |
| j-w_ | shall I send them too you | 21:59 |
| hannosch | j-w_: please do | 22:00 |
| j-w_ | ok | 22:00 |
| j-w_ | thank you guys! | 22:00 |
| hannosch | thank you! :) | 22:00 |
| ccomb | see you! | 22:00 |
| j-w_ | hannosch: there's no ztk list yet | 22:00 |
| ccomb | not sure we need one | 22:00 |
| j-w_ | shall we continue on zope-dev ml for a while? | 22:00 |
| * hannosch feels good about this. but it all sounds to easy ;) | 22:00 | |
| j-w_ | me neither actually | 22:00 |
| j-w_ | hannosch: it does :-) | 22:00 |
| hannosch | zope-dev has a tendency to be noisy. I don't want to force anyone to keep up with all of that | 22:01 |
| hannosch | I read it all, so I'm fine with zope-dev | 22:01 |
| j-w_ | ok, I'll create a list anyway then | 22:01 |
| ccomb | can't we recycle the old zope3-dev ? :) | 22:01 |
| j-w_ | I read it too... so.... | 22:01 |
| hannosch | nah, ccomb you fine with zope-dev? | 22:02 |
| ccomb | I'm ok with zope-dev now | 22:02 |
| hannosch | ok. so zope-dev it is | 22:02 |
| j-w_ | ok | 22:02 |
| j-w_ | yes | 22:02 |
| j-w_ | need to go now, I'll send the notes this evening though | 22:02 |
| j-w_ | bye and thanks again | 22:02 |
| hannosch | cool | 22:02 |
| * ccomb needs some food | 22:03 | |
| hannosch | oh, food! :) | 22:03 |
| *** j-w_ has quit IRC | 22:04 | |
| *** hannosch has left #zope | 22:04 | |
| *** hannosch has joined #zope | 22:05 | |
| hannosch | damn. my IRC client didn't log :( | 22:06 |
| betabug | hannosch: I wasn't following the conversation, but if you need logs, tell me | 22:07 |
| hannosch | betabug: if you could sent me one from the last hour | 22:07 |
| hannosch | that would save me :) | 22:07 |
| betabug | ok | 22:07 |
| betabug | /msg me your mail address :-) | 22:07 |
| hannosch | got it? | 22:08 |
| hannosch | aha, janjaap writes: "The cleaning lady keeps on pulling the ethernet cables from my machine" :)) | 22:09 |
| betabug | yupp | 22:09 |
| *** prinzdezibel has left #zope | 22:10 | |
| hannosch | betabug: Danke! | 22:11 |
| betabug | np :-) | 22:11 |
| TresEquis | hannosch: you can also get it from http://zope3.pov.lt/irclogs-zope/ | 22:12 |
| hannosch | TresEquis: right. I remembered that about a minute ago :) | 22:13 |
| *** axelix has quit IRC | 22:23 | |
| *** redir has quit IRC | 22:31 | |
| *** hannosch has left #zope | 22:32 | |
| TresEquis | Anybody mind if we enable a CIA bot for svn.zope.org changes here? | 22:36 |
| *** CIA-46 has joined #zope | 22:37 | |
| shen-long | TresEquis, ! :) | 22:47 |
| digilord | Is there a method to get the last item added to a container? | 22:48 |
| TresEquis | digilord: depends on the container | 22:49 |
| kosh | not that I can think of | 22:49 |
| kosh | why would you need to? | 22:49 |
| TresEquis | container.objectValues()[-1] will work for stock folders | 22:49 |
| digilord | TresEquis, Ok trying that | 22:49 |
| TresEquis | BTrees keep their items in sorted order by key | 22:49 |
| shen-long | rather then get the 'last item' we're trying to get the item that triggered a ContainerModified event | 22:50 |
| TresEquis | and OrderedFolders allow the user to re-order the folder, which will make [-1] be whatever the user made the last one in the list | 22:50 |
| shen-long | but the event gives us nothing beyond the object which is the container | 22:50 |
| TresEquis | you should be listing for an ObjectAdded event then ;) | 22:50 |
| shen-long | yes, except, here's the rub | 22:51 |
| shen-long | we don't want to have to edit this egg everytime we add a new object to watch for | 22:51 |
| shen-long | so we're grabbing the action method of objects in our schema to 'do crap' | 22:51 |
| shen-long | and the subscriber is in a universal egg | 22:51 |
| shen-long | and if we look for the objectadded, then we need to know what object is added ... | 22:52 |
| shen-long | hmm | 22:52 |
| shen-long | I guess we could look for a higher level interface | 22:52 |
| * digilord is working with shen-long | 22:53 | |
| TresEquis | in your added subscriber, you can examine the object's aq_parent | 22:54 |
| TresEquis | and just ignore it if the containe is not one you care about | 22:54 |
| shen-long | hmm | 22:54 |
| shen-long | ok, so aq_parent, we're in zope3 right now | 22:54 |
| shen-long | do we have aq in zope3 ? | 22:55 |
| shen-long | ztk, bluebream, yellowfish, whatever ;p | 22:55 |
| TresEquis | use __parent__ | 22:58 |
| TresEquis | contained.__parent__ | 22:59 |
| shen-long | hmm | 22:59 |
| *** benji has quit IRC | 23:00 | |
| shen-long | if I have ISomeInterface | 23:00 |
| shen-long | and then class(SomeInterface) implements(ISomeInterface) | 23:01 |
| shen-long | blah, think we got it | 23:02 |
| shen-long | by just using it's inherited class (duh....) | 23:02 |
| shen-long | and.. it works ;p | 23:04 |
| shen-long | TresEquis, thank you thank you ! :) | 23:04 |
| *** webmaven has joined #zope | 23:05 | |
| *** sunew has quit IRC | 23:06 | |
| *** smita has joined #zope | 23:10 | |
| *** lisppaste6 has quit IRC | 23:11 | |
| *** lisppaste6 has joined #zope | 23:11 | |
| *** daMaestro has quit IRC | 23:11 | |
| TresEquis | shen-long: you're welcome | 23:16 |
| *** daMaestro has joined #zope | 23:24 | |
| *** benji has joined #zope | 23:27 | |
| *** giampaolo has quit IRC | 23:33 | |
| *** giampaolo has joined #zope | 23:43 | |
| *** slackrunner has quit IRC | 23:50 | |
| *** slackrunner has joined #zope | 23:51 | |
| CIA-46 | tseaver * r112105 zopetoolkit/ztk.cfg: Use new bugfix release of zope.principalannotation. | 23:54 |
| CIA-46 | tseaver * r112106 zopetoolkit/buildout.cfg: Fussy. | 23:54 |
| *** slackrunner has quit IRC | 23:55 | |
| *** giampaolo has quit IRC | 23:57 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!