Regarding this:

GitHub issues & PRs will be transferred to the new repository.

I just want to make sure that the repository is moved, so that there's no need to actually transfer any constituent parts of it, it just gets a new name all in one "move" operation. All URLs keep working too, just with a redirect. The mentioned "Transferring a repository" describes such a "move" operation, so that's all good.

Bazel CI configurations will need to be updated to point to the new repository.

If done that way, maybe they will not even necessarily need to be updated, but of course it would be a good followup anyway.

@oprypin Yes, everything you described is exactly what will happen if we transfer the repo to bazel-contrib

I'm curious how this affects the sync to google3, per https://docs.google.com/spreadsheets/d/18oJBpAAc9hyT-3oJtque6bAxTKT4nsnryRtpccHXITw/edit?gid=186550915#gid=186550915 there's still a sync right?

That's a good question, @rickeylev @oprypin do we still plan to import rules_python after the move, it should still be possible because it's just like importing any other third party dependency.

However, should we at least set up some minimal integration tests to make sure the internal & external python rules don't diverge too far?

Hi. For the moment, I'd be more comfortable with discussing Google-internal matters on the same internal email thread.

@oprypin Makes sense

Today's SIG meeting: we reviewed the criteria from https://bazel-contrib.github.io/SIG-rules-authors/hosting-policy.html#adding-criteria and no concerns voiced, so it's approved!

@rickeylev ping me when you are ready for the transfer

@meteorcloudy Can we do the transfer Monday, Mar 17th? Any time is fine. (Or there abouts, doesn't have to be exactly that day).

No problem, will do.

I will start the transfer shortly.

This is done, testing on CI: https://buildkite.com/bazel/rules-python-python/builds/10618