search

operate-first / blueprint

This is the blueprint for the Operate First Initiative
GNU General Public License v3.0
16 stars 16 forks source link

Visibility on Collaboration #48

Closed anishasthana closed 2 years ago

anishasthana commented 3 years ago

Hi Folks,

Humair and I were talking earlier today about highlighting visibility into the collaboration we are having between the IDH, Operate First, and ODH teams. I think the engineers on the projects can generally agree that we have a good amount of shared development efforts and knowledge sharing but it is hard to quantifiably state that. Does anyone here have any ideas on improving visibility on this?

It'd be cool if there was some existing tool that lets you see interactions between organizations on Github, but a cursory google search didn't seem to surface anything.

cc @HumairAK @tumido @4n4nd @durandom @vpavlin @accorvin

HumairAK commented 3 years ago

I think for the most part, folks have been pretty good at linking to and fro from Operate-First repositories, so the information is certainly there and can/should be retrievable via github api for example. We would just need a way to aggregate/collect and present it in a fashion that is easier to consume.

accorvin commented 3 years ago

I think this is an important problem to solve, but also a challenging one and one that I don't have any great ideas for how to fix.

We could certainly write some scripts to measure contributions on pull requests and issues and that sort of thing, but... giphy

What would people thing of try to start some demo sessions where we show off to each other what we've been working on?

sesheta commented 3 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

sesheta commented 3 years ago

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 commented 2 years ago

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

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/blueprint/issues/48#issuecomment-991567197): >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](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.