[bip] developing tutorials, code samples, etc.

[Cory Tobin]

> - a discussion of how to write software packages that "don't suck",
>  i.e. a summary of Python standards, packaging, file naming
>  conventions, and basic test infrastructure, for people who don't
>  have any experience with that.

I think this should be one of the first things to be written so that
we don't have to go back and rewrite code that "does suck."


-----------------------------
Cory Tobin
ctobin at caltech.edu