The meeting log is attached to this e-mail. The following items were discuessed:
* Creating documents of how to implement the different parts * Assigning people to certain documents * What parts of Licq 2.0 are needed still * 1.3.5 Release (before summer?) We will have the meeting next week, Feb. 11th (Sunday) at 13:00GMT. Same time, same place. Anyone interested in Licq development may come. Jon -- ________________________________________________________ Jon Keating ICQ: 16325723 [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] http://www.licq.org GPG: 2290A71F http://www.thejon.org HOME: Minamiashigara, Japan
--- Log opened Sun Feb 04 21:59:53 2007 22:00 <@erijo> howdy all 22:00 <@emostar> hello 22:00 <@emostar> and it is now 13:00GMT on the dot, so let's get this started! 22:01 <@erijo> what's on the agenda? 22:01 <@emostar> So, first thing on the list ... not a big surprise but Licq 2.0 22:01 <@emostar> Basically, what needs to be done, and how we can get it done in a timely manner 22:02 <@emostar> It's been awhile since I've even touched the new code, so it will need a quick review when I start it up again 22:02 <@emostar> but where it is now, the main core of the plugin <-> daemon interaction is done 22:03 <@erijo> i've been doing some experimenting, trying out a clean start 22:03 <@emostar> what i was working on last was the LicqOwner class and how to get it working in a clean manner 22:03 <@emostar> hmm, what is wrong with the current code? 22:03 < Crazy_Hopper> erijo, I thought you were experimenting with boost in whole... 22:04 <@emostar> thats what i thought as well... 22:05 <@erijo> i wanted to test the event passing without all the extra stuff that's in licq atm 22:05 <@erijo> to have a clean core without icq etc. 22:05 <@emostar> ahh 22:06 <@erijo> and also to get a pure interface that plugins can use 22:06 <@erijo> currently, the include directory includes a lot of files that are private to the licq daemon 22:06 <@emostar> yes.. it may be best to try and separate it a bit 22:07 <@emostar> of course, i am accustomed to the files so i know which ones to ignore 22:07 <@erijo> and by make interfaces, i think it should be easier to unit test 22:07 <@erijo> s/make/making/ 22:07 <@emostar> the pluginfactory is not in the newapi branch, right? 22:08 <@erijo> no 22:08 <@emostar> i guess that is the plugin manager? 22:08 < Crazy_Hopper> speaking about plugins.. it seems to me that they should gain somewhat like 'priority'.. a queue in which they receive events... 22:08 <@erijo> that's another problem i have with the code i wrote in newapi. one class does to much 22:09 <@emostar> Crazy_Hopper: yes, that is in the current api :) 22:10 <@emostar> seperating the plugin handling and informatino is better 22:10 <@emostar> so, in other words, lets go with erijo's current way of Factory and Information classes 22:11 <@erijo> i was hoping to get a "core" up, that could load plugins, start them and then pass events around 22:12 <@emostar> there was a patch on licq-dev that accomplished that. but i didn't quite like some of the parts changed 22:13 <@emostar> one thing i'd like to do though.. is to have some simple documents describing what we are coding 22:13 <@emostar> and have that reviewed before we do the coding 22:13 <@emostar> of course it may require some coding to check on the details of things.. but it wouldn't be final code 22:13 <@emostar> (or even draft?) 22:14 <@emostar> the main reason i think it's a good idea is so we don't have to change/throw away code that we've spent time on 22:14 <@emostar> cuz that really sucks :( 22:14 <@erijo> it's just that it's more fun to write code than text ;) 22:15 <@emostar> yeah, definitely.. but easier to review and discuss a doc talking about what we are gonna do 22:15 <@emostar> because there are always many different ways to code what we are gonna do 22:15 < Crazy_Hopper> coding is good, but in team it is better to know what exactly your partner is workiing on... 22:15 <@erijo> agree 22:16 <@emostar> so, first thing is deciding what we will work on 22:16 <@emostar> i'll take the owner creation/loading (since i have some rought drafts already) 22:17 <@emostar> the plugin core has informatino already on the wiki 22:17 <@emostar> so maybe just update that with the latest factory separation 22:18 <@erijo> i have some other changes i would like to propose for the plugin core as well 22:18 <@emostar> also, maybe a doc about the life of a plugin 22:18 <@erijo> My life as a plugin :) 22:18 <@emostar> creation -> execution (events/info/etc) -> destruction 22:18 -!- wwp [EMAIL PROTECTED] has quit ["...---..."] 22:18 <@emostar> doesnt have to be an autobiography ;) 22:18 <@erijo> i'd like to work on that 22:18 <@emostar> alright, sounds good 22:19 <@emostar> ah, one other thing.. we shouldn't have long waits to review documents.. maybe just once a week send it to licq-dev to be reviewed 22:19 -!- wwp [EMAIL PROTECTED] has joined #licq 22:19 <@emostar> even if it is only a little bit.. perhaps a little bit is preferred to an overwhelming amount! 22:20 <@erijo> we should try to keep it on the wiki as well 22:20 <@emostar> yes, if you have net access when making the doc it is ideal 22:20 <@emostar> as for me.. I'll be using pen and paper then uploading it when i get access 22:20 <@erijo> perhaps just send the piece that changed during the week to licq-dev and keep the complete doc on the wiki 22:21 <@emostar> this month, i'm taking a different train, so I'll have an extra 1-2 hours of free time a day 22:21 <@emostar> yeah 22:21 -!- stephan2503_ [EMAIL PROTECTED] has quit [Read error: 104 (Connection reset by peer)] 22:22 <@emostar> with trac we can get the wiki diff right? 22:22 -!- stephan2503 [EMAIL PROTECTED] has joined #licq 22:22 <@erijo> yes 22:23 <@emostar> Just sending the diff link with a short overview is sufficient i think 22:23 -!- stephan2503 [EMAIL PROTECTED] has quit [Remote closed the connection] 22:24 <@erijo> actually, i think it's good to copy and paste the diff into the email. That makes it easier to read and quote 22:25 <@emostar> i just looked at the diff.. and it doesn't look like it is very readable as plain text.. 22:25 <@emostar> it uses colors to show what is different 22:26 <@erijo> better to copy the section you changed then 22:26 -!- stephan2503 [EMAIL PROTECTED] has joined #licq 22:26 <@emostar> yeah, well let's give it a try and see how it works 22:27 <@erijo> yep 22:27 <@erijo> btw, do you have any ideas on how to handle contacts? I'm thinking about some support for meta contacts 22:27 <@emostar> so, any other documents we want to work on this week? 22:28 <@emostar> yes, i had a similiar idea 22:28 <@erijo> the daemon would need to do translation between a meta contact and a real contact 22:29 <@emostar> hmm maybe my idea was a bit different 22:29 <@erijo> (btw, is it ok if we use contact instead of user? For me, user could mean both owner and contact) 22:29 <@emostar> i'm guessing there can be multiple meta contacts for one real contact? 22:29 <@erijo> i was thinking the other way around 22:29 <@emostar> sure, or just say LicqUser (as opposed to LicqOwner) 22:30 <@emostar> that way one contact can be linked across multiple protocols or multiple accounts within a protocol, right? 22:30 <@erijo> one icq contact, one msn contact => one meta contact 22:31 <@emostar> yeah, that would help out with organizing the list 22:32 <@erijo> but this means the daemon need to keep track of all contacts in a central database 22:32 < Crazy_Hopper> erijo: do you object this in whole? 22:33 <@emostar> yeah, which would be described in the doc 22:33 <@erijo> Crazy_Hopper: no, i think meta contacts are good. I'm just saying what needs to be done :) 22:34 < Crazy_Hopper> btw, is flynd around here? 22:34 < flynd> present 22:35 < Crazy_Hopper> i guess, we gonna need an ability to pick(select) multiple contacs in the UI.. is it something you can easily do? (both qt3/qt4) 22:36 <@emostar> erijo: if you have time in this week to make a document about meta users? if not, no hurry 22:37 <@emostar> Crazy_Hopper: it can be done, not sure how easily though 22:37 <@emostar> perhaps depends on your definition of "easily" ;) 22:38 < Crazy_Hopper> the purpose of it is... is to be able to do the same command for a whole group of contacts, not one-by-one. 22:38 <@erijo> i don't think i will have much time for licq this week, but i'll try to writing something down next week 22:38 <@emostar> alright, well first thing is the plugin api 22:38 < flynd> Crazy_Hopper: no, at least not easily as I'm not too familiar with the gui code yet 22:39 < Crazy_Hopper> ok, there is no rush, I'd just like to know if this task is sustained at all.. 22:40 < Crazy_Hopper> err s/task/idea/.... :-) 22:40 <@emostar> well, it can be done.. just how to do it is the difficult part 22:42 <@emostar> so, we have our tasks for Licq 2.0 22:42 <@emostar> for the week at least 22:42 <@erijo> to summarize: i'll write a document describing how plugins are loaded and started and how events are passed around 22:43 <@emostar> and I'll do one about LicqOwner and how a plugin loads an owner and creates them 22:43 <@erijo> great. Then on to 1.3.5? 22:44 <@emostar> yes, I'm getting abit tired though.. 22:44 <@erijo> we'll keep it short 22:45 < Crazy_Hopper> the issue with first MSN connection failure... 22:45 <@emostar> SSL issues? 22:45 < Crazy_Hopper> dunno... 22:45 <@emostar> what bug number? 22:45 < Crazy_Hopper> how could this be ivestigated? 22:46 < Crazy_Hopper> sec.. 22:46 < flynd> #1454 22:46 < Crazy_Hopper> http://trac.licq.org/ticket/1454 22:46 <@emostar> also #1445 is bugging me 22:46 <@emostar> i can't reproduce it 22:47 <@emostar> net is going at a crawl now... 22:47 < Crazy_Hopper> neither could I... 22:47 <@emostar> not sure how to debug it, other than playing around with it and looking at the openssl error in more detail 22:48 <@emostar> perhaps an openssl initiliazation issue 22:48 <@emostar> since it only happens the first time 22:48 <@erijo> i guess protocol errors are the most serious ones and the ones that needs to be resolved before 1.3.5 22:48 < Crazy_Hopper> erijo: which ones? 22:49 <@erijo> well, this msn error you are talking about and the icq 5.1 one 22:49 < flynd> I'm not sure but I think I've gotten the ssl mesrage twice a few times before msn goes online 22:50 < Crazy_Hopper> twice??? are you sure? had never seen it more than once... 22:50 <@emostar> same here 22:50 < Crazy_Hopper> pretty interesting.. 22:50 < flynd> no, I'm not sure, I get critical messages several times a day from msn so I loose count 22:51 < flynd> but I do know that sometimes it connects without any error on the first attempt 22:51 < Crazy_Hopper> rather rarely I guess.. 22:51 <@emostar> if i can get access to the uin/password of a users that experiences #1445, it will help me debug it 22:51 <@erijo> do we have any idea on when we would like to release 1.3.5? Before the summer, this year, ...? 22:51 < flynd> maybe failing to download a contact's picture should not be called "critical" 22:52 <@emostar> before summer is good. 22:52 < Crazy_Hopper> flynd: is it from msn? 22:52 < flynd> yes 22:53 <@emostar> i'm sorry, but i really do have to get going now 22:53 < Crazy_Hopper> ok, we all know what to work at, I guess.. 22:53 <@erijo> ok. I don't know if i can make it next week 22:54 <@emostar> I'm gonna look into #728, #782.. i vaguely remember how to fix it 22:54 <@emostar> alright, well just send updated documents to licq-dev then 22:55 <@emostar> and i think fixing #833 will fix #1445, so I will give that higher priority 22:55 <@erijo> yes 22:55 < Crazy_Hopper> btw, can trac/wiki notify on changes? 22:55 <@erijo> Crazy_Hopper: you can use rss 22:55 < Crazy_Hopper> hmm, indeed. 22:56 <@erijo> Crazy_Hopper: and tickets are of course sent to licq-tickets 22:57 <@emostar> alright, well I'll post the log before i go to bed, I'm gonna have to cut out now, but feel free to keep on discussing! 22:57 <@emostar> see you all later, and thanks for showing up 22:57 < Crazy_Hopper> bb! let the luck be with you! :-) 22:57 <@erijo> emostar: good night 22:58 <@emostar> night! 22:58 <@erijo> flynd: since you're the expert nowdays, in what shape is qt4-gui? 22:59 < flynd> erijo: stable and mostly working, but some features still neads to be fixed 22:59 < Crazy_Hopper> I think that the main issue with qt4, that has to be addressed as soon as possible, is the transparency... 23:00 <@erijo> Crazy_Hopper: it must be working rather well then, if transparency is the biggest issue :) 23:00 <@erijo> flynd: such as...? 23:00 < flynd> "some features" include the popup info from the contact list and the status menu seems to set wrong statuses 23:01 < flynd> main status can be set, but if I change status for just icq or msn I do net get the correct status 23:01 < Crazy_Hopper> you mean you don't get the correct status icon? 23:02 < Crazy_Hopper> or is it in network window? 23:03 < flynd> I don't get the correct status icon. Can't reproduce it now though as I'm working on fixing it =) 23:04 < Crazy_Hopper> I just tried to change msn status... I changed both statuses... :-) 23:05 < flynd> and of course there is still a lot of work to convert all the gui-code to use only qt4 (no qt3 compability classes)... some changes in qt require changes in the gui as well 23:06 < Crazy_Hopper> erijo: seems i was too quick with transparency... :-( 23:07 < flynd> the main contact list class probably needs to be rewritten to do itself what QListView did earlier 23:08 <@erijo> for 1.3.5 i think it would be acceptable to have a preview release of qt4-gui that uses qt3 compat. classes 23:08 <@erijo> as long as it works as it should 23:09 < Crazy_Hopper> hmm... i thought qt4 will be synchronized with licq2.0 23:10 < flynd> we'll see which of the qt4-gui and 1.3.5 that is ready enough first. I don't thikn you should throw away the qt3-gui too soon 23:10 <@erijo> not throw away, run in parallell 23:11 < flynd> I'm running with both GUIs all the time now ;-) 23:11 <@erijo> can you have both qt3 and qt4 running at the same time? 23:11 < Crazy_Hopper> frankly, I'm surprised that there is a difference in changing statuses code between qt3/qt4 guis 23:11 < flynd> yes, works great 23:12 < Crazy_Hopper> except for skins... 23:12 * erijo has to try that 23:12 < flynd> the anoying thing is that I get the msn critical errors popped up twice (one box for each gui) 23:13 < flynd> color names are different in qt3 and qt4 so skins look a bit different, but that can be fixed by using #rrggbb values for all colors =) 23:13 < Crazy_Hopper> hmm.. this functionality has to be moved over to msn plugin, but then it has to deal with gui... that's bad 23:14 < Crazy_Hopper> flynd: transparency.. :-))) 23:14 < flynd> and because they use the same config file, the last gui to save overwrites whatever the other gui wrote 23:15 < flynd> I'm not sure what you mean by transpareny. Should the entire contactlist be able to be transparent? I've never seen that in the qt3-gui either 23:16 < Crazy_Hopper> no... let me explain... 23:16 < Crazy_Hopper> i use thomas' skin. just try to load it yourself and you'll surely see what's wroing 23:17 < flynd> yes, I know that the contactlist i solid color when the skin background should be visible 23:18 < flynd> I thought you perhaps ment something else 23:18 < Crazy_Hopper> is it what I can call transparency then? 23:19 < flynd> yes, that is transparency. I was just thinging of the entire window =) 23:19 < flynd> thinking 23:19 < Crazy_Hopper> oh, I see.. 23:20 < Crazy_Hopper> then those squares in the corners will go when this transp... is done, right? 23:20 < flynd> but I think finding a way to make the contactlist in qt4 is the first step, then we'll see if the transparency problem is still there =) 23:21 < Crazy_Hopper> so you say qt4 has changed too much... 23:21 < flynd> either that or I just haven't found the right widget to use 23:22 < Crazy_Hopper> ok, seems I have to go now, my parents will get me buried alive soon. ;-) 23:23 < Crazy_Hopper> thank you guys. see you soon. 23:23 * Crazy_Hopper is away: I'm busy or may be just smoking... 23:23 < flynd> bya 23:23 < flynd> bye 23:23 <@erijo> bye 23:24 <@erijo> flynd: it's cool to run both qt3 and qt4 :) 23:24 < flynd> =) 23:25 < flynd> hmm... think I found a new problem. Enabling or disabling the column headers crashes the qt4-gui. I remember that working a week ago... 23:26 <@erijo> works here 23:28 < flynd> then it is just something going wrong due to the gui window being recreated as part of the config update. Probably my "fixed" status menu. Maybe I should work on it a bit more before committing =) 23:28 <@erijo> guess so :) 23:28 <@erijo> well, i need to go and get some work done. cu later 23:29 < flynd> work? it's sunday ;-) 23:31 <@erijo> i need to prepare for the presentation of my master thesis next monday 23:32 <@erijo> during the week, work takes all the energy :( 23:32 < flynd> ok, what's the thesis about? 23:34 <@erijo> remote programming of an pvr on an ip-tv set-top box using a mobile device 23:34 < flynd> sounds fun =) 23:37 <@erijo> it was, but now i'm getting a bit tired of it and just want it to be over :/ 23:37 < flynd> that definitly sounds like a thesis =) 23:37 <@erijo> so i better start working on it then :) 23:37 <@erijo> cu 23:37 < flynd> good luck 23:37 <@erijo> thanks --- Log closed Mon Feb 05 00:00:06 2007
