jekyll-avatar-0.7.0/0000755000004100000410000000000013524775746014340 5ustar www-datawww-datajekyll-avatar-0.7.0/docs/0000755000004100000410000000000013524775746015270 5ustar www-datawww-datajekyll-avatar-0.7.0/docs/CODE_OF_CONDUCT.md0000644000004100000410000000621313524775746020071 0ustar www-datawww-data# Contributor Covenant Code of Conduct ## Our Pledge In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. ## Our Standards Examples of behavior that contributes to creating a positive environment include: * Using welcoming and inclusive language * Being respectful of differing viewpoints and experiences * Gracefully accepting constructive criticism * Focusing on what is best for the community * Showing empathy towards other community members Examples of unacceptable behavior by participants include: * The use of sexualized language or imagery and unwelcome sexual attention or advances * Trolling, insulting/derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or electronic address, without explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Our Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. ## Scope This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at ben@balter.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] [homepage]: http://contributor-covenant.org [version]: http://contributor-covenant.org/version/1/4/ jekyll-avatar-0.7.0/docs/CONTRIBUTING.md0000644000004100000410000001315013524775746017521 0ustar www-datawww-data# Contributing to Jekyll Avatar Hi there! We're thrilled that you'd like to contribute to Jekyll Avatar. Your help is essential for keeping it great. Jekyll Avatar is an open source project supported by the efforts of an entire community and built one contribution at a time by users like you. We'd love for you to get involved. Whatever your level of skill or however much time you can give, your contribution is greatly appreciated. There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests, helping other users by commenting on issues, or writing code which can be incorporated into Jekyll Avatar itself. Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests. ## How to report a bug Think you found a bug? Please check [the list of open issues](https://github.com/benbalter/jekyll-avatar/issues) to see if your bug has already been reported. If it hasn't please [submit a new issue](https://github.com/benbalter/jekyll-avatar/issues/new). Here are a few tips for writing *great* bug reports: * Describe the specific problem (e.g., "widget doesn't turn clockwise" versus "getting an error") * Include the steps to reproduce the bug, what you expected to happen, and what happened instead * Check that you are using the latest version of the project and its dependencies * Include what version of the project your using, as well as any relevant dependencies * Only include one bug per issue. If you have discovered two bugs, please file two issues * Include screenshots or screencasts whenever possible * Even if you don't know how to fix the bug, including a failing test may help others track it down **If you find a security vulnerability, do not open an issue. Please email ben@balter.com instead.** ## How to suggest a feature or enhancement If you find yourself wishing for a feature that doesn't exist in Jekyll Avatar, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that Jekyll Avatar has today have been added because our users saw the need. Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and goals of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible, including describing the problem you're trying to solve. [Open an issue](https://github.com/benbalter/jekyll-avatar/issues/new) which describes the feature you would like to see, why you want it, how it should work, etc. ## Your first contribution We'd love for you to contribute to the project. Unsure where to begin contributing to Jekyll Avatar? You can start by looking through these "good first issue" and "help wanted" issues: * [Good first issues](https://github.com/benbalter/jekyll-avatar/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) - issues which should only require a few lines of code and a test or two * [Help wanted issues](https://github.com/benbalter/jekyll-avatar/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) - issues which may be a bit more involved, but are specifically seeking community contributions *p.s. Feel free to ask for help; everyone is a beginner at first* :smiley_cat: ## How to propose changes Here's a few general guidelines for proposing changes: * If you are changing any user-facing functionality, please be sure to update the documentation * If you are adding a new behavior or changing an existing behavior, please be sure to update the corresponding test(s) * Each pull request should implement **one** feature or bug fix. If you want to add or fix more than one thing, submit more than one pull request * Do not commit changes to files that are irrelevant to your feature or bug fix * Don't bump the version number in your pull request (it will be bumped prior to release) * Write [a good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) At a high level, [the process for proposing changes](https://guides.github.com/introduction/flow/) is: 1. [Fork](https://github.com/benbalter/jekyll-avatar/fork) and clone the project 2. Configure and install the dependencies: `script/bootstrap` 3. Make sure the tests pass on your machine: `script/cibuild` 4. Create a descriptively named branch: `git checkout -b my-branch-name` 5. Make your change, add tests and documentation, and make sure the tests still pass 6. Push to your fork and [submit a pull request](https://github.com/benbalter/jekyll-avatar/compare) describing your change 7. Pat your self on the back and wait for your pull request to be reviewed and merged **Interesting in submitting your first Pull Request?** It's easy! You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) ## Bootstrapping your local development environment `script/bootstrap` ## Running tests `script/cibuild` ## Code of conduct This project is governed by [the Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. ## Additional Resources * [Contributing to Open Source on GitHub](https://guides.github.com/activities/contributing-to-open-source/) * [Using Pull Requests](https://help.github.com/articles/using-pull-requests/) * [GitHub Help](https://help.github.com) jekyll-avatar-0.7.0/docs/SECURITY.md0000644000004100000410000000015513524775746017062 0ustar www-datawww-data# Security Policy To report a security vulnerability, please email [ben@balter.com](mailto:ben@balter.com). jekyll-avatar-0.7.0/.travis.yml0000644000004100000410000000023213524775746016446 0ustar www-datawww-datalanguage: ruby rvm: - 2.4 cache: bundler script: script/cibuild env: matrix: - JEKYLL_VERSION="~> 3.0" - JEKYLL_VERSION=">= 4.0.0.pre.alpha1" jekyll-avatar-0.7.0/jekyll-avatar.gemspec0000644000004100000410000000202113524775746020446 0ustar www-datawww-data# frozen_string_literal: true lib = File.expand_path("../lib", __FILE__) $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib) require "jekyll-avatar/version" Gem::Specification.new do |spec| spec.name = "jekyll-avatar" spec.version = Jekyll::Avatar::VERSION spec.authors = ["Ben Balter"] spec.email = ["ben.balter@github.com"] spec.summary = "A Jekyll plugin for rendering GitHub avatars" spec.homepage = "https://github.com/benbalter/jekyll-avatar" spec.license = "MIT" spec.files = `git ls-files -z`.split("\x0").reject do |file| file.match(%r!^(test|spec|features)/!) end spec.require_paths = ["lib"] spec.add_dependency "jekyll", ">= 3.0", "< 5.0" spec.add_development_dependency "bundler", "> 1.0", "< 3.0" spec.add_development_dependency "rake", "~> 12.3" spec.add_development_dependency "rspec", "~> 3.0" spec.add_development_dependency "rspec-html-matchers", "~> 0.9" spec.add_development_dependency "rubocop-jekyll", "~> 0.10.0" end jekyll-avatar-0.7.0/.rspec0000644000004100000410000000003713524775746015455 0ustar www-datawww-data--format documentation --color jekyll-avatar-0.7.0/README.md0000644000004100000410000000603113524775746015617 0ustar www-datawww-data# Jekyll Avatar *A Jekyll plugin for rendering GitHub avatars* [![Build Status](https://travis-ci.org/benbalter/jekyll-avatar.svg)](https://travis-ci.org/benbalter/jekyll-avatar) Jekyll Avatar makes it easy to add GitHub avatars to your Jekyll site by specifying a username. If performance is a concern, Jekyll Avatar is deeply integrated with the GitHub avatar API, ensuring avatars are cached and load in parallel. It even automatically upgrades users to Retina images, when supported. ## Installation Add the following to your site's `Gemfile`: ```ruby gem 'jekyll-avatar' ``` And add the following to your site's `_config.yml` file: ```yaml plugins: - jekyll-avatar ``` Note: If you are using a Jekyll version less than 3.5.0, use the `gems` key instead of `plugins`. ## Usage Simply add the following, anywhere you'd like a user's avatar to appear: ``` {% avatar [USERNAME] %} ``` With `[USERNAME]` being the user's GitHub username: ``` {% avatar hubot %} ``` That will output: ```html hubot ``` ### Customizing You can customize the size of the resulting avatar by passing the size argument: ``` {% avatar hubot size=50 %} ``` That will output: ```html hubot ``` ### Passing the username as variable You can also pass the username as a variable, like this: ``` {% assign user="hubot" %} {% avatar {{ username }} %} ``` Or, if the variable is someplace a bit more complex, like a loop: ``` {% assign employees = "alice|bob" | split:"|" %} {% for employee in employees %} {% avatar user=employee %} {% endfor %} ``` ### Lazy loading images For pages showing a large number of avatars, you may want to load the images lazily. ```liquid {% avatar hubot lazy=true %} ``` This will set the `data-src` and `data-srcset` attributes on the `` tag, which is compatible with many lazy load JavaScript plugins, such as: * https://www.andreaverlicchi.eu/lazyload/ * https://appelsiini.net/projects/lazyload/ ### Using with GitHub Enterprise To use Jekyll Avatars with GitHub Enterprise, you must set the `PAGES_AVATARS_URL` environmental variable. This should be the full URL to the avatars subdomain or subpath. For example: * With subdomain isolation: `PAGES_AVATARS_URL="https://avatars.github.example.com"` * Without subdomain isolation: `PAGES_AVATARS_URL="https://github.example.com/avatars"` jekyll-avatar-0.7.0/.rubocop.yml0000644000004100000410000000040613524775746016612 0ustar www-datawww-datainherit_from: .rubocop_todo.yml require: rubocop-jekyll inherit_gem: rubocop-jekyll: .rubocop.yml Naming/FileName: Enabled: false Metrics/LineLength: Exclude: - spec/*/** Metrics/BlockLength: Enabled: false AllCops: Exclude: - vendor/**/* jekyll-avatar-0.7.0/.gitignore0000644000004100000410000000013513524775746016327 0ustar www-datawww-data/.bundle/ /.yardoc /Gemfile.lock /_yardoc/ /coverage/ /doc/ /pkg/ /spec/reports/ /tmp/ *.gem jekyll-avatar-0.7.0/script/0000755000004100000410000000000013524775746015644 5ustar www-datawww-datajekyll-avatar-0.7.0/script/cibuild0000755000004100000410000000007613524775746017210 0ustar www-datawww-data#!/bin/sh set -ex bundle exec rake spec bundle exec rubocop jekyll-avatar-0.7.0/script/bootstrap0000755000004100000410000000004313524775746017604 0ustar www-datawww-data#!/bin/sh set -ex bundle install jekyll-avatar-0.7.0/.rubocop_todo.yml0000644000004100000410000000264013524775746017641 0ustar www-datawww-data# This configuration was generated by # `rubocop --auto-gen-config` # on 2019-04-18 23:25:25 +0530 using RuboCop version 0.66.0. # The point is for the user to remove these configuration records # one by one as the offenses are removed from the code base. # Note that changes in the inspected code, or installation of new # versions of RuboCop, may require this file to be generated again. # Offense count: 1 # Cop supports --auto-correct. # Configuration parameters: EnforcedStyle. # SupportedStyles: auto_detection, squiggly, active_support, powerpack, unindent Layout/IndentHeredoc: Exclude: - 'spec/jekyll/avatar_spec.rb' # Offense count: 2 # Cop supports --auto-correct. # Configuration parameters: EnforcedStyle. # SupportedStyles: braces, no_braces, context_dependent Style/BracesAroundHashParameters: Exclude: - 'spec/jekyll/avatar_spec.rb' - 'spec/spec_helper.rb' # Offense count: 2 # Cop supports --auto-correct. Style/ExpandPathArguments: Exclude: - 'jekyll-avatar.gemspec' - 'spec/spec_helper.rb' # Offense count: 1 # Cop supports --auto-correct. Style/RedundantFreeze: Exclude: - 'lib/jekyll-avatar/version.rb' # Offense count: 6 # Cop supports --auto-correct. # Configuration parameters: EnforcedStyleForMultiline. # SupportedStylesForMultiline: comma, consistent_comma, no_comma Style/TrailingCommaInHashLiteral: Exclude: - 'lib/jekyll-avatar.rb' - 'spec/jekyll/avatar_spec.rb' jekyll-avatar-0.7.0/Rakefile0000644000004100000410000000022413524775746016003 0ustar www-datawww-data# frozen_string_literal: true require "bundler/gem_tasks" require "rspec/core/rake_task" RSpec::Core::RakeTask.new(:spec) task :default => :spec jekyll-avatar-0.7.0/lib/0000755000004100000410000000000013524775746015106 5ustar www-datawww-datajekyll-avatar-0.7.0/lib/jekyll-avatar.rb0000644000004100000410000000436413524775746020210 0ustar www-datawww-data# frozen_string_literal: true require "zlib" module Jekyll class Avatar < Liquid::Tag include Jekyll::LiquidExtensions SERVERS = 4 DEFAULT_SIZE = 40 API_VERSION = 3 def initialize(_tag_name, text, _tokens) super @text = text end def render(context) @context = context @text = Liquid::Template.parse(@text).render(@context) attrs = attributes.map { |k, v| "#{k}=\"#{v}\"" }.join(" ") "" end private def attributes result = { :class => classes, :alt => username, :width => size, :height => size, "data-proofer-ignore" => true } if lazy_load? result[:src] = "" result["data-src"] = url result["data-srcset"] = srcset else result[:src] = url result[:srcset] = srcset end result end def lazy_load? @text.include?("lazy=true") end def username matches = @text.match(%r!\buser=([\w\.]+)\b!) if matches lookup_variable(@context, matches[1]) else @text.split(" ").first.sub("@", "") end end def size matches = @text.match(%r!\bsize=(\d+)\b!i) matches ? matches[1].to_i : DEFAULT_SIZE end def path(scale = 1) "#{username}?v=#{API_VERSION}&s=#{size * scale}" end def server_number Zlib.crc32(path) % SERVERS end def host if ENV["PAGES_AVATARS_URL"].is_a?(String) && !ENV["PAGES_AVATARS_URL"].empty? ENV["PAGES_AVATARS_URL"] else "https://avatars#{server_number}.githubusercontent.com" end end def parsed_host @parsed_host ||= {} @parsed_host[host] ||= Addressable::URI.parse(host) end def url(scale = 1) uri = parsed_host uri.path << "/" unless uri.path.end_with?("/") uri = uri.join path(scale) uri.to_s end def srcset (1..4).map { |scale| "#{url(scale)} #{scale}x" }.join(", ") end # See http://primercss.io/avatars/#small-avatars def classes size < 48 ? "avatar avatar-small" : "avatar" end end end Liquid::Template.register_tag("avatar", Jekyll::Avatar) jekyll-avatar-0.7.0/lib/jekyll-avatar/0000755000004100000410000000000013524775746017654 5ustar www-datawww-datajekyll-avatar-0.7.0/lib/jekyll-avatar/version.rb0000644000004100000410000000022413524775746021664 0ustar www-datawww-data# frozen_string_literal: true module Liquid; class Tag; end; end module Jekyll class Avatar < Liquid::Tag VERSION = "0.7.0".freeze end end jekyll-avatar-0.7.0/Gemfile0000644000004100000410000000020413524775746015627 0ustar www-datawww-data# frozen_string_literal: true source "https://rubygems.org" gemspec gem "jekyll", ENV["JEKYLL_VERSION"] if ENV["JEKYLL_VERSION"] jekyll-avatar-0.7.0/.ruby-version0000644000004100000410000000000613524775746017001 0ustar www-datawww-data2.5.3 jekyll-avatar-0.7.0/.github/0000755000004100000410000000000013524775746015700 5ustar www-datawww-datajekyll-avatar-0.7.0/.github/funding.yml0000644000004100000410000000002313524775746020050 0ustar www-datawww-datapatreon: benbalter jekyll-avatar-0.7.0/.github/CODEOWNERS0000644000004100000410000000024613524775746017275 0ustar www-datawww-data# Require @benbalter's :+1: for changes to the .github repo-config files # mainly due to https://github.com/probot/settings privilege escalation .github/* @benbalter jekyll-avatar-0.7.0/.github/settings.yml0000644000004100000410000000151013524775746020260 0ustar www-datawww-data# Repository settings set via https://github.com/probot/settings # Note: Please Don't edit this file directly. # Edit https://github.com/benbalter/shared-community-files instead. repository: has_issues: true has_wiki: false has_projects: false has_downloads: false labels: - name: help wanted oldname: help-wanted color: 0e8a16 - name: more-information-needed color: d93f0b - name: bug color: b60205 - name: feature color: 1d76db - name: good first issue color: "5319e7" # Not currently implemented by probot/settings, but manually implemented in script/deploy branch_protection: restrictions: null enforce_admins: false required_status_checks: strict: true contexts: - "continuous-integration/travis-ci" required_pull_request_reviews: require_code_owner_reviews: true jekyll-avatar-0.7.0/.github/config.yml0000644000004100000410000000343613524775746017676 0ustar www-datawww-data# Behaviorbot config. See https://github.com/behaviorbot/ for more information. # Note: Please Don't edit this file directly. # Edit https://github.com/benbalter/shared-community-files instead. # Configuration for update-docs - https://github.com/behaviorbot/update-docs updateDocsComment: "Thanks for the pull request! If you are making any changes to the user-facing functionality, please be sure to update the documentation in the `README` or `docs/` folder alongside your change. :heart:" # Configuration for request-info - https://github.com/behaviorbot/request-info requestInfoReplyComment: Thanks for this. Do you mind providing a bit more information about what problem you're trying to solve? requestInfoLabelToAdd: more-information-needed # Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome #newIssueWelcomeComment: > # Welcome! # Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome newPRWelcomeComment: Welcome! Congrats on your first pull request to Jekyll Avatar. If you haven't already, please be sure to check out [the contributing guidelines](https://github.com/benbalter/jekyll-avatar/blob/master/docs/CONTRIBUTING.md). # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge firstPRMergeComment: "Congrats on getting your first pull request to Jekyll Avatar merged! Without amazing humans like you submitting pull requests, we couldn’t run this project. You rock! :tada:

If you're interested in tackling another bug or feature, take a look at [the open issues](https://github.com/benbalter/jekyll-avatar/issues), especially those [labeled `help wanted`](https://github.com/benbalter/jekyll-avatar/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)." # Bug workaround contact_links: [] jekyll-avatar-0.7.0/.github/stale.yml0000644000004100000410000000171213524775746017534 0ustar www-datawww-data# Configuration for probot-stale - https://github.com/probot/stale # Note: Please Don't edit this file directly. # Edit https://github.com/benbalter/shared-community-files instead. # Number of days of inactivity before an Issue or Pull Request becomes stale daysUntilStale: 60 # Number of days of inactivity before a stale Issue or Pull Request is closed daysUntilClose: 7 # Issues or Pull Requests with these labels will never be considered stale exemptLabels: - pinned - security # Label to use when marking as stale staleLabel: wontfix # Comment to post when marking as stale. Set to `false` to disable markComment: > This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. # Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable closeComment: false # Limit to only `issues` or `pulls` # only: issues jekyll-avatar-0.7.0/.github/no-response.yml0000644000004100000410000000146313524775746020677 0ustar www-datawww-data# Configuration for probot-no-response - https://github.com/probot/no-response # Note: Please Don't edit this file directly. # Edit https://github.com/benbalter/shared-community-files instead. # Number of days of inactivity before an Issue is closed for lack of response daysUntilClose: 14 # Label requiring a response responseRequiredLabel: more-information-needed # Comment to post when closing an Issue for lack of response. Set to `false` to disable closeComment: > This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. jekyll-avatar-0.7.0/.github/release-drafter.yml0000644000004100000410000000005413524775746021467 0ustar www-datawww-datatemplate: | ## What's Changed $CHANGES jekyll-avatar-0.7.0/.github/ISSUE_TEMPLATE/0000755000004100000410000000000013524775746020063 5ustar www-datawww-datajekyll-avatar-0.7.0/.github/ISSUE_TEMPLATE/feature_request.md0000644000004100000410000000115413524775746023611 0ustar www-datawww-data--- name: Feature request about: Suggest an idea for this project --- ### Is your feature request related to a problem? Please describe the problem you're trying to solve. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] ### Describe the solution you'd like A clear and concise description of what you want to happen. ### Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. ### Additional context Add any other context or screenshots about the feature request here. jekyll-avatar-0.7.0/.github/ISSUE_TEMPLATE/bug_report.md0000644000004100000410000000100713524775746022553 0ustar www-datawww-data--- name: Bug report about: Create a report to help us improve --- ### Describe the bug A clear and concise description of what the bug is. ### Steps to reproduce the behavior 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error ### Expected behavior A clear and concise description of what you expected to happen. ### Screenshots If applicable, add screenshots to help explain your problem. ### Additional context Add any other context about the problem here. jekyll-avatar-0.7.0/LICENSE.txt0000644000004100000410000000206513524775746016166 0ustar www-datawww-dataThe MIT License (MIT) Copyright (c) 2016 Ben Balter Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.