-
Notifications
You must be signed in to change notification settings - Fork 37
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
November 2015 meeting #168
Comments
I updated @waldyrious's post above with all of the items that I found in the document linked to at the bottom and from the notes that I took during the meeting. I noticed that some of the points that we discussed during the meeting weren't added to the Google Doc, so please look this over, @waldyrious @galuszkak, in case I missed something. 😄 |
Can we move those to seperate tickets? I think having this so long open, doesn't help tracking what's in the "month meeting" issue :). |
Agreed, separate issues is the way to go. I'm afraid we might lose some info if we don't confirm whether the notes from the meeting were all added here, but if we block on that we might not move forward at all. (Confirming that all the items were added here shouldn't take too long, though.) |
I'm starting a new issue (branching off #167) to track the decisions of this month's meeting and what needs to be done (video recording / raw meeting notes). If we agree this is a good model, we can then have one such issue for each monthly meeting. Or perhaps a wiki page would work better so we can all edit in the same place.
Here are the main topics and decisions, mostly actionable items (unchecked items have open questions to resolve or actions to take):
The text was updated successfully, but these errors were encountered: