Duplicate requests: if several people request the same feature, the requests often get merged. Check whether your feature has already been suggested before posting.
0 likes 2mo
Meta · Feature requests · continued
Request: a per-category review queue posts 31–60
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Coming back to post #30, because the follow-up matters more than the original answer.
Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.
3 likes 2mo
l.vermeulen, post #28: Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up. Go to post
post #32 answers the question as asked. The question underneath it is different.
Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.
Tradeoffs: every feature has a cost in maintenance and complexity. Acknowledging tradeoffs shows you have thought through the implications.
1 like 1mo
l.vermeulen, post #28: Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up. Go to post
post #36 is right about the mechanism and I think understates the practical bit.
Deprecation requests: if you think a feature should be removed or changed, that is also a request. Explain why you think it would improve the site.
Worth separating two things that post #34 runs together.
Requests for platform and documentation features, with the reasoning that justifies them. If you think the site would be better with a feature, suggest it with enough detail that it is actionable.
31 likes 1mo
Picking up post #36: that is the part I would want checked first.
Use case: explain why you think the feature would help. "I would use this to..." makes the request concrete.
3 likes 1mo
Requests for platform and documentation features, with the reasoning that justifies them. If you think the site would be better with a feature, suggest it with enough detail that it is actionable.
10 likes 1mo
cannula_trace, post #10: post #9 answers the question as asked. The question underneath it is different. Tracking: staff will update the status of feature requests (under consideration, planned, implemented, declined). Checking back lets you know the fate of your suggestion. Go to post
Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
19 likes 1mo
Use case: explain why you think the feature would help. "I would use this to..." makes the request concrete.
0 likes 1mo
buffer_margin, post #15: post #14 answers the question as asked. The question underneath it is different. Duplicate requests: if several people request the same feature, the requests often get merged. Check whether your feature has already been suggested before posting. Go to post
Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.
Picking up post #43: that is the part I would want checked first.
Effort estimation: some features are trivial to implement; others are substantial work. Staff will estimate effort when assessing whether a feature is feasible.
27 likes 1mo
Tradeoffs: every feature has a cost in maintenance and complexity. Acknowledging tradeoffs shows you have thought through the implications.
2 likes 1mo
Tamburello, post #21: Use case: explain why you think the feature would help. "I would use this to..." makes the request concrete. Go to post
I read post #47 twice before replying, because I had assumed the opposite.
Tracking: staff will update the status of feature requests (under consideration, planned, implemented, declined). Checking back lets you know the fate of your suggestion.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
0 likes 1mo
On post #48 — agreed on the reasoning, with one qualification.
Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.
2 likes 1mo
t.varga, post #26: post #25 is right about the mechanism and I think understates the practical bit. Effort estimation: some features are trivial to implement; others are substantial work. Staff will estimate effort when assessing whether a feature is feasible. Go to post
Tracking: staff will update the status of feature requests (under consideration, planned, implemented, declined). Checking back lets you know the fate of your suggestion.
Requests for platform and documentation features, with the reasoning that justifies them. If you think the site would be better with a feature, suggest it with enough detail that it is actionable.
28 likes 1mo
Worth separating two things that post #52 runs together.
Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.
0 likes 1mo
s.salgado, post #47: Deprecation requests: if you think a feature should be removed or changed, that is also a request. Explain why you think it would improve the site. Go to post
Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.
post #58 answers the question as asked. The question underneath it is different.
Duplicate requests: if several people request the same feature, the requests often get merged. Check whether your feature has already been suggested before posting.
2 likes 1mo