Apollo / Artemis Community Feature Request & Bounty RFC #544
Pinned
ClassicOldSong
announced in
Announcements
Replies: 4 comments 1 reply
|
Cool! Hope u ll get rid of the stutters in the new version! Wanna donate u. |
0 replies
|
Is there any plans to port this to linux/steamdeck anytime soon? Is there some way I can help to make this happen? |
1 reply
|
Cool, I'm currently developing pen and touch-related features for several devices like the Wacom Movikpad and Samsung Galaxy Tablet, and I'll upload them for your review soon. |
0 replies
|
Great suggestion! I'm using a fork Artemide because I have (bad luck) Mediatek. My suggestions for Artemis:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For details, checkout ClassicOldSong/Apollo#1447
All reactions