-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next WG meeting - June 2017 #285
Comments
Here is the doodle: http://doodle.com/poll/g634n3b4vxpgitbmd8it3hv7 cc @nodejs/streams |
doodle doesn't work |
didn't mean to close |
new link, hope this works: https://doodle.com/poll/g634n3b4vxpgitbm |
I'm picking Wednesday 21st, June, at 17:00 CEST, 8:00 PDT. |
Ping! Hey folks, quiet remember of today's meeting! |
Both @lrlna and @yoshuawuyts cannot join the meeting. Will there be someone else? To watch: https://www.youtube.com/watch?v=903Gj69LOYU |
@mcollina I can join but mostly to watch! |
We are rescheduling because there not enough members. @lrlna @yoshuawuyts @mafintosh what days would you prefer? |
I can do tomorrow before 5pm CET and after 6pm CET, free the rest of the
week (:
…On Wed, Jun 21, 2017, 16:14 Matteo Collina ***@***.***> wrote:
We are rescheduling because there not enough members.
@lrlna <https://github.com/lrlna> @yoshuawuyts
<https://github.com/yoshuawuyts> @mafintosh <https://github.com/mafintosh>
what days would you prefer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#285 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWleoliRGZsuA1WytZbBQ-r76kdHkxUks5sGTNQgaJpZM4NgtrQ>
.
|
sorry about today! I can do tomorrow before 7 CET and anytime for the rest
of the week.
…On Wed, 21 Jun 2017 at 17:11 Yoshua Wuyts ***@***.***> wrote:
I can do tomorrow before 5pm CET and after 6pm CET, free the rest of the
week (:
On Wed, Jun 21, 2017, 16:14 Matteo Collina ***@***.***>
wrote:
> We are rescheduling because there not enough members.
>
> @lrlna <https://github.com/lrlna> @yoshuawuyts
> <https://github.com/yoshuawuyts> @mafintosh <
https://github.com/mafintosh>
> what days would you prefer?
>
> —
> You are receiving this because you were mentioned.
>
>
> Reply to this email directly, view it on GitHub
> <
#285 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ACWleoliRGZsuA1WytZbBQ-r76kdHkxUks5sGTNQgaJpZM4NgtrQ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#285 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHu3CJRxDfoP2Yycy2J5A3juPqeriFeAks5sGUCtgaJpZM4NgtrQ>
.
|
Hi Folks
Given our bimonthly meetings, it's time we start planning when we want to run the next streams-wg meeting :).
Agenda:
Status ofdestroy()
: stream: add destroy and _destroy methods. node#12925Status of_final()
: stream: add final method node#12828_readableState
and_writableState
in core [stream] Make _readableState and _writableState part of the public API node#7629.stream.end(chunk, enc, cb)
should always call the callback Writeable stream .end() has paradoxical logic node#5540I'll set up a doodle for the date
Invited @jessicaquynh - she wrote https://github.com/nodejs/nodejs.org/blob/f6bfed8438d8a88eb52ee0a623b56152cf8f95ae/locale/en/docs/guides/backpressuring-in-streams.md
The text was updated successfully, but these errors were encountered: