Replies: 2 comments 5 replies
-
|
Hi!
Yes, but it's also not a priority as of now. Design overhauls (theming, etc.) are done together in all Fossify apps to keep things consistent across the suite. Minor changes like icon updates are likely to get accepted.
In Fossify, there are strict rules, and nearly every change is tracked through issues because it helps with prioritization, future reference, and allows community feedback (if any). Rejecting PRs directly leads to more net work for everyone, as someone might spend a week working on something only to get it rejected. You will already find similar requests that aren't yet accepted here: https://github.com/FossifyOrg/Calendar/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen%20label%3A%22feature%20request%22 Contribution guidelines: https://github.com/FossifyOrg/General-Discussion#contributing-code But I am curious, what changes are you looking to implement? |
Beta Was this translation helpful? Give feedback.
-
|
As a user coming from the Google apps I can only also emphasize that design UI/UX is the biggest shortcoming in the Fossiy Apps. They are working great, but don't feel very polished. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
Coming from the Google Calendar app, I’ve been looking for a FOSS alternative. While I’ve found solid options in terms of functionality (like yours), I haven’t seen one that feels visually polished and pleasant to use.
Instead of forking and making changes privately, I’d like to contribute UI/UX improvements directly to this project. I realize this approach requires more collaboration and alignment, but I believe it will ultimately benefit both the community and long-term maintainability.
Before I get started, I’d like to ask:
Is there general interest in UI/UX contributions?
Would it be acceptable to submit PRs directly (with before/after screenshots and one PR per change) rather than opening an issue for each proposal first? This workflow would make things a lot easier for me, while still leaving room to discuss, improve, and either accept or discard each change.
Looking forward to hearing your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions