Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
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:
Link to comment
Share on other sites
1 answer to this question
This topic is now archived and is closed to further replies.