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.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

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?**.~~
~~(Off-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](https://meta.codidact.com/comments/thread/7746#comment-20297)** it seems better to avoid voting on the status page in order to encourage user to see/participate to 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:~~
![example of what could be a feature-request list](https://meta.codidact.com/uploads/7uoo1419de6s72g54ny36yuz6up4)

# 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](https://meta.codidact.com/comments/thread/7746#comment-20297)** 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:
![example of what could be a feature-request list](https://meta.codidact.com/uploads/7uoo1419de6s72g54ny36yuz6up4)

feature-request discussion

Communities

Review Suggested Edit