14:23 ilbot2 joined
moderator brainstorming lists: gist.github.com/203173 paste.lisp.org/display/88288
masak I think public logs would be a boon. 14:23
moritz_ here they are, at the usual location.
masak hugs ilbot2 14:24
14:25 hugme joined
moritz_ better :-) 14:25
masak hugme: hug ilbot2
hugme hugs ilbot2
14:40 pmichaud joined 15:07 [particle] joined 15:36 FOAD joined 16:09 mberends joined 17:50 chromatic joined
moritz_ wow, we have attracted quite a crowd so far ;-) 17:51
PerlJam book people and bots 17:52
moritz_ just two bots
masak is a bot 17:54
moritz_ not bot enough to get a /voice ;-)
masak p'haps not :) 17:55
17:55 diakopter joined 17:56 parduncia joined, TimToady joined
diakopter is new here 17:58
PerlJam we're all new here :)
masak :)
mberends here is new too :)
masak mberends: I was going to type that! :)
masak re-reads the script 17:59
it says in here that we're supposed to have a gathering of some kind in a minute or so.
and that it'll be fun and exciting! 18:00
TimToady what will we say?
diakopter that!
moritz_ if we knew that, we wouldn't be here
anyway, let's get started
masak guys, you're freaking me out! stop saying everything that's in here!
moritz_ did jnthn want to come? 18:01
masak yes, but I don't know if he's un-busy yet.
PerlJam don't let jnthn in here! It'll distract him from implementing stuff :)
18:01 jnthn joined 18:02 last joined
moritz_ great 18:02
so
masak meeting.
moritz_ we want a Perl 6 book
masak to the point where we're willing to write it.
moritz_ we want it to be done by the time we release rakudo *, at least roughly
masak and we have a few loose ideas already.
moritz_ masak and I have gathered some brainstorming notices, see /topiic
(those were gathered independently) 18:03
masak ooh, moritz_++
moritz_ also, this channel is publicly logged at irclog.perlgeek.de/perl6book/today
mberends "Six Chapters" is really catchy!
PerlJam all we need is another 6 from somewhere and we've got the number of the beast 18:04
diakopter start with the 6th edition? Volume 6?
PerlJam bad company had an album entitled 10 from 6, we could do 6 from 10 :) 18:05
masak "Six Ways To Perl 6"
moritz_ how do we want to proceed? got through the list of proposals, discuss them along the way?
TimToady I've decided we should rename Perl 6 to Perl 7 since it's really a different language from Perl 5
:)
PerlJam How much should the book be about Perl 6 vs. how much should it be about Rakudo? 18:06
masak the scary thing is that I didn't know whether TimToady meant it or not.
moritz_ PerlJam: it should be about the part of Perl 6 that rakudo implements by then
masak PerlJam: I figger Rakudo is the medium, but Perl 6 is the focus.
moritz_ right.
jnthn Agree.
PerlJam But what to do about the bits that rakudo *doesn't* implement?
jnthn It's about the subset of Perl 6 that Rakudo * happens to support.
PerlJam Just don't mention them?
or lots of sidebars?
moritz_ PerlJam: there's always room for appendices ;-) 18:07
masak PerlJam: mention them (a la sidebar/footnote) if it's deemed worthwhile.
chromatic That depends on how practical the book should be.
PerlJam chromatic: ueber practical would be my betn
s/betn/bent/
mberends the readers want runnable code as well as explanations
jnthn I'd hope Rakudo * will be at the point where we can write a book describing a bunch of features that work together, without having to constanting note "but don't do X"
moritz_ well, I made the experience that NYI features are very much subject to change
PerlJam jnthn: indeed
jnthn *constantly 18:08
moritz_ so if we write about macros without having them implemented, 80% will turn out not to work by the time they are implemented
masak as far as I'm concerned, there's only one decision of import to be made today. (others might disagree, of course): what should the first chapter be about?
jnthn Right.
chromatic Write the first chapter last.
pmichaud as an overall guideline, I expect the number of "very useful but nyi" things in Rakudo to be dramatically smaller than today
PerlJam also ... is the book meant to be publishable in the O'Reilly sense or just as a continual work in progress?
masak well, the chapter we're to write first, then.
moritz_ PerlJam: both ;-) 18:09
pmichaud PerlJam: I'd aim for publishable work
jnthn I think we need to step back from that a bit first and ponder how the book may be organized.
pmichaud but also work in progress
moritz_ what jnthn said
masak jnthn: nod.
chromatic Assume you have a publisher willing to make yearly revisions. Possibly bi-annual.
jnthn Will we have a chapter that focuses on OO, for example? One on subs/sigs? One on basic constructs?
Because if we're in a multi-author environment, there may not be a "chapter to write first". 18:10
pmichaud "a book that allows a junior programmer to learn a useful subset of Perl 6"
masak chromatic: bi-annual = half-yearly or with two-year gaps?
mberends assume the reader is not a beginner, so go straight for classes and objects first
pmichaud I wouldn't assume the reader is P5, though
chromatic half yearly
jnthn It may be that different people take on being the "leader" (for want of a better word) for a particular chapter.
masak jnthn: yes, I had that thought as well. 18:11
moritz_ mberends: I disagree. We shouldn't assume perl knowledge, so we should explain some lexical conventions, sigiled variables etc. first
PerlJam jnthn: collaboration is as collaboration does :)
masak jnthn: might be good to pick some chapters to captain already.
moritz_, mberends: I think we need to both assume and not assume Perl knowledge at the same time.
jnthn PerlJam: Oh, I'd very much want to encourage everyone involved in the effort to feel free to review / edit / hack on any chapter,.
18:11 colomon joined
moritz_ let's try to come up with a minimal set of features we want to cover, shall we? 18:12
pmichaud +1
masak aye.
moritz_ I want:
lexical conventions, variables, scoping, basic syntax
subroutines, signatures
OO, types 18:13
grammars
TimToady might be easier to list what you want to leave out :)
jnthn multi-dispatch probably fits in amongst the above too.
PerlJam moritz_: are these particularly ordered or just thought-first order?
moritz_ PerlJam: thought-first
aye, multi dispatch
but for example my first line can be covered rather quickly
every sane programmer knows block scoping, to some extend 18:14
pmichaud
.oO( Is Perl 6 suitable for sane programmers...? )
diakopter Implementing Your Own Capture
PerlJam the first chapter we should write should be the preface that explains the audience for the book and gives a general lay-of-the-land :)
masak for some reason, I've come to think of the book as being similar in structure to the Exigeses, in that it starts with a whole example script, and elucidates wrt that example. 18:15
moritz_ masak: agreed
masak now, that might or might not be a good i... ok :)
moritz_ luckily that doesn't conflict with what I wrote so far ;-)
chromatic What's the goal of the book?
TimToady don't ask good questions!!! 18:16
moritz_ chromatic: enable programmers to get started with (and a bit deeper into) Perl 6 (first rough vision statement)
masak chromatic: to show Perl 6 to people in a way that makes them say "well, ok, I want this. now."
chromatic What should they be able to do after reading the book?
PerlJam given rakudo and the book, a intermediate programmer should be able to ...
pmichaud junior programmer 18:17
mberends I'd like it to complement the Rakudo Star release, acting as its introductory tutorial
moritz_ chromatic: answer the beginners question on perlmonks with runniing Perl 6 code
and a bit more, hopefully
(if others disagree, please step forward)
PerlJam silence is assent 18:18
diakopter watches everyone else take a step back
chromatic What's its relationship to Rakduo *? (See also mberends's question.)
TimToady reserves the right do disagree later by writing a different book :)
moritz_ what mberends said. For some value of "introductory".
TimToady *to
PerlJam TimToady: please do! :)
moritz_ TimToady: no, henceforwards you're forbidden to write any Perl 6 related book! ;-) 18:19
pmichaud I want the book to complement the release in the sense that a software product really wants to have supporting documentation
so that when someone says "okay, how do I use this", we can say "here's a book" :)
colomon Is the primary focus to be the teaching or the examples?
masak colomon: what's the difference?
moritz_ colomon: teaching by examples and explanation 18:20
chromatic Is it a tutorial or a reference?
moritz_ it's really NOT a reference
colomon For instance, would you go for the best implementation of the example, or the one that covered the topics you wanted to teach in a chapter?
masak I hope to make u4x the reference for April.
colomon (I guess in my mind I had been picturing it being "This is why Perl 6 is cool" as much as "here is how you learn Perl 6".) 18:21
mberends colomon: cover the topics
moritz_ colomon: we'd want to pick an example which is the best implementation of that problem and shows the topics we want to cover
which is why it will be very hard to chose a good example
pmichaud I have trouble with "best implementation", fwiw :)
mberends +1
pmichaud tmtowtdi
moritz_ pmichaud: s/best/a very good/
colomon pmichaud: for sure.
mberends the perl5 perlfaq docs are impressive for breadth and depth, it would be great to be able to answer even half of those questions for Perl 6. eg How do I...?
chromatic That sounds more like a recipe book, mberends. 18:22
masak Cookbook-like.
moritz_ I think that's a different book
PerlJam Also many of the perlfaq answers are: look at such-and-such module on CPAN
definitely a different book
moritz_ I want our readers to be able to come up with most of the answers themselves
mberends ok, ok :)
jnthn (good examples) To me I think it's like, "does this feel like a natural way to solve the problem in Perl 6?"
PerlJam so, getting them used to the Perl 6 "culture" or "style" or "vibe" 18:23
moritz_ jnthn: that's certainly an important criterion, yes
jnthn That is, the example may not be the only way, but it doesn't feel like it was concoted either.
moritz_ well, for sure we'll try to write idiomatic code 18:24
chromatic Let's try a different approach to this question.
masak if there are several ways, one could mention the other ways, and point out pros and cons.
pmichaud I have a different tack to offer
chromatic diakopter suggested "What is this book *not*?"
pmichaud we know that we want to cover some fairly advanced stuff
grammars, multimethod dispatch, object system
moritz_ it will be not a reference
pmichaud perhaps we should come up with those examples first 18:25
masak aye.
moritz_ pmichaud: those are the hardest part of the whole book
pmichaud then, once we have them, we write the parts that "you need to know to get to those examples"
mberends masak: the long outstanding code review of Druid could be a chapter about games, structure, good practices
moritz_ back to the question of what it's not... 18:26
I fear it can't be too comprehensive (missing time)
masak mberends: I'd love to see a game in the book. probably not Druid, though.
colomon not a cookbook (even thought cookbooks are awesome)
moritz_ right
masak mberends: it's too weird a game, and that would detract from the topic. :)
PerlJam but is it tutorial in nature? 18:27
chromatic Not a comprehensive reference.
PerlJam Not *a* tutorial but a series of them.
masak six tutorials.
moritz_ I don't want to focus on that number too soon
masak possibly with dependencies, as pmichaud mentioned.
$N tutorials.
diakopter other options might be 'getting started with perl 6', 'the complete perl 6 reference', 'learn to program by learning perl 6 on rakudo *', 'learn rakudo * perl 6'
moritz_ I like the idea, but I think it's a fairly limiting restrictions
pmichaud in some sense I want us to be able to show the power and expressiveness of the language 18:28
(1) "Wow, you can do that?"
moritz_ +1
pmichaud (2) "Oh, that's so easy!"
moritz_ +1
pmichaud an obvious "Wow, you can do that" is grammars and regexes
moritz_ sure
PerlJam pmichaud: the slide you have with the deck of cards example is shiny in both of those ways
colomon PerlJam++
pmichaud pj: yes, it is 18:29
I've been meaning to write that up as an article
I was thinking of writing it up for TPJ, but it could go here instead
diakopter 'what's new in perl 6' 'what's cool about perl 6'
pmichaud *TPR
mberends cool solutions to generally known challenges, where P6 out-golfs the rest
PerlJam hmm 18:30
not golf
TimToady mberends: that sounds more wiki-ish
diakopter 'using perl 6 gives you wings'
pmichaud anyway, so I'm thinking that we focus on a few "Wow you can do that" sorts of examples for the "later" chapters, and then start filling in details of whatyou need to know in the earlier chapters
so, come up with good examples to demo regexes and grammars
good examples for objects and methods and multidispatch
and types 18:31
and I think if we just have those items, that pretty much dictates the rest of the first edition
diakopter 'perl 6 overview (and coolness!)'
moritz_ in some sense I like the JSON::Tiny module as an example (I don't imply we'll use it, though). Here's why:
it solves a problem completely
in a few lines really, they fit into a book easily
it's a real-world problem 18:32
it uses some shiny Perl 6 features
masak moritz_: I like the idea, or that class of ideas.
pmichaud +1
moritz_ (grammars, action methods, multi dispatch for creating the JSON)
masak we should definitely have something like that.
moritz_ and the code is easy to understand
PerlJam sounds good to me.
moritz_ it doesn't show off all the shiny grammar features, but it's still nice
masak I think of that as our "language/grammar/parsing" example.
chromatic Is this "Overview of Perl 6 with Rakudo Star"?
pmichaud "Overview" might be too broad 18:33
diakopter "Skim"
moritz_ skim plus tutorial, maybe
PerlJam The title may come later once we're written more of the book.
moritz_ aye
PerlJam btw, where is the book to live ? github? 18:34
moritz_ I don't think chromatic meant the title, though
diakopter the title connotes much about the audience and structure
moritz_ more the idea
pmichaud well, without worrying about title, we still want to have a coherent vision
moritz_ github: +1
pmichaud perl6 repo?
er, perl6 account?
masak aye.
moritz_ wfm
PerlJam yes
pmichaud let me know what it's to be called and I'll create the repo :) 18:35
PerlJam who is the "I" that strongly prefers LaTeX?
moritz_ let's think a bit more about the vision and "what it's not" in private, and focus on technical things
PerlJam: that's masak
PerlJam pmichaud: perl6-book :)
moritz_ pmichaud: just call it "book" for now
diakopter "tree-killer"
moritz_ or perl6-book, fine by me too
what about license?
pmichaud what license did the Parrot+PIR book use? 18:36
moritz_ in the end I'd love to see it under a very permissive license, but I don't know if that's the right thing to start with
PerlJam masak: do you edit it by hand or do you have some fancy editor that aids? (I haven't looked at LaTeX in years)
moritz_ I have no idea how license affects publishing
chromatic: can you give us some insight on that? are there pitfalls?
masak PerlJam: I usually write LaTeX by hand. it's one of the nicest markups out there, when it comes to writing by hand. 18:37
moritz_ that's another thing - I love latex, but it's not so well suited for a mixture of normal text and code
chromatic We didn't mind a permissive license on the PIR book, nor its presence in the Parrot repository.
Profits go to PaFo on that.
masak PerlJam: but I also automate/script a lot of things for book generation.
moritz_: I beg to differ. 18:38
PerlJam moritz_: so, what would you prefer?
chromatic PseudoPOD worked out well for the PIR book.
moritz_ for normal text + code I really prefer POD
PerlJam moritz_: me too
masak I wouldn't mind POD.
moritz_ \\verb|$foo| is just too clumsy, compared to C<$foo>
pmichaud heh
I wonder if a pod formatter could be an example in the book :)
chromatic My $company toolchain is happy with PseudoPOD -> LaTeX -> PDF -> print. 18:39
moritz_ (oh, and I don't want a single 'foo' or 'bar' in the book - OK?)
PerlJam We could even have an example perl 6 program that parses the POD and generates LaTeX or something :)
masak moritz_: :)
moritz_: what about 'Austria"?
mberends pmichaud: that's how I got involved in Perl 6
moritz_ and neither foobar, baz and Quox
masak: Austria is much better
pmichaud if you don't allow bars, that might exclude jnthn++ .
:)
masak *lol* 18:40
moritz_ well, *that* kind of bar is fine ;-)
pmichaud although I guess he would say "pub" :)
moritz_ so - license == AL2 ?
chromatic I'm more comfortable with a CC license.
PerlJam +1 CC
pmichaud I'd go with CC, I think
chromatic I wear my publisher hat for this. 18:41
moritz_ CC wfm
masak CC is nice.
chromatic attribution, noncommercial, share alike
?
pmichaud wfm
"book" or "perl6book" for the repo? 18:42
moritz_ and "commercial" is allowed for the authors?
masak why noncommercial?
pmichaud: 'book'
less to type. :)
jnthn CC fine for me too
PerlJam masak++ ever practical :)
diakopter will particular individuals be assigned 'ownership' of certain areas? (someone to own the table of contents/chapter organization, someone to own each chapter)
PerlJam diakopter: do you mean ownership as in responsibility or more like copyright? 18:43
jnthn I'd say "stewardship" more than "ownership".
PerlJam jnthn++ execllent word
chromatic Commercial is allowed for the authors.
diakopter own, as in 'responsible for', yeah
masak diakopter: I think that's inevitable in some sense. but it'd be nice to encourage a policy of 'anyone can improve anything'.
moritz_ +1
PerlJam masak: I think it's going to be hard to stop some people from improving everything ;)
diakopter but also, 'point of communication for' 18:44
pmichaud diakopter: we do that already in the codebase; it somewhat falls out naturally I think
masak diakopter: as long as that doesn't block people.
pmichaud i.e., moritz tends to be the test captain. jnthn++ is the oo/signature/multidispatch person.
we don't have formal assignment, we just know people's general areas of responsibility 18:45
(moritz++, btw, didn't mean to imply non-karma)
moritz_ :-)
pmichaud perl6/book.git now available 18:46
[particle] you might consider calling it starbook, if there are to be other books on rakudo under the rakudo github account
moritz_ every mention of my name increases my karm^Wego
[particle] wait, is this a perl 6 book, or a rakudo star book?
PerlJam perl 6
moritz_ both.
[particle] arrives from scrollbackland, a little confused
moritz_ in some sense
diakopter whichever it is, it needs to be clear in the title
masak Perl 6 using Rakudo Star.
PerlJam it's a perl 6 book with an eye towards practicality
colomon It's a perl 6 book, but it should work with Rakudo Star.
jnthn [particle]: I'm kinda seeing it as a book about the subset of Perl 6 that you can run on Rakudo *. 18:47
[particle] it needs an installation chapter
masak "Become a Perl 6 Star!" :)
PerlJam (i.e., you have to be able to run the code somewhere)
[particle] how to use proto, etc
pmichaud how about "STARting with Perl 6"? :-P
masak would be nice to have the userakudo web page online at that point...
moritz_ enough starshedding
chromatic agrees with jnthn.
mberends diakopter: as chromatic++ said, write chapter 1 last. And then write the title last after that ;)
pmichaud I think the focus is more Perl 6 than Rakudo Star
PerlJam pmichaud: that's not a half-bad title startshedding aside
s/rts/rs/ 18:48
pmichaud Rakudo Star is just a stage we'll be going through.
[particle] ok, so i really think 'book' is too generic a name for the repo
moritz_ to late
pmichaud we can rename it later
renaming is easy on github
[particle] yep
moritz_ the repo is just part of an URI
diakopter mberends: that would be nice, but *something* has to constrain the direction (title or chapter title/semantic fields, or something)
moritz_ s/repo/repo name/
[particle] so the codename for the book is 'book' :)
moritz_ right, because it's a book. 18:49
masak I agree that we still have too few constraints.
moritz_ what kinds of constraints would you like to add?
masak I don't know, something that points the way forward.
PerlJam how about we get an outline going and we can iteratively refine it until it turns into chapters of text.
TimToady it should not turn into a Camel designed by a Committee
mberends let's make random submissions into the repo for a week or so, and then meet again
masak specifically, I'd like it to be clear what to do until the next monthly release. 18:50
pmichaud points the way forward: first, let's figure out our "release schedule"
masak +1
pmichaud i.e., let's pick dates and deadlines now
PerlJam I volunteer to start a preface btw
masak PerlJam: the one that's supposed to be written last? :)
moritz_ arbitrary picking: one day after each rakudo release 18:51
PerlJam the preface it's first, it's zeroth
pmichaud some scheduling background: Rakudo #28 will be released on April 22, 2010
diakopter some words about an even-somewhat-consistent tone: should it be whimsical, serious/professional but with sublime puns, matter-of-fact, acting-ultra-pragmatic, or else
pmichaud Rakudo Star will therefore be sometime between the 22nd and the 30th
moritz_ that means we won't have a full chapter up to the first release date, but that's fine IMHO
masak moritz_: that gives us 16 days until the next release. yes, that might be enough.
pmichaud I expect that we will do some pre-releases of Rakudo Star in early 2010 18:52
i.e., to test things out and see how it's hanging together
moritz_ any objections to "1 day after the monthly rakudo releases"?
masak diakopter: I also thought of asking that question. I don't think it's something that can be decided beforehand.
pmichaud I sometimes like 2 days, but 1 works better I think 18:53
PerlJam moritz_: wfm
pmichaud i.e., Friday is better than Saturday
masak diakopter: I would love for it to be seriously whimsical, but the only way to find out is to write it.
diakopter masak: an even more basic question is whether it should have a bunch a different tones, or an even somewhat consistent one.
pmichaud I'll commit to write a draft of my playing cards example and put it in the book repo. it's okay if it doesn't make it into the final cut, but it might give us a place to start
moritz_ pmichaud: great 18:54
masak aye, releases for the book aren't as time-consuming as those for Rakudo. the test suite for the book will not be as big. :)
PerlJam diakopter: Our fearless editor can help with that :)
colomon pmichaud: seems like the start of a chapter?
masak diakopter: a somewhat consistent tone, at the very least.
diakopter as in, "haha; whee; isn't this fun?" or "JFDI; here's how"
pmichaud colomon: I just want to see it published. I think it might be useful for the book, if only to give people something to react against
where "published" means "available for others to read", not necessarily in book format 18:55
PerlJam pmichaud: it's a good small "killer app" kind of thing.
pmichaud PerlJam: exactly
moritz_ it might be too killer app, but that's fine for now
pmichaud right
moritz_ so, +1 to submitting it
pmichaud if it's too killer app, that's okay
it's worth writing in its own right
I'd like to see jnthn's example from NPW written up also, fwiw :) 18:56
masak I'll commit to setting up a Makefile that renders the book in PDF form or similar. so that there's something palpable to comment on.
pmichaud the one that did the sql stuff using multi dispatch, junctions, etc.
it might also be "too killer app", but it was a great example
masak doesn't remember that one
moritz_ I volunteer to write some summary of what we agreed on (and what not) and put it somewhere in meta/ in the repo
pmichaud excellent 18:57
diakopter here's a (different) idea: "Implementing Perl 6 - Hop in; the water's great!"
masak moritz_: please, no meta/ dirs :)
jnthn pmichaud: Ooh, that good be an idea.
pmichaud and, we can potentially always have chapters or useful things in the repo that don't make it into the printed copy :)
chromatic I have tools for PseudoPOD that make nice LaTeX and some nice stylesheets.
masak moritz_: plans/ is fine.
jnthn pmichaud: The paper/scissor/stone multi-dispatch was another one I was pondering.
moritz_ masak: plans/ is fine
PerlJam jnthn++
masak chromatic: great, I'm interested in those.
jnthn my Can of Beer $staropramen # should not make it in though ;-)
PerlJam chromatic: put them in the repo
pmichaud I liked the sql example because it had some practical use 18:58
PerlJam (or otherwise share)
moritz_ jnthn: yes, that can be go in, but I don't know if it needs to be a leading example for one chapter
s:1st/be /
pmichaud paper/scissor/stone was already published online somewhere, I think :)
moritz_ oh, and I'll add perl6/book to hugme
jnthn I've used it at many talks too.
moritz_ pmichaud: so what? ;-)
pmichaud just saying we might be able to steal words instead of rewriting them :)
moritz_ so 19:00
we have a way forward
shall we meet again in a week, same time, same "place"?
jnthn Works for me.
PerlJam yes
mberends ok
chromatic wfm
pmichaud just to confirm, we plan to release something on Oct 23 ?
moritz_ pmichaud: yes 19:01
pmichaud okay
PerlJam what does "release" mean exactly?
pmichaud is it possible that we're overloading that week with too many release announcements?
moritz_ PerlJam: it means we give the public something to talk about ;-)
pmichaud parrot, rakudo, book ?
moritz_ pmichaud: good point
PerlJam pmichaud: I don't think so.
masak make one release announcement.
pmichaud for me, iwbni "release" means "we have a pdf/tarball/something that represents that release of the book"
jnthn We don't need to make a huge thing of it.
PerlJam moritz_: I guess I'm asking how?
pmichaud well, we know there will be parrot and rakudo announcements 19:02
jnthn Just a point to take stock of what we've achieved.
[particle] so there'll be a perl 5 release, a parrot release, a rakudo release, and a perl6book release in the same week?
PerlJam pmichaud: where does this thing live? Just in the repo for now?
jnthn [particle]: yeah but Perl is still dead
;-)
pmichaud PerlJam: I'd like to see us have tools that "make release" for the book
ideally, they'd package things up into a PDF
and perhaps some other files
[particle] it's dead three weeks every month, at least :P
pmichaud and build a tarball
that we then put the tarball and/or PDF into the "Downloads" section of GitHub
and that's our "release" 19:03
masak +1
pmichaud same as what we do for Rakudo
mberends book release = polished html pdf and other formats
masak btw, found the SQL example. that's just EVIL. :) jnthn++
moritz_ masak: URL?
masak jnthn.net/papers/2009-npw-perl6expr...slides.pdf
pmichaud masak: but worth writing up, yes?
masak pmichaud: very possibly.
moritz_: the slide with a >>~~<< in it. 19:04
jnthn I'd want to explore it a bit more first.
pmichaud imo, good examples deserve blog postings, at the least.
even if they're "That's totally EVIL" examples
jnthn It's not *that* evil. :-P
chromatic Building PDF from LaTeX requires some other tools installed.
Building LaTeX from PseudoPOD requires some Perl 5 tools installed too.
Just a note, not a warning. 19:05
moritz_ wfm
pmichaud I don't mind if we say that certain tools (not in the repo) have to be present in order to cut a release
masak that's to be expected.
a general interested reader won't need those tools anyway.
pmichaud instead of /plan, I'd suggest docs/, and have a release-guide.pod
chromatic I can make a list of those tools; I need to do that for the Modern Perl book anyway.
PerlJam chromatic: please do.
moritz_ chromatic: great
pmichaud same as our other projects
masak +1
moritz_ so 19:06
did we reach a common point on the release date? 19:07
chromatic April 22, 2010?
moritz_ hugme: add moritz to book
hugme hugs moritz. Welcome to book!
moritz_ chromatic: I meant regular releases
hugme: add masak to book
hugme hugs masak. Welcome to book!
masak moritz_: one-day-after-Rakudo sounds good to me.
[particle] it's a good start.
pmichaud let's start with that, we can always change it if it doesn't work out
moritz_ ok 19:08
anything else we need to discuss before we adjurn this meeting?
pmichaud adjourn +1
anyone going to blog this? ;-)
moritz_ pmichaud: that's going to be the first release announcement
I can write that up
pmichaud +1 19:09
PerlJam pmichaud: good idea. I've been slacking for ironperl :)
moritz_ hugme: add jnthn to book
hugme hugs jnthn. Welcome to book!
chromatic Note that my company will need a week and a half to get printed books for the April release.
jnthn adjorn +1 # my dinner just finished cooking
moritz_ chromatic: noted
pmichaud I think we should target having something semi-final for March 19:10
chromatic March would be good.
pmichaud April is Rakudo *'s release, but I'd like to see everything mostly done by March
(my internal planning deadlines are actually february for many things) 19:11
moritz_ I'll stay here in the channel if we need larger discussions related to the book
pmichaud channels are cheap :)
moritz_ apart from that: meeting adjourned. have a great time everyone
masak moritz_++
pmichaud (it would be good for someone to update the README file in the book repo) 19:12
moritz_ ok
19:31 parduncia left 19:53 cognominal joined 20:22 diakopter left 22:10 FOAD_ joined 22:36 nbrown joined 22:37 nbrown left 23:23 FOAD_ joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!