Dear OpenClinica Community,
We are only hours away now from the general release of OpenClinica 3.0. There is a ton of excitement here at Akaza as we get ready to see many months of hard work come to fruition.
In advance of this milestone I’d like to describe a few changes we’re making to how OpenClinica is organized and how the name and logo can be used.
A brief background: As a founding member of the OpenClinica® open source community, I constantly strive to ensure that our technology has a reputation for meeting the highest standards of quality. The growth of OpenClinica® over the past few years is a testament to some success in that area. In my role as CEO at Akaza Research, a business that has invested millions of dollars into development of this open source technology, I recognize that the same reputation of quality is critical to our ongoing success. Part of how we maintain this reputation is to provide quality control over solutions that bear the OpenClinica® name. To enable this, Akaza Research owns the registered trademarks for OpenClinica® and Akaza and reserves the rights to their use.
With the release of 3.0, we are publishing a trademark policy on our website (also summarized below) that defines how the OpenClinica® and Akaza Research® trademarks may be used by members of the OpenClinica community. Our goal is to protect the quality of the OpenClinica® and Akaza brands without inhibiting the freedom that comes with the open source software model. These trademark terms complement the flexibility of open source licensing, by clarifying and creating confidence in the quality and reliability of solutions that bear the OpenClinica® name.
The most visible way the policy will be manifested is by separating the Community and Enterprise editions of the software. The default software download from OpenClinica.org is the Community Edition, pre-configured in a way that complies with the requirements of the trademark policy. The policy itself covers allowed uses of the trademarks for commercial and non-commercial purposes, both for modified (derivative) works and for unmodified versions of the software.
Akaza’s OpenClinica Enterprise customers and partners will be granted separate licenses that include additional permissions on how they may use the trademark in their marketing, operations, and services activities. Their installations will be distinguished as “OpenClinica Enterprise Edition” via the label in the footer of their OpenClinica pages.
I want to stress that 100% of the core OpenClinica source code remains free and under an open source software license. It is our promise that this will always be the case. Over time Akaza will offer additional proprietary services and technology offerings as part of the OpenClinica Enterprise Edition to complement this core, but it is our goal to ensure that the Community Edition always stands on its own as a fully-functioning, 100% open source EDC/CDMS platform.
I hope you share my view that this new policy will provide the clarity and confidence that allow OpenClinica to continue to thrive, without imposing undue restrictions on members of the community.
With that (too lengthy) introduction, here is a summary of the policy. Click here for the detailed, legal version:
|Category||Description||Terms and Conditions|
|OpenClinica Community Edition||You download and install the software on your own, and are not commercially supported by Akaza.||You may not use the OpenClinica brand for marketing or sales purposes, and must include the community edition disclaimer.|
|OpenClinica Enterprise Edition||You are an OpenClinica Enterprise System Level Support subscribers. Other Akaza customers/partners and OpenClinica code contributors may meet the requirements of this category. Contact sales for more detail.||Includes limited use of the OpenClinica brand for marketing and sales purposes, ongoing support, and display of “OpenClinica Enterprise Edition” in footer.|
|OpenClinica Community Edition – Derivative Work||You download and install the software on your own, make modifications to the code, and are not commercially supported by Akaza. You want to keep the OpenClinica name/logo in the modified version.||You may not use the OpenClinica brand for marketing or sales purposes, and must include the community edition disclaimer.. You must also clearly state the software has been modified and the modifications are not supported by Akaza.|
|Other Derivative Works||You choose to strip out the references to the OpenClinica and Akaza names and logos from your modified version of the software. The trademark policy does not apply.||The OpenClinica source code is licensed under the GNU Lesser General Public License (LGPL). You still must follow the terms of the LGPL, including copyright attribution and requirements for redistribution of source code. Of course, if you choose to follow this course, we hope you’ll also let us know about your software modifications and will contribute these back to the core repositories, both for the benefit of the community and to help ensuring future compatibility of your flavor of the software.|
If you are a community user of a prior version of OpenClinica and do not intend to upgrade to the latest release, please contact us if you have questions about how the new policy may affect you.
CEO, Akaza Research
Filed under: Uncategorized | Tagged: Akaza Research, Cal Collins, CDMS, clinical data management, clinical trials, community, EDC, electronic data capture, LGPL, open source, OpenClinica 3.0, oss, trademark | Leave a Comment »