`testing.rst` has very old example code within `def setUp` Should we update that now too?
I think we should highlight the 'bitesize' ticket label on the mailing list, so other devs know about it and start using it. Perhaps link to it from the wiki too. At the very least on the wiki https://forge-allura.apache.org/p/allura/wiki/Contributing%20Code/ should gain a link to this new doc once its published. Forking on forge-allura.apache.org doesn't work currently since we're not running `git` on that server. I don't know what we should suggest at this point. But probably not something that doesn't work :( --- ** [tickets:#6896] Developer architecture docs** **Status:** code-review **Labels:** docs **Created:** Tue Nov 19, 2013 08:28 PM UTC by Dave Brondsema **Last Updated:** Thu Jan 02, 2014 08:53 PM UTC **Owner:** Tim Van Steenburgh It'd be useful to have some high-level docs for developers that are getting started with Allura. And update/overhaul our current developer-oriented doc pages. I think we should cover things like: how the code is organized, what technology is used (paster, TG, EW, jinja, etc), how to log & debug, how tests work, etc. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
