| **** BEGIN LOGGING AT Fri Oct 1 12:37:54 2004 | ||
| -->You are now talking on #schooltool | 12:37 | |
| ---gregweb is now known as gregaway | 13:02 | |
| ---Disconnected (). | 13:59 | |
| **** ENDING LOGGING AT Fri Oct 1 13:59:17 2004 | ||
| **** BEGIN LOGGING AT Fri Oct 1 15:30:11 2004 | ||
| -->You are now talking on #schooltool | 15:30 | |
| -->alga (~alga@office.pov.lt) has joined #SchoolTool | 15:56 | |
| -->pips (~chatzilla@64.59.76.83.cust.bluewin.ch) has joined #schooltool | 16:09 | |
| <--gregaway (~gregweb@64.59.76.83.cust.bluewin.ch) has left #schooltool | 16:19 | |
| -->gregweb (~gregweb@64.59.76.83.cust.bluewin.ch) has joined #schooltool | 16:20 | |
| <--pips has quit ("Chatzilla 0.9.64f [Mozilla rv:1.7/20040707]") | 16:21 | |
| gregweb | Hi Marius! | 16:36 |
|---|---|---|
| mgedmin | hi | 16:37 |
| gregweb | I'm Gregoire. You probaly do not remember me. But we met at the Europython sprint more than a year ago. | 16:37 |
| gregweb | I'm currently looking at schoolbell. I have some questions regarding the timetable schema. | 16:39 |
| gregweb | Do have time at the moment? | 16:39 |
| alga | yes! you were "the responsible one" in Louvain-La-Neuve! | 16:42 |
| alga | we pair-programmed on mail system a bit :-) | 16:42 |
| gregweb | One of them, yes! | 16:42 |
| gregweb | Yes, we worked on a global smtp service as I remember. | 16:42 |
| gregweb | work == I looked and asked, you typed :-) | 16:43 |
| gregweb | how are you! | 16:43 |
| alga | fine, and you? | 16:43 |
| gregweb | I know you're currently finishing a project. | 16:44 |
| gregweb | fine, also! | 16:44 |
| alga | in fact we're getting ready for the second chunk of work on schoolbell | 16:44 |
| gregweb | good | 16:44 |
| gregweb | I'll have some time during october to work also on school tool. | 16:45 |
| gregweb | I'm currently like to understand timetabling of m7 | 16:46 |
| alga | what are you going to work on? | 16:46 |
| gregweb | w. schooltool? | 16:46 |
| alga | yes | 16:46 |
| gregweb | I'd like to be able to make a demo mid november at a school here. | 16:47 |
| gregweb | We probably have different timetable requirements than others. | 16:47 |
| alga | have you seen this post by steve: http://lists.schooltool.org/pipermail/schooltool/2003-November/000094.html | 16:48 |
| gregweb | And now I like to first understand hwo it works in m7 and what can be done to fit it to our needs (or at least partly). | 16:48 |
| alga | he outlines our assumtions there | 16:48 |
| *gregweb reading | 16:48 | |
| gregweb | hmmmm.... | 16:49 |
| gregweb | Concretely: What is a timetable schema? What is it meant for? | 16:49 |
| gregweb | schoolbell | 16:50 |
| mgedmin | a timetable schema is a definition of how a timetable looks like | 16:51 |
| mgedmin | it defines what days there are in a timetable | 16:51 |
| mgedmin | and what periods there are in each day | 16:51 |
| mgedmin | (different days may have a different set of periods) | 16:51 |
| mgedmin | (or the same periods but in a different order) | 16:51 |
| mgedmin | days in a timetable schema may match week days, or they may be completely unrelated | 16:52 |
| mgedmin | we had a bunch of example timetables from various schools and then tried to abstract everything | 16:52 |
| mgedmin | the result might be a bit too abstract and therefore hard to understand | 16:52 |
| gregweb | ok, Q: Is 08:15-09:00 a period? | 16:52 |
| mgedmin | sort of | 16:53 |
| mgedmin | a timetable schema also has a mapping of period to times | 16:53 |
| gregweb | I understand | 16:53 |
| mgedmin | so "Period 1" may be "8:15-9:00" on Mondays, but "8:15-8:45" on Wednesdays | 16:53 |
| gregweb | Ok. I understand why I didn't understand :-) | 16:54 |
| gregweb | We don't need/have this mapping. | 16:54 |
| gregweb | ok | 16:54 |
| gregweb | So for us teh best would be to name the period e.g. 16:45-18:15 and then fill in 16:45-18:15 for every day (same times every day). | 16:57 |
| gregweb | There are no names given to this periods in our case. | 16:57 |
| gregweb | reasonable? | 16:57 |
| mgedmin | I think Period 1, Period 2, Period 3 is better | 16:57 |
| mgedmin | but it's up to you | 16:58 |
| mgedmin | when a concrete timetable is defined, you only have days and period names | 16:58 |
| mgedmin | and then you fill in lectures in that matrix | 16:58 |
| mgedmin | (actually you cannot do that through the web interface, but only with the wxWidgets clients) | 16:59 |
| mgedmin | in Lithuanian schools we usually have numbered periods, so 1, 2, 3 etc seems very natural for me | 16:59 |
| gregweb | Yes, I understand | 16:59 |
| mgedmin | I've seen timetable examples where periods were named A, B, C and then mixed up in different days (A, B, C on Monday, B, C, A on Tuesday, etc.) | 16:59 |
| gregweb | We always talk about times themselves: One pupil to the other: "They moved our math class to tomorrow at 15:15, did you realize" | 17:00 |
| mgedmin | ok | 17:01 |
| gregweb | Q: what to do if a period that exists monday to friday does not exist e.g. at saturday? | 17:04 |
| gregweb | Can we leave empty the fileds? | 17:05 |
| mgedmin | yes | 17:06 |
| mgedmin | if you do not assign a time to a period on a particular week day, that period is skipped | 17:06 |
| mgedmin | if timetable days correspond to week days, then it is even better to exclude that period from the timetable schema | 17:07 |
| mgedmin | have you seen the schoolbell web interface? | 17:07 |
| mgedmin | specifically the timetable schema definition view? | 17:07 |
| gregweb | may we send you a screenshot of what we want to achieve? | 17:07 |
| mgedmin | yes | 17:07 |
| gregweb | We're currently on teh web interface | 17:07 |
| mgedmin | do you know my email? | 17:07 |
| gregweb | Yes we're filling out the timetable schema of the web interface | 17:08 |
| gregweb | e-mail: yes | 17:12 |
| gregweb | you should just have gotten the e-mail from my pair | 17:16 |
| gregweb | mgedmin: did you get teh screenshot? | 17:17 |
| mgedmin | one moment | 17:18 |
| gregweb | ok | 17:18 |
| mgedmin | yes, I hot it | 17:18 |
| mgedmin | s/h/g/ | 17:18 |
| gregweb | When we press update the saturday times move up to the first and second row. | 17:20 |
| gregweb | Do you understand how we like to define the timetable schema? | 17:21 |
| gregweb | by teh way: if you're short on time, mention it. | 17:22 |
| gregweb | s/eh/he/ | 17:23 |
| mgedmin | why do you want to keep the periods at the bottom? | 17:23 |
| mgedmin | that's not possible in schoolbell -- the day just has an ordered list of periods | 17:24 |
| gregweb | you mean the 08:15-10:00 one? | 17:24 |
| mgedmin | gaps are not allowed in that list | 17:24 |
| mgedmin | when you assign times to periods, then you can have gaps | 17:24 |
| mgedmin | (gaps in time, that is) | 17:24 |
| gregweb | In our case tehre are no classes in the vening at saturday. | 17:25 |
| gregweb | Nevertheless we have to define the evening periods. | 17:25 |
| mgedmin | why do you have to define them? | 17:26 |
| gregweb | Is it then later possible to not allocate classes in teh vening of saturday? | 17:26 |
| gregweb | Is it possible to have more than one timetable schema? I think yes. | 17:27 |
| gregweb | Shall we define one for saturday and one for the week days? | 17:27 |
| gregweb | why do you have to define them?: A: Define Saturday or what? | 17:28 |
| mgedmin | could you send me a mockup of an actual timetable | 17:30 |
| mgedmin | ? | 17:30 |
| mgedmin | it would be easier for me to understand what exactly you want to get | 17:30 |
| gregweb | We currently realize that we have to give the periods names. | 17:30 |
| gregweb | we send you a timetable (one minute) | 17:33 |
| gregweb | just sent | 17:36 |
| gregweb | got it? | 17:37 |
| ---alga is now known as alga|away | 17:43 | |
| *mgedmin is mildly busy | 17:50 | |
| mgedmin | ok I got it | 17:52 |
| mgedmin | I suggest you take a set of all times that appear on Mondays and use that set as period names | 17:53 |
| mgedmin | ditto for all other days | 17:54 |
| -->gregweb_ (~gregweb@64.59.76.83.cust.bluewin.ch) has joined #schooltool | 17:54 | |
| mgedmin | lost connection? | 17:54 |
| gregweb_ | Sorry, my battery went down... | 17:54 |
| mgedmin | <mgedmin> I suggest you take a set of all times that appear on Mondays and use that set as period names | 17:54 |
| mgedmin | <mgedmin> ditto for all other days | 17:54 |
| gregweb_ | hmmm? | 17:55 |
| gregweb_ | I currently try another approch (perhaps the one you mention): | 17:55 |
| gregweb_ | I define one day and within this day I define all possible periods. | 17:57 |
| mgedmin | see http://mg.b4net.lt/temp/gregweb/gregweb1.html | 18:00 |
| mgedmin | and http://mg.b4net.lt/temp/gregweb/gregweb2.htm | 18:00 |
| -->th1a (~hoffman@pool-64-223-50-152.prov.east.verizon.net) has joined #schooltool | 18:02 | |
| gregweb_ | ok | 18:03 |
| gregweb_ | Is that the only way currently? | 18:05 |
| gregweb_ | for our case? | 18:05 |
| gregweb_ | I made a pdf out of the above pages. You may delete them if you like. | 18:05 |
| mgedmin | I think I understand your question now | 18:06 |
| mgedmin | do you assume that because 16.45-18.15 on Freitag and 8.15-10.00 on Samstag are displayed in the same row on the first table that they necessarily have to occur at the same time? | 18:07 |
| mgedmin | it is not so | 18:07 |
| mgedmin | on the bottom table you will get different rows for different period names | 18:07 |
| mgedmin | and you may assign different times for them | 18:07 |
| gregweb_ | In the weekdays there are no classes during the day and saturday none at the evening. | 18:08 |
| <--gregweb has quit (Read error: 238 (Connection timed out)) | 18:08 | |
| mgedmin | my mockup matches the PDF you sent me | 18:09 |
| mgedmin | (at least I tried to, I did not study the PDF extensively) | 18:09 |
| mgedmin | I think that you're trying to do something different now | 18:09 |
| mgedmin | anyway the gifs you sent me look fine | 18:10 |
| gregweb_ | Sorry, there are some classes in the morning. I didn't realize. This has to do with the fact that two schools share rooms. | 18:11 |
| gregweb_ | One school mainly has classes during the day and teh other in the evenings (mainly :-). | 18:12 |
| gregweb_ | The mockup is only for one department. They seem not to have classes saturday. | 18:14 |
| gregweb_ | I have a knot somewhere. I'll play more... how long will you be on the chat today? | 18:14 |
| gregweb_ | Thanks a lot! | 18:15 |
| gregweb_ | Actually there are three schools sharing resources ... | 18:18 |
| mgedmin | I'll be here for at least 2 more hours | 18:22 |
| mgedmin | probably 3 at least | 18:22 |
| gregweb_ | Is it ok to eventually ask some more questions? | 18:23 |
| mgedmin | sure | 18:23 |
| gregweb_ | thanks | 18:23 |
| <--tvon|x31 has quit ("Leaving") | 18:23 | |
| ---alga|away is now known as alga | 18:26 | |
| alga | hi Tom! | 18:26 |
| th1a | Hi Alga. | 18:26 |
| th1a | We had a stressful night last night here in the USA. | 18:27 |
| alga | why? | 18:27 |
| th1a | The first presidential debate. | 18:27 |
| alga | ah :-) | 18:27 |
| th1a | The fate of the free world was hanging on John Kerry's shoulders. | 18:27 |
| alga | *sigh* | 18:27 |
| th1a | He did ok. Bush did pretty badly. | 18:28 |
| th1a | Anyway, what have you got on the proposal? | 18:29 |
| -->gregweb (~gregweb@64.59.76.83.cust.bluewin.ch) has joined #schooltool | 18:32 | |
| <--gregweb_ (~gregweb@64.59.76.83.cust.bluewin.ch) has left #schooltool | 18:32 | |
| alga | right | 18:32 |
| alga | I added a new story, Recurring events | 18:32 |
| th1a | OK. I think that's necessary. | 18:33 |
| alga | this is a tough one, a lot of internal calendar infrastructure rework, and the spec is messy | 18:33 |
| th1a | I know. | 18:33 |
| alga | so it will be something like 2 weeks of work or so | 18:33 |
| th1a | Eek. OK. | 18:34 |
| th1a | There's no getting around it. | 18:34 |
| alga | my blurb on it is: | 18:34 |
| alga | Handling recurring events in the calendar. Each event will support | 18:34 |
| alga | the full iCalendar specs recurring event model. iCal views will | 18:34 |
| alga | support retrieving and creating recurring events, so will web views. | 18:34 |
| th1a | Sounds good. | 18:35 |
| alga | then, there's a URI refactoring story | 18:35 |
| th1a | OK. What's the time estimate on that? | 18:35 |
| alga | Refactor URIs to be normal objects, not interfaces. They should be | 18:35 |
| alga | available to the client over a restive inteface. | 18:35 |
| alga | Estimate: 4 developer days | 18:35 |
| th1a | OK. | 18:35 |
| th1a | Is this on the wiki page? | 18:35 |
| alga | I'm editing in on our internal wiki | 18:36 |
| alga | I'll send you the result once I'm done | 18:36 |
| th1a | OK. | 18:36 |
| alga | Or maybe I should put it on schooltool.org? | 18:36 |
| th1a | Yeah, put it on the website. | 18:36 |
| alga | then, there are unclear things re. the basic functionality | 18:36 |
| alga | you expressed some concerns regarding Group, person creation, rename, deletion | 18:37 |
| alga | and also enforcing uniqueness of names | 18:37 |
| th1a | Yes. | 18:38 |
| alga | could you phrase what exactly you want done? | 18:38 |
| th1a | OK... | 18:38 |
| th1a | When a person, resource or group is created SchoolBell should warn the user if another object with that title or first and last name already exist, either through the web interface or an error code over the REST interface. | 18:41 |
| mgedmin | how do you deal with collisions? | 18:42 |
| mgedmin | (there are cases where people have the first and last names in real life) | 18:42 |
| alga | in a sample of 1000 people there's usually a name clash | 18:43 |
| mgedmin | our university faculty stopped giving students email aliases of the form "name.username@domain" for this reason | 18:43 |
| th1a | Well, you need to warn the user when it comes up. | 18:43 |
| mgedmin | a confirmation dialog then? | 18:43 |
| th1a | I guess it is trickier on the REST interface to give a warning. | 18:43 |
| alga | what about changing usernames? | 18:43 |
| th1a | Yeah. Confirmation. | 18:43 |
| mgedmin | "A user called John Ivanauskas already exists, do you want to add another user with the same name?" | 18:43 |
| mgedmin | yes, that would catch people accidentally entering the same persion into the system twice | 18:44 |
| th1a | Having people entered twice tends to be a big problem in school systems. | 18:44 |
| th1a | As does confusing two people with the same name :-) | 18:44 |
| th1a | let's see... | 18:46 |
| th1a | Oh. when groups or people are created through the web interface they should be assigned a parent group. | 18:47 |
| mgedmin | I suggest a drop-down in the adding form | 18:47 |
| th1a | Probably there should be a default group, like 'people' and a drop down. | 18:48 |
| th1a | Yeah. | 18:48 |
| mgedmin | Add this person to group [People v] | 18:48 |
| th1a | Yeah. | 18:48 |
| th1a | And also it would be good if http://example.org/persons/ showed links to all the persons. | 18:49 |
| th1a | Same for resources and groups. | 18:49 |
| alga | mgedmin: told you!!! | 18:49 |
| th1a | :-) | 18:49 |
| th1a | I'd think that should work for the REST interface as well as the web interface. | 18:50 |
| th1a | I guess the last big thing is HTML calendar views for resources. | 18:51 |
| mgedmin | I'm pretty sure that works for the REST interface | 18:51 |
| th1a | It does. | 18:52 |
| alga | lists of groups and persons will be 1/2 day | 18:52 |
| mgedmin | alga: I was always for http://example.org/persons/ showing all persons, wasn't I? | 18:52 |
| th1a | But you can't set the ACL yet. | 18:52 |
| mgedmin | and resources | 18:52 |
| mgedmin | th1a: what do you mean about the ACL? | 18:52 |
| mgedmin | allowing only certain users to see the list of all persons/groups/resources? | 18:53 |
| mgedmin | allowing certain users to add new persons/groups/resources? | 18:53 |
| mgedmin | do I understand you correctly? | 18:53 |
| th1a | Oh, I was referring to setting ACL for resources. | 18:54 |
| th1a | But... | 18:54 |
| th1a | We probably need to start paying a little more attention to access control throughout. | 18:54 |
| th1a | On those "index" pages of persons/groups/resources, the user should only see listed the ones that he has the 'view' permission for. | 18:55 |
| th1a | Perhaps we can ignore that for now. | 18:56 |
| alga | ok, suppose we're deleting a group. | 18:57 |
| alga | what if some persons are unconnected after that? put them somewhere? | 18:57 |
| th1a | Well, that's one reason to have the "persons" index page. | 19:00 |
| alga | OK | 19:02 |
| th1a | I don't know if we should also have a "all persons" group. | 19:02 |
| th1a | It is a little redundant, but I think the users would appreciate it. | 19:02 |
| alga | if so, should membership in it be enforced? | 19:03 |
| th1a | Well, perhaps only the system should be able to add people to those groups and do it automatically and transparently. | 19:04 |
| alga | so, they should not be like normal groups | 19:04 |
| th1a | Yeah. | 19:04 |
| th1a | Right now it is really hard to navigate to people in ST. | 19:05 |
| mgedmin | maybe we need a search form | 19:05 |
| th1a | We need to enforce a little more structure behind the scenes. | 19:05 |
| alga | I think a list of all persons will do it in the short term | 19:05 |
| th1a | In the long run we need to work on a few issues related to searching, but I think that can wait. | 19:06 |
| mgedmin | another thing that we've talked about before: making the timetable schema definition easier to use for simple cases | 19:07 |
| th1a | People will have more attributes soon. | 19:07 |
| th1a | Yeah. How many days have we piled onto this milestone at this point? | 19:07 |
| alga | Is it important? | 19:08 |
| th1a | Don't we keep the milestones around a month? | 19:08 |
| alga | well, we found out that our velocity is about 0.66 | 19:09 |
| th1a | ? | 19:10 |
| alga | that means that we do a month of project work in 1.5 months | 19:10 |
| th1a | Sure. | 19:10 |
| th1a | mgedmin: yeah, we should simplify the schema definition for simple cases. | 19:11 |
| alga | th1a: I suggest the following action plan: I write down all we came up with, send it to you, you choose what you want done in the next step | 19:12 |
| th1a | Right. | 19:12 |
| alga | Responsible for a resource | 19:16 |
| alga | ~~~~~~~~~~~~~~~~~~~~~~~~~~ | 19:16 |
| alga | A resource's event has to have a property stipulating who is responsible for | 19:16 |
| alga | the resource during the scheduled block of time. | 19:16 |
| alga | Can a group be responsible for a resource? | 19:16 |
| th1a | I guess so. | 19:17 |
| -->hazmat (~hazmat@c-24-15-10-12.client.comcast.net) has joined #schooltool | 19:21 | |
| alga | th1a: do you have any concrete stories on ACLs that aren't in the proposal yet? | 19:22 |
| hazmat | alga, have you guys considered davacl as a possible implementation path? | 19:23 |
| th1a | No, not other than allowing ACL's on resources to be set via the web interface. | 19:24 |
| alga | what would an acl on a resource allow/limit? | 19:26 |
| th1a | view/add/modify -- just like people | 19:27 |
| alga | hazmat: no, not yet | 19:27 |
| alga | what exactly is it? | 19:28 |
| alga | th1a: add a new resource? | 19:29 |
| alga | modify -- add to groups? | 19:29 |
| th1a | alga: no, I mean the resource's calendar. | 19:29 |
| th1a | add/modify/view events on the calendar. | 19:30 |
| alga | I thought we have done that already... | 19:30 |
| hazmat | alga, its a dav spec for permissions on resources, taking into account hierarchical permissions, hierarchical principles, and dav operations to manipulate security on resources, including the standard ones being considered here at the moment (view/modify/delete) | 19:31 |
| th1a | There just isn't an HTML calendar view for a resource. | 19:31 |
| th1a | That may be the only problem. | 19:31 |
| alga | ah, ok | 19:32 |
| th1a | People will just want to browse the resource's calendar and add events. | 19:32 |
| mgedmin | I think we don't allow that currently | 19:33 |
| mgedmin | resource calendars are read-only and only change when events are booked or unbooked | 19:33 |
| mgedmin | or am I mistaken? | 19:33 |
| mgedmin | ah, that only applies for the iCal RESTive views | 19:34 |
| th1a | Events for resources are fundamentally the same as events for people, right? | 19:34 |
| mgedmin | we have some special magic for resource booking | 19:35 |
| mgedmin | the same event appears in two calendars (the person's who booked the resource and the resource's) | 19:35 |
| th1a | Which is handy! | 19:35 |
| alga | and should disappear if it is modified/deleted in either place | 19:36 |
| mgedmin | previously we did not have globally unique IDs for events | 19:36 |
| mgedmin | so updating the resource calendar via iCal would break this linking | 19:36 |
| th1a | No I don't want to do it via iCal. | 19:36 |
| mgedmin | therefore we disabled updates through iCal | 19:36 |
| th1a | Yeah, but I want a more graphical method via the web. | 19:36 |
| th1a | Than we have now. | 19:37 |
| alga | ok | 19:37 |
| alga | so, essentially we have to let the manager specify who can book the resource and who can cancel smb else's booking? | 19:39 |
| alga | and who can view the bookings | 19:40 |
| th1a | Yep. | 19:41 |
| alga | th1a: I counted all estimates, it's ~36 dev days | 19:42 |
| alga | we can commit to do it in 6 weeks or so | 19:43 |
| th1a | OK. | 19:43 |
| th1a | Can you do the link refactoring first? | 19:45 |
| -dmwaters_-{global notice} Hi all! You guys can blame this netsplit on me.:) I restarted the firewall on that server, and didn't realize it wasn't running to start with, so it dropped all active connections.... sorry about that.... Thank you for your patience, and thank you for using freenode! | 19:45 | |
| alga | sure | 19:45 |
| th1a | Etria will be getting started next week, too. | 19:45 |
| alga | what will they be doing? | 19:46 |
| th1a | Oh, that's right, you were away, which reminds me, best wishes on your marriage! | 19:47 |
| alga | thanks! | 19:47 |
| th1a | They're doing 'person info' -- a system for handling demographic data, addresses, family relationships, etc. | 19:48 |
| alga | cool, the practically-needed missing part! | 19:48 |
| th1a | We're planning it to be very customizable. | 19:48 |
| alga | oh oh | 19:52 |
| alga | We had another idea | 19:52 |
| alga | the user should be able to select which groups' calendars should appear on his | 19:53 |
| th1a | Yes. Put that in. | 19:53 |
| alga | so a member of a group could schedule an event for a group, and all members would see it | 19:53 |
| th1a | You mean in the web interface. | 19:54 |
| alga | yes | 19:54 |
| alga | iCal does that for free | 19:54 |
| th1a | A composite view. | 19:54 |
| alga | right | 19:54 |
| alga | the current view is already a composite | 19:54 |
| alga | it merges the r/o timetable calendar onto the editable calendar | 19:54 |
| th1a | right | 19:56 |
| alga | we thought of firing up the 'dogfood' schoolbell server for ourselves | 19:59 |
| alga | and this was the feature request that immediately popped up for us | 20:00 |
| th1a | Yeah. | 20:00 |
| alga | tom, have you figured out the way the timetable manual entry should look like? | 20:01 |
| alga | probably there should be an individual view for timetables | 20:03 |
| th1a | I have a better idea of what it should look like, I think. Actually the way the wxPython interface handles it is pretty close. | 20:04 |
| alga | but the web should be able to do it better, right? | 20:05 |
| th1a | Well, I'd really like to use more drag and drop. | 20:08 |
| th1a | But maybe I'm on crack. | 20:09 |
| th1a | Drag the students onto the classes. | 20:09 |
| alga | that's one thing web deprives you of | 20:19 |
| alga | drag and drop means javascript | 20:20 |
| alga | and usually you don't want it | 20:20 |
| th1a | I know. | 20:20 |
| alga | yikes! | 20:23 |
| th1a | It would be worth using Javascript in this case. | 20:24 |
| alga | with all the added stories the total sum is 60.5 dev days | 20:24 |
| th1a | Oh. Yeah, I thought we were getting into that range... | 20:24 |
| th1a | Well, send me the list. | 20:24 |
| alga | Tom, what about splitting the work into 2 milestones? | 20:32 |
| alga | this way we could ask the payment to be delivered in more parts | 20:33 |
| alga | and you would have some kind of checkpoint | 20:33 |
| alga | cause this piece of work is getting quite large | 20:33 |
| th1a | Sure. But we may need to do some SchoolTool work in between. | 20:35 |
| alga | hm, do you suggest we should work on the schoolbell branch now | 20:35 |
| alga | ? | 20:35 |
| th1a | I'm talking to HTH on Monday and I may be committing us to have a certain amount of SchoolTool functionality ready by April. | 20:36 |
| th1a | I think that both the work you're doing and the work Etria is doing in October is equally applicable. | 20:36 |
| th1a | So I don't think we'll need to truly fork yet. | 20:36 |
| th1a | Could we actually use some of the translation machinery to manage the different interfaces for SchoolTool and SchoolBell? | 20:37 |
| alga | I think it is a good idea. | 20:39 |
| alga | ok, I have sent the proposal out. | 20:44 |
| th1a | got it | 20:45 |
| th1a | Thanks. | 20:45 |
| th1a | I'm going to go eat lunch now. | 20:45 |
| alga | one other thing we need to discuss is the story acceptance protocol | 21:15 |
| alga | we would like to know the narrative acceprance test before we start work | 21:15 |
| alga | and it would be good to get feedback once we think the story is completed | 21:16 |
| alga | probably we should mail you once each story is completed so you could chase it up and make sure it is what you wanted. | 21:16 |
| th1a | Yeah. We need to work that out. I'm feeling more prepared to handle that. | 21:55 |
| <--SteveA has quit (Remote closed the connection) | 23:05 | |
| alga | have a nice weekend everyone! | 23:46 |
| <--alga has quit ("leaving") | 23:46 | |
| ---Disconnected (). | 23:49 | |
| **** ENDING LOGGING AT Fri Oct 1 23:49:59 2004 | ||
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!