-
Notifications
You must be signed in to change notification settings - Fork 158
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
Update CG-06-06.md #1285
Update CG-06-06.md #1285
Conversation
This works for me if we can make sure to allow sufficient time for discussion. Will the presentation fit in, say, 15min? |
If this proposed agenda item is intended to communicate Mozilla's perspective on stringref and a proposed alternative design, it doesn't seem ideal to prioritise an open-ended discussion on stringref over it. @eqrion please chime in regarding whether I've got the above correct - If I'm understanding the purpose of your presentation correctly, I'd prefer we prioritise this presentation in the next meeting and if necessary due to time constraints have a more full discussion of both presentations in the next again meeting (with brief recaps if needed) and/or on github. |
Yeah, I'm working on a concrete proposal for an alternative here. I should have something to post on the design repo next week which should give some time for it to be discussed before the meeting. I have a hard time estimating time, because questions during a presentation can significantly influence the time taken. A presentation without questions would probably be 25 minutes? I have a feeling there's enough discussion here to fill up the rest of the time then too. |
I may not be able to make the 6-20 meeting, so I'm hopeful that we can fit in both @eqrion's presentation and some discussion about the higher-level question of strings & Wasm. But I agree that given the work @eqrion's put into putting together this concrete proposal, it makes sense to include it as part of the context for that discussion. |
Given @eqrion's estimate above, I think we could shoot for the presentation to be timeboxed to 25 minutes, leaving 25 minutes for discussion. @eqrion this may involve making a few small cuts to your presentation in order to leave space for minor interruptions, but we can try to defer open-ended questions to the discussion period. If the above is acceptable, I'd suggest the following agenda items
It seems inevitable that we're going to end this meeting with a lot of discussion left to have. The timing is somewhat awkward, because if 06-20 doesn't work for follow-ups, the next CG meeting would be 07-04, which might well be cancelled due to the US holiday. In any case, we can work out how to handle follow-up discussions after the 06-06 meeting. |
That sounds good to me. I updated the commit. |
@ajklein Would you be okay if presented for the follow on discussion for strings? I have a concrete proposal for compile-time imports and a string builtin API which could make the discussion more productive.