bundler-1.11.2/ 0000755 0000041 0000041 00000000000 12652443364 013270 5 ustar www-data www-data bundler-1.11.2/exe/ 0000755 0000041 0000041 00000000000 12652443364 014051 5 ustar www-data www-data bundler-1.11.2/exe/bundler 0000755 0000041 0000041 00000001122 12652443364 015426 0 ustar www-data www-data #!/usr/bin/env ruby # Exit cleanly from an early interrupt Signal.trap("INT") { exit 1 } require "bundler" # Check if an older version of bundler is installed $LOAD_PATH.each do |path| next unless path =~ %r{/bundler-0\.(\d+)} && $1.to_i < 9 err = "Looks like you have a version of bundler that's older than 0.9.\n" err << "Please remove your old versions.\n" err << "An easy way to do this is by running `gem cleanup bundler`." abort(err) end require "bundler/friendly_errors" Bundler.with_friendly_errors do require "bundler/cli" Bundler::CLI.start(ARGV, :debug => true) end bundler-1.11.2/exe/bundle 0000755 0000041 0000041 00000001122 12652443364 015244 0 ustar www-data www-data #!/usr/bin/env ruby # Exit cleanly from an early interrupt Signal.trap("INT") { exit 1 } require "bundler" # Check if an older version of bundler is installed $LOAD_PATH.each do |path| next unless path =~ %r{/bundler-0\.(\d+)} && $1.to_i < 9 err = "Looks like you have a version of bundler that's older than 0.9.\n" err << "Please remove your old versions.\n" err << "An easy way to do this is by running `gem cleanup bundler`." abort(err) end require "bundler/friendly_errors" Bundler.with_friendly_errors do require "bundler/cli" Bundler::CLI.start(ARGV, :debug => true) end bundler-1.11.2/exe/bundle_ruby 0000755 0000041 0000041 00000002620 12652443364 016311 0 ustar www-data www-data #!/usr/bin/env ruby Signal.trap("INT") { exit 1 } require "bundler/ruby_version" require "bundler/ruby_dsl" require "bundler/shared_helpers" module Bundler class GemfileError < RuntimeError; end class GemfileEvalError < GemfileError; end class Dsl include RubyDsl attr_accessor :ruby_version def initialize @ruby_version = nil end def eval_gemfile(gemfile, contents = nil) contents ||= File.open(gemfile, "rb", &:read) instance_eval(contents, gemfile.to_s, 1) rescue SyntaxError => e bt = e.message.split("\n")[1..-1] raise GemfileError, ["Gemfile syntax error:", *bt].join("\n") rescue ScriptError, RegexpError, NameError, ArgumentError => e e.backtrace[0] = "#{e.backtrace[0]}: #{e.message} (#{e.class})" STDERR.puts e.backtrace.join("\n ") raise GemfileError, "There was an error in your Gemfile," \ " and Bundler cannot continue." end def source(source, options = {}) end def gem(name, *args) end def group(*args, &blk) end end end STDERR.puts "Warning: bundle_ruby will be deprecated in Bundler 2.0.0." dsl = Bundler::Dsl.new begin dsl.eval_gemfile(Bundler::SharedHelpers.default_gemfile) ruby_version = dsl.ruby_version if ruby_version puts ruby_version else puts "No ruby version specified" end rescue Bundler::GemfileError => e puts e.message exit(-1) end bundler-1.11.2/Rakefile 0000644 0000041 0000041 00000022307 12652443364 014741 0 ustar www-data www-data # -*- encoding: utf-8 -*- $:.unshift File.expand_path("../lib", __FILE__) require "shellwords" require "benchmark" RUBYGEMS_REPO = File.expand_path("tmp/rubygems") BUNDLER_SPEC = Gem::Specification.load("bundler.gemspec") def safe_task(&block) yield true rescue false end # Benchmark task execution module Rake class Task alias_method :real_invoke, :invoke def invoke(*args) time = Benchmark.measure(@name) do real_invoke(*args) end puts "#{@name} ran for #{time}" end end end namespace :spec do desc "Ensure spec dependencies are installed" task :deps do deps = Hash[BUNDLER_SPEC.development_dependencies.map do |d| [d.name, d.requirement.to_s] end] deps["rubocop"] ||= "= 0.35.1" if RUBY_VERSION >= "1.9.3" # can't go in the gemspec because of the ruby version requirement # JRuby can't build ronn or rdiscount, so we skip that if defined?(RUBY_ENGINE) && RUBY_ENGINE == "jruby" deps.delete("ronn") deps.delete("rdiscount") end deps.sort_by {|name, _| name }.each do |name, version| sh %(#{Gem.ruby} -S gem list -i "^#{name}$" -v "#{version}" || ) + %(#{Gem.ruby} -S gem install #{name} -v "#{version}" --no-ri --no-rdoc) end # Download and install gems used inside tests $LOAD_PATH.unshift("./spec") require "support/rubygems_ext" Spec::Rubygems.setup end namespace :travis do task :deps do # Give the travis user a name so that git won't fatally error system "sudo sed -i 's/1000::/1000:Travis:/g' /etc/passwd" # Strip secure_path so that RVM paths transmit through sudo -E system "sudo sed -i '/secure_path/d' /etc/sudoers" # Install groff so ronn can generate man/help pages sh "sudo apt-get install groff-base -y" # Install graphviz so that the viz specs can run sh "sudo apt-get install graphviz -y 2>&1 | tail -n 2" if RUBY_VERSION < "1.9" # Downgrade Rubygems on 1.8 so Ronn can be required # https://github.com/rubygems/rubygems/issues/784 sh "gem update --system 2.1.11" else # Downgrade Rubygems so RSpec 3 can be installed # https://github.com/rubygems/rubygems/issues/813 sh "gem update --system 2.2.0" end # Install the other gem deps, etc. Rake::Task["spec:deps"].invoke end end end begin rspec = BUNDLER_SPEC.development_dependencies.find {|d| d.name == "rspec" } gem "rspec", rspec.requirement.to_s require "rspec/core/rake_task" desc "Run specs" RSpec::Core::RakeTask.new task :spec => "man:build" if RUBY_VERSION >= "1.9.3" # can't go in the gemspec because of the ruby version requirement gem "rubocop", "= 0.35.1" require "rubocop/rake_task" RuboCop::RakeTask.new end namespace :spec do task :clean do rm_rf "tmp" end desc "Run the real-world spec suite (requires internet)" task :realworld => %w(set_realworld spec) task :set_realworld do ENV["BUNDLER_REALWORLD_TESTS"] = "1" end desc "Run the spec suite with the sudo tests" task :sudo => %w(set_sudo spec clean_sudo) task :set_sudo do ENV["BUNDLER_SUDO_TESTS"] = "1" end task :clean_sudo do puts "Cleaning up sudo test files..." system "sudo rm -rf #{File.expand_path("../tmp/sudo_gem_home", __FILE__)}" end # Rubygems specs by version namespace :rubygems do rubyopt = ENV["RUBYOPT"] # When editing this list, also edit .travis.yml! branches = %w(master) releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.5 v2.4.8 v2.5.0) (branches + releases).each do |rg| desc "Run specs with Rubygems #{rg}" RSpec::Core::RakeTask.new(rg) do |t| t.rspec_opts = %w(--format documentation --color) t.ruby_opts = %w(-w) end # Create tasks like spec:rubygems:v1.8.3:sudo to run the sudo specs namespace rg do task :sudo => ["set_sudo", rg, "clean_sudo"] task :realworld => ["set_realworld", rg] end task "clone_rubygems_#{rg}" do unless File.directory?(RUBYGEMS_REPO) system("git clone https://github.com/rubygems/rubygems.git tmp/rubygems") end hash = nil Dir.chdir(RUBYGEMS_REPO) do system("git remote update") if rg == "master" system("git checkout origin/master") else system("git checkout #{rg}") || raise("Unknown Rubygems ref #{rg}") end hash = `git rev-parse HEAD`.chomp end puts "Checked out rubygems '#{rg}' at #{hash}" ENV["RUBYOPT"] = "-I#{File.expand_path("tmp/rubygems/lib")} #{rubyopt}" puts "RUBYOPT=#{ENV["RUBYOPT"]}" end task rg => ["man:build", "clone_rubygems_#{rg}"] task "rubygems:all" => rg end desc "Run specs under a Rubygems checkout (set RG=path)" RSpec::Core::RakeTask.new("co") do |t| t.rspec_opts = %w(--format documentation --color) t.ruby_opts = %w(-w) end task "setup_co" do rg = File.expand_path ENV["RG"] puts "Running specs against Rubygems in #{rg}..." ENV["RUBYOPT"] = "-I#{rg} #{rubyopt}" end task "co" => "setup_co" task "rubygems:all" => "co" end desc "Run the tests on Travis CI against a rubygem version (using ENV['RGV'])" task :travis do rg = ENV["RGV"] || raise("Rubygems version is required on Travis!") if RUBY_VERSION > "1.9.3" puts "\n\e[1;33m[Travis CI] Running bundler linter\e[m\n\n" Rake::Task["rubocop"].invoke end puts "\n\e[1;33m[Travis CI] Running bundler specs against rubygems #{rg}\e[m\n\n" specs = safe_task { Rake::Task["spec:rubygems:#{rg}"].invoke } Rake::Task["spec:rubygems:#{rg}"].reenable puts "\n\e[1;33m[Travis CI] Running bundler sudo specs against rubygems #{rg}\e[m\n\n" sudos = system("sudo -E rake spec:rubygems:#{rg}:sudo") # clean up by chowning the newly root-owned tmp directory back to the travis user system("sudo chown -R #{ENV["USER"]} #{File.join(File.dirname(__FILE__), "tmp")}") Rake::Task["spec:rubygems:#{rg}"].reenable puts "\n\e[1;33m[Travis CI] Running bundler real world specs against rubygems #{rg}\e[m\n\n" realworld = safe_task { Rake::Task["spec:rubygems:#{rg}:realworld"].invoke } { "specs" => specs, "sudo" => sudos, "realworld" => realworld }.each do |name, passed| if passed puts "\e[0;32m[Travis CI] #{name} passed\e[m" else puts "\e[0;31m[Travis CI] #{name} failed\e[m" end end unless specs && sudos && realworld raise "Spec run failed, please review the log for more information" end end end rescue LoadError task :spec do abort "Run `rake spec:deps` to be able to run the specs" end task :rubocop do abort "Run `rake spec:deps` to be able to run rubocop" end end begin require "ronn" namespace :man do directory "lib/bundler/man" sources = Dir["man/*.ronn"].map {|f| File.basename(f, ".ronn") } sources.map do |basename| ronn = "man/#{basename}.ronn" roff = "lib/bundler/man/#{basename}" file roff => ["lib/bundler/man", ronn] do sh "#{Gem.ruby} -S ronn --roff --pipe #{ronn} > #{roff}" end file "#{roff}.txt" => roff do sh "groff -Wall -mtty-char -mandoc -Tascii #{roff} | col -b > #{roff}.txt" end task :build_all_pages => "#{roff}.txt" end task :clean do leftovers = Dir["lib/bundler/man/*"].reject do |f| basename = File.basename(f).sub(/\.(txt|ronn)/, "") sources.include?(basename) end rm leftovers if leftovers.any? end desc "Build the man pages" task :build => ["man:clean", "man:build_all_pages"] desc "Remove all built man pages" task :clobber do rm_rf "lib/bundler/man" end task(:require) {} end rescue LoadError namespace :man do task(:require) { abort "Install the ronn gem to be able to release!" } task(:build) { warn "Install the ronn gem to build the help pages" } end end begin require "automatiek" Automatiek::RakeTask.new("molinillo") do |lib| lib.download = { :github => "https://github.com/CocoaPods/Molinillo" } lib.namespace = "Molinillo" lib.prefix = "Bundler" lib.vendor_lib = "lib/bundler/vendor/molinillo" end Automatiek::RakeTask.new("thor") do |lib| lib.download = { :github => "https://github.com/erikhuda/thor" } lib.namespace = "Thor" lib.prefix = "Bundler" lib.vendor_lib = "lib/bundler/vendor/thor" end rescue LoadError namespace :vendor do task(:molinillo) { abort "Install the automatiek gem to be able to vendor gems." } task(:thor) { abort "Install the automatiek gem to be able to vendor gems." } end end desc "Update vendored SSL certs to match the certs vendored by Rubygems" task :update_certs => "spec:rubygems:clone_rubygems_master" do require "bundler/ssl_certs/certificate_manager" Bundler::SSLCerts::CertificateManager.update_from!(RUBYGEMS_REPO) end require "bundler/gem_tasks" task :build => ["man:build"] task :release => ["man:require", "man:build"] task :default => :spec bundler-1.11.2/bin/ 0000755 0000041 0000041 00000000000 12652443364 014040 5 ustar www-data www-data bundler-1.11.2/bin/rubocop 0000755 0000041 0000041 00000000431 12652443364 015435 0 ustar www-data www-data #!/usr/bin/env ruby require "rubygems" bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__)) bundler_spec.dependencies.each do |dep| gem dep.name, dep.requirement.to_s end gem "rubocop", "= 0.35.1" load Gem.bin_path("rubocop", "rubocop") bundler-1.11.2/bin/rake 0000755 0000041 0000041 00000000523 12652443364 014710 0 ustar www-data www-data #!/usr/bin/env ruby require "rubygems" bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__)) bundler_spec.dependencies.each do |dep| begin gem dep.name, dep.requirement.to_s rescue Gem::LoadError => e $stderr.puts "#{e.message} (#{e.class})" end end load Gem.bin_path("rake", "rake") bundler-1.11.2/bin/rspec 0000755 0000041 0000041 00000000400 12652443364 015074 0 ustar www-data www-data #!/usr/bin/env ruby require "rubygems" bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__)) bundler_spec.dependencies.each do |dep| gem dep.name, dep.requirement.to_s end load Gem.bin_path("rspec-core", "rspec") bundler-1.11.2/.rubocop_todo.yml 0000644 0000041 0000041 00000005557 12652443364 016603 0 ustar www-data www-data # This configuration was generated by # `rubocop --auto-gen-config` # on 2015-11-21 00:03:12 -0600 using RuboCop version 0.35.1. # 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: 4 Lint/Eval: Exclude: - 'lib/bundler.rb' - 'lib/bundler/endpoint_specification.rb' - 'spec/support/streams.rb' # Offense count: 5 Lint/HandleExceptions: Exclude: - 'lib/bundler/fetcher/dependency.rb' - 'lib/bundler/installer.rb' - 'lib/bundler/psyched_yaml.rb' - 'lib/bundler/vendored_persistent.rb' # Offense count: 1 Lint/NestedMethodDefinition: Exclude: - 'lib/bundler/graph.rb' # Offense count: 5 Lint/RescueException: Exclude: - 'lib/bundler/cli.rb' - 'lib/bundler/dsl.rb' - 'lib/bundler/friendly_errors.rb' - 'lib/bundler/rubygems_integration.rb' - 'lib/bundler/worker.rb' # Offense count: 7 Lint/UselessAssignment: Exclude: - 'lib/bundler/graph.rb' - 'lib/bundler/index.rb' - 'lib/bundler/installer.rb' # Offense count: 1031 # Configuration parameters: AllowURI, URISchemes. Metrics/LineLength: Max: 207 # Offense count: 2 # Configuration parameters: CountKeywordArgs. Metrics/ParameterLists: Max: 6 # Offense count: 50 Metrics/PerceivedComplexity: Max: 54 # Offense count: 1 Style/AccessorMethodName: Exclude: - 'lib/bundler/source/git.rb' # Offense count: 3 Style/CaseEquality: Exclude: - 'lib/bundler/dsl.rb' - 'lib/bundler/match_platform.rb' - 'lib/bundler/rubygems_ext.rb' # Offense count: 22 # Configuration parameters: EnforcedStyle, SupportedStyles. Style/ClassAndModuleChildren: Enabled: false # Offense count: 119 # Configuration parameters: Exclude. Style/Documentation: Enabled: false # Offense count: 1 # Configuration parameters: Exclude. Style/FileName: Exclude: - 'lib/bundler/templates/Executable' # Offense count: 4 # Configuration parameters: AllowedVariables. Style/GlobalVars: Exclude: - 'lib/bundler/cli.rb' - 'spec/spec_helper.rb' - 'spec/support/helpers.rb' # Offense count: 32 # Configuration parameters: MinBodyLength. Style/GuardClause: Enabled: false # Offense count: 2 Style/ModuleFunction: Exclude: - 'lib/bundler/shared_helpers.rb' - 'spec/support/path.rb' # Offense count: 8 # Configuration parameters: NamePrefix, NamePrefixBlacklist, NameWhitelist. Style/PredicateName: Exclude: - 'lib/bundler/definition.rb' - 'lib/bundler/installer/parallel_installer.rb' - 'lib/bundler/settings.rb' - 'lib/bundler/source/git.rb' - 'lib/bundler/source/git/git_proxy.rb' - 'lib/bundler/source/path.rb' # Offense count: 7 # Configuration parameters: EnforcedStyle, SupportedStyles. Style/RaiseArgs: Enabled: false bundler-1.11.2/DEVELOPMENT.md 0000644 0000041 0000041 00000022333 12652443364 015377 0 ustar www-data www-data Great to have you here! Here are a few ways you can help out with [Bundler](http://github.com/bundler/bundler). # Where should I start? You can start learning about Bundler by reading [the documentation](http://bundler.io). If you want, you can also read a (lengthy) explanation of [why Bundler exists and what it does](http://bundler.io/rationale.html). You can also check out discussions about Bundler on the [Bundler mailing list](https://groups.google.com/group/ruby-bundler) and in the [Bundler IRC channel](http://webchat.freenode.net/?channels=%23bundler), which is #bundler on Freenode. Please note that this project is released with a contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms. ## Your first commits If you’re interested in contributing to Bundler, that’s awesome! We’d love your help. If you have any questions after reading this page, please feel free to contact either [@indirect](http://github.com/indirect) or [@hone](http://github.com/hone). They are both happy to provide help working through your first bugfix or thinking through the problem you’re trying to resolve. ## How you can help We track [small bugs](https://github.com/bundler/bundler/issues?labels=small&state=open) and [small features](https://github.com/bundler/bundler-features/issues?labels=small&state=open) so that anyone who wants to help can start with something that's not too overwhelming. We also keep a [list of things anyone can help with, any time](https://github.com/bundler/bundler/blob/master/CONTRIBUTING.md#contributing). If nothing on those lists looks good, talk to us, and we'll figure out what you can help with. We can absolutely use your help, no matter what level of programming skill you have at the moment. # Development setup Bundler doesn't use a Gemfile to list development dependencies, because when we tried it we couldn't tell if we were awake or it was just another level of dreams. To work on Bundler, you'll probably want to do a couple of things. 1. Install Bundler's development dependencies $ rake spec:deps 2. Run the test suite, to make sure things are working $ rake spec 3. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias: $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle' With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command. # Bug triage Triage is the work of processing tickets that have been opened into actionable issues, feature requests, or bug reports. That includes verifying bugs, categorizing the ticket, and ensuring there's enough information to reproduce the bug for anyone who wants to try to fix it. We've created an [issues guide](https://github.com/bundler/bundler/blob/master/ISSUES.md) to walk Bundler users through the process of troubleshooting issues and reporting bugs. If you'd like to help, awesome! You can [report a new bug](https://github.com/bundler/bundler/issues/new) or browse our [existing open tickets](https://github.com/bundler/bundler/issues). Not every ticket will point to a bug in Bundler's code, but open tickets usually mean that there is something we could improve to help that user. Sometimes that means writing additional documentation, sometimes that means making error messages clearer, and sometimes that means explaining to a user that they need to install git to use git gems. When you're looking at a ticket, here are the main questions to ask: * Can I reproduce this bug myself? * Are the steps to reproduce clearly stated in the ticket? * Which versions of Bundler (1.1.x, 1.2.x, git, etc.) manifest this bug? * Which operating systems (OS X, Windows, Ubuntu, CentOS, etc.) manifest this bug? * Which rubies (MRI, JRuby, Rubinius, etc.) and which versions (1.8.7, 1.9.3, etc.) have this bug? If you can't reproduce an issue, chances are good that the bug has been fixed (hurrah!). That's a good time to post to the ticket explaining what you did and how it worked. If you can reproduce an issue, you're well on your way to fixing it. :) Fixing issues is similar to adding new features: 1. Discuss the fix on the existing issue. Coordinating with everyone else saves duplicate work and serves as a great way to get suggestions and ideas if you need any. 2. Base your commits on the correct branch. Bugfixes for 1.x versions of Bundler should be based on the matching 1-x-stable branch. 3. Commit the code and at least one test covering your changes to a named branch in your fork. 4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the “Bugfixes” heading. 5. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your bugfix branch. Finally, the ticket may be a duplicate of another older ticket. If you notice a ticket is a duplicate, simply comment on the ticket noting the original ticket’s number. For example, you could say “This is a duplicate of issue #42, and can be closed”. # Adding new features If you would like to add a new feature to Bundler, please follow these steps: 1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) in the bundler-features repo to discuss your feature. 2. Base your commits on the master branch, since we follow [SemVer](http://semver.org) and don't add new features to old releases. 3. Commit the code and at least one test covering your changes to a feature branch in your fork. 4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the "Features" heading. 5. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your feature branch. If you don't hear back immediately, don’t get discouraged! We all have day jobs, but we respond to most tickets within a day or two. # Beta testing Early releases require heavy testing, especially across various system setups. We :heart: testers, and are big fans of anyone who can run `gem install bundler --pre` and try out upcoming releases in their development and staging environments. There may not always be prereleases or beta versions of Bundler. The Bundler team will tweet from the [@bundlerio account](http://twitter.com/bundlerio) when a prerelease or beta version becomes available. You are also always welcome to try checking out master and building a gem yourself if you want to try out the latest changes. # Translations We don't currently have any translations, but please reach out to us if you would like to help get this going. # Documentation Code needs explanation, and sometimes those who know the code well have trouble explaining it to someone just getting into it. Because of that, we welcome documentation suggestions and patches from everyone, especially if they are brand new to using Bundler. Bundler has two main sources of documentation: the built-in help (including usage information and man pages) and the [Bundler documentation site](http://bundler.io). If you’d like to submit a patch to the man pages, follow the steps for adding a feature above. All of the man pages are located in the `man` directory. Just use the “Documentation” heading when you describe what you did in the changelog. If you have a suggestion or proposed change for [bundler.io](http://bundler.io), please open an issue or send a pull request to the [bundler-site](https://github.com/bundler/bundler-site) repository. # Community Community is an important part of all we do. If you’d like to be part of the Bundler community, you can jump right in and start helping make Bundler better for everyone who uses it. It would be tremendously helpful to have more people answering questions about Bundler (and often simply about Rubygems or Ruby itself) in our [issue tracker](https://github.com/bundler/bundler/issues) or on [Stack Overflow](http://stackoverflow.com/questions/tagged/bundler). Additional documentation and explanation is always helpful, too. If you have any suggestions for the Bundler website [bundler.io](http://bundler.io), we would absolutely love it if you opened an issue or pull request on the [bundler-site](https://github.com/bundler/bundler-site) repository. Finally, sharing your experiences and discoveries by writing them up is a valuable way to help others who have similar problems or experiences in the future. You can write a blog post, create an example and commit it to Github, take screenshots, or make videos. Examples of how Bundler is used help everyone, and we’ve discovered that people already use it in ways that we never imagined when we were writing it. If you’re still not sure what to write about, there are also several projects doing interesting things based on Bundler. They could probably use publicity too. If you let someone on the core team know you wrote about Bundler, we will add your post to the list of Bundler resources on the Github project wiki. Finally, participate carefully in the all contributors to the Bundler project must agree to the contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms. bundler-1.11.2/.rspec 0000644 0000041 0000041 00000000052 12652443364 014402 0 ustar www-data www-data --format documentation --color --warnings bundler-1.11.2/CODE_OF_CONDUCT.md 0000644 0000041 0000041 00000006700 12652443364 016072 0 ustar www-data www-data # Bundler Code of Conduct The Bundler project strongly values contributors from anywhere, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, ethnicity, age, religion, or nationality. As a result, the Bundler team has agreed to and enforces this code of conduct in order to provide a harassment-free experience for everyone who participates in the development of Bundler. ### Summary Harassment in code and discussion or violation of physical boundaries is completely unacceptable anywhere in the Bundler project’s codebases, issue trackers, chat rooms, mailing lists, meetups, and any other events. Violators will be warned and then blocked or banned by the core team at or before the 3rd violation. ### In detail Harassment includes offensive verbal comments related to level of experience, gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, ethnicity, age, religion, nationality, the use of sexualized language or imagery, deliberate intimidation, stalking, sustained disruption, and unwelcome sexual attention. Individuals asked to stop any harassing behavior are expected to comply immediately. Maintainers, including the core team, are also subject to the anti-harassment policy. If anyone engages in abusive, harassing, or otherwise unacceptable behavior, including maintainers, we may take appropriate action, up to and including warning the offender, deletion of comments, removal from the project’s codebase and communication systems, and escalation to Github support. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of [the core team](http://bundler.io/contributors.html) or [email the core team](mailto:team@bundler.io) immediately. We expect everyone to follow these rules anywhere in the Bundler project’s codebases, issue trackers, IRC channel, group chat, and mailing lists. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Finally, don't forget that it is human to make mistakes! We all do. Let’s work together to help each other, resolve issues, and learn from the mistakes that we will all inevitably make from time to time. ### Thanks Thanks to the [JSConf Code of Conduct](http://jsconf.com/codeofconduct.html) and [Fedora Code of Conduct](http://fedoraproject.org/code-of-conduct) for inspiration and ideas. Additional thanks to [Contributor Covenant](http://contributor-covenant.org) for the [default code of conduct](https://github.com/bundler/bundler/blob/master/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt) included in generated gems. ### License
To the extent possible under law, The Bundler Team has waived all copyright and related or neighboring rights to the Bundler Code of Conduct. This work is published from the United States.