Goal: integrate `peprs` into PEPATAC and other packages
Open
Nobody has claimed this yet.
integration
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
It would be cool to show that we can effectively "replace" peppy in PEPATAC with peprs. That would be a good benchmark to hit I think to show feasibility and feature parity at least initially
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 examining how PEPATAC currently uses peppy and how peprs exposes equivalent functionality. Compare the required behavior and feature parity across PEPATAC and the other packages mentioned. Done means demonstrating a workable peprs-based replacement or documenting the remaining compatibility gaps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100