If you have any suggestions for new categories, please share them in this topic. We want to avoid having too many categories as that makes it harder to know where to most things. But there are bound to be some focussed categories we should have.
How about an “installation issues” category?
I’m trying to install Node-Red on a VPS, not a Raspberry Pi, and have the same issue with CenotOS 7,Ubuntu 16.04, Debian 7 and Debian 8. Nodejs installs and tests just fine. Node-red aborts attempting the install in ALL of these distros with a bcrypt <2.0 wrap-around issue. I confess I’m a Windows geek but I really expected to find the issue addressed somewhere on this site. I see this issue mentioned - but not solved - online spanning a couple of years! Help.
Thanks for the suggestion for a category. If you are looking for help with that issue, please ask it in #general - this isn’t the category to get help on an issue.
I may have missed it, but is there a preferred category for submitting PR suggestions (for new enhancements or changes to core behavior)? I know I’ve used #general and #development in the past, but it might be nice to have contributed enhancements to the core/editor in their own channel…
How about Development: Hardware
@GChapo the Development top-level category is for the development work of the Node-RED project itself - not general development topics. And so far, we don’t have any hardware plans within the project
But that aside, what sorts of topics would you see living under a hardware category?
Perhaps Development is the incorrect topic area and Hardware needs to sit on its own or in another category. I was thinking of new hardware users had come across, single board computer developments, etc
As per my other thread, I’d suggest a “3rd Party Nodes” category
@rgerrans again, not trying to be difficult, I have to ask, what specifically do you see being discussed in that category. It may sound a silly question, but it’s potentially a very broad category that doesn’t really carve off traffic in a helpful way. Most flows use 3rd party nodes, so that would mean most questions end up in there.
I do think enabling tagging would help here - some 3rd party nodes get mentioned more than others - so being able to tag a topic with a given node module would help future users find related questions.
@knolleary Not being difficult at all, and missed the early related question so apologize for that.
I would anticipate it being around the functionality, bugs, and specific use cases for specific nodes. For example, a while back I was having issues with getting Big Timer to work on holidays. I wasn’t sure if that was an issue with how I was deploying it or if it was a bug in the node. So would have been a good place to post to figure it out. Ideally the node developers will be active here too and can monitor for discussions around their nodes. Agree that Tags are a very necessary part of making this category useful (though they help in other areas as well for cross tagging).
For an example check out how OpenHab organized a category for their add-on related discussions: https://community.openhab.org/c/add-ons
Let me know any other input I can help with on thinking this through.
Shouldn’t bugs in third party nodes be reported to the author of the node, in general via opening an issue on the nodes github page? It would surely be far less efficient if there is an expectation that all node authors keep up to date with the category here.
Agree. But my premise above was I wasn’t sure if it was a bug or my misapplication of the node.
Can I put in a suggestion for a category for new and updated node announcements.
In another forum, where I spent many years, we have a category “Coding Corner” that proved to be very successful and used a lot
Another category to consider could be “Node Support” with sub categories / folders for all nodes we have, to get a better structure and to make it easier to browse the board