search

Couchers-org / couchers

The next-generation couch surfing platform. Free forever. Community‑led. Non‑profit. Modern. Chuck us a star :)
https://couchers.org
MIT License
360 stars 76 forks source link

Feature: feature request board #4239

Open aapeliv opened 2 months ago

jesseallhands commented 2 months ago

I originally thought maybe we could use Canny.io for this, but it's pricy and I see that there is a free, open-source alternative here which looks exactly the same with a really nice, modern UI:

https://logchimp.codecarrot.net/ https://github.com/logchimp/logchimp

schradert commented 1 month ago

I'm a proponent of self-hosted FOSS for everything. LogChimp looks pretty good! Here are some others I found:

Fider [Demo] Astuto [Demo] Feedbase [Demo]

As much as it pains me to say, I suspect that we can get more out of GitHub Projects, Issues, and Discussions so that this repository can also adequately function as a public roadmap, support forum, and request manager, not just ticketing for internal project management. GitHub itself even has a roadmap and support forum/request tracker. I think it's worth trying to build this out together first before introducing yet another tool that won't integrate as well with our current workflows.

schradert commented 1 month ago

@aapeliv @jesseallhands @bakeiro what did we resolve today about an official feature request board? Although GitHub Discussions could work well for us internally by integrating with our current project tracking workflow, I recognize the friction in having people create GitHub accounts (a tool that is probably only familiar and intuitive to a developer), as well as the preference for a self-hosted service that integrates with couchers profiles and that many are already using.

We may ultimately accomplish our goal of soliciting community feedback on feature requests much quicker through the current forum, even if it lacks a primary voting mechanism. Self-hosting one of the alternatives above with couchers auth support could be a slightly better solution but it requires more initial effort from us and users. Therefore, I think I'm on board with a push to engage users through existing forum channels instead of an alternative service, as it may be easiest and most effective.

The "App Feedback" category appears to already function this way but without the expectation that our team is treating them as formal feature requests. I think we can just commit to engaging with these submissions from now on and announce to the community through standard channels that going forward we will be using that as intended and that engaging with submissions through comments and likes will tell us that the community values these features.

Is anybody seeing this differently than me? Do we prefer hosting another service that has the look and feel of a formal request tracker? Should we consider fully supporting couchers auth on whichever solution we implement?