--- Log opened Mon Mar 21 00:00:04 2011
--- Day changed Mon Mar 21 2011
00:00 < sebastienb> I 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 < jrayhawk> I 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:01 < jrayhawk> Nothing directly profitable, anyway.
00:01 < sebastienb> That'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:02 < sebastienb> That may be best, since that may be the same or similar server to where we'll be running piny anyways.
00:02 < sebastienb> I'll look into it.
00:03 < sebastienb> I 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:04 < jrayhawk> If that prove untenable, you're also free to complain at me until I write better documentation.
00:04 < jrayhawk> proves
00:05 < sebastienb> I'd suggest a 2 line explanation here:
00:05 < sebastienb> http://piny.be
00:05 < jrayhawk> Hmm, yeah, I suppose.
00:05 < sebastienb> Of what piny actually is, for new folk.
00:05 < jrayhawk> I should really rename piny-the-codebase or piny-the-hosting-service to something else.
00:06 < sebastienb> you're in portland, btw?
00:06 < jrayhawk> Yeah.
00:06 < sebastienb> You may want to ping folk:
00:07 < sebastienb> http://forums.reprap.org/read.php?195,57338,page=1
00:07 < sebastienb> Our portland forum.
00:07 < jrayhawk> About Piny?
00:07 < sebastienb> About portland, if you're doing up a mendel?
00:08 < jrayhawk> Oh. 3d printing isn't particularly useful to any of my projects; maybe someday, but not today.
00:08 < sebastienb> But 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:09 < jrayhawk> I'll pass that on to some other people who probably will be interested.
00:10 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 255 seconds]
00:10 < sebastienb> re portland?  'k.
00:10 < sebastienb> regarding pinging reprap-dev, I'll chat with kanzure about it.
00:11 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
00:11 < sebastienb> prusajr is starting to work on the same sort of problem with thingdoc, so we don't want launch two competing projects ...
00:12 < jrayhawk> http://gnusha.org/logs/ can probably be used to work out kanzure's current sleep schedule, fwiw.
00:12 < sebastienb> Mind you, it would be very reprappish.  I think we're fractally self-forking.
00:12 < jrayhawk> haha
00:13 < jrayhawk> Often it doesn't hurt to pursue multiple approaches so long as everyone plays nice.
00:14 < sebastienb> My policy is to create a new forum every time people start arguing.  Then each dev gets a forum to be right in.
00:14 < sebastienb> Works for forking, too.
00:15 < jrayhawk> haha
00:15 < sebastienb> That's why reprap has ~225 forums.
00:15 < jrayhawk> Ikiwiki sortof-supports forums, so piny would give you forkable discussions for free!
00:15 < jrayhawk> it's a little clunky, though.
00:16 < jrayhawk> http://ikiwiki.info/forum/
00:16 < sebastienb> Similar to mediawiki talk pages?
00:17 < jrayhawk> Actually, it looks like that isn't quite set up the way it should be.
00:17 < sebastienb> We've got a forum siloed from a mediawiki right now ...
00:17 < sebastienb> I noticed the ikiwiki devs are against having a mailing list, since they're dogfooding ikiwiki.  Which is admirable.
00:17 < sebastienb> Aside from wanting to email them.  :D
00:18 < jrayhawk> There's also #ikiwiki on OFTC
00:18 < jrayhawk> Their mailing list is realistically bugs.debian.org
00:19 < jrayhawk> if you're unfamiliar with bugs.debian.org, it is exclusively handled through email
00:19 < sebastienb> so ikiwiki bugs go to bugs.debian.org?
00:20 < sebastienb> http://ikiwiki.info/ikiwikiusers/ shows some of this.
00:20 < jrayhawk> If you really want to deal with them over email, yes. Joey Hess is both upstream and package maintainer.
00:21 < sebastienb> No issues yet.  I just wanted to make ikiwiki wasn't a one-dev type project that'd fall apart if the dev disappeared.
00:22 < jrayhawk> Ah. Joey has a history of abandoning some social projects, but not technical projects.
00:22 < jrayhawk> Joey has been *immensely* important to Debian.
00:25 < sebastienb> Very good to know.
00:25 < sebastienb> Ah, it's 330 am here.  Need to sign off.
00:25 < jrayhawk> Godspeed.
00:25 < sebastienb> Thanks for the chat.
00:27 < sebastienb> Night, jrayhawk.  Night, channel.
00:27 -!- sebastienb [~sbailard@206.248.158.253] has left ##hplusroadmap ["Leaving"]
00:36 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 276 seconds]
00:37 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
00:52 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 260 seconds]
00:53 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
01:03 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 246 seconds]
01:04 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
01:07 -!- augur [~augur@129.2.129.33] has quit [Remote host closed the connection]
01:20 -!- wrldpc2 [~benny@58-89-241-19.nttmil.net] has joined ##hplusroadmap
01:24 -!- 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 ##hplusroadmap
01:31 -!- augur [~augur@208.58.6.161] has joined ##hplusroadmap
01:33 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 240 seconds]
01:35 < wrldpc2> Why 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 ##hplusroadmap
01:37 -!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]
01:38 -!- phreedom [~quassel@109.254.17.41] has quit [Ping timeout: 250 seconds]
01:43 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 260 seconds]
01:46 < jrayhawk> Not sure what you're asking. The media reaction has been incredibly dire and has probably set back nuclear energy for decades.
01:49 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
01:51 < jrayhawk> The radioactive release for fukushima is relatively minor and will probably have unpleasant consequences for a dozen workers at the plant.
02:07 < Utopiah> pedagogical and adding informations as they arrive (mostly from IAEA, TEPCO and some media reviews) http://mitnse.com
02:27 < jrayhawk> Yeah, thankfully *somebody's* motivated by something other than viewership.
02:44 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 260 seconds]
02:45 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
03:04 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 240 seconds]
03:05 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
03:10 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 276 seconds]
03:16 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
03:21 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 240 seconds]
03:28 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
03:51 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 276 seconds]
04:08 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has joined ##hplusroadmap
04:49 -!- Technicus [~Technicus@DSLPool-net209-116.wctc.net] has quit [Read error: Connection reset by peer]
05:05 -!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has joined ##hplusroadmap
05:10 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 252 seconds]
05:17 -!- Daeken [~daeken@straylight.daeken.com] has quit [Ping timeout: 276 seconds]
05:17 -!- Daeken [~daeken@straylight.daeken.com] has joined ##hplusroadmap
06:16 -!- ThomasEgi [~thomas@panda3d/ThomasEgi] has joined ##hplusroadmap
06:19 -!- JayDugger [~duggerj@pool-173-74-79-43.dllstx.fios.verizon.net] has joined ##hplusroadmap
06:19 < JayDugger> Good morning, everyone.
06:34 -!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has quit [Quit: mheld]
06:48 -!- strages [~qwebirc@dev.throwthemind.com] has joined ##hplusroadmap
07:21 -!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has joined ##hplusroadmap
07:32 -!- mheld [~mheld@c-75-69-89-109.hsd1.ma.comcast.net] has joined ##hplusroadmap
07:46 < kanzure> fun times: http://www.reddit.com/r/askscience/comments/g7wnt/are_kurzweils_postulations_on_ai_and/
07:50 < kanzure> re: gitduino, i'm awful and very busy
07:57 < jrayhawk> you should still shove a git repo for it somewheres
08:02 -!- strages [~qwebirc@dev.throwthemind.com] has quit [Ping timeout: 255 seconds]
08:04 -!- jmil [~jmil@2001:468:1802:e148:223:32ff:feb1:9dfc] has joined ##hplusroadmap
08:20 -!- mheld [~mheld@c-75-69-89-109.hsd1.ma.comcast.net] has quit [Quit: mheld]
08:33 -!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has quit [Quit: Computer has gone to sleep.]
08:33 < kanzure> right 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 < kanzure> i think i might be using git all wrong, i tend to rewrite a lot of history
08:43 -!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has joined ##hplusroadmap
09:14 -!- Juul [~Juul@slim.dhcp.lbl.gov] has joined ##hplusroadmap
09:15 < jrayhawk> Well, 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:16 -!- jrabbit [~babyseal@unaffiliated/jrabbit] has quit [Ping timeout: 250 seconds]
09:16 < jrayhawk> but if you're just doing it for yourself, then yes, that is a rather vain pursuit
09:17 -!- jrabbit [~babyseal@unaffiliated/jrabbit] has joined ##hplusroadmap
09:17 < kanzure> huh?
09:18 < kanzure> i'm saying that i tend to have stuff in repositories that also has other related-but-private stuff
09:18 < jrayhawk> oh, yes. that is a little dumb.
09:18 < kanzure> but what do you mean by "by how they should be reviewed"
09:19 < jrayhawk> Usually when people are rewriting history, they're rewriting a large series of commits into a single, more coherent commit.
09:19 < kanzure> oh
09:19 < kanzure> yeah i don't know about that either.. i don't do that, but maybe i should?
09:19 < kanzure> i usually try to commit 1) when a feature is complete or 2) before i'm about to do something potentially stupid
09:19 < jrayhawk> Do you do all that much collaboration or git-bisection?
09:20 < kanzure> caveat to #1 is "it's also tested"
09:20 < kanzure> i haven't used bisection yet.. but i've been wanting to :)
09:20 < jrayhawk> It's great for kernel regressions.
09:21 -!- strages [~qwebirc@dev.throwthemind.com] has joined ##hplusroadmap
09:21 < jrayhawk> That and kexec.
09:21 < kanzure> is there a standard way to reference a commit in a bug report ticket/issue?
09:21 < kanzure> in a commit, you can reference issues usually like #5910
09:22 < kanzure> but as far as i can tell, nobody parses bug tickets to link to commits in git repos
09:22 < jrayhawk> The commit id, yeah. Some people shorten it, but that's a matter of taste.
09:22 < kanzure> i mean, semantically parsed or whatever
09:22 < kanzure> i've been using unfuddle on my mobile testing project, and it attaches any commit to a ticket when the commit references the ticket
09:22 < kanzure> but if the ticket references a commit, nothing happens :x
09:22 < kanzure> *unfuddle with
09:23 < jrayhawk> What's supposed to happen when a ticket references a commit?
09:23 < jrayhawk> Oh, you want it attached. That's weird.
09:23 < kanzure> well why not? if you attach tickets to commits by referencing tickets in the commit messages, why not the other way around
09:24 < jrayhawk> Far better to put bug reports in the same repository, but to each their own.
09:24 < kanzure> anyway, it's just a minor nit pick
09:24 < kanzure> yeah i agree, but there's no distributed git-based bug tracker that works yet
09:24 < kanzure> bugs everywhere apparently doesn't work consistently or there's various issues that i have already forgotten
09:24 < kanzure> i forget if BE has built their locally-hosted web-based bug interface yet.
09:25 < jrayhawk> I 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 < kanzure> http://bugseverywhere.org/be/show/HomePage
09:25 < jrayhawk> Where does it list its features?
09:26 < kanzure> 'be help' heh
09:27 < jrayhawk> this appears to be a frontend for 'grep'
09:28 < jrayhawk> as in, i fail to see what this does that a directory full of text files doesn't
09:29 < jrayhawk> a directory full of text files, a text editor, and grep
09:29 < kanzure> i'm pretty sure it does create a directory full of text files
09:29 < kanzure> last time i checked.
09:29 < kanzure> they have probably changed it and broken compatibility with everything by now
09:30 < jrayhawk> so in what sense does the world need special software for distributed git-based bug tracking
09:30 < kanzure> nobody is going to fill out the metadata required for bugs in text files
09:30 < kanzure> plus, having 10k+ text files for bugs is just stupid in large projects
09:30 < kanzure> and is mostly unmanageable
09:31 < kanzure> especially if the text files have no consistent format
09:31 < jrayhawk> somehow debbugs works fine letting end users freely structure text.
09:31 < kanzure> i should day *10k+ text files for unstructured bugs
09:32 < jrayhawk> you act like organizing text files is a crazy thing to do
09:32 < jrayhawk> what do you think the entire linux kernel source tree is
09:33 < kanzure> unstructured text files
09:33 < kanzure> there's nothing wrong with flat files in general
09:33 < jrayhawk> why would they be unstructured
09:34 < kanzure> haha you seem to be more crazy than normal this morning
09:34 < kanzure> you seem to be advocating users just typing into text files directly
09:34 < kanzure> most people do not want to write tickets in the first place; do you really think they have the force of mind to keep structure consistent
09:34 < kanzure> you were also advocating *against* clients like BE to manage the text files
09:35 < eridu> most people also don't use git
09:35 < kanzure> :(
09:35 < jrayhawk> All 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 < kanzure> let's assume they use git
09:36 < eridu> then they have the force of mind to keep the structure consistent
09:36 < eridu> otherwise, you just won't let them merge with your canonical git repo
09:36 < kanzure> maintenance of text files is something a computer can do
09:36 < kanzure> more efficiently/better.
09:36 < eridu> you'd have bug guidelines, like code guidelines
09:37 < eridu> then why don't people write source code in YAML or XML editors?
09:37 < kanzure> you mean text editors?
09:37 < eridu> no, I mean something comparable to BE or ditz
09:37 < kanzure> it's very clear that if you write bad code, it doesn't compile
09:38 < eridu> okay, so maybe we have a bug-language that is machine-parsable; that's obviously handy
09:38 < eridu> but then you have a bts that is exactly equivalent to code, and obviously doesn't need management systems beyond what you use for code
09:39 < eridu> also, I think your earlier arguments regarding scale are irrelevant here, since I've never seen a large project using something like BE or ditz
09:40 < eridu> I use ditz on projects where I personally know everyone who would be filing a bug
09:43 < jrayhawk> ooh, ditz does timekeeping in the git repository, too. that's an interesting idea.
09:44 < eridu> it also has an emacs mode
09:44 < eridu> which I think is why I chose it instead of BE
09:44 < eridu> BE might also not have been in Ubuntu when I was making this decision
09:55 < jrayhawk> I 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.
10:01 < jrayhawk> and obviously existing infrastructure for distributed code management is already quite good
10:35 < kanzure> http://www.themonthly.com.au/julian-assange-cypherpunk-revolutionary-robert-manne-3081
10:35 < kanzure> "By the time Assange was working on NetBSD he had been involved for several
10:35 < kanzure> years with a movement known as the cypherpunks."
10:36 < kanzure> "The cypherpunks emerged from a meeting of minds in late 1992 in the Bay Area
10:36 < kanzure> of San Francisco... eric hughes.. tim may.. john gilmore.. "
10:36 -!- Juul [~Juul@slim.dhcp.lbl.gov] has quit [Ping timeout: 250 seconds]
10:37 < kanzure> "They had created a small group, which met monthly in Gilmore’s office at a business he had created, Cygnus"
10:39 -!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has joined ##hplusroadmap
10:42 < kanzure> http://blog.danhett.com/2011/03/enter-amateur-diybio-madlab.html
10:43 < kanzure> also, it looks like there's a portland biobus for whatever that's worth
10:49 -!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has quit [Read error: Connection reset by peer]
10:58 -!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has joined ##hplusroadmap
10:58 -!- Juul [~Juul@slim.dhcp.lbl.gov] has joined ##hplusroadmap
11:00 -!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has quit [Read error: Operation timed out]
11:01 -!- elmom [~elmom@hoasnet-ff01dd00-112.dhcp.inet.fi] has joined ##hplusroadmap
11:38 < 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:44 -!- ThomasEgi [~thomas@panda3d/ThomasEgi] has quit [Read error: Operation timed out]
11:56 -!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]
11:59 -!- ThomasEgi [~thomas@panda3d/ThomasEgi] has joined ##hplusroadmap
12:10 -!- jennicide [jen@173-19-240-62.client.mchsi.com] has joined ##hplusroadmap
12:46 -!- augur [~augur@208.58.6.161] has quit [Remote host closed the connection]
12:55 -!- Juul [~Juul@slim.dhcp.lbl.gov] has quit [Ping timeout: 240 seconds]
13:27 -!- augur [~augur@129.2.129.33] has joined ##hplusroadmap
13:39 -!- wrldpc2 [~benny@58-89-241-19.nttmil.net] has quit [Quit: wrldpc2]
13:44 -!- augur [~augur@129.2.129.33] has quit [Remote host closed the connection]
13:45 -!- augur [~augur@129.2.129.33] has joined ##hplusroadmap
14:36 -!- eridu [debian-tor@gateway/tor-sasl/eridu] has quit [Ping timeout: 246 seconds]
14:36 -!- Juul [~Juul@slim.dhcp.lbl.gov] has joined ##hplusroadmap
14:51 -!- strages [~qwebirc@dev.throwthemind.com] has quit [Quit: Page closed]
15:00 -!- eridu [debian-tor@gateway/tor-sasl/eridu] has joined ##hplusroadmap
15:07 -!- strages [~strages@wifi.makerslocal.org] has joined ##hplusroadmap
15:21 -!- jmil [~jmil@2001:468:1802:e148:223:32ff:feb1:9dfc] has quit [Quit: jmil]
15:24 -!- Juul [~Juul@slim.dhcp.lbl.gov] has quit [Quit: Leaving]
15:51 -!- technetium_s [~IceChat77@host86-145-234-7.range86-145.btcentralplus.com] has joined ##hplusroadmap
15:54 < technetium_s> hello
15:58 -!- eridu [debian-tor@gateway/tor-sasl/eridu] has quit [Ping timeout: 246 seconds]
16:46 < kanzure> hi technetium_s
17:01 -!- strages [~strages@wifi.makerslocal.org] has quit [Read error: Operation timed out]
17:14 -!- jmil [~jmil@c-68-81-252-40.hsd1.pa.comcast.net] has joined ##hplusroadmap
17:29 -!- sebastienb [~sbailard@206.248.158.253] has joined ##hplusroadmap
17:30 < sebastienb> Evening, all.
17:30 < sebastienb> hi kanzure.
17:32 < JayDugger> Good evening, everyone.
17:33 -!- jrabbit [~babyseal@unaffiliated/jrabbit] has quit [Ping timeout: 264 seconds]
17:34 < sebastienb> evening.
17:34 -!- strages [~strages@wifi.makerslocal.org] has joined ##hplusroadmap
17:46 -!- jrabbit [~babyseal@unaffiliated/jrabbit] has joined ##hplusroadmap
17:47 < kanzure> sebastienb: realistically, i'm not going to have time to complete this
17:47 < kanzure> i'm thinking about hiring some people though
17:47 < kanzure> or at least a person
17:48 < sebastienb> ah, hi kanzure!
17:48 < sebastienb> I 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 ETA
17:49 < sebastienb> I think it'd be good to do a status update soonish?
17:49 < sebastienb> reprap-dev and blog?
17:51 < sebastienb> Are you under major time pressure with paying projects right now, or did you run into architecture issues with gitduino ...?
17:56 < sebastienb> ping?
17:57 < kanzure> paying projects
17:58 < sebastienb> Well, that is good.
17:59 < sebastienb> Aside from hiring folk, what about opening it up to people via a blog.reprap.org and reprap-dev media campaign?
17:59 < kanzure> all of the hard architecture stuff is done
17:59 < sebastienb> btw, is this a good time to chat?
18:00 < kanzure> i'm kind of against a "media campaign" for something that isn't launched
18:00 < kanzure> it's a waste of space :)
18:00 < sebastienb> Right, but ... do we let it languish?  And watch prusajr re-invent it?
18:00 < kanzure> prusajr isn't doing anything close..
18:01 < kanzure> unless prusa is doing something other than thingdoc?
18:01 < kanzure> anyway, that's why i'm going to just pay someone to work on this
18:02 < kanzure> this is a weeks worth of work.. at most
18:02 < sebastienb> hmmm
18:04 < sebastienb> You know what is best, and if it is a well-defined set of tasks, then I imagine a hired gun is best.
18:05 -!- jrabbit [~babyseal@unaffiliated/jrabbit] has quit [Ping timeout: 260 seconds]
18:08 < sebastienb> So, when do you think you'd be hiring someone, and what waypoints would be ticked off by the guy?
18:10 < kanzure> this week i hope
18:10 < sebastienb> :D
18:11 < kanzure> basically the things that need to be done are making standard model-controller-views for git repositories.. standard stuff
18:12 < sebastienb> I sense this is a sticking point for self-hosting.
18:12 < kanzure> what?
18:12 < kanzure> then tying in my rendering scripts to pull in images for each revision
18:13 < kanzure> then (later) prettying up the site for public consumption
18:13 < sebastienb> anthong redbeard can help with that?
18:13 < kanzure> i guess?
18:13 < sebastienb> He's quite keen to help.
18:14 < kanzure> look, when i have something for him, i'll send it to him
18:14 < kanzure> i know you think i've been ignoring him
18:14 < kanzure> but really, he can't make his css magic work without something to apply the stylesheets *to*
18:14 < sebastienb> Not exactly.
18:14 < kanzure> ok cool
18:14 < sebastienb> Right.  I sort of understood that.
18:14 < pasky> kanzure: why not just take something existing like gitorious and adding your stuff?
18:14 < kanzure> because gitorious sucks
18:14 < kanzure> that's the primary reason heh
18:15 < sebastienb> Worse than mediawiki?
18:15 < JayDugger> Sucks differently.
18:15 < sebastienb> (Different toolset for different needs, so.)
18:16 < sebastienb> kanzure, does it make sense for me to learn django to try to understand this and eventually help with small bits of it?
18:16 < kanzure> sucking is better than not existing i suppose
18:16 < pasky> kanzure: well they did invent the wheel :)
18:17 < pasky> your flamingo is pretty tho
18:17 < kanzure> ha ha
18:17 < JayDugger> eye candy > suckware > vaporware. Got it.
18:18 < sebastienb> So, yes on django?
18:18 < kanzure> well, no, if i just extend gitorious, that means it's in rails
18:19 < kanzure> the work i've done in django is fairly generic- again, there's nothing inherently complicated about the remaining work..
18:19 < kanzure> sebastienb: http://gitorious.org/
18:19 < kanzure> just imagine that "but with pictures of hardware too"
18:20 < sebastienb> At some point I was thinking about installing _that_ on the wiki, but it wouldn't have made sense.
18:20 < kanzure> on the wiki?
18:20 < kanzure> why
18:20 < sebastienb> server, I mean.
18:21 < sebastienb> well, without rendering, it doesn't make sense.
18:22 < sebastienb> but django is one of the ingredients, along with ikiwiki and piny, so I should learn it, I imagine.
18:22 < kanzure> django is not one of the ingredients of gitorious
18:22 < sebastienb> no, of what we'll have on the reprap server.
18:25 < kanzure> http://diyhpl.us/~bryan/irc/stl2pov/gitduino-post-receive-hook.sh
18:26 < kanzure> oops i mean this:
18:26 < kanzure> http://diyhpl.us/~bryan/irc/stl2pov/gitduino-post-receive-hook.txt
18:27 < sebastienb> the #!/bin/bash suggests this isn't django.  :D
18:28  * sebastienb is reading it.
18:29 -!- jrabbit [~babyseal@unaffiliated/jrabbit] has joined ##hplusroadmap
18:30 < pasky> kanzure:
18:30 < pasky> oops
18:30 < pasky> kanzure: how long does that openscad / povray take?
18:31 < pasky> kanzure: 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 uselessly
18:31 < kanzure> sebastienb: i don't think you understand what a git hook is :P
18:31 < sebastienb> yup.
18:31 < pasky> kanzure: 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) useful
18:31 < kanzure> pasky: of course; this is an unoptimized script
18:32 < sebastienb> I've got a PHB understanding of this stuff.
18:32 < kanzure> pasky: this is still very debuggy and experimental
18:32 < pasky> or something along these lines
18:32 < kanzure> pasky: the obvious thing to do would be to ping a daemon called renderbot
18:35 < kanzure> er, sorry, i was on the phone for the last 15min
18:36 < sebastienb> no worries.
18:36 -!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has joined ##hplusroadmap
18:36 < kanzure> anyway, no sebastienb, you don't put django code in a git post-receive hook.. although you could if you want
18:37 < kanzure> if someone wants to write a rails gem to add it to gitorious, that's fine
18:37 < sebastienb> but 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 < ybit> i'm guessing gitduino is github with pretty pictures of hardware and some file format for representing changes to hardware
18:37 < kanzure> yes
18:37 < sebastienb> And that would be done in ... django?
18:37 < ybit> sounds like what i was wanting to do
18:37 < kanzure> a "join project" button is trivial in django
18:37 < sebastienb> right.
18:38 < kanzure> it's also trivial in rails (which is what gitorious is built on)
18:38 < sebastienb> and 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:39 < kanzure> pasky's suggestion is to just use gitorious instead of writing a custom django project
18:39 < sebastienb> ah.
18:39 < ybit> my little mockup: http://image.bayimg.com/jaebcaadj.jpg
18:39 < pasky> kanzure: 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 < kanzure> pasky: it's so experimental that it's not even funny
18:40 < kanzure> here's what it renders to:
18:40 < kanzure> http://diyhpl.us/~bryan/irc/stl2pov//dremelfuge/01604aefda5a079f740ff5fa966bcade9511ed80/gears.scad-1101b4abdb.png
18:40 < pasky> oh you could also use girocco but that is very unweb2.0
18:40 < kanzure> http://diyhpl.us/~bryan/irc/stl2pov//dremelfuge/305fce14356203666ebffe6141630bd2b8f240c3/dremelfuge-v4.scad-72422eca27.png
18:40 < sebastienb> ah, pretty gears.
18:41 < sebastienb> kanzure, that was done by that bash script?
18:41 < kanzure> yes
18:42 < kanzure> specifically, when i made a change to cathal's dremelfuge and pushed (uploaded) it to gitduino
18:42 < kanzure> more specifically, made a change to the model definition..
18:42 < sebastienb> ah.
18:43 < sebastienb> And a hook sniffed the  change, and updated the render.
18:43 < pasky> then 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 now
18:44 < kanzure> to gitweb? ha ha
18:44 < sebastienb> kanzure, you're using ... piny for the git web interface?
18:44 < kanzure> ..?
18:44 < kanzure> piny is a set of tools for managing a server full of git repositories
18:44 < sebastienb> Oh!
18:45 < kanzure> piny basically automates all of the pain of setting up git repositories, wikis and mailing lists associated with each project
18:45 < kanzure> plus access controls for different contributors, etc. etc.
18:45 < sebastienb> ok.  When  someone changes text, and a wiki page shows a diff, what software renders that?
18:46 < kanzure> your browser
18:46 < sebastienb> right.
18:46 < sebastienb> but that diff may be inlaid into a webpage, and ...
18:46 < kanzure> i don't know what you're asking
18:47 < sebastienb> It's not crucial right now.
18:47 < kanzure> if you let piny mess with your apache config, it can use ikiwiki's perl scripts to show diffs
18:47 < kanzure> but frankly if you have a django or rails-based site, you should just render your diffs through coderay/pygments/whatever
18:47 < sebastienb> But 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:48 < pasky> it seems piny by defaults relies on cgit to do this?
18:48 < kanzure> pasky: sure
18:48 < sebastienb> Mind you, hiring a guy to help get it working takes priority.
18:48 < kanzure> but he was asking about wiki diffs
18:48 < pasky> ah sorry
18:50 < kanzure> writing a gem for gitorious actually sounds like an ok plan
18:50 < sebastienb> I'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:51 < kanzure> well, if we're using gitorious, then gitorious.. (rails)
18:51 < sebastienb> Ah.
18:51 < kanzure> if we're using a custom django system, it'll be (django)
18:51 < sebastienb> And right now we don
18:51 < sebastienb> And right now we don't know if we're going to use django or gitorious?
18:52 < kanzure> O_o well right now gitduino.com has a prototype of itself written in django
18:52 < kanzure> *written in python using django
18:52 < kanzure> what are you trying to learn from me?
18:52 < sebastienb> Site architecture stuff.  What's going to do what.
18:53 < sebastienb> And the gitorious discussion is pure hypothetical, right?
18:53 < kanzure> well gitorious has a more extensive, more real code base than my fictional django code
18:54 < sebastienb> And would gitorious work neatly with ikiwiki the way django would?
18:54 < kanzure> no, gitorious implements its own wiki iirc
18:54 < kanzure> which is stupid & dumb
18:55 < kanzure> there's probably a ruby-based gem that can be thrown in that works with ikiwiki
18:55 < ybit> i'm going to work on this
18:55 < kanzure> are you?
18:55 < ybit> yeah
18:55 < kanzure> what part
18:55 < sebastienb> :D
18:56 < ybit> i'm not really sure what language, this is all similar to what i've been brainstorming over
18:56 < ybit> if django, i was considering building on top of mercurial
18:56 < kanzure> writing a gitorious plugin would be really quick
18:56 < ybit> if gitorious, the gem route for gitduino sounds nice too
18:57 < ybit> the obvious question, i don't suppose anyone would be willing to use my own dvcs system written in js? :D
18:57 < kanzure> it would be something like:
18:57 < kanzure> add a join table to list images to a specific commit
18:57 < kanzure> have the rendering service POST to the commit model on gitorious
18:57 < ybit> -system
18:57 < kanzure> run the rendering service on a separate vps
18:58 < kanzure> ybit: elevenarm's opinion is that this should just be a pure js client on top of github
18:58 < kanzure> using the github api
18:59 < ybit> that's interesting too
18:59 < kanzure> he and i kind of go overboard when it comes to js.. especially in our paid work
18:59 < kanzure> http://apps.facebook.com/socialmuse
19:00 < kanzure> the client is pure js
19:01  * sebastienb clicks.
19:01 -!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has joined ##hplusroadmap
19:02 < ybit> where is the reprap dev channel?
19:02 < sebastienb> #reprap
19:02 < ybit> oh, i thought there was something like #reprap-dev
19:02 < ybit> \/list wasn't showing anything :)
19:02 < ybit> grr
19:02 < sebastienb> reprap-dev is a mailing list. Compulsory to join, and all that.  :D
19:02 < ybit> i'm probably already subscribed
19:02 < kanzure> reprap-dev seems to forget about reprap-users
19:03 < sebastienb> Well, that's because everyone's a dev, and not just a user.
19:03 < sebastienb> I need to rename it reprap-dev-chat and reprap-dev-support
19:03 < kanzure> huh?
19:03 < kanzure> that's dumb
19:03 < kanzure> just say "development goes here"
19:03 < kanzure> that's why it's reprap-dev
19:03 < kanzure> it's not "for developers only"
19:04 < sebastienb> reprap-dev's intro page does say "development goes here".
19:04 < kanzure> okay, then tell non-development threads to go somewhere else.. if it matters
19:05  * kanzure goes back to work
19:05 < sebastienb> kanzure, should I ping ya in 2-3 days to see how things are going?
19:05 < pasky> well if you need any git-fu help or some-such, feel free to highlight me... the project seems like a nice idea
19:06 < sebastienb> pasky, that's very kind.
19:06 < kanzure> sebastienb yeah sure
19:06 < kanzure> pinging is always good/acceptable
19:06 < sebastienb> Will do.
19:06 < kanzure> pasky: feel free to make creative complaints about the post-receive hook
19:06 < sebastienb> And should I learn django in 15 minutes, or rails?
19:07 < kanzure> sebastienb: up to you.. i say both, but i have unreasonable expectations for everyone (incl. myself)
19:07 < sebastienb> For the stuff we're doing up on the server soonish.
19:10 < sebastienb> I'm guessing django?
19:11 < sebastienb> oh, hey, I just found http://www.reviewboard.org/
19:11 < sebastienb> django based and integrates with git.
19:12 < sebastienb> has a diff viewer.
19:12 < sebastienb> dunno if it has anything to do with what we're up to.
19:12 < sebastienb> kanzure, I should let you get back to work?
19:14 < pasky> kanzure: 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:15 < 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 away
19:16 < ybit> i'm typically busy throughout the week, i'll spend my weekends working on this
19:16 < ybit> and i guess no one should expect anything to come from my work
19:16  * ybit no likey expectations
19:16  * ybit fails miserably typically
19:17 < sebastienb> No worries.  I've got a lot to learn about this stuff.
19:17 < ybit> heh
19:17 < sebastienb> I also have a very keen sense of just how our mediawiki doesn't meet our needs, so ...
19:18 < ybit> as far as web frameworks, i've been leaning more toward js based stuff
19:18 < pasky> kanzure: (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:19 < ybit> from my own experience,i can usually count on more than one programming language to slow work down a little
19:20 < ybit> i trip up easily
19:20 < ybit> ..mostly because i suck
19:20 < pasky> 'nite
19:20 < ybit> night
19:20 < sebastienb> nite, pasky.
19:20 < ybit> sebastienb: you have experience with fpga?
19:21 < sebastienb> no.
19:21 < sebastienb> People occassionally mention them in terms of reprap.
19:21 < sebastienb> I know what they are, haven't touched on.
19:21 < sebastienb> one.
19:22  * ybit gets back to work as well
19:23 -!- strages [~strages@wifi.makerslocal.org] has quit [Ping timeout: 255 seconds]
20:16 < kanzure> i find it retarded that tom is posting about "how to be social"
20:16 < kanzure> http://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 ##hplusroadmap
20:16 < kanzure> why do so many people i know suuuuck
20:46 < QuantumG> the people you know are not statistical outliers
20:59 -!- mayko [~mayko@71-22-217-151.gar.clearwire-wmx.net] has quit [Ping timeout: 252 seconds]
21:00 -!- devrandom [debian-tor@gateway/tor-sasl/niftyzero1] has quit [Ping timeout: 246 seconds]
21:02 -!- jmil [~jmil@c-68-81-252-40.hsd1.pa.comcast.net] has quit [Quit: jmil]
21:12 -!- mayko [~mayko@71-22-217-151.gar.clearwire-wmx.net] has joined ##hplusroadmap
21:56 -!- klord [~klord@64.39.5.118] has joined ##hplusroadmap
22:00 -!- strages [~strages@c-71-207-215-204.hsd1.al.comcast.net] has quit [Ping timeout: 250 seconds]
22:17 -!- klord_ [~klord@72-254-120-166.client.stsn.net] has joined ##hplusroadmap
22:19 -!- klord [~klord@64.39.5.118] has quit [Ping timeout: 246 seconds]
22:29 -!- klafka [~textual@cpe-66-66-10-44.rochester.res.rr.com] has quit [Quit: Computer has gone to sleep.]
22:51 -!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has quit [Quit: mheld]
22:54 -!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has joined ##hplusroadmap
22:57 -!- mheld [~mheld@pool-173-76-224-45.bstnma.fios.verizon.net] has quit [Client Quit]
23:23 -!- klord_ [~klord@72-254-120-166.client.stsn.net] has quit [Ping timeout: 264 seconds]
23:27 < sebastienb> Night, all.
23:31 < kanzure> good night sebastienb
23:35 < sebastienb> I'll ping ya in a few days, eh?
23:36 < ybit> we shall never know
23:36 < ybit> night sebastienb
23:36 < sebastienb> night!
23:36 -!- sebastienb [~sbailard@206.248.158.253] has left ##hplusroadmap ["Leaving"]
--- Log closed Tue Mar 22 00:00:10 2011