<charliesome>
sora_h: thank you for parallel tests!!
<sora_h>
Note that I've graduated, so now I'm not a student :D
<bitsweat>
congratulations!
<sora_h>
charliesome: You're welcome :)
<sora_h>
bitsweat: Thanks!
carlosantonio has quit [Remote host closed the connection]
<znz_v>
biff: [ruby-changes:26952] charliesome:r39004 (trunk): * array.c (rb_ary_dup): make returned array the same class as the original - http://mla.n-z.jp/?ruby-changes=26952
<zzak>
charliesome: i think there are some recent minitest.. tests.. that use it
<zzak>
sora_h: congrats!
<charliesome>
zzak: did your talk go well?
<zzak>
charliesome: it was good, for my first talk i feel like it could have gone a lot worse and i was actually prepared
<charliesome>
the first time i ever spoke i was shitting myself
<charliesome>
so i think you did quite well
<zzak>
how many people were there?
<charliesome>
maybe 30~40 ish, not sure
<zzak>
yah we only had around 30
<charliesome>
ah yeah
<charliesome>
well received?
<zzak>
i think so, havent gotten any patches yet tho ;)
<zzak>
im more nervous for boston on the 12th, in front of a few hundred people and live streamed
<charliesome>
drink some courage before hand!
<zzak>
im afraid i will take too long, my first time i went on for almost an hour
<charliesome>
that's quite a long time for a talk
<zzak>
i did answer a few questions during the talk
<charliesome>
oh right
<zzak>
and a bunch after, so that might be why
<charliesome>
what you should do
<charliesome>
is organise a hack-night sort of thing afterwards
<charliesome>
get everyone hacking on docs
<zzak>
we are doing that in new haven, ct on the 7th
<zzak>
its a fairly easy transition to workshop from this talk
kosaki8 has joined #ruby-core
<zzak>
i might just turn it into one for bostonrb's project nights
<charliesome>
project nights sounds like a pretty interesting idea
<zzak>
it can be a rough 3~4 hour drive though
<charliesome>
at the melbourne ruby group, there's a couple of hours of talks, chat and pizza, then we head to the pub
<charliesome>
but i'd like to participate in a hack night
<zzak>
i liked project night
<zzak>
it's way more laid back
<zzak>
it would be nice if we could do a project night in town
<charliesome>
oh btw
<charliesome>
i wrote some documentation the other day
<charliesome>
which is what i was pinging you about
<charliesome>
i was actually pretty amazed that nothing was there before
<charliesome>
such a dangerous method
<zzak>
there is a section in the overview of Marshal on load
<zzak>
it might be good to add something there too
<zzak>
security notices really deserve to be top-level
<charliesome>
true
<zzak>
the same could be true for psych and json
<charliesome>
do you think move the notice to the overview, expand on it a bit, then replace the notice on load with a "please see the overview for security considerations" or something?
<zzak>
we could really use a doc/security file
<zzak>
yeh, in the method just say "this could be harmful, please see the overview" or something like that
<charliesome>
cool
<zzak>
like we have syntax guides, there should be a security guide
<charliesome>
definitely
<zzak>
i dont know the first thing tho
<charliesome>
i'll draft one up
<charliesome>
gonna go to bed soonish
<charliesome>
i'll fix up the marshal stuff then i'll take a first pass at a security doc tomorrow
<zzak>
that would be awesome!
<zzak>
thanks charlie
<charliesome>
if i can do my bit to help make ruby less of a laughing stock on the internet i sure will
<charliesome>
january was embarrassing as a rubyist
<zzak>
you are already helping a lot
<charliesome>
me and a coworker actually did a security related talk at the melbourne ruby group the other day