DOCSLIB.ORG

WP-MIRROR 0.5 Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
WP-MIRROR 0.5 Reference Manual WP-MIRROR 0.5 Reference Manual Dr. Kent L. Miller December 14, 2012 1 2 To Tylery i WP-MIRROR 0.5 Reference Manual Legal Notices Copyright (C) 2012 Dr. Kent L. Miller. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. THIS PUBLICATION AND THE INFORMATION HEREIN ARE FURNISHED AS IS, ARE FURNISHED FOR INFORMATIONAL USE ONLY, ARE SUBJECT TO CHANGE WITH- OUT NOTICE, AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY THE AU- THOR. THE AUTHOR ASSUMES NO RESPONSIBILITY OR LIABILITY FOR ANY ER- RORS OR INACCURACIES THAT MAY APPEAR IN THE INFORMATIONAL CONTENT CONTAINED IN THIS MANUAL, MAKES NO WARRANTY OF ANY KIND (EXPRESS, IMPLIED, OR STATUTORY) WITH RESPECT TO THIS PUBLICATION,AND EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR PAR- TICULAR PURPOSES, AND NONINFRINGEMENT OF THIRD-PARTY RIGHTS. The WP-MIRROR logotype (see margin) includes a sunflower that is derived from 119px-Mediawiki logo sunflower Tournesol 5x rev2.png, which is in the public domain. See http://en.wikipedia.org/wiki/File:Mediawiki_logo_sunflower_Tournesol_5x.png. Debian is a registered United States trademark of Software in the Public Interest, Inc., man- aged by the Debian project. Linux is a trademark of Linus Torvalds. InnoDB and MySQL are trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Abstract The WikiMedia Foundation offers wikipedias in nearly 300 languages. WP-MIRROR is a free utility for mirroring any desired set of these wikipedias. That is, it builds a wikipedia farm that the user can browse locally. Many users need such off-line access, often for reasons of mobility, availability, and privacy. They currently use kiwix which provides selected articles and thumbnail images. WP-MIRROR builds a complete mirror with original size images. WP-MIRROR is robust and uses check-pointing to resume after interruption. By default, WP-MIRROR mirrors the simple wikipedia (Simple English means shorter sentences). The default should work ‘out-of-the-box’ with no user configuration. It should build in 200ks (two days), occupy 60G of disk space, be served locally by a virtual host http://simple.wpmirror.site/, and update automatically every week. The default should be suitable for anyone who learned English as a second language (ESL). The top ten wikipedias are: en de, fr, nl, it, es, pl, ru, ja, and pt. Because WP-MIRROR uses original size image files, these wikipedias are too large to fit on a laptop with a single 500G disk. When higher capacity hard disk drives reach the market, this list may be shortened. But for now, a desktop PC with ample disk space and main memory is required for any of the top ten, unless the user does not need the images (and this is configurable). ii The en wikipedia is the most demanding case. It should build in 5Ms (two months), occupy 3T of disk space, be served locally by a virtual host http://en.wpmirror.site/, and update automatically every month. This project’s current Web home page is http://www.nongnu.org/wp-mirror/. This document was generated on December 14, 2012. Features WP-MIRROR has been designed for robustness. WP-MIRROR asserts hardware and software prerequisites, skips over unparsable articles and bad file names, validates image files (many are corrupt), waits for Internet access when needed, uses check-pointing to resume after interruption, and offers concurrency to accelerate mirroring of the largest wikipedias. WP-MIRROR warns: if MySQL is insecure (e.g. has a root account with no password), and if a caching web proxy is detected. WP-MIRROR warns if disk space may be inadequate for the default (a mirror of the simple wikipedia), and gracefully exits if disk space runs too low. WP-MIRROR normally runs in background as a weekly cron job, updating the mirror when- ever the WikiMedia Foundation posts new dump files. Most features are configurable, either through command-line options, or via the configuration file /etc/wp-mirror/local.conf. Wikipedias can be added to the mirror, or dropped from it. If a user makes a hash of the configuration files and wants to start over, just execute root-shell# wp-mirror --restore-default which drops all WP-MIRROR related databases and files (except image files). This option is used regularly during software development and debugging. A user who wishes also to delete the image files, may execute: root-shell# cd /var/lib/mediawiki/images/ root-shell# rm --recursive --force * That said, a good network citizen would try to avoid burdening the Internet by downloading the same files, over and over. Troubleshooting If WP-MIRROR fails or hangs, please take a look at the log files /var/log/wp-mirror.log. Alternatively, try running root-shell# wp-mirror --debug root-shell# tail -n 1000 /var/log/wp-mirror.log The last few lines in the log file should provide a clue. Developers should select some of the smaller wikipedias (e.g. the cho, xh, and zu wikipedias) to speed up the test cycle. WP-MIRROR was written and is maintained by Dr. Kent L. Miller. Please see §1.8, Credits for a list of contributors. Please report bugs in WP-MIRROR to <[email protected]>. iii Contents WP-MIRROR 0.5 Reference Manual ii Contents iv List of Figures xii List of Tables xiii 1 General Information 1 1.1 About This Manual ................................... 1 1.2 Typographical and Syntax Conventions ........................ 2 1.3 Overview of WP-MIRROR ............................... 2 1.3.1 What is WP-MIRROR? ............................ 2 1.3.2 History of WP-MIRROR ............................ 3 1.3.3 The Main Features of WP-MIRROR ..................... 4 1.4 WP-MIRROR Development History .......................... 5 1.5 What Is New in WP-MIRROR ............................. 6 1.5.1 What Is New in WP-MIRROR 0.5 ....................... 6 1.5.2 What Is New in WP-MIRROR 0.4 ....................... 7 1.5.3 What Is New in WP-MIRROR 0.3 ....................... 8 1.5.4 What Is New in WP-MIRROR 0.2 ....................... 8 1.5.5 What Is New in WP-MIRROR 0.1 ....................... 9 1.6 WP-MIRROR Information Sources .......................... 10 1.6.1 Project Home Page for WP-MIRROR ..................... 10 1.6.2 Downloading WP-MIRROR .......................... 10 1.6.3 Documentation for WP-MIRROR ....................... 10 1.6.4 Mailing Lists for WP-MIRROR ........................ 10 1.7 How to Report Bugs or Problems ........................... 11 1.8 Credits .......................................... 11 1.8.1 Contributors to WP-MIRROR ......................... 11 1.8.2 Documenters and Translators ......................... 11 2 Installing and Upgrading WP-MIRROR 12 2.1 General Installation Guidance ............................. 12 2.1.1 Operating Systems Supported by WP-MIRROR ............... 12 2.1.2 GNU/Linux Distributions Supported by WP-MIRROR ........... 12 2.1.3 How to Get WP-MIRROR ........................... 12 2.1.4 Choosing Which WP-MIRROR Distribution to Install ........... 13 2.1.4.1 Choosing Which Version of WP-MIRROR to Install ....... 13 2.1.4.2 Choosing a Distribution Format ................... 13 2.1.4.3 Choosing When to Upgrade ..................... 13 2.1.5 Verifying Package Integrity Using Checksums or GnuPG ........... 13 2.1.5.1 How to Get the Author’s Public Build Key ............ 13 2.1.5.1.1 Download the Public Key from Public Keyserver . 14 iv Contents 2.1.5.1.2 Cut and Paste the Public Key from Public Keyserver . 14 2.1.5.2 Checksums for a DEB Package .................... 15 2.1.5.3 Checksums for a RPM Package .................... 16 2.1.5.4 Signature Checking for a Tarball .................. 16 2.2 Installing WP-MIRROR on Linux ........................... 16 2.2.1 Installing from a DEB Package ......................... 17 2.2.2 Installing from a RPM Package ......................... 17 2.3 Installing WP-MIRROR from Source ......................... 17 2.3.1 Installing Dependencies ............................. 18 2.3.1.1 Installing Build Dependencies .................... 18 2.3.1.2 Verifying clisp Version ....................... 18 2.3.1.3 Configuring common-lisp-controller ............... 18 2.3.1.4 Configuring cl-asdf ......................... 19 2.3.1.5 Installing Binary Dependencies ................... 19 2.3.2 Installing WP-MIRROR from a Standard Source Distribution ....... 20 2.3.3 WP-MIRROR Build Options .......................... 20 2.4 Postinstallation Configuration and Testing ...................... 21 2.4.1 Default Configuration .............................. 21 2.4.2 Working with X ................................. 21 2.4.3 Configuration of a Wikipedia Farm ...................... 22 3 System Planning and Configuration 24 3.1 General Information ................................... 24 3.2 Laptop Planning and Configuration .......................... 25 3.2.1 Plan Your Disk Space .............................. 25 3.2.1.1 Disable HDD Write Caching ..................... 25 3.2.1.2 Put images Directory on Partition with Adequate Free Space . 26 3.2.1.3 Setup Thermal Management ..................... 27 3.2.1.4 Setup smart Disk Monitoring .................... 27 3.2.2 Plan Your Database Management System ................... 28 3.2.2.1 Secure the Database Management System ............. 28 3.2.2.2 Load the DBMS time zone Tables ................. 29 3.2.2.3 Configure the InnoDB Storage Engine ................ 30 3.2.3 Plan Your DRAM ................................ 31 3.2.4 Plan Your Internet Access ........................... 31 3.2.4.1 Configure cURL ............................ 31 3.2.5 Plan Your MediaWiki .............................. 32 3.2.5.1 Configure MediaWiki ......................... 32 3.2.5.2 Enable MediaWiki Extensions .................... 33 3.2.5.3 MediaWiki Redux ........................... 34 3.2.6 Plan Your Image Processing .........................
Load more

Recommended publications
  • Darktable 1.2 Darktable 1.2 Copyright © 2010-2012 P.H
    darktable 1.2 darktable 1.2 Copyright © 2010-2012 P.H. Andersson Copyright © 2010-2011 Olivier Tribout Copyright © 2012-2013 Ulrich Pegelow The owner of the darktable project is Johannes Hanika. Main developers are Johannes Hanika, Henrik Andersson, Tobias Ellinghaus, Pascal de Bruijn and Ulrich Pegelow. darktable is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. darktable is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with darktable. If not, see http://www.gnu.org/ licenses/. The present user manual is under license cc by-sa , meaning Attribution Share Alike . You can visit http://creativecommons.org/ about/licenses/ to get more information. Table of Contents Preface to this manual ............................................................................................... v 1. Overview ............................................................................................................... 1 1.1. User interface ............................................................................................. 3 1.1.1. Views ..............................................................................................
    [Show full text]
  • Scape D10.1 Keeps V1.0
    Identification and selection of large‐scale migration tools and services Authors Rui Castro, Luís Faria (KEEP Solutions), Christoph Becker, Markus Hamm (Vienna University of Technology) June 2011 This work was partially supported by the SCAPE Project. The SCAPE project is co-funded by the European Union under FP7 ICT-2009.4.1 (Grant Agreement number 270137). This work is licensed under a CC-BY-SA International License Table of Contents 1 Introduction 1 1.1 Scope of this document 1 2 Related work 2 2.1 Preservation action tools 3 2.1.1 PLANETS 3 2.1.2 RODA 5 2.1.3 CRiB 6 2.2 Software quality models 6 2.2.1 ISO standard 25010 7 2.2.2 Decision criteria in digital preservation 7 3 Criteria for evaluating action tools 9 3.1 Functional suitability 10 3.2 Performance efficiency 11 3.3 Compatibility 11 3.4 Usability 11 3.5 Reliability 12 3.6 Security 12 3.7 Maintainability 13 3.8 Portability 13 4 Methodology 14 4.1 Analysis of requirements 14 4.2 Definition of the evaluation framework 14 4.3 Identification, evaluation and selection of action tools 14 5 Analysis of requirements 15 5.1 Requirements for the SCAPE platform 16 5.2 Requirements of the testbed scenarios 16 5.2.1 Scenario 1: Normalize document formats contained in the web archive 16 5.2.2 Scenario 2: Deep characterisation of huge media files 17 v 5.2.3 Scenario 3: Migrate digitised TIFFs to JPEG2000 17 5.2.4 Scenario 4: Migrate archive to new archiving system? 17 5.2.5 Scenario 5: RAW to NEXUS migration 18 6 Evaluation framework 18 6.1 Suitability for testbeds 19 6.2 Suitability for platform 19 6.3 Technical instalability 20 6.4 Legal constrains 20 6.5 Summary 20 7 Results 21 7.1 Identification of candidate tools 21 7.2 Evaluation and selection of tools 22 8 Conclusions 24 9 References 25 10 Appendix 28 10.1 List of identified action tools 28 vi 1 Introduction A preservation action is a concrete action, usually implemented by a software tool, that is performed on digital content in order to achieve some preservation goal.
    [Show full text]
  • Grafika Rastrowa I Wektorowa
    GRAFIKA RASTROWA I WEKTOROWA Grafikę komputerową, w dużym uproszczeniu, można podzielić na dwa rodzaje: 1) grafikę rastrową, zwaną też bitmapową, pikselową, punktową 2) grafikę wektorową zwaną obiektową. Grafika rastrowa – obraz budowany jest z prostokątnej siatki punktów (pikseli). Skalowanie rysunków bitmapowych powoduje najczęściej utratę jakości. Grafika ta ma największe zastosowanie w fotografice cyfrowej. Popularne formaty to: BMP, JPG, TIFF, PNG GIF, PCX, PNG, RAW Znane edytory graficzne: Paint, Photoshop, Gimp. Grafika wektorowa – stosuje obiekty graficzne zwane prymitywami takie jak: punkty, linie, krzywe opisane parametrami matematycznymi. Podstawową zaletą tej grafiki jest bezstratna zmian rozmiarów obrazów bez zniekształceń. Popularne formaty to: SVG, CDR, EPS, WMF - cilparty Znane edytory graficzne: Corel Draw, Sodipodi, Inscape, Adobe Ilustrator, 3DS LISTA PROGRAMÓW DO GRAFIKI BITMAPOWEJ Darmowe: CinePaint , DigiKam , GIMP , GimPhoto , GIMPshop , GNU Paint , GrafX2 , GraphicsMagick , ImageJ , ImageMagick , KolourPaint , Krita , LiveQuartz , MyPaint , Pencil , Pinta , Pixen , Rawstudio , RawTherapee , Seashore , Shotwell , Tile Studio , Tux Paint , UFRaw , XPaint , ArtRage Starter Edition , Artweaver , Brush Strokes Image Editor , Chasys Draw IES , FastStone Image Viewer , Fatpaint , Fotografix , IrfanView , Paint.NET , Picasa , Picnik , Pixia , Project Dogwaffle , TwistedBrush Open Studio , Xnview Płatne: Ability Photopaint, ACD Canvas, Adobe Fireworks, Adobe Photoshop, Adobe Photoshop Lightroom, Adobe Photoshop Elements,
    [Show full text]
  • Fieldview User's Guide SOFTWARE RELEASE VERSION 16
    FieldView User’s Guide SOFTWARE RELEASE VERSION 16 Intelligent Light 301 Route 17 North 7th Floor Rutherford, NJ 07070 Copyright 2015 Intelligent Light Revision 16 All Rights Reserved Printed in USA First Printing November 2001 FieldView is a registered trademark of Intelligent Light Intelligent Light reserves the right to make changes in specifications and other information contained in this publication without prior notice and the reader should in all cases consult Intelligent Light to determine whether any such changes have been made. The terms and conditions governing the licensing of Intelligent Light software consist solely of those set forth in the Intelligent Light Binary License Terms and Conditions set forth in this document. No representations or other affirmation of fact contained in this publication, including but not limited to statements regarding capacity, response-time performance, suitability for use or performance of products described herein shall be deemed to be a warranty of Intelligent Light for any purpose, or give rise to any liability by Intelligent Light whatsoever. In no event shall Intelligent Light be liable for any incidental, indirect, special or consequential damages whatsoever (including but not limited to lost profits) arising out of or relating to this publication or the information contained in it, even if Intelligent Light has been advised, knew or should have known of the possibility of such damages. The software programs described in this document are confidential information and proprietary products of Intelligent Light or its licensors. Copyright © 1999-2010 ImageMagick Studio LLC, a non-profit organization dedicated to making software imaging solutions freely available.
    [Show full text]
  • Technical Notes All Changes in Fedora 13
    Fedora 13 Technical Notes All changes in Fedora 13 Edited by The Fedora Docs Team Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. Abstract This document lists all changed packages between Fedora 12 and Fedora 13.
    [Show full text]
  • 1. Why POCS.Key
    Symptoms of Complexity Prof. George Candea School of Computer & Communication Sciences Building Bridges A RTlClES A COMPUTER SCIENCE PERSPECTIVE OF BRIDGE DESIGN What kinds of lessonsdoes a classical engineering discipline like bridge design have for an emerging engineering discipline like computer systems Observation design?Case-study editors Alfred Spector and David Gifford consider the • insight and experienceof bridge designer Gerard Fox to find out how strong the parallels are. • bridges are normally on-time, on-budget, and don’t fall ALFRED SPECTORand DAVID GIFFORD • software projects rarely ship on-time, are often over- AS Gerry, let’s begin with an overview of THE DESIGN PROCESS bridges. AS What is the procedure for designing and con- GF In the United States, most highway bridges are budget, and rarely work exactly as specified structing a bridge? mandated by a government agency. The great major- GF It breaks down into three phases: the prelimi- ity are small bridges (with spans of less than 150 nay design phase, the main design phase, and the feet) and are part of the public highway system. construction phase. For larger bridges, several alter- There are fewer large bridges, having spans of 600 native designs are usually considered during the Blueprints for bridges must be approved... feet or more, that carry roads over bodies of water, preliminary design phase, whereas simple calcula- • gorges, or other large obstacles. There are also a tions or experience usually suffices in determining small number of superlarge bridges with spans ap- the appropriate design for small bridges. There are a proaching a mile, like the Verrazzano Narrows lot more factors to take into account with a large Bridge in New Yor:k.
    [Show full text]
  • Life Science Software
    Life Science Software Installation and User Instructions Doc-It®LS Image Acquisition Software Doc-It®LS Image Analysis Software VisionWorks®LS Image Acquisition Software VisionWorks®LS Image Acquisition and Analysis Software UVP, LLC Ultra-Violet Products Ltd. 2066 W. 11th Street Unit 1, Trinity Hall Estate, Nuffield Road Upland, CA 91786 Cambridge, CB4 1TG UK (800) 452-6788 or (909) 946-3197 +44(0)1223-420022 Fax: (909) 946-3597 Fax: +44(0)1223-420561 Web Site: www.uvp.com 81-0254-01 Rev. F UVP LIFE SCIENCE SERIES SOFTWARE TABLE OF CONTENTS CHAPTER ONE: WELCOME TO LIFE SCIENCE (LS) SOFTWARE .................................11 Introduction ................................................................................................................................................11 Minimum System Requirements ................................................................................................................11 Installation Instructions ..............................................................................................................................12 Secure User Accounts ...............................................................................................................................13 Usernames and Passwords .......................................................................................................................14 Matrix of User Rights .................................................................................................................................17 CHAPTER TWO: SOFTWARE
    [Show full text]
  • Darktable 2.0 Darktable 2.0 Copyright © 2010-2012 P.H
    darktable 2.0 darktable 2.0 Copyright © 2010-2012 P.H. Andersson Copyright © 2010-2011 Olivier Tribout Copyright © 2012-2015 Ulrich Pegelow Copyright © 2013-2015 Jérémy Rosen Le fondateur du projet darktable est Johannes Hanika. darktable a été développé avec les contributions majeures de Aldric Renaudin, Alexandre Prokoudine, Ammon Riley, Andrew Toskin, Andrey Kaminsky, Antony Dovgal, Artur de Sousa Rocha, Axel Burri, Brian Teague, Bruce Guenter, Cherrot Luo, Christian Himpel, Christian Tellefsen, Dan Torop, David Bremner, Dennis Gnad, Dimitrios Psychogios, Dušan Kazik, Eckhart Pedersen, Edouard Gomez, Frédéric Grollier, Gaspard Jankowiak, Ger Siemerink, Gianluigi Calcaterra, Guilherme Brondani Torri, Guillaume Benny, Henrik Andersson, Igor Kuzmin, Ivan Tarozzi, James C. McPherson, Jan Kundrát, Jean-Sébastien Pédron, Jérémy Rosen, Jesper Pedersen, Jochen Schröder, Johanes Schneider, Johnny Run, José Carlos Casimiro, Jose Carlos Garcia Sogo, Josep Vicenç Moragues Pastor, Kaminsky Andrey, Kanstantsin Shautsou, Karl Mikaelsson, Loic Guibert, Marcel Laubach, Matthias Gehre, Matthieu Volat, Mauro Bartoccelli, Michal Babej, Michel Leblond, Mikko Ruohola, Milan Knížek, Moritz Lipp, Olivier Tribout, Pascal de Bruijn, Pascal Obry, Pedro Côrte-Real, Petr Styblo, Ralf Brown, Richard Hughes, Richard Levitte, Richard Wonka, Robert Bieber, Roman Lebedev, Rostyslav Pidgornyi, Sergey Pavlov, Simon Spannagel, Stuart Henderson, Tatica Leandro, Thomas Pryds, Tobias Ellinghaus, Tom Vijlbrief, Ulrich Pegelow, Victor Lamoine, Wolfgang Goetz, Wyatt Olson et de beaucoup d'autres. darktable est un logiciel libre : vous pouvez le redistribuer ou le modifier selon les termes de la Licence Publique Générale GNU telle que publiée par la Free Software Fundation, soit dans la version 3, soit (à votre choix), dans toute autre version ultérieure. darktable est distribué dans l’espoir qu’il sera utile mais SANS AUCUNE GARANTIE, sans même les garanties implicites de COMMERCIABILITÉ et de CONFORMITÉ à une utilisation particulière.
    [Show full text]
  • Free and Open Source Software
    Free and open source software Copyleft ·Events and Awards ·Free software ·Free Software Definition ·Gratis versus General Libre ·List of free and open source software packages ·Open-source software Operating system AROS ·BSD ·Darwin ·FreeDOS ·GNU ·Haiku ·Inferno ·Linux ·Mach ·MINIX ·OpenSolaris ·Sym families bian ·Plan 9 ·ReactOS Eclipse ·Free Development Pascal ·GCC ·Java ·LLVM ·Lua ·NetBeans ·Open64 ·Perl ·PHP ·Python ·ROSE ·Ruby ·Tcl History GNU ·Haiku ·Linux ·Mozilla (Application Suite ·Firefox ·Thunderbird ) Apache Software Foundation ·Blender Foundation ·Eclipse Foundation ·freedesktop.org ·Free Software Foundation (Europe ·India ·Latin America ) ·FSMI ·GNOME Foundation ·GNU Project ·Google Code ·KDE e.V. ·Linux Organizations Foundation ·Mozilla Foundation ·Open Source Geospatial Foundation ·Open Source Initiative ·SourceForge ·Symbian Foundation ·Xiph.Org Foundation ·XMPP Standards Foundation ·X.Org Foundation Apache ·Artistic ·BSD ·GNU GPL ·GNU LGPL ·ISC ·MIT ·MPL ·Ms-PL/RL ·zlib ·FSF approved Licences licenses License standards Open Source Definition ·The Free Software Definition ·Debian Free Software Guidelines Binary blob ·Digital rights management ·Graphics hardware compatibility ·License proliferation ·Mozilla software rebranding ·Proprietary software ·SCO-Linux Challenges controversies ·Security ·Software patents ·Hardware restrictions ·Trusted Computing ·Viral license Alternative terms ·Community ·Linux distribution ·Forking ·Movement ·Microsoft Open Other topics Specification Promise ·Revolution OS ·Comparison with closed
    [Show full text]
  • Pillow (PIL Fork) Documentation Release 8.3.2
    Pillow (PIL Fork) Documentation Release 8.3.2 Alex Clark Sep 02, 2021 CONTENTS 1 Overview 3 1.1 Installation................................................3 1.2 Handbook................................................ 12 1.3 Reference................................................. 53 1.4 Porting.................................................. 180 1.5 About................................................... 181 1.6 Release Notes............................................... 181 1.7 Deprecations and removals........................................ 234 2 Indices and tables 239 Python Module Index 241 Index 243 i ii Pillow (PIL Fork) Documentation, Release 8.3.2 Pillow is the friendly PIL fork by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors. Pillow for enterprise is available via the Tidelift Subscription. Learn more. CONTENTS 1 Pillow (PIL Fork) Documentation, Release 8.3.2 2 CONTENTS CHAPTER ONE OVERVIEW The Python Imaging Library adds image processing capabilities to your Python interpreter. This library provides extensive file format support, an efficient internal representation, and fairly powerful image pro- cessing capabilities. The core image library is designed for fast access to data stored in a few basic pixel formats. It should provide a solid foundation for a general image processing tool. 1.1 Installation 1.1.1 Warnings Warning: Pillow and PIL cannot co-exist in the same environment. Before installing Pillow, please uninstall PIL. Warning: Pillow >= 1.0 no longer supports
    [Show full text]
  • Well Known NYC Media Company
    Well Known NYC Media Company InVision Assessment PREPARED FOR WELL KNOWN NYC MEDIA COMPANY n Version 2.0 n April 30, 2020 Confidentiality Notice This document contains confidential and proprietary information of CPP Associates and Well Known NYC Media Company, except as noted in this paragraph, may not be shared with any other party. Well Known NYC Media Company may copy or disclose the information contained herein (with the exception of any pricing) as needed for the purpose of providing this information to the end user customer identified in this Assessment Report, provided that any such disclosure of information is accompanied by a requirement to maintain the confidentiality of such information. Except as expressly authorized in the preceding sentence, Well Known NYC Media Company may not copy or disclose without the prior written permission of CPP Associates. Table of Contents Executive Summary ...................................................................................................... 4 1.1 Scope ................................................................................................................ 6 1.2 Network Infrastructure ..................................................................................... 7 1.3 Windows Infrastructure .................................................................................... 8 1.4 Overall Client Risk ........................................................................................... 11 1.5 Servers ..........................................................................................................
    [Show full text]
  • Darktable 3.4 Darktable 3.4 Copyright © 2010-2012 P.H
    darktable 3.4 darktable 3.4 Copyright © 2010-2012 P.H. Andersson Copyright © 2010-2011 Olivier Tribout Copyright © 2012-2018 Ulrich Pegelow Copyright © 2013-2017 Jérémy Rosen The founder of the darktable project is Johannes Hanika. darktable has been developed with major contribution by Aldric Renaudin, Alexander V. Smal, Alexandre Prokoudine, Am- mon Riley, Anders Brander, Andreas Schneider, Andrea Volpato, Andrew Toskin, Antony Dovgal, Artur de Sousa Rocha, Asma AL-Bahanta, Aurélien Pierre, Axel Waggershauser, Báthory Péter, Benoit Brummer, Bernd Steinhauser, Brian Teague, Bruce Guenter, Cherrot Luo, Chris Hodapp, Christian Himpel, Christian Tellefsen, Dan Torop, David Bremner, Dennis Gnad, Dimitrios Psychogios, Dušan Kazik, Eckhart Pedersen, Edgardo Hoszowski, Edouard Gomez, Frédéric Grollier, Gaspard Jankowiak, Ger- mano Massullo, Ger Siemerink, Gianluigi Calcaterra, Gianni Carabelli, Guilherme Brondani Torri, Guillaume Benny, Heiko Bauke, Henrik Andersson, Igor Kuzmin, Ivan Tarozzi, James C. McPherson, Jan Kundrát, Jérémy Rosen, Jean-Sébastien Pédron, Jesper Pedersen, Jochen Schroeder, Johanes Schneider, Johannes Hanika, José Carlos Casimiro, José Carlos Garcia Sogo, Josep V. Moragues, K. Adam Christensen, Kaminsky Andrey, Kanstantsin Shautsou, Karl Mikaelsson, Klaus Post, Loic Guibert, Marcel Laubach, Matjaž Jeran, Matthias Gehre, Matthieu Moy, Matthieu Volat, Maurizio Paglia, Mauro Bartoccelli, Maximilian Tresch- er, Michal Babej, Michel Leblond, Mikko Ruohola, Milan Knížek, Moritz Lipp, Nicolas Belleville, Novy Sawai, Olivier Tribout, Pascal de Bruijn, Pascal Obry, Pedro Côrte-Real, Peter Budai, Petr Styblo, Pierre Lamot, Ralf Brown, Richard Hughes, Richard Levitte, Richard Wonka, Rikard Öxler, Robert Bieber, Robert William Hutton, Roman Lebedev, Rostyslav Pidgornyi, Sergey Pavlov, Shlomi Braitbart, Simon Spannagel, Stefan Hoffmeister, Stefan Löffler, Stefan Schöfegger, Stuart Henderson, Tatica Leandro, Thomas Pryds, Timur I.
    [Show full text]