hsbt_away changed the topic of #ruby-core to: check the latest release candidate for 1.9.1 release ftp.ruby-lang.org:/home/yugui/ruby-1.9.1-r26021+1.tar.bz2
nari has joined #ruby-core
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
charliesome has joined #ruby-core
tylersmith has joined #ruby-core
tylersmi_ has quit [Read error: Connection reset by peer]
tylersmith has quit [Remote host closed the connection]
r0bgleeson has quit [Ping timeout: 260 seconds]
<hsbt>
zzak: hi
<hsbt>
I started to prepare git-svn repository on my mac. I'll provide this repository via s3 to hone.
<hsbt>
I discussion this issue with shyouhei. Most fast solution is packaging to git-svn repository.
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<znz_jp>
biff: [ruby-changes:32052] hsbt:r44131 (trunk): * ext/racc/cparse/README: [DOC] Use upstream and github link instead of RAA. - http://mla.n-z.jp/?ruby-changes=32052
charliesome has joined #ruby-core
charliesome has quit [Client Quit]
charliesome has joined #ruby-core
<znz_jp>
biff: [ruby-changes:32053] hsbt:r44132 (trunk): * ext/tk/lib/tkextlib/SUPPORT_STATUS: [DOC] remove link of RAA. - http://mla.n-z.jp/?ruby-changes=32053
<znz_jp>
biff: [ruby-changes:32054] ko1:r44133 (trunk): * eval.c (rb_raise_jump): pop frame after setup exception. - http://mla.n-z.jp/?ruby-changes=32054
<_ko10>
do you plan to announce all meeting logs on ruby-lang.org?
<_ko10>
i don't against to announce important decision
<_ko10>
however, bug fixes or spec discussions are on ticket.
<_ko10>
i think it does not need to announce all of discussion
<_ko10>
such as > GC Merits and Documentation
<_ko10>
only wiki is enough.
marcandre has quit [Remote host closed the connection]
banister has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<zzak>
_ko10: hi
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<zzak>
_ko10: did you see the pull request?
<zzak>
i think its important to display transparency with our users about the discussions we have internally
<zzak>
so they can prepare before we write official announcements
<zzak>
i dont like using the wiki for such things
<zzak>
i want to move most documentation off the wiki
<nurse>
such internal documents are not for normal ruby users; it is not news
<zzak>
i disagree
<zzak>
users want to know when 1.9.3 is EOL, this gives them notice and shares our inside discussion
<zzak>
theres no difference between having it on ruby-lang.org or on some wiki page, both are open to anyone
<nurse>
EOL announcement must as the news; not a part of log
<zzak>
in the document, i mentioned that this what we discussed during the meeting, and link to tickets for further discussion and conclusion
<zzak>
"Below I have summarized the meetings for each day and organized them into agenda items. Each agenda item should have an associated ticket on our bug tracker that you can follow for more information. I will be updating these tickets with our conclusion shortly!"
<nurse>
if there's no difference, it is no need to move
<zzak>
please also see discussion on tickets, i plan to write official documentation on our decisions
<zzak>
the difference is clarity
tylersmith has joined #ruby-core
<zzak>
if we publish a summary to ruby-lang it can be easily maintained and translated via the www.ruby-lang.org translation teams
<nurse>
the point is why it is published as news
<nurse>
it is not a news for normal ruby users
<zzak>
because it was an important meeting to discuss the future of ruby? our users care about the future of their applications?
<nurse>
meeting is not important
<nurse>
If the conclusion is important, the conclusion should be published as the standalone article.
<nurse>
The title is not "meeting log", but for example "EOL plan of 1.9.3"
<zzak>
the conclusion will be published in official documentation
<nurse>
the anounce is not the summary of meeting, standalone announce document
tylersmith has quit [Ping timeout: 264 seconds]
<nurse>
In other words, news is news release, it is not a log.
<nurse>
News release has a single topic.
<nurse>
We concluded some topics in last meeting, we should write some news articles; not single meeting log
<nurse>
(for normal ruby users)
<nurse>
of course meeting log is good for ruby-itself-developers
<zzak>
my point is, in this case, we're relying on non-japanese speaking committers and invested users to rely on google translate to decide the fate of ruby
<nurse>
as far as it should be translated to English but what we did is save it is Japanese
<nurse>
(people can translate if someone has resource
<nurse>
oops, meeting in business
<zzak>
well if we write the log in english the first time, we have a team of translators on ruby-lang.org
<zzak>
we dont have a google docs team or redmine wiki team available to do that
<zzak>
i dont want to force you to use english for these logs, but if they are published on ruby-lang.org there are translators available there
<zzak>
if i could be at every meeting and lead the discussion in english with japanese translation support i would
<zzak>
i want us to be more open about when and why we make these decisions
charliesome has joined #ruby-core
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 250 seconds]
<hsbt>
zzak: Could you separate "1.9.3 EOL announce" from your pull request?
<zzak>
hsbt: any reason?
nokada_ has quit [Read error: Connection reset by peer]
<zzak>
i think we are discussing removing the log from ruby-lang.org
nokada has joined #ruby-core
<zzak>
what is the purpose of having a log that doesn't include valuable detail? i dont think it should be editted unless we have a good reason
nokada has quit [Read error: Connection reset by peer]
nokada has joined #ruby-core
nari has quit [Ping timeout: 245 seconds]
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 246 seconds]
nari has joined #ruby-core
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
charliesome has joined #ruby-core
<hsbt>
I can't merge your pull request. you need to applied ko1 and nurse's comments.
<hsbt>
I think better published only important things.
nokada has quit [Remote host closed the connection]
nokada has joined #ruby-core
nokada has quit [Remote host closed the connection]
judofyr has joined #ruby-core
tylersmith has joined #ruby-core
nokada has joined #ruby-core
tylersmith has quit [Ping timeout: 260 seconds]
banister has joined #ruby-core
banister has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
_whitelogger has joined #ruby-core
judofyr has quit [Remote host closed the connection]
tylersmith has joined #ruby-core
judofyr has joined #ruby-core
judofyr_ has joined #ruby-core
judofyr has quit [Read error: Connection reset by peer]
tylersmith has quit [Ping timeout: 246 seconds]
soba has quit [Ping timeout: 265 seconds]
judofyr_ is now known as judofyr
nagachika has joined #ruby-core
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 260 seconds]
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
r0bgleeson is now known as kingr0b
enebo has joined #ruby-core
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 260 seconds]
shinnya has joined #ruby-core
banister has joined #ruby-core
ZachBeta has joined #ruby-core
judofyr has quit [Remote host closed the connection]
tylersmith has joined #ruby-core
ZachBeta has quit [Quit: Computer has gone to sleep.]
tylersmith has quit [Ping timeout: 264 seconds]
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 246 seconds]
ZachBeta has joined #ruby-core
nagachika has quit [Remote host closed the connection]
tylersmith has joined #ruby-core
hone has joined #ruby-core
shinnya has quit [Ping timeout: 260 seconds]
shinnya has joined #ruby-core
tylersmith has quit [Remote host closed the connection]
ZachBeta has quit [Quit: Computer has gone to sleep.]
ZachBeta has joined #ruby-core
enebo has quit [Quit: enebo]
banister has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nari has quit [Ping timeout: 252 seconds]
ZachBeta has quit [Quit: Computer has gone to sleep.]
tylersmith has joined #ruby-core
marcandre has joined #ruby-core
tylersmith has quit [Ping timeout: 250 seconds]
tylersmith has joined #ruby-core
banister has joined #ruby-core
enebo has joined #ruby-core
eLobato has quit [Ping timeout: 259 seconds]
shinnya has quit [Ping timeout: 260 seconds]
kingr0b is now known as r0bgleeson
<zzak>
hsbt: agree! i'm actually going to publish a new document soon for MeetingGuidelines, similar to what we have for irc
<zzak>
this was my first developer meeting (not counting implementer meetings), so i'm still learning ;)
ZachBeta has joined #ruby-core
eLobato has joined #ruby-core
judofyr has joined #ruby-core
tylersmith has quit [Read error: Connection reset by peer]
tylersmi_ has joined #ruby-core
tylersmi_ has quit [Read error: Connection reset by peer]
judofyr has quit [Read error: Connection reset by peer]
<znz_jp>
biff: [ruby-changes:32061] marcandRe: r44140 (trunk): * array.c: More doc examples for Array#{map|collect}{!} using both forms - http://mla.n-z.jp/?ruby-changes=32061
judofyr has quit [Remote host closed the connection]
banister has quit [Ping timeout: 246 seconds]
tylersmi_ has joined #ruby-core
tylersmith has quit [Read error: Connection reset by peer]
judofyr has joined #ruby-core
Guest93703 has joined #ruby-core
tylersmi_ has quit [Ping timeout: 240 seconds]
ItSANgo has quit [Ping timeout: 246 seconds]
judofyr has quit [Remote host closed the connection]
ItSANgo_ has joined #ruby-core
charliesome has joined #ruby-core
tylersmith has joined #ruby-core
nokada has quit [Read error: Connection reset by peer]
nokada has joined #ruby-core
lopex has quit [Ping timeout: 260 seconds]
lopex has joined #ruby-core
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
tylersmi_ has joined #ruby-core
tylersmith has quit [Read error: Connection reset by peer]
ZachBeta has quit [Quit: Computer has gone to sleep.]
ZachBeta has joined #ruby-core
ZachBeta has quit [Client Quit]
tylersmi_ has quit [Ping timeout: 246 seconds]
tylersmith has joined #ruby-core
enebo has quit [Quit: enebo]
enebo has joined #ruby-core
enebo has quit [Client Quit]
charliesome has joined #ruby-core
soba has joined #ruby-core
soba has quit [Read error: Connection reset by peer]