Notes, idpy dev meeting, 23 January 2018
Scott, John, John, Ivan, Roland, Heather
1. flake8 and SOLID not mutually exclusive?
2. Any objections we should consider against PEP8/flake8?
PEP8 is a start, but need some higher level constraints on things like
Google’s style guide builds on top of PEP8.
Perhaps use both? Homework for people to study before TIIME - if you’re
not familiar with any of the above, please look them over and be
prepared to offer an opinion as to whether using PEP*+flake8 and the
Google coding guide should be adopted for idpy projects.
Do we want to rely on autogenerated documentation on the code? Any
guidance we want to apply? Roland is using Sphinx for some of his
projects. Add to discussion at TIIME
Incubator program - Ivan’s proposal vs following the model of one of the
Discuss at TIIME
* separate email
Google would like OIDF to host the libraries Roland is working on. Not
sure what that means with regards to using GitHub to maintain (since
OIDF doesn’t have a GitHub space). Roland would still like the python
libraries in idpy. Not sure what Google would think about that (though
they probably want everything in one space). What if they were offered a
spot on the idpy board? There are many dependencies between them, which
means hosting across different orgs would be unreasonably complicated.
Next meeting @ TIIME (Cancel next week’s call)