fusuma 2.0.0 → 2.0.5

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# 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 yhkyky@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and 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/

data/CONTRIBUTING.md

@@ -1,72 +0,0 @@
-# Contributing to Fusuma
-
-1. Fork the repo, develop and test your code changes.
-2. Send a pull request.
-
-## Setup
-
-In order to use the Fusuma console and run the project's tests,
-there is a small amount of setup:
-
-1. Install Ruby. Fusuma requires Ruby 2.3+. You may choose to
-   manage your Ruby and gem installations with [RVM](https://rvm.io/),
-   [rbenv](https://github.com/rbenv/rbenv), or
-   [chruby](https://github.com/postmodern/chruby).
-
-2. Install [Bundler](http://bundler.io/).
-
-   ```sh
-   $ gem install bundler
-   ```
-
-3. Install the top-level project dependencies.
-
-   ```sh
-   $ bundle install
-   ```
-
-## Fusuma Tests
-
-Tests are very important part of Fusuma. All contributions
-should include tests that ensure the contributed code behaves as expected.
-
-To run tests:
-
-``` sh
-$ bundle exec rspec
-```
-
-### Fusuma Document
-
-The project uses [YARD](https://github.com/lsegal/yard) for generating documentation.  
-
-If you're not sure about YARD, please refer to [YARD cheatsheet](https://gist.github.com/phansch/db18a595d2f5f1ef16646af72fe1fb0e).
-
-To run the Fusuma documentation tests:
-
-``` sh
-$ bundle exec yard --fail-on-warning
-```
-
-To check Fusuma documents with running local server:
-
-```
-$ bundle exec yard server
-```
-Then open (http://localhost:8808/)
-
-## Coding Style
-
-Please follow the established coding style in the library.
-The style is is largely based on [The Ruby Style Guide](https://github.com/bbatsov/ruby-style-guide).
-
-You can check your code against these rules by running Rubocop like so:
-
-```sh
-$ bundle exec rubocop
-```
-
-## Code of Conduct
-
-Please note that this project is released with a Contributor Code of Conduct. By
-participating in this project you agree to abide by its terms.

data/Gemfile

@@ -1,23 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in fusuma.gemspec
-gemspec
-
-gem 'bundler'
-gem 'coveralls'
-gem 'github_changelog_generator', '~> 1.14'
-gem 'pry-byebug', '~> 3.4'
-gem 'pry-doc'
-gem 'pry-inline'
-gem 'rake', '~> 13.0'
-gem 'rblineprof'
-gem 'rblineprof-report'
-gem 'reek'
-gem 'rspec', '~> 3.0'
-gem 'rubocop'
-gem 'rubocop-rake'
-gem 'rubocop-rspec'
-gem 'solargraph'
-gem 'yard'

data/Rakefile

@@ -1,15 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-task default: :spec
-
-require 'github_changelog_generator/task'
-
-GitHubChangelogGenerator::RakeTask.new :changelog do |config|
-  config.user = 'iberianpig'
-  config.project = 'fusuma'
-end