IRC log for #gsoc on 20110113

00:12.45*** join/#gsoc lh (~lh@osuosl/staff/lh)
00:12.45*** mode/#gsoc [+o lh] by ChanServ
01:19.30*** join/#gsoc catfish_man (~david@adium/CatfishMan)
01:19.30*** mode/#gsoc [+o catfish_man] by ChanServ
01:29.39*** join/#gsoc aspotashev (~aspotashe@91.79.52.126)
01:38.20*** part/#gsoc aviraldg (~aviraldg@59.161.188.143)
01:40.26*** join/#gsoc lh (~lh@osuosl/staff/lh)
01:40.26*** mode/#gsoc [+o lh] by ChanServ
02:06.42*** join/#gsoc Upthorn (~ogmar@69.62.144.108)
02:39.17theboltmorning
02:43.39*** join/#gsoc venkatna (~venkatesh@nat/yahoo/x-hdcbdluxttaasxqk)
02:45.11*** join/#gsoc asanka (~asanka@112.135.16.160)
02:54.00*** join/#gsoc catfish_man (~david@adium/CatfishMan)
02:54.00*** mode/#gsoc [+o catfish_man] by ChanServ
03:15.07*** join/#gsoc amaurymedeiros (~amaury@187.114.212.68)
03:23.15*** join/#gsoc wtfness (~dsc@89.211.217.79)
03:31.34*** join/#gsoc yanli (~YanLi@nat/intel/x-jvfpudwqaxqwwmnv)
03:46.14*** join/#gsoc Ivanovic_ (~ivanovic@dtmd-4db2e3a2.pool.mediaWays.net)
03:54.04*** join/#gsoc lh (~lh@osuosl/staff/lh)
03:54.04*** mode/#gsoc [+o lh] by ChanServ
03:56.54*** part/#gsoc lh (~lh@osuosl/staff/lh)
04:05.55*** join/#gsoc pwbarnes (~nman64@fedora/nman64)
04:09.02*** join/#gsoc Kapace (~david@d205-250-124-216.bchsia.telus.net)
04:18.46*** join/#gsoc laknath (~buddhika@124.43.251.26)
04:27.17*** join/#gsoc robbyoconnor (~wakawaka@guifications/user/r0bby)
04:43.59*** join/#gsoc brownfox (~numbers32@70-91-62-42-BusName-middletown.nj.hfc.comcastbusiness.net)
04:55.31*** join/#gsoc lh (~lh@osuosl/staff/lh)
04:55.31*** mode/#gsoc [+o lh] by ChanServ
05:11.04*** join/#gsoc lh (~lh@osuosl/staff/lh)
05:11.04*** mode/#gsoc [+o lh] by ChanServ
05:30.16*** join/#gsoc holger_ (~holger@piratenpartei/ni/holger)
05:48.04*** join/#gsoc dukeleto (~leto@turkeyberry.sgn.cornell.edu)
05:52.10*** join/#gsoc can (~IceChat7@202.129.234.222)
05:52.35*** join/#gsoc milki (~milki@s230-180.resnet.ucla.edu)
05:54.15*** join/#gsoc idlecool (~idlecool@117.200.35.235)
06:01.07*** join/#gsoc otaciliofl (~otacilio@189.71.115.46)
06:14.43*** join/#gsoc laknath_ (~buddhika@124.43.251.26)
06:28.37*** join/#gsoc Soliton (~Soliton@wesnoth/developer/soliton)
06:39.02*** join/#gsoc kstar (~kstar@kde/developer/asimha)
07:17.51*** join/#gsoc GautamGupta (~GautamGup@59.94.103.50)
07:19.26*** join/#gsoc z4chh (~zach@aolclient-67-9-195-57.aol.hot.res.rr.com)
07:37.03*** join/#gsoc ianmcorvidae (~ianmcorvi@fsf/member/ianmcorvidae)
07:41.08*** join/#gsoc krkhan (~Khan@eclipse.sh3lls.net)
07:41.18*** join/#gsoc ricky (~ricky@fedora/ricky)
07:49.44*** join/#gsoc araujo (~araujo@gentoo/developer/araujo)
07:49.48*** join/#gsoc Upthorn (~ogmar@69.62.144.108)
08:06.10*** join/#gsoc Kaetemi (Kaetemi@pdpc/supporter/base/kaetemi)
08:12.29*** join/#gsoc superpointer (~gpolitis@pdc35-1-82-242-133-140.fbx.proxad.net)
08:15.34*** join/#gsoc spectie (~fran@unaffiliated/spectie)
08:19.56*** join/#gsoc wolf (~MrWolf@cs27009233.pp.htv.fi)
08:20.03*** join/#gsoc mhutch_ (~Michael@nat/novell/x-fcefcpeuwrupyvsp)
08:24.03*** join/#gsoc xparo (73f83214@gateway/web/freenode/ip.115.248.50.20)
08:25.29*** join/#gsoc _Samo (~chatzilla@84.76.170.103)
08:26.03kaiyawns
08:29.12dreimark!next
08:29.13socinfodreimark: "next" is February 14, 2011: Open source projects announce Grand Prize Winners
08:37.32*** join/#gsoc napster00 (~chatzilla@27.107.130.173)
08:56.15*** join/#gsoc allisterb (~allisterb@186.45.18.99)
08:58.50*** join/#gsoc EFBL (~EFBL@econ01.iibf.hacettepe.edu.tr)
08:59.36*** join/#gsoc can (~IceChat7@202.129.235.20)
09:01.00*** join/#gsoc Guest45821 (~cilution@c-69-180-141-47.hsd1.mn.comcast.net)
09:02.41*** join/#gsoc napster00 (~chatzilla@27.107.130.173)
09:25.37*** join/#gsoc aviraldg (~aviraldg@117.200.80.230)
09:26.55*** join/#gsoc Ivanovic_ (~ivanovic@wesnoth/developer/ivanovic)
09:31.34*** join/#gsoc k0p (~bastiao@bl15-96-8.dsl.telepac.pt)
09:49.26*** join/#gsoc napster00 (~chatzilla@27.107.130.173)
09:59.00*** join/#gsoc spectie (~fran@unaffiliated/spectie)
10:33.54*** join/#gsoc otaciliofl (~otacilio@189.71.115.46)
10:45.17*** join/#gsoc aspotashev (~aspotashe@91.79.52.126)
10:48.56*** join/#gsoc Chainsaw (~chainsaw@gentoo/developer/atheme.member.chainsaw)
11:13.11*** join/#gsoc neL (~neL@2001:df0:92:0:215:17ff:fefd:29bc)
11:27.38*** join/#gsoc Neo-- (~neo@93-103-53-209.dynamic.t-2.net)
11:37.33*** join/#gsoc RT|Chatzilla (~rt@reactos/tester/RT)
11:48.54*** join/#gsoc nmudgal (d2d46c84@gateway/web/freenode/ip.210.212.108.132)
11:57.43*** join/#gsoc GautamGupta (~GautamGup@59.94.103.5)
12:13.25*** join/#gsoc nmudgal (d2d46c84@gateway/web/freenode/ip.210.212.108.132)
12:14.56*** join/#gsoc can (~IceChat7@202.129.235.24)
12:16.11*** join/#gsoc keheliya (~keheliya@101.2.184.41)
12:17.49*** join/#gsoc andre__ (~andre@192.100.124.156)
12:17.49*** join/#gsoc andre__ (~andre@Maemo/community/bugmaster/andre)
12:37.29*** join/#gsoc skwashd (~skwashd@phpgroupware/skwashd)
13:05.05*** join/#gsoc goose (~goose@samson.honk-honk.org)
13:14.21*** join/#gsoc WonTu (~WonTu@p57B5411A.dip.t-dialin.net)
13:14.35*** part/#gsoc WonTu (~WonTu@p57B5411A.dip.t-dialin.net)
13:23.08*** join/#gsoc idlecool (~idlecool@117.200.33.222)
13:23.32*** join/#gsoc lucaz (~lucaz@186.19.147.149)
13:27.15*** join/#gsoc promulo (~promulo@187.114.217.136)
13:29.02*** join/#gsoc aspotashev (~aspotashe@91.79.52.126)
13:39.23*** join/#gsoc jacktheripper (~jacktheri@41.68.33.111)
13:40.05*** join/#gsoc umashanthi (~umashanth@112.135.136.196)
13:42.26*** join/#gsoc amaurymedeiros (~amaury@187.114.212.68)
13:49.04*** join/#gsoc pwbarnes (~pwbarnes@fedora/nman64)
13:59.00*** join/#gsoc allisterb (~allisterb@186-45-42-157.dynamic.tstt.net.tt)
14:03.24*** join/#gsoc aspotashev| (~aspotashe@91.79.126.2)
14:03.51*** join/#gsoc laknath (~buddhika@112.135.68.112)
14:05.07*** join/#gsoc keheliya (~keheliya@101.2.184.41)
14:18.04*** join/#gsoc nmudgal (d2d46c84@gateway/web/freenode/ip.210.212.108.132)
14:23.11*** join/#gsoc napster00 (~chatzilla@27.107.213.16)
14:32.10*** join/#gsoc pcviruz (7aa2035b@gateway/web/freenode/ip.122.162.3.91)
14:32.55pcviruzanyone working o tux 4 kids??
14:35.11*** join/#gsoc akssps011 (~Siddharth@59.178.177.13)
14:35.11*** join/#gsoc akssps011 (~Siddharth@kde/developer/siddharthsrivastava)
14:35.25*** join/#gsoc komputes (~komputes@ubuntu/member/komputes)
14:36.30aviraldgpcviruz: ?
14:37.10pcviruzi mean is anyone working on tux 4 kids???
14:37.35aviraldgpcvirus: in GCI, no, since it's over
14:37.40aviraldgbut otherwise, yes
14:37.45aviraldgwhy?
14:38.13pcviruzactually i m tthinking
14:38.25pcviruzto work on it
14:38.41pcviruzbut cant get a starting
14:41.28aviraldgpcviruz: Talk to David <davidstuartbruce@gmail.com>
14:41.58*** join/#gsoc skwashd (~skwashd@phpgroupware/skwashd)
14:42.01pcviruzthanks aviral
14:42.44pcviruzaviraldg: is he on this channel
14:43.05aviraldgNo, he's not on IRC
14:43.26aviraldgif you want any help with the code, esp. Factoroids, you could even ask me
14:43.40aviraldgfor starters you might want to clone the git repository
14:46.05kaiaviraldg: you might not want to paste people's email addresses in an archived channel
14:46.31aviraldgkai: hmmm...
14:46.48aviraldgbots, right?
14:46.57*** part/#gsoc neL (~neL@2001:df0:92:0:215:17ff:fefd:29bc)
14:47.00kaispam crawlers
14:47.15aviraldgFunny thing though, I got his mail by googling his name...
14:47.25aviraldgpublic git logs
14:47.33kaifair enough :)
14:47.39kaibut no need to make it worse :)
14:47.43aviraldgyeah
14:47.51aviraldgwill keep that in mind
14:54.15*** join/#gsoc sioraiocht (~tomh@unaffiliated/sioraiocht)
15:13.27*** part/#gsoc umashanthi (~umashanth@112.135.136.196)
15:20.35aviraldgpcviruz: He's online right now; you might want to drop him a mail....
15:20.48*** join/#gsoc Kaythxbye (~samuel@p57ADD54A.dip.t-dialin.net)
15:21.02pcviruzthanks aviral
15:21.35aviraldgyou're welcome
15:22.00Kaythxbyesomeone student here from outside from the USA? Then you might be interested in this discussion, since there's the question that the method Google wants to use to transfer money doesn't work outside the US: http://groups.google.com/group/gci-discuss/browse_thread/thread/8ea13c6f1975aaa2
15:23.56amaurymedeirosKaythxbye, thanks! I'll take a look
15:24.59jacktheripperKaythxbye, :S
15:26.00KaythxbyeI hope they think about theitr plans again
15:28.33amaurymedeirosKaythxbye, it's just for Google Code-in, isn't it?
15:29.36Kaythxbyeyepp, as far as i know (I found the passage with the AMEX cheque in GCI's FAQ)
15:29.48Kaythxbyesorry that I didn't specify that in my link...
15:29.54*** join/#gsoc Noughmad (~quassel@89.142.246.193)
15:30.16Kaythxbyei don't know if it's related to gsoc, too
15:31.17amaurymedeirosI hope not
15:31.35Kaythxbyethat'd be seriously bad
15:32.56jacktheripperI don't see what's the wrong with the bank account way
15:33.00jacktherippers/the//
15:34.33Kaythxbyeand even if they don't want to do a bank transfer (too high costs?) they can use normal cheques, I think. But too high costs shouldn't bother a enterprise like Google too much ;-)
15:36.27Kaythxbyelet's wait a few hours, since it's 7:30 a.am at Google's HQ now and Carol is probably not at work now...
15:42.37Kaythxbyeah they seem to have a solution - as it's sstated in the latest message in the thread :-)
15:42.52Kaythxbyes/sstated/stated/
15:44.36jacktheripperoh good
15:44.41*** join/#gsoc jordan___ (~jordan@unaffiliated/jordan---/x-8776605)
15:44.43jacktheripperI want ma monies!
15:46.38*** join/#gsoc dzhus (~sphinx@95-27-175-98.broadband.corbina.ru)
15:59.17*** join/#gsoc barra_home (barra@g227120044.adsl.alicedsl.de)
15:59.19barra_homehola
15:59.41barra_homeI was sent here as kblin might be able to help me with his insight :-)
16:00.06barra_homeI'm involved in an open source project and we consider to use from SVN to git or hg down the line
16:00.25barra_homeand we were a bit worried how switching to a dvcs might affect our art workflow
16:00.48*** join/#gsoc z4chh (~zach@aolclient-67-9-195-57.aol.hot.res.rr.com)
16:01.04barra_homewe're looking for some pointers how to make it easy for artists to contribute to the project even when using a dvcs
16:01.18*** join/#gsoc jordan___ (~jordan@unaffiliated/jordan---/x-8776605)
16:01.30*** join/#gsoc amaurymedeiros (~amaury@187.114.212.68)
16:01.49kaibarra_home: out of curiosity, who sent you here? :)
16:01.55Ivanovickblin: no idea what your current status of "wombat" is/was, but it *might* be what could help them
16:01.59Ivanovicof course!
16:02.08kaiah
16:02.10barra_homeI blame Ivanovic :-)
16:02.58barra_homefor the good pointer, that is
16:03.01kaibarra_home: ok, I didn't check in a while, but my last information was that DCVS is a bad idea for art
16:03.10barra_homehmm
16:03.27barra_homedo you happen to know how OSS game projects usually tackle this?
16:03.29*** join/#gsoc spectie (~fran@180.Red-81-39-98.dynamicIP.rima-tde.net)
16:03.32*** join/#gsoc spectie (~fran@unaffiliated/spectie)
16:03.38kaidepends a bit on how much churn you have in art of course
16:03.38barra_homewe are working with two kinds of art/assets
16:03.48barra_home1. baked assets that are needed to run the game
16:03.53Ivanovickai: that is why the idea on wombat which would provide some "decent" webinterface for artists
16:04.01barra_home2. raw assets that are basically the source versions of the baked assets
16:04.03Ivanovicso that no direct usage of tools is required
16:04.13kairight
16:04.32barra_homethe baked assets are prerendered versions of the raw assets
16:04.38barra_home(this is an isometric 2d game)
16:04.42Ivanoviccurrently their artwork workflow appears to be "send the stuff to a core dev by mail and they got to handle it somehow"
16:04.56barra_homehaha, that's not that sophisticated :-)
16:05.16kaibarra_home: ok, I don't have much experience with how other projects do this, but here's how we do this at worldforge
16:05.22Ivanovicsure, this technique would still work with a dvcs...
16:05.48kaiwe had CVS with all our stuff in, and pserver would tank every time someone checked out the artwork in one go
16:05.49*** join/#gsoc dzhus (~sphinx@95-27-175-98.broadband.corbina.ru)
16:06.16kaithen, this newfangled SVN project released a 0.4.something, and we switched to that for artwork
16:06.34*** join/#gsoc welterde (welterde@thinkbase.srv.welterde.de)
16:06.48kaisome years ago (when we got into gsoc), we ditched CVS for code, and moved that to git
16:06.57kaiwe still use svn for artwork
16:06.58barra_homealrighty
16:07.11barra_homewhat about artwork that is needed to run the game?
16:07.20barra_homebecause that needs to be in sync with the code I assume
16:07.28kaiartwork here means 3d models, 2d images, music, GUI elements
16:07.46barra_homeyep, let's use the term "assets"?
16:08.22kaihow many game clients do you have?
16:08.24*** join/#gsoc idlecool (~idlecool@117.200.33.191)
16:08.38barra_homewe work on a single game, not an engine
16:08.49kaiwe had some fun with this for a while as we had a 2d isometric client, and a couple of 3d clients
16:09.02barra_homeso this single game is 2d isometric
16:09.04kaibut now we're down to one actively developed 3d client
16:09.14barra_homebut this isometric 2d art is often based on 3d models
16:09.36kaiso we basically have one directory for the "source" assets and one directory for the "baked" assets
16:09.47barra_homeso we have to store raw assets (3d models, textures) and baked assets somewhere in version control
16:09.55barra_homeyep, that's what we do as well
16:10.01barra_homewe have a media branch with raw assets
16:10.14barra_homeand the baked assets reside close to the code as they're needed to run the game
16:10.32kaiok, so here's what I'd do
16:10.33barra_homethat might be easier to get the idea: http://wiki.parpg.net/How_to_use_SVN#Repository_structure
16:11.51kaigo to a DVCS for code. It's soo much nicer. I'm personally partial to git, but this somewhat depends on the "userbase" for the source code repository
16:12.00kaistick to svn for the artwork
16:12.01*** join/#gsoc chinthakarukshan (~IceChat7@202.129.235.24)
16:12.13barra_homehow would we keep baked assets in sync with the code?
16:12.24barra_homebecause they often depend on each other
16:12.33kaiadd a script to your codebase that gets the baked assets from svn
16:12.34barra_homee.g. map files are basically baked assets as well
16:12.43barra_homenah, how would you sync revisions
16:12.59barra_homecertain code revisions will only work with certain baked asset revisions
16:13.17barra_homethis can be tricky if you have to check when a bug was introduced
16:13.22barra_homeyou go back some revisions in code
16:13.23kaihow big are your assets, and how many binary files change over one iteration?
16:13.38barra_homebut you also need the right assets that work with this code revision
16:13.57barra_homecould you elaborate on the iteration term?
16:14.13kaifrom one release to the next
16:14.25barra_homehmm, that's actually hard to say
16:14.37kaiDVCSes suck for binary data. that tends to not diff very well
16:14.47barra_homein which regard?
16:15.09kaiWorldForge's media repository is 7 GB in size, and there's quite some churn when we have an active artist
16:15.16barra_homewe don't really have to store the media branch with the raw assets in a dvcs
16:15.17gevaertss/for binary data//
16:15.20gevaertsruns
16:15.25barra_homewe could stick to SVN for that BUT
16:15.43barra_homein this case artists will have to use two different types of version control
16:15.51barra_homebecause they'll commit raw and baked assets
16:16.16kaihmmm
16:16.23Ivanovicbarra_home: can't they just commit the raw work and some daily script on a server generates the baked versions?
16:16.25barra_homeyep, it's somewhat tricky :-)
16:16.32kaiso you can't script the baking?
16:16.41barra_homeI have no idea how :-)
16:16.47barra_homewe don't have root access to the server
16:16.56barra_homeSVN & trac is hosted by a 3rd party
16:17.01Ivanovicbarra_home: no need to have it on "this" server
16:17.03barra_homekeep in mind this is a somewhat smaller project
16:17.10Ivanovicany server with an account that can commit would be possible
16:17.15barra_homehmm
16:17.30Ivanovic(even if this server belonged to dev ABC who ran the script automagically on his local system)
16:17.35kaimost of what we do to convert e.g. raw textures to "game-ready" textures is scaling them down
16:17.46barra_homewe don't use textures in the game kai
16:17.55barra_homeremember: this is a 2d game
16:17.56kaibarra_home: as an example
16:18.06barra_homeyep sure, just trying to underline that it's a bit more tricky
16:18.18barra_homebecause artists actually have to tweak the baked assets a bit
16:18.22kaiI assumed you had a script that'd take the 3d model and create sprites from them
16:18.24Ivanovichow are the raw versions transalted to baked ones?
16:18.40barra_homee.g. they have to apply some manual X & Y shifts so the art is correctly positioned
16:18.53barra_homethis information is stored in external XML files that reside close to the art file
16:19.00kaibarra_home: ok, that's a bit more tricky
16:19.04barra_homeyep
16:19.35kaiI was toying with a script like that when we decided to discontinue the 2d client
16:19.52kaibefore we decided to discontinue it, of course :)
16:20.18kaianyway, so here's how I'd see a good workflow..
16:21.07kaiyour artists create raw and baked assets and commit them into the asset repository
16:22.00kaithey tag the baked assets with some information to indicate which version of your game they are designed for
16:22.39barra_homeand programmers would sync the art with the git repo?
16:22.50kaiin your game build system, you add a "media" command, so e.g. "make media" will get the art for the correct version
16:23.02kaier, current version
16:23.59kaimake media gets this information from a file that keeps track of the assets used, and the respective revision or somesuch
16:24.06barra_homehmm
16:24.17barra_homethat actually feels more complicated than our status quo :-/
16:24.26barra_homebut this is simply a tricky field
16:24.57barra_homebecause in this case the artists would be responsible for tagging the assets with versioning information
16:25.08kainot necessarily, actually
16:25.08barra_homeI actually think we should do some performance tests
16:25.19barra_homebasically import our media branch into a git repo
16:25.23barra_homeand see how it performs
16:25.25kaisure, do that
16:25.32kaifor us it was out of the question
16:25.44barra_homealrighty, that brainstorming has helped :-) thanks a bunch
16:26.02kaino one wants to grab 7 GB of artwork jsut for working on the terrain generation library
16:26.30sfbAmen.
16:26.46kaibarra_home: feel free to email me or drop by here if you want to discuss this some more
16:27.19barra_homealrighty, i'll add gsoc to my channel autojoin list
16:27.35kaiit's kai(dot)blin(at)gmail(dot)com for email
16:28.18barra_homeIRC is fine with me
16:28.35barra_homeI'm usually not the guy who sends around lenghty emails
16:29.06barra_homeI'll flesh out the topic in more detail here, just in case you're interested in what we'll end up doing: http://wiki.parpg.net/Distributed_version_control_software
16:29.32kaibarra_home: I still think separate repos and automation is the way to go
16:29.50barra_homefair enough :-) I'll consider this
16:30.47kaiI've been working on a web frontend to hide the actual backend from the artists completely, based on my frustration on trying to explain svn to 3d modellers
16:30.51*** join/#gsoc Gracenotes (~person@wikipedia/Gracenotes)
16:31.49barra_homehehe, yep, that can be frustrating indeed :-)
16:31.49*** join/#gsoc promulo (~promulo@150.165.63.86)
16:31.49sfbkai: I mentioned to barra_home that I don't need revision - I just need a means of fetch/upload for artists.
16:31.56kaiyeah
16:32.09barra_homeI actually brought up the topic at stackoverflow lately
16:32.16sfbkai: So my intention is to just add another dialog to my Object Viewer tool that sends a chosen file to a NeL service which stores it on the server.
16:32.16kaiunless you want to go back in time and need media that matches the old code
16:32.32barra_homeand they gave a good pointer: use cheat sheets for common tasks in a field
16:32.41sfbI don't need media that matches old code because of the nature of our system.
16:32.46barra_homefor details see http://stackoverflow.com/questions/4389578/can-artists-realistically-cope-with-distributed-version-control-in-an-open-sour
16:32.50kaibarra_home: and I say "use automation" :)
16:32.51sfbThe *sheets* are version controled.
16:33.11sfbSo when I run my build_gamedata script the sheets determine which files are used.
16:33.29barra_homeI'm not saying that automation wouldn't be good
16:33.50barra_homebut I'm slightly worried about the time and the effort it will take up to set up such an infrastructure
16:34.09kaibarra_home: hmm, I see that mercurial seems to have subversion subrepos
16:34.14kaithat sounds interesting
16:35.26sfb<3 Hg
16:36.13kaiit's too "almost, but not quite" git for my taste
16:38.37barra_homegood point about subrepos kai :-)
16:38.48barra_homeI'll dig deeper there, thanks for the pointer
16:38.58barra_homeand the game is already written in python anyway :-)
16:39.28barra_homeso hg might be a valid choice over git for philosophical reasons
16:39.33kaithe subrepo thing seems to do what I proposed with the automation
16:39.51kaidunno, I'd stick to technical reasons over philosophical reasons
16:40.02kaiI keep all my python projects in git
16:40.09kaias well as my perl and C projects
16:40.11*** join/#gsoc svaksha (~svaksha@unaffiliated/svaksha)
16:40.23kaiall of them work the same way :)
16:40.25gevaertsWhat's the philosophical reason for wanting your VCS to be written in the same language as the project you're managing with it?
16:40.54kaigevaerts: it's an excuse to not use version control with VB.Net code
16:41.20aviraldgloves the above post
16:42.27kaibarra_home: in any case, if getting the artists to use your VCS is an issue, wombat might be a viable option
16:42.44kaiit currently only has a SVN backend, but the code's pretty modular
16:42.58kaias long as the VCS understands the concepts of add, delete and update
16:43.21barra_homeI guess it's the silly idea that you could dig through the source code if necessary to get an idea how it works gevaerts
16:43.36barra_homefor whatever reason somebody might actually come up with such a silly idea :-)
16:43.51gevaertsbarra_home: but what do you do if you have a project that uses *two* languages?
16:44.02barra_homewe don't :-)
16:44.08kaigevaerts: use a VCS written in the more painful one
16:44.21gevaertsSounds like a plan :)
16:44.30kaiso people don't get distracted hacking on the VCS
16:44.36barra_homedarcss it is, in this case!
16:44.54kaior just use a closed-source VCS
16:45.04kaimicrosoft source safe comes to mind ;)
16:45.21barra_homebut you've got a point there: the main reason should be features, performance, 3rd party client support for win32 and mac
16:46.20kaisounds reasonable
16:46.32gevaertsI'm pretty sure that with a more or less advanced VCS the implementation language will be the least of your worries if you want to fix a bug in it
16:46.58gevaertsYou'll first have to understand its inner workings anyway, and that's probably not a five minute job
16:47.32kaiyeah, it's usually faster to bitch at the VCS upstream :)
16:48.33*** join/#gsoc laknath (~buddhika@112.135.94.203)
17:05.59*** join/#gsoc lh (~lh@osuosl/staff/lh)
17:05.59*** mode/#gsoc [+o lh] by ChanServ
17:07.42*** join/#gsoc brion (~brion@wikipedia/Brion-VIBBER)
17:08.02*** join/#gsoc mhutchm (~mhutchmac@209-6-53-164.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com)
17:11.17*** join/#gsoc m4k3r (~maker@host77-80-dynamic.20-87-r.retail.telecomitalia.it)
17:32.18*** join/#gsoc carols (~carols@nat/google/x-djfgutzwndjbcxdy)
17:32.18*** mode/#gsoc [+o carols] by ChanServ
17:34.35*** join/#gsoc andre__ (~andre@Maemo/community/bugmaster/andre)
17:35.05*** join/#gsoc milki (~milki@s230-180.resnet.ucla.edu)
17:36.08*** join/#gsoc laknath (~buddhika@112.135.94.8)
17:41.46*** join/#gsoc nikre (~n1kr3@94.123.129.187)
17:52.51*** join/#gsoc thiago (~thiago@kde/thiago)
17:55.04*** join/#gsoc napster00 (~chatzilla@49.201.3.190)
17:55.10*** join/#gsoc Nightrose (~lydia@kde/lydia)
18:07.11*** join/#gsoc nmudgal (d2d46c84@gateway/web/freenode/ip.210.212.108.132)
18:12.22*** join/#gsoc napster00 (~chatzilla@49.201.3.190)
18:14.35*** join/#gsoc Nightrose (~lydia@kde/lydia)
18:15.46*** join/#gsoc andrei1089 (~andrei108@81.18.92.10)
18:17.12*** join/#gsoc brion (~brion@wikipedia/Brion-VIBBER)
18:24.01*** join/#gsoc khetzal (~quetzal@2a01:e35:8b51:6f0:6ef0:49ff:fee6:8e93)
18:34.11*** join/#gsoc catfish_man (~david@adium/CatfishMan)
18:34.11*** mode/#gsoc [+o catfish_man] by ChanServ
18:44.50*** join/#gsoc schumaml (schumaml@dslb-178-002-176-194.pools.arcor-ip.net)
18:55.51*** join/#gsoc danielmarth (~quassel@212-183-46-144.adsl.highway.telekom.at)
18:56.06danielmarthcarols: hi, can you tell me if a student still has an open task?
18:56.20carolsdanielmarth: SRabbelier would be a better help for that than i would
18:56.30danielmarthcarols: thanks :)
18:56.34carolsyw
18:57.02danielmarthSRabbelier: can you tell me if a student has a task open? i'm 10th at the moment and i want to check if i can still drop out of top-10
18:57.33SRabbelierdanielmarth: we still have to run the re-count-all-tasks routine, so don't count on anything yet
18:57.55danielmarthSRabbelier: ok, thanks :) when will this be done?
18:58.30SRabbelierdanielmarth: when the last tasks have been reviewed
18:58.36danielmarthok, thanks
19:01.22*** join/#gsoc llnz (~lee@router.harmonic.co.nz)
19:06.34*** join/#gsoc kane77 (~kane@194.1.130.108)
19:07.34Ivanovicdanielmarth: to be 100% sure: wait for the announcement of the final results
19:07.44Ivanovictill then a whole lot can (theoretically) still happen
19:07.46Ivanovic;)
19:07.57gevaertsUntil then, enjoy tea and cookies here :)
19:08.01gevaertsserves some
19:08.17danielmarthi guess i can't do anything else ;)
19:09.01danielmarthit's the only student that can still kick me out of the top-10, and which mentor would reject a work submission now?
19:09.59aviraldgdanielmarth: ?
19:10.12danielmarthaviraldg: ?
19:10.39aviraldgwho?
19:11.15danielmarthaviraldg: http://www.google-melange.com/gci/student_ranking/show_details/google/gci2010/aoihana 1 point behind me, the only one that can kick me out
19:12.08*** join/#gsoc nmudgal (d2d46c84@gateway/web/freenode/ip.210.212.108.132)
19:12.45*** join/#gsoc nmudgal (d2d46c84@unaffiliated/nmudgal)
19:12.45*** join/#gsoc nmudgal (d2d46c84@gateway/web/freenode/ip.210.212.108.132)
19:13.14carolsmunches tea and cookies
19:13.16carolsthanks gevaerts
19:13.30gevaertsYou're welcome!
19:14.08Ivanovicdanielmarth: new work submissions are not possible since time is out
19:14.39danielmarthIvanovic: i know, but someone is now in front of me because he submitted work before the deadline, but the task was closed today
19:15.05aviraldgdanielmarth: That can still happen.
19:15.27aviraldgbut what Ivanovic means is that 1. new tasks cannot be claimed 2. new submissions cannot be made
19:15.42danielmarthyes, i know that :)
19:15.56*** join/#gsoc amaury_ (~amaury@187.114.212.251)
19:15.59andre__patience. as usual. patience.
19:16.16carols!patience
19:16.16socinfocarols: "patience" is Patience is very important in GSoC/GCI. Relax and go code something useful.
19:16.30aviraldgcarols: :)
19:16.46aviraldgyou actually had the bot remember that?
19:16.57carolsbut of course. it's very important
19:17.18carols!couch
19:17.18socinfocarols: "couch" is An open source couch on which to chill.
19:17.27carolssits on couch and munches cookies
19:17.45aviraldg:O
19:17.59aviraldgcan put stuff in Couch. CouchDB!
19:18.23gevaerts!cookies
19:18.23socinfogevaerts: Error: "cookies" is not a valid command.
19:18.27gevaerts!tea
19:18.28socinfogevaerts: Error: "tea" is not a valid command.
19:18.32gevaertsThe bot is broken!
19:18.42aviraldg!learn
19:18.43socinfoaviraldg: Invalid arguments for learn.
19:18.52aviraldg!learn cookies Yummy!
19:18.53socinfoaviraldg: Invalid arguments for learn.
19:19.03aviraldghmmm...
19:20.01llnzi think it's "!learn cookies as Yummy!", iirc
19:20.10aviraldgoh
19:20.26llnzalso, try priv message bot for help
19:20.33gevaerts!learn tea as Hot!
19:20.34socinfogevaerts: The operation succeeded.
19:20.34aviraldgwell, I'll leave it up to Carol, haven't tasted them anyway
19:30.50*** join/#gsoc sioraiocht (~tomh@unaffiliated/sioraiocht)
19:37.27aviraldgSRabbelier: there?
19:38.05SRabbelieraviraldg: yeah
19:38.15aviraldgremember the task I mailed you about?
19:38.39SRabbelieraviraldg: I've gotten a lot of emails about a lot of tasks, please be more specific
19:38.39aviraldgdid you, or anyone from the administrative (?) team explicitly "validate" it?
19:38.51aviraldgif not, then I may have a bug report
19:38.52SRabbelieraviraldg: link?
19:39.26aviraldghttp://www.google-melange.com/gci/task/show/google/gci2010/tux4kids/t129463056359
19:40.14aviraldgSRabbelier: ?
19:40.16SRabbelieraviraldg: the current status of that task is Closed
19:40.26aviraldgyes, but I mean to ask that
19:40.31aviraldgthat particular task
19:40.40SRabbelieraviraldg: I manually fixed that one didn't I?
19:40.51aviraldgoh, that was done manually?
19:41.24aviraldgthe reason I was asking
19:41.36aviraldgwas that I got "log emails" like:
19:42.34aviraldgOn 11th January 2011 20:31, by Google Open Source Programs Automatic Updater: ¶
19:42.38aviraldg(This task was marked invalid by an administrator. Please contact the Google Open Source Programs team if you have any questions regarding the same.)
19:42.40aviraldgChanges: User-MelangeAutomatic; Action-None; Status-Invalid
19:42.42aviraldgOn 11th January 2011 21:59, by Google Open Source Programs Automatic Updater: ¶
19:42.46aviraldg(The Melange Automated System has detected that the deadline has been passed and no more work can be submitted.)
19:42.48aviraldgChanges: User-MelangeAutomatic; Action-Deadline passed; Status-NeedsReview
19:42.50aviraldgoops
19:42.55aviraldgsorry for a direct paste
19:43.18*** join/#gsoc barra_away (barra@f050134129.adsl.alicedsl.de)
19:43.38aviraldgSRabbelier: anyway, the log makes it look like the task was invalid first, and then it changed to "NeedsReview" because the deadline was passed, so I thought it was a bug
19:44.03SRabbelieraviraldg: no, it was marked as invalid first, and then as NeedsReview I guess
19:44.33aviraldgSRabbelier: so, not a bug, right?
19:44.58SRabbelieraviraldg: nope
19:48.50aviraldgSRabbelier: just wanted to confirm, thanks anyway
19:49.11SRabbelieraviraldg: thanks for checking
19:55.35*** join/#gsoc allisterb (~allisterb@186-45-22-133.dynamic.tstt.net.tt)
19:56.54*** join/#gsoc ricky (~ricky@fedora/ricky)
20:45.56*** join/#gsoc dhaun (~geeklog@p54A11888.dip0.t-ipconnect.de)
20:51.22*** join/#gsoc catfish_man (~david@adium/CatfishMan)
20:51.22*** mode/#gsoc [+o catfish_man] by ChanServ
20:58.14*** join/#gsoc spectie (~fran@unaffiliated/spectie)
21:19.02*** join/#gsoc Chainsaw (~chainsaw@gentoo/developer/atheme.member.chainsaw)
21:41.20*** join/#gsoc joeyadams (~joeyadams@208.96.182.115)
21:41.36*** join/#gsoc jacktheripper (~jacktheri@41.68.33.111)
21:44.17*** join/#gsoc kaydsoft (~kaydsoft@88.247.29.213)
21:53.58*** join/#gsoc secureendpoints (~chatzilla@75.99.247.221)
22:00.26*** join/#gsoc asmeurer (~asmeurer@c-68-42-39-41.hsd1.nm.comcast.net)
22:01.14*** join/#gsoc secureendpoints (~chatzilla@75.99.247.221)
22:12.22*** join/#gsoc kstar (~kstar@kde/developer/asimha)
22:13.28*** join/#gsoc brion (~brion@wikipedia/Brion-VIBBER)
22:38.17*** join/#gsoc RT|Chatzilla (~rt@reactos/tester/RT)
22:39.35*** join/#gsoc jacktheripper (~jacktheri@41.68.12.238)
22:42.53*** join/#gsoc thiago (~thiago@kde/thiago)
22:48.09*** join/#gsoc yanli (~YanLi@114.249.220.115)
22:49.11m4k3rcarols:  the 'proof of enrollment' for GCI must be in English language?
22:49.37carolsm4k3r: as long as its an official document from your school adhering to the guidelines laid out in the email, it doesn't have to be in english
22:50.33m4k3rGreat, thank you.
22:55.16*** join/#gsoc allisterb (~allisterb@186-45-41-20.dynamic.tstt.net.tt)
22:55.44*** join/#gsoc Peter17 (~peter@wikipedia/Peter17)
23:09.53*** join/#gsoc aviraldg (~aviraldg@117.200.80.230)
23:19.46*** join/#gsoc thiago_home (~thiago@kde/thiago)
23:20.14*** join/#gsoc madewokherd (~urk@c-24-118-59-147.hsd1.mn.comcast.net)
23:28.47*** join/#gsoc aviraldg (~aviraldg@117.200.80.230)
23:31.10*** join/#gsoc thiago_home (~thiago@kde/thiago)
23:41.23*** join/#gsoc thiago_home (~thiago@kde/thiago)
23:51.24*** join/#gsoc thiago_home (~thiago@kde/thiago)

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