Bug 853269

Summary: RFE -- Ship default entities in brands
Product: [Community] Publican Reporter: Ruediger Landmann <rlandman>
Component: publicanAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED WONTFIX QA Contact: Ruediger Landmann <rlandman+disabled>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.0CC: rlandman+disabled
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-04 05:52:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ruediger Landmann 2012-08-30 23:59:51 UTC
Description of problem:
The "publican create" action generates an entities file for new books with some commonly useful entities pre-loaded into it. 

However, extra entities might be useful to a brand -- for example, a project might want to specify an entity that contains a URL to their bug tracker. Brands can already call new entities in their Common Content files, but without a corresponding entity in the .ent files of newly created books, these books will not build.

Brands might also want to provide defaults or overrides for the standard Publican-supplied entities; in particular, for the &HOLDER; entity, which is typically the same right across a project.

Version-Release number of selected component (if applicable):
3.0

Comment 1 Jeff Fearn 🐞 2012-09-04 05:52:54 UTC
Long stated policy is that we will not expand entity support in any way and we will kill it off if we get half a chance ... DocBook5 is at least a 45% chance.