OpenEMR is working on implementing a user registration process prior to downloading the software. We need your opinion on whether registration should be mandatory or optional. ANY THOUGHTS ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thinking on the fly:
There are other opensource projects that require users to register the software upon use not download.
During the setup process there could be a registration page that has to be filled out before the software completes installation.
The hole in the theory above is getting bogus information. Unless there was some key system in the software that would unlock it once a valid key was sent back from a key gen to their email address.
What's in it for them who register?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thinking on the fly:
There are other opensource projects that require users to register the
software upon use not download.
During the setup process there could be a registration page that has to be
filled out before the software completes installation.
The hole in the theory above is getting bogus information. Unless there
was some key system in the software that would unlock it once a valid key
was sent back from a key gen to their email address.
Will first clarify what is going on with OEMR and OpenEMR infrastructure to maintain transparency on this. OEMR currently has an AWS account where both the Registration Service is being served along with OpenEMR infrastructure items with plans to even migrate the OpenEMR website there (by combining things will make it less expensive since can share resources such as Load Balancers and database instances). The folks that have access to the aws account(and thus direct access to the database) are myself, Matthew, Scott, Robert, and Rod (note Rod is not an OEMR board member but has access since he is an OpenEMR administrator and this account serves both OEMR and OpenEMR services).
I think it will make sense to formalize some ground rules for what we can do with these email addresses at the next OEMR board meeting.
I propose that we should only be allowed to send the following categories of announcements to this email list:
1. New releases
2. New patches
3. Security issues
4. Donation requests
I also propose that we can only send the announcement out to the entire list (ie. can not go into the list and pick and choose).
And I also propose that this list is never to be used by vendors/companies/professionals to solicit services.
OpenEMR is working on implementing a user registration process prior to downloading the software. We need your opinion on whether registration should be mandatory or optional. ANY THOUGHTS ?
I'm pretty sure mandatory registration would violate the GPL.
Rod
http://www.sunsetsystems.com/
Can't make registration prior to download happen, it's not feasible given the nature of how we distribute the software.
If oemr's idea is to get as many people to download the openemr as possible - then having registration is a dumb idea.
If the oemr's idea is to get as many people to register as possible, then it's probably a dumb idea the optional registration
If the oemr wants to get a really focused list of people who are passionate about openemr - then registration is a really good idea.
Thinking on the fly:
There are other opensource projects that require users to register the software upon use not download.
During the setup process there could be a registration page that has to be filled out before the software completes installation.
The hole in the theory above is getting bogus information. Unless there was some key system in the software that would unlock it once a valid key was sent back from a key gen to their email address.
What's in it for them who register?
hi Sherwin, please see this:
https://sourceforge.net/p/openemr/discussion/oemr_501c3/thread/dda6e042/#085f
Matthew's on to something promising...
Sherwin, Very good question.
What is in it for them to register?
Regular update on patch releases and new functionality
Security / Vulnerability updates.
Healthcare news
BTW, we should not make the registration mandatory but should make it
optional....
On Mon, Sep 19, 2016 at 8:35 PM, Sherwin Gaddis juggernautsei@users.sf.net
wrote:
Now other question, will the certified contributors have access to the registerd users?
Hi Sherwin,
This is a good thing to bring up and discuss.
Will first clarify what is going on with OEMR and OpenEMR infrastructure to maintain transparency on this. OEMR currently has an AWS account where both the Registration Service is being served along with OpenEMR infrastructure items with plans to even migrate the OpenEMR website there (by combining things will make it less expensive since can share resources such as Load Balancers and database instances). The folks that have access to the aws account(and thus direct access to the database) are myself, Matthew, Scott, Robert, and Rod (note Rod is not an OEMR board member but has access since he is an OpenEMR administrator and this account serves both OEMR and OpenEMR services).
I think it will make sense to formalize some ground rules for what we can do with these email addresses at the next OEMR board meeting.
I propose that we should only be allowed to send the following categories of announcements to this email list:
1. New releases
2. New patches
3. Security issues
4. Donation requests
I also propose that we can only send the announcement out to the entire list (ie. can not go into the list and pick and choose).
And I also propose that this list is never to be used by vendors/companies/professionals to solicit services.
thoughts?
-brady
OEMR Organization
Is there a means of "Opting out of the registration"?
Hi,
Can opt out by clicking No Thanks(this is currently set as a permanent opt out and won't get asked again to register).
-brady
OEMR Organization