OpenHPI currently has an old documentation directory, docs/hld in the
source tree. The documents there were written early in the OpenHPI
project history. IMO, some are still useful to new users, but many are
out of date.
There was a suggestion some years ago that these be moved to the OpenHPI
wiki, where there would be a better chance of having them be updated,
possibly even by end users who are the people that would naturally look
at them first. To date, this hasn't happened.
There is a second issue with the documents. They are licensed under a
different license than the rest of the project. The license is:
This material may be distributed only subject to the terms and
conditions set forth in the Open Publication License, v1.0 or
later (the latest version is currently available at
http://www.opencontent.org/openpub/). Distribution of
substantively modified version of this document is prohibited
without the explicit
permission of the copyright holder.
In this, the copyright holder would be the initial author of each
section of the document. I don't believe any of these authors are still
actively involved in the OpenHPI project.
My concern is that if the sections dealing with parts of OpenHPI that
have changed greatly were brought up to date, this might constitute a
"substantively modified version" and original author permission would
pose an undue burden on the change process.
Given where we are today, I am proposing that we remove docs/hld from
the next release of OpenHPI. These documents (in their older forms)
will continue to be available in past OpenHPI release tarballs, as well
as from the svn source history. Should someone have the time to start a
documentation portion of the OpenHPI wiki (http://openhpi.org), they can
draw from this material as a starting point.
Thoughts? Counter-proposals?
Bryan Sutula
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
