[pony-build] Next steps for Khushboo and Fatima

C. Titus Brown ctb at msu.edu
Wed Feb 24 09:55:31 PST 2010


Hey guys,

here are some ideas for more client-side work.

First, you could write some more build-scripts for Python packages.
Any one of the mock libraries (google 'python mock') would be great,
for example.  Or you could ask on the 'testing-in-python' list to see
who would like to volunteer their package.

One package that I know some people would like tested is 'mechanize'.

You could also test unittest2 under several different versions of Python.

At some point this kind of project will get really boring, but if you want
to continue gaining familiarity with pony-build and client-side stuff it
should be pretty straightforward.

--

Second, one of you could implement branch support for HgClone.  Right
now GitClone supports branches other than 'master', the default, while
HgClone does not support branches other than 'default'.  I know beans
about Mercurial, though, so this would be a reasonably independent
research project ;).  To get started, here are some things you could do --

 - look through the GitClone code in pony_client.py, specifically
   'create_repository';

 - look through the test code in client/test_client/test_git_client.py,
   specifically the test_other_branch functions;

 - sign up for bitbucket and fork my pony-build-hg-test repository, and
   set it up with multiple branches;

 - ...fix HgClone, add a test in test_hg_client.py, etc. etc. :)

I can hook you up with one of the Mercurial maintainers quite easily if you
need that level of expertise, BTW.  (You shouldn't but it's always nice to
have it on tap!)

--

And, of course, there's a whole list of ideas on the wiki, but some of them
are pretty big.

--

cheers,
--titus
-- 
C. Titus Brown, ctb at msu.edu



More information about the pony-build mailing list