Try renaming `shim/` to make it more clear that it's an internal/infra concept
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
As described in https://github.com/pytorch/executorch/pull/6860, the shim/ tree exists to make the buck2 build system work in both Meta internal and open-source repos. But no-one should really be looking at it most of the time, and it's more of a config thing than a part of the core tree.
We should see if we could rename it to something like .shim or build/buck2-shims. This would make it more clear that it's an internal config thing.
The main trick is that we need to coordinate this with the Meta-internal code mirroring config when we make the change.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading PR #6860 and inspecting the shim/ tree and the Meta-internal code mirroring configuration. Determine whether .shim or build/buck2-shims fits the repository structure; done means the rename is coordinated with mirroring and the Buck2 setup continues to work in both internal and open-source repositories.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100