|
1 |
| - |
2 |
| -Photo by [Rushen](https://www.flickr.com/photos/rushen/12171498934/in/photostream/) |
| 1 | + |
3 | 2 |
|
4 | 3 | [](https://search.maven.org/search?q=g:%22org.organicdesign%22%20AND%20a:%22Paguro%22)
|
5 | 4 | [](https://javadoc.io/doc/org.organicdesign/Paguro)
|
6 | 5 | [](https://travis-ci.org/GlenKPeterson/Paguro)
|
7 | 6 | [](https://codecov.io/gh/GlenKPeterson/Paguro)
|
| 7 | +[](https://groups.google.com/d/forum/paguro) |
8 | 8 |
|
9 | 9 | # Why Use Paguro?
|
10 | 10 |
|
11 |
| -Paguro is designed for two goals: |
12 |
| - 1. Make Functional Programming simpler AND easier in Java. |
| 11 | +Paguro is designed to: |
| 12 | + 1. Make Functional Programming simpler and easier in Java. |
13 | 13 | 2. Decrease the number of things you need to think about when coding.
|
14 | 14 |
|
15 |
| -If you spend your mental energies on distractions, that's less energy for creativity and problem-solving. |
| 15 | +Removing distractions leaves you more energy for creativity and problem-solving. |
16 | 16 | Paguro lets you forget about:
|
17 | 17 |
|
18 | 18 | * Potential modifications to shared collections (immutable collections are safe to share)
|
@@ -111,14 +111,19 @@ Unless otherwise stated, the rest of this work is licensed under the Apache 2.0
|
111 | 111 | New contributions should be made under the Apache 2.0 license whenever practical.
|
112 | 112 | I believe it is more popular, clearer, and has been better tested in courts of law.
|
113 | 113 |
|
| 114 | +Hermit Crab Photo by [Rushen](https://www.flickr.com/photos/rushen/12171498934/in/photostream/) |
| 115 | + |
114 | 116 | # Contributing
|
115 | 117 |
|
| 118 | +Questions? Ideas? Feedback? Use the [Google Group Email List](https://groups.google.com/d/forum/paguro). |
| 119 | +Clear bugs or simple pull requests can be made on Github without discussing them first on the email list. |
| 120 | + |
116 | 121 | If you submit a patch, please:
|
117 | 122 | - Keep the changes minimal (don't let your IDE reformat whole files).
|
118 | 123 | - Try to match the code style as best you can.
|
119 | 124 | - Clearly document your changes.
|
120 | 125 | - Update the unit tests to clearly and simply prove that your code works.
|
121 |
| - - It's a good idea to discuss proposed changes by opening an issue on github before you spend time coding. |
| 126 | + - It's a good idea to discuss proposed changes on the email list before you spend time coding. |
122 | 127 |
|
123 | 128 | ### Build from Source
|
124 | 129 |
|
|
0 commit comments