Feature Request: A Feature Request Table as a Forum Thread

[s3igell]

There are a number of Feature Requests posted to the Forum via various Threads.

 

Some are Clearly Delineated as Unique Threads with a Title that calls attention that it is a Feature Request, some threads don't have such a Title to call attention, while other Threads simply end up with a Feature Request embedded within it as a result of the conversation.

 

Some Feature Requests garner an immediate Response from Guylain, either accepting/acknowledging the Request or advising that it is Out-of-Scope or Unfeasible.  Other Requests gain a comment from Guylain that is Non-Committal.  And still others garner Responses advising that the Suggested Feature is Already Present within BYE/BYN.  And, some Feature Requests seem to get Repeat Requests - even if the previous iterations have already been Accepted or Denied.

 

To help Consolidate all this, and to Reduce the amount of Work and Attention given it on Guylain's part, I'd like to suggest the Publication of a Feature Requests List as a Forum Thread.  It could live as a Locked Sticky akin to the BackyardNikon v1 BETA Progress Grid, only placed in the Application Support / General Forum (or replicated to both the BYE and BYN Forums).  It would serve as a Starting Point for anyone wishing to suggest a Feature, and with a bit of Feedback from Guylain it could even be a "Rally Point" for Future Versions of BYE / BYN.  (Of course, any Features listed wouldn't be taken as Commitments - unless Guylain made any of them so...)

 

It would obviously take work on Guylain's part as the Owner/Moderator to make any Updates.  But I'd bet that a few Users might join with me to scour the existing Threads to compile the Original List - if Guylain doesn't already keep the bulk of one for his Private Dev/Support Purposes.  And I'd hope that if implemented, such a Table could reduce some of the repetitive Responses required - Positive or Negative - of Guylain as a condition of moderating User feedback. 

 

I'd envision the following Columns in such a Table:

1. Product (BYE / BYN / Both / BYRed)
2. Feature Request title (hyperlinked to a Description posted to the Thread)
3. Feature Request Thread (hyperlinked to the User Thread originating the Request)
4. Date (date of original post, or inclusion on the List, or Roll-out into Product, or Denial/Out-of-Scope determination)
5. Status (Listed / Considered / Agreed / Implemented / Rolled-Out / Denied / Out-of-Scope / Already Available)
6. Release Version (if Implemented / Rolled-Out)

[admin]

There are a number of Feature Requests posted to the Forum via various Threads.

 

Some are Clearly Delineated as Unique Threads with a Title that calls attention that it is a Feature Request, some threads don't have such a Title to call attention, while other Threads simply end up with a Feature Request embedded within it as a result of the conversation.

 

Some Feature Requests garner an immediate Response from Guylain, either accepting/acknowledging the Request or advising that it is Out-of-Scope or Unfeasible.  Other Requests gain a comment from Guylain that is Non-Committal.  And still others garner Responses advising that the Suggested Feature is Already Present within BYE/BYN.  And, some Feature Requests seem to get Repeat Requests - even if the previous iterations have already been Accepted or Denied.

 

To help Consolidate all this, and to Reduce the amount of Work and Attention given it on Guylain's part, I'd like to suggest the Publication of a Feature Requests List as a Forum Thread.  It could live as a Locked Sticky akin to the BackyardNikon v1 BETA Progress Grid, only placed in the Application Support / General Forum (or replicated to both the BYE and BYN Forums).  It would serve as a Starting Point for anyone wishing to suggest a Feature, and with a bit of Feedback from Guylain it could even be a "Rally Point" for Future Versions of BYE / BYN.  (Of course, any Features listed wouldn't be taken as Commitments - unless Guylain made any of them so...)

 

It would obviously take work on Guylain's part as the Owner/Moderator to make any Updates.  But I'd bet that a few Users might join with me to scour the existing Threads to compile the Original List - if Guylain doesn't already keep the bulk of one for his Private Dev/Support Purposes.  And I'd hope that if implemented, such a Table could reduce some of the repetitive Responses required - Positive or Negative - of Guylain as a condition of moderating User feedback. 

 

I'd envision the following Columns in such a Table:

1. Product (BYE / BYN / Both / BYRed)
2. Feature Request title (hyperlinked to a Description posted to the Thread)
3. Feature Request Thread (hyperlinked to the User Thread originating the Request)
4. Date (date of original post, or inclusion on the List, or Roll-out into Product, or Denial/Out-of-Scope determination)
5. Status (Listed / Considered / Agreed / Implemented / Rolled-Out / Denied / Out-of-Scope / Already Available)
6. Release Version (if Implemented / Rolled-Out)

 

That is a good idea.  Let touch base in a month or two once BYN 1.0 and BYE 3.1 are released.  I'm overwhelmed right now but when these 2 get released I'll be able to entertain something to support this, or something of that nature.

 

Regards,