Breaks/Splits update
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.9k
- Forks
- 323
- PR merge metrics
- No merged PRs in 30d
Description
Have you had any success with breaks or splits (or rather all the issues in https://github.com/smacke/ffsubsync/issues/10)?
Could you dedicate more time to this issue if I would sponsor you at the 100$ tier?
What kind of timeframe do you think it would take to solve this?
Thank you and sorry if this is worded in a rude way :)
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 reading the linked issue #10 and the discussion on breaks or splits; this issue does not identify files, tests, or an entry point. Before starting, clarify the expected behavior and scope, then define done as resolving the agreed breaks/splits cases in ffsubsync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100