add engineering OKRs for 2019Q1 #109
Conversation
Signed-off-by: Santiago M. Mola <[email protected]>
README.md
Outdated
|
|
||
| ## Hiring | ||
|
|
||
| - Hiring: Test (1 Senior) [P0][ENG] |
There was a problem hiding this comment.
So far as OKR only for LA team. But we may still hire beyond these.
| ### Lookout Platform | ||
|
|
||
| - [ ] Collect GitHub reactions as feedback to comments [P1][APPS] | ||
| - [ ] Provide metrics on usage [P0][APPS] |
There was a problem hiding this comment.
may we have info about which kind of metrics are meant here?
There was a problem hiding this comment.
@smacker We need to meet together with @vmarkovtsev and @rporres to define this. We need to define how analyzers should expose custom metrics (e.g. such as metrics about models built by style-analyzer).
| ### Simplify usage | ||
|
|
||
| - [ ] Gitbase to expose only reachable objects [P0][DP] | ||
| - [ ] Provide installers [P2][APPS][PRODUCT] |
There was a problem hiding this comment.
installers of what? How is it different from engine that is an "installer" for most of src-d projects already?
There was a problem hiding this comment.
I had the same doubt. Needs clarification.
There was a problem hiding this comment.
Needs product discussion. This was initially meant to be apt-get and homebrew, but we still need to see if this would actually make things easier or not.
| @@ -2,19 +2,134 @@ | |||
|
|
|||
| ## Bring 'Code as Data' to market with enterprises | |||
|
|
|||
| ### Enable engine integration with 3rd parties | |||
|
|
|||
| - [ ] gitbase-spark-connector SQL 3rd party interop (Spark Thrift Server) [P0][DP] | |||
There was a problem hiding this comment.
Since the section is "Enable engine integration with 3rd parties", will this be expected to be available in engine?
There was a problem hiding this comment.
Not now or not yet. Probably in next quarter, but still requires product discussions.
| ### Get bblfsh ready for wide language support of our use cases | ||
|
|
||
| - [ ] Make UAST v2 the standard interface for Babelfish [P0][LA] | ||
| - [ ] Compact diffs of UAST trees [P1][LA] |
There was a problem hiding this comment.
One thing that isn't clear in this document are the dependencies between teams that arise from these objectives. (I'm adding this comment here because this one happens to affect LA, but there are others).
I suppose some of that dependency information will probably fall out of the product planning cycle, but could we have the OKR document include some record of "shared" OKRs? E.g., we could record multiple teams, and/or assign numbers and say "required for 1.2.1" or something?
Signed-off-by: Santiago M. Mola <[email protected]>
| ### Improve current lookout analyzers | ||
|
|
||
| - Style Analyzer in one more language (possibly Python) [P0][ML] | ||
| - Release Typo Analyzer [P0][ML] |
There was a problem hiding this comment.
- Style Analyzer improve the analysis quality [P1][ML]
|
|
||
| - [ ] Collect GitHub reactions as feedback to comments [P1][APPS] | ||
| - [ ] Provide metrics on usage [P0][APPS] | ||
| - [ ] Live Demo Repository with all available analyzers set-up [P1][APPS][INFRA] |
There was a problem hiding this comment.
- Define the analyzers configuration format in repositories [P1][?]
This is required to provide the rules blacklist feature in style-analyzer.
There was a problem hiding this comment.
material for the backlog at this point
Co-Authored-By: smola <[email protected]>
|
@smola do you think this should be merged at some point? |
Co-Authored-By: smola <[email protected]>
Co-Authored-By: smola <[email protected]>
No description provided.