Lets get started in another minute and have a small discussion to know whats happening and moving further with coming releases "releases", hmm mcrha, yup we have 2.28.1 and 29.1 coming this month * mcrha was hoping in the upcoming year forecast :) ;) lol step by step as we all know dbus calendar has been merged now yeah, one big step, then few small steps and i would like lakhil to play a major part in bringing the major bugs during every meeting and we can share the bugs among us assigning and making sure the issues are fixed before the release chen, i keep sharing in irc daily ... though i will try to prepare one for meeting * mcrha noticed flood of those yesterday prolly we can discuss over bugs like https://bugzilla.gnome.org/show_bug.cgi?id=557613 to ensure they are fixed on time lakhil, bring it to light and discussing it would make sure these go in before the release yeah, sure lakhil, would be great if you have a list before us during these meetings :) mcrha, and coming on patch reviews, know there are lot of ur patches waiting on the same actually, i changes a strategy slightly mcrha, can all the patches which are straight forward or if your confident on the fixes be committed directly ? and consult on the fixes where you have some doubt.. I attach patches for "test or review", if reporter can try the patch and says ok, then I commit chen, yup, i can do that, I was hoping in starting with that on January, though mcrha, oh why ? mcrha, prolly you can attach the patch marking it as committed right away just for fun of attaching patches to bugzilla. does it worth it? mcrha, and the left ones means that they are requiring some review comment mcrha, don think so 'don' ~~ don't? ok don't :) just clarifying a meaning. I do not think it worth it too, the commit ID should be enough there mcrha, i would say testing from the reporter is fine, but commit it if you feel the approach taken is correct mcrha, agree you know the code will be quite different when you allow me to commit without asking, right? mcrha, well we have all spent enough time to make a judgement whether the approach is right or wrong and of-course having a review is always better, but considering the ammount of people we have now we will not be able to follow the same style right, that's a bad thing (low human resources) mcrha, so if you have patches, which are on the above category commit them! i mean for the patches right now in the bugzilla as well * mcrha is wondering how chen means 'if' :) :D :D * chen leaves the rest to mcrha :) patches in bugzilla, I miss the user statistic page there mcrha, now it's added back haha and lakhil the points page :D lol all are back :D chen, I'll go the safe side, killing master only aah :D mcrha: lol lakhil, is the statistics page back? you the one who has to save the killing :D mcrha, ok, hold it on stable as well by ur judgement mcrha, yep lakhil, good, let me look how I stand for past few weeks ;) to update what i have been doing, chen, yeah, stable is a different story https://bugzilla.gnome.org/page.cgi?id=weekly-bug-summary.html committed the imapx initial stuff to master and cooked a patch for ebook issue perhaps feel it has to be combined with mcrha's patch on keeping open ebook's in memory mcrha, i felt that the open ebooks can be kept in memory somewhere so that all components in evo can access them mcrha, https://bugzilla.gnome.org/page.cgi?id=describeuser.html&login=mcrha redhat com :) mcrha, would that be good ? would have to start more on imapx/dbus and issues in master chen, with the actual concept, only shell would do that, and that shouldn't look on address books at all lakhil, I see :) abharath, what were u upto last week? chen: looking into the libmapi issue for now. before that the windows installers http://www.gnome.org/~pchen/bharath_windows_installers/ mcrha, should be possible atleast for mailer right? 2.28 maybe I'll make an installer for that by this weekend chen, yup, there's a patch for maler already, I updated it some time ago, on your request mcrha, keeping book's in memory just for one purpose may not be optimal isn it? mcrha, will go through it again and there's that bug on MAPI GAL which needs to be fixed now. I'll get you the bug details mcrha, somehow feel we really just open the book syncronously and so allocating the struct contents in heap is just a work-around mcrha, if the operation is not cancellable chen, they are there for two, one is for faces, other for image loading abharath, https://bugzilla.gnome.org/show_bug.cgi?id=595480 mcrha, need to look at traces more to see if threading should be done somewhere else abharath, fine chen, let's discuss that after the meeting, it's quite low in the code now chen: cool thanks abharath, let me know the bug on the build_cache and i can have a look at that since ur fully booked mcrha, sure chen: https://bugzilla.gnome.org/show_bug.cgi?id=595480 lakhil, anything to share? chen, hard time with master .. found many crashes due to calendar-dbus changes ...all are getting logged in bugzilla thanks to mcrha for his quick responses :) lakhil, with the white-board status ? * chen is yet to look into the bugs, have not looked into them last couple of days chen, http://tinyurl.com/yaeahsx thanks mcrha, anything to share? not much, I think. You probably noticed eex back in live, though some troubles arises, which are question for fix I know mcrha feels too bad when chen say words like anything and if, but he doesn't mean that :) :) lakhil, from next meeting would leave the floor to you while we start the meeting and we can pick up the issues abharath, :)) chen, :) ah don mean it in that sense :) am also little bit bad in english, maybe will improve it going further :) * lakhil wonders did chen watch DOn movie yesterday :P lakhil, don movie ? :) ah ok ok :) so any concerns from anyone ? please have a look at https://bugzilla.gnome.org/show_bug.cgi?id=594379 for imapx or irrespective of that :) lakhil, sure * mcrha is wondering who the Colin Walters is lakhil, how about imap keyword for these bugs ? chen, nope .. we have 90% bugs on imap :P ok :) mcrha: http://www.ohloh.net/accounts/colinwalters lets then catch up next week see you abharath, hmm, I see him here: https://bugzilla.gnome.org/page.cgi?id=weekly-bug-summary.html&days=300 mcrha: aah :) either I slowed down or he did it quite quickly :) haha He's still at Redhat I guess ;) so you know what to do :D why is it taking so long for the link to open up chen: bugzilla is down ;) chen, 300 days are 300 days :) lol so it seems I'll attach patches to bugzilla at least by the January evolution bug count is in green color ..wow :D * Now talking on #evolution-meet mbarnes|away, not having the meeting today as there not much people * mbarnes|away is now known as mbarnes * mbarnes is now known as mbarnes|afk * mbarnes|afk (~mbarnes c-24-147-161-46 hsd1 ma comcast net) has left #evolution-meet * Now talking on #evolution-meet * knirav (~knirav ecoprobe-dmz gns novell com) has joined #evolution-meet * You are now known as chen_tea * You are now known as chen * mcrha (~mcrha nat-pool-brq-t redhat com) has joined #evolution-meet * lakhil (~lakhil ecoprobe-dmz gns novell com) has joined #evolution-meet * jony (~jjohnny ecoprobe-dmz gns novell com) has joined #evolution-meet * abharath (~abharath ecoprobe-dmz gns novell com) has joined #evolution-meet Lets get started in another couple of minutes.. tick, tack, tick, tack, ... tick, tack... yup on :) There are couple of things which we would be discussing in the meeting today, 1) revised meeting timings 2) Frequency and agenda for the meetings Lets start with the 1st.. I was just thinking about a good overlap time for EST/IST/CET timezones, would 8-9 pm IST be a good one ? 3) blockers/bugs to be done which would be 3:30 PM for mcrha and 9:30 am for mbarnes|away (i guess) mcrha, yup, that would come under agenda discussion :) fine for me, that time I'm usually working chen, i am fine at 9 pm IST nice jony, abharath ? works for me too abharath, 8 or 9 ? :) 8 during winter, 9 during summer :) 9 pm IST mcrha: :D chen: sounds good . when you make it UTC, then the time shift makes changes (having trouble with wireless) mcrha, lol both remains same here :) not much change in climate during nights :) chen, I meant time shift during winter and summer. mcrha, when does the shift happen for u? chen, by the way, that doesn't sound much fair for you, in IST, havin it so late summer time, winter time, right? it's in the timezone info ;) mcrha, yeah mcrha, not a problem for us, its better to have it late evening than early morning :) chen: i'm fine with anything above 10 pm ist :) jony, cool chen, http://www.timeanddate.com/time/dst2009.html so shall we go with 9 pm IST ? * chen checks chen: i think mbarnes|away would have to give his opinion .. he wakes up very early for this. jony, had a word with him on monday and he was ok with having it one later than now, which should be 6:00 am for him but since our office shuttles starts after 1 1/2 hours from now, chen: oh oki. 6am is still too early for me :) that too winter time :D it wont be good for some of us to be in the meeting chen: cool. so if we get it any time around 7 PM IST it would suit everyone 7 PM is less than 10 PM for jony :) so meetings at wednesday's 9 PM from next week ok ? +1 * chen just wanted to see the +1's :) is it 9+1 or +1 like "yeah"? ;) mcrha, anything that says everyone are fine with it :) jony, abharath knirav ? chen: +1 chen, I'm fine, just give the time in UTC chen: sounds good to me :) 3:30 PM UTC mcrha: thanks :) ok done, will announce it in e-h later tonight after having a word with mbarnes|away moving on with the next, mbarnes|away, has a veto right ;) what shall we have as an agenda for weekly meetings ? a bug list from lakhil for the forth coming release would be good, and each one of us can assign bugs from that which we feel is important and discuss on that ? mcrha, what do u think? mcrha, jony, abharath lakhil ? some are just important, not by a feeling. But yes, I'm fine with that. * lakhil wants to give bug list which will have wish list + critical bugs :) hehe :) because wish list gives opportunity to try out something different :P lakhil, fine with it, lets try it and make changes based on how it goes.. sure I'm sure lakhil just wants to feel like a king ;) mcrha, that would include the blockers and ones critical for the release how many of them? giving link to a list of them? abharath, i am the one who is serving not ordering ;-) lakhil: :D with a link one might have an overlook what is going on with those, and whether anyone is on them mcrha, yes a link to them and we can go over them and we can assign them to us in the metting itself :) mcrha, sure .. i will give link also ok, sounds good so the plan is send the agenda for the meeting with the list of bugs on every monday.. and if in case we don have an agenda for a week, we can just meet to have a get together :) ah .. bug list should be sent fortnightly and meeting cancellations will be announced on monday if any when you send the list on monday, assign it on wednesday evening, when will you work on that? lakhil, yup fine mcrha, in the next couple of weeks.. I mean, the critical bugs should be fixed quite quickly... mcrha, ah yeah that would be for a release mcrha, yep .. that i share always on irc without waiting for meeting mcrha, would be good to mention a target milestone in the bug hmm, what will happen to the list from two weeks back? mcrha, if any bug is not fixed and, it needs to be, it will obviously remain on the new list as well so anyone who has it assigned to them will be able to answer about the same.. mcrha, lakhil should be able to maintain that :) so will we endup with a link to the full bugzilla after a year? ;) mcrha, lol mcrha, ah not all are blockers/critical ones :D mcrha, prolly we will know how it goes in a month :) * lakhil usually moves one without thinking about old bugs :P don need to wait for a year ;) mcrha, is it not ? ok, so lakhil will monitor newly added bug reports to eds/evo/eex/ema/gtkhtml and pick critical one to the list a) and then there will be a list b) of "nice to have based on users/... preference" both will be updated week by week (question mark)? lakhil, ? * chen is keen on the first than the second for begining period :) chen, mcrha i usually pick up the bugs which are ignored ... like i didn't pick even a single bug from kb regression as i thought those are taken care already if you want to pick from all of them .. then i will do the same * mcrha doesn't know what he wants :D better to have blockers/critical ones for the next releases first mcrha, i will catch you on irc as usual :D and once we get started, we can evolve it based on how it goes the only thing I noticed is that newly crashers might be relatively easily catch because of newly added changes in the code yup ok, so give a word to lakhil now? :) mcrha, on ? :) with a demo of bugs he has ready. I suppose he has some :) mcrha, maybe better to go on from next meeting! mcrha, or after the meet on #evolution ? :) up to you. I'm here one more thing - you people can let me by time to time if i am not picking right bugs ... /me needs feedback :) * chen does not want to rush lakhil today lakhil, sure!! be sure, lakhil, be sure though i have my small list always :P lol mcrha, who complains more .. will be given the opportunity to prepare bug list ... /me hides will summarize these and share in e-h list so that if any users/more devs wants to join, they can lakhil: :D * mcrha gave a little list of semi-known issues already, few days ago on the irc, might call it blockers for 2.30, maybe we might get some more people coming up with bugs, who knows :) understood sir (lakhil) chen: you know ;) abharath, :) mcrha, hehe :) starting with my work during last week, was working a bit on imapx, adding multiple namespace support and syncronizing folders - almost complete should be done by today chen, last week only? give us an overview since last meeting will get the code committed by tomorrow mcrha, when was the last meeting ? :) * chen is forgot :) yeah, that's the point :) mcrha, right and thats why we are discussing to have agenda and so :) yup, I agree * chen did not have much pace for sometime due to some reasons, but overcoming it now abharath, whats going on with mapi? chen: I'll put up a patch for that libmapi issue. Fix on evo-mapi should do it. Just started with looking into some Free/Busy stuff. would be onto some of Paul Smith's issues and then GAL :d abharath, upstream the fixes.. chen: yeah would do them this week jony, updates? abharath, cool knirav, anything to share? lakhil, updates? random testing on master, more stress on mapi testing , bug triaging .. that's all from my side and poking mcrha time to time :P chen: working on events .. would be pushing it to master on monday .. probably would do a screencast on it :) lakhil, nice :) jony, awesome!! mcrha, updates ? I probably didn't mention yet, thus doing now: I did commit few of mine pending patches in bugzilla to master, it'll either break something or will help. Will see. I'm attaching patches for review very rarely now, I usually commit right to the sources. You said I can, so I do. it's the biggest change in my workflow for few last weeks there are still quite many patches to be reviewed, though mcrha, yup a good change too. if u have any doubts on a patch, do attach them review.. mcrha, yeah just looking at that, would be good if we can separate out areas between us.. sure, but as I'm testing it, then it's partially safe to commit understand that there would be some part of code which each one of us might not know well enough to review, but with a small team we just have to take the responsibility there to understand and then review.. I tried to review few patches, but it's something I didn't growth for enough yet mcrha, so I will let u know the list am picking and we can share the others among each one of us * mcrha has a link for pending patches mcrha, so we will clearly have a boundary on who is responsible for what and would help to discuss in the meeting.. mcrha, shall we follow this approach ? abharath, jony lakhil ? there are only 60 unreviewed at the moment, not bad chen: okies mcrha, so divide based on components or a list ? nope, let me pastebin the link chen, I am fine with any approach as well as patch are getting committed in right time s/patch/patches http://pastebin.com/d659ddcd0 * chen looks at ti mcrha, http://tinyurl.com/ it's a good site for making short urls :) mcrha, am looking at having some responsibilities for future too.. mcrha, so if we have more patches coming in, we would know where most lie and who to ask for.. lakhil, yup, I guess the bugzilla itself can also save searches, but I'm not sure how it works chen, aren't patches usually random, what users like or not? mcrha, usually only some components get many patches mcrha, prolly we can discuss it over a mail, i can send the trend and we can decide on things, mail would give each one to think a bit.. mcrha, ok ? I do not know, but from my point of view the best approach would be to kill pending patches quite quickly, and then take care of newly added once in a week or two. I guess not many people are helping with evo code. though the above link is showing only unreviewed patches, those reviewed-waiting for clarification, aren't there mcrha, u know at some point we might all ignore it carrying on with coding, god knows. a concept of individual component maintainers was even thought for the same reason i suppose.. ? mcrha, maybe better to take it offline :) chen, yup, I understand. Might be good. just that long pending patches are most likely obsolete by something else or by code changes, so the initial "cleanup" is sort of crucial mcrha, yup agree * mcrha is seeing a clear volunteer for a cleanup ;) mcrha, will send out a mail today looking at the list * chen volunteers mcrha, so if I don do it by next week, kick me :) good. thanks. anything else to discuss? same as I told lakhil: be sure, chen, be sure :) lol no blocker bugs these week then? as for example the evo alarm notify doesn't work for me, it crashes lakhil, can u send them over to all of us by mail? it's a blocker for sure, as without it people will claim mcrha, what about assigning after lakhil sends? chen, sure .. no idea if this exact one is a bug already. Just I noticed and didn't care enough mcrha, master or stable ? i haven't seen any bug in bugzilla yet the trouble is that the locking around dbus calls is not helping there * chen remembers hearing it as master yup, master. mcrha, please file a bug and lakhil can test and add to the list and just yesterday I noticed, also on master, starting evolution the second time crashes e-addressbook-factory somewhere in gconf, but no evo code related, very strange ok, I'll do that. mcrha, cool I guess that's all. An hour passed so quickly :) mcrha, yeah :) lakhil, send over a mail :) chen, i will send in another half an hr We can again catch up next week with new timings :) lakhil, nice!! yup, just ping me before I get used to the new time mcrha, sure!! mcrha, abharath jony lakhil thanks all!! thank you :) * You are now known as chen|gym see you