-
Notifications
You must be signed in to change notification settings - Fork 152
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
An issue to collect open discussion items for unused CG meeting slots #1163
Comments
I don't have anything to add to the list, but big +1 from me for using meeting slots as bug triage and documentation improvement hackathons. |
Idea: The website currently has a git submodule for the design repo to pull in selected files. To simplify this and make it easier to work on the website, could we move the files it needs from the design repo into the website repo, and replace the design repo copies with links to the website? We could then eliminate the submodule. |
I think issue triage can be the default - a discussion on newly updated issues on common repositories (design, spec, meetings, etc) would be straight-forward and useful. Documentation is a good idea, but there needs to be a list of some sort to go through. |
One of the things that came up in discussion with @conrad-watt recently was to use some of the time for informational sessions, i.e. on understanding the formal spec, working with the interpreter, a walk through of writing spec tests etc. We could record these sessions and make them accessible for easier ramp up. We don't have too many slots in the near future, but we can schedule this for when we run into empty slots again. Please reach out if you'd be interested on presenting, or add yourself to the agenda. |
In the roadmapping session for last week's CG meeting, there was interest in using CG meeting slots that we cancel for open discussion. Given the size of the group, we should decide on what the best use of time is. @conrad-watt suggested we could have a curated list of discussion topics that we can work our way through. Opening this issue to see what folks would thing would be worthwhile to discuss. Other ideas that came up at the meeting:
The text was updated successfully, but these errors were encountered: