Skip to content
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

Time at TPAC? #369

Closed
LJWatson opened this issue Jun 13, 2017 · 4 comments
Closed

Time at TPAC? #369

LJWatson opened this issue Jun 13, 2017 · 4 comments

Comments

@LJWatson
Copy link

Would you like time at TPAC to update the WG on progress and/or bring issues up for discussion?

Please let me know by Friday 16th June. If yes, please also let me know how much time you think you'll need.

@domenic
Copy link
Member

domenic commented Jun 14, 2017

@tobie, @bzbarsky, any thoughts? It seems to me we're still working through a backlog of things from last TPAC; @tobie and I have been working through a pretty well-defined list of large/medium/small tasks. I'm not sure we'd need more dedicated time this year.

@tobie
Copy link
Collaborator

tobie commented Jun 14, 2017

Yeah, we still have a lot of material from last year's breakout session. I don't think doing one this year would be super useful.

I'm not sure whether I'll be at TPAC this year, but I'm happy to give the WG a quick update if I am. Unfortunately, I won't be able to confirm my presence for a while.

@bzbarsky
Copy link
Collaborator

I'm pretty sure I will not be able to make TPAC this year. I've also not been very actively involved in the editing activity, so don't know that I'd have much to contribute.

I agree we have enough work items that a breakout session is not likely to be useful, though if people have issues they should raise them. One issue I know is outstanding is Tab's concerns about typed arraylikes, though I'd hope we decide something there before TPAC.

@LJWatson
Copy link
Author

Thanks domenic, @tobie, and @bzbarsky. A quick update would be welcome if you're there @tobie, I'll throw 15 mins into the schedule as a placeholder for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants