4 Commits

Author	SHA1	Message	Date
John Plaisted	fbb52304e8	doc(rfc): Add requirements / non requirements section to RFC. (#1818) ... This seems helpful to reviewers (and probably also the author). Motivation is too high level to be able to properly review a design. We need a clear set of requirements to review the design against.	2020-09-13 18:41:11 -07:00
Jyoti Wadhwani	91486a2ffd	feat(ML models): RFC for ML models (#1812) ... * Create RFC for ML Model * Add ml model graph file * add link to graph * Add high level design for ML model * ai->ml * Rename 000-ml_models.md to README.md * Add link to RFC PR * Update README.md * address some comments * Delete ml_model_graph.png * add ML Model graph * Address reviewer comments * Address more comments * Update README.md * Rename docs/rfc/active/000-ml_models/README.md to docs/rfc/active/1812-ml_models/README.md * Delete high_level_design.png * Delete ml_model_graph.png * Add files via upload Co-authored-by: Mars Lan <mars.th.lan@gmail.com>	2020-09-11 11:32:58 -07:00
Kerem Sahin	ce9dc9ce38	feat(dashboards): RFC for dashboards (#1778) ... * feature(dashboards): RFC for dashboards * Change directory structure * Create goals & non-goals sections * Removing alternatives section	2020-08-24 18:30:05 -07:00
John Plaisted	c5738d6403	Add documentation around the DataHub RFC process. (#1754) ... Other repos have similar RFC processes (though they seem to have a separate repo for their RFC docs). This provides a more structured way for contributors to make siginficant design contributions. https://github.com/linkedin/datahub/issues/1692	2020-07-28 16:43:40 -07:00