-
Notifications
You must be signed in to change notification settings - Fork 11
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
Build agenda for February Call #19
Comments
Furthermore, a) maybe it's time to incorporate the three outstanding pull requests into the master branch, so we can start working on that? b) @lazaral has been working on an example MPM dataset. He will soon make a pull request for this. Maybe interesting to have a look before we meet tomorrow. |
Like promised, I had a look at the old Google Doc |
Lastly, I would like to discuss again how to be a bit more pro-active in finishing this project into some kind of first version draft that people can actually use. I feel a very strong resistance within myself to "just incorporate some text" or change things, because I fell this should be a democratic exercise and maybe I'm not the ultimate expert. However, this also feels super-crippling and makes us slow down, also because we have no clear system of solving issues and pull requests. I would like to hear your feelings/thoughts about this. |
We are meeting tomorrow at Thursday 28 February at 6pm CET / 5pm GMT / 12noon EDT / 9am PST. Everyone's welcome!
What should we discuss tomorrow?
First thing that comes to mind is the new version of the spec. @agahkarakuzu, did you have time to e.g., the new metadata fields?
The text was updated successfully, but these errors were encountered: