sinatra-rack-3-commonlit 3.1.0

data/CONTRIBUTING.md

@@ -0,0 +1,100 @@
+# Contribute
+
+Want to show Sinatra some love? Help out by contributing!
+
+## Found a bug?
+
+Log it in our [issue tracker][ghi] or send a note to the [mailing list][ml].
+Be sure to include all relevant information, like the versions of Sinatra and
+Ruby you're using. A [gist](http://gist.github.com/) of the code that caused
+the issue as well as any error messages are also very helpful.
+
+## Need help?
+
+The [Sinatra mailing list][ml] has over 900 subscribers, many of which are happy
+to help out newbies or talk about potential feature additions. You can also
+drop by the [#sinatra](irc://chat.freenode.net/#sinatra) channel on
+[irc.freenode.net](http://freenode.net).
+
+## Have a patch?
+
+Bugs and feature requests that include patches are much more likely to
+get attention. Here are some guidelines that will help ensure your patch
+can be applied as quickly as possible:
+
+1. **Use [Git](http://git-scm.com) and [GitHub](http://github.com):**
+   The easiest way to get setup is to fork the
+   [sinatra/sinatra repo](http://github.com/sinatra/sinatra/).
+   Or, the [sinatra.github.com repo](http://github.com/sinatra/sinatra.github.com/),
+   if the patch is doc related.
+
+2. **Write unit tests:** If you add or modify functionality, it must
+   include unit tests. If you don't write tests, we have to, and this
+   can hold up acceptance of the patch.
+
+3. **Mind the `README`:** If the patch adds or modifies a major feature,
+   modify the `README.md` file to reflect that. Again, if you don't
+   update the `README`, we have to, and this holds up acceptance.
+
+4. **Push it:** Once you're ready, push your changes to a topic branch
+   and add a note to the ticket with the URL to your branch. Or, say
+   something like, "you can find the patch on johndoe/foobranch". We also
+   gladly accept GitHub [pull requests](http://help.github.com/pull-requests/).
+
+__NOTE:__ _We will take whatever we can get._ If you prefer to attach diffs in
+emails to the mailing list, that's fine; but do know that _someone_ will need
+to take the diff through the process described above and this can hold things
+up considerably.
+
+## Want to write docs?
+
+The process for contributing to Sinatra's website, documentation or the book
+is the same as contributing code. We use Git for versions control and GitHub to
+track patch requests.
+
+* [The sinatra.github.com repo](http://github.com/sinatra/sinatra.github.com/)
+  is where the website sources are managed. There are almost always people in
+  `#sinatra` that are happy to discuss, apply, and publish website patches.
+
+* [The Book](http://sinatra-org-book.herokuapp.com/) has its own [Git
+  repository](http://github.com/sinatra/sinatra-book/) and build process but is
+  managed the same as the website and project codebase.
+
+* [Sinatra Recipes](http://recipes.sinatrarb.com/) is a community
+  project where anyone is free to contribute ideas, recipes and tutorials. Which
+  also has its own [Git repository](http://github.com/sinatra/sinatra-recipes).
+
+* [The Introduction](http://www.sinatrarb.com/intro.html) is generated from
+  Sinatra's [README file](http://github.com/sinatra/sinatra/blob/main/README.md).
+
+* If you want to help translating the documentation, the README is already
+  available in
+  [Japanese](http://github.com/sinatra/sinatra/blob/main/README.ja.md),
+  [German](http://github.com/sinatra/sinatra/blob/main/README.de.md),
+  [Chinese](https://github.com/sinatra/sinatra/blob/main/README.zh.md),
+  [Russian](https://github.com/sinatra/sinatra/blob/main/README.ru.md),
+  [European](https://github.com/sinatra/sinatra/blob/main/README.pt-pt.md) and
+  [Brazilian](https://github.com/sinatra/sinatra/blob/main/README.pt-br.md)
+  Portuguese,
+  [French](https://github.com/sinatra/sinatra/blob/main/README.fr.md),
+  [Spanish](https://github.com/sinatra/sinatra/blob/main/README.es.md),
+  [Korean](https://github.com/sinatra/sinatra/blob/main/README.ko.md), and
+  [Hungarian](https://github.com/sinatra/sinatra/blob/main/README.hu.md).
+  The translations tend to fall behind the English version. Translations into
+  other languages would also be appreciated.
+
+## Looking for something to do?
+
+If you'd like to help out but aren't sure how, pick something that looks
+interesting from the [issues][ghi] list and hack on. Make sure to leave a
+comment on the ticket noting that you're investigating (a simple "Taking…" is
+fine).
+
+[ghi]: http://github.com/sinatra/sinatra/issues
+[ml]: http://groups.google.com/group/sinatrarb/topics "Sinatra Mailing List"
+
+* ["Help Wanted"](https://github.com/sinatra/sinatra/labels/help%20wanted):  Anyone willing to pitch in is open to contribute to this ticket as they see fit (will try to add context / summarize or ask for requirements)
+
+* ["Good First Issue"](https://github.com/sinatra/sinatra/labels/good%20first%20issue): Potential first time contributors should start here
+
+* ["Wishlist"](https://github.com/sinatra/sinatra/labels/Wishlist): All the things I wish we had but have no time for

data/Gemfile

@@ -0,0 +1,68 @@
+# frozen_string_literal: true
+
+# Why use bundler?
+# Well, not all development dependencies install on all rubies. Moreover, `gem
+# install sinatra --development` doesn't work, as it will also try to install
+# development dependencies of our dependencies, and those are not conflict free.
+# So, here we are, `bundle install`.
+#
+# If you have issues with a gem: `bundle install --without-coffee-script`.
+
+source 'https://rubygems.org'
+gemspec
+
+gem 'rake'
+
+rack_version = ENV['rack'].to_s
+rack_version = nil if rack_version.empty? || (rack_version == 'stable')
+rack_version = { github: 'rack/rack' } if rack_version == 'head'
+gem 'rack', rack_version
+
+puma_version = ENV['puma'].to_s
+puma_version = nil if puma_version.empty? || (puma_version == 'stable')
+puma_version = { github: 'puma/puma' } if puma_version == 'head'
+gem 'puma', puma_version
+
+gem 'minitest', '~> 5.0'
+gem 'rack-test', github: 'rack/rack-test'
+gem 'rubocop', '~> 1.32.0', require: false
+gem 'yard'
+
+gem 'rack-protection', path: 'rack-protection'
+gem 'sinatra-contrib', path: 'sinatra-contrib'
+
+# traces 0.10.0 started to use Ruby 2.7 syntax without specifying required Ruby version
+# https://github.com/socketry/traces/pull/8#discussion_r1237988182
+# async-http 0.60.2 added traces 0.10.0 as dependency
+# https://github.com/socketry/async-http/pull/124/files#r1237988899
+gem 'traces', '< 0.10.0' if RUBY_VERSION >= '2.6.0' && RUBY_VERSION < '2.7.0'
+
+gem 'activesupport', '~> 6.1'
+
+gem 'asciidoctor'
+gem 'builder'
+gem 'commonmarker', '~> 0.23.4', platforms: [:ruby]
+gem 'erubi'
+gem 'eventmachine'
+gem 'falcon', '~> 0.40', platforms: [:ruby]
+gem 'haml', '~> 6'
+gem 'kramdown'
+gem 'liquid'
+gem 'markaby'
+gem 'nokogiri', '> 1.5.0'
+gem 'pandoc-ruby', '~> 2.0.2'
+gem 'rabl'
+if rack_version == '~> 2'
+  gem 'rainbows', platforms: [:mri] # uses #fork
+end
+gem 'rdiscount', platforms: [:ruby]
+gem 'rdoc'
+gem 'redcarpet', platforms: [:ruby]
+gem 'sass-embedded', '~> 1.54'
+gem 'simplecov', require: false
+gem 'slim', '~> 4'
+gem 'yajl-ruby', platforms: [:ruby]
+
+gem 'json', platforms: %i[jruby mri]
+
+gem 'jar-dependencies', '= 0.4.1', platforms: [:jruby] # Gem::LoadError with jar-dependencies 0.4.2

data/LICENSE

@@ -0,0 +1,26 @@
+The MIT License (MIT)
+
+Copyright (c) 2007, 2008, 2009 Blake Mizerany
+Copyright (c) 2010-2017 Konstantin Haase
+Copyright (c) 2015-2017 Zachary Scott
+
+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.

data/MAINTENANCE.md

@@ -0,0 +1,29 @@
+# Sinatra maintenance
+
+## Versions
+
+### Releases
+
+The next major version of Sinatra will be released from the main branch. Each version will be tagged so it will be possible to branch of should there be a need for bug fixes and other updates.
+
+## Issues
+
+### New features
+
+New features will only be added to the main branch and will not be made available in point releases.
+
+### Bug fixes
+
+Only the latest release series will receive bug fixes. When enough bugs are fixed and its deemed worthy to release a new gem, this is the branch it happens from.
+
+### Security issues
+
+The current release series will receive patches and new versions in case of a security issue.
+
+### Severe security issues
+
+For severe security issues we will provide new versions as above, and also the last major release series will receive patches and new versions. The classification of the security issue is judged by the core team.
+
+### Unsupported Release Series
+
+When a release series is no longer supported, it’s your own responsibility to deal with bugs and security issues. We may provide back-ports of the fixes and publish them to git, however there will be no new versions released. If you are not comfortable maintaining your own versions, you should upgrade to a supported version.