Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/
Set by moderator on 29 September 2011.
00:48 bluescreen joined 01:02 whiteknight joined 06:05 alvis joined 09:05 lucian joined 12:17 bluescreen joined 13:21 jlaire joined 18:22 alvis joined 19:04 NotFound joined, benabik joined, whiteknight joined
whiteknight WHAT I DID: Played with the alerts code a little. Last-minute release prep, testing, windows fixes 19:06
WHAT I WILL DO: Put out the release later this evening, try to get some branches merged in thereafter.
EOR
19:07 benabik joined, tadzik joined
alvis What I did: 19:10
* Set up a remote branch 'documentation_revisions' on github
* Posted blog on parrot.org and email to parrot-dev/parrot-users about
it
* Wrote (but will post after 3.10.0 release) blog and email, asking for input/advice/suggestions on Chapter organization of Developer & User Manuals
* Started revision of './README' (converting to '*.pod', plus corrections) 19:11
* Started working on github pages to begin the process of converting'docs.parrot.org' to github pages
* Further research on an autogen indexer for parrot docs
- Temporarily confiscated and setup my wife's Vista box to test Parrot 3.10.0 under Vista (MS Windows SDK) & Cygwin 19:12
- Temporarily confiscated and setup my wife's XP laptop to test Parrot 3.10.0 under XP (via VC++6.0) & Cygwin
EOR
NotFound What I did: 19:16
-parrot
* Testing and minor fixes
-winxed
* Several code generation optimizations, specially for expressions
in void context
* Improved syntax error detection and its messages
* Added testdebug make target to test debug mode and exercise
the assertions in the stage 1 compiler
* Released 1.4.0, and shortyl after 1.4.1 with a bug fix
* Snapshoted 1.4.1 for the parrot release
What I will do:
No plan
EOR
Util Done: Minimal Perl 6 work only. No plan for Parrot work next week; $WORK-based tuit drought continues. 19:28
Will review my old tickets that have shown up on GitHub.
.end
19:28 atrodo joined
cotto hello 19:29
whiteknight hello
NotFound Hola 19:30
tadzik hello
alvis hello
dukeleto What I did:
* hacked on parrot-libgit2
* unpublished/alpha blog post labs.leto.net/2011/11/15/parrot-lib...corns.html
* got Parrot into Google Code-In
What I will do:
* attempt to get parrot paid for GSoC
* hack on GCI stuff
Blockers:
* ENOTIME
.EOR
Util Hello
cotto How's this week gone? 19:31
mls++ has a pull request open (last I checked) 19:32
looks like we should get to that soon. Conflicts seem to have crept in. 19:33
If the HLLs are happy, I'm happy. 19:34
alvis I have a question or two, if this is the place for it (or should I ask on #parrot)?
cotto alvis: this is the place. 19:35
before that, any volunteers to merge the branch?
alvis Ok, on the conversion of 'docs.parrot.org', is that just run it through html2pod and fixup the html links?
whiteknight cotto: I can help merge it 19:36
cotto whiteknight: great. Thank you.
whiteknight also, mls has another branch in the pipeline that I want to be aggressive with, refactoring subs and fixing closures (for Rakudo)
benabik I assume merge is post release?
whiteknight I don't think he's ready yet, but will be soon
cotto benabik: It'd be a bad idea to merge anything non-trivial this close to a release. 19:37
so yes, you're correct
whiteknight I will be cutting the release tonight, probably. I have a release_3_10 branch split out already. I think we can start breaking master if people want to
benabik That's what I thought, but wanted to make sure...
whiteknight if there are any fixes or docs/NEWS updates that need to be in the release, do them in the branch
I can cherry-pick too, if we get things in master between now and then that we want (which I doubt) 19:38
cotto git++
dukeleto howdy
alvis: what is your question? 19:40
alvis I guess my real question is, we want 'docs.parrot.org' to look and feel like the new wiki, correct?
dukeleto alvis: i think parrot.github.com would become the new docs.parrot.org
tadzik q1q
dukeleto alvis: and then we can make docs.parrot.org -> parrot.github.com
alvis: i would prefer to have the entire docs site in a github repo, so that we can push to it and update it 19:41
alvis: right now, to update docs.parrot.org, you need manually ssh into servers and type undocumented junk in
alvis Ahh, ok. I get what you want now.
dukeleto alvis: i would prefer that any parrot dev be able to commit to parrot.github.com.git and have the site be updated
cotto That would be helpful. 19:42
alvis dukeleto: Ok, sorry. I thought you wanted something different, but that's good too.
cotto & dukeleto: Ok, I (hopefully) got it now. I'll make a start in coupl'a days. 19:44
cotto alvis: thanks
alvis cotto: your welcome 19:45
cotto any other questions? 19:49
tadzik mine is more dukeleto-directed
dukeleto: what do potential mentors need to do/know in terms of the upcoming GCI?
whiteknight tadzik: Have energy. Eat a good breakfast, get a good night's sleep. Be prepared 19:50
when the program gets going, it goes
tadzik do I need to sign up or something?
whiteknight well, if we're good about keeping up with tasks
tadzik: I don't think you have to yet. We'll post an announcement when we know more 19:51
tadzik okay, thanks
NotFound And... let's be careful out there.
19:53 benabik_ joined
dukeleto is back. irc doesn't like me 19:57
tadzik: i will post something to parrot-dev
tadzik: good questions :) GCI starts in about a week
tadzik: and it looks like some of the same, extremely productive students from last year are back 19:58
tadzik oh, great
dukeleto tadzik: Yuki`N is interested in crypto stuff, and I have seen rfw lurking
tadzik: feel free to add the "gci" tag to github issues in the parrot org that would make good gci tasks 19:59
tadzik: i just added the gci tag to this: github.com/letolabs/parrot-libgit2/issues/9
tadzik: and anything parrot-related is fine to make into a GCI task 20:00
tadzik dukeleto: I'll look into it, thanks 20:01
whiteknight is the perl foundation in GCI too? 20:02
tadzik yes
whiteknight okay
dukeleto tadzik: good to know
alvis Do we still consider the "auto-generated HTML documentation" experimental? 20:06
cotto I didn't know it was experimental. We've been using it since forever.
alvis cotto: That's what it says in 'docs/gettingstarted.pod' 20:07
whiteknight our list of things that are "experimental" needs to be reviewed 20:08
alvis cotto: Ok, I'll remove that bit then, along the way.
cotto That line was added in 2005
probably safe to remove at this point
20:08 mikehh joined
cotto ;) 20:08
alvis cotto: :)
mikehh hi folkes, ain't been around for awhile, should be getting back into it in a week or so 20:10
dukeleto mikehh: howdy! 20:11
mikehh hi dukeleto
benabik dukeleto: Every time you say "howdy", I think of Toy Story: "Howdy, howdy, howdy!" 20:12
mikehh been totally involved in a project which I hope will finish soon, then I canget back into things here
it's been very lucrative, but no time for anything else 20:13
like I seriously need a break or something :-} 20:14
cotto Does anyone have any remaining unanswered questions? 20:16
whiteknight nope 20:18
cotto ok. Let's call it a wrap.
20:22 benabik left 20:23 atrodo left 20:58 whiteknight left 21:06 NotFound left 22:59 whiteknight joined