-
Notifications
You must be signed in to change notification settings - Fork 228
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
Add discussion points to the agenda #45
Conversation
@@ -44,6 +44,8 @@ Mike Marcacci | Boltline | San Diego, CA | |||
1. Determine volunteers for note taking (5m) | |||
1. Discuss upcoming meeting schedule (5m) | |||
1. Present [graphql-import](https://github.com/graphcool/graphql-import) (5m) | |||
1. Discuss exposing schema metadata (30m) | |||
1. Discuss errors (30m) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this has been discussed previously, feel free to remove it if you feel like this won't add much to the conversation 👍
Thanks! |
@@ -44,6 +44,8 @@ Mike Marcacci | Boltline | San Diego, CA | |||
1. Determine volunteers for note taking (5m) | |||
1. Discuss upcoming meeting schedule (5m) | |||
1. Present [graphql-import](https://github.com/graphcool/graphql-import) (5m) | |||
1. Discuss exposing schema metadata (30m) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks a lot for adding this agenda topic, @xuorig! 👍 I was also thinking about adding it, should be an interesting discussion.
@xuorig It would be great to have a short description of both agenda items. I think it allows attendees to think about them beforehand so we will have a more productive discussion.
Do you mean something similar to graphql/graphql-spec#300 ? |
@IvanGoncharov sure, good idea. I can add a bit of context here: I'd like to be clear that I am adding these to the agenda to discuss potential solutions, not to propose one, so both links could be related. Issue #300 does talk a lot about the problem and is probably a good read before the work group meeting. Amongst other things, I'd like to discuss:
For the errors point, I'd like to discuss a few points:
(I can also talk about our specific use cases at the meeting.) |
Adding two discussion points to the agenda.
They're both quite large subjects so I put 30m but feel free to scale that down to leave room for other subjects if needed 🙏
cc @leebyron