Closed Bug 1485973 Opened 8 years ago Closed 6 years ago

Define a workflow for publishing and socializing experiment reports

Categories

(Data Science :: Documentation, task, P3)

Product:
Data Science
Component:
Documentation
Platform:
x86_64
Linux
Type:
task
Points:
3

Tracking

(Not tracked)

Status:
RESOLVED INACTIVE

People

(Reporter: harter, Assigned: ethompson)

References

Details

We cover the process for generating an experiment report in "Anatomy of an Experiment Report" [1]. That document hand-waves at the process of publishing and socializing a report. For example, after an analyst gets review via Github and publishes their report, how do they share the report? How do consumers give feedback? How do we ensure all of the necessary stakeholders have had a chance to review the report? [1] https://docs.google.com/document/d/1KSBgiKFRFqzcZWjRZt6faiRp4mR56jxaJtZwJRPa3Jk/edit#
Priority: -- → P2
I have a draft proposal here [0]. There's a bunch of comments there and I'll need to revise. It looks like we're going to require a bug be filed before publishing a report. The bug will then provide the ability to leave comments relating to an analysis. This may also augment review. [0] https://docs.google.com/document/d/1IEcYcQ4LCGHnUJ9oGYPPm6NATY1sts_ZnqgEHPDIpjw/edit#
Component: Documentation and Knowledge Repo (RTMO) → Documentation
Product: Data Platform and Tools → Data Science
Priority: P2 → P1
Status: NEW → ASSIGNED
Priority: P1 → P2
Priority: P2 → P3

taking this while doing ruthless bug triage ;)

Assignee: rharter → ethompson

Work for the DS team is now tracked in Jira. You can search with the Data Science Jira project for the corresponding ticket.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.