├── .npmignore ├── .readme-assets ├── grader.JPG ├── wingrader.JPG ├── grader_logo.png └── default binary sizes.JPG ├── work ├── future ├── todo ├── release.notes └── achievements ├── notes └── caveats.md ├── .github └── FUNDING.yml ├── package.json ├── scripts └── bring_grader.sh ├── README.md └── LICENSE /.npmignore: -------------------------------------------------------------------------------- 1 | .readme-assets 2 | notes 3 | work 4 | 5 | -------------------------------------------------------------------------------- /.readme-assets/grader.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/DO-SAY-GO/graderjs/HEAD/.readme-assets/grader.JPG -------------------------------------------------------------------------------- /.readme-assets/wingrader.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/DO-SAY-GO/graderjs/HEAD/.readme-assets/wingrader.JPG -------------------------------------------------------------------------------- /.readme-assets/grader_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/DO-SAY-GO/graderjs/HEAD/.readme-assets/grader_logo.png -------------------------------------------------------------------------------- /.readme-assets/default binary sizes.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/DO-SAY-GO/graderjs/HEAD/.readme-assets/default binary sizes.JPG -------------------------------------------------------------------------------- /work/future: -------------------------------------------------------------------------------- 1 | Icons 2 | - add ability to create dmg and add icon, add ability to create windows icon, and mac icon. 3 | 4 | differentiate from pkg and nexe via: 5 | - support .node imports (binaries natives) 6 | -------------------------------------------------------------------------------- /work/todo: -------------------------------------------------------------------------------- 1 | Priority 2 | - put archivist in this framework. 3 | - improve API based on what I learned from porting and 4 | - write documentation about how to use grader to build cross-platform apps 5 | 6 | Lesser 7 | - implement apiInUI flag 8 | - improve progress . metrics (no clearline just add 1 dot on each turn using stdout.write) 9 | - add sessionIds to old-sessions on every exit path from the app (even before UI launched for example) 10 | - fix it so we ALWAYS (no matter what) delete old sessions 11 | - add security checks on origin for API proxy 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /work/release.notes: -------------------------------------------------------------------------------- 1 | I think it's easier to make it like a create-app or a template repo. 2 | 3 | Because ... 4 | 5 | To have these apps an author needs 2 parts: 6 | 7 | 1) Grader API and code 8 | 2) Build their code into a binary 9 | 10 | And 2 requires 11 | 12 | 3) Correct structure of their code 13 | 14 | There could be a post install script, that sets up 3. 15 | 16 | And also copies all the required build scripts. 17 | 18 | And also sets up their config. 19 | 20 | This is an option. 21 | 22 | --- but 23 | 24 | 25 | I think at the start, it's easier just to make it a template repository. 26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /notes/caveats.md: -------------------------------------------------------------------------------- 1 | # Flags 2 | 3 | ## Localstorage and multiple windows 4 | 5 | If you want localstorage you need to pick persistent session storage. If you do this, you can only have one app window. 6 | 7 | If you want to open multiple app windows, they are all temporary and transient and you cannot rely on local storage. 8 | 9 | ### Why 10 | 11 | This is the case because, Chrome, running with more than one window, and each window having RDP on different ports cannot share the same user data directory. In order to run multiple windows, each window/chrome needs to have its own user data directory. So if you want multiple windows, we need to create them transiently and delete them. If you want persistent localstorage (but hey you can use filesystem since you have node), you must accept one window only. 12 | -------------------------------------------------------------------------------- /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] 4 | patreon: # Replace with a single Patreon username 5 | open_collective: # Replace with a single Open Collective username 6 | ko_fi: # Replace with a single Ko-fi username 7 | tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel 8 | community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry 9 | liberapay: # Replace with a single Liberapay username 10 | issuehunt: # Replace with a single IssueHunt username 11 | otechie: # Replace with a single Otechie username 12 | lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry 13 | custom: https://buy.stripe.com/3cs7tEcC53Yv3zG8xb 14 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "graderjs", 3 | "version": "3.0.0", 4 | "description": "Tool to copy the Grader.JS base repo into the current directory", 5 | "bin": { 6 | "graderjs": "scripts/bring_grader.sh" 7 | }, 8 | "scripts": {}, 9 | "repository": { 10 | "type": "git", 11 | "url": "git+https://github.com/crisdosyago/graderjs.git" 12 | }, 13 | "keywords": [ 14 | "devtools", 15 | "node", 16 | "hybrid", 17 | "desktop", 18 | "template", 19 | "electron", 20 | "sciter", 21 | "gradebr", 22 | "cross-platform apps", 23 | "chromium", 24 | "chrome" 25 | ], 26 | "author": "@dosy", 27 | "license": "AGPL-3.0", 28 | "bugs": { 29 | "url": "https://github.com/crisdosyago/graderjs/issues" 30 | }, 31 | "homepage": "https://github.com/crisdosyago/graderjs#readme", 32 | "dependencies": {}, 33 | "devDependencies": {} 34 | } 35 | -------------------------------------------------------------------------------- /scripts/bring_grader.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | if [ -z "$1" ]; then 4 | echo "Use: graderjs " 5 | exit 1 6 | fi 7 | 8 | set -e 9 | 10 | echo 11 | echo "Making it Grader-ified..." 12 | 13 | mkdir -p $1 14 | 15 | cd $1 16 | 17 | set +e 18 | bash -e < name.txt 46 | 47 | echo 48 | echo "Grader app directory created!" 49 | echo 50 | echo "Make sure you have nvm installed, and also node 14.15.3 (nvm install 14.15.3 will do it)." 51 | echo "Then you can run" 52 | echo "cd ./$1 && ./scripts/compile.sh" 53 | echo "right now to get some binaries." 54 | echo "Or copy your SPA into the ./$1/src/public/ folder (or start editing in there)" 55 | echo "Or if you need more functionality you can also edit ./$1/src/app.js" 56 | echo "to build your own app." 57 | echo "See the docs: https://github.com/crisdosyago/graderjs or open the README.md in this directory" 58 | echo "Happy Grading!" 59 | echo 60 | 61 | -------------------------------------------------------------------------------- /work/achievements: -------------------------------------------------------------------------------- 1 | - verify window control buttons work 2 | - add a build step that zips up our website / app directory 3 | - add the website zip into the nexe build 4 | - write the server.js and website zip to a temp directory 5 | - unzip the website zip 6 | - start the server 7 | - refactor to have app as a launch process for a fatter server. app closes quickly, leaving no trace of console. 8 | - test this on windows and linux (ubuntu vnc) 9 | - clean up code and remove most of it 10 | - Decide how to handle config, names, folders of different apps 11 | - perf: try keeping the chrome profile dir (per app), and experiment with cache dir as temp or persistent. Also try opening chrome earlier and using DevTools if needed as fallback to make it load the UI 12 | - global $HOME/.grader directory for all grader apps, installs and configs 13 | - handle picking a random port that's available 14 | - work out how to delete the session directories on windows 15 | - make it into a great API and clean the code 16 | - ensure all sessions are correctly accounted for (seems at least 1 window will not be saved in old session log, need to work out why) 17 | - create API bridge plumbing! 18 | - remove bugs about adding binding/related code twice 19 | - work out that trying make window controls top bar available (for systems that don't use them, like ubuntu) is actually an error because ubuntu does provide them, and trying to provide on ourselves (using app region drag) doesn't work. But be grateful that I got all the plumbing for the API bridge done! YAY 20 | - implement way to pass back info from service side to UI side (promise resolver account) 21 | - allow setting initial position and size (and get screen size by opening headless chrome window and evaluating screen.width, everytime. We can also use this headless vanguard to provide us other useful properties.) 22 | - improve way to get screen coorindates (faster and less waste, let's try to keep these two browsers using the same session directories) 23 | - get rid of console window opening on browser exit / shutdown process 24 | - implement addHandlers, server and keepConsoleOpen settings (as well as other sketched and unimplemented settings) 25 | - add download_chrome script to pull it in if system doesn't have it 26 | - this can be an npm repo 27 | - call a function {install} and depending on win, nix or osx download the right installer and run it 28 | - multiple windows handling 29 | - fix bug where service doesnt' close after last UI closed (because 'headless' still there) 30 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 |

3 | Windows Grader app screenshot 4 | Ubuntu Linux Grader app screenshot 5 |

6 | 7 | # [:sweat_drops: GRaderJS](https://github.com/crisdosyago/graderjs) ![npm downloads](https://img.shields.io/npm/dt/graderjs?label=npm%20downloads) ![version](https://img.shields.io/npm/v/graderjs?label=version) [![visitors+++](https://hits.seeyoufarm.com/api/count/incr/badge.svg?url=https%3A%2F%2Fgithub.com%2Fc9fe%2Fgraderjs&count_bg=%2379C83D&title_bg=%23555555&icon=&icon_color=%23E7E7E7&title=%28today%2Ftotal%29%20visitors%2B%2B%2B%20since%20Nov%209%202020&edge_flat=false)](https://hits.seeyoufarm.com) 8 | 9 | Turn your full-stack NodeJS application into a downloadable cross-platform binary. Also works for SPAs, or regular web-sites. 10 | 11 | ## Features that work right out of the box 12 | 13 | - Create a downloadable binary for any platform ✔️ 14 | - NodeJS ✔️ 15 | - Chrome DevTools API ✔️ 16 | - GUI in HTML/JavaScript/CSS ✔️ 17 | - BYO front-end framework ✔️ 18 | - BYO back-end framework ✔️ 19 | - A GUI window with OS-default topbar controls that can be dragged, maximized, minimized, resized ✔️ 20 | - A simple API for controlling windows, and interacting with DevTools ✔️ 21 | - GUI window has app title and can have app icon. ✔️ 22 | - ES6 all the latest features (that work in the latest Chrome). ✔️ 23 | - Cross-platform builds (build for everywhere on Linux, or Mac or Windows). ✔️ 24 | 25 | ## Features that don't (yet?) work 26 | 27 | - App binary icons (it's just the NodeJS icon) 💀 28 | - App system tray icons (on Mac, tray icons work on Windows) 💀 29 | - Code signing and associated bona fides that give apps a "passport for safe and unimpeded passage" through your system (it's not built in, but you can sign your own binary, if you have the right setup). 💀 30 | 31 | ## What are apps built with GraderJS, technically? 32 | 33 | A GraderJS app is just a full-stack application written in NodeJS that runs locally on your client's machine. It achieves this by: 34 | 35 | - bundling a NodeJS (for the target platform) and your back-end and front-end source code into the binary. 36 | - on execution the binary: 37 | 1. starts the back-end service 38 | 2. unzips the front-end to a temporary directory 39 | 3. probes the screen to find its dimensions using a silently launched chrome window (and downloads and installs chrome if it is not) 40 | 4. opens an "app view" chrome UI window to display the front-end 41 | 42 | GraderJS apps are un-opinionated. You can code the front and back-end however you like, and all details like persisting state to the client's machine, and other useful things, are left to the app author to figure out themselves, and decide which way they want to go. 43 | 44 | Unlike a regular full-stack app, GraderJS apps: 45 | 46 | 1. Look like a native app and run on the desktop. 47 | 2. Have full access to the system. 48 | 3. Have full access to the Chrome DevTools API to be able to fully utilize the great browser APIs, enabling you to incorporate "browser power" (think, automation of browsers, but that's just a fraction of what's possible) into your app experiences 49 | 50 | ## Details 51 | 52 | Minimal binary is 50MB (Macos, Hello World App, using node v16.16.0, with executable built by pkg). 53 | 54 | 55 | ------------------- 56 | - [Overview](##goggles-graderjs---) 57 | * [Details](#details) 58 | * [Advantages](#advantages) 59 | * [Disadvantages](#disadvantages-or-opportunities-and-opportunities-for-improvement-yes) 60 | * [Grader workflow](#grader-workflow) 61 | * [Extended Workflow](#extended-workflow) 62 | * [Ultimate Workflow](#ultimate-workflow-still-impossible) 63 | * [License](#license) 64 | * [Built with Grader](#built-with-grader) 65 | - [Getting Started](#getting-started) 66 | * [API & Documentation](#api--documentation) 67 | * [Extraordinary Control](#extraordinary-control) 68 | * [NodeJS related](#nodejs-related) 69 | * [App lifecycle](#app-lifecycle) 70 | * [Window related](#window-related) 71 | * [Docketty Docs](#docketty-docs) 72 | * [Questions](#questions) 73 | - [Step by step guide](#step-by-step-guide) 74 | * [Get Started from the Command line](#get-started-from-the-command-line) 75 | * [Get Started from GitHub](#get-started-from-github) 76 | * [Start Building!](#start-building) 77 | * [Start Coding](#start-coding) 78 | - [API](#api) 79 | - [Then build it](#then-build-it) 80 | - [Configuration](#configuration) 81 | - [Screenshots](#screenshots) 82 | - [More](#more) 83 | - [Licensing](#licensing) 84 | - [Related projects](#related-projects) 85 | -------------------- 86 | 87 | ## Advantages 88 | 89 | - Simplicity. Grader is just a web server running on localhost viewed with the user's browser. If they have Chrome installed then you get a proper looking desktop app (thanks to the --app flag), and access to a bunch of cool APIs to control the browser (thanks to remote DevToosl protocol). 90 | - Extensive APIs. Because you have access to Node.JS and, with Chrome, DevTools APIs there's so many things you can do. You can do almost anything. 91 | 92 |

Top

93 | 94 | ## Disadvantages (...or, Opportunities, and Opportunities for Improvement? Yes) 95 | 96 | - New. Undeveloped. Embryonic. Fragile. Untested. Unknown (relatively). 97 | - Requires Chrome to be installed for a great experience (some people don't have it). 98 | - Bundles Node.JS (and packs using upx but the binaries are still bigger than using Tauri or Neutralino). 99 | - API still undeveloped and likely to change. 100 | - Icons (for the binary) don't work (and it's a hard problem). 101 | 102 |

Top

103 | 104 | ## Grader Workflow 105 | 106 | 1. Create a new Grader app 107 | 2. Fill out the sections with your business logic and app specific node 108 | 3. Compile to get cross-platform binaries 109 | 110 |

Top

111 | 112 | ## Extended Workflow 113 | 114 | 4. Code-sign your binaries and upload them to app stores or GitHub releases or your own website. 115 | 116 |

Top

117 | 118 | ## Ultimate Workflow (still impossible) 119 | 120 | 5. Use ~impossible non-existant~ ~(future?)~ packaging tool to bundle each binary in a soothing bath of platform specific app metadata that includes icons and associated weird OS specific coolness to make things truly awesome. 121 | 122 |

Top

123 | 124 | ## License 125 | 126 | Copyright (c) 2020, Dosyago and/or its affiliates. All rights reserved. 127 | 128 | This is a release of Grader, an cross-platform app builder. 129 | 130 | License information can be found in the LICENSE file. 131 | 132 | This software is dual-licensed. For information about commercial licensing, see [Dosyago Commercial License for OEMs, ISVs and VARs](https://github.com/dosyago/dual-licensing). 133 | 134 |

Top

135 | 136 | ## Built with Grader 137 | 138 | - [wingrader](https://github.com/crisdosyago/winrader) - windows 95 cross platform 139 | - [jspaint.exe](https://github.com/crisdosyago/jspaint.exe) - classic paint cross platform 140 | 141 |

Top

142 | 143 | ## Getting Started 144 | 145 | ```sh 146 | npx graderjs my-app 147 | ``` 148 | 149 |

Top

150 | 151 | ### API & Documentation 152 | 153 | Only a couple of API calls, classed into four categories: Protocol, NodeJS, App, Window. 154 | 155 | Read [the API docs](https://github.com/crisdosyago/grader-base) for a detailed usage or see below for an overview. 156 | 157 |

Top

158 | 159 | ### Protocol Control 160 | 161 | Instrument the browser directly with DevTools\*. 162 | 163 | - constrol.send(command, params) 164 | - control.on(eventName, handlerFunction) (also off) 165 | 166 | \**See commands available at [DevTools protocol homepage](https://chromedevtools.github.io/devtools-protocol/tot/)* 167 | 168 |

Top

169 | 170 | ### NodeJS related 171 | 172 | *As normal just use npm to add dependencies and import to use them* 173 | 174 | ### App Lifecycle 175 | 176 | - launch: `go()` 177 | - shutdown: `stop()` 178 | 179 |

Top

180 | 181 | ### Window Related 182 | 183 | - ui.open 184 | - ui.close 185 | - ui.move 186 | - ui.size 187 | - ui.minimize 188 | - ui.maximize 189 | - ui.restore 190 | - ui.fullscreen 191 | - ui.partscreen 192 | - ui.getLayout 193 | - ui.openBlank (*not yet implemented*) 194 | - ui.writePage (*not yet implemented*) 195 | - ui.getScreen 196 | 197 |

Top

198 | 199 | ### Docketty Docs 200 | 201 | Then, read the [API docs](https://github.com/crisdosyago/grader-base/blob/master/README.md) or see below for the Getting Started Goose Guide. 202 | 203 |

Top

204 | 205 | ### Questions 206 | 207 | Open an issue! 208 | 209 |

Top

210 | 211 | ## Step By Step Guide 212 | 213 | ### Get Started from the Command line 214 | 215 | Use npm to get the [Grader.JS tool](https://github.com/crisdosyago/graderjs) to automatically populate your new grader app. 216 | 217 | ```sh 218 | $ npm i -g graderjs@latest 219 | $ graderjs my-new-app 220 | ``` 221 | 222 | Then, read the [API docs](https://github.com/crisdosyago/grader-base/blob/master/README.md) or see below for the Getting Started Goose Guide. 223 | 224 | *Or...* 225 | 226 |

Top

227 | 228 | ### Get Started from GitHub 229 | 230 | Click ["Use This Template"](https://github.com/crisdosyago/grader-base) on the base-repo and you will have a new repo, then clone it to your workspace and `cd` into it, and run: 231 | 232 | ```sh 233 | npm i 234 | ``` 235 | 236 | *Then...* 237 | 238 |

Top

239 | 240 | ### Start Building! 241 | 242 | Read [the API docs](https://github.com/crisdosyago/grader-base), or create yer binaries right away: 243 | 244 | ```sh 245 | ./scripts/compile.sh 246 | ``` 247 | 248 | You now have a GUI app in Node.JS and JavaScript/HTML/CSS. 249 | 250 | And you will have cross-platform binaries available in `/bin` 251 | 252 | (*and also for download from the computer you're on at port 8080.*) 253 | 254 |

Top

255 | 256 | ### Start Coding 257 | 258 | Put your own code into, `src/app.js`: 259 | 260 | **E.g**: 261 | 262 | ```js 263 | import Grader from './index.js'; 264 | 265 | start(); 266 | 267 | async function start() { 268 | await Grader.go(); 269 | } 270 | ``` 271 | 272 | And put your JS/HTML/CSS into, `src/public/index.html`: 273 | 274 | ```html 275 | 276 | Your Cross-Platform App 277 | 296 |

Hello World!

297 |

Meet Grader

298 |

299 | 300 | 301 | 302 | 320 | ``` 321 | 322 | ### API 323 | 324 | Read [the API docs](https://github.com/crisdosyago/grader-base)! 325 | 326 |

Top

327 | 328 | ### Build it 329 | 330 | ```sh 331 | ./scripts/compile.sh 332 | ``` 333 | 334 | You now have a GUI app in Node.JS and JavaScript/HTML/CSS. 335 | 336 | And you will have cross-platform binaries available in `/bin` 337 | 338 | and also for download from the computer you're on at port 8080. 339 | 340 | For more demos see the demos in `src/demos`. 341 | 342 | ### Configuration 343 | 344 | You can configure some options, via the configuration located in `src/config.js`: 345 | 346 | ```js 347 | module.exports = { 348 | name: "MyGraderApp", 349 | entry: "./app.js", 350 | author: { 351 | name: "my name", 352 | url: "https://github.com/my-github-username", 353 | }, 354 | desiredPort: 49666, 355 | version: "0.0.1", 356 | description: "A Beautiful Demonstration", 357 | source: "https://github.com/my-github-username/MyGraderApp", 358 | organization: { 359 | name: "My Org", 360 | url: "https://github.com/my-github-org-name" 361 | }, 362 | apiOrigins: [], // origins allowed to call API from UI (not implemented) 363 | DEBUG: false // switch on debug output when you're ready to debug 364 | } 365 | ``` 366 | 367 |

Top

368 | 369 | ## Screenshots 370 | 371 | ![Windows Grader](https://github.com/crisdosyago/graderjs/raw/master/.readme-assets/wingrader.JPG) 372 | ![Linux Grader](https://github.com/crisdosyago/graderjs/raw/master/.readme-assets/grader.JPG) 373 | 374 |

Top

375 | 376 | ## More 377 | 378 | See [the API docs](https://github.com/crisdosyago/grader-base) for more. Or just read the README.md of the grader app you've just created, it contains the full API docs. You can also take a look at the API code in `src/index.js`. 379 | 380 |

Top

381 | 382 | ## Licensing 383 | 384 | You're free to use this so long as you abide by AGPL-3.0. If you want to use it commercially or don't want this license, you can [purchase an exemption](mailto:cris@dosycorp.com?subject=Grader.JS). 385 | 386 |

Top

387 | 388 | ## Related projects 389 | 390 | See [this list of Electron alternatives](https://github.com/sudhakar3697/electron-alternatives) for more options for cross-platform desktop app developement using web technologies. 391 | 392 |

Top

393 | 394 | ## nerding warnung 395 | 396 | **WARNING:** This project uses Google Chrome to display the UI. Running this will download and install Google Chrome if you don't already have it installed. If you are allergic to Google Chrome, please avoid running or ingesting this coode. 397 | 398 |

Top

399 | 400 | ---------------------- 401 | 402 | 403 | # *Grader.JS!* 404 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | 2 | Licensing Information 3 | 4 | Grader 5 | 6 | =========== 7 | 8 | Introduction 9 | 10 | This License Information contains Dosyago's product license 11 | and other licensing information, including licensing information for 12 | third-party software which may be included in this distribution of 13 | grader-base. 14 | 15 | Last updated: November 2020 16 | 17 | Licensing Information 18 | 19 | This is a release of grader, brought to you by Cris Stringfellow at 20 | Dosyago. This software is released under version 3 of the GNU Affero General 21 | Public License (AGPLv3), as set forth below, with the following 22 | additional permissions: 23 | 24 | This distribution of grader-base is distributed with certain software 25 | (including but not limited to Node.JS) that is licensed under separate 26 | terms, as designated in a particular file or component or in the 27 | license documentation. Without limiting your rights under the AGPLv3, 28 | the authors of grader hereby grant you an additional permission to link 29 | the program and your derivative works with the separately licensed 30 | software that they have included with the program. 31 | 32 | This distribution includes, or will cause the inclusion of, 33 | the grader-base app-builder application 34 | otherwise known as grader-base app-builder. Without limiting 35 | the foregoing grant of rights under the AGPLv3 and additional permission 36 | as to separately licensed software, this app-builder is also subject to 37 | the Universal FOSS Exception, version 1.0, a copy of which is 38 | reproduced below and can also be found along with its FAQ at 39 | http://oss.oracle.com/licenses/universal-foss-exception. 40 | 41 | Copyright (c) 2020, Dosyago and/or its affiliates. 42 | 43 | Election of AGPLv3 44 | 45 | For the avoidance of doubt, except that if any license choice other 46 | than AGPL is available it will apply instead, Dosyago elects to 47 | use only the Affero General Public License version 3 (AGPLv3) at this time for 48 | any software where a choice of AGPL license versions is made available 49 | with the language indicating that AGPLv3 or any later version may be 50 | used, or where a choice of which version of the AGPL is applied is 51 | otherwise unspecified. 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | GNU AFFERO GENERAL PUBLIC LICENSE 60 | Version 3, 19 November 2007 61 | 62 | Copyright (C) 2007 Free Software Foundation, Inc. 63 | Everyone is permitted to copy and distribute verbatim copies 64 | of this license document, but changing it is not allowed. 65 | 66 | Preamble 67 | 68 | The GNU Affero General Public License is a free, copyleft license for 69 | software and other kinds of works, specifically designed to ensure 70 | cooperation with the community in the case of network server software. 71 | 72 | The licenses for most software and other practical works are designed 73 | to take away your freedom to share and change the works. By contrast, 74 | our General Public Licenses are intended to guarantee your freedom to 75 | share and change all versions of a program--to make sure it remains free 76 | software for all its users. 77 | 78 | When we speak of free software, we are referring to freedom, not 79 | price. Our General Public Licenses are designed to make sure that you 80 | have the freedom to distribute copies of free software (and charge for 81 | them if you wish), that you receive source code or can get it if you 82 | want it, that you can change the software or use pieces of it in new 83 | free programs, and that you know you can do these things. 84 | 85 | Developers that use our General Public Licenses protect your rights 86 | with two steps: (1) assert copyright on the software, and (2) offer 87 | you this License which gives you legal permission to copy, distribute 88 | and/or modify the software. 89 | 90 | A secondary benefit of defending all users' freedom is that 91 | improvements made in alternate versions of the program, if they 92 | receive widespread use, become available for other developers to 93 | incorporate. Many developers of free software are heartened and 94 | encouraged by the resulting cooperation. However, in the case of 95 | software used on network servers, this result may fail to come about. 96 | The GNU General Public License permits making a modified version and 97 | letting the public access it on a server without ever releasing its 98 | source code to the public. 99 | 100 | The GNU Affero General Public License is designed specifically to 101 | ensure that, in such cases, the modified source code becomes available 102 | to the community. It requires the operator of a network server to 103 | provide the source code of the modified version running there to the 104 | users of that server. Therefore, public use of a modified version, on 105 | a publicly accessible server, gives the public access to the source 106 | code of the modified version. 107 | 108 | An older license, called the Affero General Public License and 109 | published by Affero, was designed to accomplish similar goals. This is 110 | a different license, not a version of the Affero GPL, but Affero has 111 | released a new version of the Affero GPL which permits relicensing under 112 | this license. 113 | 114 | The precise terms and conditions for copying, distribution and 115 | modification follow. 116 | 117 | TERMS AND CONDITIONS 118 | 119 | 0. Definitions. 120 | 121 | "This License" refers to version 3 of the GNU Affero General Public License. 122 | 123 | "Copyright" also means copyright-like laws that apply to other kinds of 124 | works, such as semiconductor masks. 125 | 126 | "The Program" refers to any copyrightable work licensed under this 127 | License. Each licensee is addressed as "you". "Licensees" and 128 | "recipients" may be individuals or organizations. 129 | 130 | To "modify" a work means to copy from or adapt all or part of the work 131 | in a fashion requiring copyright permission, other than the making of an 132 | exact copy. The resulting work is called a "modified version" of the 133 | earlier work or a work "based on" the earlier work. 134 | 135 | A "covered work" means either the unmodified Program or a work based 136 | on the Program. 137 | 138 | To "propagate" a work means to do anything with it that, without 139 | permission, would make you directly or secondarily liable for 140 | infringement under applicable copyright law, except executing it on a 141 | computer or modifying a private copy. Propagation includes copying, 142 | distribution (with or without modification), making available to the 143 | public, and in some countries other activities as well. 144 | 145 | To "convey" a work means any kind of propagation that enables other 146 | parties to make or receive copies. Mere interaction with a user through 147 | a computer network, with no transfer of a copy, is not conveying. 148 | 149 | An interactive user interface displays "Appropriate Legal Notices" 150 | to the extent that it includes a convenient and prominently visible 151 | feature that (1) displays an appropriate copyright notice, and (2) 152 | tells the user that there is no warranty for the work (except to the 153 | extent that warranties are provided), that licensees may convey the 154 | work under this License, and how to view a copy of this License. If 155 | the interface presents a list of user commands or options, such as a 156 | menu, a prominent item in the list meets this criterion. 157 | 158 | 1. Source Code. 159 | 160 | The "source code" for a work means the preferred form of the work 161 | for making modifications to it. "Object code" means any non-source 162 | form of a work. 163 | 164 | A "Standard Interface" means an interface that either is an official 165 | standard defined by a recognized standards body, or, in the case of 166 | interfaces specified for a particular programming language, one that 167 | is widely used among developers working in that language. 168 | 169 | The "System Libraries" of an executable work include anything, other 170 | than the work as a whole, that (a) is included in the normal form of 171 | packaging a Major Component, but which is not part of that Major 172 | Component, and (b) serves only to enable use of the work with that 173 | Major Component, or to implement a Standard Interface for which an 174 | implementation is available to the public in source code form. A 175 | "Major Component", in this context, means a major essential component 176 | (kernel, window system, and so on) of the specific operating system 177 | (if any) on which the executable work runs, or a compiler used to 178 | produce the work, or an object code interpreter used to run it. 179 | 180 | The "Corresponding Source" for a work in object code form means all 181 | the source code needed to generate, install, and (for an executable 182 | work) run the object code and to modify the work, including scripts to 183 | control those activities. However, it does not include the work's 184 | System Libraries, or general-purpose tools or generally available free 185 | programs which are used unmodified in performing those activities but 186 | which are not part of the work. For example, Corresponding Source 187 | includes interface definition files associated with source files for 188 | the work, and the source code for shared libraries and dynamically 189 | linked subprograms that the work is specifically designed to require, 190 | such as by intimate data communication or control flow between those 191 | subprograms and other parts of the work. 192 | 193 | The Corresponding Source need not include anything that users 194 | can regenerate automatically from other parts of the Corresponding 195 | Source. 196 | 197 | The Corresponding Source for a work in source code form is that 198 | same work. 199 | 200 | 2. Basic Permissions. 201 | 202 | All rights granted under this License are granted for the term of 203 | copyright on the Program, and are irrevocable provided the stated 204 | conditions are met. This License explicitly affirms your unlimited 205 | permission to run the unmodified Program. The output from running a 206 | covered work is covered by this License only if the output, given its 207 | content, constitutes a covered work. This License acknowledges your 208 | rights of fair use or other equivalent, as provided by copyright law. 209 | 210 | You may make, run and propagate covered works that you do not 211 | convey, without conditions so long as your license otherwise remains 212 | in force. You may convey covered works to others for the sole purpose 213 | of having them make modifications exclusively for you, or provide you 214 | with facilities for running those works, provided that you comply with 215 | the terms of this License in conveying all material for which you do 216 | not control copyright. Those thus making or running the covered works 217 | for you must do so exclusively on your behalf, under your direction 218 | and control, on terms that prohibit them from making any copies of 219 | your copyrighted material outside their relationship with you. 220 | 221 | Conveying under any other circumstances is permitted solely under 222 | the conditions stated below. Sublicensing is not allowed; section 10 223 | makes it unnecessary. 224 | 225 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 226 | 227 | No covered work shall be deemed part of an effective technological 228 | measure under any applicable law fulfilling obligations under article 229 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 230 | similar laws prohibiting or restricting circumvention of such 231 | measures. 232 | 233 | When you convey a covered work, you waive any legal power to forbid 234 | circumvention of technological measures to the extent such circumvention 235 | is effected by exercising rights under this License with respect to 236 | the covered work, and you disclaim any intention to limit operation or 237 | modification of the work as a means of enforcing, against the work's 238 | users, your or third parties' legal rights to forbid circumvention of 239 | technological measures. 240 | 241 | 4. Conveying Verbatim Copies. 242 | 243 | You may convey verbatim copies of the Program's source code as you 244 | receive it, in any medium, provided that you conspicuously and 245 | appropriately publish on each copy an appropriate copyright notice; 246 | keep intact all notices stating that this License and any 247 | non-permissive terms added in accord with section 7 apply to the code; 248 | keep intact all notices of the absence of any warranty; and give all 249 | recipients a copy of this License along with the Program. 250 | 251 | You may charge any price or no price for each copy that you convey, 252 | and you may offer support or warranty protection for a fee. 253 | 254 | 5. Conveying Modified Source Versions. 255 | 256 | You may convey a work based on the Program, or the modifications to 257 | produce it from the Program, in the form of source code under the 258 | terms of section 4, provided that you also meet all of these conditions: 259 | 260 | a) The work must carry prominent notices stating that you modified 261 | it, and giving a relevant date. 262 | 263 | b) The work must carry prominent notices stating that it is 264 | released under this License and any conditions added under section 265 | 7. This requirement modifies the requirement in section 4 to 266 | "keep intact all notices". 267 | 268 | c) You must license the entire work, as a whole, under this 269 | License to anyone who comes into possession of a copy. This 270 | License will therefore apply, along with any applicable section 7 271 | additional terms, to the whole of the work, and all its parts, 272 | regardless of how they are packaged. This License gives no 273 | permission to license the work in any other way, but it does not 274 | invalidate such permission if you have separately received it. 275 | 276 | d) If the work has interactive user interfaces, each must display 277 | Appropriate Legal Notices; however, if the Program has interactive 278 | interfaces that do not display Appropriate Legal Notices, your 279 | work need not make them do so. 280 | 281 | A compilation of a covered work with other separate and independent 282 | works, which are not by their nature extensions of the covered work, 283 | and which are not combined with it such as to form a larger program, 284 | in or on a volume of a storage or distribution medium, is called an 285 | "aggregate" if the compilation and its resulting copyright are not 286 | used to limit the access or legal rights of the compilation's users 287 | beyond what the individual works permit. Inclusion of a covered work 288 | in an aggregate does not cause this License to apply to the other 289 | parts of the aggregate. 290 | 291 | 6. Conveying Non-Source Forms. 292 | 293 | You may convey a covered work in object code form under the terms 294 | of sections 4 and 5, provided that you also convey the 295 | machine-readable Corresponding Source under the terms of this License, 296 | in one of these ways: 297 | 298 | a) Convey the object code in, or embodied in, a physical product 299 | (including a physical distribution medium), accompanied by the 300 | Corresponding Source fixed on a durable physical medium 301 | customarily used for software interchange. 302 | 303 | b) Convey the object code in, or embodied in, a physical product 304 | (including a physical distribution medium), accompanied by a 305 | written offer, valid for at least three years and valid for as 306 | long as you offer spare parts or customer support for that product 307 | model, to give anyone who possesses the object code either (1) a 308 | copy of the Corresponding Source for all the software in the 309 | product that is covered by this License, on a durable physical 310 | medium customarily used for software interchange, for a price no 311 | more than your reasonable cost of physically performing this 312 | conveying of source, or (2) access to copy the 313 | Corresponding Source from a network server at no charge. 314 | 315 | c) Convey individual copies of the object code with a copy of the 316 | written offer to provide the Corresponding Source. This 317 | alternative is allowed only occasionally and noncommercially, and 318 | only if you received the object code with such an offer, in accord 319 | with subsection 6b. 320 | 321 | d) Convey the object code by offering access from a designated 322 | place (gratis or for a charge), and offer equivalent access to the 323 | Corresponding Source in the same way through the same place at no 324 | further charge. You need not require recipients to copy the 325 | Corresponding Source along with the object code. If the place to 326 | copy the object code is a network server, the Corresponding Source 327 | may be on a different server (operated by you or a third party) 328 | that supports equivalent copying facilities, provided you maintain 329 | clear directions next to the object code saying where to find the 330 | Corresponding Source. Regardless of what server hosts the 331 | Corresponding Source, you remain obligated to ensure that it is 332 | available for as long as needed to satisfy these requirements. 333 | 334 | e) Convey the object code using peer-to-peer transmission, provided 335 | you inform other peers where the object code and Corresponding 336 | Source of the work are being offered to the general public at no 337 | charge under subsection 6d. 338 | 339 | A separable portion of the object code, whose source code is excluded 340 | from the Corresponding Source as a System Library, need not be 341 | included in conveying the object code work. 342 | 343 | A "User Product" is either (1) a "consumer product", which means any 344 | tangible personal property which is normally used for personal, family, 345 | or household purposes, or (2) anything designed or sold for incorporation 346 | into a dwelling. In determining whether a product is a consumer product, 347 | doubtful cases shall be resolved in favor of coverage. For a particular 348 | product received by a particular user, "normally used" refers to a 349 | typical or common use of that class of product, regardless of the status 350 | of the particular user or of the way in which the particular user 351 | actually uses, or expects or is expected to use, the product. A product 352 | is a consumer product regardless of whether the product has substantial 353 | commercial, industrial or non-consumer uses, unless such uses represent 354 | the only significant mode of use of the product. 355 | 356 | "Installation Information" for a User Product means any methods, 357 | procedures, authorization keys, or other information required to install 358 | and execute modified versions of a covered work in that User Product from 359 | a modified version of its Corresponding Source. The information must 360 | suffice to ensure that the continued functioning of the modified object 361 | code is in no case prevented or interfered with solely because 362 | modification has been made. 363 | 364 | If you convey an object code work under this section in, or with, or 365 | specifically for use in, a User Product, and the conveying occurs as 366 | part of a transaction in which the right of possession and use of the 367 | User Product is transferred to the recipient in perpetuity or for a 368 | fixed term (regardless of how the transaction is characterized), the 369 | Corresponding Source conveyed under this section must be accompanied 370 | by the Installation Information. But this requirement does not apply 371 | if neither you nor any third party retains the ability to install 372 | modified object code on the User Product (for example, the work has 373 | been installed in ROM). 374 | 375 | The requirement to provide Installation Information does not include a 376 | requirement to continue to provide support service, warranty, or updates 377 | for a work that has been modified or installed by the recipient, or for 378 | the User Product in which it has been modified or installed. Access to a 379 | network may be denied when the modification itself materially and 380 | adversely affects the operation of the network or violates the rules and 381 | protocols for communication across the network. 382 | 383 | Corresponding Source conveyed, and Installation Information provided, 384 | in accord with this section must be in a format that is publicly 385 | documented (and with an implementation available to the public in 386 | source code form), and must require no special password or key for 387 | unpacking, reading or copying. 388 | 389 | 7. Additional Terms. 390 | 391 | "Additional permissions" are terms that supplement the terms of this 392 | License by making exceptions from one or more of its conditions. 393 | Additional permissions that are applicable to the entire Program shall 394 | be treated as though they were included in this License, to the extent 395 | that they are valid under applicable law. If additional permissions 396 | apply only to part of the Program, that part may be used separately 397 | under those permissions, but the entire Program remains governed by 398 | this License without regard to the additional permissions. 399 | 400 | When you convey a copy of a covered work, you may at your option 401 | remove any additional permissions from that copy, or from any part of 402 | it. (Additional permissions may be written to require their own 403 | removal in certain cases when you modify the work.) You may place 404 | additional permissions on material, added by you to a covered work, 405 | for which you have or can give appropriate copyright permission. 406 | 407 | Notwithstanding any other provision of this License, for material you 408 | add to a covered work, you may (if authorized by the copyright holders of 409 | that material) supplement the terms of this License with terms: 410 | 411 | a) Disclaiming warranty or limiting liability differently from the 412 | terms of sections 15 and 16 of this License; or 413 | 414 | b) Requiring preservation of specified reasonable legal notices or 415 | author attributions in that material or in the Appropriate Legal 416 | Notices displayed by works containing it; or 417 | 418 | c) Prohibiting misrepresentation of the origin of that material, or 419 | requiring that modified versions of such material be marked in 420 | reasonable ways as different from the original version; or 421 | 422 | d) Limiting the use for publicity purposes of names of licensors or 423 | authors of the material; or 424 | 425 | e) Declining to grant rights under trademark law for use of some 426 | trade names, trademarks, or service marks; or 427 | 428 | f) Requiring indemnification of licensors and authors of that 429 | material by anyone who conveys the material (or modified versions of 430 | it) with contractual assumptions of liability to the recipient, for 431 | any liability that these contractual assumptions directly impose on 432 | those licensors and authors. 433 | 434 | All other non-permissive additional terms are considered "further 435 | restrictions" within the meaning of section 10. If the Program as you 436 | received it, or any part of it, contains a notice stating that it is 437 | governed by this License along with a term that is a further 438 | restriction, you may remove that term. If a license document contains 439 | a further restriction but permits relicensing or conveying under this 440 | License, you may add to a covered work material governed by the terms 441 | of that license document, provided that the further restriction does 442 | not survive such relicensing or conveying. 443 | 444 | If you add terms to a covered work in accord with this section, you 445 | must place, in the relevant source files, a statement of the 446 | additional terms that apply to those files, or a notice indicating 447 | where to find the applicable terms. 448 | 449 | Additional terms, permissive or non-permissive, may be stated in the 450 | form of a separately written license, or stated as exceptions; 451 | the above requirements apply either way. 452 | 453 | 8. Termination. 454 | 455 | You may not propagate or modify a covered work except as expressly 456 | provided under this License. Any attempt otherwise to propagate or 457 | modify it is void, and will automatically terminate your rights under 458 | this License (including any patent licenses granted under the third 459 | paragraph of section 11). 460 | 461 | However, if you cease all violation of this License, then your 462 | license from a particular copyright holder is reinstated (a) 463 | provisionally, unless and until the copyright holder explicitly and 464 | finally terminates your license, and (b) permanently, if the copyright 465 | holder fails to notify you of the violation by some reasonable means 466 | prior to 60 days after the cessation. 467 | 468 | Moreover, your license from a particular copyright holder is 469 | reinstated permanently if the copyright holder notifies you of the 470 | violation by some reasonable means, this is the first time you have 471 | received notice of violation of this License (for any work) from that 472 | copyright holder, and you cure the violation prior to 30 days after 473 | your receipt of the notice. 474 | 475 | Termination of your rights under this section does not terminate the 476 | licenses of parties who have received copies or rights from you under 477 | this License. If your rights have been terminated and not permanently 478 | reinstated, you do not qualify to receive new licenses for the same 479 | material under section 10. 480 | 481 | 9. Acceptance Not Required for Having Copies. 482 | 483 | You are not required to accept this License in order to receive or 484 | run a copy of the Program. Ancillary propagation of a covered work 485 | occurring solely as a consequence of using peer-to-peer transmission 486 | to receive a copy likewise does not require acceptance. However, 487 | nothing other than this License grants you permission to propagate or 488 | modify any covered work. These actions infringe copyright if you do 489 | not accept this License. Therefore, by modifying or propagating a 490 | covered work, you indicate your acceptance of this License to do so. 491 | 492 | 10. Automatic Licensing of Downstream Recipients. 493 | 494 | Each time you convey a covered work, the recipient automatically 495 | receives a license from the original licensors, to run, modify and 496 | propagate that work, subject to this License. You are not responsible 497 | for enforcing compliance by third parties with this License. 498 | 499 | An "entity transaction" is a transaction transferring control of an 500 | organization, or substantially all assets of one, or subdividing an 501 | organization, or merging organizations. If propagation of a covered 502 | work results from an entity transaction, each party to that 503 | transaction who receives a copy of the work also receives whatever 504 | licenses to the work the party's predecessor in interest had or could 505 | give under the previous paragraph, plus a right to possession of the 506 | Corresponding Source of the work from the predecessor in interest, if 507 | the predecessor has it or can get it with reasonable efforts. 508 | 509 | You may not impose any further restrictions on the exercise of the 510 | rights granted or affirmed under this License. For example, you may 511 | not impose a license fee, royalty, or other charge for exercise of 512 | rights granted under this License, and you may not initiate litigation 513 | (including a cross-claim or counterclaim in a lawsuit) alleging that 514 | any patent claim is infringed by making, using, selling, offering for 515 | sale, or importing the Program or any portion of it. 516 | 517 | 11. Patents. 518 | 519 | A "contributor" is a copyright holder who authorizes use under this 520 | License of the Program or a work on which the Program is based. The 521 | work thus licensed is called the contributor's "contributor version". 522 | 523 | A contributor's "essential patent claims" are all patent claims 524 | owned or controlled by the contributor, whether already acquired or 525 | hereafter acquired, that would be infringed by some manner, permitted 526 | by this License, of making, using, or selling its contributor version, 527 | but do not include claims that would be infringed only as a 528 | consequence of further modification of the contributor version. For 529 | purposes of this definition, "control" includes the right to grant 530 | patent sublicenses in a manner consistent with the requirements of 531 | this License. 532 | 533 | Each contributor grants you a non-exclusive, worldwide, royalty-free 534 | patent license under the contributor's essential patent claims, to 535 | make, use, sell, offer for sale, import and otherwise run, modify and 536 | propagate the contents of its contributor version. 537 | 538 | In the following three paragraphs, a "patent license" is any express 539 | agreement or commitment, however denominated, not to enforce a patent 540 | (such as an express permission to practice a patent or covenant not to 541 | sue for patent infringement). To "grant" such a patent license to a 542 | party means to make such an agreement or commitment not to enforce a 543 | patent against the party. 544 | 545 | If you convey a covered work, knowingly relying on a patent license, 546 | and the Corresponding Source of the work is not available for anyone 547 | to copy, free of charge and under the terms of this License, through a 548 | publicly available network server or other readily accessible means, 549 | then you must either (1) cause the Corresponding Source to be so 550 | available, or (2) arrange to deprive yourself of the benefit of the 551 | patent license for this particular work, or (3) arrange, in a manner 552 | consistent with the requirements of this License, to extend the patent 553 | license to downstream recipients. "Knowingly relying" means you have 554 | actual knowledge that, but for the patent license, your conveying the 555 | covered work in a country, or your recipient's use of the covered work 556 | in a country, would infringe one or more identifiable patents in that 557 | country that you have reason to believe are valid. 558 | 559 | If, pursuant to or in connection with a single transaction or 560 | arrangement, you convey, or propagate by procuring conveyance of, a 561 | covered work, and grant a patent license to some of the parties 562 | receiving the covered work authorizing them to use, propagate, modify 563 | or convey a specific copy of the covered work, then the patent license 564 | you grant is automatically extended to all recipients of the covered 565 | work and works based on it. 566 | 567 | A patent license is "discriminatory" if it does not include within 568 | the scope of its coverage, prohibits the exercise of, or is 569 | conditioned on the non-exercise of one or more of the rights that are 570 | specifically granted under this License. You may not convey a covered 571 | work if you are a party to an arrangement with a third party that is 572 | in the business of distributing software, under which you make payment 573 | to the third party based on the extent of your activity of conveying 574 | the work, and under which the third party grants, to any of the 575 | parties who would receive the covered work from you, a discriminatory 576 | patent license (a) in connection with copies of the covered work 577 | conveyed by you (or copies made from those copies), or (b) primarily 578 | for and in connection with specific products or compilations that 579 | contain the covered work, unless you entered into that arrangement, 580 | or that patent license was granted, prior to 28 March 2007. 581 | 582 | Nothing in this License shall be construed as excluding or limiting 583 | any implied license or other defenses to infringement that may 584 | otherwise be available to you under applicable patent law. 585 | 586 | 12. No Surrender of Others' Freedom. 587 | 588 | If conditions are imposed on you (whether by court order, agreement or 589 | otherwise) that contradict the conditions of this License, they do not 590 | excuse you from the conditions of this License. If you cannot convey a 591 | covered work so as to satisfy simultaneously your obligations under this 592 | License and any other pertinent obligations, then as a consequence you may 593 | not convey it at all. For example, if you agree to terms that obligate you 594 | to collect a royalty for further conveying from those to whom you convey 595 | the Program, the only way you could satisfy both those terms and this 596 | License would be to refrain entirely from conveying the Program. 597 | 598 | 13. Remote Network Interaction; Use with the GNU General Public License. 599 | 600 | Notwithstanding any other provision of this License, if you modify the 601 | Program, your modified version must prominently offer all users 602 | interacting with it remotely through a computer network (if your version 603 | supports such interaction) an opportunity to receive the Corresponding 604 | Source of your version by providing access to the Corresponding Source 605 | from a network server at no charge, through some standard or customary 606 | means of facilitating copying of software. This Corresponding Source 607 | shall include the Corresponding Source for any work covered by version 3 608 | of the GNU General Public License that is incorporated pursuant to the 609 | following paragraph. 610 | 611 | Notwithstanding any other provision of this License, you have 612 | permission to link or combine any covered work with a work licensed 613 | under version 3 of the GNU General Public License into a single 614 | combined work, and to convey the resulting work. The terms of this 615 | License will continue to apply to the part which is the covered work, 616 | but the work with which it is combined will remain governed by version 617 | 3 of the GNU General Public License. 618 | 619 | 14. Revised Versions of this License. 620 | 621 | The Free Software Foundation may publish revised and/or new versions of 622 | the GNU Affero General Public License from time to time. Such new versions 623 | will be similar in spirit to the present version, but may differ in detail to 624 | address new problems or concerns. 625 | 626 | Each version is given a distinguishing version number. If the 627 | Program specifies that a certain numbered version of the GNU Affero General 628 | Public License "or any later version" applies to it, you have the 629 | option of following the terms and conditions either of that numbered 630 | version or of any later version published by the Free Software 631 | Foundation. If the Program does not specify a version number of the 632 | GNU Affero General Public License, you may choose any version ever published 633 | by the Free Software Foundation. 634 | 635 | If the Program specifies that a proxy can decide which future 636 | versions of the GNU Affero General Public License can be used, that proxy's 637 | public statement of acceptance of a version permanently authorizes you 638 | to choose that version for the Program. 639 | 640 | Later license versions may give you additional or different 641 | permissions. However, no additional obligations are imposed on any 642 | author or copyright holder as a result of your choosing to follow a 643 | later version. 644 | 645 | 15. Disclaimer of Warranty. 646 | 647 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 648 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 649 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 650 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 651 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 652 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 653 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 654 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 655 | 656 | 16. Limitation of Liability. 657 | 658 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 659 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 660 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 661 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 662 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 663 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 664 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 665 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 666 | SUCH DAMAGES. 667 | 668 | 17. Interpretation of Sections 15 and 16. 669 | 670 | If the disclaimer of warranty and limitation of liability provided 671 | above cannot be given local legal effect according to their terms, 672 | reviewing courts shall apply local law that most closely approximates 673 | an absolute waiver of all civil liability in connection with the 674 | Program, unless a warranty or assumption of liability accompanies a 675 | copy of the Program in return for a fee. 676 | 677 | END OF TERMS AND CONDITIONS 678 | 679 | How to Apply These Terms to Your New Programs 680 | 681 | If you develop a new program, and you want it to be of the greatest 682 | possible use to the public, the best way to achieve this is to make it 683 | free software which everyone can redistribute and change under these terms. 684 | 685 | To do so, attach the following notices to the program. It is safest 686 | to attach them to the start of each source file to most effectively 687 | state the exclusion of warranty; and each file should have at least 688 | the "copyright" line and a pointer to where the full notice is found. 689 | 690 | 691 | Copyright (C) 692 | 693 | This program is free software: you can redistribute it and/or modify 694 | it under the terms of the GNU Affero General Public License as published 695 | by the Free Software Foundation, either version 3 of the License, or 696 | (at your option) any later version. 697 | 698 | This program is distributed in the hope that it will be useful, 699 | but WITHOUT ANY WARRANTY; without even the implied warranty of 700 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 701 | GNU Affero General Public License for more details. 702 | 703 | You should have received a copy of the GNU Affero General Public License 704 | along with this program. If not, see . 705 | 706 | Also add information on how to contact you by electronic and paper mail. 707 | 708 | If your software can interact with users remotely through a computer 709 | network, you should also make sure that it provides a way for users to 710 | get its source. For example, if your program is a web application, its 711 | interface could display a "Source" link that leads users to an archive 712 | of the code. There are many ways you could offer source, and different 713 | solutions will be better for different programs; see section 13 for the 714 | specific requirements. 715 | 716 | You should also get your employer (if you work as a programmer) or school, 717 | if any, to sign a "copyright disclaimer" for the program, if necessary. 718 | For more information on this, and how to apply and follow the GNU AGPL, see 719 | . 720 | 721 | ================================= 722 | 723 | The Universal FOSS Exception, Version 1.0 724 | 725 | In addition to the rights set forth in the other license(s) included in 726 | the distribution for this software, data, and/or documentation 727 | (collectively the "Software", and such licenses collectively with this 728 | additional permission the "Software License"), the copyright holders 729 | wish to facilitate interoperability with other software, data, and/or 730 | documentation distributed with complete corresponding source under a 731 | license that is OSI-approved and/or categorized by the FSF as free 732 | (collectively "Other FOSS"). We therefore hereby grant the following 733 | additional permission with respect to the use and distribution of the 734 | Software with Other FOSS, and the constants, function signatures, data 735 | structures and other invocation methods used to run or interact with 736 | each of them (as to each, such software's "Interfaces"): 737 | i. The Software's Interfaces may, to the extent permitted by the 738 | license of the Other FOSS, be copied into, used and distributed in 739 | the Other FOSS in order to enable interoperability, without 740 | requiring a change to the license of the Other FOSS other than as 741 | to any Interfaces of the Software embedded therein. The Software's 742 | Interfaces remain at all times under the Software License, 743 | including without limitation as used in the Other FOSS (which upon 744 | any such use also then contains a portion of the Software under the 745 | Software License). 746 | ii. The Other FOSS's Interfaces may, to the extent permitted by the 747 | license of the Other FOSS, be copied into, used and distributed in 748 | the Software in order to enable interoperability, without requiring 749 | that such Interfaces be licensed under the terms of the Software 750 | License or otherwise altering their original terms, if this does 751 | not require any portion of the Software other than such Interfaces 752 | to be licensed under the terms other than the Software License. 753 | iii. If only Interfaces and no other code is copied between the 754 | Software and the Other FOSS in either direction, the use and/or 755 | distribution of the Software with the Other FOSS shall not be 756 | deemed to require that the Other FOSS be licensed under the license 757 | of the Software, other than as to any Interfaces of the Software 758 | copied into the Other FOSS. This includes, by way of example and 759 | without limitation, statically or dynamically linking the Software 760 | together with Other FOSS after enabling interoperability using the 761 | Interfaces of one or both, and distributing the resulting 762 | combination under different licenses for the respective portions 763 | thereof. For avoidance of doubt, a license which is OSI-approved or 764 | categorized by the FSF as free, includes, for the purpose of this 765 | permission, such licenses with additional permissions, and any 766 | license that has previously been so approved or categorized as 767 | free, even if now deprecated or otherwise no longer recognized as 768 | approved or free. Nothing in this additional permission grants any 769 | right to distribute any portion of the Software on terms other than 770 | those of the Software License or grants any additional permission 771 | of any kind for use or distribution of the Software in conjunction 772 | with software other than Other FOSS. 773 | 774 | ===================== 775 | --------------------------------------------------------------------------------