| *** AnsiC has left #schooltool | 00:32 | |
| *** didymo has joined #schooltool | 00:41 | |
| *** jinty has joined #schooltool | 01:04 | |
| *** jinty has quit IRC | 03:30 | |
| povbot` | /svn/commits: * hoffman committed revision 5967: | 09:52 |
|---|---|---|
| povbot` | /svn/commits: I don't seem to need this. | 09:52 |
| *** mooky has quit IRC | 10:12 | |
| *** alga has joined #SchoolTool | 11:03 | |
| *** ignas has joined #schooltool | 11:37 | |
| *** jinty has joined #schooltool | 11:42 | |
| *** alga has quit IRC | 11:56 | |
| *** thisfred has joined #schooltool | 12:01 | |
| *** Aiste has quit IRC | 12:03 | |
| *** faassen has joined #schooltool | 12:24 | |
| *** alga has joined #SchoolTool | 12:25 | |
| *** ignas has quit IRC | 12:32 | |
| faassen | I have a failed doctest example in the schooltool tests today | 12:43 |
| faassen | File "/home/faassen/working/schooltool/schooltool/src/schooltool/setupdata/tests/test_browser.py", line 71, in schooltool.setupdata.tests.test_browser.doctest_SetupDataView_update | 12:43 |
| faassen | basically it's this: | 12:44 |
| faassen | [('work', | 12:44 |
| faassen | - <schooltool.app.app.SchoolToolApplication object at ...>, | 12:44 |
| faassen | ? ^^^ | 12:44 |
| faassen | + <schooltool.app.app.SchoolToolApplication object at 0xb14c63ac>, | 12:44 |
| faassen | ? ^^^^^^^^^^ | 12:44 |
| *** Aiste has joined #schooltool | 12:52 | |
| *** mgedmin has joined #schooltool | 12:55 | |
| *** ignas has joined #schooltool | 13:09 | |
| *** srichter has joined #schooltool | 14:18 | |
| povbot` | /svn/commits: * faassen committed revision 5968: | 14:59 |
| povbot` | /svn/commits: store version in a src/schooltool/version.txt text file, so that both the setup script as well as the schooltool UI can make use of it. | 14:59 |
| *** mgedmin has quit IRC | 15:10 | |
| *** didymo has quit IRC | 15:16 | |
| *** alga has quit IRC | 15:54 | |
| th1a | srichter: Are you back in MA now? | 16:09 |
| srichter | no | 16:10 |
| *** mgedmin has joined #schooltool | 16:18 | |
| faassen | th1a: I replied to your post. | 16:20 |
| faassen | th1a: on the permissions table which I do not quite understand yet I'm afraid. :) | 16:20 |
| th1a | Reading... | 16:20 |
| * faassen waits for the virtual gravel thing. | 16:29 | |
| th1a | OK. | 16:31 |
| th1a | I just sent a reply. | 16:31 |
| th1a | Essentially, you found a few bugs in the table. | 16:31 |
| ignas | hi | 16:32 |
| th1a | hi ignas | 16:32 |
| th1a | is jinty here? | 16:32 |
| faassen | yes,I think the table effort is valuable, though I'm a bit worried we'll lose rules by trying to encapulate. | 16:32 |
| jinty | indeed | 16:32 |
| faassen | th1a: blanking things that make no sense makes sense. | 16:33 |
| * mgedmin scoops a shovelful of gravel and tosses it towards faassen | 16:33 | |
| faassen | th1a: I think we might see two types of permissions, some that apply to person-related data, and some that apply globally, and we may find we end up with two tables. | 16:33 |
| th1a | Is this some Lithuanian idiom? | 16:33 |
| faassen | th1a: anyway, I think we need regular updates. | 16:33 |
| *** wrobel has quit IRC | 16:33 | |
| faassen | no, I think that's just Marius ragging me. :) | 16:33 |
| * faassen uses his force field to withstand the gravel attack. | 16:33 | |
| * faassen points his easter egg powered cannon in Marius's direction. | 16:34 | |
| th1a | faassen: OK we'll get back to the table in a bit. | 16:34 |
| ignas | th1a: one question | 16:34 |
| th1a | Yes? | 16:34 |
| ignas | yellow bits signify global setting in schooltool configuration | 16:34 |
| faassen | did I get the word wrong and it is the thing you hammer the table with something else? | 16:34 |
| ignas | or will they have to be customizable per/user | 16:34 |
| th1a | Oh, yes. Gavel. | 16:35 |
| faassen | gavel, right. | 16:35 |
| faassen | see, I got it all mixed up. | 16:35 |
| faassen | no wonder I got Marius's wrath. | 16:35 |
| th1a | ignas: Not per user. | 16:35 |
| ignas | th1a: cool :) | 16:35 |
| ignas | i think the yellow bits is what's important | 16:35 |
| ignas | as they will have to become a nice access control-pannel | 16:35 |
| th1a | Yes. | 16:35 |
| ignas | or at least a set of zcml directives | 16:35 |
| *** wrobel has joined #schooltool | 16:36 | |
| th1a | OK, faassen: what have you been up to? | 16:36 |
| th1a | What's the plan for this week? | 16:36 |
| faassen | I've been up to.. | 16:39 |
| faassen | the plan I spend as much time as possible on schooltool. | 16:39 |
| faassen | what I've been up to is having a cold and stuff. :) | 16:39 |
| faassen | however, I made the eggs work on the branch. | 16:40 |
| faassen | and I hope to be able to merge that into the trunk. | 16:40 |
| faassen | if it doesn't meet with objections. | 16:40 |
| th1a | Yes, I guess we have to determine that. | 16:40 |
| faassen | basically all the branch does is pull in zc.table (and thus zc.resourcelibrary) as eggs. | 16:40 |
| faassen | when you do 'make' | 16:40 |
| th1a | This is the kind of decision I'm not very useful for. | 16:41 |
| faassen | I want to land this branch. | 16:41 |
| faassen | as soon as possible. | 16:41 |
| faassen | as then I can proceed in trying to plug in my demographics stuff. | 16:41 |
| th1a | jinty: Are you ok with this? | 16:41 |
| faassen | and then continue working on that. | 16:41 |
| * jinty is comfortable merging as soon as he figures out what kind of tarball the releas scripts will generate | 16:41 | |
| th1a | Or do you need to investigate? | 16:41 |
| faassen | jinty: what do you mean about the tarball? I didn't think about generated tarballs at all. :) | 16:42 |
| th1a | srichter: Do you want to take a look at this before we merge? | 16:42 |
| jinty | and a documented installation process | 16:42 |
| th1a | mgedmin? | 16:42 |
| faassen | jinty: I'd like to merge today if possible and I don't know exactly what you want. :) | 16:42 |
| srichter | th1a: I don't understand eggs enough yet to give it a useful review; if it works, it's fine with me | 16:42 |
| mgedmin | does it add any software requirements? | 16:43 |
| faassen | the main thing it does now is pull in some eggs. | 16:43 |
| faassen | mgedmin: setuptools. | 16:43 |
| mgedmin | mhm | 16:43 |
| jinty | faassen: well, er, we normally distribute tarballs to non-developers | 16:43 |
| faassen | it pulls in eggs beyond Zope 3 itself. | 16:43 |
| mgedmin | is setuptools packaged for debian/ubuntu? | 16:43 |
| jinty | mgedmin: yes | 16:43 |
| faassen | the way it hooks in their ZCML is still hacked directly into site.zcml | 16:43 |
| srichter | my main question is: Are we sure that all bugs concerning eggs and Zope 3 are worked out? | 16:44 |
| faassen | what bugs? | 16:44 |
| srichter | well, whatever there might be | 16:44 |
| th1a | We aren't using eggs for Zope 3 itself. | 16:44 |
| faassen | I'm just using eggs for Zope 3 extensions. | 16:44 |
| srichter | Zope 3 has not committed to eggs in the upcoming release... | 16:44 |
| faassen | it is much less impact on the makefile and so on than actually extending the makefile. | 16:44 |
| faassen | that's fine, I just need eggs for zc.table and zc.resourcelibrary, and those exist as I made them. | 16:44 |
| faassen | and any other package I want to pull in, I'll just make an egg. that's easy. | 16:45 |
| srichter | I would let Zope 3 make the step to eggification first and then use it in ST | 16:45 |
| srichter | will those pulled in packages be writable checkouts? | 16:45 |
| faassen | no. | 16:45 |
| srichter | that is not good | 16:45 |
| srichter | I often fix bugs during development | 16:45 |
| srichter | the current Makefile allows me to checkout writable versions if I wish | 16:46 |
| faassen | look, I just want to use a few measly libraries to develop demographics stuff. | 16:46 |
| faassen | I don't want to eggify zope 3. | 16:46 |
| faassen | if you want to have writable checkout you can check them out yourself and install them in development mode. | 16:46 |
| * th1a thinks srichter is overreacting a bit. | 16:46 | |
| jinty | srichter: it is easy to checkout a writable checkout of an eggified package and have the schooltool build use that | 16:47 |
| faassen | I started out changing the makefile but it soon turned into a huge ball of make cruft. | 16:47 |
| jinty | it just needs documentation | 16:47 |
| faassen | unmaintainable makefile cruft. | 16:47 |
| srichter | I am just making an argument; at the end of the day I am far too tired right now to heavily argue for or against anything ;-) | 16:47 |
| th1a | OK. | 16:47 |
| * mgedmin is inclined to try the egg solution | 16:47 | |
| th1a | So primarily this is jinty's domain. If it is ok with him it is ok with me. | 16:48 |
| faassen | I shall add in a document on how to do the development mode checkout egg thing. | 16:48 |
| th1a | mgedmin: Do you want to personally inspect this before it is merged? | 16:48 |
| *** alga has joined #SchoolTool | 16:48 | |
| mgedmin | what's the url? | 16:48 |
| faassen | it's the schooltool-eggs branch. | 16:48 |
| alga | hello, sorry I'm late | 16:48 |
| jinty | I will make a test with the release scripts and come back to faassen with a response | 16:48 |
| faassen | http://source.schooltool.org/svn/branches/schooltool-eggs/ | 16:49 |
| faassen | ok. | 16:49 |
| * mgedmin expected it to be schooltool-omlette | 16:49 | |
| jinty | this afternoon, i think | 16:49 |
| faassen | ok, that would be good. | 16:49 |
| faassen | it's one obstacle that makes it hard to start integrating my other stuff. | 16:49 |
| th1a | Yes, it would be good to actually see some demographics code ;-) | 16:49 |
| faassen | yes. | 16:49 |
| faassen | so my plan is that after this lands.. | 16:50 |
| faassen | I can start moving in some demographics stuff. | 16:50 |
| faassen | I'm still scared of the schooltool skin and viewlets and so on. | 16:50 |
| faassen | but I'll just make a stupid UI first. | 16:50 |
| faassen | as I'm not the UI guy anyway. hopefully we'll get some UI work done here but I don't think we can count on it anytime soon. | 16:50 |
| th1a | A stupid UI will do for starters. | 16:51 |
| th1a | OK... POV? ignas? | 16:52 |
| th1a | Thanks faassen. | 16:52 |
| ignas | we will have ~25 dd for may | 16:52 |
| ignas | what will be your orders ? :) | 16:53 |
| faassen | the security work would be nice. :) | 16:54 |
| th1a | I guess that takes us to the next order of business. | 16:54 |
| th1a | Yes, this might be the time for that, if we can figure out what we want. | 16:54 |
| faassen | I think the steps you and I have been taking were good. | 16:54 |
| th1a | What would we need to decide to do "the security work?" | 16:54 |
| faassen | the longer I stared at the table the more problems I found but also the more sense it made. :) | 16:55 |
| ignas | as in - get rid of ACL views, replace everything with a centralized access control pannel | 16:55 |
| ignas | make the panel usable | 16:55 |
| faassen | and a centralized policy for security, somehow. | 16:55 |
| faassen | this needs some implementation thought. | 16:55 |
| th1a | faassen: I think it was particularly buggy because I kind of changed the design of the table as I went. | 16:55 |
| faassen | th1a: I hope we can get a bugfix release soon. :) I understand how that goes anyway. | 16:56 |
| faassen | anyway, we need to figure out what notions there are in the access control picture. | 16:56 |
| faassen | there is a notion of 'my information' | 16:56 |
| faassen | there's a notion of 'information I have access to through a kind of relationship' | 16:56 |
| faassen | and a notion of 'stuff I can do because I have a certain global group membership/role' | 16:57 |
| faassen | the latter is simplest; those are permissions someone has globally. | 16:57 |
| th1a | Yes. | 16:57 |
| th1a | Yes. | 16:58 |
| faassen | anyway, the question I can't answer myself right now is whether the systm contains enough meta information to get the former two. | 16:58 |
| faassen | like, there doesn't seem to be a notion of 'self' data yet, as far as I understand. | 16:58 |
| faassen | there is a notion of relationship. This may be powerful enough, though the question remains whether we can make it all perform adequately, as far I understand. | 16:59 |
| th1a | That pretty much just comes from context in the database. | 16:59 |
| faassen | context? | 16:59 |
| ignas | could we please go back to the: "now that i own the PoV what am i supposed to do with this thing" | 16:59 |
| ignas | :) | 16:59 |
| faassen | ok, sorry. | 16:59 |
| th1a | ignas: What? | 16:59 |
| ignas | you have got 25 dev days of PoV | 17:00 |
| th1a | Yes. | 17:00 |
| ignas | and i still don't have a clear picture what do you want to do with that timew | 17:00 |
| th1a | Well, fixing access control would be a good use of that time. | 17:00 |
| th1a | That's what launched us down that path. | 17:00 |
| ignas | there are things like ACL, LDAP, SchoolBell extraction ... | 17:01 |
| th1a | Yes. | 17:01 |
| faassen | how important is schoolbell in all of this? | 17:01 |
| th1a | LDAP I think we should pass on. | 17:01 |
| faassen | schoolbell isn't on the critical path right? | 17:01 |
| th1a | It is important that at some point in the next six months we have some kind of SchoolBell release. | 17:01 |
| faassen | ah, ok. | 17:01 |
| th1a | Which shouldn't be that hard. | 17:02 |
| jinty | as release manager, jinty, would like to see SchoolBell building sooner rather than later as he considers it a release blocker | 17:02 |
| th1a | Unless we miscalculated. | 17:02 |
| th1a | jinty: That's what I'm thinking. | 17:02 |
| faassen | jinty talks about himself in the third person. :) | 17:02 |
| jinty | just like Saddam Hussein;) | 17:02 |
| faassen | oh, he does? | 17:02 |
| th1a | So the eggs related changes should be settled quickly enough. | 17:03 |
| faassen | jinty: right, please by the way if you want me to do more eggs stuff. | 17:03 |
| th1a | So that's not a SchoolBell-packaging blocker (barring unforseen disaster). | 17:03 |
| faassen | jinty: that you need as a release manager, etc, let me know. | 17:03 |
| faassen | jinty: I already fixed the version number issue. | 17:03 |
| faassen | jinty: (though didn't do it for Schoolbell yet, that has its own version) | 17:03 |
| jinty | I think we are bound to release schoolbella and schooltool together | 17:04 |
| faassen | jinty: (don't know how schoolbell fits into all this) | 17:04 |
| faassen | with the same version number? | 17:04 |
| jinty | because they use the same base libraries | 17:04 |
| jinty | yep | 17:04 |
| faassen | ok, then it's a 1 line fix I think. | 17:04 |
| th1a | Hm... we should probably sync the ST/SB version numbers. Make them both 2006 x.x | 17:04 |
| mgedmin | SchoolTool Vista | 17:05 |
| mgedmin | then we could postpone the release date a couple of years | 17:05 |
| mgedmin | ;) | 17:05 |
| th1a | OK so, for POV: | 17:06 |
| th1a | * I'll pick out some bugs to fix; | 17:06 |
| th1a | * extracting SchoolBell | 17:06 |
| th1a | Is there a reasonable first step in fixing permissions? | 17:06 |
| th1a | Without trying to solve the problem all at once? | 17:07 |
| ignas | th1a: hiding the current ACL view behind an Access Control Pannel ? | 17:07 |
| th1a | Creating a "permissions control panel" for site-wide permissions configuration? | 17:07 |
| faassen | even though it wouldn't do anything yet? | 17:08 |
| th1a | It would do something. | 17:08 |
| faassen | what? | 17:08 |
| ignas | faassen: even though it would just set some "checkboxes" | 17:08 |
| th1a | The limitation would be that it would only change group-related permissions. | 17:08 |
| ignas | flags | 17:08 |
| faassen | right, if it only changed global group related permissions.. | 17:09 |
| th1a | We'll need more work under the hood to do relationship-based permissions. | 17:09 |
| faassen | and self-permissions. | 17:09 |
| th1a | Yes, I think. | 17:09 |
| faassen | global group related permissions, i.e. parts of the permission role mapping. :) | 17:09 |
| faassen | would work. | 17:09 |
| th1a | OK. We'll shoot for that. | 17:10 |
| th1a | Does that make sense to everyone? | 17:11 |
| faassen | sure. | 17:12 |
| ignas | processing | 17:12 |
| mgedmin | hmm... | 17:12 |
| faassen | for the acl, let's continue the discussion. | 17:12 |
| faassen | refining that table. | 17:12 |
| faassen | and thinking about implementation choices. | 17:12 |
| th1a | Yes. | 17:13 |
| th1a | I think the "staff member" column should go. | 17:13 |
| ignas | th1a: i think i'll need more time to think of a viable first step, as doing the UI apparently has it's downsides | 17:14 |
| th1a | Such as? | 17:15 |
| mgedmin | having to make the UI work with a backend that is not suitable for it? | 17:15 |
| * mgedmin hasn't thought very deeply about security so his comments may be entirely mistaken | 17:16 | |
| th1a | If we're just doing group-based access control, I think our back end is sufficient. | 17:17 |
| alga | but then we'll have to do this stuff over again when the backend changes | 17:17 |
| th1a | I guess it depends on how much the backend has to change. | 17:18 |
| faassen | well, there are three categories of .. | 17:18 |
| faassen | permissions. | 17:18 |
| th1a | I'm not against doing the backend first, though. | 17:18 |
| ignas | th1a: well - with the notion of local permissions gone - probably a lot | 17:18 |
| faassen | some things you are allowed to do globally, or not. | 17:18 |
| faassen | like, add new uers. | 17:18 |
| faassen | users. | 17:18 |
| faassen | if you're a school administrator, you can just add new users. | 17:18 |
| faassen | I think th1a was suggesting we create a UI for the configurable parts of that first. | 17:18 |
| faassen | (not all of those settings are configurable; some things a school admin will always be allowed to do, but in some cases there exist choices in what a student may see, for instance) | 17:19 |
| faassen | some other permissions depend on your relationship with the 'owner' of the object. | 17:19 |
| faassen | like, I may see a student's demographics if I'm his teacher. | 17:19 |
| faassen | th1a wasn't proposing we do a UI for that yet. | 17:19 |
| faassen | I'm not sure how much sense a UI would make right now though. | 17:20 |
| faassen | as after all it's fairly simple check boxes. | 17:20 |
| faassen | all of those settings are global and they need good descriptions on what they do if you check or uncheck them. | 17:20 |
| faassen | (or whatever the UI will look like) | 17:20 |
| th1a | faassen: Yes. | 17:20 |
| th1a | It could be quite simple. | 17:20 |
| faassen | so perhaps it makes more sense to just work on the security story as a design first. | 17:20 |
| faassen | as the UI work wouldn't help (or harm) us that much in the scope of things. | 17:21 |
| faassen | and the shape of the configuration UI *might* be affected by further thinking along the road. | 17:21 |
| th1a | Well, one question is whether or not any changes actually have to be made to implement group based permission. | 17:21 |
| faassen | I think group based permission is the one thing that more or less works now. | 17:22 |
| faassen | except perhaps the permission distribution needs to be more fine grained. | 17:22 |
| faassen | or altered in some way. | 17:22 |
| faassen | i.e. modifying lots of ZCML. | 17:22 |
| faassen | anyway, whatever we do, we need to continue the actual design. | 17:22 |
| th1a | I should note that we can get through SchoolTool 2006 with just group and self based permission if we need to. | 17:23 |
| th1a | self-based meaning the system knows who "owns" their own data. | 17:23 |
| faassen | well, dunno. | 17:23 |
| th1a | Which we can do now reasonably well. | 17:23 |
| faassen | what about a gradebook? | 17:23 |
| faassen | is that owned by the teachers of the section? | 17:24 |
| th1a | Yes. | 17:24 |
| faassen | then that looks like it could work. | 17:24 |
| jinty | mgedmin: apparently the egg setup in schooltool-eggs needs a later version of setuptools than that currently in Debian | 17:25 |
| mgedmin | jinty: is 0.6a9-1ubuntu1 recent enough? | 17:25 |
| jinty | mgedmin: nope needs 0.6a11 AFAIK | 17:26 |
| mgedmin | :( | 17:26 |
| ignas | th1a: so it's ACL design + SchoolBell extraction and some bugs? | 17:26 |
| th1a | OK. I'm thinking that we won't actually have relationship-based permissions in ST 2006. | 17:26 |
| th1a | ignas: That sounds reasonable. | 17:26 |
| mgedmin | this is why I'm not too keen on trying eggs myself -- everything needs bleeding edge, released just yesterday, version of setuptools | 17:26 |
| ignas | faassen: when will your demographics changes be ready, as they might conflict with the extraction in some places ? | 17:27 |
| th1a | argh. | 17:27 |
| faassen | ignas: what extraction? | 17:27 |
| ignas | faassen: not demographics, but skin if to be exact | 17:27 |
| ignas | faassen: schoolbell from schooltool | 17:27 |
| faassen | ignas: oh, the skin changes are currently on hold, I mean, a lot more work could be done but I'm not going to do it soon. | 17:28 |
| faassen | ignas: what's in schooltool.skin is in there. | 17:28 |
| ignas | faassen: you will be the one merging then :D | 17:28 |
| faassen | ignas: sure. | 17:28 |
| faassen | mgedmin: that dependency thing sucks. :( | 17:28 |
| faassen | mgedmin: then again it's reasonably easy to bootstraps the whole thing. | 17:29 |
| th1a | If we don't have the version of setuptools we need in Dapper... is that a showstopper? | 17:29 |
| mgedmin | maybe not, but it is a pain in the donkey | 17:30 |
| faassen | mgedmin: dapper doesn't have it either? | 17:30 |
| mgedmin | dapper has 0.6a9 | 17:30 |
| * mgedmin runs dapper | 17:30 | |
| th1a | OK. I'll keep working on the permissions table. | 17:31 |
| th1a | Have a good week, folks. | 17:31 |
| * th1a bangs the virtual bag of gravel. | 17:31 | |
| faassen | gravel. :) | 17:32 |
| ignas | with a shovel :) | 17:32 |
| faassen | jinty: could you let me/the mailing list know what's needed before you deem the egg branch landable? | 17:32 |
| faassen | mgedmin: and the same to you? | 17:32 |
| mgedmin | faassen: I'm not opposed to landing that branch | 17:33 |
| mgedmin | let's just see what happens | 17:33 |
| jinty | faassen: sure, am busy with it now, | 17:33 |
| faassen | ok. :) | 17:33 |
| faassen | the main advantage is that it doesn't add a whole lot of new infrastructure to the makefile. | 17:34 |
| faassen | just a few minor tweaks. | 17:34 |
| *** srichter has quit IRC | 17:50 | |
| *** wrobel has quit IRC | 18:08 | |
| *** wrobel has joined #schooltool | 18:10 | |
| *** alga has quit IRC | 18:19 | |
| *** faassen has quit IRC | 18:59 | |
| ignas | th1a: ping | 19:11 |
| th1a | ignas: pong. | 19:23 |
| ignas | maybe you do imagine the requirements for booker/ booked resources in calendars | 19:23 |
| th1a | Hm? | 19:24 |
| ignas | as at the moment i am planning to simplify that bit to make it manageable | 19:24 |
| ignas | the problem is: | 19:24 |
| ignas | we had some weird logic that was sorting out information seen on events | 19:24 |
| ignas | depending on what calendar and who was looking at | 19:24 |
| ignas | example: | 19:24 |
| ignas | if you are looking at the calendar of ResourceA you will see only "Booked by: john" not both "Booked by: john" + "Booked resources: ResourceA" | 19:25 |
| ignas | if you are looking at the calendar of john you will not see "Booked by john" | 19:25 |
| th1a | Yes. | 19:25 |
| th1a | Is that more of a pain than it is worth? | 19:26 |
| ignas | and everything mangled up for overlaying | 19:26 |
| ignas | well with sections and timetable events | 19:26 |
| ignas | it is geting out of hand | 19:26 |
| ignas | as i can't reliably decide what should be seen where | 19:26 |
| ignas | and usecases are pretty difficult to express | 19:26 |
| ignas | in some manageable way | 19:26 |
| th1a | On the other hand, all we're trying to avoid is a little redundancy, right? | 19:27 |
| ignas | at the moment i am leaning to: show all the booking information | 19:27 |
| ignas | th1a: yes | 19:27 |
| th1a | OK. Screw it. | 19:27 |
| th1a | It won't kill you to see "Booked resources: Resource A" on Resource A's calendar. | 19:28 |
| Aiste | th1a: can I quote you on that? :DDD | 19:28 |
| Aiste | the 'Screw it' bit? | 19:28 |
| th1a | Well, whether or not ignas can screw Resource A depends on what Resource A is. | 19:28 |
| Aiste | :DDDD | 19:29 |
| th1a | Presumably A does not stand for Aiste. | 19:29 |
| Aiste | :DDDD | 19:29 |
| ignas | hu-mans are not resources :) | 19:30 |
| th1a | Good point. | 19:30 |
| Aiste | they are | 19:30 |
| Aiste | haven't you heard of HR? | 19:30 |
| th1a | Not in SchoolTool. | 19:30 |
| Aiste | :DD | 19:30 |
| Aiste | well, I'm not in school | 19:30 |
| Aiste | haven't been for a long time | 19:30 |
| th1a | You can't book a person. | 19:30 |
| th1a | Person. | 19:30 |
| th1a | In SchoolTool. | 19:30 |
| th1a | Anyhow, if that's the only cost, I think it is a reasonable move. | 19:31 |
| ignas | if users will want that data hidden they will know what they don't what to see better than we do anyway :) | 19:33 |
| povbot` | /svn/commits: * jinty committed revision 5969: | 19:56 |
| povbot` | /svn/commits: Make get_version a bit more OS independent and port it to i18nextract.py | 19:56 |
| povbot` | /svn/commits: * jinty committed revision 5970: | 20:12 |
| povbot` | /svn/commits: Change the schooltool release script configuration to test with the eggs branch. Also change the version number test to the new version.txt file. | 20:12 |
| *** thisfred has left #schooltool | 20:15 | |
| *** Aiste has quit IRC | 20:24 | |
| ignas | th1a: what is the semantic meaning of group timetables ? | 20:25 |
| ignas | because apparently one can add timetables to groups through restive interface | 20:26 |
| ignas | while not through the normal web interface | 20:27 |
| povbot` | /svn/commits: * jinty committed revision 5971: | 20:43 |
| povbot` | /svn/commits: Include the version.txt file in the zpkg metadata. | 20:43 |
| mgedmin | ignas: aren't group timetables automatically composited into the timetables of their members? | 20:45 |
| ignas | yes they are | 20:50 |
| ignas | but you can't create them through normal user accessible means | 20:50 |
| ignas | and you can't book resources for groups | 20:50 |
| ignas | 2 choices | 20:50 |
| ignas | 1. Dump group timetables in favour of Recurring Events | 20:51 |
| ignas | 2. Add resource booking and scheduling to Groups | 20:51 |
| ignas | because now i will have to add code that works around the fact that groups can't book resources while they can theoretically have timetables | 20:52 |
| *** Aiste has joined #schooltool | 21:14 | |
| *** jinty has quit IRC | 21:16 | |
| *** mgedmin has quit IRC | 21:20 | |
| *** ikonia has left #schooltool | 21:33 | |
| th1a | ignas: Still there? | 21:46 |
| ignas | yes | 21:46 |
| th1a | I don't think there should be group timetables. | 21:47 |
| th1a | I don't know what that would be either. | 21:47 |
| ignas | i see | 21:49 |
| th1a | There is, quite frankly, probably still some conceptual weirdness around timetables we've never completely straightened out. | 21:50 |
| th1a | Like this case. | 21:50 |
| ignas | well - clients should help us see what is really required and which excess flexibility should be slowly removed | 21:52 |
| th1a | Yes, some fresh eyes should be able to sort it out at some point. | 21:53 |
| *** ignas has quit IRC | 22:24 | |
| *** Joe_Violanti has joined #SchoolTool | 23:25 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!