Do we want a publicly editable wiki for centralized storage of all UAVCAN-related information excepting library documentation (because library docs are to be kept close to their sources)? There have been independent efforts such as creating a list of UAVCAN-enabled hardware or developing a new GUI tool (I’m not talking about Yukon here) which may remain undiscovered by most of the UAVCAN users because such information is spread out over a large variety of sources (such as this forum or GitHub repositories). With a wiki we could either fix that ourselves or at least provide users with a possibility of managing entries relevant to their activities themselves.
A downside of having a wiki is that it’s yet another source to maintain and keep up-to-date.
- Yes, we need a dedicated place for user-editable UAVCAN-related information
- No, we are unlikely to find sufficient resources for adequate content management
- No for other reasons (please describe)
(if we decided to go forward with the wiki, what wiki engine should we use? wiki.js comes to mind, anything else?)