CCD and CCD reporting is not functional yet, so basically just removed it form the planned release (just committed this to rel-400 branch on sourceforge). Left the option there (but marked with disabled) to make it easy to add as a patch in the future if needed.
Feel free to put bugs here. Then can triage whether they need fixes now or should go into the tracker for future fixes.
The builds above are built daily at approximately 8:00 AM pacific standard time. Note there is a timestamp in the download section to see exactly what time/day it was built.
For anybody that has contributed code, fixed bugs, submitted bugs or just tested code, then please feel free to place yourself on the copyright (the more the better): http://www.openmedsoftware.org/wiki/OpenEMR_Copyright_Notice
(note this is not an ad compaign, follow current formatting)
(do not ask me to put you on it; you need to get wiki access and do it yourself; if you don’t quite get the formatting, don’t worry, just put yourself on it and we will sort it out later)
I propose we allow anybody whom has contributed any resources (ie. time to answer questions and provide support on the forums, board members, etc.) to be able to place their name/company contact info on the copyright.
I agree with Rod and aethelwulfe. “Copyright” has a specific legal meaning, which doesn’t cover “time to answer questions” or “board members”. A “Credits” / “Contributors” / “Recognition” / etc. section is a great idea, we should just avoid using a legally loaded term.
Hey, read the wiki page. Everybody is under the heading of “Developers and Contributors”. The lowest maintenance way to do this is to lump everybody together in alphabetical order. Unless somebody wants to be responsible for maintaining it. My goal was to give contributors credit (if they wish). I’m not gonna spend much more time on this item for the release, so options are:
1)Continue allowing non-code contributors on this page (note kilian was not a developer but is on there)
2)Only allow coders on there
3) Change the label(if want this provide specified label to put on login page)
4) Organize multiple labels/pages/categories/sections (if serious about this proposal then will assume you will maintain it)
-brady
It would be slander to list php noob idiots like me in the same list as the primary coders that have packed together what?…some significant fraction of the 40mb mass of the openemr download in pure code. That is a crapload of work. It has to be individually recognized. On the other hand, coders that build without users providing input tend to create apps that are unusable by “normals”. People that have been long recognized by by the primary developers as bug reporters and the like should also be accredited, and it’s the developers who ultimately know who those folks were. Anyone else, well, if they go into a credits list, it should be under the heading of “OpenEMR Community Members” or the like, and THAT listing can be the alphabetical list.
There is of course one more important segment. Brady, Rod, Tony….all you guys spend time monitoring these forums and handling your own client accounts. When someone pops up onto the boards, screaming that they can’t get something to work/install, it should not fall to you guys to help them out. For anyone that wants to get more involved, but has not been a major contributor in any way up to this point, you could have a list of folks and contact info for those who are willing to be “volunteer support”, listed along with date ranges and times that they agree to be available to support the “community” as it were. This list would not be under “credits” however. It would be an active page/link that provides updateable/reviewable resources for OpenEMR users. This might possibly even be of some help to those of you that are earning your living with this project right now. Catagories of help could be: Network/installation; ACL; EDI; Upgrades; you name it. I myself would gladly pop my name on such a list (especially to help out non-profits).
As far as someone maintaining a contributors list, you can count me in, provided it also entails some actual volunteer coordinator duties to keep me abreast of who/what should actually be on a list. I am currently a near full-time volunteer… but I am not actually permanently committed anywhere. I am free to do such a thing, I very much want to be part of this project, and I have been looking for a way in which to do such in this interm period of learning php.
Hi, authelwulffe,
lol, you’re killing my argument here (I didn’t think anybody would offer to do number 4 because of the work involved). I think the point I’m trying to make is that everybody in the community (developers, testers, free support on forums, grant writers, etc.) is integral and having a simple list to credit everybody is very easy to maintain. I’m currently the most prolific volunteer contributor and would have no problem with having you and all other contributors on the same list; I’m way more concerned with getting robust features, releases, documentation, and forum support. Would rather not spend resources keeping track of contributions etc… If you want a non-php project, we could definitely figure something out (wiki, ubuntu package, appliance, releases, demos, etc.). Just shoot me (and Tony) an email to figure something out.
thanks,
-brady
It would probably take a software patent attorney to figure this out.
Clearly, if you are contributing code, even if it is a single bug fix, then you fall into the category of software contributor and the copyright section would be appropriate. I don’t think simply volunteering time would be legally sufficient to included in copyright.
Certainly using the word “contributors” would be sufficient.
Board members are different. Legally it is the board of directors that will take the hit in any alleged copyright infringement action. So whether the board members have contributed code or not they would likely still be considered copyright holders it a legal action.
Obviously, board members who also contribute code would be listed in both sections.
If we are going to make the effort to make more than one list then perhaps there should be three:
Software contributors
Board members with dates of service
Contributors
The board member section is optional since board members are obviously contributing time and legally it won’t matter if they are listed as software contributors or not,
Board members are different. Legally it is the board of directors that will take the hit in any alleged copyright infringement action. So whether the board members have contributed code or not they would likely still be considered copyright holders it a legal action.
That’s not how copyright works. You become a copyright holder by producing a work covered under applicable copyright law. You become potentially liable for copyright infringement anytime you propagate a work where you are not the sole copyright holder. They are independent actions and status, although they are specified by a common body of law (in the U.S., at least). The board members should not be listed as a copyright holders unless they are copyright holders. Their potential liability is a separate issue.
I take it that Brady would just rather post an alpha list of anyone that wants to be on it and get it over with like yesterday.
Anyway, GNU public license, plagiarism, copyright and other terms are subject to the media type and socio-political geography. You are potentially liable anytime you BREATH. Anywho, “Contributors” are very much in the same position as folks who write submissions to an editorial. You can get sued by them for defamation, slander, or whatever when you use the material, but when they submitted the content, they gave it away as a whole and in detail. If they wish to mark a copyright and submit it for inclusion, they are STILL giving over rights/implied license to it, by virtue of a standing policy you hold all rights to the submission.
If you publish something yourself, or do not publish it at all, and someone else obtains it or utilizes it in a manner not compliant with the your license, they have committed copyright infringement, theft ,holding, or piracy depending on the jurisdiction. This also applies to recorded conversations etc… In any case, board members are not copyright holders by virtue of being on the board…not by any twist of logic. Unrelated subject. On the other hand, the Board members ARE responsible for following licensing restrictions of any redistributed material licensed by other entities.
