| *** alga has quit IRC | 02:07 | |
| *** alga has joined #schooltool | 02:29 | |
| *** alga has quit IRC | 02:59 | |
| *** dlobo has joined #schooltool | 03:27 | |
| *** dlobo has quit IRC | 03:49 | |
| *** dlobo has joined #schooltool | 05:32 | |
| *** dlobo has quit IRC | 06:17 | |
| *** dlobo has joined #schooltool | 07:20 | |
| *** alga has joined #schooltool | 09:14 | |
| *** povbot has joined #schooltool | 09:55 | |
| *** alga has joined #schooltool | 09:56 | |
| *** menesis has quit IRC | 10:29 | |
| *** menesis has joined #schooltool | 10:31 | |
| *** dlobo has quit IRC | 10:41 | |
| *** replaceafill has joined #schooltool | 11:24 | |
| *** lisppaste5 has quit IRC | 11:42 | |
| *** menesis has quit IRC | 12:31 | |
| *** menesis has joined #schooltool | 13:29 | |
| replaceafill | menesis, ping | 13:41 |
|---|---|---|
| menesis | replaceafill? | 13:42 |
| replaceafill | hi menesis, just a question | 13:42 |
| replaceafill | do you know what could be causing http://pastebin.com/2YELmKUr | 13:42 |
| replaceafill | a user sent me his paste.log | 13:42 |
| replaceafill | it's karmic btw | 13:43 |
| menesis | replaceafill: yes I know | 13:43 |
| menesis | I replied but you were not online at the time | 13:43 |
| replaceafill | :| | 13:43 |
| * replaceafill checks the logs | 13:43 | |
| menesis | There was a broken zope.security package for a few days | 13:43 |
| replaceafill | ah! | 13:44 |
| menesis | but I have uploaded a fixed version last week already | 13:44 |
| replaceafill | so, apt-get install python-zope.security | 13:44 |
| replaceafill | will do it? | 13:44 |
| menesis | yes | 13:44 |
| replaceafill | cool! i'll let him know | 13:44 |
| replaceafill | thanks menesis | 13:44 |
| *** jelkner has joined #schooltool | 14:46 | |
| *** ignas has joined #schooltool | 15:10 | |
| *** Aiste has joined #schooltool | 15:28 | |
| replaceafill | aelkner, ping | 15:35 |
| replaceafill | jelkner, ping | 15:35 |
| *** th1a has joined #schooltool | 15:45 | |
| *** yvl has joined #schooltool | 16:28 | |
| th1a | hi yvl, aelkner, replaceafill, menesis. | 16:30 |
| replaceafill | good morning/afternoon | 16:31 |
| yvl | hi guys | 16:31 |
| aelkner | morning | 16:31 |
| th1a | yvl: OK, where are we now? | 16:32 |
| yvl | well, I am sick :) | 16:32 |
| th1a | I figured. | 16:33 |
| replaceafill | yvl, :( | 16:33 |
| yvl | caught a rotovirus | 16:33 |
| yvl | will be fully available on Wed | 16:33 |
| yvl | so | 16:33 |
| yvl | the status is, as far as I know | 16:33 |
| yvl | we released trunks to Karmic | 16:33 |
| yvl | and we have most of the zope and something of schooltool released to Lucid | 16:34 |
| yvl | the Lucid release is broken at least on my home machine | 16:34 |
| yvl | but menesis has clearer status on that | 16:34 |
| yvl | well, at least it runs on python 2.6 | 16:34 |
| th1a | menesis? | 16:34 |
| th1a | Glad it at least works on the system Python. ;-) | 16:35 |
| th1a | ... | 16:36 |
| menesis | hi. | 16:36 |
| th1a | hi menesis. | 16:37 |
| th1a | Where are we with Lucid? | 16:37 |
| menesis | all zope packages are in Lucid PPA since last week | 16:37 |
| menesis | and I've uploaded all schooltool packages to Lucid PPA on Friday | 16:38 |
| th1a | aelkner: bug email from Chris in your inbox. | 16:38 |
| menesis | so SchoolTool is available on Lucid already | 16:38 |
| th1a | menesis: You need to be more communicative. | 16:38 |
| menesis | and it works. | 16:38 |
| th1a | also: Good work. | 16:39 |
| aelkner | th1a: do you agree with him? | 16:39 |
| th1a | I can't see it. | 16:39 |
| th1a | aelkner ^ | 16:39 |
| aelkner | i'll send you a screenshot | 16:39 |
| th1a | thanks. | 16:39 |
| th1a | menesis: Also, *please* coordinate with me before pushing changes to users. | 16:40 |
| th1a | We have to start doing that in a more predictable way from the user's point of view. | 16:40 |
| menesis | th1a: yes, sorry, saw your email | 16:41 |
| menesis | what I understood from last week's meeting was "do releases of what we have this week" | 16:41 |
| menesis | so I did | 16:41 |
| th1a | For example, aelkner pushed our trunk intervention changes to SLA without warning them and they've been pooping in their pants about it for a week. | 16:41 |
| menesis | managed to finish only by Friday | 16:41 |
| th1a | menesis: Yes, I probably wasn't clear. | 16:42 |
| menesis | everything apart from the new intervention release were bugfixes, I wanted to release that for a while already | 16:43 |
| th1a | I mean, when we get to this point, I'm probably always going to act like we should just push things out as quickly as possible. | 16:43 |
| th1a | But I really don't want that. | 16:43 |
| th1a | So... basically, I'm trying to tell you how to interpret my pronouncements. | 16:43 |
| menesis | well doing .tar.gz releases affects only those who are in this room so I will do that when asked | 16:44 |
| aelkner | it's not an exact science :) | 16:44 |
| menesis | releasing packages of that into Karmic is another matter, and I admit I haven't asked if it's ok to do that | 16:44 |
| yvl | th1a, I thought we were on the same page about this Karmic release | 16:44 |
| th1a | We were except for interventions. | 16:45 |
| menesis | but I have uploaded a few *hundreds* of packages to Karmic this year already. | 16:45 |
| th1a | And it isn't in practical terms a big deal. | 16:45 |
| th1a | I guess what I would have liked is an email with the release notes on Friday saying, "OK, this is what we're ready to push on Monday." | 16:46 |
| yvl | yes, I just thought you knew that interventions work is also going to be pushed - as an exception, not a general rule | 16:46 |
| th1a | And I would have said "Great, but lets hold back the interventions changes." | 16:46 |
| th1a | Well. | 16:46 |
| yvl | yes, that would be a nice protocol | 16:46 |
| menesis | th1a: okay I will warn before mailing announcements and uploading schooltool packages | 16:46 |
| th1a | ... | 16:46 |
| th1a | I'm saying I need to doublecheck myself as much as you. | 16:47 |
| menesis | th1a: also I would like the body part of the release notes to be written by you | 16:47 |
| menesis | because I do not always know what the important changes for users were | 16:47 |
| th1a | Yes... we just need be talking more in the lead up. | 16:48 |
| th1a | Communication is the issue. | 16:48 |
| th1a | I mean, I can follow what's going on in general via Launchpad, but we just need more specific preparation for release. | 16:49 |
| th1a | And not releasing on Friday. ;-) | 16:49 |
| menesis | further about pushing major changes to users -- karmic was an exception, we were not ready for this release, so it could not be considered stable | 16:50 |
| th1a | Yes. | 16:50 |
| yvl | that is true | 16:50 |
| menesis | from the point that Lucid is released, the 1.4 series is declared stable, and only bugfixes go into them | 16:51 |
| th1a | It is really just the Interventions part that freaked me out, in part since SLA has been freaking out. | 16:51 |
| *** alga has quit IRC | 16:51 | |
| th1a | I can do a better job of targeting bugs in Launchpad too, to indicate which ones are for the current release and which are only for the next release. | 16:52 |
| menesis | so I will have four releases to maintain from two branches: 1.0 for hardy and jaunty, and 1.4 for karmic and lucid. then trunk for development and maverick | 16:52 |
| th1a | I wasn't very conscious of the distinction. this time. | 16:52 |
| th1a | Hm. | 16:53 |
| th1a | I'd say only security bugs need to go into 1.0 at this point? | 16:53 |
| th1a | Strictly maintenance. | 16:53 |
| menesis | it is like that since long ago | 16:54 |
| th1a | I thought so. | 16:54 |
| menesis | there were a few releases with backported bugfixes | 16:55 |
| menesis | and for CanDo needs | 16:55 |
| th1a | And what I'm saying is that I'll be more focused about what really needs to be backported into 1.4. | 16:55 |
| th1a | That is, keep that more limited. | 16:55 |
| menesis | good | 16:56 |
| yvl | menesis, can you elaborate a bit more on current status in Lucid? | 16:57 |
| menesis | btw as I was preparing the release on Friday, I have updated all the release notes in the book. so you can see what was really released for any of the series | 16:57 |
| menesis | http://book.schooltool.org/htmlhelp/1.4-release-notes.html | 16:57 |
| th1a | menesis, Thanks! | 16:57 |
| menesis | http://book.schooltool.org/htmlhelp/1.0-release-notes.html | 16:57 |
| th1a | OK, following onto this, what do you guys think about going to UDS? | 17:00 |
| th1a | Brussels: 10-14 May 2010 | 17:00 |
| menesis | Now I'm trying to use blueprint for status https://blueprints.edge.launchpad.net/schooltool/+spec/schooltool-in-lucid | 17:00 |
| th1a | (that is, menesis & yvl) | 17:01 |
| th1a | For, say, two days. | 17:01 |
| th1a | The main reason not to go would just be if literally there'd literally be no useful work to be done there other than schmoozing. | 17:01 |
| menesis | yvl: everything is in the PPA. filing bugs for packages that are in Lucid but I'm not happy with. That's it. | 17:02 |
| th1a | LITERALLY. | 17:02 |
| menesis | UDS. | 17:02 |
| aelkner | th1a: why did you change my fix commited to in progress? i did commit the fix. i just isn't merged. | 17:02 |
| aelkner | it isn't merged | 17:02 |
| th1a | You told replaceafill you were still working on it. | 17:02 |
| replaceafill | that was a question of mine | 17:03 |
| replaceafill | do we change to Fix Committed until it lands on trunk? | 17:03 |
| th1a | To me, fix committed implies that it is publically available on a branch. | 17:03 |
| replaceafill | any branch? | 17:04 |
| menesis | replaceafill: change to Fix Committed when you commited a fix to a public branch | 17:04 |
| replaceafill | menesis, ah ok | 17:04 |
| menesis | yes | 17:04 |
| menesis | because then I know that a fix is available somewhere | 17:04 |
| th1a | Right. | 17:04 |
| replaceafill | oops, have to change some now :P | 17:04 |
| menesis | it helps if you link a branch to the bug | 17:05 |
| th1a | Committed to a private branch isn't helpful to the rest of us. | 17:05 |
| yvl | yes | 17:05 |
| yvl | it's not released | 17:05 |
| yvl | that's why it's not helpful ;) | 17:05 |
| menesis | then I can see where the fix is, is it merged, and look at the diff | 17:05 |
| aelkner | commited comes BEFORE released | 17:06 |
| menesis | in a couple clicks | 17:06 |
| aelkner | otherwise, what's the point of commited? | 17:06 |
| aelkner | i did comit changes | 17:06 |
| th1a | Committed means published to a public branch. | 17:06 |
| th1a | Merged means merged into trunk. | 17:06 |
| yvl | yes | 17:06 |
| aelkner | what do i do when i make a bug fix | 17:06 |
| th1a | Released means trunk converted to a release. | 17:06 |
| aelkner | what action in launchpad? | 17:06 |
| replaceafill | :O i didnt know there was a Merged | 17:07 |
| th1a | Is there? | 17:07 |
| yvl | (there is no Merged sadly) | 17:07 |
| th1a | Oops. | 17:07 |
| aelkner | there outhg to be | 17:07 |
| yvl | hence the confusion | 17:07 |
| menesis | th1a: I haven't though about UDS much, yet. Maybe I reply in email what I think we could do there | 17:07 |
| * yvl seconds | 17:07 | |
| th1a | menesis: Sure. Have you been to one? | 17:07 |
| aelkner | in progress is wrong becuase i'm done dong the work | 17:08 |
| aelkner | so what status should i set it to? | 17:08 |
| Lumiere | until it is committed to a public branch | 17:08 |
| Lumiere | it is in progress | 17:08 |
| Lumiere | because it isn't available to the development team | 17:09 |
| aelkner | Lumiere: please, let them answer | 17:09 |
| th1a | Perhaps part of the confusion is that Launchpad is really designed for one branch per bug. | 17:09 |
| aelkner | i am not going to do one branch per commit | 17:09 |
| * replaceafill feels guilty he put three bugs in the same branch | 17:09 | |
| menesis | "Merged" is a status of a merge proposal that is displayed below a branch linked to the bug | 17:09 |
| aelkner | that is huge waste of time | 17:09 |
| th1a | So in that model every time you finish a bug, you should have a branch to publish and link, and then you say "fix committed." | 17:09 |
| menesis | th1a: actually I have not been to any sprint | 17:10 |
| aelkner | that assumes that people are doing very little work pe onth | 17:10 |
| aelkner | it's not true for our efforts | 17:10 |
| th1a | If you want to do several bugs in one branch, then you don't switch to "fix committed" until you publish the collective branch. | 17:10 |
| replaceafill | th1a, got it | 17:10 |
| th1a | Basically, it is not designed as a productivity report. | 17:10 |
| th1a | It is designed so that you can announce to your collaborators that your work is available to them. | 17:11 |
| aelkner | i create new branches every couple of months | 17:11 |
| menesis | I've been in Europython when it was held in Vilnius, but haven't met many people or participated in sprints | 17:11 |
| aelkner | and commit to them during the week | 17:11 |
| th1a | menesis: Basically, UDS is different because it is mostly just people working. | 17:11 |
| aelkner | and then i propose merges every week or so | 17:11 |
| aelkner | menesis: you told me it was ok for me to work like this | 17:11 |
| aelkner | is not true? | 17:11 |
| yvl | ok, guys, calm down | 17:12 |
| replaceafill | :D | 17:12 |
| menesis | aelkner: it is ok | 17:12 |
| th1a | aelkner: I'm not so much telling you how you can work as how you should use that particular field in Launchpad. | 17:12 |
| menesis | one branch, many bugs | 17:12 |
| yvl | I'd say the rule of the thumb is: | 17:12 |
| aelkner | but if commit a fix to a bug, i want to be able to update launchpad to reflect that | 17:12 |
| aelkner | so i always say fix commited | 17:13 |
| aelkner | which is in fact the case | 17:13 |
| yvl | once you committed some bugfixes to a public branch in Launchpad, please change status to "Fix Committed" *AND* request the merge to respective trunks | 17:13 |
| replaceafill | yvl, got it | 17:13 |
| aelkner | ok, i can do both together | 17:13 |
| menesis | well the branch might not be ready to merge yet | 17:13 |
| aelkner | if i commit a bug to a vranch, i consider it ready for merge | 17:14 |
| aelkner | as lng as i make the merge request | 17:14 |
| *** dlobo has joined #schooltool | 17:14 | |
| th1a | I'd say the rule just should be "don't switch to 'fix committed' unless it is publically available, whether or not it is ready for merge. | 17:14 |
| menesis | I am totally happy by aelkner's use of Launchpad lately | 17:14 |
| yvl | yeah | 17:14 |
| replaceafill | if for instance, yvl says "you need to change what you did" in a fix commited, we just change it back to "in progress", correct? | 17:14 |
| th1a | Yes. | 17:15 |
| yvl | by the way, if you guys be so kind and always link a bug to a branch when setting to "Fix Committed".... | 17:15 |
| aelkner | th1a: are you saying i need to wait until it is merged to change it to fix comitted? | 17:15 |
| th1a | No. | 17:15 |
| th1a | I am saying it has to be *publically* committed. | 17:15 |
| aelkner | publicly available: what does that mean | 17:15 |
| yvl | other people can get that code | 17:15 |
| yvl | literally | 17:15 |
| th1a | It is available on a branch on LP, not just on your box. | 17:15 |
| th1a | You've pushed the changes. | 17:16 |
| aelkner | but it is, i don't change to fix commited unless i commit and push | 17:16 |
| aelkner | so why the in progress | 17:16 |
| * aelkner sighs | 17:16 | |
| menesis | in progress means "I am or will be working on that soon" | 17:17 |
| th1a | OK... | 17:17 |
| th1a | Here is what you wrote: "I didn't request the merge yet as I'm still changing it." | 17:17 |
| menesis | so that someone else does not work on the same bug as you | 17:17 |
| th1a | That's actually why I changed it. | 17:17 |
| aelkner | ok, fair enough, my coment was bad | 17:18 |
| aelkner | working n it | 17:18 |
| aelkner | i meant on the branch | 17:18 |
| aelkner | not the bug | 17:18 |
| aelkner | my bad | 17:18 |
| aelkner | i wanted to get pdf changes in before requesting the merge | 17:18 |
| aelkner | because i don't want menesis and yvl to have to merge new bugs each tme | 17:19 |
| th1a | So replaceafill was confused because he thought it should be in trunk already. | 17:19 |
| aelkner | when i'm going to be changing many things on one week | 17:19 |
| replaceafill | yes | 17:19 |
| aelkner | i prefer to wait before requesting the merge | 17:19 |
| th1a | So you should link to the branch when you commit the change. | 17:19 |
| th1a | Even if you don't yet request a merge. | 17:19 |
| menesis | aelkner: that's all very good :) | 17:20 |
| aelkner | i can try to remember to link to branches like i've been trying to be good about Changes.txt | 17:20 |
| th1a | Regarding 1 branch per bug: I'm saying that *LP is designed to be used that way* so if it seems like the design isn't quite fitting your use, that's why. | 17:20 |
| th1a | But it doesn't necessarily mean you have to change your work to fit that. | 17:20 |
| aelkner | it's ok, i'll link to branches in my bugs before changing to fix commited | 17:21 |
| aelkner | or while i mean | 17:21 |
| menesis | th1a: why do you think 1 branch per bug? | 17:21 |
| menesis | that's not true | 17:21 |
| th1a | I think the whole system makes the most sense that way. | 17:22 |
| menesis | 1 branch per bug makes no sense unless that bug is a big feature | 17:22 |
| menesis | I am very happy with Launchpad :) | 17:22 |
| th1a | We're all happy! | 17:23 |
| aelkner | i'm not complaining now that we agree on how to preceed | 17:23 |
| th1a | OK, regarding proceeding. | 17:23 |
| th1a | aelkner, Today, try to get vertical text going. | 17:24 |
| menesis | if you use `bzr commit --fixes lp:123456` then on the branch page all the bugs that are fixed in that branch are automatically listed and linked | 17:24 |
| th1a | Does anyone have any ideas about turning text 90 degrees in RML? | 17:24 |
| replaceafill | menesis, !!! | 17:24 |
| aelkner | menesis: cool | 17:24 |
| th1a | aelkner, is there anything about that in the RML reference? | 17:25 |
| th1a | I think there are some things you can do in ReportLab but not RML. | 17:25 |
| aelkner | yes, i haven't read the section yet, but i know it's there | 17:25 |
| yvl | I think you can turn pages... maybe frames | 17:25 |
| aelkner | i'll look at the docs right now | 17:26 |
| yvl | draw rotated text strings | 17:26 |
| th1a | OK. So work on that today. Tomorrow we should talk on the phone about transcripts. | 17:26 |
| th1a | We're going to work on putting data right into an .xls version of the crazy Philippine transcript we've got. | 17:27 |
| aelkner | ok | 17:27 |
| th1a | aelkner, You have skype, right? | 17:27 |
| aelkner | yeah, but skype sucks | 17:27 |
| aelkner | it's always filing from my experience | 17:28 |
| aelkner | but i could give it another try | 17:28 |
| th1a | Let's try that tomorrow because I don't want to hold the phone to my ear. | 17:28 |
| aelkner | ok | 17:28 |
| th1a | And I can't talk on the phone while sitting. | 17:28 |
| aelkner | don't you have headhones? | 17:28 |
| aelkner | headphones | 17:28 |
| aelkner | that's what i do | 17:29 |
| th1a | For my computer, not my phone. | 17:29 |
| aelkner | i have them for both | 17:29 |
| th1a | Well, you're cooler than me then. | 17:29 |
| aelkner | apparently :) | 17:29 |
| menesis | gtalk + pidgin or empathy should work like skype | 17:29 |
| aelkner | badly, you mean? | 17:29 |
| aelkner | :) | 17:30 |
| th1a | OK, let's try to get to replaceafill and wrap this up. | 17:30 |
| replaceafill | ok | 17:30 |
| menesis | it should work better, but I haven't tried :) | 17:30 |
| replaceafill | i have a few questions | 17:30 |
| replaceafill | yvl, the changes to the catalog were on your /dev branch, right? | 17:30 |
| replaceafill | i couldn't find them :( | 17:31 |
| yvl | lemme try to remember... | 17:31 |
| replaceafill | th1a, i sent an email requestion a translation for es_SV | 17:33 |
| replaceafill | *requesting | 17:33 |
| replaceafill | *translation template | 17:33 |
| th1a | OK... just reread that. | 17:35 |
| th1a | That sounds right to me... menesis? | 17:36 |
| replaceafill | th1a, if you want your eyes to burn http://schooltool.sugarlabs.org :) | 17:36 |
| th1a | One thing we could probably settle finally at UDS is the translation permissions on LP translations. | 17:37 |
| menesis | ? | 17:37 |
| th1a | Didn't we end up leaving them open? | 17:37 |
| menesis | cp es.po es_SV.po | 17:38 |
| menesis | and edit the file | 17:38 |
| menesis | but you want to use Launchpad Translations? | 17:38 |
| replaceafill | menesis, yes | 17:38 |
| replaceafill | so other people can work on them | 17:38 |
| menesis | btw es_CL has problems | 17:39 |
| yvl | replaceafill, I think I deleted the whole work on catalogs | 17:39 |
| yvl | as in permanently | 17:39 |
| replaceafill | yvl, :((( | 17:39 |
| replaceafill | yvl, but it was there!!! | 17:39 |
| replaceafill | and a few days later, gone!!! | 17:39 |
| yvl | yes | 17:39 |
| menesis | it is not exported or imported automatically like all other translations. don't remember and don't know why | 17:39 |
| th1a | yvl: We have this thing called a revision control system. | 17:39 |
| replaceafill | and i dont see removed files in the history | 17:39 |
| yvl | did you check out hte branch? | 17:39 |
| replaceafill | yes | 17:39 |
| yvl | th1a, there are ways to delete the branches too | 17:39 |
| yvl | ok | 17:39 |
| yvl | replaceafill, do you have the branch? | 17:40 |
| replaceafill | i have it but without your work | 17:40 |
| yvl | crap | 17:40 |
| yvl | that's it | 17:40 |
| th1a | I just needed to make someone other than aelkner the butt of my favorite joke. | 17:40 |
| replaceafill | you dont have it? | 17:40 |
| yvl | after release | 17:40 |
| yvl | I'm going to a vacation | 17:40 |
| aelkner | th1a: thanks for that | 17:41 |
| replaceafill | ok, th1a, enrollment statuses are only for students, correct? | 17:41 |
| replaceafill | i mean, we're displaying "Enrollment Status" as the name of the field? | 17:41 |
| replaceafill | or just "Status"? | 17:41 |
| replaceafill | Enrollment Status is way long | 17:42 |
| th1a | Status is fine. | 17:42 |
| replaceafill | I used: Pre-Enrolled, Enrolled and Post-Enrolled as values | 17:42 |
| th1a | OK. | 17:43 |
| replaceafill | yvl, that's another question of mine, is it ok to use: status = _("Enrolled") as a class attribute for BasicPerson? | 17:43 |
| replaceafill | i mean, it's a i18n messageid | 17:43 |
| yvl | I'd rather you didn;t | 17:44 |
| yvl | so, well, good news, people | 17:44 |
| replaceafill | you found it? | 17:44 |
| yvl | I nuked the work on catalogs | 17:44 |
| yvl | clear | 17:44 |
| replaceafill | damn! | 17:44 |
| replaceafill | yvl, was it when you merged trunk to your branch? | 17:45 |
| yvl | no | 17:45 |
| yvl | I nuked the branch on launchpad | 17:45 |
| yvl | then on my laptop | 17:45 |
| replaceafill | ah!! | 17:45 |
| yvl | then removed all saved diffs from work in progress | 17:45 |
| yvl | then checked out trunk | 17:45 |
| yvl | and replaced everything ;) | 17:46 |
| replaceafill | :((( | 17:46 |
| replaceafill | evolution to update the catalog? | 17:46 |
| menesis | something about catalog cache? | 17:46 |
| replaceafill | yes | 17:46 |
| replaceafill | menesis, you have it?!?! | 17:46 |
| menesis | I have looked at that branch on launchpad | 17:47 |
| menesis | but do not have a checkout of it | 17:47 |
| replaceafill | :( | 17:47 |
| menesis | it might be possible to fish out the lost branch from the shared repository | 17:48 |
| menesis | but I don't know how | 17:48 |
| replaceafill | ok, my last question | 17:50 |
| replaceafill | regarding ftests | 17:50 |
| replaceafill | and the SchoolTool skin | 17:50 |
| replaceafill | i mean, the old skin | 17:50 |
| replaceafill | yvl, i changed schooltool.app ftests to use the BasicPerson skin | 17:50 |
| replaceafill | a ftest there need to access the Courses and Groups viewlets | 17:51 |
| replaceafill | those break in the SchoolTool skin | 17:51 |
| replaceafill | since they need resource files available only in the BasicPerson skin | 17:51 |
| yvl | why did you change the test? | 17:51 |
| yvl | to use BasicPerson skin... | 17:52 |
| yvl | I'm just curious | 17:53 |
| yvl | wait | 17:53 |
| replaceafill | i used new resources for the person index.html view | 17:53 |
| yvl | I'm not entirely in working condition, so pardon me | 17:53 |
| yvl | still sick, you know | 17:53 |
| replaceafill | yvl, i understand | 17:53 |
| replaceafill | yvl, i'll better send an email with lots of questions, ok? | 17:54 |
| yvl | ok | 17:54 |
| replaceafill | and you reply when you feel better | 17:54 |
| yvl | ok | 17:54 |
| yvl | th1a, as for the rest of the week.... | 17:54 |
| yvl | I'll be fixing the damage I did the evening before I got sick | 17:54 |
| th1a | OK. | 17:55 |
| replaceafill | th1a, still bugging you on Statuses | 17:55 |
| replaceafill | could we use something like: | 17:55 |
| replaceafill | Pre-Active, Active, Post-Active? | 17:55 |
| replaceafill | so it can be used for everyone not only students? | 17:55 |
| th1a | Oh. | 17:56 |
| th1a | True. | 17:56 |
| th1a | Let's shift gears for a minute. | 17:56 |
| th1a | So statuses is not going to be in Lucid, right? | 17:56 |
| yvl | ok, guys, gotta go lay down. Happy coding :) | 17:57 |
| aelkner | yvl: feel better | 17:57 |
| yvl | statuses... probably not in lucid | 17:57 |
| th1a | OK. | 17:57 |
| th1a | Get well yvl. | 17:57 |
| yvl | thanks | 17:57 |
| replaceafill | th1a, we wanted to put the status field in the catalog | 17:57 |
| replaceafill | yvl, get well man | 17:57 |
| th1a | replaceafill: Sure. | 17:58 |
| replaceafill | so i'd say we should wait for yvl to recover and recover his catalog cache work | 17:58 |
| replaceafill | th1a, last thing on my list, reminding you guys of the crowd issue we found about a month ago | 17:59 |
| replaceafill | there's not a public bug for it | 17:59 |
| replaceafill | so it's easy to forget about it | 18:00 |
| th1a | Perhaps you should file one. | 18:00 |
| replaceafill | one without all the details, correct? | 18:00 |
| replaceafill | just as a reminder | 18:00 |
| th1a | You can mark bugs a security-related. | 18:01 |
| replaceafill | are they treated differently? | 18:01 |
| replaceafill | like private? | 18:01 |
| th1a | Yes. | 18:02 |
| replaceafill | i'll look into that | 18:02 |
| replaceafill | that's all from me | 18:02 |
| replaceafill | thanks gentlemen | 18:02 |
| th1a | OK... | 18:02 |
| th1a | officially, | 18:03 |
| * th1a drops the bag of gravel. | 18:03 | |
| th1a | Have a great week, gentlemen! | 18:03 |
| th1a | replaceafill: continuing... | 18:03 |
| th1a | Can we implement the UI for statuses such that you only see the basic statuses if you haven't created an equivalent extended one? | 18:04 |
| th1a | So that then it doesn't matter if we give them a weird abstract name? | 18:04 |
| Lumiere | security bugs | 18:04 |
| Lumiere | are only given to the person who submitted it | 18:05 |
| Lumiere | the security contacct | 18:05 |
| Lumiere | and the assigned person | 18:05 |
| replaceafill | Lumiere, :O | 18:05 |
| Lumiere | noone else can see them | 18:05 |
| replaceafill | they are the only ones that see the bug? | 18:05 |
| Lumiere | yes | 18:05 |
| Lumiere | until they're made public | 18:05 |
| replaceafill | cool, i'll file it and assign it to yvl :) | 18:06 |
| replaceafill | th1a, how do we know if they created an equivalent? | 18:06 |
| th1a | Um, look at the existing extended statuses? | 18:06 |
| replaceafill | by equivalent you mean "Enrolled" == "Enrolled" for their titles? | 18:07 |
| replaceafill | i'm confused in the "equivalent" part | 18:07 |
| th1a | I mean, if I'm a user, and I've defined an extended status as, I dunno, "foo." | 18:09 |
| th1a | Say I've got "foo," as a pre-active, "bar" as "active" "baz" as a post-active. | 18:09 |
| th1a | Right, because each extended enrollment state corresponds to a basic one? | 18:09 |
| replaceafill | !?!? | 18:10 |
| th1a | ? | 18:10 |
| replaceafill | i guess i'm lost here | 18:10 |
| replaceafill | ok, we have Pre-Active, Active and Post-Active as basic statuses | 18:11 |
| * th1a is now completely sure enrollment status won't be in Lucid... | 18:11 | |
| replaceafill | th1a, definetily :( | 18:11 |
| replaceafill | can you tell me about the "corresponds" part? | 18:11 |
| replaceafill | ah wait | 18:12 |
| replaceafill | i just saw the enrollment part in the extended ones!!! | 18:12 |
| replaceafill | you want the extended ones related to the basic ones!!! | 18:13 |
| replaceafill | so i define extended: "First Semester" associated with "Active" | 18:13 |
| replaceafill | "Getting Trained" associated with "Pre-Active" | 18:14 |
| replaceafill | "Dead" associated with "Post-Active" | 18:14 |
| replaceafill | th1a, something like that? | 18:14 |
| th1a | Yes. | 18:14 |
| th1a | Is that what you've done? | 18:14 |
| replaceafill | no, the extended ones are just objects containing titles | 18:15 |
| replaceafill | but i can put the reference to the basic one | 18:16 |
| th1a | Yes. | 18:16 |
| th1a | That's necessary. | 18:16 |
| replaceafill | when the user creates the extended one he's asked for "Title" and "Basic Status" | 18:16 |
| th1a | So what I'm saying -- and I don't think I thought of this before -- is that the user shouldn't have to see this as a hierarchy. | 18:18 |
| th1a | He shouldn't be constantly doing Basic > Extended status. | 18:18 |
| th1a | If there are extended statuses, he should just see them. | 18:18 |
| th1a | Does that make sense? | 18:19 |
| replaceafill | yes | 18:19 |
| replaceafill | by equivalent you meant a extended status pointing to a basic one | 18:19 |
| th1a | Yes. | 18:19 |
| replaceafill | if you have pointers to the basic one, the basic one is hidden | 18:20 |
| th1a | So if you don't really care about statuses, or if you manage to break your extended statuses, you'll see the basic ones. | 18:20 |
| th1a | Otherwise, you'll define a couple extended ones that make sense to you and never see the basic ones again. | 18:21 |
| th1a | Or... | 18:21 |
| th1a | Hm... | 18:21 |
| th1a | If you assign someone a basic one, then it has to be a filter option. | 18:21 |
| th1a | Well... | 18:21 |
| th1a | For *filtering* you probably need to see the basic ones. | 18:21 |
| th1a | For *assignment* I think it is safe to not show them. | 18:22 |
| th1a | See what I'm getting at? | 18:22 |
| replaceafill | filtering as in filtering in the gradebook, as in filtering in the journal, etc? correct? | 18:22 |
| replaceafill | assignment as in creating a person | 18:22 |
| th1a | aelkner: Can you send me that SLA screenshot? | 18:22 |
| th1a | Yes. | 18:23 |
| replaceafill | th1a, got it, will work on that | 18:23 |
| th1a | I'm just trying to make the form easier to use. | 18:24 |
| th1a | I mean, I may be overreacting. | 18:24 |
| th1a | It might be fine to just list the basic ones at the end of the menu. | 18:24 |
| th1a | That actually might be sufficient in terms of the views. | 18:24 |
| replaceafill | by menu, you mean a dropdown html element? | 18:25 |
| th1a | Just keep them out of the way. | 18:25 |
| th1a | Well, whatever list you're providing. | 18:25 |
| replaceafill | ah ok | 18:25 |
| th1a | We're not going to expect people to type them exactly every time. | 18:25 |
| replaceafill | th1a, a display like this: | 18:26 |
| replaceafill | In Training | 18:26 |
| replaceafill | First Semester | 18:26 |
| replaceafill | Second Semester | 18:26 |
| replaceafill | Dead | 18:26 |
| replaceafill | ---- | 18:26 |
| replaceafill | Pre-Active | 18:26 |
| replaceafill | Active | 18:26 |
| replaceafill | Post-Active | 18:26 |
| replaceafill | with the basics out of the way | 18:27 |
| th1a | Yeah. | 18:29 |
| th1a | I mean, that is probably gets us there without adding a bunch of logic which might confuse everyone anyhow. | 18:30 |
| replaceafill | i this understandable: | 18:31 |
| replaceafill | In Training | 18:31 |
| replaceafill | Active | 18:31 |
| replaceafill | Dead | 18:31 |
| replaceafill | ---- | 18:31 |
| replaceafill | Pre-Active | 18:31 |
| replaceafill | Post-Active | 18:31 |
| th1a | Let's not do that. | 18:31 |
| replaceafill | basic always in the same place | 18:31 |
| replaceafill | In Training | 18:31 |
| replaceafill | Dead | 18:31 |
| replaceafill | ---- | 18:31 |
| replaceafill | Pre-Active | 18:31 |
| replaceafill | Active | 18:31 |
| replaceafill | Post-Active | 18:31 |
| th1a | Yeah. | 18:32 |
| replaceafill | if the manager set a person "In Training" that automatically should change the basic status to Pre-Active, correct? | 18:32 |
| th1a | What we don't want is the user drilling through that as a hierarchy. | 18:33 |
| replaceafill | if the In Training is pointing to PreActive | 18:33 |
| th1a | Yes. | 18:33 |
| th1a | OK, so I assigned two bugs to you this morning, that you probably should do now, because they might need to go into the release. | 18:36 |
| th1a | replaceafill ^ | 18:36 |
| replaceafill | yes, i saw you set them to lucid | 18:36 |
| replaceafill | Security-related bugs are by default private (visible only to their direct subscribers). You may choose to publicly disclose this bug. | 18:37 |
| replaceafill | :O | 18:37 |
| th1a | Is there a standard pdf footer we're using? | 18:37 |
| replaceafill | i think so, the default page i guess | 18:37 |
| th1a | OK, just get the right Zonki in there, please. | 18:38 |
| th1a | And I guess we should stop people from creating new non-ascii usernames for the time being? | 18:39 |
| th1a | Until SchoolTool works with them? | 18:39 |
| replaceafill | yes, that's should be strongly tested before putting it to work | 18:39 |
| replaceafill | as menesis recommended in his last comment | 18:39 |
| replaceafill | <image tal:attributes=" | 18:41 |
| replaceafill | file string:${context/schooltool:app/@@absolute_url}/@@/schooltool-report-logo.png; | 18:41 |
| replaceafill | x view/footer/logo/x; | 18:41 |
| replaceafill | y view/footer/logo/y; | 18:41 |
| replaceafill | height view/footer/logo/height" | 18:41 |
| replaceafill | preserveAspectRatio="True" /> | 18:41 |
| th1a | Right, so in the meantime we should just filter that on creation? | 18:41 |
| replaceafill | hhmm we could do that | 18:41 |
| replaceafill | the personaddview | 18:41 |
| th1a | replaceafill, So just switch schooltool-report-logo.png to point to the right place. | 18:42 |
| replaceafill | th1a, yes | 18:42 |
| th1a | I guess we also need to check it on other import methods, too? | 18:42 |
| replaceafill | csv and xls? | 18:42 |
| th1a | Should we just raise an exception at the model level? | 18:43 |
| th1a | (and catch it in the views) | 18:43 |
| th1a | We're going to be making more importers soon, particularly for schools using non-ascii character sets... | 18:43 |
| th1a | (probably) | 18:43 |
| replaceafill | i guess the view is the place to put it | 18:44 |
| th1a | Don't we have to add it in multiple places, then? | 18:45 |
| replaceafill | we would have to change them to react anyway | 18:45 |
| th1a | OK. | 18:47 |
| replaceafill | we could use an invariant in the ibasicperson interface to react | 18:47 |
| replaceafill | i'll ask yvl :P | 18:48 |
| th1a | All right. | 18:48 |
| replaceafill | thanks th1a | 18:48 |
| th1a | So what's your timeframe on statuses? | 18:48 |
| replaceafill | i say it will take me a couple of days to adjust everything to what we just talked | 18:50 |
| replaceafill | i mean, the linking and the filtering | 18:51 |
| th1a | OK. | 18:51 |
| th1a | Also, I *really* need specific tasks for the El Salvador grant proposal. | 18:52 |
| th1a | VERY SOON. | 18:52 |
| replaceafill | th1a, yes i know | 18:52 |
| replaceafill | although during the weekend i checked schooltool.cambodia really close | 18:53 |
| th1a | OK. So you have enough to keep you busy a few days. ;-) | 18:53 |
| replaceafill | and i found that it could adjust well to our needs | 18:53 |
| th1a | Yes, your next job is to set up a demo instance for Cambodia, once you clear these tasks. | 18:53 |
| replaceafill | :| | 18:53 |
| replaceafill | th1a, http://docs.google.com/Doc?docid=0Ade78VyWm8bnZGR2bWp4NzZfM2ZzbXdia2Ru | 18:55 |
| replaceafill | sorry that is in spanish | 18:55 |
| replaceafill | but in the last part | 18:55 |
| replaceafill | there's the "Courses" | 18:55 |
| replaceafill | it all match cambodia | 18:56 |
| replaceafill | *matches | 18:56 |
| th1a | There are standard courses in El Salvador? | 18:56 |
| replaceafill | yes | 18:56 |
| replaceafill | some schools teach their own courses | 18:57 |
| replaceafill | but they have to teach those | 18:57 |
| replaceafill | we use Grades and Classes the same way Cambodia does | 18:57 |
| th1a | OK. | 18:58 |
| replaceafill | and for importing for the first school, i took one of their XLS and spit our import XLS format | 18:58 |
| replaceafill | and it worked | 18:59 |
| th1a | One would hope. ;-) | 18:59 |
| * th1a goes to take a shower. | 19:06 | |
| *** Aiste has quit IRC | 19:11 | |
| th1a | replaceafill: SInce that's already a security bug, perhaps you could actually describe it in the bug. ;-) | 19:12 |
| replaceafill | i wasnt sure it was going to behave as it did :P | 19:13 |
| replaceafill | now i can edit it ;) | 19:13 |
| th1a | ok, I'm really going to take a shower now. | 19:17 |
| replaceafill | :) | 19:17 |
| *** ignas has quit IRC | 19:33 | |
| *** lisppaste5 has joined #schooltool | 19:47 | |
| *** dlobo has quit IRC | 19:50 | |
| *** menesis has quit IRC | 19:57 | |
| *** yvl has quit IRC | 20:14 | |
| *** dlobo has joined #schooltool | 20:28 | |
| * replaceafill would like ST to have bool demographic fields :) | 20:41 | |
| *** dlobo has quit IRC | 20:47 | |
| *** replaceafill has quit IRC | 20:56 | |
| *** replaceafill has joined #schooltool | 21:21 | |
| *** dlobo has joined #schooltool | 21:36 | |
| *** menesis has joined #schooltool | 21:57 | |
| *** replaceafill has quit IRC | 22:01 | |
| *** ignas has joined #schooltool | 22:59 | |
| *** dlobo has quit IRC | 23:17 | |
| *** replaceafill has joined #schooltool | 23:25 | |
| *** alga has joined #schooltool | 23:26 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!