Camelia, the Perl 6 bug

IRC log for #kaizendo, 2011-06-07

| Channels | #kaizendo index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
07:20 sjn http://bergie.iki.fi/blog/de​coupling_content_management/
09:46 TommyK joined #kaizendo
09:47 TommyK left #kaizendo
09:48 TommyKan joined #kaizendo
10:17 sjn o/ TommyKan
10:17 TommyKan hello
10:18 TommyKan Thought I'd pop in to see what was going on
10:18 sjn not much here :)
10:18 TommyKan How is the project going?  Is it your full time occupation?
10:18 sjn nah, only part-time
10:19 sjn tings are going slowly forward :)
10:19 sjn atm, I'm spending some time getting a book project up and running, so we can learn a little from that
10:19 TommyKan I see
10:20 TommyKan Have you found potential users/sponsors?
10:20 sjn plenty of users
10:20 sjn haven't really spent much time on finding sponsors
10:20 TommyKan :)
10:20 sjn did that a little last year, but it didn't work out
10:20 sjn :-/
10:21 TommyKan It's the nature of open source!
10:21 sjn yep
10:21 sjn got a little support from two foundations though.
10:21 sjn but only enough to do some travelling and buy some stuff
10:22 sjn TommyKan: so, what brings you here? :)
10:22 TommyKan well, I thought I'd find out a little more about a project that has so many parallels to mine!
10:23 TommyKan I don't have any ambitions to make much money from it, so it's kind of hard to commit resources
10:23 sjn yeah, your project is that tool for negotiating contracts and such
10:23 sjn right?
10:23 TommyKan well, yes.  It's more general than that
10:23 sjn yep
10:23 * sjn looked a little at the sandbox you linked to
10:24 sjn have to say your project is quite a bit more complicated that what I had in mind :)
10:24 TommyKan It can be used to scrutinise contacts and laws, but it can be used in any context where there are diverse opinions.
10:24 TommyKan Yes, it does look complex at the moment - I'm hoping to make it simpler
10:24 sjn thought it had a good way of showing alternative suggestions for specific content
10:25 sjn seemed so at the first glance, at least :)
10:25 TommyKan Thanks!
10:25 TommyKan Do you have a working demo of Kaizendo online?
10:26 TommyKan or is Kaizendo.org the demo?
10:26 sjn no working demo online
10:27 TommyKan I see. Perl is still scary to me, so I haven't been encouraged to install it
10:27 sjn you can get it up and running fairly easily (if you're familiar with Perl and CPAN) though
10:27 sjn install it?
10:27 TommyKan :D
10:27 sjn ah, you're a windows user? :)
10:27 TommyKan on my local machine
10:28 * sjn really hasn't tested Kaizendo on windows
10:28 TommyKan no, no, no.  Mac, but not trained in IT
10:28 sjn well, then Perl should already be installed
10:28 sjn not all modules though
10:28 sjn anyhoo, the tool really isn't that much to look at
10:29 sjn still spending some time trying to figure out what could be done simpler
10:30 sjn was thinking of gutting some of the document storage backend and replacing it with a simple storage layer that uses git :)
10:30 sjn TommyKan: what's your field, since it's not IT?
10:37 * sjn topic
10:38 sjn oops
10:38 Topic for #kaizendo is now http://kaizendo.org/ | http://talk.kaizendo.org/ma​ilman/listinfo/kaizendoers | http://kaizen.do/talks
10:39 sjn krunen: taking the trip to town later today. I suggest we find a quite pub for working at the outline
10:40 TommyKan left #kaizendo
10:43 TommyKan joined #kaizendo
10:47 sjn TommyKan: connection issues? :)
10:49 TommyKan left #kaizendo
10:50 TommyKan joined #kaizendo
10:50 TommyKan are you talking about using git for storing content (as in, not as software repository)
10:51 sjn yes
10:51 TommyKan I had no idea that git could be used for that,
10:51 TommyKan but it kind of makes sense
10:51 sjn git stores text
10:52 TommyKan it would be hard to extend though, don't you think?
10:52 sjn extend?
10:52 TommyKan if you decide that you want extra features further down the line...
10:52 sjn just need to decide on a good way to keep track of content and aspects, and that's about it...
10:53 sjn (actually, not doing too many features is a rather strict goal I have)
10:53 TommyKan makes sense :)
10:53 sjn KISS FTW :)
10:53 sjn but yes, some features will be useful to have
10:54 sjn to make those possible, I try to decouple content from other features as much as I can
10:54 TommyKan Yes, that's sensible
10:55 TommyKan I was wondering if others are working on the project too?
10:55 sjn mainly by having an (as far as possible) complete REST API to the current features
10:55 sjn not many atm. t0m spent some time last year getting us started
10:56 sjn another guy (not here has helped with some thoughts on the UI/front end issues
10:56 TommyKan Were they frinds of yours, or people who were attracted to the project?
10:56 sjn sveinns is trying to help with other stuff, but he's still learning :)
10:56 TommyKan I ask because it's very encouraging when others help out - makes you want to do more yourself
10:57 TommyKan It's a lonely world otherwise!
10:57 sjn only one in the channel that I have a longer background with is krunen :)
10:57 sjn TommyKan: yes, that's trye
10:57 sjn true*
10:58 TommyKan I best get on with my paid work now.  It's been a pleasure to touch base.
10:58 TommyKan I'll be back soon
10:58 sjn I've come to realize that a project's success is much more dependenent on the _second_ person than the first one :)
10:58 sjn ok, feel free to drop by later! :)
10:59 TommyKan I know what you mean by the second person - the one with the perspective, and the one who is more critical than you are
10:59 TommyKan neways
10:59 TommyKan speak soon
16:32 sjn krunen: http://irclog.perlgeek.de/perl6book/2011-06-02
16:32 sjn krunen: http://irclog.perlgeek.de/perl6book/2011-05-28
16:34 sjn krunen: http://irclog.perlgeek.de/perl6book/2011-05-14
17:43 github-sjn joined #kaizendo
17:43 github-sjn book: outline-rework Moritz Lenz * 0281365 (1 files in 1 dirs): [basics] made first example more robust wrt whitespace. Text still needs updating
17:43 github-sjn book: outline-rework Moritz Lenz * 346ed6a (1 files in 1 dirs): [basics] start to updated description of the new first example
17:43 github-sjn book: outline-rework Moritz Lenz * e83af18 (1 files in 1 dirs): [basics] further wording changes after the s/split/words/ refactor
17:43 github-sjn book: outline-rework Moritz Lenz * e9930d3 (1 files in 1 dirs): [basics] fix duplicate invocant explanation found by PerlJam++
17:43 github-sjn book: outline-rework Moritz Lenz * 3d702f6 (1 files in 1 dirs): Merge branch 'first-example-more-robust'
17:43 github-sjn book: outline-rework Salve J. Nilsen * e9f6bbb (1 files in 1 dirs): Merge remote-tracking branch 'perl6book-upstream/master' into outline-rework
17:43 github-sjn book: outline-rework Salve J. Nilsen * fda2914 (0 files in 0 dirs): Add a the beginning of an experimental outline
17:43 github-sjn book: outline-rework Daniel Stojanov * c62b02f (1 files in 1 dirs): fixed a/an typo in regexes.pod
17:43 github-sjn book: outline-rework Daniel Stojanov * 493f99e (1 files in 1 dirs): a/an typo in regexes.pod
17:43 github-sjn book: outline-rework Jonathan Scott Duff * 76b1e78 (1 files in 1 dirs): minor wording fix (daniel stojanov)++
17:43 github-sjn book: outline-rework Jonathan Scott Duff * c284546 (1 files in 1 dirs): Merge pull request #55 from daniel-s/master ...
17:43 github-sjn book: outline-rework Moritz Lenz * 8ebeb7e (1 files in 1 dirs): [multi] fix order of multis, pharvey++
17:43 github-sjn book: outline-rework Moritz Lenz * 4ed4419 (11 files in 1 dirs): [src] start to properly cross-link sections
17:43 github-sjn book: outline-rework Salve J. Nilsen * 6eacbcc (11 files in 1 dirs): Merge remote-tracking branch 'perl6book-upstream/master' into outline-rework
17:43 github-sjn left #kaizendo
18:42 sjn note to self: http://wiki.creativecommons.org/LRMI/FAQ
23:00 TommyKan left #kaizendo

| Channels | #kaizendo index | Today | | Search | Google Search | Plain-Text | summary