| 00:10.30 | *** join/#melange tansell (n=tansell@nat/google/x-6bde3abc838050b1) |
| 00:17.27 | tlarsen | _Allen_: I have not yet gotten to creating those Question, Answer, etc. models. I will have to do it tomorrow morning. |
| 00:17.44 | tlarsen | _Allen_: I spent all day getting caught up on outstanding code reviews that piled up while I was on vacation last week. |
| 00:18.00 | tlarsen | _Allen_: The Question and Answer stuff is at the top of my TODO list, though, so I will work on it first thing tomorrow. |
| 00:18.10 | tlarsen | I've got to sign off now. |
| 00:18.16 | _Allen_ | tlarsen: that's ok |
| 01:14.40 | *** join/#melange penyaskito (n=penyaski@85.137.209.69.dyn.user.ono.com) |
| 01:26.18 | *** join/#melange lh (n=lhawthor@nat/google/x-cff80acc8c54741b) |
| 01:26.33 | *** mode/#melange [+o lh] by ChanServ |
| 01:26.35 | lh | _Allen_: ping |
| 01:43.38 | _Allen_ | lh: morning |
| 01:45.24 | lh | _Allen_: how are you? |
| 01:45.32 | lh | we are not really meeting tonight |
| 01:45.34 | lh | everyone is sleeping |
| 01:45.38 | lh | <PROTECTED> |
| 01:45.51 | _Allen_ | lh: fine |
| 01:46.26 | _Allen_ | lh: I just got up |
| 01:46.46 | _Allen_ | lh: and I am reading the IRC log |
| 01:47.08 | _Allen_ | lh: that's ok |
| 01:47.15 | lh | _Allen_: very cool on reading the logs |
| 01:47.54 | _Allen_ | lh: so, will we use Gtalk on later meeting? |
| 01:52.09 | lh | _Allen_: sure can |
| 01:52.12 | lh | we will work that out |
| 01:52.16 | lh | i have to go get dinner, bbl |
| 01:52.23 | _Allen_ | lh: see u |
| 02:59.50 | *** part/#melange _Allen_ (n=user@218.27.66.131) |
| 04:00.19 | *** join/#melange tpb (n=supybot@verbal.mithis.com) |
| 05:42.40 | *** join/#melange lhawthorn (n=lhawthor@nat/google/x-90a243d93c7d84e4) |
| 05:42.53 | *** join/#melange lh (n=lh@ip67-152-80-226.z80-152-67.customer.algx.net) |
| 05:42.53 | *** mode/#melange [+o lh] by ChanServ |
| 06:19.09 | *** join/#melange lh_ (n=lh@ip67-152-80-226.z80-152-67.customer.algx.net) |
| 06:30.18 | *** part/#melange lh_ (n=lh@ip67-152-80-226.z80-152-67.customer.algx.net) |
| 06:52.49 | *** join/#melange mithro (n=tim@unaffiliated/mithro) |
| 06:52.49 | *** mode/#melange [+v mithro] by ChanServ |
| 09:04.53 | *** join/#melange penyaskito (n=penyaski@85.137.209.69.dyn.user.ono.com) [NETSPLIT VICTIM] |
| 10:10.48 | *** join/#melange _Allen_ (n=user@218.27.66.131) |
| 12:43.15 | *** join/#melange madrazr (n=madhu@59.96.59.80) |
| 13:11.25 | *** join/#melange madrazr (n=madhu@59.92.169.47) |
| 13:29.21 | *** join/#melange James--Crook (n=client@89.100.50.76) |
| 14:53.32 | *** part/#melange _Allen_ (n=user@218.27.66.131) |
| 14:56.04 | *** part/#melange James--Crook (n=client@89.100.50.76) |
| 15:00.03 | *** join/#melange tlarsen (n=tlarsen@adsl-074-237-182-025.sip.hsv.bellsouth.net) |
| 15:00.03 | *** mode/#melange [+o tlarsen] by ChanServ |
| 15:27.38 | *** join/#melange lh (n=lhawthor@nat/google/x-eba87181a638ed66) |
| 15:28.08 | *** mode/#melange [+o lh] by ChanServ |
| 15:48.31 | *** join/#melange mithro_ (n=tim@unaffiliated/mithro) |
| 15:48.31 | *** mode/#melange [+v mithro_] by ChanServ |
| 16:34.40 | *** join/#melange mithro (n=tim@unaffiliated/mithro) |
| 16:34.40 | *** mode/#melange [+v mithro] by ChanServ |
| 16:36.25 | *** join/#melange PINguAR_ (n=PINguAR_@88.234.102.231) |
| 16:36.39 | *** part/#melange PINguAR_ (n=PINguAR_@88.234.102.231) |
| 17:20.30 | *** join/#melange Mek__ (n=marijn@93.157.1.37) |
| 18:11.49 | *** join/#melange mithro (n=tim@unaffiliated/mithro) |
| 18:11.49 | *** mode/#melange [+v mithro] by ChanServ |
| 18:23.54 | *** join/#melange James--Crook (n=client@89.100.50.76) |
| 18:31.11 | James--Crook | tlarsen: Hi, I've some questions about past user-stories to run past you if you're not totally snowed under. |
| 18:31.33 | James--Crook | There are some gaps in the numbers, and I'm wondering about the ones that are 'missing'. |
| 18:32.43 | James--Crook | It's relevant to mentor summit, people will be likely looking for user stories to work from - and/or writing new ones |
| 18:38.32 | tlarsen | James--Crook: Some have been implemented. |
| 18:38.48 | tlarsen | James--Crook: when they get marked "Fixed" or whatever, they don't show up in the default view. |
| 18:41.02 | James--Crook | Oh... my mistake. I thought maybe there had been quite a few that had been rejected as not suitable. |
| 18:41.26 | James--Crook | So does that mean that there have been virtually no stories coming in from outside? |
| 18:42.13 | James--Crook | ..if so we should try to change that before the summit, because otherwise peopel won't have much idea what to 'hackathon' on. |
| 18:50.32 | tlarsen | James--Crook: Yes, the stories have been written by existing Contributors at this point, for the most part. |
| 18:50.53 | tlarsen | James--Crook: Well, there are 40+ outstanding User Stories already. |
| 18:51.33 | James--Crook | ..yes but many of them are very similar, and my expectation about what will motivate people at the summit is that they will want to do |
| 18:51.39 | James--Crook | the 'spectacular' things. |
| 18:52.34 | James--Crook | There will be people there who are incredibly fluent at client side javascript for example. |
| 18:53.43 | James--Crook | As I see it, virtually no one is looking at Melange other than the dozen or so names that we see on this IRC channel. |
| 18:55.34 | *** 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 |
| 18:55.41 | James--Crook | Partly it is a question of what the objective is for the demo at the mentor summit. I'm working on the assumption that the intention is to get many people each contributing something, so more people are taking ownership of the project. |
| 19:05.21 | tlarsen | James--Crook: That is not actually my intention ("to get many people each contributing something"). That is something that lh wants, though. |
| 19:05.45 | James--Crook | tlarsen: What is your intention for the summit? |
| 19:05.54 | tlarsen | James--Crook: I am wary, because the software is so incomplete at the moment. This is a classic "mythical man-month" problem. |
| 19:06.01 | tlarsen | James--Crook: I don't have one. |
| 19:06.09 | tlarsen | James--Crook: Ask lh what her intention is. |
| 19:06.12 | James--Crook | Hmm... |
| 19:06.16 | lh | i think it is worth seeing what we can get out of more contributors. we don't have to to take their patches. |
| 19:06.26 | tlarsen | I am working on Melange at the best pace that the current set of contributors can work on it. |
| 19:06.33 | James--Crook | well whatever I would like people to feel that Melange is something exciting to work on, even if people do feel |
| 19:06.40 | tlarsen | That pace will be *dramatically* reduced with a rapid influx of "help". |
| 19:06.47 | tlarsen | lh does not agree with me, though. |
| 19:06.48 | lh | objective for the demo is to get more contributions afaic - people are going to have to use it, so they ought to improve it. that was the main complaint we heard about the current web app. |
| 19:06.49 | James--Crook | that they have a bit of a mountain to climb to meet the reviewing standrards etc. |
| 19:07.08 | lh | tlarsen: i think we can manage the incoming help appropriately. these are smart people with years of experience. |
| 19:07.20 | James--Crook | tlarsen: I think it depends on what kind of help we get and how we ask for it. |
| 19:07.42 | tlarsen | lh: I wish we could just open source the existing, working web app, and have our only job be to review patches that make it better, but we can't, for well-known reasons. |
| 19:07.47 | James--Crook | So it is vital to not ask 'hey please all just pile in'! |
| 19:07.53 | lh | tlarsen: agreed. |
| 19:07.56 | lh | James--Crook: also agreed. |
| 19:08.07 | lh | i think the best approach is to let people log as many user stories as they want |
| 19:08.10 | tlarsen | James--Crook: Yes, but that is what the approach comes across as currenty. |
| 19:08.13 | lh | we then do some extensive triage |
| 19:08.19 | tlarsen | James--Crook: I personally cannot handle a pile-on. |
| 19:08.31 | James--Crook | I don't think that's lh's intention. |
| 19:08.35 | lh | then let folks know that they can do whatever they want, but we are only reviewing patches in priority order, and we set the priority |
| 19:08.36 | tlarsen | lh: "we" will need to be "you" |
| 19:08.49 | lh | people are welcome to do as they like |
| 19:08.51 | James--Crook | triage... yes. |
| 19:08.54 | lh | tlarsen: i dont follow |
| 19:08.57 | lh | oh wait yes i do |
| 19:09.07 | lh | tlarsen: i know, i'm ready for that. i control the firehose for you. |
| 19:09.14 | lh | already planned on that. |
| 19:09.14 | tlarsen | lh: The coders (me, Pawel, Sverre, Allen, ...) can code all sorts of things, but there is no direction from you, the primary user, in terms of the relative importance of features. |
| 19:09.23 | tlarsen | lh: That is why we agreed on IRC to the current approach. |
| 19:09.31 | James--Crook | OK. Let's get specific about what we can do. |
| 19:09.37 | tlarsen | lh: It is top-down, with common features needed to get the site running. |
| 19:09.54 | James--Crook | Firstly, I can cope with say 100 new stories. Some rubbish. One or two gems. |
| 19:09.55 | tlarsen | lh: Once we have that, there will be a lot more room for people to bolt-on specific stuff. |
| 19:10.06 | James--Crook | I don't mean writing the code :-) |
| 19:10.14 | lh | tlarsen: it was my understanding that this was the best we could do before the summit. without that foundation in place we cannot get things done. setting priorities for the nicer to have than the basics should, IMHO, come after the basics are there. |
| 19:10.21 | lh | tlarsen: perfection. |
| 19:10.32 | lh | James--Crook: agreed. there is always lots of rubbish in issue trackers |
| 19:10.47 | tlarsen | James--Crook: Oh, I'm fine with GSoC mentors contributing User Stories, but not GSoC students. |
| 19:10.58 | James--Crook | And the one or two gems get approved and refined. |
| 19:11.03 | tlarsen | James--Crook: Anyone can subscribe to the melange-soc mailing list. Anyone. |
| 19:11.13 | James--Crook | tlarsen: Great. So actions for me: |
| 19:11.32 | tlarsen | lh: It isn't about perfection at all at this point. It is about fundamentals, and "there's no there there." |
| 19:12.03 | James--Crook | 1) I post (again) about stories on the melange-soc list. Ask for more. There will NOT be a deluge. |
| 19:12.17 | James--Crook | and if there is, I will be very glad and will 'cope with it'. |
| 19:12.19 | tlarsen | lh: A tight, focused team will move much faster than having to sift through dozens of potential patches each day, most of them questionable. |
| 19:12.31 | James--Crook | NOT patches. Stories. |
| 19:12.47 | tlarsen | James--Crook: Yes, work with lh and pick out the ones that are well-written and turn them into issues. |
| 19:13.00 | lh | tlarsen: that's what i planned on. |
| 19:13.07 | James--Crook | Action 2 (for me). I post to gsoc-mentors and point people to the request... |
| 19:13.19 | lh | James--Crook: thanks for offering to help about that |
| 19:13.24 | tlarsen | I think most people don't realize how many full-time man-months (interns) went into the current web app. |
| 19:13.36 | tlarsen | James--Crook: sounds good to me. |
| 19:13.39 | James--Crook | actually, I'd like people to post them direct as issues, like I did, and we weed out the duds. |
| 19:13.48 | James--Crook | merge |
| 19:13.50 | lh | James--Crook: agreed |
| 19:13.51 | James--Crook | iterate. |
| 19:13.53 | lh | agreed |
| 19:13.58 | lh | i have to go to lunch, i am sorry |
| 19:13.58 | tlarsen | James--Crook: if the issue tracker could delete issues, I'd be all for that, but it can't. |
| 19:14.02 | lh | i will be back soon. |
| 19:14.06 | lh | tlarsen: we mark as obsolete |
| 19:14.07 | James--Crook | Meanwhile you and Sverre and co can code. |
| 19:14.07 | lh | or wont fix |
| 19:14.12 | lh | or even "go away" |
| 19:14.16 | James--Crook | exactly. |
| 19:14.20 | tlarsen | James--Crook: I really don't want the closed issues cluttered with a bunch of rejects. |
| 19:14.36 | James--Crook | Do they not get filtered out? |
| 19:14.38 | tlarsen | Fine. I don't actually care about it that much. |
| 19:14.45 | James--Crook | Yurk. Tool issue. |
| 19:14.51 | lh | we just pick the right label and filter it out |
| 19:14.54 | tlarsen | I'll just ignore the issue tracker, basically, and let people point out ones that need my attention. |
| 19:14.57 | lh | i am in favor of "no go away" |
| 19:15.01 | lh | bbialb |
| 19:15.02 | James--Crook | me too. |
| 19:15.14 | James--Crook | (in favour of no go away) |
| 19:15.24 | tlarsen | I want to code the app, not decide what the app is. |
| 19:15.44 | James--Crook | I know that. |
| 19:15.57 | tlarsen | My objections tend to be about difficulty of implementation, performance bottlenecks, things requiring schema changes later, etc. |
| 19:16.25 | James--Crook | go on... |
| 19:16.29 | tlarsen | The traditional "patches welcome" model is not for rapid development of something not even at version 0.1. |
| 19:17.23 | James--Crook | I too think we should not be saying 'absolutley any patch is welcome'... I mean even one that has no story motivating it, nor obvious reduction in code size/complexity |
| 19:17.53 | tlarsen | A firehose of interest will derail this project quite effectively. It would basically be a DDoS attack to the existing committers. |
| 19:18.37 | James--Crook | So there are various ways to counter that. One is to give a really boring talk at the summit. |
| 19:19.05 | James--Crook | Another is to ask for the right kind of help. |
| 19:19.43 | James--Crook | please, I'd also like to know more about the specific problems, the concerns that casual committers tend to NOT pay attention to. |
| 19:20.00 | tlarsen | James--Crook: I really want to be an individual contributor, not a community manager. |
| 19:20.06 | James--Crook | you mentioned performance bottlenecks, schema changes later |
| 19:20.28 | tlarsen | James--Crook: No one is taking that role at the moment, so it falls to me. Hence, I take a very conservative view of offers of help. |
| 19:21.03 | tlarsen | James--Crook: Without care, we can end up implementing things in App Engine that exceed the maximum request deadline, require queries that are too expensive, etc. |
| 19:21.26 | tlarsen | That is the stuff I want to avoid, using a code review model like the one we are already using among the existing contributors. |
| 19:21.39 | James--Crook | Sverre and Pawel would be relatively unaware of such issues. Correct? |
| 19:21.50 | tlarsen | The thing is, most open source stuff, and most products at Google actually, are "shipped when they are ready". |
| 19:22.09 | tlarsen | But, that isn't the case with Melange. There is a big time pressure that feels very unnatural. |
| 19:22.25 | tlarsen | At the summit, my plan was to show the app in whatever state it is in. |
| 19:22.38 | James--Crook | The review process in Google is outstanding, and it is something open source could learn from. |
| 19:22.54 | tlarsen | That got co-opted into it needing to do certain things "to get new contributors interested", and I don't think that is the way to go. |
| 19:23.09 | James--Crook | I cringe at the memorty leaks we have in Audacity (open source app I work on). |
| 19:23.44 | tlarsen | My goal for this project all along was to at least get it to the state where we could run GHOP and GSoC, and then let contributors fix what they didn't like, and have GSoC students sign up for a "Melange organization" and let GHOP students do Melange tasks. |
| 19:24.14 | tlarsen | Pretty much everything that I know of that Google has open-sourced is in working order before we "un-hide" the Google Code project. |
| 19:24.29 | tlarsen | This development model for Melange is very different from that approach, and I don't like it at all. |
| 19:24.49 | tlarsen | This isn't what I thought I was signing up for, basically. |
| 19:24.50 | James--Crook | So.. at the summit, we show the app... let people know 'it's not ready'. We can do some other things too. I'd liek to get someone from Nmap involved, as we are currently naive about security. I know enough to know that we are. |
| 19:26.06 | tlarsen | I'm making the best of it, though, because I care about the Google Summer of Code program, and I think having the web app open-sourced is in the program's best interest. |
| 19:26.08 | James--Crook | So we need to find a way to solve some of that. I've got some ideas. |
| 19:27.20 | tlarsen | I, too, think that the way Google develops software works very well. |
| 19:27.45 | James--Crook | In open source, code often has started out as one person's pet project, and is quite mature before it gets released to general scrutiny. |
| 19:27.49 | tlarsen | I am not willing to compromise that belief to do this project "the way it is done in the open source world" if those ways are broken. |
| 19:28.02 | tlarsen | Yes, and that didn't happen with Melange, and it is a sore spot with me. |
| 19:28.31 | tlarsen | I feel very pressured to do something that does not seem like the best way to get this done. |
| 19:28.55 | tlarsen | Gears, GWT, protobufs, etc. None of these were done this way. I did not want to be some sort of guinea pig. |
| 19:29.41 | *** part/#melange madrazr (n=madhu@59.92.169.47) |
| 19:32.06 | tlarsen | (and I consider all of those to be "successful" open source projects now) |
| 19:32.07 | James--Crook | I need to think about this. It may end up as an e-mail, or I may want to talk again before that. I'm understanding a lot more of what I see in the project space now, now that I'm getting a better picture. To some extent we're stuck with the project being open at this stage, and I think it's impossible for you on your own to solve the consequences of that. |
| 19:32.46 | James--Crook | I don't think it's possible to go closed-doors again at this stage. |
| 19:32.47 | tlarsen | I suspect that as soon as Melange doesn't need me specifically any more, I will move on. |
| 19:34.35 | James--Crook | If that is going to happen then I want to make sure we have captured specific 'care-abouts' that other people are not aware of yet. |
| 19:36.06 | James--Crook | Talk again later. |
| 19:38.11 | tlarsen | OK, later. |
| 20:00.22 | *** join/#melange minunea_konsole (n=yaib@86.120.66.182) |
| 20:00.52 | *** part/#melange minunea_konsole (n=yaib@86.120.66.182) |
| 20:02.23 | *** join/#melange tansell (n=tansell@nat/google/x-707a9d878b988515) |
| 20:30.45 | *** join/#melange SRabbelier (n=SRabbeli@ip138-114-211-87.adsl2.static.versatel.nl) |
| 20:30.45 | *** mode/#melange [+v SRabbelier] by ChanServ |
| 20:31.47 | SRabbelier | lh, tlarsen: school is catching up for me |
| 20:31.58 | SRabbelier | I need to finish this take-home examn :( |
| 22:31.13 | *** join/#melange PINguAR_ (n=PINguAR_@88.234.102.231) |
| 22:31.20 | *** part/#melange PINguAR_ (n=PINguAR_@88.234.102.231) |
| 22:44.33 | *** join/#melange solydzajs (n=solydzaj@apn-77-115-52-115.gprs.plus.pl) |
| 22:44.33 | *** mode/#melange [+v solydzajs] by ChanServ |
| 22:45.10 | solydzajs | tlarsen: ping. |
| 22:45.19 | tlarsen | solydzajs: Hello. |
| 22:45.51 | solydzajs | tlarsen: Hi :-) I didn't have time to talk to you. How was your backpacking trip ? |
| 22:46.32 | tlarsen | LONG. :) |
| 22:47.26 | solydzajs | :-) but you made it |
| 22:47.37 | solydzajs | how long it was ? 50 miles ? |
| 22:50.50 | solydzajs | tlarsen: I wanted to ask what are you working on right now ? |
| 22:54.09 | tlarsen | solydzajs: 50 miles, and pouring rain on Tuesday night and Wednesday morning, plus an injured adult leader that required an extra *10* mile hike back to the van the first day. |
| 22:54.37 | tlarsen | solydzajs: So, two of us actually hiked 60+ miles, including 20.2 miles the first day (and into the night until 3:00 AM). |
| 22:54.54 | solydzajs | tlarsen: oh my :-) nice trip. was it hard for kids ? |
| 22:56.55 | tlarsen | solydzajs: They all survived. It was harder on the one other adult (not me :). |
| 22:58.07 | tlarsen | solydzajs: To answer your other question, I am working on the Question, Answer, Quiz, Response Models. |
| 22:58.33 | tlarsen | solydzajs: by the way, +1 to the "no roadmap" document :) |
| 22:58.45 | solydzajs | tlarsen: heh :-) |
| 22:59.07 | solydzajs | tlarsen: I'm fixing some code after Sverre's commits, but I'm almost done |
| 22:59.19 | tlarsen | solydzajs: As I learned a couple of months ago, "code talks, documents walk", when the documents describe code or coding to do. |
| 22:59.31 | tlarsen | solydzajs: I like the docs that James is writing, about community and the like. |
| 22:59.55 | solydzajs | tlarsen: I like them too, really informative |
| 23:00.15 | solydzajs | tlarsen: who is James btw ?;-) |
| 23:00.29 | tlarsen | solydzajs: James--Crook |
| 23:00.51 | tlarsen | solydzajs: Our first Documenter. He is a "Project Member", but only has permission to edit the wiki, basically. |
| 23:01.04 | solydzajs | tlarsen: isn't he from audacity project ? |
| 23:01.39 | tlarsen | solydzajs: Yes. |
| 23:01.50 | solydzajs | tlarsen: okie dokie :-) |
| 23:02.48 | solydzajs | tlarsen: regarding SiteSettings and HomeSettings logic, basicaly I can create HomeSettings but right now it's going to be the same as SiteSettings :-) |
| 23:02.49 | James--Crook | +2 on using issue tracker as roadmap. A conventional roadmap is only possible when you have a detailed design spec. |
| 23:03.17 | solydzajs | James--Crook: hi :-) |
| 23:03.30 | James--Crook | solydzajs: Hi. How goes it? |
| 23:03.41 | solydzajs | James--Crook: nice wiki pages ;-) |
| 23:03.44 | tlarsen | James--Crook: Heh, and the utter crap floating around in the wiki was my *very* unsuccessful attempt to write a detailed design spec initially. |
| 23:03.47 | solydzajs | James--Crook: pretty good, fixing code :-) |
| 23:04.00 | tlarsen | James--Crook: that *totally* failed, because I couldn't get any meaningful input from the "customers". |
| 23:04.13 | James--Crook | tlarsen: ... only possible when you get feedback. |
| 23:04.33 | James--Crook | tlarsen: yes I can see that. |
| 23:04.38 | tlarsen | James--Crook: Yeah, nothing like having some brainstorm meetings, then trying to write a design doc, and having no one to review it. |
| 23:04.57 | solydzajs | tlarsen: it was before I joined right ? |
| 23:05.28 | James--Crook | tlarsen: I don't know if you're subscribed to gsoc-mentors list... |
| 23:06.02 | James--Crook | I linked to the user stories request from there, so with a bit of luck we'll have some input from peopel who've used the original app. |
| 23:07.31 | James--Crook | solydzajs: How are you dividing the code work amongst you so as not to tread on each others toes? |
| 23:07.45 | tlarsen | James--Crook: I am not. I stay off of the gsoc lists, because they are *way* too noisy. |
| 23:07.49 | tlarsen | Dinner time, be back later. |
| 23:08.28 | solydzajs | James--Crook: I talk with Sverre and Todd and decide who is working on what features. |
| 23:09.58 | James--Crook | solydzajs: cool. What about feature overlap, e.g. read-only-pages (with tables in them) has overlap with questionnaires? |
| 23:10.33 | James--Crook | I'm guessing here that questionnaires will evolve to be like google forms... |
| 23:11.29 | James--Crook | But the user created pages are something similar too - the same code that adds a block of html between two tables on a user created page could equally do the same thing in a questionnaire |
| 23:13.40 | solydzajs | true, I'm not that far in coding :-) basically right now I'm focusing on "Promote to Host" functionality and creation of Programs |
| 23:13.49 | solydzajs | and Todd is working on questionnaires |
| 23:14.40 | James--Crook | ah, I'd misread the response from Todd as being from you. |
| 23:15.04 | solydzajs | :-) |
| 23:15.24 | solydzajs | James--Crook: when do you arrive for Mentor Summit ? |
| 23:15.32 | James--Crook | Had you worked on Django and GAE before? It's one of the things that bothers me. |
| 23:16.31 | James--Crook | I'm actually arriving in SFO on Thursday, but I have to work Friday (at Actel HQ, which happens to be in MV) |
| 23:16.56 | James--Crook | You? |
| 23:17.21 | James--Crook | [I am on the Amarin Thai list - will probably go straight from Actel to Amarin Thai] |
| 23:17.49 | solydzajs | I started to experiment with GAE when it was released and that's about it. But right now I feel pretty good in this environment :-) |
| 23:18.05 | solydzajs | I'm at SFO on Friday 3PM |
| 23:18.23 | solydzajs | James--Crook: where are you from ? |
| 23:18.47 | James--Crook | From UK, but living in Dublin last 17 yrs. You? |
| 23:21.55 | James--Crook | ..completing sentence... one of the things that bothers me is that for most people there is a significant activation-energy to geting involved at all in Melange (GAE, Django.... ) making it hard to contribute smaller pieces. |
| 23:24.32 | solydzajs | From Poland, living in Wroclaw city |
| 23:25.40 | James--Crook | been to a mentor summit before? (me not, this is first time for Audacity) |
| 23:25.41 | solydzajs | James--Crook: yes that's true, I guess we are looking for people who are passioned about GAE, Django or GSoC/GHOP and are willing to learn new things |
| 23:26.11 | solydzajs | James--Crook: nope, first time too. First time in GSoC for NUI Group. But I was a student in 2006 and 2007 |
| 23:26.32 | James--Crook | Student become mentor. Very cool. |
| 23:28.09 | James--Crook | What time is it in your TZ? |
| 23:29.24 | solydzajs | 1:30 AM |
| 23:29.40 | solydzajs | just 1h difference between you and me |
| 23:29.46 | solydzajs | If I remember correctly |
| 23:29.50 | James--Crook | Correct. |
| 23:31.08 | James--Crook | I've one or two things to do before I go to bed. Get a good night's sleep! Talk with you tomorrow I hope. Bfn. |
| 23:32.46 | *** part/#melange James--Crook (n=client@89.100.50.76) |
| 23:39.45 | tlarsen | Too bad James--Crook left. |
| 23:40.15 | tlarsen | solydzajs: Well, for something that Google-scales but is open source, Google App Engine was pretty much the only game in town. |
| 23:40.53 | tlarsen | solydzajs: As for a learning curve for GAE and Django, I do wonder what people thought the current GSoC web app was, just a couple of scripts? |
| 23:41.36 | tlarsen | solydzajs: It is tens of thousands of lines of code, built on top of an even more complex framework that is the "Google platform for Python" for lack of a real name. |
| 23:42.24 | solydzajs | tlarsen: yep I can imagine that. Everything accessing BigTable directly without nice abstraction that we get in GAE |
| 23:42.40 | tlarsen | solydzajs: Heh, Bigtable is just as nice. |
| 23:43.03 | tlarsen | solydzajs: The "abstraction" equivalent to db.Model is protobufs, and it is just as flexible (and multi-language). |
| 23:43.24 | tlarsen | http://code.google.com/p/protobuf/ |
| 23:43.25 | tpb | Title: protobuf - Google Code (at code.google.com) |
| 23:43.58 | tlarsen | Not more difficult, or better or worse, just different. |
| 23:44.06 | solydzajs | tlarsen: yep I read about it and it was open sourced. |
| 23:44.12 | tlarsen | Also, EZT templates instead of Django. Django is much nicer. |