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:
grep for pyforge and "new forge", change to Allura
move search from a tool to platform service
remove home tool
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]
most of this will change soon
need to write it
delete the paster template too
s/why there are there./why they...
s/(including me) //
"Pluggable Event Listeners¶"
change when changed
delete "The html2text tool ............. metadata in e-mail message bodies."
change to a paragraph within another page, and mention the syntax help/examples within allura
s/both users and groups / groups/
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
Log in to post a comment.