**** BEGIN LOGGING AT Fri Dec 17 09:12:01 2004 | ||
-->You are now talking on #schooltool | 09:12 | |
---Topic for #schooltool is http://schooltool.org | 09:12 | |
---Topic for #schooltool set by Aiste at Mon Oct 18 11:47:26 2004 | 09:12 | |
---Disconnected (). | 10:00 | |
**** ENDING LOGGING AT Fri Dec 17 10:00:20 2004 | ||
**** BEGIN LOGGING AT Fri Dec 17 15:54:08 2004 | ||
-->You are now talking on #schooltool | 15:54 | |
---Topic for #schooltool is http://schooltool.org | 15:54 | |
---Topic for #schooltool set by Aiste at Mon Oct 18 11:47:26 2004 | 15:54 | |
-->alga (~alga@office.pov.lt) has joined #SchoolTool | 16:47 | |
<--tvon (tvon@dsl093-119-225.blt1.dsl.speakeasy.net) has left #schooltool ("Leaving") | 17:03 | |
alga | hi, th1a, are you there? | 17:10 |
---|---|---|
th1a | I'm here. | 17:11 |
th1a | What's up, alga? | 17:12 |
alga | what is the status of the proposal? | 17:14 |
th1a | It's OK by me. Maybe I only sent my reply to mgedmin. | 17:15 |
alga | the thing is, I think we'd like to shift the schedule back a week or so | 17:15 |
alga | Marius is away, I got ill, and Gintas is deep in his studies | 17:16 |
alga | so, we kind of lost this week | 17:16 |
th1a | I noticed that. | 17:16 |
th1a | I've been under the weather myself. | 17:16 |
<--jinty has quit (Read error: 60 (Operation timed out)) | 17:17 | |
alga | Marius said that the next release will include just the Etria UI work anyway | 17:17 |
th1a | Right. I've been focusing my attention on that side. | 17:17 |
alga | so the timing is not so essential anyway. Is it true? | 17:17 |
th1a | Well, the overall pace of development is important. | 17:18 |
th1a | But no, I'm not sweating your deadline. | 17:18 |
th1a | otoh, this is probably bad management on my part. | 17:18 |
th1a | I need to start cracking the whip. | 17:19 |
alga | come on ;-) | 17:28 |
th1a | It shouldn't make much difference that you're starting next week. | 17:30 |
mgedmin | was there an explicit deadline date in the proposal? | 17:36 |
th1a | I think so. | 17:37 |
-->jinty (~jinty@213.151.107.243) has joined #schooltool | 17:47 | |
th1a | jinty: hi | 17:47 |
jinty | th1a: hey | 17:48 |
jinty | just wanted to ask about the release schedule. | 17:48 |
th1a | Right. I was going to send you an email. | 17:49 |
th1a | Let's do a release candidate for SchoolBell 0.8 next week, if you can. | 17:49 |
th1a | Then the final after Christmas. | 17:49 |
th1a | At the beginning of January. | 17:50 |
jinty | From which branch, and what work still needs to be done? | 17:50 |
jinty | Who are the people involved? | 17:51 |
th1a | There's still a fair amount of work to be done. I think we're shooting for finishing on Tuesday. | 17:51 |
th1a | This is all Etria, and all the work is in the schoolbell-ui branch. | 17:52 |
th1a | So I guess we can just release from that. | 17:52 |
jinty | Ok, but what are the plans for the branch after this release? will it be merged into the trunk? | 17:53 |
th1a | Yes. | 17:53 |
jinty | But it will have to be schooltool 0.9 and schoolbell 0.9 together. | 17:54 |
th1a | I don't have any strong views about when the merge will happen. | 17:54 |
th1a | SchoolBell 0.9 is going to preceed SchoolTool 0.9, probably by about a month. | 17:55 |
jinty | It's quite difficullt to do it that way. | 17:56 |
jinty | Because the schooltool and bell share the same source package | 17:56 |
jinty | and the version number comes from the source package | 17:56 |
th1a | In Debian, you mean? | 17:56 |
jinty | Debian + Ubuntu + everything else with debs | 17:57 |
jinty | but what about a 0.9 now, and a 0.10 later? | 17:57 |
th1a | Well, I was also going to write a longer post about the coming divergence of SchoolBell and SchoolTool. | 17:58 |
th1a | Maybe I should do that now. | 17:59 |
jinty | how much are they ging to diverge? | 18:00 |
jinty | s/ging/going/ | 18:00 |
mgedmin | it is going to be confusing if we refer both to the calendaring library, and the calendaring product as 'SchoolBell' | 18:00 |
mgedmin | maybe we should come up with different names? | 18:00 |
th1a | Also, perhaps we'll have to delay the .debs for 0.9 but we'll be able to do a source release. | 18:00 |
th1a | Names are a problem. | 18:00 |
th1a | You're right, library should probably have a different name. | 18:01 |
th1a | "Bell?" | 18:01 |
jinty | Is this going to be split into a completely separate python module? | 18:02 |
mgedmin | it is going to be a separate python package | 18:02 |
mgedmin | that depends on parts of Zope 3, but does not depend on the rest of SchoolTool | 18:03 |
mgedmin | I have an initial stab at this library after the week in MatarĂ³ | 18:03 |
jinty | Great, then I can package it in a separate source package. | 18:03 |
jinty | but no, maybe thats not required | 18:04 |
mgedmin | that's probably not useful before there's a zope3 package in debian/ubuntu | 18:04 |
jinty | but, like schooltool it can contain parts of zope. How much of zope does it need? | 18:05 |
*mgedmin looks | 18:05 | |
jinty | in % terms? | 18:06 |
mgedmin | zope.interface, zope.schema | 18:06 |
mgedmin | also zope.publisher.browser if you want to use the bundled iCalendar read view | 18:06 |
mgedmin | and that dependency is only used in unit tests, to get TestRequest | 18:07 |
mgedmin | we also need zope.testing.doctest | 18:07 |
mgedmin | that's it for now | 18:08 |
th1a | So we could still package that all together. | 18:08 |
mgedmin | yes, but how many copies of zope.interface do I need on my system? | 18:08 |
th1a | True. | 18:08 |
jinty | agreed, but pull in all of zope for the interfaces? | 18:09 |
mgedmin | eventually we will want separate packages for this library, but I think that will be when useful zope libraries will be packaged separately | 18:09 |
jinty | my next question was if zope was monolithic | 18:10 |
jinty | but I agree, wait and see | 18:10 |
jinty | back to the schooltool/bell issue | 18:10 |
alga | wooho, I've made rev 2222! | 18:11 |
th1a | So my thoughts at this point are that we should do SchoolBell 1.0 in March, and after that, most of the development will be community driven, at least for features. | 18:11 |
jinty | Right now, If I release some base of code as schoolbell x, I automatically release schooltool x | 18:11 |
th1a | We'll continue marching along with SchoolTool development, and fold relevant bits back in. | 18:12 |
th1a | For SchoolBell 1.0 we'll probably want to as much of the irrelevant school-related bits out as we can. | 18:12 |
th1a | This is more of a pain from our point of view, but it will make SchoolBell easier to use and develop on for other people. | 18:14 |
jinty | but, what I am worried about, is, if we release schoolbell/tool 0.9 with the branch, then all of the features of that branch should be in the next release as well | 18:14 |
th1a | Hm? | 18:14 |
jinty | so we can't release once from the -ui branch, and next from the trunk | 18:14 |
jinty | unless we merge first | 18:14 |
th1a | OK. | 18:15 |
jinty | good, thanks | 18:15 |
th1a | I don't know how difficult merging will be. | 18:16 |
*mgedmin still has to take a look at the changes | 18:16 | |
mgedmin | I didn't have time to do that at the conference | 18:16 |
jinty | since the -ui branch will be released as "stable" in the next release, why not merge often | 18:17 |
jinty | i.e. every few days? | 18:17 |
jinty | the pain might be less later | 18:17 |
jinty | But otherwise, no problems, I will release the -ui branch as a RC when etria is ready. (Wednesday?) | 18:22 |
jinty | it will be released as schoolbell 0.9 and schooltool 0.9 | 18:23 |
jinty | is this ok? | 18:24 |
-->bskahan (~bskahan@dsl093-119-225.blt1.dsl.speakeasy.net) has joined #schooltool | 18:27 | |
th1a | Well, no. Because SchoolBell 0.9 will hide a lot of SchoolTool functionality. | 18:27 |
jinty | Ah. | 18:27 |
th1a | So we could skip SchoolTool 0.9. | 18:27 |
th1a | Or delay the .debs of SchoolBell 0.9. | 18:27 |
jinty | I have to look at the debian build process, but I dont think so. | 18:28 |
th1a | Or just make this SchoolBell 0.8.1? | 18:28 |
jinty | The problem is that because they are from the same source package. | 18:29 |
th1a | I'm getting the feeling that this isn't going to be a quick and easy release. | 18:29 |
jinty | it's really difficult, because the version number of the debs is from the source package | 18:30 |
jinty | and, actually, i never upload .debs | 18:30 |
jinty | they are always built automatically from the source package | 18:31 |
jinty | so the debs always have the same version number as the source package | 18:31 |
th1a | Let me write up the overall strategy for getting to SchoolBell and SchoolTool 1.0 and then we can come up with a long-range plan that make sense. | 18:31 |
---pere_poff is now known as pere | 18:32 | |
th1a | It's a little hard to get across the big picture via IRC. | 18:32 |
bskahan | I think they need to be split into seperate trees, once we can dep on Zope 3 | 18:33 |
jinty | is there a problem with a schooltool 0.9 that is the same as schooltool 0.8? | 18:33 |
th1a | In the medium term, SchoolTool and SchoolBell are going to have to have different sets of page templates. | 18:35 |
jinty | is that all? | 18:35 |
th1a | Which we figure we can handle in the build process. | 18:35 |
bskahan | they have different view code as well | 18:35 |
bskahan | not significantly now, but they will diverge | 18:36 |
bskahan | well, depending on how we go forward | 18:36 |
jinty | but they are one code base right now, with only one difference in configuration? | 18:37 |
bskahan | but we've made changes to schooltool.browser to accomodate the new templates | 18:37 |
jinty | so actually schooltool-ui is schoolbell? | 18:37 |
bskahan | they're one code base right now | 18:40 |
jinty | then will they diverge before for 0.9? | 18:40 |
bskahan | but the sr/schooltool/browser/www directory will have to diverge | 18:40 |
jinty | s/for// | 18:40 |
bskahan | yes, there's features specific to schools (like "view by periods") that won't be in the UI | 18:41 |
jinty | ok, so building schoolbell requires something to be done to this directory? | 18:42 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!