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.

Post History

83%
+8 −0
Q&A A feature-request status page

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 ...

posted 1y ago by ArtOfCode‭  ·  edited 1y ago by tripleee‭

Answer
#2: Post edited by user avatar tripleee‭ · 2023-06-25T18:25:29Z (over 1 year ago)
Typo
  • 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:
  • ![Filter settings; set to include tags "feature-request", and exclude tags "status-completed, status-norepro, status-planned, status-bydesign, status-declined, status-deferred".](https://meta.codidact.com/uploads/pxdz1afyw01438xgmy8sdr6d0olr)
  • * **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 <a href="https://meta.codidact.com/categories/3/tags/377" class="badge is-tag is-red is-outlined">status-completed</a> (done), <a href="https://meta.codidact.com/categories/3/tags/941" class="badge is-tag is-red is-outlined">status-planned</a> (we're planning to do this at some point), <a href="https://meta.codidact.com/categories/3/tags/995" class="badge is-tag is-red is-outlined">status-deferred</a> (idea is doable but we don't have time/resources right now), and <a href="https://meta.codidact.com/categories/3/tags/2820" class="badge is-tag is-red is-outlined">status-declined</a> (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 things we should do or are planning to do gets logged as an [issue on our GitHub repository](https://github.com/codidact/qpixel/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) &mdash; 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 &mdash; 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.
  • 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:
  • ![Filter settings; set to include tags "feature-request", and exclude tags "status-completed, status-norepro, status-planned, status-bydesign, status-declined, status-deferred".](https://meta.codidact.com/uploads/pxdz1afyw01438xgmy8sdr6d0olr)
  • * **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 <a href="https://meta.codidact.com/categories/3/tags/377" class="badge is-tag is-red is-outlined">status-completed</a> (done), <a href="https://meta.codidact.com/categories/3/tags/941" class="badge is-tag is-red is-outlined">status-planned</a> (we're planning to do this at some point), <a href="https://meta.codidact.com/categories/3/tags/995" class="badge is-tag is-red is-outlined">status-deferred</a> (idea is doable but we don't have time/resources right now), and <a href="https://meta.codidact.com/categories/3/tags/2820" class="badge is-tag is-red is-outlined">status-declined</a> (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](https://github.com/codidact/qpixel/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) &mdash; 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 &mdash; 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.
#1: Initial revision by user avatar ArtOfCode‭ · 2023-06-24T13:43:40Z (over 1 year ago)
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:

   ![Filter settings; set to include tags "feature-request", and exclude tags "status-completed, status-norepro, status-planned, status-bydesign, status-declined, status-deferred".](https://meta.codidact.com/uploads/pxdz1afyw01438xgmy8sdr6d0olr)

 * **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 <a href="https://meta.codidact.com/categories/3/tags/377" class="badge is-tag is-red is-outlined">status-completed</a> (done), <a href="https://meta.codidact.com/categories/3/tags/941" class="badge is-tag is-red is-outlined">status-planned</a> (we're planning to do this at some point), <a href="https://meta.codidact.com/categories/3/tags/995" class="badge is-tag is-red is-outlined">status-deferred</a> (idea is doable but we don't have time/resources right now), and <a href="https://meta.codidact.com/categories/3/tags/2820" class="badge is-tag is-red is-outlined">status-declined</a> (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 things we should do or are planning to do gets logged as an [issue on our GitHub repository](https://github.com/codidact/qpixel/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) &mdash; 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 &mdash; 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.