[EPIC] As a service user, when I open a PR, I want to have an estimated timeline for its resolution:

Gkrumbach07 commented 2 years ago

Persona / User

Thoth Guidance Service user

User's Story

when I open a PR, I want to have an estimated timeline for its resolution

Reason

So that I can have a better understanding of when any related issues will be resolved
So that I can anticipate the amount of additional time and effort that will go in the PR and plan other tasks accordingly

Define Done

[ ] https://github.com/open-services-group/community/issues/173
[ ] https://github.com/open-services-group/community/issues/174
[ ] Update the tekton pipeline github bot to comment on the org/repo decided in criterion 1

chauhankaranraj commented 2 years ago

Hey @Gkrumbach07, @oindrillac and I were thinking of having these as the "define done" criteria, please let us know if you have any feedback!

Define Done

[ ] Figure out which repo/org we want to create this service for
[ ] Retrain models (re-engineering features if needed) on that repo/org
[ ] Update seldon inference service to use new model
[ ] Update the tekton pipeline github bot to comment on the org/repo decided in criterion 1

Gkrumbach07 commented 2 years ago

Looks good. We might want to talk with @KPostOffice to see if this could be a job for Kebechet or a separate bot. I am not familiar with the bot mentioned.

oindrillac commented 2 years ago

Thanks! Right now the PoC service was setup as a webhook by @harshad16 which will comment on PRs such as like this. @KPostOffice @harshad16 please feel free to advise on where this would fit best.

harshad16 commented 2 years ago

As this would provide a single service i.e time to merge for a PR. It was designed to be a single tekton pipeline that can be triggered via an event listener.

I would suggest, that if there is some more feature that is in the planning stage, then we can convert this into its own GitHub app. If we feel, we should plan for this, aicoe-ci is happy to accommodate this feature as its part till then.

This might not be a direct fit for kebechet in my opinion.

sesheta commented 2 years ago

@Gkrumbach07: The label(s) /label epic cannot be applied. These labels are supported: community/discussion, community/group-programming, community/maintenance, community/question, deployment_name/ocp4-stage, deployment_name/ocp4-test, deployment_name/moc-prod, hacktoberfest, hacktoberfest-accepted, kind/cleanup, kind/demo, kind/deprecation, kind/documentation, kind/question, sig/advisor, sig/build, sig/cyborgs, sig/devops, sig/documentation, sig/indicators, sig/investigator, sig/knowledge-graph, sig/slo, sig/solvers, thoth/group-programming, thoth/human-intervention-required, thoth/potential-observation, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, triage/accepted, triage/duplicate, triage/needs-information, triage/not-reproducible, triage/unresolved, lifecycle/submission-accepted, lifecycle/submission-rejected

In response to [this](https://github.com/open-services-group/community/issues/147#issuecomment-1117612103): >/label epic Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

sesheta commented 2 years ago

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

KPostOffice commented 2 years ago

/lifecycle active

Gkrumbach07 commented 2 years ago

Has been superseded by https://github.com/thoth-station/core/issues/425

/close

sesheta commented 2 years ago

@Gkrumbach07: Closing this issue.

In response to [this](https://github.com/open-services-group/community/issues/147#issuecomment-1270036915): >Has been superseded by https://github.com/thoth-station/core/issues/425 > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

open-services-group / community