Org has archiving and sorting built in, you can sort entries such that the completed ones sink to the bottom, and archive them to an archive file. With sparse

Org has archiving and sorting built in, you can sort entries such that the completed ones sink to the bottom, and archive them to an archive file. With sparse trees you can filter out uninteresting entries, and with org-goto jump around more easily. Frankly I haven't maintained any big or medium sized projects, and for anything with more than one regular committer I'd probably want to have something like Trac or Github or just make it a GNU project if applicable. Still though I can imagine using an org file in conjunction with a mailing list (a Google group, even), but I don't have practical experience with such setup. A Readme.org for me is a description of the project followed by notes and a hierarchy of issues i.e. to-do items. Also, when starting out sometimes I use src blocks to write initial bits of a script while exploring the data or the library I'm planning to work with.