Linux port collaboration: phased re-land, attribution, and tester hardware
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 457
- Forks
- 58
- Avg merge
- 57m
- Merged PRs (30d)
- 114
Description
Context
@ForrestKnight, thank you for the six-phase work in ForrestKnight/videorc-linux. We are re-landing the Linux port phase by phase on current Videorc rather than merging the stale fork branches directly. L1 is now on main via #204, and the current phase contract is in docs/linux-port-plan.md.
Attribution and contribution contract
For every re-derived commit that materially uses the fork work, we propose preserving a Co-Authored-By trailer for you. Because Videorc is AGPL/open-core, we also need your DCO sign-off for contributed/re-landed work (Signed-off-by confirming you have the right to contribute it under the repository license). We can use an identity you confirm privately or your public GitHub noreply identity; no private address needs to be posted here.
Please confirm whether that attribution and DCO arrangement works for you.
Tester invitation
Would you also be willing to serve as the named Linux tester for L2 onward? The required box is real Ubuntu 24.04 x64 hardware with Wayland, PipeWire, a webcam, microphone, and /dev/dri access. CI or a VM can prove compile and AppImage packaging, but it cannot prove portal consent, camera/audio capture, VAAPI, lifecycle, or recording quality.
The next acceptance slices are:
- LGPL-only encoder path: VAAPI with OpenH264 fallback, never libx264.
- PipeWire microphone and sink-monitor desktop audio.
- V4L2 camera capture and mask parity.
- xdg-desktop-portal ScreenCast + PipeWire.
- CPU composition and JPEG preview.
- AppImage plus an isolated
linux-alphacandidate/pilot/public lane.
If you can test, please share only the non-sensitive capability summary (Ubuntu version, GPU vendor, Wayland session, webcam/mic availability). Device IDs, logs, recordings, and local paths stay private.
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 with docs/linux-port-plan.md and the L1 work merged via #204, then review the six acceptance slices and the referenced videorc-linux fork. Done means the attribution and DCO arrangement is confirmed and a named tester verifies the required Ubuntu 24.04 hardware capabilities for later Linux phases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust, ubuntu
- Domain
- audio-video-rtc, build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100