IRC log for #melange on 20081013

15:04.49*** join/#melange ibot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt)
15:04.49*** topic/#melange is Want to make Summer of Code and the Highly Open Participation Contest better? Melange is the next generation GSoC and GHOP web app - Code and more at http://code.google.com/p/soc/ - Want to contribute? Start here: http://code.google.com/p/soc/wiki/GettingStarted - Most especially, feel the love!
15:04.56TimRiker~save
15:04.56ibotsaved user and chan files
15:05.20SRabbelierTimRiker: I hear you're our log guy? :D
15:05.20TimRikerlh: bot addeded. sorry I didn't get online much yesterday. :)
15:05.27lhTimRiker: you rock, dude.
15:05.33lhhands TimRikera laurel wreath
15:05.36lhhrm
15:05.37TimRikerlh: got a couple shirts in the mail though, thx! :)
15:05.40lha laurel wreath even
15:05.41lhrock!
15:05.46lhloves the swag love
15:05.49TimRiker~wreath lh
15:05.50ibotACTION hands lh a laurel wreath and nods in gratitude.
15:05.50lhTimRiker: many many thanks
15:05.59lhi love ibot
15:06.01lh:)
15:06.14TimRiker~logs
15:06.15ibotAll conversations are logged to http://ibot.rikers.org/channel, where "channel" is replaced by the URL-encoded channel name, such as %23freenode for #freenode. Lines starting with spaces are not logged.
15:06.16lhokay folks, we now have perma logging thanks to mr. riker
15:06.44lhfolks one sec someone at my desk
15:06.48_Allen_TimRiker: wreath
15:06.50lhplease talk about pawel's mail
15:06.51lh:)
15:07.45SRabbelierI'm not sure what the 'apple' is doing in there :P
15:07.48tlarsenIt is fabulous.  It touched a deep part of me.  :)
15:07.50TimRikerif you're not familiar with ibot... /msg ibot help   is a good place to start.
15:08.24SRabbelierbut it looks good :)
15:09.35TimRikerwhat's with tpb? that bot is messaging me with error lines.
15:09.50SRabbelierTimRiker: what's it saying?
15:09.58_Allen_10 minutes left before the electric power off
15:10.03TimRiker<tpb> Error: "where" is not a valid command.
15:10.06SRabbelier_Allen_: oh?
15:10.23_Allen_SRabbelier: it's 23:10 in my country now
15:10.37SRabbelier_Allen_: the power goes of at 23:20?
15:10.51_Allen_SRabbelier: exactly at 23:30
15:11.01SRabbelier_Allen_: the power jsut goes off?
15:11.30_Allen_SRabbelier: power cut
15:11.38SRabbelier_Allen_: how come?
15:12.02_Allen_SRabbelier: it is the rule of my school
15:12.16SRabbelier_Allen_: lol... ok :P
15:12.47_Allen_SRabbelier: so this is another discussion?
15:12.51*** join/#melange madrazr (n=madhu@59.96.202.123)
15:13.06SRabbelier_Allen_: uhm, we're gonna talk about the demo now
15:13.35_Allen_SRabbelier: sorry that I can not participate
15:13.36tlarsenI think we need to get the Question/Answer/Questionnaire/Response stuff done before the summit.
15:13.53SRabbeliertlarsen: is there a lot of specific logic for those?
15:13.59tlarsenlh: the Terms of Service, Organization applications, etc. are implemented in terms of this.
15:14.05tlarsenNo, here is the plan:
15:14.36tlarsenIn the (Site/Sponsor/Organization) Settings, you can:
15:14.38tlarsen1)  pick a Questionnaire that has already been created.
15:15.28tlarsen2) within that Questionnaire, pick the question that represents the "I agree" question
15:15.28SRabbeliertlarsen: similar to how in SiteSetting a Document is selected?
15:15.40lhTimRiker: thank you for the help hint
15:15.42tlarsen3) within that Question, select the "I agree" affirmative answer
15:15.49tlarsenSRabbelier:
15:15.51tlarsenSRabbelier: Yes.
15:15.56lh_Allen_: will you be online later?
15:16.09tlarsenThe Settings entity would store three things:
15:16.18tlarsen1) ReferenceProperty to the selected Questionnaire
15:16.37_Allen_lh: 9 hours later
15:16.48tlarsen2) StringProperty of the "I agree" Question short_name, or maybe even a ReferenceProperty to the Question entity
15:16.49_Allen_lh: sorry that I need off now
15:17.04SRabbelier_Allen_: will see you later then
15:17.13lh_Allen_: we have another meeting in 8 hrs - i can push it back if you want to participate
15:17.15tlarsen3) something to record what the "I agree" answer value needs to be
15:17.18lh_Allen_: no problem
15:17.25lhis happy to do the demo at the summit btw
15:17.43tlarsenSRabbelier: I am going to commit drafts of the Question, Answer, Questionnaire, and Response Models today.
15:17.54_Allen_lh: that's good
15:18.00SRabbeliertlarsen: I was just reading that mail :)
15:18.01tlarsenSRabbelier: I had them very fleshed out at one point, but I lost the code somehow, so I will have to re-write it.
15:18.03lh_Allen_: will do.
15:18.21tlarsenSRabbelier: I will then create issues in the issue tracker describing these pieces.
15:18.38SRabbeliertlarsen: ok, sounds good; you're meaning just the model and logic code, no view code yet?
15:18.50tlarsenSRabbelier: actually, I only had the Models.
15:18.53_Allen_lh: also feel free to hold that before I come back, I can see the log
15:18.57tlarsenSRabbelier: I will commit something today.
15:19.01SRabbeliertlarsen: ok, that's np :)
15:19.08_Allen_lh: hold --> start
15:19.11tlarsenSRabbelier: the required logic was going to be described in a series of issues.
15:19.22tlarsenSRabbelier: A UI is needed as well, to:
15:19.23lh_Allen_: okay, but that's an hour before you are back, we will wait for you
15:19.23lh:)
15:19.26SRabbeliertlarsen: ok, makes sense; would be good for _Allen_ to work on
15:19.33tlarsen1) create Questions
15:19.44tlarsen2) create Questionnaires that combine a series of Questions
15:20.12_Allen_lh: ok, :)
15:20.17_Allen_see u guys
15:20.19tlarsen3) let users create Responses containing specific Answers to the Questions in a given Questionnaire
15:20.23*** part/#melange _Allen_ (n=user@218.27.64.127)
15:20.29SRabbeliertlarsen: how much different from soc.logic.models.questionaires.getOrInsertFromFields... would the create part be?
15:20.40SRabbeliertlarsen: is there a lot of additional stuff needeD?
15:20.52tlarsenSRabbelier: You'll have to wait and see the Model :)
15:20.59SRabbeliertlarsen: ok, will wait for that :)
15:21.15tlarsenSRabbelier: A lot of the fields are *not* required, since the Question Model supports many types of questions.
15:21.35tlarsenSRabbelier: Now that we have inheritance via PolyModel, I'm thinking about having a small hierarchy.
15:21.50tlarsenSRabbelier: That wasn't available to me before, and the Question Model got unnecessarily complex.
15:21.56SRabbeliertlarsen: the Questions will be stored in teh Questionairy in a ListProperty?
15:22.15lhTimRiker: when will the melange logs show up at ibot.rikers.org?
15:22.36tlarsenSRabbelier: No, in a many-to-many relation between Question and Questionnaire.
15:22.54SRabbeliertlarsen: ok, so a question can appear in multiple questionaires?
15:22.58tlarsenQuestions can be reused in other Questionnaires.
15:23.24SRabbeliernods
15:23.31SRabbelierok, makes sense
15:23.40SRabbelierso we'll have a 'list questions' view etc.?
15:23.59lhplease make sure to build this so that hosts can easily add/remove questions for questionairres
15:24.07lhi dont want to bug devs for this every time
15:24.32SRabbelierlh: that's easy to do with a many-to-many relation :)
15:24.33tlarsenlh: It is completely run-time dynamic.
15:24.43tlarsenlh: That is why it is so complicated to describe.
15:25.04tlarsenlh: We couldn't possibly have something like Melange work with code changes being required to change or create Questionnaires.
15:25.25tlarsenlh: They will be a sort of Document (Work, actually) that can be created on-the-fly.
15:25.27lhtlarsen: that's very very good
15:26.12tlarsenUgh, I have 45 emails related to Melange that I still haven't answered, despite reading my emails on the trail.  :(
15:26.42SRabbeliertlarsen: I'm looking forward  to your reviews :)
15:26.56SRabbelierI managed to get all but the 'edit' part working generic
15:26.58SRabbelier(for Sponsors)
15:27.07SRabbelierand I haven't got edit workign cos I didnt' have time to start on that yet :P
15:33.17lhahem
15:33.21lhconversation has stopped
15:33.25lhlets keep it going here folks
15:33.48SRabbelieris not sure what to discuss atm :)
15:33.51durin42sorry, I vanished because of random bugs I wrote two weeks ago.
15:34.00durin42Did I miss anything I should have paid attention to?
15:34.02lhdurin42: no worries. any time to look at the test suite?
15:34.04lhdurin42: no you were fine.
15:34.11durin42lh: on the agenda for tonight
15:34.13lhSRabbelier: how much work is left on the sponsors area
15:34.16lhdurin42: awesome. :)
15:34.19lhthank you!
15:34.24SRabbelierlh: for the refactored view stuff?
15:34.28lhSRabbelier: yes
15:34.35durin42lh: with the MBP in the shop, I can't do hgsubversion stuff as well
15:34.39SRabbelierlh: I think about an hour of work at most
15:34.54lhdurin42: MBP?
15:34.58tlarsenprefers email threads for stuff like this, rather than IRC
15:35.06lhSRabbelier: ok cool
15:35.17durin42lh: MacBook Pro, aka 'a steev'
15:35.19SRabbelierlh: the concept is up for review though
15:35.21lhtlarsen: i know, but some people prefer this way. we will do both to make sure we have effective logs and discussions
15:35.23lhdurin42: understood
15:35.30lhSRabbelier: what do you mean by concept up for review?
15:35.49SRabbelierlh: the 1602 codereview
15:35.54tlarsenlh: For me, it is like 10 conversations going on at once, very hard to follow.
15:35.56SRabbelierlh: it's "pseudo code"
15:36.02tlarsenlh: I guess I will just read the logs later.
15:36.06TimRikerlh: logs run nightly, so tomorrow.
15:36.25lhtlarsen: is it going by too fast for you?
15:36.27lhTimRiker: thank you
15:36.27lh:)
15:36.29tlarsenTimRiker: I can read the back-scroll in my own client, but thanks.
15:36.35lhSRabbelier: checking code review
15:36.41SRabbelierlh: -nod-
15:36.51lhtlarsen: it also logs online forever and ever and stuff. ++
15:36.56tlarsenlh: No, it is just that no one has the floor and three different conversations are intertwined.
15:37.01SRabbelierlh: the views/model/sponsor.py module will get smaller as we make the django templates more generic
15:37.11lhand has some other features that i dont understand but that sound really good
15:37.17lhtlarsen: i see.
15:37.19lhok
15:37.21lhserializing
15:37.32lhdurin42: you have test suites. anything else on your mind?
15:37.37lheveryone, durin42 has the floor
15:37.47tlarsenlh: it is just as annoying as when three separate conversations are going on in the same face-to-face meeting room.  :)
15:38.05*** join/#melange solydzajs (n=ps@156.17.48.51)
15:38.10lhtlarsen: it's the way of the open source team. and we are now both talking over durin42 too. :)
15:38.10durin42I'm going to look into various nose plugins for handling GAE stuff
15:38.17solydzajshi all
15:38.19lhdurin42: cool.
15:38.20solydzajssorry for being late
15:38.21durin42from what I've seen, they all have elements of suck
15:38.28durin42so I'll probably just write something basic we can use
15:38.29lhsolydzajs: hey. durin42 is updating us right now.
15:38.35SRabbelierdurin42: that would be good, seems like GAE has some particularities that need dealing with for testing
15:38.36lhdurin42: cool. what does this do exactly?
15:38.59durin42lh: makes it possible for people to write tests of the actual views and utility functions
15:39.20lhdurin42: very good, thanks for the explanation.
15:39.26lhdurin42: anything else on your mind?
15:39.44durin42Not really.
15:39.47solydzajsdurin42: I was also looking into pymox for mocking
15:40.32SRabbeliersolydzajs: yeah, that might be usefull with the django stuff
15:40.41durin42solydzajs: To be perfectly honest, I find a "real" mocking library superfluous with Python
15:40.57lhok you two get two minutes to talk about testing
15:41.04lhthen we are going to ask SRabbelier to update on what he's up to
15:41.07lhthen solydzajs
15:41.13SRabbeliernods
15:41.23lhtlarsen has asked that we continue discussing the demo on list, so we will honor that request
15:41.35durin42I'd rather keep our deps down, and I don't see what pymox gets us.
15:41.47tlarsenI have to agree with durin42 here.
15:41.47solydzajsdurin42: ;-) there is some project for using nose with appengine already
15:41.49solydzajsdurin42: http://code.google.com/p/nose-gae/
15:41.50tpbTitle: nose-gae - Google Code (at code.google.com)
15:42.01tlarsenIt is so easy to mock even existing classes in Python.
15:42.09durin42solydzajs: I know, but I don't know if JP and Kumar are maintaining it
15:42.40durin42(I work with the guys that wrote that, the problem as I see it is that we'd have to install it globally)
15:42.40solydzajsdurin42: probably not :-)
15:43.05durin42Thus me looking into just having a 't.py' or something that sets up the environment and then calls nose's test runner
15:43.58SRabbelierdurin42: if it's only a simple file?
15:44.04tlarsendurin42: Ummm, t.py?
15:44.20tlarsendurin42: A more descriptive file name, perhaps?  :)
15:44.22durin42tlarsen: or runtests.py or whatever
15:44.39durin42I'm working over a 1.5 second typing lag here, so cut me a bit of slack ;)
15:45.25durin42Anywho, that's the state of automated testing. With any luck, we'll have a usable testing framework by the end of the week.
15:45.26solydzajsdurin42: btw did you see the link I sent to the group about testing recipe ?
15:45.46durin42solydzajs: I did, but have not looked at it. I've been knee deep in subversion ctypes stuff until today or so.
15:45.56solydzajsdurin42: oh ok :-)
15:46.09durin42I'll be starting on this stuff around dinnertime for people in Chicago.
15:46.22lhhave we talked about testing enough? looks like we have.....
15:46.44durin42I think so.
15:47.27solydzajsyep
15:48.50lhokay next
15:48.54lhSRabbelier: what's on your mind?
15:49.10SRabbelierdid everybody have a look at, or at least see http://codereviews.googleopensourceprograms.com/1602 ?
15:49.12tpb<http://ln-s.net/2KTD> (at codereviews.googleopensourceprograms.com)
15:49.34lhlooks at sverre's code review
15:50.09lhSRabbelier: do you need people to review and comment before proceeding?
15:50.22solydzajsSRabbelier: yes I did, but didn't have time to review yet
15:50.25SRabbelierlh: well, I can finish it up to actual working code
15:50.29tlarsenlh: for some things, YES.
15:50.40SRabbelierlh: but before I start refactoring more modules I'd like it to be reviewed
15:50.40tlarsenlh: For major new things, we need to discuss things.
15:50.50tlarsenlh: Also, SRabbelier I believe indicated that this was speculative.
15:51.05SRabbeliertlarsen: speculative?
15:51.14SRabbelieris not sure what that means :$
15:51.22tlarsenSRabbelier: OK, maybe not that particular review.
15:51.34lhspeculative means that it is not necessarily what you want to do, it is just an idea
15:51.36lhokay, so
15:51.43lhtlarsen: do you want to review and comment on 1602 now?
15:51.45SRabbelierok, -nods-
15:52.02SRabbeliertlarsen: 1602 is what I think would be good, but I'm open for suggestions on how to do it better
15:52.02tlarsenlh: During this meeting?  I don't think that is a good idea.
15:52.08tlarsenlh: You can't just mandate a code review.
15:52.19tlarsenlh: We aren't going to pair-program over IRC, sorry.
15:52.25SRabbeliertlarsen: for example the I'm using dicts to store some values, but it's probably a bit overkill
15:52.38lhtlarsen: i am suggesting assigning action items for following this meeting.
15:52.44SRabbeliersaw some very awesome Eclipse plugin for pair programming the other day at solydzajs's reader
15:52.49tlarsenSRabbelier: I am working my way through a huge backlog of stuff you just committed on *Sunday*.
15:53.00tlarsenSRabbelier: I was caught up on Saturday evening.  :)
15:53.01lhtlarsen: since you are not available due to car problems, is there someone you would like to review instead? i would suggest solydzajs
15:53.21tlarsenlh: I want to review this.
15:53.25SRabbeliertlarsen: -nods-, right, that was mostly in reply to your and pawels' suggestions I think, hopefully it'll mostly be LGTM's, no major changes
15:53.27solydzajstlarsen: I still have some commits to do regarding your comments to my commits from a week ago :-)
15:53.28tlarsenlh: And I will *make* the time.
15:53.43lhtlarsen: okay, great. can you give SRabbelier an ETA on a review?
15:53.45SRabbeliersolydzajs: -reads that a few times-
15:53.59tlarsenlh: SRabbelier and I don't see some things eye-to-eye, and I at least want to get my specific $0.02 in.
15:54.06tlarsenlh: Today.
15:54.07lhtlarsen: that's a good thing.
15:54.18lhtlarsen: okay, any idea when today? just because we are all in different time zones
15:54.22solydzajslh: yep it's better for tlarsen to review this, cause this is major change
15:54.55lhsolydzajs: agreed. just trying to get an idea of timing.
15:55.05tlarsenlh: Before 3 AM Tuesday morning, CDT.
15:55.11lhtlarsen: rocking.
15:55.35SRabbeliertlarsen: ok, then I'll finish it up to where all sponsor views are actually with the new code in place, and put that up for review
15:55.39lhSRabbelier: this means by tuesday afternoon your time you will have comments. can you prioritize your other work around this needed review?
15:55.40tlarsenlh: My wife puts on a sleep mask and ear plugs, so I can work all night if needed.   :)
15:55.40SRabbelierafter that I'll take a break to work on school stuff
15:55.45lhtlarsen: rock on. :)
15:55.54lhmakes note: buy fashion earplugs for mrs. tlarsen
15:56.02solydzajs:-)
15:56.03tlarsenlh: Ewwww...
15:56.04SRabbelierchuckles
15:56.18SRabbeliertlarsen: it's called "sleepign, in stylleeee"
15:56.58lhexactly
15:56.59lhok
15:57.09lhSRabbelier: do you know what you need to do in between now and tlarsen's review of 1602?
15:57.14SRabbelierlh: I don't have any other work atm except that (and the review)
15:57.42solydzajsSRabbelier: start working on generic profiles
15:57.47solydzajsSRabbelier: Roles
15:57.54SRabbeliersolydzajs: can you define that better?
15:57.54lhSRabbelier: there you go, help pawel.
15:58.01SRabbeliersolydzajs: what is needed for those?
15:59.05*** join/#melange mithro (n=tim@unaffiliated/mithro)
15:59.05*** mode/#melange [+v mithro] by ChanServ
15:59.25*** topic/#melange by lh -> Want to make Summer of Code and the Highly Open Participation Contest better? Melange is the next generation GSoC and GHOP web app - Code and more at http://code.google.com/p/soc/ - Want to contribute? Start here: http://code.google.com/p/soc/wiki/GettingStarted - Logs at http://ibot.rikers.org/%23melange within 24 hours
15:59.32solydzajsSRabbelier: Generic Profile Form that can be reused in all Roles Profiles, Generic Logic for Profiles (saving in datastore etc) and user view/public view
15:59.56SRabbeliersolydzajs: ok, so like my earlier Person related commits?
16:00.14solydzajsSRabbelier: yes like your earlier not finished commits :D
16:00.14SRabbeliers/commits/review/
16:00.23SRabbelier*LAUGHS*
16:00.25SRabbelieromgomg!
16:00.27SRabbelierthat is too awesome
16:00.36SRabbeliers/too/totally
16:00.45solydzajsso we have too bots now for logging :-)
16:00.53SRabbeliers/too/two/ ?
16:01.01SRabbelierfigures you need to include teh trailing slash
16:01.03SRabbeliers/teh/the/
16:01.27SRabbelierdid I break it? 0.o
16:01.35lhSRabbelier: focus!
16:01.45SRabbeliersolydzajs: ok, I can do that
16:01.46lhSRabbelier: sounds like you have some unfinished coding work to get done.
16:01.53SRabbeliersolydzajs: with the new logic and view code it'll be easier
16:02.04SRabbelierlh: I suspended it till after generic logic was done
16:02.21SRabbelierlh: actually, the generic logic code came from working on that module
16:02.48lhSRabbelier: so can you finish it now?
16:03.05SRabbelierlh: yes
16:03.14lhSRabbelier: there you go.
16:03.20lhSRabbelier: anything else on your mind?
16:03.20SRabbelierI'll do the (trivial) logic stuff first
16:03.31SRabbelierand then wait to do the view code till after todd's review
16:03.54lhSRabbelier: sounds good.
16:04.08SRabbeliergood thing I didn't delete that branch :P
16:05.15lhokay
16:05.17lhSRabbelier: you done?
16:05.20solydzajsok good
16:05.24tlarsenUgh, stupid IRC bot tricks.
16:05.33tlarsenIt will be a feature on Letterman before you know it.
16:05.37SRabbelierlh: sure, I'm good to get started
16:05.42lhSRabbelier: good.
16:06.10lhtlarsen: what's on your mind for the next couple of days besides catching up on commits and commenting on CL 1602 for SRabbelier
16:06.37tlarsenBesides taking another week off because the 50-mile hike was tortuous?
16:06.43SRabbelierlh, tlarsen: well, and the fix-ups for r733 I reckon
16:06.59tlarsenSRabbelier: Yes, undoing a bunch of stuff I didn't like in r733.  :)
16:07.15SRabbeliertlarsen: we're a concencus community though
16:07.25tlarsentlarsen: No, really.  I want to get the Question/Answer and Questionnaire/Response models defined.
16:07.31SRabbeliertlarsen: I think reverts should be after community concencus
16:07.39tlarsenSRabbelier: Yes, but you didn't have consensus when you committed. :)
16:07.44lhtlarsen: another week off is good.
16:07.55tlarsenlh: one of the hazards of review-before-commit:  commit wars!
16:07.58lhtlarsen: you can't always wait for consensus to committ.
16:08.08lhtlarsen: this is a war i am willing to fight. :)
16:08.20tlarsenlh: Yes, and the one who didn't have consensus when he committed can't get upset when someone patches over them.
16:08.35tlarsenlh: I will put my code where my mouth is.
16:08.49tlarsenlh: I outlined in graphic detail in the previous discussion what I plan to do and why.
16:08.53lhtlarsen: that is totally true.
16:08.56tlarsenlh: Existing functionality was *removed* by r733.
16:09.04SRabbeliertlarsen: see my reply to your comments in r733
16:09.06lhtlarsen: and did it cause breakage?
16:09.09tlarsenlh: I will restore it in the current framework of r733.
16:09.12SRabbeliertlarsen: and also CL1602
16:09.27SRabbeliertlarsen: I believe that will explain why I think it won't be needed
16:09.29tlarsenlh: No, but it removed my ability to customize the login prompts per-page, which I was planning to do as soon as I had time.
16:09.38lhtlarsen: can this be worked around?
16:09.44SRabbeliertlarsen: right, but with the new view refactor you won't have to
16:09.45tlarsenlh:  The current UI is pretty lame regarding asking the user to login when they are not.
16:09.48SRabbeliertlarsen: you can define it in teh base classes
16:09.57tlarsenSigh.
16:10.53lhokay. so tlarsen, can you look at CL1602 first, then comment on r733?
16:11.04tlarsenlh: The point is this:  the functionality was removed, and justification for it being there was provided in the review-after-commit, but no justification of similar weight and coherency was provided as to why it should not be added back.  But, yes, I will look at 1602 first.
16:11.26lhtlarsen: thank you. perhaps that would be helpful.
16:11.29tlarsenlh: consensus is meaningless when some of the parties do not justify their position with facts.
16:11.36lhSRabbelier: you may also want to add more detail to r733 too
16:11.44lhtlarsen: we're working on fixing that now, aren't we? :)
16:11.49SRabbeliertlarsen: you read my latest comments to r733?
16:11.51tlarsenlh: Why, yes, we are.
16:12.00lhtlarsen: ++
16:12.08tlarsenlh: But, please don't be good cop to my bad cop, OK?
16:12.15lhtlarsen: i'm not. i am facilitating.
16:12.35tlarsenlh: So, you won't mind being disintermediated, then?
16:12.50lhtlarsen: what does that mean?
16:12.52lhuses google
16:12.53tlarsenlh: This discussion was going just fine in the code review thread.
16:13.05tlarsenfucking hates IRC
16:13.10SRabbeliertlarsen: if you read my reply, please comment :)
16:13.14lhtlarsen: this is how open source works todd
16:13.17tlarsenIt doesn't show when someone else is typing like Jabber does.
16:13.28lhtlarsen:  i dont think the discussion should not take place on list too.
16:13.32tlarsenThat is the primary reason why people type over each other.
16:13.46lhthere has to be a tool that accomodates.
16:14.20lhtlarsen: i am happy to read on list comments too, but can't read them all. this meeting helps me keep in sync. other people, i hope, find it useful.
16:14.22tlarsenlh: "this is how open source works" is also why asbestos underwear is required.  :)
16:14.52solydzajsi'm back, so where are we at ?
16:16.03durin42lh: TBQH, I hate irc too. It's a time drain, and sucks for having coherent conversations most of the time.
16:16.32SRabbeliermust be too young
16:16.54tlarsendurin42: exactly.
16:16.56solydzajshow about we make a Skype conference call next time ?
16:16.58lhdurin42: to each their own
16:17.01lhsolydzajs: i like this idea.
16:17.08SRabbeliersolydzajs: +1 on that
16:17.12lhtlarsen: thoughts?
16:17.12SRabbelierdoes everybody have a mic/headset?
16:17.20solydzajsSRabbelier: I do
16:17.20tlarsensolydzajs: How about we just use Jabber, with the "someone is typing" indicator?
16:17.31SRabbeliertlarsen: skype has that -nods-
16:17.39solydzajstlarsen: we can do that too, make a gtalk group chat
16:17.49SRabbeliersolydzajs: that would work
16:18.01durin42does pidgin support grouptalk on gtalk?
16:18.10SRabbelierdurin42: not really
16:18.10durin42(and if so, does Adium?)
16:18.13SRabbelierdurin42: only half
16:18.26SRabbelierdurin42: you get the invite, but last time I tried it didn't know what to do with it
16:18.50lhi dont give a crap what tool we use.
16:18.57lhyou guys figure that out
16:19.37SRabbelierI'm fine with whatever is good for you
16:20.08lhi want tlarsen to be happy with our tool choice. sounds like jabber works well for him. however, skype offers voice.
16:20.20SRabbelierdoesn't have a jabber profile
16:20.26SRabbelierhow do you make one?
16:20.29SRabbelierjabber.com or such?
16:20.36solydzajsSRabbelier: you have gmail.com
16:20.45SRabbeliersolydzajs: that works?
16:20.55solydzajsSRabbelier: GTalk is based on XMPP and has group chat
16:21.14lhdo we all agree that our next meeting with be on GChat?
16:21.27lhif so is there a way to bridge that so that our meeting still gets logged to our regular logs
16:21.35SRabbelierlh: I'm good with gchat
16:21.56lhokay.
16:22.22lhGChat it is
16:22.31lhi will paste the logs in channel so they get logged by ibot
16:22.34lhokay
16:22.37lhso
16:22.41lhsolydzajs: what are you up to right now?
16:23.57SRabbeliertlarsen: on the email=id thing, it works only because str(id) returns id.email()
16:24.25tlarsenSRabbelier: Yes, but id.email() is explicit and conveys *intent*.
16:24.30SRabbeliertlarsen: Pawel asked me to do a patch to clean all those up and us id.email() everywhere
16:24.32tlarsenSRabbelier: That is important in readable code.
16:24.36SRabbeliertlarsen: right, I agree
16:24.45tlarsenSRabbelier: Yes, please fix this.
16:25.00solydzajslh: after recent code reviews, I'm working on Delete Document feature and when I commit that I will move to Promote to Host probably
16:25.07lhsolydzajs: sounds good.
16:25.09tlarsenSRabbelier: we have pretty much established "id" in the code meaning Google Account (as a users.User object).
16:25.24SRabbeliertlarsen: ok, then let's go with that everywhere
16:25.34SRabbeliertlarsen: I'll double check the code to see if it's not abused anywhere
16:26.15lhok gentlemen
16:26.21lhi am 30 minutes late for another meeting
16:26.37lh_Allen_ requested that we move our next meeting back so he could attend
16:26.42lhdoes this work for all?
16:26.43lhhttp://tinyurl.com/melangemondaymeeting
16:26.45tpbTitle: The World Clock - Time Zone Converter - U.S.A. California San Francisco vs Poland Warsaw (at tinyurl.com)
16:27.03SRabbelierlh: 3am in the morning?
16:27.13SRabbelier:P
16:27.29SRabbelierwhy is our next meeting so soon though?
16:27.36solydzajs3 AM doesn't work for me :-)
16:27.47SRabbeliersolydzajs: same here
16:28.16lhhrm.
16:28.29lhSRabbelier: it was our regularly scheduled meeting
16:28.35lhi will just check in with _Allen_ tonight
16:28.39lhdo we need that meeting at all?
16:28.51SRabbeliernot me personally
16:29.01lhsolydzajs: you need it?
16:29.04lhtlarsen: you need it?
16:29.06lhdurin42: you need it?
16:29.09solydzajslh: tlarsen wrote _Allen_ what he could work on, so I think he will be fine when he reads his inbox :-)
16:29.12tlarsenlh: No I do not.
16:29.27tlarsenlh: I believe these are mostly for you.  :)
16:30.01lhtlarsen: done, today is canceled
16:30.08lhi will still check in with _Allen_
16:30.27lhtlarsen: i scheduled them because people wanted to make sure i was commenting. :) so i hope they are good for more than just me.
16:30.28tlarsenlh: I'm sure he will check his email once power is restored.
16:31.53solydzajsIs there anything else to discuss ? I would like to get back to work and do some coding :-)
16:32.05SRabbelierwould like to get to dinner himself :P
16:32.23lhSRabbelier: go eat
16:32.34lhtlarsen: always nice to say hello too
16:32.38lhsolydzajs: i think we are done
16:32.44lhanyone have anything to add?
16:33.11SRabbelierlh: I like them, it's nice to make sure we all stay in touch
16:33.24SRabbelieruhm, "Eta Beta Pi" (eat a better pie :P)
16:33.25lhSRabbelier: cool.
16:33.34lhSRabbelier: wtf dude. :p
16:33.39SRabbelier:D
16:33.49lhalright
16:33.51lhgoes to other meeting
16:34.00SRabbelierlh: ok, ttyl
16:34.46tlarsendefinitely prefers the store-and-forward nature of email, given his ridiculously hectic schedule.
16:36.40solydzajsokie dokie guys :-)
16:36.59solydzajsI'm going back to coding
16:37.10solydzajsciao
16:37.15tlarsenSigh.  I am continuing to code review.
16:37.21tlarsenputs on his Code Review Monkey hat.
16:38.02solydzajsyay
16:38.06solydzajsttyl
16:38.11solydzajsi'm going offline
16:38.11solydzajs:-)
16:39.27tlarsenSRabbelier: was this committed?  http://codereviews.googleopensourceprograms.com/1601
16:39.30tpb<http://ln-s.net/2KUU> (at codereviews.googleopensourceprograms.com)
16:39.35tlarsenSRabbelier: If so, has the review been marked "closed"?
16:40.32SRabbeliertlarsen: mhhh, yes, it has been committed, didn't close it yet since you hadn't commented on that version; I'll close it now
16:47.20*** join/#melange mithro (n=tim@unaffiliated/mithro)
16:47.20*** mode/#melange [+v mithro] by ChanServ
17:13.59SRabbeliertlarsen: pawel and I suggested earlier for the reviewer today to fix style mistakes instead of pointing them out, since now it takes trice the time; once for you to point them out, once for me to fix them, then once more for you to see if they were fixed to satistfaction
17:14.53SRabbeliertlarsen: style, spelling, indentation, little things like that
17:15.27tlarsenSRabbelier: Sorry, but when I am code reviewing, I point out everything.  I don't know until I am done that I will end up with only style mistakes.
17:15.40tlarsenSo, I send out what I have already taken the time to type.
17:16.05tlarsenSRabbelier: when I am focused on the code, I see everything (or, I am not focused enough and miss important stuff).
17:16.13tlarsenSRabbelier: Sorry, but that is the way my brain works.  :)
17:17.08tlarsenSRabbelier: I don't know how to do two different kinds of code review.  I don't think the burden should be on the reviewer, since review-before-commit would catch this and the burden would still be on the committer.
17:17.17tlarsenSRabbelier: it is part of the price that is paid for review-after-commit.
17:17.33tlarsenSRabbelier: That being said, when I see stuff in existing files that I am modifying, I'll just fix it.
17:17.58tlarsenSRabbelier: This is one of the reasons we do not do review-after-commit at Google, ever (except for to-be-reviewed *emergencies*).
17:31.09SRabbeliertlarsen: ok, I understand, no problem :)
17:31.16SRabbeliertlarsen: thanks for the explanation :)
17:34.13tlarsenSRabbelier: The point is that the committer, not the reviewer, is responsible for correctly reviewer comments.
17:34.46SRabbeliertlarsen: yes, I agree on the responsibility part -nod-
17:35.00tlarsenI have *tons* of reviews sent to me each week.  If I had to *fix* as well as review, I'd just stop reviewing.  :)
17:35.13tlarsen(Melange plus Google internal code reviews)
17:35.38SRabbeliertlarsen: -nod-, yeah, I can imagine
18:26.43tlarsenSRabbelier: OK, first thoughts on 1602 sent.
18:26.56SRabbeliertlarsen: thanks, -reads-
18:27.43tlarsenSorry it took so long.
18:27.49tlarsenSRabbelier: I had a lot to say, I suppose.
18:27.51SRabbeliertlarsen: I don't see a TODo above existing code?
18:27.54SRabbelierit's ok, :)
18:28.23SRabbeliertlarsen: oh, on the silly import naming scheme, sometimes it just breaks for no reason
18:28.43SRabbeliertlarsen: when you do "from soc.logic import models" and then later on models.settings, it says there's no settings module
18:28.45tlarsenPlease respond in the code review tool and not on IRC.
18:28.46tlarsenThanks.
18:28.54tlarsenYes, you need:
18:29.05tlarsenfrom soc.logic.models import settings
18:29.12tlarsenThen just use settings.Foo()
18:29.18tlarsenOr:
18:29.25tlarsenfrom soc.logic import models
18:29.31tlarsenimport soc.logic.models.settings
18:29.36tlarsenand then models.settings will work.
18:29.39SRabbeliertlarsen: aaaah, ok!
18:29.41SRabbeliertlarsen: thank you!
18:29.48SRabbeliergoes to clean up code
18:31.28SRabbeliertlarsen: how about a script that detects things like that; do you know of one?
18:31.43tlarsenpychecker?
18:32.09SRabbeliertlarsen: mhh, I remember you mentioning it earlier, was there a reason we're not really using it?
18:33.16tlarsenI am all out of round tuits.
18:33.43SRabbelierround tuits?
18:51.31tlarsen"I will do it when I get around to it..."
18:51.36tlarsen"a round tuit"
18:51.41SRabbelierlol, ok
18:51.52tlarsenhttp://www.myrtlewoodgallery.com/get_a_round_tuit.htm
18:51.53tpb<http://ln-s.net/2KWs> (at www.myrtlewoodgallery.com)
18:52.02tlarsenI have lots of the square ones these days.
18:52.18SRabbeliertlarsen: cute, never heard that one :)
18:53.47*** join/#melange mithro (n=tim@unaffiliated/mithro)
18:53.47*** mode/#melange [+v mithro] by ChanServ
19:42.24SRabbeliertlarsen: replied :)
19:42.29SRabbeliertlarsen: thanks for the detailed review
21:04.45*** join/#melange TimRiker (n=timr@72-62-179-250.area1.spcsdns.net)
21:05.09*** part/#melange TimRiker (n=timr@bzflag/projectlead/TimRiker)
21:17.22*** join/#melange solydzajs (n=solydzaj@apn-77-113-116-102.gprs.plus.pl)
21:17.22*** mode/#melange [+v solydzajs] by ChanServ
21:18.10solydzajstlarsen: ping
21:18.26SRabbeliertlarsen: replying now, then going to bed :)
21:19.09solydzajstlarsen: "Pawel, what about the more-generic HomeSettings class that already exists in soc/models/home_settings.py?" You mean to replace SiteSettings with HomeSettings ?because right now SiteSettings inherits from HomeSettings
22:03.33*** join/#melange James--Crook (n=client@89.100.50.76)
22:21.28*** part/#melange James--Crook (n=client@89.100.50.76)
22:33.48SRabbeliertime for bed
22:33.49SRabbelierg'night
22:34.01SRabbelierholy cr*p
22:36.23SRabbeliersolydzajs: damn Pawel, please tell me you used a script to sort those imports?
22:36.37solydzajsSRabbelier: yo :-)
22:36.45solydzajsSRabbelier: no
22:36.58solydzajsSRabbelier: why ?;-)
22:37.16SRabbeliersolydzajs: cos I hate manual labor like that :P
22:37.24SRabbeliersolydzajs: nice job!
22:37.40solydzajsSRabbelier: it was my break (no need to use brain ;-) ) :D
22:38.04SRabbeliersolydzajs: thanks for applying Todd's suggestions, I did not have time to code at all today, have been doing code review (well, it was really design the app I guess) all day
22:38.09SRabbeliersolydzajs: hehe, sweet :)
22:38.21solydzajssure no problem
22:38.25solydzajsI just need to clear my inbox
22:38.26solydzajs:-)
22:38.36solydzajsso I'm fixing what ever I can
22:38.37solydzajs:-)
22:39.06SRabbeliersolydzajs: awesome :)
22:40.48SRabbeliersolydzajs: btw, implicit LGTM on everything that I don't comment on :P
22:40.59solydzajsSRabbelier: ok :-)
22:41.11SRabbelier(downside of that ofcourse is if for some reason I don't have time to review, a LGTM is unjustifiedly assumed :P)
22:41.32SRabbelieranyway
22:41.37SRabbelierI must really be off to bed now
22:41.44SRabbeliersolydzajs: ps: will you code the _as_table template?
22:41.58solydzajsSRabbelier: hopefully tomorrow
22:42.18SRabbeliersolydzajs: really? awesome!
22:42.27SRabbelierhopefully we can generalize even more views that way :)
22:42.30solydzajsSRabbelier: hope so
22:43.09SRabbelierg'night then :)
22:43.46SRabbeliertlarsen: thanks for the reviews (it felt more like design than review though :), that's good I think)
22:45.53solydzajsg'night
23:36.36*** join/#melange _Allen_ (n=user@218.27.66.131)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.