DevChat 2.0 Action Items

[DanielWright]

As I mentioned at the very end of today's DevChat, I'm going to list out the take-aways from our discussion. What I'd love is for you fine folks to claim ownership of one of the items, and move it forward as best you can. In some cases, this will mean writing up some documentation, in others it will require some research.

When you have selected a topic, please:

• post a separate issue;
• assign the new issue the "DevChat 2.0" milestone;
• reference this GHI.

Topics include:

• documentation for reviewing code as a whole (@gen035 and ...?)
• documentation for nesting pull-requests (@simonwalsh)
• documentation for keeping PRs focussed and manageable
• researching CI options for code-style and linting (@cabouffard - could be great if we were 2)
• documenting CI integration for code-style and linting (@cabouffard - could be great if we were 2)
• proposing a Pester implementation
• investigating a GitHub integration for converting FIXME notes into issues/milestones
• investigating GitLab's code-review mode

Please feel free to leave a comments here if I've omitted something you thought was important from the chat, or if you'd like to propose another avenue to strengthening our implementation of code-reviews!

/cc @DynamoMTL/devchat

[simonwalsh]

Just a side but related note: I had started those 2 things last year if it can help anyone....

https://github.com/DynamoMTL/dynamo-central/wiki/Branch-Naming-Convention
https://github.com/DynamoMTL/dynamo-central/wiki/Issues-Structure-Convention

[DanielWright]

@cabouffard It's totally cool if you want to claim only the research side of the CI question and leave the documentation to someone else later on.

[thisiscab]

@DanielWright If feel like both are really binded together. One goes with the other.