ForumVsWiki (2019-08-01 21:56:22)

This page brainstorms on compromises to keep efficiency as high as possible and satisfy communication-related bad habit (of a significant number of people) to dilute useful information (continuously, and indefinitely) and waste other's time by chronologically writing instead of thematically.

Forum can be appealing: one can ask something without even checking [help pages], without thinking about where the information belongs.


There is a forum site [here]


So - sigh - work must be done on the site (not just new firmware and HW features).

People who intend to spend some leasure time would use forums more often and those who want to contribute would use one of the first 2. Some would hang in forum from time 2 time and contribute to first 2.

The first 2 can be organized with some effort (but not without effort!), forum cannot be organized but information can be merged and pumped over to the organized site.

note: whatever method is used, CompenSation/Distribution credits must be based on achieved results not time spent.


Forum is basically a set of messages the same way as mailing list:

There are many gateways, eg. 'sourceforge forums' is a flexible implementation of forum and mailing list.

A product is much more than the hardware and software, customers have to get the right feeling about it, and the evidence suggests that people are not getting that feeling, the people that I have directed here take one look at the Wiki and never come back (and I am talking about technical people here).

With forum people spend much more time around vems (regardless of how same time could be spent more efficiently), and that makes a community. Contraselection is very common in our society: eg. we pay more for support to a software company that sells broken software than one that sells working software.


Solution - it doesn't sound hard to get the best of both worlds

I think that some tags in wiki like the "<code>" are desired and more urgent than the forums (for now we need people who tend to organize information the proper way, so they help build the manual; than anyone can come, many will realize sooner or later how to do things properly). These tags would hide (by default; configurable of course) development related info, or info relevant for v3.1 only.

The general way to implement this is:

It is self explanatory what the relevancy tag would do. (x could be used for board version, 31 means v3.1

Frank (and others) please elaborate on feasibility.


A lot of these stand alone systems can't lay a candle to Genboard and they are top dollar units with not even half the features at genboard. there should be one Genboard runing car in each state of the US and world for that matter. that 50 cars in the USA so one person in each state for someone to talk to about it and advertise the unit and help people that are trying to get started.


The wiki should be used to build pages like normal websites.


Search suggestion:

How about maybe using a Google search for the site instead of the builtin wiki

' Pet Peeve

Why do I have to remember the entire directory structure to link to a page. Wiki should be smart enough to know that GrmRacer is a WikiKeyWord and point to it not requiring a user to remember MembersPage/GrmRacer or MembersPage/GrmRacer/GrmCircuits this will make cross linking that much better and more useful.

MembersPage/... was a standard adopted at some point (we not start that way) to make member's pages not clutter SiteIndex. You are absolutely right: better ways are possible, and needed.


IRC - see ChatViaIrc page

FacebookBlocksContentAndUsersWithoutCauseOrExplanatation - The recipient should have control of what she sees... not a third party, definitely not Facebook - the nonsense times are back (people not always noticing, if the same that happened before happens again: if it is NOT black and white, it cannot be mass manipulation after all).