Tom's DocImpact automation proposal <https://review.openstack.org/25887> got me thinking more generally about DocImpact and new features. I would like to propose to the opentack-dev mailing list that for commits that require doc changes ("DocImpact"), there must be sufficient information in the commit message for a member of the doc team to use this info to update the docs (i.e., we shouldn't need to go splunking through the code diff). If there isn't enough info in the commit log, then it should be socially acceptable to vote "-1" on the proposed code change. Does that sound reasonable? Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130611/76f012d6/attachment.html>