Our own standards -- discussions on call

[kaushalvivek]

• Verify Interface Compliance
• argument type -- pointers, unless we're concerned that there'll be modifications downstream
• slice as an argument (tricky, cc Anshal)
• channel size non-unit buffer
• error : document our own structure
• lifecycle management before container based deployment
• line-length: we need a cap on line size, check if this can be done through a linter
• plural package name -- do it when it makes sense, at max two words concatenated
• file-size: capped at 500/1000 lines
• separating services at proto level -- cc Anshal

[kaushalvivek]

• enum -- add context
• go enum -- prefix with type

[kaushalvivek]

We are okay with goDoc errors -- anything else should be resolved before merging with master.