├── funding.json ├── README.md ├── giveth2-planning.md └── LICENSE /funding.json: -------------------------------------------------------------------------------- 1 | { 2 | "opRetro": { 3 | "projectId": "0xe434930e189c807b137ff0d8e2fa6a95eaa57dde574143a02ca0d7fb31a40bea" 4 | } 5 | } 6 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # giveth-planning 2 | WE'RE MOVING THIS TO NOTION -> https://www.notion.so/giveth/d43ba90865ae430e982ac2eda39e103e?v=8ece43d3a2db4b6191d1bde4056e1f1a 3 | 4 | PLEASE CREATE YOUR COMMS & MARKETING ISSUES THERE FROM NOW ON 5 | 6 | -------------------------------------------------------------------------------- /giveth2-planning.md: -------------------------------------------------------------------------------- 1 | # DEV Call 2 | 3 | [![hackmd-github-sync-badge](https://hackmd.io/Qqhlz_EYQH-J8aXTgeqCWg/badge)](https://hackmd.io/Qqhlz_EYQH-J8aXTgeqCWg) 4 | 5 | 6 | Sunday and Wednesday 17:00 CET (Berlin) // set up as weekly 7 | - Share DEV progress 8 | - GitHub issue cleaning (process `new issues`, look at `in progress` and assign, review `review and QA`, close `done` issues) 9 | - Saturday: Plan weekly sprint (what issues, projection and time commitment) 10 | - Wednesday: Evaluate sprint progress and talk about implementation details and pain points 11 | 12 | ## Notes for DEV CALL 07/02/2021 13 | 14 | ### Updates 15 | James - Migrations for database, fix bugs with metamask donations when logged in with tor.us 16 | Mateo - Changes donation flow. Now checks for way the user is logged in as default and other wallets optional. Some issues with wallets fixed. Network connection indicator. Needs to do still: Event that catches if Metamask is on wrong network. After that will look out for more issues in ZenHub. 17 | Kay - Change landing page content [here](https://raw.githubusercontent.com/Giveth/giveth-2/staging/src/content/giveth.md) 18 | 19 | ### Softlaunch 20 | - We need a way for users to delete campaigns! 21 | - We need to speed up build time. A good way to do this is described in #484 22 | 23 | 24 | ## Notes for DEV CALL 03/02/2021 25 | 26 | ### Updates 27 | 28 | Mateo-metamask and torus integration, made login smoother. currently working on wallet notifications 29 | 30 | James-working on authentication issue and login 31 | 32 | Amin- no real updates 33 | 34 | Mitch- ready for testing 35 | 36 | Lauren- ready for testing 37 | 38 | Forest- orgazational guru 39 | 40 | Kay- merged changes to master, 41 | 42 | Marco- no real updates 43 | 44 | Dani- ready for testing 45 | 46 | 47 | Agenda: 48 | - evaluate last changes 49 | James working on authentication login issue from last broken testing session 50 | 51 | - notes for testers 52 | 53 | use staging.giveth.io this week 54 | We will also soon test v2 on mainnet for soft launch 55 | next week it will be on giveth.io and it will be announced to test there or move giveth1 projects 56 | 57 | user and developers testing needed 58 | 59 | - check "Last before MVP sprint" milestone 60 | - assign and discuss new issues 61 | 62 | https://github.com/Giveth/giveth-2/issues/452 - Mateo,Marco - how to prioritize using the wallet users are logged in as. add a notice above the donate button 63 | 64 | https://github.com/Giveth/giveth-2/issues/386 - James and Kay 65 | 66 | banner for soft launch is done - Mateo 67 | 68 | https://github.com/Giveth/giveth-2/issues/454- Dani - pop up for firsttime users- if a user has been logged in then how do they choose their previous user account. do we have a 'remember me? option'? if you return, you should be logged in. fast follow/ice box 69 | 70 | https://github.com/Giveth/giveth-2/issues/435 - Mateo - fiat onramp, donating crypto still? will it be on the crypto ledger? 71 | can we know and have a transcation i.d.? fiat donations have a fee, and currently we advertise not having fees. fiat fees need clarity that they are not giveth fees 72 | 73 | https://github.com/Giveth/giveth-2/issues/436- James, Kay- graphQL endpoints pants down? currently anyone can run queries. 74 | engineX configurations expert would be helpful 75 | 76 | - LAST SPRINT before soft launch 77 | 78 | we have many issues that do not have anyone assigned, though we have plenty to do. 79 | Whatever is in backlog and progress is good for MVP 80 | bug fixes only now please 81 | 82 | Reminders: 83 | 84 | Need to choose a feature completeness lockdown 85 | Do not use v2 for testing right now, use staging.giveth.io 86 | When we are live on soft launch will need to test mainnet v2 87 | 88 | 89 | Landing page textblock put into Contentful? or Markdown file? 90 | if we use markdown and github we can allow for more editors. Contentful has limited available users. Github also comes with SourceCred ease. 91 | 92 | We use Contentful for the FAQ. if you want to be added to the Contentful profile page, send Kay one Picture and bonus points for some social links 93 | 94 | FAQ needs more help on hackmd. Dani needs to transfer some content from google docs. 95 | 96 | Where is our central note taking space? We are spread between Notion and hackmd 97 | share links to all platforms between them 98 | markdown is handy for wiki, docs, and is connected to Github 99 | 100 | 101 | ## Notes for DEV CALL gaps 31/01/2020 to 03/02/2021 need transfer from Notion? 102 | 103 | ## Notes for DEV CALL 31/01/2020 104 | 105 | ### Updates & Login/Wallet Flow Discussion 106 | Mateo - James implemented a check if user has metamask installed and falls back to tor.us 107 | James - User should not be able to create project before profile is updated. We should change the flow accordingly. If Metamask is not installed it should automatically default to torus sign-in. If Metamask IS installed we should show onboard.js (might be complicated). Alternative - NO MM installed we show Tor.us, when MM installed show selection menu like now. 108 | Dani - Tor.us does have some pitfalls when it comes to that login procedure (i.e. she expected a different social login to use the same wallet but it creates a different one). Another thing - "My Projects" should also contain projects the user donated to. 109 | Willy - Will present it at ETH Denver on Wednesday!! There should be a banner at the top that we are in softlaunch. 110 | 111 | To summarize the rest of the call - we talked a lot about the wallet and login flow and spent some minutes looking at various UX issues. We fixed to softlaunch to giveth.io on Tuesday 02nd February 2021 - ideally 24 hours before Willy presents it at ETH Denver. 112 | 113 | 114 | ## Notes for DEV CALL 27/01/2020 115 | 116 | ### Notes 117 | 118 | James: Refactor of Authentication is done 119 | Mateo: Implement other User public profile view, missing mutation on impact-graph for user account (issue follows) 120 | For Tester: Login, Logout, Refresh, try to break it 121 | 122 | 123 | ## Notes for DEV CALL 24/01/2020 124 | 125 | ### Agenda 126 | - Roadmap and go live tomorrow? 127 | - Authentication refactor - is supernice now but would push softlaunch out for at least one more week 128 | 129 | 130 | ## Notes for DEV CALL 20/01/2020 131 | - State of giveth2 looking good 132 | - some things still to optimize, i.e. gracefully recovering from errors, trying to add ramp.network as FIAT provider 133 | 134 | ## Notes for DEV CALL 10/01/2020 135 | 136 | ### Agenda 137 | 138 | - Torus embed 139 | - support from Torus - domain prefix signing functionality 140 | - Multiple wallets 141 | 142 | ### Notes 143 | 144 | 145 | ## Notes for DEV CALL 30/12/2020 146 | - If Camilo is available he is happy to work on issues. 147 | 148 | 149 | ## Notes for DEV CALL 20/12/2020 150 | 151 | - Mateo mentions problem with creating projects currently 152 | - Circle CI failed to build, Amin was looking at it. Once git credentials were updated the build was working. 153 | - Mateo added lots of visual updates on likes, updates, fixes, address display. Missing alerts, optimization with impact-graph following. 154 | - Requesting for early (internal) user testing and collection of questions for faq. 155 | 156 | 157 | ## Notes for DEV CALL 16/12/2020 158 | 159 | Mateo dropped SSR in favor of client side rendering. Network indicator will show tor.us network (account page). Donations will remember choice of user. 160 | Amin is working on API for currency conversion. Unsure how to secure access at this point. 161 | 162 | ## Notes for DEV CALL 25/11/2020 163 | 164 | 165 | Attending: 166 | 167 | Check ins: 168 | Amin, Mateo, Benjamin, Kay, Mateo, Camilo, WIlly, Griff 169 | 170 | Using hackMD for Notes and agenda instead of google docs. 171 | 172 | Mateo: participating in hackathon 173 | Kay: not much news since wednesday did switch out graphics and names for pages biggest thing on todo list and backend 174 | was very interested in codebase 175 | 176 | Camilo: working with matthew on webflow on fiat flow and project slug no more distractions no more updates 177 | Griff no major updates no distrcations 178 | 179 | Mateo: already downloaded it to computer needs some changes to environment variables. some changes in environment backend to localhost. Mentioned to James that camilo made some changes. Now only need to be a user to make a project. if you comment those lines it will break. it didnt work when they made a PR. 180 | 181 | we are having a token when having a user. 182 | 183 | better when making changes on repo because of sourcecred. Camilo does a lot of work but not sure it's measured somewhere. 184 | 185 | 186 | Camilo: who can make a project and that is supposed to be a token. 187 | 188 | Enviornment variables and API keys we have prod for Stripe. Now we can test doing a real donation and receive it in the SDG impact fund bank account. 189 | 190 | Should we use production keys or development keys? even when using prod keys you can make test transactions. 191 | 192 | Willy: We got bank account enabled. next day Stripe: your account has been closed because of crowdfunding. Willy is back and fourth with Stripe to be reenalbed. 193 | 194 | Not planning for failure yet! 195 | 196 | We have disabled the application. Have no implemented 197 | 198 | Talked to Bryan on Friday about PDF generation, was worried if he made big updates 199 | 200 | Meeting recording: what about using YouTube? 201 | 202 | Griff has someone on UpWork to standardize streaming 203 | 204 | *Ben will talk to Kay about meeting streaming/recording* 205 | 206 | mateo is working on graphql. donate fiat Epic is moved to Review/QA. 207 | 208 | need to set up an issue to make the backend points 209 | 210 | 211 | 212 | 213 | ## Notes for DEV CALL 18/11/2020 214 | 215 | Notes are also on https://docs.google.com/document/d/1EQKAGlxM-xH2hbq3AzE540iaRhF1i84Fnsx-rLf6Ggw/edit?usp=sharing 216 | 217 | #144 donation flow that is almost done after both of those parts are done we should be a qa for the MVP for a basic version. revising all the design after the "my account" is complete and "project details" 218 | #141 authentication is a complete mess 219 | 220 | Kay: 221 | Amin: create page API in gatsby because its a common functionality that's required. 222 | 223 | * need to figure out authentication flow. 224 | * we should design organization first. 225 | * Marko is the best to figure it out. 226 | * 227 | 228 | Search Algolia: plugin with gastby, really good search 229 | 230 | ## Notes for DEV CALL 11/10/2020 231 | * Ben: Organizing dev meetings. Donation executive summary material creation with Dani. Distracted by markets. Intentions listen to updates and take notes. 232 | * Mateo: Excited to have started work on last Friday. Busy with donation flow. Need PDF receipt for fiat donations. Will make issue and ask Marco for design. Donation history is next in line. Intention is to dive fully into things this week. 233 | * Bryan: Working on account page. Intention is to get updated. 234 | * Amin: Pushed tor.us embed. Error when building with Gatsby. Tries to fix. 235 | * Kay: did mostly build stuff set up source cred. maintaining bridges because discord changed some stuff. Still hogging low hanging fruit issues promise to be ready soon. Crazy week. Left some questions in figma for marco and willy and got some responses from Marco some things to decide so will keep adding to questions. Info pages about Giveth which did not change the text. Heavily distracted, intentions are to still follow meeting. 236 | 237 | #31 want to implement search using Minisearch. Assigned to Amin. 238 | #61 Project View Mateo asked Bryan about implementation. Bryan needs to know what to do to generate the slug. Needs to generate projects. Markup in gastby node file. 239 | #120 bryan will investgiate 240 | Kay will build front end info pages like About Us and FAQ from Figma. 241 | 242 | Bryan and Amin are generating pages based on Gatsby files. When you want to create a new page. Gasby has templates you can use so without templates using from a slug to rehydrate. 243 | 244 | Mateo forked the previous Impact Graph repository which has all implementation of stripe. Will try and make a pull request and so will Kay. 245 | 246 | Kay: Please don't push anything yet just create a pull request. 247 | 248 | ## Notes for DEV CALL 07/10/2020 249 | 250 | * Amin: changed Torus wallet to standard wallet. asked user to sign message with private key. popup will be shown 251 | * Kay: do we really want search on the FAQ pages. will do the pixel for vector graphics 252 | * Reoganize ZenHub to correct flow. Bring up ideas in Discord. 253 | * Proposal for work sprints to deliver work. 254 | * Mateo: needs a lot of changes in the backend, make the screen actually synchronized 255 | * 256 | 257 | ## Notes for DEV call 04/10/2020 258 | 259 | * Kay: meeting monday. The issue was Epic editing pages. Most links are already up there. Played with wiki 260 | * Bryan: started project view making more updates to it making some pages generated during deployment. Check latest branches that has fiat credit card 261 | * Mateo: finished most of the stripe payment, only missing a webhook, hoping james would jump in. 262 | * Camilo: 1. Simple flow want to create temporary token 2. Identity of donations now donations are anonymous or require user token 3. Apollo web checking change to apollo express. We should let Camilo and Mateo finish backend. 263 | * Willy: ask James to explain white labeling and organizations. How to create an organization. 264 | 265 | 266 | Post MVP, consider migrating from Gatsby to Next.js so front and backend can be bundled together and whitelabeling can be streamlined. 267 | 268 | 269 | 270 | ## Notes for DEV call of 01/10/2020 271 | * Amin - closed issues related to node gateway. web socket connections were broken. Andre changed config and fixed it. Will handle buttons this week. Questions about mobile view. was occupied this week, needs help with leaderboard. Adding PAN moved to beta and needs to be tested. 272 | * Andre - Adding tokens in beta server. looking for contract address in forwarding address. Need to test "In Progress" issues so it doesnt break system. 273 | * Hadai - question about 1459 button off center. if button is moved to right, button is not in the center. No progress on issue cleanup task. Will implement #1413 tomorrow finally. 274 | * Griff - closed #1459 and made it part of #1376 #1214 moved to sprint backlog because of low priority. 275 | * Benjamin - testing adding PAN to Dapp with Amin. 276 | 277 | ## Notes for DEV Sprint Call of 28/09/2020 278 | - Amin is going to take ownership of the Topia backend, specifically mapping new features in front end to backend. Next step is connecting the project creation flow to the backend. 279 | - Mateo and Camillo are aiming to finish the 'Donate Fiat' flow this week 280 | - New issue: Replace Tor.Us direct auth integration with Tor.us wallet integration 281 | - New design needs: Show projects their donation address in the project creation flow (maybe the high five screen?) Give 'crypto savvy' projects the ability to 'Edit' their donation address. Give 'crypto noobie' projects a path to learn more about their new donation address and how it works. 282 | - Time zones: 283 | - Ben: Virginia (GMT -5) 284 | - Mateo: Columbia (GMT -7) 285 | - Camillo: Columbia (GMT -7) 286 | - Bryan: East Africa (GMT +3) 287 | - Amin: Iran (GMT+3.3) 288 | - Kay: Austria (GMT +2) 289 | 290 | ## Notes for DEV Call of 27/09/2020 291 | - Attending: Kay, Amin, Benjamin (Socretes), Mateo, Willy 292 | - Staging is great again! Login is fixed: staging.giveth.io 293 | - Gatsby handles env variables in a unique way. Kay needs to investigate and will report back. 294 | - Mateo: Made a PR for donation flow earlier in the week. Need access to official account for Stripe Connect. 295 | - Amin: Amin is back! Will be working on some v2 issues this week 296 | - 297 | 298 | ## Notes for DEV Call of 20/09/2020 299 | - We use Stripe Connect Express. Stripe handles KYC. Enables Project bank accounts and accept FIAT donations 300 | - add create_organization mutaion to backend? 301 | - Fiat donations and account management: Organizations might have more than one bank account. Lots of variables to talk about in follow up. 302 | - Camilo created automated stripe customer creation on log-in. Created stripe endpoint that manages communication with stripe and have confirmations, errors about FIAT tranactions. 303 | - Mateo takes care of frontend for Camilo's work 304 | - PRs coming from Mateo for frontend and Camilo for the backend server 305 | --- 306 | ## Notes for DEV Call of 13/09/2020 307 | - All PRs have been approved and merged! 308 | - Amin, Mateo, Bryan: Please test your changes in prod and ensure they are still working as intended 309 | - There is a bug in staging where users cannot sign in. Need to debug this. A request is being made for the $walletaddress and the response is causing an error. 310 | - Next step: finalize project create flow so that projects are saved after creation. Bryan is working on this along with the High Five success page and the Project View page. (https://github.com/Giveth/giveth-2/pull/103) 311 | - Willy worked with Mateo on donate fiat workflow. working with marko on more mockups. Use stripe to simply donate fiat. 312 | - Mateo has a friend who wants to take on some backend development. He is badass. Wants to help us with stuff like graphql integration with stripe. auto creation of market place i.e. 313 | --- 314 | ## Notes for DEV Call of 05/09/2020 315 | - Check out the new staging environment! (h/t @geleeroyale) https://staging.giveth.io/ 316 | - New process for reviewing and merging PRs: feature-branch -> staging -> master 317 | - Mateo was able to replace some PNGs with SVGs. Some of the SVGs were not rendering properly. Mateo will make a PR to update the images that rendered correctly, and Kay will update the remaining images in the future. 318 | - Mateo will make a PR to update the style of the Project Cards. 319 | - Amin completed image upload functionality on the client side. Projects can upload a photo to IPFS in the project creation flow. *Still needs to be implemented in the project creation flow 320 | *We are using pinata's IPFS service for this. This gives us 1GB of storage for free, after that we should pay 321 | - Marko and Willy had a call. Shared doc from this in chat. Talked about settings. Required: Send funds example (should we just let app.tor.us pop up). Can we get the same private key in our dapp that they get in app.tor.us - torus embed could give us required functionality. (Amin explains drawback: behaviour of torus should be considered in our tx. rewrite functionality that use transactions for embed.) 322 | 323 | To-Do 324 | - Amin to create a ticket to move image upload functionality to server side so we're not exposing our pinata/IPFS key. 325 | - Ping Bryan about implementing the pinata image upload functionality in the 326 | - Project creation flow: Need the 'Confirm' and High Five' page along with the publishing the project to the backend 327 | 328 | --- 329 | ## Notes for DEV Call of 30/08/2020 330 | - Kay reviewed Bryan's contribution, did some issue cleaning, deployed new sourcecred (cred.giveth.io), did start code work on localhost 331 | - Bryan's update: Has a complete branch with Create a Project epic (https://github.com/Giveth/giveth-2/tree/dev/create-project-flow-epic). Kay will review and merge so we can test. Final remaining step is to make the call to GraphQL to save the project and fix any bugs. 332 | - Mateo: Call with Willy, private issues so not much progress this week, James accepted backend PR for FIAT donation flow, help invetigate integration for Paypal or similar, SVG transformation is in progress. Will wait for Bryan's PR for SVG (Kay will ping) 333 | - James: Wants to realize staging with Kay, need to schedule call 334 | - Amin: 335 | - Willy: Update board 336 | 337 | To-Do 338 | - Set up the backend for a staging environment for testing new features (https://github.com/Giveth/giveth-2/issues/88) 339 | - Customize weight configurations in cred.giveth.io; Schedule meeting for Giveth 2 members and Hamad to determine optimal weight config. Propose to DAO before merging. 340 | - 341 | --- 342 | ## Notes for DEV Call of 23/08/2020 343 | - Kay is on last stretch of vacation, so assigned issues come next week 344 | - Bryan is making good progress. Needs someone to look through PRs, bug with validation. Will schedule with Kay and Mateo to go through PR. Should be finished by Friday. Awesome! 345 | - Mateo was able to set up project from guides. Solved on frontend and needs help with integration into backend. Needs invite to repo to make PR. Was looking at codebase and has some suggestions. Starting with replacing PNGs with SVGs. 346 | - Amin implemented IPFS image upload. Is done client-side, but should be sent on to backend. 347 | 348 | - To-do: Create an issue to replace PNG illlustrations with vector images (SVGs) 349 | 350 | ### Dev Progress 351 | 352 | --- 353 | ## Notes for DEV Call of 16/08/2020 354 | 355 | ### Dev Progress 356 | - James worked on the GraphQL server, basically ready for MVP 357 | - Amin looked at image uploader services (will implement IPFS service and push within next days) 358 | - Bryan is almost done with create project flow and will issue PR soon 359 | - Kay implemented sourcecred for GitHub and Discord. We need to work on weighting for it to be useful (see https://cred.giveth.io) 360 | - Matteo will take on the Donation Flow epic 361 | --- 362 | ## Notes for DEV Call of 26/07/2020 363 | 364 | - not much progress on frontend this week, more elements for homepage - still not done 365 | - Amin finishes Tor.us embed integration and opened a new PR for @jamespfarrell to review 366 | - Kay will continue working on frontend, Amin will pick an issue to work on (likely project view filtering) 367 | - Gus takes charge of compiling info to guide contributors and development in general across Giveth and The Commons Stack 368 | - Whitelabel versions will be feature-heavy. Currently two different ones are talked about (Panvala and https://gaiaprotection.com/) 369 | --- 370 | ## Giveth2 - technical planning 371 | 372 | ### Frontend Framework 373 | 374 | Which framework do we want to build on. Currently we are using Gatsby, but that decision might be too opinionated for our aplication going forward. We are sure we want to build it on React. 375 | - `gatsbyjs` stick with gatsbyjs for now 376 | - ~~`vercel`~~ 377 | - ~~`create-react-app`~~ + some library for static rendering like [react-snap](https://github.com/stereobooster/react-snap) 378 | 379 | ### Tech stack 380 | What is our full software stack? Should include important dependencies as well. 381 | - `tech stack` 382 | - `Frontend: React-based` 383 | - `State Management: Apollo Client` 384 | - `GraphQL server: Apollo, TypeGraphQL` 385 | - `Blockchain-development: Set of smart contracts? Reuse?` 386 | - `Blockchain-production: xDAI POA sidechain` 387 | - `services` 388 | - `Authentication integration and wallet provider: tor.us` (investigate risks of unseein issues with tor.us for complex usescases like managing campaigns and milestones, talk to tor.us) 389 | - `OAuth provider: google` 390 | - `blockchain query: infura?, thegraph?` - GraphQL stitching and federation 391 | - `devtools` 392 | - `storybook ?` 393 | 394 | ### Data structure and backend(s) 395 | We have multiple pieces of data infrastructure. We should define: 396 | - `data models` 397 | - `db` & `blockchain` -> use database as store for state (postgres ...) -> triggers in database fire off actions to write to blockchain. Makes probably most sense for i.e. campaigns 398 | - `data flow` : User enters data of a project -> we create entry in db -> upload info to ipfs -> return ipfs hash value to user -> user sign transaction with value of ipfs hash 399 | 400 | ### Deployment 401 | Where is code deployed and hosted 402 | - `code hosting: GitHub` 403 | - `frontend & frontend CI: Netlify` 404 | - `backend: digitalocean?` 405 | - `backend CI: ?` 406 | - `smart contracts` 407 | 408 | ### Development 409 | How development is structured and organized 410 | - DevFlow: `figma -> storybook -> develop` 411 | - GitFlow: `feature-branch -> develop -> master` 412 | - Project Management: `GitHub issues` & `Zenhub` & `Trello` 413 | - Issue cleaning: `every 2 weeks?` -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | --------------------------------------------------------------------------------