Two small suggestions: clarify the documentation with regard to "the gem has to be xyz"; and a suggestion to test jim with regards to github uploads

[rubyFeedback]

Hey there duckinator,

I assume jim is in development flux, so that is fine.

When I read the main README, I saw this:

"Your gem needs to:

be pure Ruby"

I assume this refers primarily to e. g. no C extensions. However had, what exactly would "pure Ruby" mean?
Can we publish yaml files? How about .csv files or .md files or .txt files? Perhaps the README could clarify
this; I assume we can also publish other things, e. g. text files, which is why the requirement "pure" ruby
was a bit confusing.

I get it that jim can eventually be used to help with regard to publishing gems. This brings me to my
second suggestion. Would it be possible to use jim to publish gems on a github repository, as-is? Here
I assume that it would be the same author, so that author should be able to publish data on github. The
reason for this question is mostly to test out jim for those who wish to publish new gem releases, until
this can be done, be it at rubygems.org or coop eventually - or anywhere else such as github. It would be
very convenient if jim could work with as many different hosts as possible here; gives both users as well
as developers more flexibility. Anyway, these are just two tiny suggestions - please feel free to proceed
how you see fit, including closing this issue request at any moment in time. (I guess it may be resolved
"on its own" anyway in the future, if jim remains under active development eventually.)