Amp Redux: How to get involved

[Justin Love]

Ari Brown:

"It's worth STUDYING the old codebase, but it's mostly broken right
now. The comments are worth reading though, since they'll give you a
heads up for what's cool, what's not, and what parts of Mercurial are
driving us crazy. The latest release is good, but not the latest
checkout. Tests fail, things don't work, etc.

Glad you like the todo-list! I made it that way because I found it
useful for myself. Start with anything you think you can tackle. It's
semi-organized, so I'd recommend starting with the insects (trivial
bugs) or anything small, and moving up. The higher up you move, the
more you'll learn about the codebase. Inline documentation would be a
good task if you wanted, however your efforts would be for naught
since we're basically planning on scrapping it. Well, most of the
comments will be saved, so I guess it wouldn't really be for naught.
Give that a shot if you want – comment the Who, What, and Why for
important methods. Faster bit structs (we only need normal things,
like bits that are multiples of 2) is an easy one that doesn't need
knowledge of the codebase.

One thing you might like to try and solve is to find a way to deal
with remote repositories. If I pass in an HTTP URL, how do I know if
it's git or hg? I don't. So how do we specify? You don't even have to
code for this one; just come up with a plan and write it up."