Separate shims into a LensKit Addons repository
Open
Nobody has claimed this yet.
components
idea
- Dominant language
- Python
- Stars
- 314
- Forks
- 77
- Avg merge
- 4d 6m
- Merged PRs (30d)
- 10
Description
The time required to compile hpfrec, and sometimes implicit, slows down build cycles.
Separating these back out into a separate project repo would speed up CI runs and local dev setup. LensKit now maintains enough compatibility this is feasible.
Contributor guide
No contributing guide indexed for this repository
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 mapping where the hpfrec and implicit shims are defined and how the repository's build and CI setup compiles them. Done means the shims live in a separate LensKit Addons repository and the main project's CI and local setup no longer compile them as part of the normal build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100