Gabriela Gibson wrote on Sun, Dec 30, 2012 at 22:31:36 +0000: > But this would leave space for other projects. Does anyone have ideas > for good (relatively small) projects to help me learn the code base?
Perhaps pick a library and grep for "###|TODO|FIXME"? Investigating any one of them (and removing it, or fixing it) will get you familiar with some part of the code. Normally I'd have some concrete suggestions too, but fsfs is a moving target now (being refactored on a feature branch) and I don't recall offhand what outstanding TODOs related to the new-in-1.8 major features might be. I'd also like to suggest bindings work. Extending the C API's available to the bindings, or otherwise improving the bindings' usability to programmers, should have plenty of tasks of small-to-medium scale. (In addition to the swig/java/ctypes bindings, Brane has started work on C++ bindings --- you might ask him if there is a project opportunity for you there.) For some bindings the knowledge among devs of the bindings is not very high, and although someone opined on private it wasn't a suitable entry project I disagree. It will require working both with our C API and with the glue API --- that might make it a harder or trickier task, but I wouldn't rule it out without consideration. (And the C++ bindings, I expect, don't suffer having an opaque "glue" layer the way some other bindings do.) For completeness, svnpubsub has a bunch of TODOs (mostly in Ben and I's heads), but while it's a supported tool, it's not part of the core libraries. HTH
