Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
A feature-request status page
Motivation
I have the feeling (obviously biased ;) that some feature requests get forgotten over time. I absolutely do not claim that it is anyone's fault but that they naturally become less visible over time because they are less active (it's a guess).
Based on this assumption, the question is: how to improve/maintain the visibility of feature-request posts over time?
(Of course we can also consider that a non-active request means that nobody wants it... But is the feature-request enough visible to be active?)
Proposal
A "feature request status page" could be created on meta (maybe more like an article than a question: i.e. no possible answer) which list all feature-requests and give some info about them, for e.g.:
- Status: pending, implemented, implemented (partially), rejected.
- Vote counts (with the possibility of voting directly on this page EDIT after follow-up comment it seems better to avoid voting on the status page in order to encourage user to see/participate in the entire discussion before voting).
- Link to the "announcement post" if implemented or the GitHub issue if pending (if relevant).
Here an example of what could be a feature-request list:
Codidact is small, as is our team. Our development team is even smaller. That means that time, especially dev time, is a …
1y ago
I've updated the feature-request tag description to incorporate the suggestions in this answer. Thanks for putting that …
1y ago
EDIT after follow-up comments thread (where links for tags tab and status are given) and answer: The solution proposed h …
1y ago
3 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I've updated the feature-request tag description to incorporate the suggestions in this answer. Thanks for putting that together, ArtOfCode!
Codidact is small, as is our team. Our development team is even smaller. That means that time, especially dev time, is a very precious resource that we have little of. Something like this requires a fairly significant time investment both in development and in keeping up to date; I'm not convinced that it would be worth that investment at the moment.
Here's what we do have, some of which you may have missed, that might help you keep an eye on the status of various feature requests:
-
Filters. I've set up a custom filter for open feature-requests on my Meta home page so that I can see at a glance what's open. It looks like this:
-
Tags. As you might have gathered from that filter setup, we use status tags on Meta to indicate where things are holding. There are a fair few, but the major ones are status-completed (done), status-planned (we're planning to do this at some point), status-deferred (idea is doable but we don't have time/resources right now), and status-declined (won't or can't do this). You can browse these tags to get an idea of where things are.
-
GitHub. Any feature request that our team thinks we should do or are planning to do gets logged as an issue on our GitHub repository — this is what our devs look through for things needing to be done.
The final thing you might encounter from time to time is feature requests or bugs that we've completed or fixed, but aren't on the live site yet because they're waiting to be deployed when we next have time.
I hope that gives you a few tools to keep an eye — if you're looking for where a specific feature request is holding, feel free to ping one of the team in Discord, and if you have ideas for how we can improve these tools/processes we'd be happy to hear them.
2 comment threads
EDIT after follow-up comments thread (where links for tags tab and status are given) and answer: The solution proposed here already exists so it is irrelevant. The pro/cons part could still be used to compare the current solution and the solution with a "status page" (#1 in the table below)...
Simple solution partially fulfilling the objectives
Here a solution that would easily (from dev point of view) answer a large part of the specifications set in the current question:
- Create 3 new status tags: pending, implemented, rejected (maybe these tags should be usable only by staff)
- (colored tags could be interresting: orange: pending, green: implemented, red: rejected).
- Then the user can obtain the list of all feature-requests with the search bar and filtering by tag status, vote counts, date, etc. (which will look approximately the same as the "feature list" in the proposal in the current question).
Solution comparison
| # | Solution | Pro | Cons |
|---|---|---|---|
| 1 | "feature request status page" | Quick visibility of all feature requests and their current status | More dev work |
| Possible link to the "announcement post" if implemented | Accessibility: how to find this page? | ||
| Possible advanced filtering of the request list | |||
| 2 | Tags solution | Easier to implement | feature-request status less visible (users need to know the tricks to get status info) |
| Less concatenated view with less information related to feature-request specificities (because the method uses the search system common to all Q&A) | |||
| Less room for improvement later |
3 comment threads