My question was more aimed at the fact that I know some people here have knowledge in the correct technical fields and could share it with the rest of us (like me) on the strictly-user side so we can evaluate whether or not we’re asking for something unreasonable before we add it to the list. I’m probably more techy than average, being an engineer who likes to mess around with 'nix systems, but I’m far from a professional in the infosys/database fields. The more I learn, the smarter I get about what to ask for and how to formulate the desired set of features to make it more practically implemented.
Of course, I recognize that the professionals from the BSA will ultimately be the ones making the call as to whether or not it gets implemented. It’s just not clear what pathway from this message board to the planned features list these types of requests take and how they are evaluated.
I see new feature requests the same way I suggest my scouts look at event planning. There’s no reason to automatically assume we can’t do a long trip to Hawaii from California, but the scouts planning such a trip need to contemplate costs, lead time, risks, etc at least somewhat before they bring the idea to the adults for any kind of review. Otherwise, it’s likely to get kicked back for additional planning. Similarly, there’s no reason, per se, not to request that file storage be added to the system for units to maintain unit-level documents. However, given an understanding of the costs to implement and maintain such a thing, more units may decide to pursue an alternate path and throw their weight behind advocating other tasks. At the same time, if it’s important enough to enough people, those people may start a funding campaign to help BSA pay for the added storage/overhead/etc associated with such a cloud system. If everything is viewed as the same level of cost (whether measured in programming hours, maintenance/overhead costs, server space, etc), then I think it’s hard for a lot of folks without the relevant technical background to understand why one request that doesn’t seem too difficult on its face could be a huge undertaking.
I understand the viewpoint that we just ask for features and assign a priority. I’m hoping to educate the user base a bit more as we go along so we all better understand what we’re asking about.