[01:54] <newz2000> ooh, nice stuff
[08:59] <qense> hello
[09:05] <thorwil> hi
[10:01] <nand> qense: see that : https://wiki.ubuntu.com/identi.ca (and ctrl-f for "wanted")
[10:01] <qense> yes, I read the post to the maillist.
[10:03] <qense> I don't think it would be a good idea to use it for the website as main component. However, I think it would be a good way to show activity at the page to other people.
[10:05] <nand> damn, missed this one :)
[10:07] <nand> well, it can be interesting, but to be done once we have something workable
[10:07] <nand> I have no idea at all about the API, nor the use of microblogging services, never used them before
[10:11] <qense> I just use Twitter sometimes, but I've got no experience with microbloggin APIs.
[10:15] <nand> we'll have to see about the audience. Right now, the ubuntu account is all new, 3 suscribers :)
[10:15] <qense> It can wait
[10:15] <qense> I've created a view for a single task.
[10:16] <nand> cool!
[10:16] <nand> commited and pushed?
[10:16] <qense> not yet
[10:16] <qense> Now I'm working on a userdata model to get the data of several users to use them at the display of posts.
[10:16] <qense> I want to finish that first
[10:17] <nand> to get the data of several users  => for the job listings?
[10:17] <qense> yes
[10:17] <nand> why don't you use a LEFT JOIN ?
[10:17] <qense> that isn't a bad idea, but a separate model could be used again at other sections.
[10:19] <nand> of course, it can be useful for pages where there is one user only, but I don't recommend you to make a query for *each* users in the idea listing page.
[10:19] <qense> Of course not
[10:19] <qense> You pass an array of uids and an array of fiels you want to get
[10:20] <nand> why not... I'll be curious to look at your implementation
[10:21] <qense> When you commit locally it isn't pushed upstream right away, isn't it?
[10:42] <nand> qense: nop. You will have to "bzr push"
[10:42] <nand> and then the website at www-wanted will automatically update itself within the hour
[10:42] <qense> What will happen with the SQL file?
[10:44] <nand> since the wanted.install won't be executed, you will have to put on the SQL file all the necessary SQL to make wanted work. I.e. if you added a new table in wanted.install, put it also in the sql file
[10:48] <qense> Only the new queries in that file are executed?
[10:53] <qense> brb
[10:57] <qense> back
[10:59] <nand> yep
[10:59] <qense> nice
[11:00] <nand> and all that was present was deleted
[11:00] <qense> from the file or database?
[11:00] <nand> database
[11:02] <qense> Now I'm confused. It deletes everyt query you forget to remove from the file?
[11:05] <nand> ooh ok I was mixing with the devel branch of ideatorrent
[11:06] <nand> qense: here on this script, you will need to remove everything that was here (DROP table and such) and then add again the tables, plus the sample data
[11:06] <nand> the current version of the file is not good (shame on me) since it is not dropping the table at the beginning of the script
[11:07] <nand> The header of the update-db.sql file is pretty explanatory
[11:08] <qense> ok
[13:55] <qense> nand: about the names we use for jobs/roles/tasks: persia told me at the beginning of the idea for UW that we should watch for making it appear like you can do just one thing. Using the word 'job' could make it seem like it's fulltime, or at least that you're limited to just one thing. I think using 'task' instead of 'job' would make this clear to visitors.
[13:55] <qense> By the way, I pushed my changes.
[13:56] <qense> Another question, could you explain what you had in mind for the lenght and the meanings of the values of the fields in the database.
[13:57] <qense> I'm now working on the skills.
[14:00] <nand> qense: indeed, "task" sounds better. But for consistency stake, continue to use the word "job" in the code
[14:00] <qense> ok
[14:01] <qense> Bzr isn't that good yet in renaming, isn't it?
[14:01] <nand> you mean, file renaming?
[14:01] <qense> yes
[14:01] <qense> I've read something about it handling it badly.
[14:02] <nand> nup, I did some mass renaming some times ago, and it was all okay
[14:02] <nand> don't forget to use bzr mv instead of mv, that's all :)
[14:03] <nand> updating the website....
[14:03] <qense> ok
[14:03] <nand> NOTICE:  CREATE TABLE will create implicit sequence "wanted_job_skill_id_seq1" for serial column "wanted_job_skill.id"
[14:03] <nand> ERROR:  relation "wanted_job_skill" already exists
[14:03] <nand> NOTICE:  CREATE TABLE will create implicit sequence "wanted_job_skill_link_id_seq1" for serial column "wanted_job_skill_link.id"
[14:03] <nand> ERROR:  relation "wanted_job_skill_link" already exists
[14:03] <nand> NOTICE:  CREATE TABLE will create implicit sequence "wanted_wanted_job_id_seq1" for serial column "wanted_wanted_job.id"
[14:04] <nand> ERROR:  relation "wanted_wanted_job" already exists
[14:04] <qense> I didn't do a thing to the database!
[14:04] <nand> you didn't modified the update-db.sql to correct my mistakes? :)
[14:04] <qense> no
[14:04] <nand> I'll do it then
[14:04] <qense> oh, oops
[14:04] <qense> Now I get it
[14:04] <nand> http://ubuntu-wanted-devel.ideatorrent.org/
[14:05] <qense> I was too deep in the code when i asked I think
[14:05] <nand> website up, looking at your changes
[14:05] <nand> everything seems to be working good :)
[14:06] <qense> nice!
[14:06] <qense> Now I'm working on adding more detaisl
[14:06] <qense> What did you have in mind for the skills and lenght system? You already added some things for that.
[14:07] <nand> to be sure, do you understand the purpose of the wanted_job_skill_link table?
[14:08] <qense> yes
[14:08] <qense> I learned about that when trying Propel.
[14:08] <nand> It's a N-N liaison, so you have to have another table
[14:09] <nand> 2s, correcting one thing...
[14:09] <qense> ok
[14:13] <nand> qense: oook, pushed the corrected update-db.sql
[14:13] <qense> thanks!
[14:13] <nand> what I had in mind with the skills
[14:14]  * qense is running bzr update now
[14:14] <nand> is that for one given job, you can select several skills
[14:14] <nand> a job can require several skills
[14:14] <nand> then, the search engine will allow us to search by skill
[14:14] <qense> Are skill levels implemented?
[14:15] <nand> that is what I had in mind for the skill.
[14:15] <qense> nice
[14:15] <nand> ah, didn't though of that
[14:15] <nand> good idea
[14:15] <nand> hmmm
[14:15] <nand> in this case, a "level" field should be added in the wanted_job_skill_link table
[14:16] <qense> I can do that, I'm already starting to work on displaying skills.
[14:16] <nand> cool!
[14:16] <nand> concerning the lenght
[14:17] <nand> lengthtypeid integer DEFAULT -1,  -- None/Don't know (-1), Fixed length(1), Regular interval(2)
[14:17] <qense> Thanks
[14:17] <qense> I'm really a psql novice
[14:17] <nand> It can be none, a given one-time job, or a regular job every once in a while
[14:17] <nand> lengthvalueid integer DEFAULT 1, -- A few minutes (1), A few hours (2), Afew days (3), A few weeks (4), A few months (5), A few years (6)
[14:18] <nand> it describe the lenght of the job, when lengthtypeid = 1 or 2
[14:18] <nand> I don't think it's worthwhile to be too precise
[14:18] <qense> no
[14:18] <nand> lengthintervalid integer DEFAULT 1, -- Per hour (1), Per Day (2), Per week (3), Per month (4), Per year (5)
[14:19] <nand> This field is only for lengthtypeid = 2
[14:19] <nand> so that if we have lengthvalueid = 1 and lengthintervalid = 3, that will mean the job will require a few minutes every week
[14:20] <qense> Thanks!
[14:21] <qense> By the way, did you hear anything of the others?
[14:21] <nand> nup
[14:33] <qense> I've got these names for the experience:   skill_experience integer, -- Level of the skill: Beginner(1), Moderate(2), Expert(3)
[14:33] <qense> whoops, whole line
[14:33] <qense> anyway, I'm not happy with moderate
[14:33] <qense> but I've got no inspiration
[14:33] <qense> It doesn't fit with the other two. Someone here has got a suggestion?
[14:34] <nand> intermediate
[14:34] <qense> of course
[14:34] <qense> thx
[17:48] <qense> nand: A new commit has been made!
[17:49] <nand> qense: and website updated :)
[17:50] <qense> ok!
[17:50] <nand> eh, great!
[17:51] <nand> the links to the skills names does not work, normal I guess?
[17:52] <qense> yes
[17:52] <qense> I haven't created that part.
[17:52] <nand> well, I like the skill table
[17:53] <nand> Once filtering by skill and the submission part will be done, we'll beginning to get something usable :)
[17:53] <qense> yeah!
[17:54] <nand> hopefully that will boost the motivation of others contributors
[17:54] <qense> I hope so
[17:54] <nand> keeping the project alive means boosting motivation
[17:54] <qense> Do we already want to store applications in a table?
[17:55] <nand> for now (since we want to have something usable very quickly), I'd rather use a simple contact form like I do in the contributor page in brainstorm
[17:56] <nand> have you seen it?
[17:56] <qense> yes
[17:56] <qense> I even used it!
[17:56] <qense> I contacted the person that submitted the idea of a volunteer pool with that form.
[17:57] <nand> great to hear this feature is useful :)
[17:57] <nand> So that's the idea I have of application right now, if the poster allows it
[17:57] <qense> ok