Activity, over time
Daily GitHub activity and social mentions.
Mentions
Daily posts linking to this repository
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
No packages found.
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
Thanks for the announcement, great to see a first-party UI happening! I'm interested in contributing to Incus UI. For context, I maintain IXUI (xlmnxp/ixui), a community web UI for Incus, and I have a few ideas I'd still like to explore there. My one concern is that once an official UI ships, community projects become hard to discover, and users may never learn that alternatives exist. A suggestion: during incus admin init, when the user enables the HTTPS API, an optional step could ask which web UI to install, with a one-line description for each: - Incus UI (official, recommended) - IXUI (community) - Other community UIs - None The official UI would stay the default, so nothing changes for most users. Community projects would just get a visible, opt-in path. Since Incus can already serve a UI from a directory, this could be a fairly small change in packaging and init rather than in the core. Rough mockup:  Happy to help implement this if there's interest.