I think all the effort you've put into open sourcing these modules is great! And one of the great things about open source is you don't have to worry if you don't have the time, someone else can easily step up. So don't stress about it! As I've mentioned, I'll be trying out your RPi:: libraries soon (most likely RPi::I2C first), so I'll get a little bit of exposure to them, and I can take a peek into the code :-) I'm pretty busy myself, but at the very least I can make some pull requests if I come across anything.
In general, what kind of tasks do the modules need done? I looked through all of your dists and repos, and it seems like most of the issues are reported by yourself, so I guess you've been using it as a to-do list? If you don't mind a suggestion, perhaps you have a few minutes of time to go through them and label the issues in some way that lets people judge the priority? I see you've added a couple of "enhancement" and "bug" labels, but there are some repos with no labels. Perhaps labels like "enhancement", "wishlist", "minor issue", "documentation", "bug", etc.?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
