Hi Folks, It's time to start publicizing the chandler2 codebase to encourage people to hack on it. That code doesn't yet have anything end-user useful, but it's the future of development.
I've set up http://chandler2.osafoundation.org/ to show the documentation Grant and I have been working on, and in the next week we'll do a blog post. How else should we update our documents? The wiki has all sorts of information that's of varying levels of accuracy for chandler1, usually less accurate for chandler2. I think we should: - Create a chandler2 wiki page, explaining how chandler2 differs from chandler1, and what broad features are the same (still Python, still cross platform, etc.). - Add a paragraph at the top of http://chandlerproject.org/Developers/WebHome explaining that that page applies to chandler1, developers looking to hack should look at chandler2 - Add some kind of explanation (probably a paragraph at the top) of http://chandlerproject.org/wikihome, since we link directly there from the chandlerproject.org landing page - Add a chandler2 link to the landing page sidebar How does that strike folks? Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
