Part of lp.registry.model.pillaraffiliation View In Hierarchy
Known subclasses: lp.registry.model.pillaraffiliation.BugTaskPillarAffiliation, lp.registry.model.pillaraffiliation.DistroSeriesPillarAffiliation, lp.registry.model.pillaraffiliation.ProductSeriesPillarAffiliation, lp.registry.model.pillaraffiliation.QuestionPillarAffiliation, lp.registry.model.pillaraffiliation.SpecificationPillarAffiliation
Subclasses may need to override getPillars() in order to provide the pillar entities for which affiliation is to be determined. A given context may supply for than one pillar for which affiliation can be determined. The default is just to use the context object directly.
|Method||getAffiliationBadges||Return the affiliation badge details for people given a context.|
|Method||_getAffiliation||Return the affiliation information for a person, if any.|
|Method||_getAffiliationTeamRoles||Return teams for which a person needs to belong, if affiliated.|
Subclasses will override this method to perform specific affiliation checks. The return result is a list of AffiliationRecord.
A person is affiliated with a pillar if they are in the list of drivers or are the maintainer.
Return the affiliation badge details for people given a context. There are 2 ways we check for affiliation: 1. Generic membership checks of particular teams as returned by _getAffiliationTeamRoles 2. Specific affiliation checks as performed by _getAffiliation