On Jan 10, 2011, at 1:01 PM, Jordan Kay wrote: > One idea I had: I can't believe a project as big as this has almost > zero documentation from what I understand. I use AppleDoc (http:// > www.gentlebytes.com/home/appledocapp/) to generate documentation for > my Cocoa projects in almost the exact same format as Apple's Cocoa > documentation. Would it be wise to simply go through some of the major > classes of the app and start understanding, documenting, cleaning them > up, and them adding the generated docsets to GitHub?
That sounds like a great way to handle the documentation. > For the more experienced, what do you suggest I branch off of from the > repository? We should be using the new repo under the Quicksilver account, not the one under Etienne's account (where unfortunately, all the issues were previously posted). If you don't already have access to it, send Patrick Robertson your GitHub username. https://github.com/quicksilver/Quicksilver It only seems to have one branch (which should be the B5X code). Etienne's copy has the B5X branch and a master branch which was a rewrite Alcor started. I know nothing about the state of that one. -- Rob McBroom <http://www.skurfer.com/>
