DEMO \| ORDER \| CUSTOMER CENTER \| CONTACT US

Resources For Contributors

Get Involved
This page is for users contributing to the OpenEngagement code base or to one or more of the Plone products which we develop and distribute.

There are many ways to get involved with the OpenEngagement community, including contributing to the OpenEngagement knowledge base, or providing documentation, testing or translation. For more information about getting involved other than at the source code level, please see our Get Involved page.

Code Organization
Our source code is available free for download. This includes the Zope and Plone platforms upon which OpenEngagement is built. Firms using either Hosted or Local solutions may download the code. We prefer to maintain all code changes in the form of Plone products, and so encourage contributors to either factor their changes into separate Plone products or to work on Plone products that we have already initiated (see below). In most cases, code submissions not in this form, but which are accepted, will be organized by OpenEngagement into Plone products.

Contributor Contact
To contact us about contributing to OpenEngagement's projects, please write to Brett Kennedy at: admin@openengagement.com.

Copyrights/Licensing
Similar to Plone, OpenEngagement's products are licensed under the open source license GPL (similar to Linux and many other successful open source software products).

This means that no one can prevent you from using the software now or in the future - see GNU General Public License for specific terms. Connectivity products (e.g. Go-Between) are available to integrate OpenEngagement with other packages. These may be developed and maintained by third parties, and will be licensed by those parties. The Working Papers-OpenEngagement Go-Between available on this site is licensed under similar terms as CaseWare Working Papers. Community supplied content will generally follow one of the licenses under the Creative Commons. Similar to GPL, this will mean that you will always be able to use the content that you and your community have created and collaborated on. It may be in the interest of the community that content is used from authors who do not follow one of the licenses under the Creative Commons. Where this occurs, it will be clearly laid out so that our community can fully understand the current and future limitations (if any) on using this content in their workplace.

See Licensing and Copyrights for more information.

Plone Products Released By OpenEngagement

These are products that are maintained by OpenEngagement, but which may be developed, tested and documented by the Plone and OpenEngagement Communities.

RoleMap
See the RoleMap page

Content History
See the Content History page

NoProblem
We have developed a product to: allow end users to submit problem reports in response to server exceptions (overrides error page) or at will; allow administrators to view the Zope event log through a Plone-friendly interface; and provide an API for plugging in "consistency checks" of the contents of the ZODB, keyed by class or interface. Presently problem reports are merely sent to a configurable email address. It would be nice to be able to support issue trackers, or to keep a database of problem reports on the server (though this would need to be augmented with other methods, for example if the problem is exhausted disk space).

NoProblem is included with OpenEngagement CMS 2.5. It will also be made available as a Plone product here soon.

Other Products

All functionality listed on the DMS Roadmap will be introduced in later releases of OpenEngagement. Members of the Plone and OpenEngagement community are encouraged to help collaborate on these. In particular interest to the general Plone community are:

Integration with Project Management Tools
Presently, we make much use of CMS work-flow. This tends to deal with questions regarding what needs to be done now. We would like to extend this into the past and future, to help set goals, analyse whether they are being met, help schedule complex, composite tasks, and make predictions about completion dates. This would either be a fully Plone-based solution, or integration with existing project management tools.

Find and Replace We understand that this is a desired but unimplemented core feature. We would like to implement it, and to first hear from prior attempts, expected gotchas, etc.

Support for Hand-held Devices
We also understand that there have been some attempts to make this a core feature. We think it would be very useful to our audience, and are interested in developing this feature. Any guidance and review of historic attempts would be very welcome.

Google Desktop Integration Sort of a free-association idea at this point, not well defined or researched. Both directions of integration could be useful; enter a query into Google Desktop and receive results from the portal, or enter queries into the portal and receive results from a pool of Google Desktop instances scattered around a network. We're interested in hearing about any work along these lines.

Document Signing The content in our application is typically edited outside of Plone through a check in/check out mechanism. Content review also generally occurs outside Plone's demesne. As an unfortunate consequence, there can be many copies and versions of a document in existence outside of the CMS. Furthermore, due to the nature of the documents, our typical user is very concerned with the possibility of documents being tampered with. To safeguard against accidental or intentional document corruption and confusion, we are considering a digital signature system. We are interested in discussing this with other developers who have similar problems, and working together for a solution.

OpenEngagement DMS: Manage all your documents. Cut costs. Increase efficiencies.

Prospective Customers	Current Customers	Contributors
Copyright © 2007™- CaseWare International Inc. - Privacy Policy