darius
May 20, 2015, 7:11pm
1
My message quoted below was incorrectly parsed by the email processor. I had put three dashes on a line in my email to separate two thoughts, and the parser apparently interpreted this as the start of the forwarding/reply info.
Continuing the discussion from Non-free licensing in bundled modules :
Hi Burke,
Of course people implementing organizations should be able to sell OpenMRS, and they should have to deal with the licensing ramifications of this.
My point is that the #1 priority should be that anyone who downloads the OpenMRS-produced reference application can use it for free without having to do anything additional to use all bundled features. That means, for example, that we cannot include the SNOMED CT reference terminology, and would require people to install it themselves (and ensure they are in compliance with any related licensing).
I think that a “commercial or government” run health facility should be able to download the OpenMRS reference application and use it out of the box for free also. I.e. if you get the official distro from the OpenMRS website, it shouldn’t matter who you are, you should be able to use it for free. Hence the specific options I suggested.
michael
May 20, 2015, 7:18pm
2
Thanks for pointing this out.
The GitHub email reply parser library which is used by Discourse for email processing interprets dashes on a single line as the RFC 3676 standard start of a signature block:
A signature block (often abbreviated as signature, sig block, sig file, .sig, dot sig, siggy, or just sig) is a block of text automatically appended at the bottom of an email message, Usenet article, or forum post.
An email signature is a block of text appended to the end of an email message often containing the sender's name, address, phone number, disclaimer or other contact information.
"Traditional" internet cultural .sig practices assume the use of monospaced ASCII text because they pre-da...
So be careful out there with stray dashes!
michael
May 21, 2015, 12:48pm
3
