Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Episode 10: four Personae to work on one app #11

Closed
goern opened this issue May 12, 2021 · 4 comments
Closed

Episode 10: four Personae to work on one app #11

goern opened this issue May 12, 2021 · 4 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@goern
Copy link
Member

goern commented May 12, 2021

Title
four Personae to work on one app

User Story
As a Data Scientist, I depend on work done by the Data Engineer, and I depend on work done by the MLDevOps Eng and I depend on work done by the AI DevSecOps Bots, so that I get my model into production

What are the Personae we talk about?
How do they interact with each other, what is their responsibility?
Can we describe interfaces between the three?

...

Teaser
In the next episode...

Release Date
Add target date for the release

Script URL:
Add link to the script to be reviewed

References
https://docs.google.com/document/d/1h3DRZvfaethUMls0svvovRvbRkO2QfoKtvh7ul1-81A/edit
https://docs.google.com/presentation/d/1XvdawGMIz68GXF7wKCBfIVZ2SBkdqy3bkIPNkkYIfMg/edit#slide=id.gdb4b126888_0_4

@goern goern changed the title three Personae to work on one app four Personae to work on one app May 20, 2021
@goern goern added this to Ideas in Espresso Series May 27, 2021
@goern goern moved this from Ideas to In progress in Espresso Series May 27, 2021
@goern goern changed the title four Personae to work on one app Episode 10: four Personae to work on one app May 27, 2021
@goern goern self-assigned this May 27, 2021
@sesheta
Copy link
Member

sesheta commented Oct 15, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 15, 2021
@sesheta
Copy link
Member

sesheta commented Nov 14, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 14, 2021
@sesheta
Copy link
Member

sesheta commented Dec 14, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Dec 14, 2021
Espresso Series automation moved this from In progress to Published Dec 14, 2021
@sesheta
Copy link
Member

sesheta commented Dec 14, 2021

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
No open projects
Espresso Series
  
Published
Development

No branches or pull requests

2 participants