Repository navigation
Apollo / Artemis Community Feature Request & Bounty RFC #1447
Replies: 4 comments 3 replies
|
This is really good. As much as I'm a fan of derflacco's Artemide client fork, it's super experimental for very specific SoCs and ends up muddying the conversation when converting gamers to see the light. "What's Artemis - what's Artemide - which one to download?" Don't get me wrong, Artemis/de shares a lot of users/testers but I agree that we need to have a stable mainline everyone can agree on and set seasonal standards the same way Jellyfin & SVT-AV1 teams keeps their developers aligned. I have notifications on for both forks and people are repeating the same requests every other day. Seasonal workflow should reduce this. Mainline should prioritize useful or introduce helpful experimental features - then repeat next season. |
|
I think this change is good; it really allows different patches to share features and functionalities. |
|
Title: Problem: Proposed behavior:
Affected area: Existing related work:
Technical notes:
The concept is sound and the results are real, but a proper implementation would need per-device capability detection, proper fallback chains, and extensive testing across GPU vendors. Why this matters: My results:
The approach is validated by VRidge shipping it commercially for VR streaming and Google building the same architecture into AndroidX for low-latency stylus input. It just hasn't been applied to game streaming clients yet. |
|
any news about this? |
Uh oh!
There was an error while loading. Please reload this page.
Apollo and Artemis now have multiple community forks with genuinely useful modifications. That is good for experimentation, but it also creates a real coordination problem: some features overlap, some conflict with each other, and long term this can fragment the community and make updates harder to maintain across the ecosystem.
To reduce that problem, I want to propose a more centralized process for feature planning and implementation: a shared feature request / voting / bounty thread.
The goal is not to stop people from experimenting or forking. The goal is to make it easier to coordinate work, reduce duplicate effort, avoid code conflicts, and keep the project maintainable.
Proposed structure
Each season, the thread will manage a limited pool of feature requests and improvement proposals.
This is meant to keep the process focused and avoid turning the thread into an unmanageable wishlist.
Why this is needed
Without coordination, several problems show up quickly:
A centralized request and claim process should make it easier to align on priorities and reduce unnecessary fragmentation.
Important limitations
This bounty system is currently RFC only. The details are open for discussion and can be improved.
Also, I need to be clear about the current constraints:
Votes help indicate demand. They do not override technical, maintenance, or project-direction concerns.
Submission rules for feature requests
To keep requests useful and actionable, each submission should follow these rules:
One request per post
Clear problem statement
Expected behavior
Scope and impact
Conflicts or overlaps
Technical constraints
No vague wishlist posts
No duplicate requests
Maintainability matters
Project direction matters
Submission template
Title:
Short name of the feature or improvement
Problem:
What problem does this solve?
Proposed behavior:
What should happen?
Affected area:
Apollo / Artemis / protocol / UI / installer / other
Existing related work:
Links to relevant forks, PRs, or prior discussions if any
Technical notes:
Known limitations, risks, compatibility concerns, or implementation notes
Why this matters:
Why should this be prioritized?
Rules for bounty claims
If you want to claim a bounty item for implementation:
Comment to claim it first
Provide an implementation plan
Coordination is required
One active claim per developer by default
Reasonable progress is required
Approval is not automatic
Implementation quality matters
Be prepared to revise
Abandoned claims may be reassigned
Claiming does not guarantee merge
Claim template
Bounty item:
Which feature you want to claim
Planned approach:
Short summary of how you intend to implement it
Affected components:
Apollo / Artemis / protocol / other
Potential conflicts:
Anything that may overlap with existing work
Estimated scope:
Small / medium / large
Status updates:
Developers with approved claims should post periodic updates so others know the slot is still active
Proposed seasonal workflow
Final note
This is an RFC. The system is not final, and suggestions for improving the rules, process, and structure are welcome.
The main purpose is simple: keep good ideas flowing without turning Apollo / Artemis development into a fragmented mess that becomes harder to maintain over time.
All reactions