Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Comments on A feature-request status page

Parent

A feature-request status page

+6
−0

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: example of what could be a feature-request list

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

3 comment threads

Potential problem with in page voting (2 comments)
GitHub issues (1 comment)
Related Features (2 comments)
Post
+0
−0

I've updated the feature-request tag description to incorporate the suggestions in this answer. Thanks for putting that together, ArtOfCode!

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

General comments (2 comments)
About username in Q&A body (1 comment)
General comments
zetyty‭ wrote over 1 year ago

Tanks for this update! I think this answer will be more used as an "text box" on top of the linked answer (as it is made for duplicates, "the blue rectangle" or like a quoted text). It would be like an announcement about the fact that the answer leads to a new "feature" (or an action) (but it is just my humble opinion to contribute to this wonderful project! ;).

Monica Cellio‭ wrote over 1 year ago

I added a status-completed tag to the question, but didn't want to bury what the change was in a revision comment, so I added this answer to explain. It can sit here at the bottom of the list; the answer with all the details is already voted up to the top.