diff --git a/docs/COPYING b/docs/COPYING index d24b584..e4e998e 100644 --- a/docs/COPYING +++ b/docs/COPYING @@ -1,192 +1,193 @@ -KnowledgeTree Public License - -The KnowledgeTree Public License ("KPL") consists of the Mozilla Public License Version 1.1, modified to be specific to KnowledgeTree, with the Additional Terms in Exhibit B. The original Mozilla Public License 1.1 can be found at: http://www.mozilla.org/MPL/MPL-1.1.html - -Changelog: - - * KnowledgeTree Public License 1.1.1 - o Modified to reflect www.knowledgetree.com - o Modified to reflect new branding - -KNOWLEDGETREE PUBLIC LICENSE -Version 1.1.1 - -1. Definitions. - -1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code available to a third party. - -1.1. ''Contributor'' means each entity that creates or contributes to the creation of Modifications. - -1.2. ''Contributor Version'' means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. - -1.3. ''Covered Code'' means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. - -1.4. ''Electronic Distribution Mechanism'' means a mechanism generally accepted in the software development community for the electronic transfer of data. - -1.5. ''Executable'' means Covered Code in any form other than Source Code. - -1.6. ''Initial Developer'' means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. - -1.7. ''Larger Work'' means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. - -1.8. ''License'' means this document. - -1.8.1. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein. - -1.9. ''Modifications'' means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: - -A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. - -B. Any new file that contains any part of the Original Code or previous Modifications. - -1.10. ''Original Code'' means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. - -1.10.1. "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. - -1.11. ''Source Code'' means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. - -1.12. "You'' (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You'' includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control'' means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity. - -2. Source Code License. - -2.1. The Initial Developer Grant. -The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: - -(a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and - -(b) under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof). - -(c) the licenses granted in this Section 2.1(a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License. - -(d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices. - -2.2. Contributor Grant. -Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license - - -(a) under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and - -(b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination). - -(c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first makes Commercial Use of the Covered Code. - -(d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor. - - -3. Distribution Obligations. - -3.1. Application of License. -The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. - -3.2. Availability of Source Code. -Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. - -3.3. Description of Modifications. -You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. - -3.4. Intellectual Property Matters - -(a) Third Party Claims. -If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL'' which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained. - -(b) Contributor APIs. -If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the LEGAL file. - -(c) Representations. - -Contributor represents that, except as disclosed pursuant to Section 3.4(a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License. - - -3.5. Required Notices. -You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. - -3.6. Distribution of Executable Versions. -You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. - -3.7. Larger Works. -You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. - -4. Inability to Comply Due to Statute or Regulation. - -If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. - -5. Application of this License. - -This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code. - -6. Versions of the License. - -6.1. New Versions. -The Jam Warehouse Software (Pty) Ltd may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. - -6.2. Effect of New Versions. -Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by The Jam Warehouse Software (Pty) Ltd, trading as KnowledgeTree. No one other than The Jam Warehouse Software (Pty) Ltd has the right to modify the terms applicable to Covered Code created under this License. - -6.3. Derivative Works. -If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases ''KnowledgeTree'', ''KPL'' or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the KnowledgeTree Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) - -7. DISCLAIMER OF WARRANTY. - -COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. - -8. TERMINATION. - -8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. - -8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that: - -(a) such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above. - -(b) any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant. - -8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license. - -8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination. - -9. LIMITATION OF LIABILITY. - -UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. - -10. U.S. GOVERNMENT END USERS. - -The Covered Code is a ''commercial item,'' as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of ''commercial computer software'' and ''commercial computer software documentation,'' as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. - -11. MISCELLANEOUS. - -This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. - -12. RESPONSIBILITY FOR CLAIMS. - -As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability. - -13. MULTIPLE-LICENSED CODE. - -Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the SPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A. -KnowledgeTree Public License 1.1 - Exhibit A - -The contents of this file are subject to the KnowledgeTree Public License Version 1.1 -("License"); You may not use this file except in compliance with the -License. You may obtain a copy of the License at http://www.ktdms.com/KPL -Software distributed under the License is distributed on an "AS IS" basis, -WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for -the specific language governing rights and limitations under the License. - -The Original Code is: KnowledgeTree Open Source - -The Initial Developer of the Original Code is The Jam Warehouse Software (Pty) Ltd, trading as KnowledgeTree. -Portions created by The Jam Warehouse Software (Pty) Ltd are Copyright (C) 2006 The Jam Warehouse Software (Pty) Ltd; -All Rights Reserved. -Contributor(s): ______________________________________. - -[NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.] -KnowledgeTree Public License 1.1.1 - Exihibit B - -Additional Terms applicable to the KnowledgeTree Public License. - -I. Effect. -These additional terms described in this KnowledgeTree Public License - Additional Terms shall apply to the Covered Code under this License. - -II. KnowledgeTree and logo. -This License does not grant any rights to use the trademarks "KnowledgeTree" and the "KnowledgeTree" logos even if such marks are included in the Original Code or Modifications. - -However, in addition to the other notice obligations, all copies of the Covered Code in Executable and Source Code form distributed must, as a form of attribution of the original author, include on each user interface screen (i) the "KnowledgeTree Document Management Made Simple" logo and (ii) the copyright notice in the same form as the latest version of the Covered Code distributed by The Jam Warehouse Software (Pty) Ltd. at the time of distribution of such copy. In addition, the "KnowledgeTree Document Management Made Simple" logo must be visible to all users and be located at the top right-hand corner of each user interface screen, other than the user log-in page, on which it must be located at the top-center of the user log-in form. Notwithstanding the above, the dimensions of the "KnowledgeTree Document Management Made Simple" logo must be at least 200 x 40 pixels. When users click on the "KnowledgeTree Document Management Made Simple" logo it must direct them back to http://www.knowledgetree.com. In addition, the copyright notice must remain visible to all users at all times at the bottom of the user interface screen. When users click on the copyright notice, it must direct them back to http://www.knowledgetree.com +KNOWLEDGETREE PUBLIC LICENSE +Version 1.1.2 + +1. Definitions. + +1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code available to a third party. + +1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications. + +1.2. "Contributor Version" means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. + +1.3. "Covered Code" means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. + +1.4. "Electronic Distribution Mechanism" means a mechanism generally accepted in the software development community for the electronic transfer of data. + +1.5. "Executable" means Covered Code in any form other than Source Code. + +1.6. "Initial Developer" means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. + +1.7. "Larger Work" means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. + +1.8. "License" means this document. + +1.8.1. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein. + +1.9. "Modifications" means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: + +A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. + +B. Any new file that contains any part of the Original Code or previous Modifications. + +1.10. "Original Code" means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. + +1.10.1. "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. + +1.11. "Source Code" means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. + +1.12. "You" (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity. + +2. Source Code License. + +2.1. The Initial Developer Grant. +The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: + +(a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and + +(b) under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof). + +(c) the licenses granted in this Section 2.1(a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License. + +(d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices. + +2.2. Contributor Grant. +Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license + + +(a) under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and + +(b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination). + +(c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first makes Commercial Use of the Covered Code. + +(d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor. + + +3. Distribution Obligations. + +3.1. Application of License. +The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. + +3.2. Availability of Source Code. +Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. + +3.3. Description of Modifications. +You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. + +3.4. Intellectual Property Matters + +(a) Third Party Claims. +If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained. + +(b) Contributor APIs. +If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the LEGAL file. + +(c) Representations. + +Contributor represents that, except as disclosed pursuant to Section 3.4(a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License. + + +3.5. Required Notices. +You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. + +3.6. Distribution of Executable Versions. +You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. + +3.7. Larger Works. +You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. + +If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. + +5. Application of this License. + +This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code. + +6. Versions of the License. + +6.1. New Versions. +The Jam Warehouse Software (Pty) Ltd may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. + +6.2. Effect of New Versions. +Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by The Jam Warehouse Software (Pty) Ltd, trading as KnowledgeTree. No one other than The Jam Warehouse Software (Pty) Ltd has the right to modify the terms applicable to Covered Code created under this License. + +6.3. Derivative Works. +If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "KnowledgeTree", "KPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the KnowledgeTree Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) + +7. DISCLAIMER OF WARRANTY. + +COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. + +8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. + +8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that: + +(a) such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above. + +(b) any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant. + +8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license. + +8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination. + +9. LIMITATION OF LIABILITY. + +UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. + +10. U.S. GOVERNMENT END USERS. + +The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. + +11. MISCELLANEOUS. + +This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. + +12. RESPONSIBILITY FOR CLAIMS. + +As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability. + +13. MULTIPLE-LICENSED CODE. + +Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the SPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A. +KnowledgeTree Public License 1.1.2 - Exhibit A + +The contents of this file are subject to the KnowledgeTree Public +License Version 1.1.2 ("License"); You may not use this file except in +compliance with the License. You may obtain a copy of the License at +http://www.knowledgetree.com/KPL + +Software distributed under the License is distributed on an "AS IS" +basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. +See the License for the specific language governing rights and +limitations under the License. + +All copies of the Covered Code must include on each user interface screen: + (i) the "Powered by KnowledgeTree" logo and + (ii) the KnowledgeTree copyright notice +in the same form as they appear in the distribution. See the License for +requirements. + +The Original Code is: KnowledgeTree Open Source + +The Initial Developer of the Original Code is The Jam Warehouse Software +(Pty) Ltd, trading as KnowledgeTree. +Portions created by The Jam Warehouse Software (Pty) Ltd are Copyright +(C) 2007 The Jam Warehouse Software (Pty) Ltd; +All Rights Reserved. +Contributor( s): ______________________________________ + +[NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.] +KnowledgeTree Public License 1.1.2 - Exihibit B + +Additional Terms applicable to the KnowledgeTree Public License. + +I. Effect. +These additional terms described in this KnowledgeTree Public License - Additional Terms shall apply to the Covered Code under this License. + +II. KnowledgeTree and logo. +This License does not grant any rights to use the trademarks "KnowledgeTree" and the "KnowledgeTree" logos even if such marks are included in the Original Code or Modifications. + +However, in addition to the other notice obligations, all copies of the Covered Code in Executable and Source Code form distributed must, as a form of attribution of the original author, include on each user interface screen (i) the "KnowledgeTree Document Management Made Simple" logo and (ii) the copyright notice in the same form as the latest version of the Covered Code distributed by The Jam Warehouse Software (Pty) Ltd. at the time of distribution of such copy. In addition, the "KnowledgeTree Document Management Made Simple" logo must be visible to all users and be located at the top right-hand corner of each user interface screen, other than the user log-in page, on which it must be located at the top-center of the user log-in form. Notwithstanding the above, the dimensions of the "KnowledgeTree Document Management Made Simple" logo must be at least 200 x 40 pixels. When users click on the "KnowledgeTree Document Management Made Simple" logo it must direct them back to http://www.knowledgetree.com. In addition, the copyright notice must remain visible to all users at all times at the bottom of the user interface screen. When users click on the copyright notice, it must direct them back to http://www.knowledgetree.com diff --git a/docs/CREDITS.txt b/docs/CREDITS.txt deleted file mode 100644 index 3d83386..0000000 --- a/docs/CREDITS.txt +++ /dev/null @@ -1,26 +0,0 @@ -KnowledgeTree(tm) makes use of the following components: --------------------------------------------------------- - -Email: -phpmailer - http://phpmailer.sourceforge.net (LGPL) - -Javascript: -MochiKit - http://www.mochikit.com/ (MIT License) -JS Calendar - http://dynarch.com/mishoo/calendar.epl (LGPL) -TinyMCE - http://sourceforge.net/projects/tinymce/ (LGPL) -Option Transfer Widget - http://www.mattkruse.com/ (Custom License) - -Tests: -simpletest - http://www.lastcraft.com/simple_test.php (LGPL) - -Icons: -"Silk" - http://www.famfamfam.com/lab/icons/silk/ (CC Attribution License) - -Alumni: -------- - -KnowlegeTree has previously utilised code from the following sources: - -Mark Round's AuthLDAP class (class.AuthLDAP.php): -http://phpclasses.dknss.com/browse/package/893.html (GPL) - diff --git a/docs/FAQ.txt b/docs/FAQ.txt deleted file mode 100644 index e813638..0000000 --- a/docs/FAQ.txt +++ /dev/null @@ -1,66 +0,0 @@ -KnowledgeTree(tm) DMS - Frequently Asked Questions - -Q: I can't seem to search inside my files? - -A: There are two things which may cause full-text search not to work: - - 1. Make sure that the Indexing plugin is enabled - (in Admin > Misc > Manage Plugins) - 2. Ensure that the appropriate programs are installed, and - (especially on Windows) that the config.ini section "indexer" - contains the correct paths to the files. - -Q: Where do I post questions about installing, configuring or using KnowledgeTree? - -A: Our community forums are a good place to ask questions about - installing, configuring or using KnowledgeTree. Our developers, along - with other members of the open source community and our partner - network, will endeavour to answer your questions. - - Click on the link below to access the forums: - http://forums.knowledgetree.com/ - -Q: Where can I discuss document management best practices, change - management and training issues? - -A: Our community forums are a good place to discuss best practices for - document management, software implementation and training with our - developers, other members of the open source community and our - partner network. - - Click on the link below to access the forums: - - http://forums.knowledgetree.com/ - -Q: Where can I report bugs in KnowledgeTree? - -A: You can report bugs in KnowledgeTree by accessing our online - ticketing system. The ticketing system will also provide feedback on - the status of the issue. You may view issues reported by other people - and search the system to determine if your issue has already been - reported. - - Click on the link below to access the ticketing system: - - http://issues.knowledgetree.com/ - -Q: I want to modify KnowledgeTree or develop new functionality for it. - Where do I find more information on how to go about doing this? - -A: You can find out more information about modifying KnowledgeTree, - developing new functionality or translating the software at the - development Wiki. The Wiki is constantly under development and even - you may add content to it! - - Click on the link below to access the Wiki: - - http://wiki.knowledgetree.com/ - - -KnowledgeTree Document Management System -Web page: http://www.knowledgetree.com/ -Wiki: http://wiki.knowledgetree.com/ -Forums: http://forums.knowledgetree.com/ -Bug reporting: http://issues.knowledgetree.com/ - -$Id$ diff --git a/docs/INSTALL.WIN32.txt b/docs/INSTALL.WIN32.txt deleted file mode 100644 index 7686aa8..0000000 --- a/docs/INSTALL.WIN32.txt +++ /dev/null @@ -1,153 +0,0 @@ -Windows Specific Installation Instructions -========================================== - -Installation on Windows XP and 2003 requires a slightly different approach to -the generic instructions. - -The easiest installation approach for the Windows plaform is to use our -Windows installer. You can find this for download on SourceForge, -alongside our usual install bundles: - - http://sourceforge.net/projects/kt-dms - -Manual Install (XAMPP) ----------------------- - -If you need to do a manual installation of KnowledgeTree for some reason, -we recommend using a bundled version of Apache, MySQL and PHP. For testing -purposes, we use XAMPP (version 1.5.1): - - http://www.apachefriends.org/en/xampp.html - -NOTE - - At this time, KnowledgeTree 3 supports only PHP 4.x, so please ensure that - your XAMPP install is using PHP 4. - - Details can be found inside the XAMPP control panel, under the menu item - PHP Switch. - -General procedure: - - * Install XAMPP - - * Extract the KnowledgeTree zipfile inside the XAMPP htdocs directory. If - you installed XAMPP in - - c:\Program Files\xampp - - then you need to extract KnowledgeTree so that its files are in - - c:\Program Files\xampp\htdocs\knowledgeTree - - This will be referred to as "" in paths from here on. - - * Conduct the Pre-installation checkup. Assuming you are running XAMPP on - "localhost", visit - - http://localhost/knowledgeTree/setup/ - - * Configure the Database. The most effective way to do this with XAMPP is - to use phpmyadmin: - - http://localhost/phpmyadmin/ - - 1. Create a new database (call it "dms") - 2. Create the tables: - - - open the "dms" database from the left-menu/. - - go to "SQL" at the top of the screen. - - Where it says "Location of the text file" click browse and then run: - - * \sql\mysql\install\structure.sql - * \sql\mysql\install\data.sql - * \sql\mysql\install\user.sql - - * Configure your installation in config\config.ini: - - - The default configuration will determine many settings on your - installation automatically, and this is the preferred method of - running KnowledgeTree. Please do not manually set these settings - unless you know what you are doing. - - - The default configuration uses the database username and password - in the user.sql file mentioned above, use the local host for the - database, and use the database named 'dms'. If you follow the - examples above in setting up the database, this means KnowledgeTree - should be fully configured to start working. - - - However, you should change this once you've performed your initial - evalution of KnowledgeTree for the security of your documents. - - - The following settings in config/config.ini control the - database connectivity, and can be set as shown: - - [db] - dbHost = localhost - dbName = dms - dbUser = myuser - dbPass = mypassword - - * Check the post-installation checklist: - - If your knowledgeTree installation is at http://localhost/, go to: - - http://localhost/setup/ - - And click on "Post-installation checkup". - - * Login: - - in a web browser go to your KnowledgeTree installation via the web - - default user is "admin" with password "admin" - - * Register the standard plugins. - - - in a web browser go to "DMS Administration" , then "Miscellaneous", - then "Manage Plugins" - - click "Reread plugins" to load the list of available plugins. - - enable the plugins as required. - - * Please note: * - Fulltext indexing of files (e.g. checking their contents) needs to be - activated from this menu or the full-text search WILL NOT work. - - -External applications ---------------------- - -The file indexing and other facilities of KnowledgeTree make use of -external applications to perform their jobs. - -For the Windows platform, these are: - -. antiword - http://www.informatik.uni-frankfurt.de/~markus/antiword/ -. xpdf - http://www.foolabs.com/xpdf/ -. InfoZip unzip and zip - http://www.info-zip.org/ - -Installing these packages is beyond the scope of this document - please -consult the KnowledgeTree Wiki at http://wiki.knowledgetree.com/ -to see how others have approached this on your platform. - -You can find Windows specific installation instructions here: - - http://wiki.knowledgetree.com/Windows_XP_installation_instructions - - -Troubleshooting ---------------- - -Please make sure that your KnowledgeTree installation passes all the -pre- and post-installation checkups first. - -Refer to the Frequently Asked Questions list on the KnowledgeTree Wiki -at http://wiki.knowledgetree.com/ - -Ask on the KnowledgeTree forums on http://forums.knowledgetree.com/. - -If you have found a bug, please report it to the KnowledgeTree bug -reporting system at http://issues.knowledgetree.com/. - -Upgrading ---------- - -Refer to docs/UPGRADE.txt diff --git a/docs/INSTALL.txt b/docs/INSTALL.txt deleted file mode 100644 index b59cfe6..0000000 --- a/docs/INSTALL.txt +++ /dev/null @@ -1,162 +0,0 @@ -KnowledgeTree Installation Notes --------------------------------- - -* KnowledgeTree requires the following software to run: - - Apache 1.3 or above - - MySQL 4.1.6 or above, with InnoDB support - - PHP 4.3.0 or above, but not yet PHP 5.0 - -* Move the knowledgeTree folder to the directory it is going to be served from: - $ mv knowledgeTree /path/to/your/html/directory/ - -* Configure your web server to access the KnowledgeTree system. - - Due to the many different configuration possibilities, these can not - all be discussed here. Please consult the KnowledgeTree Wiki system - at http://wiki.knowledgetree.com/ to see what others have done - on your platform, and discuss the pros and cons of various options on - the KnowledgeTree Forums at http://forums.knowledgetree.com/ - -* Check the pre-installation checkup: - - If your knowledgeTree installation is at http://localhost/, go to: - - http://localhost/setup/ - -* Set up the database - - On a Unix-like system, the command line tools can generally be used: - - - Create a database: - $ mysqladmin -p create dms - - - Create and populate the tables: - $ mysql -p dms < sql/mysql/install/structure.sql - $ mysql -p dms < sql/mysql/install/data.sql - - - Create the database users - $ mysql -p dms < sql/mysql/install/user.sql - - These tools may requite the setting of the user (-u username) and of - a password (-p, and you will be asked for the password). - - Using other tools is beyond the scope of this document. Consult the - KnowledgeTree Wiki at http://wiki.knowledgetree.com/ to see how - others have approached this on your platform. - -* Configure your installation in config/config.ini: - - The default configuration will determine many settings on your - installation automatically, and this is the preferred method of - running KnowledgeTree. Please do not manually set these settings - unless you know what you are doing. - - - The default configuration uses the database username and password - in the user.sql file mentioned above, use the local host for the - database, and use the database named 'dms'. If you follow the - examples above in setting up the database, this means KnowledgeTree - should be fully configured to start working. - - - However, you should change this once you've performed your initial - evalution of KnowledgeTree for the security of your documents. - - - The following settings in config/config.ini control the - database connectivity, and can be set as shown: - [db] - dbHost = localhost - dbName = dms - dbUser = myuser - dbPass = mypassword - -* Check permissions on the folders - - The "var" folder in the root of the KnowledgeTree - installation MUST be able to be written to by your web server. - - - The pre-configuration checkup will display the user which must be - able to write to these folders. - - - The remaining folders should preferably not be able to be written - to by your web server. - - - eg. - If your web server is running as user "nobody" and group "nogroup" - then cd to the files directory and type: - - *nix: 'chown -R nobody.nogroup var' - Windows: Check the permissions and security tabs - - -* Check the post-installation checklist: - - If your knowledgeTree installation is at http://localhost/, go to: - - http://localhost/setup/ - - And click on "Post-installation checkup". - - -* Login: - - in a web browser go to your KnowledgeTree installation via the web - - default user is "admin" with password "admin" - -* Register the standard plugins. - - in a web browser go to "DMS Administration" , then "Miscellaneous", - then "Manage Plugins" - - click "Reread plugins" to load the list of available plugins. - - enable the plugins as required. - - * Please note: * - Fulltext indexing of files (e.g. checking their contents) needs to be - activated from this menu or the full-text search WILL NOT work. - -External applications ---------------------- - -The file indexing and other facilities of KnowledgeTree make use of -external applications to perform their jobs. - -For the Windows platform, these are: - -. catdoc - http://www.45.free.net/~vitus/ice/catdoc/ -. xpdf - http://www.foolabs.com/xpdf/ -. InfoZip unzip and zip - http://www.info-zip.org/ - -Installing these packages is beyond the scope of this document - please -consult the KnowledgeTree Wiki at http://wiki.knowledgetree.com/ -to see how others have approached this on your platform. We recommend -that you use the appropriate package management procedures for -installing these packages on your system to ensure ease of maintenance -and upgrade. - -NOTE: if you install the packages outside of the path normally searched -by your operating system (e.g. in c:\antiword or /usr/local/bin) you will -need to specify the _full_ path to the actual applications (e.g. -/usr/local/bin/pdftotext). - -Troubleshooting ---------------- - -Please make sure that your KnowledgeTree installation passes all the -pre- and post-installation checkups first. - -Refer to the Frequently Asked Questions list on the KnowledgeTree Wiki -at http://wiki.knowledgetree.com/ - -Ask on the KnowledgeTree forums on http://forums.knowledgetree.com/. - -If you have found a bug, please report it to the KnowledgeTree bug -reporting system at http://issues.knowledgetree.com/. - -Upgrading ---------- - -Refer to docs/UPGRADE.txt - - - -KnowledgeTree Document Management System -Web page: http://www.knowledgetree.com/ -Wiki: http://wiki.knowledgetree.com/ -Forums: http://forums.knowledgetree.com/ -Bug reporting: http://issues.knowledgetree.com/ - -$Id$ diff --git a/docs/README.txt b/docs/README.txt index d967583..b76226e 100644 --- a/docs/README.txt +++ b/docs/README.txt @@ -1,49 +1,14 @@ -KnowledgeTree Document Management System ----------------------------------------- +===================================================== + Knowledgetree Documentation, Support and Community +===================================================== -KnowledgeTree 3 is intended to be easier to use for users and -administrators (including a new user interface) and also easy for -developers to customise it and make plugins for it. +* You can access all the KnowledgeTree documentation online at: -KnowledgeTree 3 includes a set of core and standard plugins that broadly -cover the functionality offered by KnowledgeTree 2, although almost all -code has been rewritten or analysed before reuse. +- http://docs.knowledgetree.com -New and extended functionality includes: - * Entirely new template-based user interface, allowing for easy changes to - the application's look and feel and easy to implement co-branding - opportunities. - * On-demand indexing of files as opposed to scheduled indexing, ensuring - files are searchable immediately after uploading and simplifying the - installation of the server. - * Secure versioning of document metadata, not just the document itself. - This vastly increases the application's applicability in regulatory - compliance scenarios. - * A new tree document metadata type has been added with the tree being - represented graphically on the user interface. - * The User/Group schema has been extended to allow groups to be nested, - thus providing for the mapping of users in more complex organisations. - * The move folder and move file functionality is now transactional and - records a history of changes to the folder structure. - * Bulk import functionality allows administrators to import large numbers - of files from external data sources quickly and easily. - * KnowledgeTree administrators may customise and extend the KnowledgeTree - online help facilities using a web-based editor. - * A powerful plug-in architecture, providing KnowledgeTree developers with - the ability to easily create new application functionality, hook into - system events and expose the functionality on the user interface. - * A revamped permissions system which is easier to use and provides finer - grained control over a user's actions than in KnowledgeTree 2.x. The - extended functionality also lets KnowledgeTree community developers - create their own permissions on the system, allowing their plug-ins to - easily check permissions that they require to function. -For installation instructions please refer to docs/INSTALL.txt +* To learn more about KnowledgeTree and the KnowledgeTree community you can start at: -KnowledgeTree Document Management System -Web page: http://www.knowledgetree.com/ -Wiki: http://wiki.knowledgetree.com/ -Forums: http://forums.knowledgetree.com/ -Bug reporting: http://issues.knowledgetree.com/ +- http://www.knowledgetree.com/products/opensource/welcome/ -$Id$ +where you will find many community resources including forums, wikis, irq, etc. \ No newline at end of file diff --git a/docs/TODO.txt b/docs/TODO.txt deleted file mode 100644 index edca825..0000000 --- a/docs/TODO.txt +++ /dev/null @@ -1,17 +0,0 @@ -KnowledgeTree DMS Development TODO List ---------------------------------------- - -- Reporting- Simple usage and statistics report generator -- Zip functions - - Mass download - - download- zip up and download file lists (folders, categories, document types, search list) -- Automated Test Suite - - For Coverage and performance tests -- Write custom error handler -- Security audit -- Logging - - Make logging robust - - Revisit application logging and tidy up logging levels. -- Allow thumbnails for image types (API for any other filetype) - -$Id$ diff --git a/docs/UPGRADE.txt b/docs/UPGRADE.txt deleted file mode 100644 index 28f49f2..0000000 --- a/docs/UPGRADE.txt +++ /dev/null @@ -1,97 +0,0 @@ -KnowledgeTree Upgrade instructions -================================== - -Before you upgrade ------------------- - -Before you upgrade, ensure that your data (KnowledgeTree, Documents, and -database) is backed up safely. An upgrade may fail to accurately change -the data to the format required by the next version of KnowledgeTree, -and a backup will allow you to return to the original version of -KnowledgeTree. Please report failed upgrades to the KnowledgeTree -developers. - -Ensure that the web user may write to all the folders within the 'var' -folder, so that logging and other changes are possible. - -Make sure to read the "Additional steps" section towards the end of the -document to ensure that any specific steps for your upgrade are -performed before you continue. - -Automated upgrade ------------------ - -The automated upgrade may be used from the command line or through a web -page. The web page is preferable, as it provides better error -reporting. The automated upgrade works between any version of -KnowledgeTree to the current version. The automated upgrade remembers -which upgrades it has performed, and will not perform them again, unless -forced to do so. Using the automated upgrade will create an upgrade -history that can be reviewed via the KnowledgeTree administrators -interface. - -If you are upgrading KnowledgeTree from versions prior to 3.0.0, see the -section at the bottom of this document to set up automated upgrades. - -Web page: - -- If your KnowledgeTree installation is at http://example.org/kt/, - visit: - - http://example.org/kt/setup/upgrade.php - -- Review the upgrades available to you, and select the button to perform - the upgrade. - -- Review the results of the upgrade. - -Command line: - -- Run bin/automated-upgrade.php -- Any errors will be reported. - -========================================================================== - - -Additional steps ----------------- - -KnowledgeTree 2.0.6 -------------------- - -The automated upgrade requires that you set up a database administrator -user (name configurable in config/environment.php, defaults to -'dmsadmin') for the upgrade process to function. You need to run this -command on your database (say, 'dms') from the MySQL command prompt: - -mysql> use dms; -mysql> GRANT ALL PRIVILEGES ON * TO dmsadmin@localhost IDENTIFIED BY 'js9281djw'; - -In config/environment.php, you should add: - -$default->dbAdminUser = "dmsadmin"; -$default->dbAdminPass = "js9281djw"; - -You should now be able to use the automated upgrade. - -KnowledgeTree 3.0.0 -------------------- - -KnowledgeTree 3.0 includes the move of the default document storage -location from "Documents" in the root of the KnowledgeTree install to -"var/Documents". The "log" directory has also moved to "var/log". - -If you are using the default document storage location (ie, you have not -specifically set another document location), move the Documents -directory to "var/Documents before upgrading. - - ---------------------------------------------------------------------------- - -KnowledgeTree Document Management System -Web page: http://www.knowledgetree.com/ -Wiki: http://wiki.knowledgetree.com/ -Forums: http://forums.knowledgetree.com/ -Bug reporting: http://issues.knowledgetree.com/ - -$Id$ diff --git a/docs/developer/Browse.txt b/docs/developer/Browse.txt deleted file mode 100644 index b0eadef..0000000 --- a/docs/developer/Browse.txt +++ /dev/null @@ -1,40 +0,0 @@ -KT3 Browse System -================= - -KnowledgeTree's browse view has been a serious bottleneck in terms of -performance, and makes extending the system in useful ways (and re-using items) -unnecessarily hard. - -To understand this code, you'll need to look at: - - - lib/browse/DocumentCollection.inc.php - - lib/browse/BrowseColumns.inc.php - - presentation/.../browse.php - -Objectives of the refactor: - - - improve code-reuse - - make more advanced document-sets possible - - unify all document-collection logic (where possible). - -BROWSE VIEW GENERATION ----------------------- - -Generating a browse view is now done as follows: - - - create a DocumentCollection object - - add "BrowseColumns" to it. - - specify (on the collection) which column to sort on. - - specify any batching that may be required (count, start). - - execute the query (using generateCollection). - returns a set of document ids, in order (more info cached internally). - - for each row, use "getInfo(docid)" to extract the information from the database. - returns an array with info (more later), and caches this internally. - - at render-time, call "renderRow(docid)". - -Internally this does a fair bit more work. Particularly: - - - each Column can contribute JOINs, WHERE clauses. _if_ its the sort column, - it gets asked for an ORDER clause. - - the system fetches a LOT of information about each batched item - don't do too much. - diff --git a/docs/developer/Permissions.txt b/docs/developer/Permissions.txt deleted file mode 100644 index ca1c73a..0000000 --- a/docs/developer/Permissions.txt +++ /dev/null @@ -1,72 +0,0 @@ -KnowledgeTree Permission System -=============================== - -Permission Object ------------------ -Permissions on items in the DMS are handled via a Permission Object. -This permission object is where the permissions for the object are kept. -Previously, a permission folder was used, but this was changed to an -autonomous permission object to allow greater flexibility - such as -allowing documents to have their own permissions in future. - -Permission Assignments ----------------------- -This permission object links the item with a number of permission -assignments - one permission assignment per permission. A permission -assignment is uniquely specified by a permission object and a -permission. The final component is a permission descriptor, which -describes the groups, users, or roles that have that permission on that -permission object. - -Permission Descriptor ---------------------- -The permission descriptor is an indirection to reduce the number of rows -to describe which groups, users, and roles that have permissions on each -permission object. It allows assignments that cover the same groups, -users, and roles to be described textually and looked up quickly by a 32 -character hash. A particular collection of groups, users, and roles -will always be described by a unique descriptor. - -Permission Lookup ------------------ -Permission Lookup objects describe the collections of groups and users -that have each permission on the item in the repository. It is an -expanded form of the permission object - if an owner role has a -permission in terms of the permission object, the exact user with that -role on that object will be mentioned in the permission lookup. - -Permission lookups exist mostly for restricting a search for items in -the repository to those items for whom a particular user has a given -permission. The most obvious users of this are the content and metadata -searches, which need to restrict results to documents readable by the -current user. Other users may be the list of documents in a folder -readable by the current user, or the list of folders in the repository -that the user can add documents to. - -Managing Permissions --------------------- - -Permission lookups use descriptors that never expand groups. Changes in -membership of a group don't require permission lookups. When looking up -using permission lookups, the descriptors that the user has access to -are looked up at run-time first, and these are used to limit the -searches. - -On creation, folders and documents inherit the permission object of -their parent. They then update their own permission lookups. -(Document::create, Folder::create) - -When folders change their permission object (become their own master, -start using their parent again, are moved), they update all ancestor -folders and documents that had the old permission object to the new one. -Those changed then have their permission lookups updated. -(KTPermissionUtil::copyPermissionObject, -KTPermissionUtil::inheritPermissionObject) - -When documents change their permission object (become their own master, -start using their parent again, are moved), they update their own -permission lookups. -(KTPermissionUtil::copyPermissionObject, -KTPermissionUtil::inheritPermissionObject) - - diff --git a/docs/developer/RELEASE.txt b/docs/developer/RELEASE.txt deleted file mode 100644 index dfbcb55..0000000 --- a/docs/developer/RELEASE.txt +++ /dev/null @@ -1,25 +0,0 @@ -Here is the release process for KnowledgeTree. - -Test: -1.1. Testing. - -Prepare: -2.1. Update Changelog. -2.2. Put release date into Changelog.txt -2.3. Update database install and upgrade SQL scripts -2.4. Update version number in database install and upgrade scripts -2.5. Tag CVS - RELEASE_1_2_3_20040909 -2.6. kt/releaseKT.sh -b RELEASE_1_2_3_20040909 -v 1.2.3 -2.7. Test final release - -Release: -3.1. ncftpput upload.sourceforge.net /incoming knowledgeTree-1.2.3.tgz knowledgeTree-1.2.3.zip -3.2. Add to Sourceforge file manager -3.3. Update Web site version number and features. - -Inform: -4.1. Mail kt-dms-users and kt-dms-developers and kt-dms-announce -4.2. Add to Forums - -Post-release: -5.1. Prepare Changelog.txt for next release diff --git a/docs/developer/codingStandards.txt b/docs/developer/codingStandards.txt deleted file mode 100644 index 77f457f..0000000 --- a/docs/developer/codingStandards.txt +++ /dev/null @@ -1,13 +0,0 @@ -Coding Standard Doc -===================== -(Inform - can be formalized later. Only standards above and beyond those in the original spec are included here) - -1) All functions return their required value on success or false otherwise. On returning false, all function - set the $_SESSION["errorMessage"] variable -2) All presentation layer files must contain a list of the expected querystring and form variables they will receive -3) Any function that inserts into a database table must begin its name with "create" e.g. createFolder(). The exception - to this is a function which inserts into a link table. It must begin its name with "add" e.g. addUserToGroup() -4) All database tables that consist of id, name pairs will end in the word "lookup" e.g. groups_lookup -5) All database tables that link two or more tables together will end in the word "link" -6) When using the @return tag in the case of mixed return types, the return type should always be the - type that is returned if the function succeedes i.e. does what it is supposed to do diff --git a/docs/developer/i18n.txt b/docs/developer/i18n.txt deleted file mode 100644 index a36d146..0000000 --- a/docs/developer/i18n.txt +++ /dev/null @@ -1,10 +0,0 @@ -KnowledgeTree Internationalisation (i18n) ------------------------------------------ - -Generating the PO template file -------------------------------- - -- install gettext command line utilities -- use bin/genpo.sh - -$Id$ diff --git a/docs/developer/metadata-versions.txt b/docs/developer/metadata-versions.txt deleted file mode 100644 index 30e52a7..0000000 --- a/docs/developer/metadata-versions.txt +++ /dev/null @@ -1,28 +0,0 @@ -Metadata versions -================= - -KnowledgeTree can keep a historic view of both the physical document and -the associated metadata. - -Version creation ----------------- -Metadata versions need to occur when: -- A new physical document is added -- Metadata is changed - -Database effects ----------------- -Metadata versions are stored in the standard documents table, with the -document status set to STATUS_HISTORY (6). Metadata versions are copies -of the document table currently, and all associated generic and -type-specific metadata. Each metadata version has its own metadata -version number (metadata_version, getMetadataVersion()). - -This configuration makes searches much easier. - -Interface changes ------------------ -Metadata versions are listed in the document detail view under "Metadata -Versions". When selected, the document detail view is updated to place -the metadata version on the right-hand side of the view, allowing -comparison. diff --git a/plugins/ktcore/KTBulkActions.php b/plugins/ktcore/KTBulkActions.php index 7fb3940..e5d0821 100644 --- a/plugins/ktcore/KTBulkActions.php +++ b/plugins/ktcore/KTBulkActions.php @@ -232,7 +232,7 @@ class KTBulkMoveAction extends KTBulkAction { $this->iTargetFolderId = $_REQUEST['data']['fFolderId']; $this->oTargetFolder = Folder::get($this->iTargetFolderId); $_REQUEST['fReturnData'] = ''; - $_REQUEST['fFolderId'] = $this->iTargetFolderId; + $_REQUEST['fFolderId'] = $this->iTargetFolderId; // does it exists if(PEAR::isError($this->oTargetFolder)) {