Talk:Heyu

Review Process

Coming from this thread let's talk here.

You (christian) have this:

User experience

• Tested with SME Server 7.3 and X10's CM11a - Works

at the bottom of the page. Is this based on your single experience or is that a reason for removing the needs review template? --Ente 17:03, 13 October 2008 (UTC)

It is based on my own set up, I usually add this section to have people indicate actual success data points. I did this in the Myth set up as well.

It does work fine and reliably. In general if I come across issues in future, I update the wiki.

I take your point about gcc, but it is also used in other How-to's such as "vmware". I'm open to suggestions on this front.

I would have thought that the "needs review" template would require someone to review the content for potential technical issues or bad practice; which is a good thing to do.

BTW, how do you automatically add the signature/date tage such as you did on your comment?

Regarding the signature: place four tildes behind your post, the two dashes are optional, or simply use the second button from the right above the text input area.

Regarding User experience: maybe write some more words about that in the article, that it's based on your tests, I guess it may be that with other hardware or software installed one could get problems.

Regarding gcc: Never read the whole vmware article ;) Maybe somepne with more experience or one of the developers could say something regarding the use of gcc in a how-to --Ente 17:32, 13 October 2008 (UTC)

Added a bit more in user experience including defining its purpose. The likelihood of conflict is low. heyu is mature and the only real area of interaction is usage of the serial port.

BTW, thank you for taking the time to review and comment! --Christian 17:53, 13 October 2008 (UTC)