[openstack-dev] Newb looking to contribute

Jeff Learman jeff.learman at gmail.com
Sat Jun 27 19:33:43 UTC 2015

Big help!  Thanks to Dims, Steve, and Jay.

Jay, starting with unit tests does seem like a great way to get going for
the reasons you mentioned, plus limiting damage (though I realize messed up
tests could be a hassle too, if a foul-up gates patch commits.)  I think
I'll take some time getting acquainted with Nova, mox and mock.  Please
point me to any good mock tutorials you happen to know (though I can see
lots of them plus the official docs), or any other resources you think
might help me spin up.  After this, I'll start a new topic with
[openstack-dev][nova] regarding this subject (or whatever you recommend.)

Sorry to sound like someone from last century, but is "#openstack-nova" a
twitter account?  I've yet to use Twitter, but this could be a good time to
get started.  (I don't text much either.  Old-school.  Yeah, I even still
use 'vi' a lot!)


On Sat, Jun 27, 2015 at 3:01 PM, Jay Pipes <jaypipes at gmail.com> wrote:

> On 06/27/2015 11:06 AM, Jeff Learman wrote:
>> I'm an OpenStack newbie, but a seasoned programmer with decades of
>> experience in data communications (especially IP stack lower layers) and
>> embedded systems.  I'm fluent in Python, C, C++, and Java.
>> I'm looking for some pro-bono work to do, and am open to any
>> suggestions, advice, or pleas for help.  I'll need a bit of mentoring,
>> mostly in terms of mentioning terms to study up on.
>> I know about as much about OpenStack as I can learn from the Wikipedia
>> entry.  I started setting it up on Ubuntu on Cisco UCS for a project
>> where I worked, but no longer work there.  I don't have any resources
>> other than a Windows laptop and the Internet, but I could wrestle up an
>> x86-based Linux box if necessary (not a rack server, though -- low
>> budget, I'd take an old tower, install a new MOBO, and go from there.)
>> I'm willing to do tedious grunt work, as long as I'm learning something
>> in the process (at least, to begin with.)  For example, if there's a
>> desire to convert to Python 3, that'd be a great way to get involved,
>> learn a lot, and make a contribution, with minimal deep knowledge
>> required about OpenStack, and hopefully relatively minimal risk.
> Hi Jeff! Welcome to the OpenStack community! :)
> Dims and Steve had some great suggestions. I would add one specific
> low-hanging fruit item that wasn't on the nova-low-hanging-fruit etherpad
> until just now when I added it: unit test cleanups.
> There are a ton of unit tests in Nova that use the mox/stubout library
> instead of the (now-standard in Py3K) mock library. We'd love to get the
> older test cases slowly converted over time. Converting the test cases can
> be done in an iterative fashion; allows the submitter to learn new parts of
> the Nova source code in an slow, metered fashion; and the contributor can
> feel good about making test code easier to read and rationalize about.
> I'm on #openstack-nova most of the time. Feel free to hit me up with
> questions. Happy to assist ya :)
> Best,
> -jay
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150627/bdb460c2/attachment.html>

More information about the OpenStack-dev mailing list