Read the docs, try following them. Update/enhance as needed. Generated copy at http://allura.sourceforge.net/
Notes from me & Jenny about what should be updated:
:::text grep for pyforge and "new forge", change to Allura http://allura.sourceforge.net/platform_tour.html move search from a tool to platform service remove home tool s/forum/discussion Ming Databases and the Context Object¶ drop project database txt most of the time the "context" stuff is automagically set by the request [Ticket:#151] can just be [#151], and it's not "TIcket" but name of tool [Commit#abac332a] wrong, should be [code:asdfasdf] or just [asdfasdf] "Asynchronous Processing¶" most of this will change soon "Migrations" delete http://allura.sourceforge.net/tutorials/wiki-tool.html need to write it delete the paster template too http://allura.sourceforge.net/tools.html remove all http://allura.sourceforge.net/platform.html s/why there are there./why they... s/(including me) // s/supper/super/ "Pluggable Event Listeners¶" delete http://allura.sourceforge.net/guides/message_bus.html change when changed http://allura.sourceforge.net/guides/email.html delete "The html2text tool ............. metadata in e-mail message bodies." delete Spam¶ http://allura.sourceforge.net/guides/markup.html change to a paragraph within another page, and mention the syntax help/examples within allura http://allura.sourceforge.net/guides/permissions.html s/both users and groups / groups/ s/admin_users// delete Tools are encouraged to prefix their permissions with the tool name, so for a tool called “tracker” a good permission name would be tracker_edit_ticket. Individual artifacts and ACL’s¶ add that this is mostly a platform service, and not exposed as a UI in the current tools copyright 2011, the Allura Team s/v0.1//
Tickets: #151
forge:db/1558
Log in to post a comment.
Notes from me & Jenny about what should be updated:
Related
Tickets:
#151forge:db/1558