celluloid 0.18.0.pre → 0.18.0.pre2

data/culture/CONDUCT.md

@@ -1,38 +0,0 @@
-Contributor Code of Conduct
-
-As contributors and maintainers of this project, and in the interest of fostering
-an open and welcoming community, we pledge to respect all people who contribute
-through reporting issues, posting feature requests, updating documentation,
-submitting pull requests or patches, and other activities.
-
-We are committed to making participation in this project a harassment-free experience for
-everyone, regardless of level of experience, gender, gender identity and expression,
-sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
-religion, or nationality.
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
-* Public or private harassment
-* Publishing other's private information, such as physical or electronic addresses,
- without explicit permission
-* Other unethical or unprofessional conduct.
-
-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. By adopting this Code of Conduct, project maintainers
-commit themselves to fairly and consistently applying these principles to every aspect
-of managing this project. Project maintainers who do not follow or enforce the Code of
-Conduct may be permanently removed from the project team.
-
-This code of conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
-opening an issue or contacting one or more of the project maintainers.
-
-This Code of Conduct is adapted from the Contributor Covenant
-(http://contributor-covenant.org), version 1.2.0, available at
-http://contributor-covenant.org/version/1/2/0/

data/culture/GSoC/1010-why_we_will_participate.md

@@ -1,17 +0,0 @@
-### Why does your org want to participate in Google Summer of Code?
-
-This year is pivotal for us. Celluloid is approaching "1.0" across its suite of Ruby gems. We need students' attention focused on Celluloid itself now.
-
-We want to participate directly this year, for three reasons:
-
-1) We grew beyond the scope of umbrella organizations, and are establishing a new non-profit corporation.
-
-2) We are important to one of the most epic shifts in software. With us, any coder can create parallel, asynchronous, concurrent, and/or distributed systems, simply. We hold & gain ground in a fierce, ordinarily complicated, multi-threaded multi-core space; fought over by Erlang/Elixr, Go, Rust, Akka, etc.
-
-3) We are important to Ruby:
-
-a) We maintain many widely used libraries, and have millions of downloads.
-
-b) We bring design diversity to Ruby. The vast majority of Rubyists tend toward one design approach: Rails+Rack. We offer alternatives sparing Ruby from monoculture.
-
-c) We cause Ruby itself to evolve. We use and stretch nearly every aspect of every Ruby engine.

data/culture/GSoC/1020-how_mentors_stay_engaged.md

@@ -1,7 +0,0 @@
-### How will you keep mentors engaged with their students?
-
-We have many contributors with management experience. One of our administrators will not be mentoring a student, but instead will be responsible for assessing public communication and activity, providing encouragement and support. We will also be creating healthy competition between mentors.
-
-All mentors and students will be present in Ryver. All student activity ( code and communication ) will be visible, and administrators will be monitoring student activity and mentor interactions. On a weekly basis, before prolonged trouble or inactivity, at least one person in addition to the mentor involved will know a mentor or student began to fall behind the stated project goals, and/or the program's expectations.
-
-Celluloid is a tight community who will be encouraging both mentors and students. But we will also be offering incentives to top performing students, offering prizes such as stickers, shirts, virtual server credits, internships at Celluloid supporting organizations, etc.

data/culture/GSoC/1030-keeping_students_on_schedule.md

@@ -1,9 +0,0 @@
-### How will you help your students stay on schedule to complete their projects?
-
-We will hold short but frequent status meetings every two weeks at the longest ( but aspiring to weekly ) - implementing the Agile and Scrum methodology's style of status and assistance meetings.
-
-We will treat the group of mentors as a team, the students as a team, the students and mentors as teams, and treat the entire organization as a pool of talent and assistance for all the other students and mentors in the organization. If anyone encounters a roadblock, they have plenty of support.
-
-Rather than treat projects as a water-tight compartments, we will cross-motivate students: We will share successes, draw attention to unique dilemmas, etc. We will encourage, showcase progress, and foster a spirit of respectful competition between projects for mentors and students alike.
-
-And as mentioned, will have a non-mentor organization administrator acting as a communications and performance monitor, mentor assistant, and "cheer-leader" for both students and mentors.

data/culture/GSoC/1040-getting_students_involved.md

@@ -1,5 +0,0 @@
-### How will you get your students involved in your community during GSoC?
-
-In addition to Ryver, we will be engaging students on GitHub, Hangouts, IRC, Twitter, Google Groups, even LinkedIn. These will be all introduced and utilized by students during the GSoC program. By the time the program is over, the students will be new community members who are each deeply connected.
-
-Our quick but frequent Agile-style meetings will further orient the students to the wider community, rather than just speaking with their mentor. By the end, everyone will know each other. Students will become aware of opportunities to work in the community, and community veterans will have a chance to observe -- then establish relationships which lead to their own businesses and other organizations engaging students as interns, future contractors, technical co-founders, and more.

data/culture/GSoC/1050-student_involvement_after.md

@@ -1,5 +0,0 @@
-### How will you keep students involved with your community after GSoC?
-
-Organizations who use Celluloid will be offering internships to top performing students. We have many disciplines a student start a career in after school, both in Open Source directly, and in organizations all over the world.
-
-In the past Celluloid mentors and students have been known to keep contact long after GSoC is over. We draw students into the organic relationships and community ties we normally have in our existing sub-culture.

data/culture/GSoC/README.md

@@ -1,16 +0,0 @@
-### Answers to our GSoC Organization application questions:
-
-Please feel free to fork, edit, and request your changes be pulled in.
-
-* [Why does your org want to participate in Google Summer of Code?][1]
-* [How will you keep mentors engaged with their students?][2]
-* [How will you help your students stay on schedule to complete their projects?][3]
-* [How will you get your students involved in your community during GSoC?][4]
-* [How will you keep students involved with your community after GSoC?][5]
-
-
-[1]: https://github.com/celluloid/culture/blob/master/GSoC/1010-why_we_will_participate.md
-[2]: https://github.com/celluloid/culture/blob/master/GSoC/1020-how_mentors_stay_engaged.md
-[3]: https://github.com/celluloid/culture/blob/master/GSoC/1030-keeping_students_on_schedule.md
-[4]: https://github.com/celluloid/culture/blob/master/GSoC/1040-getting_students_involved.md
-[5]: https://github.com/celluloid/culture/blob/master/GSoC/1050-student_involvement_after.md

data/culture/Gemfile

@@ -1,9 +0,0 @@
-source "https://rubygems.org"
-
-group :development, :test do
-  gem "rubocop"
-  gem "rspec"
-  gem "rake"
-end
-
-gemspec

data/culture/LICENSE.txt

@@ -1,22 +0,0 @@
-Copyright (c) 2012 Tony Arcieri, Donovan Keme
-
-MIT License
-
-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/culture/README.md

@@ -1,22 +0,0 @@
-Celluloid::Culture
-==================
-[![Build Status](https://travis-ci.org/celluloid/culture.svg)](https://travis-ci.org/celluloid/culture)
-
-### Please see...
-* Important [issues for discussion](https://github.com/celluloid/culture/issues).
-* Information about [Celluloid::Sync](SYNC.md).
-* Information about [RuboCop](rubocop/README.md).
-
-
-## Integration
-To add `celluloid/culture` and its many splendors to a gem, install it as a sub-module of the gem repository. Once you fully integrate [`Celluloid::Sync`](SYNC.md), the sub-module will be automatically refreshed.
-
-##### Add celluloid/culture as GIT submodule:
-```sh
-git submodule add http://github.com/celluloid/culture.git
-```
-
-Make sure `http://` is used and no other method of inclusion. CI needs it to be `http://`
-
-### Then what?
-Once you've done that, read up on [Celluloid::Sync](SYNC.md) and [RuboCop](rubocop/README.md).

data/culture/Rakefile

@@ -1,5 +0,0 @@
-require "bundler/gem_tasks"
-
-Dir["tasks/**/*.rake"].each { |task| load task }
-
-task default: "rubocop"

data/culture/SYNC.md

@@ -1,70 +0,0 @@
-# Celluloid::Sync
-
-The `celluloid/culture` sub-module needs to be updated in ever repository which uses it, and integrations between all the gems in Celluloid's core suite began to need greater efficiency in handling many gems at once. This lead to the birth of `Celluloid::Sync` and its automation of several otherwise tedious tasks.
-
-
-## When all is said and done...
-
-Running `bundle` or `rspec` will trigger `Celluloid::Sync` automatically, without slowing you down.
-
----
-
-## So what does it do?
-
-**1. It adds the gem you're in to the `$LOADPATH`.**
-
-**2. It tries to find the `VERSION` constant for the current gem and load it.**
-
-This allows easy inclusion of `VERSION` in gemspec, without individually including the required file first.
-
-**3. It updates the `celluloid/culture` sub-module.**
-
-Whenever `bundle` is run, the `culture/` directory is synchronized with the repository before it's used any further.
-
-**4. It keeps `Gemfile` and `gemspec` requirements up to date.**
-
-Avoid circular dependency errors, but still have the power to use locally sourced repositories.
-
----
-
-## How is it installed in `Gemfile` and `gemspec` then?
-
-Add the line above to the top of both files, before everything else:
-
-
-```ruby
-require File.expand_path("../culture/sync", __FILE__)
-```
-
-
-#### Finishing off `gemspec` ...
-
-You only have one other line to add, other than line above ... right before the closing `end` in the file:
-
-```ruby
-require File.expand_path("../culture/sync", __FILE__)
-Gem::Specification.new do |gem|
-  # ...
-  # ...
-  # Keep in mind, the VERSION constant of this gem ought to be loaded.
-  # ...
-  # ...
-  Celluloid::Sync.gems(gem)
-end
-
-```
-
-#### Finishing off `Gemfile` ...
-
-Same as in `gemspec` you have only two bits to add. The second line we're adding goes at the very end, or at least after `gemspec` is called:
-
-```ruby
-require File.expand_path("../culture/sync", __FILE__)
-
-# ...
-# below any calls to `gemspec`
-# below any other gems
-# ...
-
-Celluloid::Sync.gems(self)
-```

data/culture/celluloid-culture.gemspec

@@ -1,18 +0,0 @@
-# coding: utf-8
-
-Gem::Specification.new do |spec|
-  spec.name          = "celluloid-culture"
-  spec.version       = "0.2"
-  spec.authors       = ["Tony Arcieri", "Donovan Keme"]
-  spec.email         = ["bascule@gmail.com", "code@extremist.digital"]
-
-  spec.summary       = "The culture of Celluloid, in RubyGem form!"
-  spec.description   = "In which we try to codify Celluloid's life philosophy as Ruby"
-  spec.homepage      = "https://github.com/celluloid/culture"
-
-  spec.files        = Dir["README.md", "CHANGES.md", "LICENSE.txt", "lib/**/*", "spec/**/*"]
-  spec.require_path = "lib"
-
-  spec.add_development_dependency "bundler", "~> 1.9"
-  spec.add_development_dependency "rake",    "~> 10.0"
-end

data/culture/gems/README.md

@@ -1,39 +0,0 @@
-# Motivation
-To achieve the higher level of modularity, Celluloid was split into small sub-projects that naturally depend on each other.
-Bundler can't handle circular dependencies properly and currently the only workaround is to list all celluloid-ish dependencies in both Gemfile and gemspec.
-This is error-prone and not efficient. Thus it was required to put some better workaround in place.
-
-# Configuration
-The list of gems and their properties are now defined in `dependencies.yml`.
-
-For example:
-
-```yml
-celluloid:
-  bundler:
-    github: celluloid/celluloid
-    branch: 0.17.0-prerelease
-celluloid-extras:
-  bundler:
-    github: celluloid/celluloid-extras
-celluloid-supervision:
-  bundler:
-    github: celluloid/celluloid-supervision
-celluloid-pool:
-  bundler:
-    github: celluloid/celluloid-pool
-celluloid-fsm:
-  bundler:
-    github: celluloid/celluloid-fsm
-timers:
-  gemspec:
-     - ~> 4.0.0
-  bundler:
-    github: celluloid/timers
-```
-
-# Modification of `gemspec` and `Gemfile`
-
-The injection of dependencies into `gemspec` and `Gemfile` is handled by `Celluloid::Sync.gems()`, which routes to either `Celluloid::Gems.gemspec` or `Celluloid::Gems.gemfile` depending on what is passed to it:
-
-* Discussed in [SYNC.md](../SYNC.md#how-do-you-install-it-in-gemfile-and-gemspec-then)

data/culture/gems/dependencies.yml

@@ -1,93 +0,0 @@
-bundler:
-  dependency: development
-
-nenv:
-  dependency: development
-
-dotenv:
-  dependency: development
-
-benchmark_suite:
-  dependency: development
-
-rubocop:
-  dependency: development
-
-transpec:
-  dependency: development
-
-pry:
-  dependency: development
-
-rake:
-  dependency: development
-
-rspec:
-  dependency: development
-
-listen:
-  version: '3.0.3'
-  dependency: development
-
-guard:
-  version: '2.13.0'
-  dependency: development
-
-guard-rspec:
-  dependency: development
-
-rspec-retry:
-  dependency: development
-
-coveralls:
-  dependency: development
-  gemfile:
-    require: false
-
-celluloid:
-  dependency: core
-  version: ">= 0.17.2"
-  gemfile:
-    github: celluloid/celluloid
-    branch: master
-    submodules: true
-
-celluloid-essentials:
-  dependency: module
-  gemfile:
-    github: celluloid/celluloid-essentials
-    branch: master
-    submodules: true
-
-celluloid-supervision:
-  dependency: module
-  gemfile:
-    github: celluloid/celluloid-supervision
-    branch: master
-    submodules: true
-
-celluloid-pool:
-  dependency: module
-  gemfile:
-    github: celluloid/celluloid-pool
-    branch: master
-    submodules: true
-
-celluloid-fsm:
-  dependency: module
-  gemfile:
-    github: celluloid/celluloid-fsm
-    branch: master
-    submodules: true
-
-celluloid-extras:
-  dependency: module
-  gemfile:
-    github: celluloid/celluloid-extras
-    branch: master
-    submodules: true
-
-timers:
-  version: ">= 4.1.1"
-  gemfile:
-    github: celluloid/timers

data/culture/gems/loader.rb

@@ -1,101 +0,0 @@
-require "yaml"
-
-module Celluloid
-  module Sync
-    module Gemfile
-      class << self
-        def [](dsl)
-          dsl.source("https://rubygems.org")
-          dsl.gemspec # Runs gemspec, but also @sets gem_name.
-          Gems.gemfile(dsl)
-        end
-      end
-    end
-    module Gemspec
-      class << self
-        def [](gem)
-          Gems.gemspec(gem)
-        end
-      end
-    end
-  end
-  module Gems
-    extend self
-    @gem_name = nil
-
-    undef gems rescue nil
-    def gems
-      File.expand_path("../dependencies.yml", __FILE__)
-    end
-
-    unless @dependencies ||= nil
-      @dependencies = YAML.load_file(gems) if File.exist?(gems)
-    end
-
-    unless @dependencies.is_a?(Hash) && @dependencies.any?
-      raise "Celluloid cannot find its dependencies."
-    end
-
-    undef core? rescue nil
-    def core?(name=@gem_name)
-      return false unless @dependencies[name].is_a? Hash
-      @dependencies[name]["dependency"] == "core"
-    end
-
-    undef separate? rescue nil
-    def separate?
-      !@dependencies.keys.include?(@gem_name)
-    end
-
-    undef gemspec rescue nil
-    def gemspec(gem)
-      @gem_name = gem.name
-      loader do |name, spec|
-        # Rules for dependencies, to avoid so-called circular dependency:
-        # - Only the core gem lists all the modules as runtime dependencies.
-        # - If this gem is not in the dependencies list, then it needs the core gem at runtime;
-        #   the module gems are development dependencies only. This is a depending separate gem.
-        #   There is the core gem, module gems, true dependencies, and separately depending gems.
-        # - If the dependency is a module, it is only a development dependency to other modules,
-        #   and even the core gem is a development dependency. It is not expected to be used alone.
-        meth = case spec["dependency"]
-               when "core", "module"
-                 # For the core gem, all modules are runtime dependencies.
-                 # For separate gems, only the core gem is a runtime dependency.
-                 if core? || (separate? && core?(name))
-                   :add_runtime_dependency
-                 else
-                   :add_development_dependency
-                 end
-               when "development"
-                 :add_development_dependency
-               else
-                 :add_dependency
-               end
-        gem.send(meth, name, spec["version"] || ">= 0")
-      end
-    end
-
-    undef gemfile rescue nil
-    def gemfile(dsl)
-      loader do |name, spec|
-        params = [name, spec["version"] || ">= 0"]
-        req = spec["gemfile"] || {}
-        params << req.each_with_object({}) { |(k, v), o| o[k.to_sym] = v }
-        current = dsl.dependencies.find { |d| d.name == name }
-        dsl.dependencies.delete(current) if current
-        dsl.gem(*params)
-      end
-    end
-
-    private
-
-    def loader
-      @dependencies.each do |name, spec|
-        next if name == @gem_name
-        spec ||= {}
-        yield name, spec
-      end
-    end
-  end
-end