Repository Name Change: perfpod/memory-collector -> unvariance/collector

[yonch]

Repo Name Update

We are updating the name of this repository from perfpod/memory-collector to unvariance/collector. Unvariance better aligns with our mission of fighting performance variance in cloud environments.

The repository URL will change to https://github.com/unvariance/collector. While GitHub will automatically redirect web browsers from the old repository URL to the new location, contributors with existing local clones will need to update their git remote settings.

Required Actions for Contributors

If you cloned the repository directly (without forking), please update your git remote settings:

git remote set-url origin https://github.com/unvariance/collector.git
git remote -v  # Verify the change

If you forked the repository, no changes to your git settings are needed. Your fork's remote settings will continue to point to your fork, and GitHub will handle the redirect automatically when you interact with the upstream repository.

Where We're Announcing the Change

• README: We will update the README to reflect the new repository name and add a brief note about the change and redirect.
• Repo description: GitHub allows editing the repository description separately from the README. We'll update this to mention the name change.
• Pinned issue: This issue will be pinned to the repository for increased visibility of the update in the short-term.

Please bear with us as we update documentation and links to align with the new name. The project roadmap, contribution guidelines, and development process remain the same.

If you have any questions or concerns about this change, please comment below. Looking forward to continuing our work together in the unvariance/collector repository!

cc @tverghis @darshan-dedhia @cr-nimrodliberman @atimeofday

[yonch]

Just moved the repo.

Setting up AWS permissions for Github Actions with OIDC (which is the recommended way) requires the organization and repository name, so moving the repo before that setup work would help us not to redo the AWS setup later.

Let's keep the issue around for ~30 days, then remove it and the notice on the README.