2011-03-21.log

--- Log opened Mon Mar 21 00:00:04 2011
--- Day changed Mon Mar 21 2011
sebastienbI think it would be good to do that soonish.  I don't have one immediately on hand, but I think I need to dig one up for other reprap matters.00:00
jrayhawkI guess I could look into getting a VPS set up for you on pdx.edu's infrastructure so long as nothing profitable happens on it.00:00
jrayhawkNothing directly profitable, anyway.00:01
sebastienbThat's kind, but I think reprap is moving house to another server soon anyways, so I may bring it up with the fellow who's offering us space.00:01
sebastienbThat may be best, since that may be the same or similar server to where we'll be running piny anyways.00:02
sebastienbI'll look into it.00:02
sebastienbI also need to be a grown up and start trying read piny's code, learn django, etc.00:03
-!- ThomasEgi [~thomas@panda3d/ThomasEgi] has quit [Remote host closed the connection]00:03
jrayhawkIf that prove untenable, you're also free to complain at me until I write better documentation.00:04
jrayhawkproves00:04
sebastienbI'd suggest a 2 line explanation here:00:05
sebastienbhttp://piny.be00:05
jrayhawkHmm, yeah, I suppose.00:05
sebastienbOf what piny actually is, for new folk.00:05
jrayhawkI should really rename piny-the-codebase or piny-the-hosting-service to something else.00:05
sebastienbyou're in portland, btw?00:06
jrayhawkYeah.00:06
sebastienbYou may want to ping folk:00:06
sebastienbhttp://forums.reprap.org/read.php?195,57338,page=100:07
sebastienbOur portland forum.00:07
jrayhawkAbout Piny?00:07
sebastienbAbout portland, if you're doing up a mendel?00:07
jrayhawkOh. 3d printing isn't particularly useful to any of my projects; maybe someday, but not today.00:08
sebastienbBut I do think we need to ping reprap-dev regrarding piny & gitduino by the end of the week.  Self-hosting may be a good waypoint there.00:08
jrayhawkI'll pass that on to some other people who probably will be interested.00:09
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 255 seconds]00:10
sebastienbre portland?  'k.00:10
sebastienbregarding pinging reprap-dev, I'll chat with kanzure about it.00:10
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap00:11
sebastienbprusajr is starting to work on the same sort of problem with thingdoc, so we don't want launch two competing projects ...00:11
jrayhawkhttp://gnusha.org/logs/ can probably be used to work out kanzure's current sleep schedule, fwiw.00:12
sebastienbMind you, it would be very reprappish.  I think we're fractally self-forking.00:12
jrayhawkhaha00:12
jrayhawkOften it doesn't hurt to pursue multiple approaches so long as everyone plays nice.00:13
sebastienbMy policy is to create a new forum every time people start arguing.  Then each dev gets a forum to be right in.00:14
sebastienbWorks for forking, too.00:14
jrayhawkhaha00:15
sebastienbThat's why reprap has ~225 forums.00:15
jrayhawkIkiwiki sortof-supports forums, so piny would give you forkable discussions for free!00:15
jrayhawkit's a little clunky, though.00:15
jrayhawkhttp://ikiwiki.info/forum/00:16
sebastienbSimilar to mediawiki talk pages?00:16
jrayhawkActually, it looks like that isn't quite set up the way it should be.00:17
sebastienbWe've got a forum siloed from a mediawiki right now ...00:17
sebastienbI noticed the ikiwiki devs are against having a mailing list, since they're dogfooding ikiwiki.  Which is admirable.00:17
sebastienbAside from wanting to email them.  :D00:17
jrayhawkThere's also #ikiwiki on OFTC00:18
jrayhawkTheir mailing list is realistically bugs.debian.org00:18
jrayhawkif you're unfamiliar with bugs.debian.org, it is exclusively handled through email00:19
sebastienbso ikiwiki bugs go to bugs.debian.org?00:19
sebastienbhttp://ikiwiki.info/ikiwikiusers/ shows some of this.00:20
jrayhawkIf you really want to deal with them over email, yes. Joey Hess is both upstream and package maintainer.00:20
sebastienbNo issues yet.  I just wanted to make ikiwiki wasn't a one-dev type project that'd fall apart if the dev disappeared.00:21
jrayhawkAh. Joey has a history of abandoning some social projects, but not technical projects.00:22
jrayhawkJoey has been *immensely* important to Debian.00:22
sebastienbVery good to know.00:25
sebastienbAh, it's 330 am here.  Need to sign off.00:25
jrayhawkGodspeed.00:25
sebastienbThanks for the chat.00:25
sebastienbNight, jrayhawk.  Night, channel.00:27
-!- sebastienb [~sbailard@206.248.158.253] has left ##hplusroadmap ["Leaving"]00:27
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 276 seconds]00:36
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap00:37
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 260 seconds]00:52
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap00:53
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 246 seconds]01:03
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap01:04
-!- augur [~augur@129.2.129.33] has quit [Remote host closed the connection]01:07
-!- wrldpc2 [~benny@58-89-241-19.nttmil.net] has joined ##hplusroadmap01:20
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Remote host closed the connection]01:24
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap01:24
-!- augur [~augur@208.58.6.161] has joined ##hplusroadmap01:31
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 240 seconds]01:33
wrldpc2Why is Alex Lightman losing his mind re: Fukushima?  Is it really that dire?01:35
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap01:35
-!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]01:37
-!- phreedom [~quassel@109.254.17.41] has quit [Ping timeout: 250 seconds]01:38
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 260 seconds]01:43
jrayhawkNot sure what you're asking. The media reaction has been incredibly dire and has probably set back nuclear energy for decades.01:46
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap01:49
jrayhawkThe radioactive release for fukushima is relatively minor and will probably have unpleasant consequences for a dozen workers at the plant.01:51
Utopiahpedagogical and adding informations as they arrive (mostly from IAEA, TEPCO and some media reviews) http://mitnse.com02:07
jrayhawkYeah, thankfully *somebody's* motivated by something other than viewership.02:27
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 260 seconds]02:44
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap02:45
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 240 seconds]03:04
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap03:05
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 276 seconds]03:10
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap03:16
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 240 seconds]03:21
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap03:28
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 276 seconds]03:51
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap04:08
-!- Technicus [~Technicus@DSLPool-net209-116.wctc.net] has quit [Read error: Connection reset by peer]04:49
-!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has joined ##hplusroadmap05:05
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 252 seconds]05:10
-!- Daeken [~daeken@straylight.daeken.com] has quit [Ping timeout: 276 seconds]05:17
-!- Daeken [~daeken@straylight.daeken.com] has joined ##hplusroadmap05:17
-!- ThomasEgi [~thomas@panda3d/ThomasEgi] has joined ##hplusroadmap06:16
-!- JayDugger [~duggerj@pool-173-74-79-43.dllstx.fios.verizon.net] has joined ##hplusroadmap06:19
JayDuggerGood morning, everyone.06:19
-!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has quit [Quit: mheld]06:34
-!- strages [~qwebirc@dev.throwthemind.com] has joined ##hplusroadmap06:48
-!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has joined ##hplusroadmap07:21
-!- mheld [~mheld@c-75-69-89-109.hsd1.ma.comcast.net] has joined ##hplusroadmap07:32
kanzurefun times: http://www.reddit.com/r/askscience/comments/g7wnt/are_kurzweils_postulations_on_ai_and/07:46
kanzurere: gitduino, i'm awful and very busy07:50
jrayhawkyou should still shove a git repo for it somewheres07:57
-!- strages [~qwebirc@dev.throwthemind.com] has quit [Ping timeout: 255 seconds]08:02
-!- jmil [~jmil@2001:468:1802:e148:223:32ff:feb1:9dfc] has joined ##hplusroadmap08:04
-!- mheld [~mheld@c-75-69-89-109.hsd1.ma.comcast.net] has quit [Quit: mheld]08:20
-!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has quit [Quit: Computer has gone to sleep.]08:33
kanzureright now it's kind of locked up in a git repo with some other code (that's why i haven't done it yet)08:33
kanzurei think i might be using git all wrong, i tend to rewrite a lot of history08:33
-!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has joined ##hplusroadmap08:43
-!- Juul [~Juul@slim.dhcp.lbl.gov] has joined ##hplusroadmap09:14
jrayhawkWell, it's nice when sharing patches to organize commits by how they should be reviewed rather than how they were written (which is usually somewhat messier)09:15
-!- jrabbit [~babyseal@unaffiliated/jrabbit] has quit [Ping timeout: 250 seconds]09:16
jrayhawkbut if you're just doing it for yourself, then yes, that is a rather vain pursuit09:16
-!- jrabbit [~babyseal@unaffiliated/jrabbit] has joined ##hplusroadmap09:17
kanzurehuh?09:17
kanzurei'm saying that i tend to have stuff in repositories that also has other related-but-private stuff09:18
jrayhawkoh, yes. that is a little dumb.09:18
kanzurebut what do you mean by "by how they should be reviewed"09:18
jrayhawkUsually when people are rewriting history, they're rewriting a large series of commits into a single, more coherent commit.09:19
kanzureoh09:19
kanzureyeah i don't know about that either.. i don't do that, but maybe i should?09:19
kanzurei usually try to commit 1) when a feature is complete or 2) before i'm about to do something potentially stupid09:19
jrayhawkDo you do all that much collaboration or git-bisection?09:19
kanzurecaveat to #1 is "it's also tested"09:20
kanzurei haven't used bisection yet.. but i've been wanting to :)09:20
jrayhawkIt's great for kernel regressions.09:20
-!- strages [~qwebirc@dev.throwthemind.com] has joined ##hplusroadmap09:21
jrayhawkThat and kexec.09:21
kanzureis there a standard way to reference a commit in a bug report ticket/issue?09:21
kanzurein a commit, you can reference issues usually like #591009:21
kanzurebut as far as i can tell, nobody parses bug tickets to link to commits in git repos09:22
jrayhawkThe commit id, yeah. Some people shorten it, but that's a matter of taste.09:22
kanzurei mean, semantically parsed or whatever09:22
kanzurei've been using unfuddle on my mobile testing project, and it attaches any commit to a ticket when the commit references the ticket09:22
kanzurebut if the ticket references a commit, nothing happens :x09:22
kanzure*unfuddle with09:22
jrayhawkWhat's supposed to happen when a ticket references a commit?09:23
jrayhawkOh, you want it attached. That's weird.09:23
kanzurewell why not? if you attach tickets to commits by referencing tickets in the commit messages, why not the other way around09:23
jrayhawkFar better to put bug reports in the same repository, but to each their own.09:24
kanzureanyway, it's just a minor nit pick09:24
kanzureyeah i agree, but there's no distributed git-based bug tracker that works yet09:24
kanzurebugs everywhere apparently doesn't work consistently or there's various issues that i have already forgotten09:24
kanzurei forget if BE has built their locally-hosted web-based bug interface yet.09:24
jrayhawkI don't really understand what features of a bug tracker would be valuable besides email notification, which can't really be done in a distributed manner anyway.09:25
kanzurehttp://bugseverywhere.org/be/show/HomePage09:25
jrayhawkWhere does it list its features?09:25
kanzure'be help' heh09:26
jrayhawkthis appears to be a frontend for 'grep'09:27
jrayhawkas in, i fail to see what this does that a directory full of text files doesn't09:28
jrayhawka directory full of text files, a text editor, and grep09:29
kanzurei'm pretty sure it does create a directory full of text files09:29
kanzurelast time i checked.09:29
kanzurethey have probably changed it and broken compatibility with everything by now09:29
jrayhawkso in what sense does the world need special software for distributed git-based bug tracking09:30
kanzurenobody is going to fill out the metadata required for bugs in text files09:30
kanzureplus, having 10k+ text files for bugs is just stupid in large projects09:30
kanzureand is mostly unmanageable09:30
kanzureespecially if the text files have no consistent format09:31
jrayhawksomehow debbugs works fine letting end users freely structure text.09:31
kanzurei should day *10k+ text files for unstructured bugs09:31
jrayhawkyou act like organizing text files is a crazy thing to do09:32
jrayhawkwhat do you think the entire linux kernel source tree is09:32
kanzureunstructured text files09:33
kanzurethere's nothing wrong with flat files in general09:33
jrayhawkwhy would they be unstructured09:33
kanzurehaha you seem to be more crazy than normal this morning09:34
kanzureyou seem to be advocating users just typing into text files directly09:34
kanzuremost people do not want to write tickets in the first place; do you really think they have the force of mind to keep structure consistent09:34
kanzureyou were also advocating *against* clients like BE to manage the text files09:34
eridumost people also don't use git09:35
kanzure:(09:35
jrayhawkAll information repositories have *maintainers* to keep them sorted. You're acting like a bug tracking system is a black hole of user input.09:35
kanzurelet's assume they use git09:35
eriduthen they have the force of mind to keep the structure consistent09:36
eriduotherwise, you just won't let them merge with your canonical git repo09:36
kanzuremaintenance of text files is something a computer can do09:36
kanzuremore efficiently/better.09:36
eriduyou'd have bug guidelines, like code guidelines09:36
eriduthen why don't people write source code in YAML or XML editors?09:37
kanzureyou mean text editors?09:37
eriduno, I mean something comparable to BE or ditz09:37
kanzureit's very clear that if you write bad code, it doesn't compile09:37
eriduokay, so maybe we have a bug-language that is machine-parsable; that's obviously handy09:38
eridubut then you have a bts that is exactly equivalent to code, and obviously doesn't need management systems beyond what you use for code09:38
eridualso, I think your earlier arguments regarding scale are irrelevant here, since I've never seen a large project using something like BE or ditz09:39
eriduI use ditz on projects where I personally know everyone who would be filing a bug09:40
jrayhawkooh, ditz does timekeeping in the git repository, too. that's an interesting idea.09:43
eriduit also has an emacs mode09:44
eriduwhich I think is why I chose it instead of BE09:44
eriduBE might also not have been in Ubuntu when I was making this decision09:44
jrayhawkI need to take off, but statements like '09:24 < kanzure> yeah i agree, but there's no distributed git-based bug tracker that works yet' confuse me because there's only a handful of reasons I've ever wanted to treat bugs differently from code and I'm wondering what yours are.09:55
jrayhawkand obviously existing infrastructure for distributed code management is already quite good10:01
kanzurehttp://www.themonthly.com.au/julian-assange-cypherpunk-revolutionary-robert-manne-308110:35
kanzure"By the time Assange was working on NetBSD he had been involved for several10:35
kanzureyears with a movement known as the cypherpunks."10:35
kanzure"The cypherpunks emerged from a meeting of minds in late 1992 in the Bay Area10:36
kanzureof San Francisco... eric hughes.. tim may.. john gilmore.. "10:36
-!- Juul [~Juul@slim.dhcp.lbl.gov] has quit [Ping timeout: 250 seconds]10:36
kanzure"They had created a small group, which met monthly in Gilmoreā€™s office at a business he had created, Cygnus"10:37
-!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has joined ##hplusroadmap10:39
kanzurehttp://blog.danhett.com/2011/03/enter-amateur-diybio-madlab.html10:42
kanzurealso, it looks like there's a portland biobus for whatever that's worth10:43
-!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has quit [Read error: Connection reset by peer]10:49
-!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has joined ##hplusroadmap10:58
-!- Juul [~Juul@slim.dhcp.lbl.gov] has joined ##hplusroadmap10:58
-!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has quit [Read error: Operation timed out]11:00
-!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has joined ##hplusroadmap11:01
kanzure"Interestingly, recent analyses have found that life expectancy at the age of 50 years among members of the Russian Academy of Sciences has been increasing steadily over the past 60 years, almost in parallel and only just below that of the fellows of the Royal Society in the UK."11:38
kanzure"Russian Academicians have apparently managed to isolate themselves from the massive fluctuations in mortality experienced by the bulk of the Russian population"11:38
-!- ThomasEgi [~thomas@panda3d/ThomasEgi] has quit [Read error: Operation timed out]11:44
-!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]11:56
-!- ThomasEgi [~thomas@panda3d/ThomasEgi] has joined ##hplusroadmap11:59
-!- jennicide [jen@173-19-240-62.client.mchsi.com] has joined ##hplusroadmap12:10
-!- augur [~augur@208.58.6.161] has quit [Remote host closed the connection]12:46
-!- Juul [~Juul@slim.dhcp.lbl.gov] has quit [Ping timeout: 240 seconds]12:55
-!- augur [~augur@129.2.129.33] has joined ##hplusroadmap13:27
-!- wrldpc2 [~benny@58-89-241-19.nttmil.net] has quit [Quit: wrldpc2]13:39
-!- augur [~augur@129.2.129.33] has quit [Remote host closed the connection]13:44
-!- augur [~augur@129.2.129.33] has joined ##hplusroadmap13:45
-!- eridu [debian-tor@gateway/tor-sasl/eridu] has quit [Ping timeout: 246 seconds]14:36
-!- Juul [~Juul@slim.dhcp.lbl.gov] has joined ##hplusroadmap14:36
-!- strages [~qwebirc@dev.throwthemind.com] has quit [Quit: Page closed]14:51
-!- eridu [debian-tor@gateway/tor-sasl/eridu] has joined ##hplusroadmap15:00
-!- strages [~strages@wifi.makerslocal.org] has joined ##hplusroadmap15:07
-!- jmil [~jmil@2001:468:1802:e148:223:32ff:feb1:9dfc] has quit [Quit: jmil]15:21
-!- Juul [~Juul@slim.dhcp.lbl.gov] has quit [Quit: Leaving]15:24
-!- technetium_s [~IceChat77@host86-145-234-7.range86-145.btcentralplus.com] has joined ##hplusroadmap15:51
technetium_shello15:54
-!- eridu [debian-tor@gateway/tor-sasl/eridu] has quit [Ping timeout: 246 seconds]15:58
kanzurehi technetium_s16:46
-!- strages [~strages@wifi.makerslocal.org] has quit [Read error: Operation timed out]17:01
-!- jmil [~jmil@c-68-81-252-40.hsd1.pa.comcast.net] has joined ##hplusroadmap17:14
-!- sebastienb [~sbailard@206.248.158.253] has joined ##hplusroadmap17:29
sebastienbEvening, all.17:30
sebastienbhi kanzure.17:30
JayDuggerGood evening, everyone.17:32
-!- jrabbit [~babyseal@unaffiliated/jrabbit] has quit [Ping timeout: 264 seconds]17:33
sebastienbevening.17:34
-!- strages [~strages@wifi.makerslocal.org] has joined ##hplusroadmap17:34
-!- jrabbit [~babyseal@unaffiliated/jrabbit] has joined ##hplusroadmap17:46
kanzuresebastienb: realistically, i'm not going to have time to complete this17:47
kanzurei'm thinking about hiring some people though17:47
kanzureor at least a person17:47
sebastienbah, hi kanzure!17:48
sebastienbI was chatting in #reprap with prusajr about thingdoc a moment ago.17:48
sebastienb<prusajr> Im going to bed. sebastienb make a writeup as I did for builders blog, and try to write as much as you can including ETA17:48
sebastienbI think it'd be good to do a status update soonish?17:49
sebastienbreprap-dev and blog?17:49
sebastienbAre you under major time pressure with paying projects right now, or did you run into architecture issues with gitduino ...?17:51
sebastienbping?17:56
kanzurepaying projects17:57
sebastienbWell, that is good.17:58
sebastienbAside from hiring folk, what about opening it up to people via a blog.reprap.org and reprap-dev media campaign?17:59
kanzureall of the hard architecture stuff is done17:59
sebastienbbtw, is this a good time to chat?17:59
kanzurei'm kind of against a "media campaign" for something that isn't launched18:00
kanzureit's a waste of space :)18:00
sebastienbRight, but ... do we let it languish?  And watch prusajr re-invent it?18:00
kanzureprusajr isn't doing anything close..18:00
kanzureunless prusa is doing something other than thingdoc?18:01
kanzureanyway, that's why i'm going to just pay someone to work on this18:01
kanzurethis is a weeks worth of work.. at most18:02
sebastienbhmmm18:02
sebastienbYou know what is best, and if it is a well-defined set of tasks, then I imagine a hired gun is best.18:04
-!- jrabbit [~babyseal@unaffiliated/jrabbit] has quit [Ping timeout: 260 seconds]18:05
sebastienbSo, when do you think you'd be hiring someone, and what waypoints would be ticked off by the guy?18:08
kanzurethis week i hope18:10
sebastienb:D18:10
kanzurebasically the things that need to be done are making standard model-controller-views for git repositories.. standard stuff18:11
sebastienbI sense this is a sticking point for self-hosting.18:12
kanzurewhat?18:12
kanzurethen tying in my rendering scripts to pull in images for each revision18:12
kanzurethen (later) prettying up the site for public consumption18:13
sebastienbanthong redbeard can help with that?18:13
kanzurei guess?18:13
sebastienbHe's quite keen to help.18:13
kanzurelook, when i have something for him, i'll send it to him18:14
kanzurei know you think i've been ignoring him18:14
kanzurebut really, he can't make his css magic work without something to apply the stylesheets *to*18:14
sebastienbNot exactly.18:14
kanzureok cool18:14
sebastienbRight.  I sort of understood that.18:14
paskykanzure: why not just take something existing like gitorious and adding your stuff?18:14
kanzurebecause gitorious sucks18:14
kanzurethat's the primary reason heh18:14
sebastienbWorse than mediawiki?18:15
JayDuggerSucks differently.18:15
sebastienb(Different toolset for different needs, so.)18:15
sebastienbkanzure, does it make sense for me to learn django to try to understand this and eventually help with small bits of it?18:16
kanzuresucking is better than not existing i suppose18:16
paskykanzure: well they did invent the wheel :)18:16
paskyyour flamingo is pretty tho18:17
kanzureha ha18:17
JayDuggereye candy > suckware > vaporware. Got it.18:17
sebastienbSo, yes on django?18:18
kanzurewell, no, if i just extend gitorious, that means it's in rails18:18
kanzurethe work i've done in django is fairly generic- again, there's nothing inherently complicated about the remaining work..18:19
kanzuresebastienb: http://gitorious.org/18:19
kanzurejust imagine that "but with pictures of hardware too"18:19
sebastienbAt some point I was thinking about installing _that_ on the wiki, but it wouldn't have made sense.18:20
kanzureon the wiki?18:20
kanzurewhy18:20
sebastienbserver, I mean.18:20
sebastienbwell, without rendering, it doesn't make sense.18:21
sebastienbbut django is one of the ingredients, along with ikiwiki and piny, so I should learn it, I imagine.18:22
kanzuredjango is not one of the ingredients of gitorious18:22
sebastienbno, of what we'll have on the reprap server.18:22
kanzurehttp://diyhpl.us/~bryan/irc/stl2pov/gitduino-post-receive-hook.sh18:25
kanzureoops i mean this:18:26
kanzurehttp://diyhpl.us/~bryan/irc/stl2pov/gitduino-post-receive-hook.txt18:26
sebastienbthe #!/bin/bash suggests this isn't django.  :D18:27
* sebastienb is reading it.18:28
-!- jrabbit [~babyseal@unaffiliated/jrabbit] has joined ##hplusroadmap18:29
paskykanzure:18:30
paskyoops18:30
paskykanzure: how long does that openscad / povray take?18:30
paskykanzure: if more than a second or two, you probably really do not want to do this within the receive session or user's git push will hang uselessly18:31
kanzuresebastienb: i don't think you understand what a git hook is :P18:31
sebastienbyup.18:31
paskykanzure: you may find girocco's taskd (http://repo.or.cz/w/girocco.git/blob/HEAD:/hooks/post-receive http://repo.or.cz/w/girocco.git/tree/HEAD:/taskd) useful18:31
kanzurepasky: of course; this is an unoptimized script18:31
sebastienbI've got a PHB understanding of this stuff.18:32
kanzurepasky: this is still very debuggy and experimental18:32
paskyor something along these lines18:32
kanzurepasky: the obvious thing to do would be to ping a daemon called renderbot18:32
kanzureer, sorry, i was on the phone for the last 15min18:35
sebastienbno worries.18:36
-!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has joined ##hplusroadmap18:36
kanzureanyway, no sebastienb, you don't put django code in a git post-receive hook.. although you could if you want18:36
kanzureif someone wants to write a rails gem to add it to gitorious, that's fine18:37
sebastienbbut django is a significant part of this, right?  And we'll have folk doing thing like "join project", and have their user page reflect membership in a project, and that will be part of it all, right?18:37
ybiti'm guessing gitduino is github with pretty pictures of hardware and some file format for representing changes to hardware18:37
kanzureyes18:37
sebastienbAnd that would be done in ... django?18:37
ybitsounds like what i was wanting to do18:37
kanzurea "join project" button is trivial in django18:37
sebastienbright.18:37
kanzureit's also trivial in rails (which is what gitorious is built on)18:38
sebastienband I'm one of the guys everyone thinks is responsible for the front end, and this way I can fill some of my own pony requests.18:38
sebastienb... and gitorious has nothing to do with the gitduino project?18:38
kanzurepasky's suggestion is to just use gitorious instead of writing a custom django project18:39
sebastienbah.18:39
ybitmy little mockup: http://image.bayimg.com/jaebcaadj.jpg18:39
paskykanzure: ah good, then i guess you know about the race with two git pushes within single second and all sorts of trouble with filenames containing spaces :)18:39
kanzurepasky: it's so experimental that it's not even funny18:39
kanzurehere's what it renders to:18:40
kanzurehttp://diyhpl.us/~bryan/irc/stl2pov//dremelfuge/01604aefda5a079f740ff5fa966bcade9511ed80/gears.scad-1101b4abdb.png18:40
paskyoh you could also use girocco but that is very unweb2.018:40
kanzurehttp://diyhpl.us/~bryan/irc/stl2pov//dremelfuge/305fce14356203666ebffe6141630bd2b8f240c3/dremelfuge-v4.scad-72422eca27.png18:40
sebastienbah, pretty gears.18:40
sebastienbkanzure, that was done by that bash script?18:41
kanzureyes18:41
kanzurespecifically, when i made a change to cathal's dremelfuge and pushed (uploaded) it to gitduino18:42
kanzuremore specifically, made a change to the model definition..18:42
sebastienbah.18:42
sebastienbAnd a hook sniffed the  change, and updated the render.18:43
paskythen again i have already once done contract work to heavily customize gitweb to be able to show custom rendered files and structured repositories in a fancy way... but i never got around to releasing this and i'm not likely to get time to ever do it now18:43
kanzureto gitweb? ha ha18:44
sebastienbkanzure, you're using ... piny for the git web interface?18:44
kanzure..?18:44
kanzurepiny is a set of tools for managing a server full of git repositories18:44
sebastienbOh!18:44
kanzurepiny basically automates all of the pain of setting up git repositories, wikis and mailing lists associated with each project18:45
kanzureplus access controls for different contributors, etc. etc.18:45
sebastienbok.  When  someone changes text, and a wiki page shows a diff, what software renders that?18:45
kanzureyour browser18:46
sebastienbright.18:46
sebastienbbut that diff may be inlaid into a webpage, and ...18:46
kanzurei don't know what you're asking18:46
sebastienbIt's not crucial right now.18:47
kanzureif you let piny mess with your apache config, it can use ikiwiki's perl scripts to show diffs18:47
kanzurebut frankly if you have a django or rails-based site, you should just render your diffs through coderay/pygments/whatever18:47
sebastienbBut we'll need a text+image description of what chunks of software do what when we're doing the blog post and reprap-dev discussion.18:47
paskyit seems piny by defaults relies on cgit to do this?18:48
kanzurepasky: sure18:48
sebastienbMind you, hiring a guy to help get it working takes priority.18:48
kanzurebut he was asking about wiki diffs18:48
paskyah sorry18:48
kanzurewriting a gem for gitorious actually sounds like an ok plan18:50
sebastienbI'm assuming we'll be showing code diffs at some point, and that we're not right now.  What code will we use to do it?18:50
kanzurewell, if we're using gitorious, then gitorious.. (rails)18:51
sebastienbAh.18:51
kanzureif we're using a custom django system, it'll be (django)18:51
sebastienbAnd right now we don18:51
sebastienbAnd right now we don't know if we're going to use django or gitorious?18:51
kanzureO_o well right now gitduino.com has a prototype of itself written in django18:52
kanzure*written in python using django18:52
kanzurewhat are you trying to learn from me?18:52
sebastienbSite architecture stuff.  What's going to do what.18:52
sebastienbAnd the gitorious discussion is pure hypothetical, right?18:53
kanzurewell gitorious has a more extensive, more real code base than my fictional django code18:53
sebastienbAnd would gitorious work neatly with ikiwiki the way django would?18:54
kanzureno, gitorious implements its own wiki iirc18:54
kanzurewhich is stupid & dumb18:54
kanzurethere's probably a ruby-based gem that can be thrown in that works with ikiwiki18:55
ybiti'm going to work on this18:55
kanzureare you?18:55
ybityeah18:55
kanzurewhat part18:55
sebastienb:D18:55
ybiti'm not really sure what language, this is all similar to what i've been brainstorming over18:56
ybitif django, i was considering building on top of mercurial18:56
kanzurewriting a gitorious plugin would be really quick18:56
ybitif gitorious, the gem route for gitduino sounds nice too18:56
ybitthe obvious question, i don't suppose anyone would be willing to use my own dvcs system written in js? :D18:57
kanzureit would be something like:18:57
kanzureadd a join table to list images to a specific commit18:57
kanzurehave the rendering service POST to the commit model on gitorious18:57
ybit-system18:57
kanzurerun the rendering service on a separate vps18:57
kanzureybit: elevenarm's opinion is that this should just be a pure js client on top of github18:58
kanzureusing the github api18:58
ybitthat's interesting too18:59
kanzurehe and i kind of go overboard when it comes to js.. especially in our paid work18:59
kanzurehttp://apps.facebook.com/socialmuse18:59
kanzurethe client is pure js19:00
* sebastienb clicks.19:01
-!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has joined ##hplusroadmap19:01
ybitwhere is the reprap dev channel?19:02
sebastienb#reprap19:02
ybitoh, i thought there was something like #reprap-dev19:02
ybit\/list wasn't showing anything :)19:02
ybitgrr19:02
sebastienbreprap-dev is a mailing list. Compulsory to join, and all that.  :D19:02
ybiti'm probably already subscribed19:02
kanzurereprap-dev seems to forget about reprap-users19:02
sebastienbWell, that's because everyone's a dev, and not just a user.19:03
sebastienbI need to rename it reprap-dev-chat and reprap-dev-support19:03
kanzurehuh?19:03
kanzurethat's dumb19:03
kanzurejust say "development goes here"19:03
kanzurethat's why it's reprap-dev19:03
kanzureit's not "for developers only"19:03
sebastienbreprap-dev's intro page does say "development goes here".19:04
kanzureokay, then tell non-development threads to go somewhere else.. if it matters19:04
* kanzure goes back to work19:05
sebastienbkanzure, should I ping ya in 2-3 days to see how things are going?19:05
paskywell if you need any git-fu help or some-such, feel free to highlight me... the project seems like a nice idea19:05
sebastienbpasky, that's very kind.19:06
kanzuresebastienb yeah sure19:06
kanzurepinging is always good/acceptable19:06
sebastienbWill do.19:06
kanzurepasky: feel free to make creative complaints about the post-receive hook19:06
sebastienbAnd should I learn django in 15 minutes, or rails?19:06
kanzuresebastienb: up to you.. i say both, but i have unreasonable expectations for everyone (incl. myself)19:07
sebastienbFor the stuff we're doing up on the server soonish.19:07
sebastienbI'm guessing django?19:10
sebastienboh, hey, I just found http://www.reviewboard.org/19:11
sebastienbdjango based and integrates with git.19:11
sebastienbhas a diff viewer.19:12
sebastienbdunno if it has anything to do with what we're up to.19:12
sebastienbkanzure, I should let you get back to work?19:12
paskykanzure: well you said it was experimental version :) your temp_token will make a dupe for two invocations in single second, a good way to avoid that is to include $$ in the md5sum; loading a whole file content to a variable and dumping it off again somewhere is a no-no for variety of reasons, just redirect it directly; you should use quotes rigorously when mentioning variables, $file may contain spaces and then things like git show ...19:14
pasky... $commit:$file will fail miserably (also, redirects will fail as ambiguous ones), for the same reason you should iterate over files using while read instead of for; nothing else comes on mind right away19:15
ybiti'm typically busy throughout the week, i'll spend my weekends working on this19:16
ybitand i guess no one should expect anything to come from my work19:16
* ybit no likey expectations19:16
* ybit fails miserably typically19:16
sebastienbNo worries.  I've got a lot to learn about this stuff.19:17
ybitheh19:17
sebastienbI also have a very keen sense of just how our mediawiki doesn't meet our needs, so ...19:17
ybitas far as web frameworks, i've been leaning more toward js based stuff19:18
paskykanzure: (you can use git ls-tree -z if you want to also support filenames with newlines embedded, but then things get quite hairy so i just suggest punting on those)19:18
ybitfrom my own experience,i can usually count on more than one programming language to slow work down a little19:19
ybiti trip up easily19:20
ybit..mostly because i suck19:20
pasky'nite19:20
ybitnight19:20
sebastienbnite, pasky.19:20
ybitsebastienb: you have experience with fpga?19:20
sebastienbno.19:21
sebastienbPeople occassionally mention them in terms of reprap.19:21
sebastienbI know what they are, haven't touched on.19:21
sebastienbone.19:21
* ybit gets back to work as well19:22
-!- strages [~strages@wifi.makerslocal.org] has quit [Ping timeout: 255 seconds]19:23
kanzurei find it retarded that tom is posting about "how to be social"20:16
kanzurehttp://hplusmagazine.com/2011/03/22/building-and-growing-transhumanist-communities/20:16
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap20:16
kanzurewhy do so many people i know suuuuck20:16
QuantumGthe people you know are not statistical outliers20:46
-!- mayko [~mayko@71-22-217-151.gar.clearwire-wmx.net] has quit [Ping timeout: 252 seconds]20:59
-!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]21:00
-!- jmil [~jmil@c-68-81-252-40.hsd1.pa.comcast.net] has quit [Quit: jmil]21:02
-!- mayko [~mayko@71-22-217-151.gar.clearwire-wmx.net] has joined ##hplusroadmap21:12
-!- klord [~klord@64.39.5.118] has joined ##hplusroadmap21:56
-!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 250 seconds]22:00
-!- klord_ [~klord@72-254-120-166.client.stsn.net] has joined ##hplusroadmap22:17
-!- klord [~klord@64.39.5.118] has quit [Ping timeout: 246 seconds]22:19
-!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has quit [Quit: Computer has gone to sleep.]22:29
-!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has quit [Quit: mheld]22:51
-!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has joined ##hplusroadmap22:54
-!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has quit [Client Quit]22:57
-!- klord_ [~klord@72-254-120-166.client.stsn.net] has quit [Ping timeout: 264 seconds]23:23
sebastienbNight, all.23:27
kanzuregood night sebastienb23:31
sebastienbI'll ping ya in a few days, eh?23:35
ybitwe shall never know23:36
ybitnight sebastienb23:36
sebastienbnight!23:36
-!- sebastienb [~sbailard@206.248.158.253] has left ##hplusroadmap ["Leaving"]23:36
--- Log closed Tue Mar 22 00:00:10 2011

Generated by irclog2html.py 2.15.0.dev0 by Marius Gedminas - find it at mg.pov.lt!