Clarify the difference between the hacking tips and the style guidelines.
Replace "Code Review" with "Submitting a patch" (which in turn links to Code Review).
|Deletions are marked like this.||Additions are marked like this.|
|Line 24:||Line 24:|
|* [[Reviews|Code Review]]||* [[PatchSubmission|Submitting a patch]] The steps to get a patch into Launchpad.|
Launchpad Development Wiki
[This wiki is still very much a work in progress. When this notice disappears, that means it's still a work in progress, just not so much in progress that it demands a notice. The notice should go away before Launchpad is open sourced this July]
Launchpad is a suite of tools that help people and teams to work together on free software.
But if you're a heavy user of Launchpad who wants to help shape its future -- e.g. an Ubuntu Core Dev, MOTU, or Launchpad developer -- then this is the wiki for you.
Common Hacking Tips Finding your way around the Launchpad code.
Coding style guidelines How incoming code should look.
Submitting a patch The steps to get a patch into Launchpad.
VersionThreeDotO - feature plans and estimates for the mid-2009 major release
Parts of Launchpad
Translations - translating programs into multiple languages
Registry - people, projects and teams
This wiki is new and we're still moving information to it from other places:
Foundations - everything that holds Launchpad together
Bugs - the bug tracker
Code - version control
Answers - knowledge base
Blueprint - collaborative design
There are several possible causes:
The attribute does not exist. (This would normally cause an AttributeError.)
- The attribute is present in the database class, but not in the relevant interface class.
- The attribute is not named in the relevant ZCML file. This does not apply if the entire interface is allowed.
There is no corresponding interface.
This is not the same as Unauthorized. Unauthorized means that an authorization regime has been properly set up, but the current user is not authorized.