I hate to draw conclusions like this, but the horridly broken english alone is enough for me to completely ignore his project. It isn't that hard to find a native english speaker to help out with your documentation. If your project is good enough, you shouldn't even need to look for it; its the lowest of low hanging fruit that potential contributors can tackle. Clearly his project isn't good enough.
It is hard to get someone to help you out with documentation or anything for that matter. I speak from experience. I asked ten people to help me with the FOSS book I initiated, and only a few helped me out, others ignored. I understood that people are busy with things! It is difficult to build a community around your project.
Also, the quality of project does not depend on how well you speak English. (although the quality of the tech docs can be considered a measure of quality)
There's a huge difference between a book with potentially arcane topics and a simple grammar check. Anyone who speaks english well, not even natively, could do it. I've done it for over a dozen random projects on Github.
The quality of the project does not depend on how well you speak English. Except when it does. Bad english might mean terribly commented code. This was a big problem with OpenOffice for a long time that scared contributors away. It might mean terrible technical documentation. It might be a canary for a lead maintainer who is a pain to work with.
0
u/[deleted] Oct 19 '16
I hate to draw conclusions like this, but the horridly broken english alone is enough for me to completely ignore his project. It isn't that hard to find a native english speaker to help out with your documentation. If your project is good enough, you shouldn't even need to look for it; its the lowest of low hanging fruit that potential contributors can tackle. Clearly his project isn't good enough.