text2048 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: e85082a7a9811119fd638e5dc7e163c670ea45fb
4
+ data.tar.gz: 6072216598424d89bc4ac20b4c8c62b507b87a8b
5
+ SHA512:
6
+ metadata.gz: dbf18ee75d43a5c61dbe9c866f0fdcef642b7321db7fe7d1e4d441acab10f517d1bce4a0c8aa5b6cee8e82510bd95a5e2cff3de3f0db4ecdc0eee737cd892ae2
7
+ data.tar.gz: 30a1bca88794b26870d799cc037339dbf6214672a54a65da00221a69871125982628dca00f974c52ef4ce409f207b2dc9ece7b6636171769a51d64e17399d7af
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,48 @@
1
+ ## Contributing
2
+ In the spirit of [free software][free-sw], **everyone** is encouraged to help
3
+ improve this project.
4
+
5
+ [free-sw]: http://www.fsf.org/licensing/essays/free-sw.html
6
+
7
+ Here are some ways *you* can contribute:
8
+
9
+ * by using alpha, beta, and prerelease versions
10
+ * by reporting bugs
11
+ * by suggesting new features
12
+ * by writing or editing documentation
13
+ * by writing specifications
14
+ * by writing code (**no patch is too small**: fix typos, add comments, clean up
15
+ inconsistent whitespace)
16
+ * by refactoring code
17
+ * by fixing [issues][]
18
+ * by reviewing patches
19
+ * [financially][gittip]
20
+
21
+ [issues]: https://github.com/yasuhito/text2048/issues
22
+ [gittip]: https://www.gittip.com/yasuhito/
23
+
24
+ ## Submitting an Issue
25
+ We use the [GitHub issue tracker][issues] to track bugs and features. Before
26
+ submitting a bug report or feature request, check to make sure it hasn't
27
+ already been submitted. When submitting a bug report, please include a [Gist][]
28
+ that includes a stack trace and any details that may be necessary to reproduce
29
+ the bug, including your gem version, Ruby version, and operating system.
30
+ Ideally, a bug report should include a pull request with failing specs.
31
+
32
+ [gist]: https://gist.github.com/
33
+
34
+ ## Submitting a Pull Request
35
+ 1. [Fork the repository.][fork]
36
+ 2. [Create a topic branch.][branch]
37
+ 3. Add specs for your unimplemented feature or bug fix.
38
+ 4. Run `bundle exec rake spec`. If your specs pass, return to step 3.
39
+ 5. Implement your feature or bug fix.
40
+ 6. Run `bundle exec rake default`. If your specs fail, return to step 5.
41
+ 7. Run `open coverage/index.html`. If your changes are not completely covered
42
+ by your tests, return to step 3.
43
+ 8. Add, commit, and push your changes.
44
+ 9. [Submit a pull request.][pr]
45
+
46
+ [fork]: http://help.github.com/fork-a-repo/
47
+ [branch]: http://learn.github.com/p/branching.html
48
+ [pr]: http://help.github.com/send-pull-requests/