Looking for collaborators

[bluzi]

We're looking for people who would like to review and approve changes to the collection.
If you're interested and you already contributed to this repository before, you may apply by submitting a comment to this issue.

The goal is to grow and to make this repository as responsive to pull requests as possible.

[haloboy777]

I'd love to help.. 👍

[arminkhoshbin]

I'd be happy to help as well @bluzi

[CodeWritingCow]

I'd love to help too @bluzi

[roastchicken]

Although I just stumbled upon this and made my first PR about a minute ago, it seems interesting and I'd like to help get through the PR backlog.

[bluzi]

@haloboy777 @arminkhoshbin @CodeWritingCow @roastchicken

Welcome aboard!
Please click here and accept the invitation.

As you all can see, the project is getting more and more popular every day. People contributed about 400 PRs in less than a week, so feel free to merge name additions and translations, just make sure that the tests pass successfully, and that the changes make sense.

Please be nice to contributors, and create "thank you comments" after merging a PR.
I also like to help people fix their PRs when the test fails, by providing a guiding comment. Some of our contributors are not IT guys, so they may struggle with JSON and things like that.

Another important thing: Please reference every PR you merge to one or more of the following issues:

• Add a name (Easy PR, large impact) #1 - Name additions
• Translate a name #33 - Translations
• Add aliases  #87 - Aliases

That's about it. If you need anything, if you're not sure about a PR, or if you have any question or suggestion, feel free to @mention me or contact me via email: eliran013 AT gmail.com (replace the AT with @ of course), via Hangouts, or using the issue system in this repository.

Hopefully we all make some productive things together in the near future!

[roastchicken]

I'm assuming we shouldn't merge our own changes, just so another pair of eyes verifies any code. Let me know if you think otherwise @bluzi, or if anyone else has an opinion on this.

[bluzi]

@roastchicken
Yup, sounds reasonable.

[chrisf]

If you're still looking, I'd be happy to help

[bluzi]

Sure @chrisf, we could use some more help.
Welcome aboard!

Click here to accept the invitation

[bluzi]

@roastchicken @ChaosKaoz @arminkhoshbin @CodeWritingCow

There are some PRs with forever-pending Travis builds.
To solve this, please edit one of the files in the PR, and make a slight change (add space at the end or something), and commit your changes.

That should kick Travis and restart the build process.

Sorry for the inconvenience, it's a Travis bug.

[jonafrank]

If you want I can help to review, also contribute in the API. The project is interesting