Synchronize ProWizard changes with upstream.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 392
- Forks
- 82
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
Since libxmp has made a large number of changes to fix crashes and other strange behavior, these fixes and their example files should be sent upstream to asle. I suspect some of libxmp's changes actually break things, so they will all need to be verified by him. This process will probably take a while.
Upstream ProWizard also has fixes that may or may not be present in libxmp.
I do not think refactoring libxmp's copy of ProWizard to match upstream is feasible right now, since it still uses e.g. a large number of globals that would absolutely ruin libxmp's ability to be thread-safe.
Task list pending.
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
The issue concerns libxmp's copy of ProWizard and its example files, but names no specific source files or tests. Start by inventorying the local ProWizard changes and comparing them with upstream; verify each change and check the corresponding examples with the upstream maintainer. Done means the differences are reviewed and a concrete synchronization plan is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100