[GitHub Request] Archive traffic-replayer and traffic-comparator

[msfroh]

What is the type of request?

Repository Management

Details of the request

Both the traffic-replayer and traffic-comparator repositories were added in 2023 as part of the original OpenSearch Migrations vision. Neither project really took off, though, leaving both repositories orphaned.

We have outstanding issues in both repositories asking for them to be archived, but think we will get more traction with a .github issue (since this is related to repository management).

• [PROPOSAL] Archive this repo traffic-replayer#12
• [GitHub Request] Archive this repo traffic-comparator#30

Additional information to support your request

This is part of a broader effort by @epugh to archive orphaned repositories that are probably not worth trying to revive.

I'd also like to use this issue as a starting point for the question of whether the Build TAG should vote on archiving repositories (the way that we vote on whether or not to create a repository). My opinion is that we should, but it's not a very strongly-held opinion.

@bugmakerrrrrr, @mishail, @anirudha, @getsaurabh02, @peterzhuamazon -- what do y'all think? Should we wield the power of both life and death over repositories?

When does this request need to be completed?

No rush

Notes

Track the progress of your request here: Engineering Effectiveness Board (view).
Member of @opensearch-project/admin will take a look at the request soon.
Thanks!

[peterzhuamazon]

Hi @msfroh ,

Maintainers have the call on whether to archive these repos.

Can maintainers of each repo (at least 1, need 2 if @msfroh is not a maintainer of these repos) confirm here to archive these repos?

• https://github.com/opensearch-project/traffic-replayer/blob/main/.github/CODEOWNERS
• https://github.com/opensearch-project/traffic-comparator/blob/main/.github/CODEOWNERS

Thanks.

[gregschohn]

The projects are doing well, but in a different repo. Instead of using separate repos, we maintain a mono-repo for all CDC and historical backfill tools for open search at https://github.com/opensearch-project/opensearch-migrations.

I'm fine archiving these since they'll only create confusion at this point. I'd like to see one more commit on the README to redirect users to https://github.com/opensearch-project/opensearch-migrations before we lock them up though.

[epugh]

Would it make sense in this specific case to just delete them?

[AndreKurait]

I agree with greg, if they live up forever then we should link to the opensearch-migrations repo. Deleting them could be helpful to reduce confusion particularly on https://github.com/opensearch-project/traffic-replayer since there isn't any code there

[epugh]

@peterzhuamazon I think you have your two +1's for this. Let's delete if we can, otherwise archive with pointers.

[peterzhuamazon]

Hi @epugh

1. We will never delete code repo, we will only archive.
2. @gregschohn is the maintainer of both, but @AndreKurait @epugh @msfroh are not I believe.

Can any of @chelma @kartg @lewijacn @mikaylathompson @okhasawn @sumobrian give a go as well?

Thanks.