Merge lp:~jcsackett/launchpad/unknown-blueprints-service-597738 into lp:launchpad

[j.c.sackett]

Updates the blueprints service page to use the blueprints_usage enum and display relevant data for each setting.

= Summary =

Updates the blueprints service to present relevant data for the UNKNOWN, EXTERNAL, and NOT_APPLICABLE settings of the blueprints_usage enum.

== Proposed fix ==

Modify the template and/or view to detect the usage status and present the correct template/info.

== Pre-implementation notes ==

Spoke with Curtis Hovey (sinzui) and Brad Crittenden (bac).

== Implementation details ==

The HasSpecificationsView has been updated to select a different template for contexts of Product, Distribution, and DistributionSeries in the event that the blueprints_usage enum indicates the context doesn't use Launchpad.

The new template presents slightly different information based on the enum case, and provides some basic controls if relevant (e.g. configure blueprints if the user has edit permissions).

== Tests ==

bin/test -vvcm lp.blueprints.browser

== Demo and Q/A ==

In Launchpad.dev, signed in as admin, go to http://blueprints.launchpad.dev/thunderbird. Try each configuration option and confirm that the presentation makes sense.

Linting changed files:
  lib/lp/answers/browser/questiontarget.py
  lib/lp/answers/doc/question.txt
  lib/lp/answers/doc/questionsets.txt
  lib/lp/app/enums.py
  lib/lp/blueprints/browser/configure.zcml
  lib/lp/blueprints/browser/specificationtarget.py
  lib/lp/blueprints/browser/tests/test_specificationtarget.py
  lib/lp/blueprints/templates/unknown-specs.pt
  lib/lp/registry/browser/distribution.py
  lib/lp/registry/browser/pillar.py
  lib/lp/registry/browser/productseries.py
  lib/lp/registry/browser/tests/distribution-views.txt
  lib/lp/registry/browser/tests/pillar-views.txt
  lib/lp/registry/browser/tests/product-views.txt
  lib/lp/registry/browser/tests/productseries-views.txt
  lib/lp/registry/browser/tests/projectgroup-views.txt
  lib/lp/registry/doc/distribution.txt
  lib/lp/registry/doc/product.txt
  lib/lp/registry/templates/distribution-index.pt
  lib/lp/registry/templates/distribution-search.pt
  lib/lp/registry/templates/distroseries-index.pt
  lib/lp/registry/templates/product-index.pt
  lib/lp/registry/templates/productseries-index.pt
  lib/lp/registry/templates/project-index.pt

Lint output corrupted by merged dependent branch.

[j.c.sackett (jcsackett)]

Sorry about the bad update. Just in case of divergences between the prereq and this post update from devel, here's the diff:

=== modified file 'lib/lp/blueprints/browser/configure.zcml'
--- lib/lp/blueprints/browser/configure.zcml 2010-07-27 17:17:59 +0000
+++ lib/lp/blueprints/browser/configure.zcml 2010-09-08 20:11:11 +0000
@@ -53,8 +53,7 @@
             name="+mdz-specs.csv"
             attribute="mdzCsv"/>
         <browser:page
- name="+specs"
- template="../templates/hasspecifications-specs.pt"/>
+ name="+specs"/>
         <browser:page
             name="+portlet-latestspecs"
             template="../templates/specificationtarget-portlet-latestspecs.pt"/>
@@ -500,8 +499,7 @@
             class="lp.blueprints.browser.specificationtarget.HasSpecificationsView"
             permission="zope.Public">
             <browser:page
- name="+specs"
- template="../templates/hasspecifications-specs.pt"/>
+ name="+specs"/>
         </browser:pages>
         <browser:page
             for="lp.blueprints.interfaces.specificationtarget.ISpecificationGoal"
@@ -532,8 +530,7 @@
             class="lp.blueprints.browser.specificationtarget.HasSpecificationsView"
             permission="zope.Public">
             <browser:page
- name="+specs"
- template="../templates/hasspecifications-specs.pt"/>
+ name="+specs"/>
             <browser:page
                 name="+portlet-latestspecs"
                 template="../templates/specificationtarget-portlet-latestspecs.pt"/>
@@ -583,8 +580,7 @@
         facet="specifications"
         permission="zope.Public">
         <browser:page
- name="+specs"
- template="../templates/hasspecifications-specs.pt"/>
+ name="+specs"/>
         <browser:page
             name="+portlet-latestspecs"
             template="../templates/specificationtarget-portlet-latestspecs.pt"/>

=== modified file 'lib/lp/blueprints/browser/specificationtarget.py'
--- lib/lp/blueprints/browser/specificationtarget.py 2010-08-24 10:45:57 +0000
+++ lib/lp/blueprints/browser/specificationtarget.py 2010-09-09 18:06:03 +0000
@@ -15,6 +15,7 @@

 from operator import itemgetter

+from z3c.ptcompat import ViewPageTemplateFile
 from zope.component import queryMultiAdapter

 from canonical.config import config
@@ -32,6 +33,8 @@
     Link,
     )
 from canonical.lazr.utils import smartquote
+from lp.app.enums import service_uses_launchpad
+from lp.app.interfaces.launchpad import IServiceUsage
 from lp.blueprints.interfaces.specification import (
     SpecificationFilter,
     SpecificationSort,
@@ -133,6 +136,50 @@
     is_sprint = False
     has_drivers = False

+ # Templates for the various conditions of blueprints:
+ # * On Launchpad
+ # * External
+ # * Disabled
+ # * Unknown
+ default_template = ViewPageTemplateFile(
+ '../templates/hasspecifications-specs.pt')
+ not_launchpad_template = ViewPageTemplateFile(
+ '../templates/unknown-specs.pt')
+
+ @property
+ def template(self):
+ # If the template has been defined in the zcml, use that, as t...

[Brad Crittenden (bac)]

Hi Jon,

Thanks for working on this branch. I was unaware of the added
complexity of the whole template/page/portlet mess.

I like the work you've done here modulo the on-going discussion with
Gary about a better approach to the template swapping. I'm marking
the MP 'needs information' so I can track the change you come up with,
but the branch is very close.

You mentioned lint being confused by the dependency on another
branch. Even so, please ensure these are not for real:

./lib/lp/blueprints/browser/specificationtarget.py
     251: E301 expected 1 blank line, found 0
     254: E301 expected 1 blank line, found 0
./lib/lp/blueprints/templates/unknown-specs.pt
      38: Line has trailing whitespace.
./lib/lp/registry/doc/distribution.txt
     582: source exceeds 78 characters.
     584: source exceeds 78 characters.

> === modified file 'lib/lp/blueprints/browser/specificationtarget.py'
> --- lib/lp/blueprints/browser/specificationtarget.py 2010-08-24 10:45:57 +0000
> +++ lib/lp/blueprints/browser/specificationtarget.py 2010-09-10 14:48:00 +0000
> @@ -15,6 +15,7 @@
>
> from operator import itemgetter
>
> +from z3c.ptcompat import ViewPageTemplateFile
> from zope.component import queryMultiAdapter
>
> from canonical.config import config
> @@ -32,6 +33,8 @@
> Link,
> )
> from canonical.lazr.utils import smartquote
> +from lp.app.enums import service_uses_launchpad
> +from lp.app.interfaces.launchpad import IServiceUsage
> from lp.blueprints.interfaces.specification import (
> SpecificationFilter,
> SpecificationSort,
> @@ -133,6 +136,50 @@
> is_sprint = False
> has_drivers = False
>
> + # Templates for the various conditions of blueprints:
> + # * On Launchpad
> + # * External
> + # * Disabled
> + # * Unknown
> + default_template = ViewPageTemplateFile(
> + '../templates/hasspecifications-specs.pt')
> + not_launchpad_template = ViewPageTemplateFile(
> + '../templates/unknown-specs.pt')
> +
> + @property
> + def template(self):
> + # If the template has been defined in the zcml, use that, as this
> + # isn't the base service page for blueprints.
> + if hasattr(self, 'index'):

As we discussed on IRC, you should use 'safe_hasattr' from
canonical.lazr.utils. Also, as I suggested please check around and
see if there is a more obvious technique for this. Sadly I cannot
offer any other solution.

> + return super(HasSpecificationsView, self).template
> +
> + # Sprints and Persons don't have a usage enum for blueprints, so we
> + # have to fallback to the default.
> + if (ISprint.providedBy(self.context)
> + or IPerson.providedBy(self.context)):
> + return self.default_template
> +
> + # ProjectGroups are a special case, as their products may be a
> + # combination of usage settings. Use the default, since it handles
> + # fetching anything that's set for ProjectGroups, and it's not correct
> + # to say anything about the ProjectGroup's usage.
> + if IProjectGroup.providedBy(self.context):
> + return self.default_template
> +
> + # If specific...

review: Needs Information (code)

[Curtis Hovey (sinzui)]

On Fri, 2010-09-10 at 15:59 +0000, Brad Crittenden wrote:
> > + @property
> > + def template(self):
> > + # If the template has been defined in the zcml, use that,
> as this
> > + # isn't the base service page for blueprints.
> > + if hasattr(self, 'index'):
>
> As we discussed on IRC, you should use 'safe_hasattr' from
> canonical.lazr.utils. Also, as I suggested please check around and
> see if there is a more obvious technique for this. Sadly I cannot
> offer any other solution.

We can abandon safe_hasattr when lpnet is on lucid. This issue was fixed
several years ago in pythong 2.6

[Brad Crittenden (bac)]

Good changes Jon. Please alphabetize the imports where you added safe_hasattr.

review: Approve (code)

[Guilherme Salgado (salgado)]

The UI changes look good to me, although it's confusing that the new template (lib/lp/blueprints/templates/unknown-specs.pt) uses the term "specification[s]" when the rest of the page uses "blueprint[s]". I think we should use only one of them, and most likely the preferred would be "blueprint[s]" as that's what is used in the top heading.

review: Needs Fixing (ui*)

[Curtis Hovey (sinzui)]

Gentleman, I think the reviewers and developers need to consider why we are making this change, and what we are really changing.

Our goal is to communicate to the user where certain kinds of activities are performed--which site does the user need to visit to complete his goal. Launchpad blueprints is a branded service that provides specifications and documentation. The page needs to be talking about "specifications and documentation" because other sites, most often wikis, do not use the term blueprints. We want to allow the users to provide a URL when they choose external (maybe repurpose the wiki field). The page is not really stating that Launchpad Blueprints allows the user to track specifications and documentation...I see no reason why I would turn the feature on since it does not have a sentence stating the basics of what it is for. Specification itself may be too technical. This app is essentially about planning and documenting features.

My other concern is about what has specifications--a SpecificationTarget. I reviewed the bugs branch a few days ago and saw only IProduct was supports well. A BugTarget may be a product, projectgroup, distribution, and distributionsourcepackage. I think these are also SpediciationTargets, so everyone needs to visit an example of each to ensure the message is correct and the actions that can be takes are presented. eg, a project group's use of an app is implicit in the settings of its products. I took a brief look at this branch in launchpad.dev and am pretty sure thunderbird is somewhat right, kubuntu, firefox and mozilla are wrong.

jcsackett, Salgado, take a look at the branch again from the perspective of kinds of users who are interested in feature planning.

review: Needs Fixing

[j.c.sackett (jcsackett)]

I just discovered I missed comments within the diff; sorry for not replying on Friday.

> If the enum is wrong, how will the user get here? The tab will be
> disabled, so we assume they have a direct URL?

I'm not sure the tab will be disabled--if no blueprints existed, and the enum said "EXTERNAL" or something, you could still get to this view so the "${Pillar} does not use blueprints" could be displayed. In this instance if it's set to EXTERNAL but people have been using the blueprints, we continue to display the blueprints information when you get here.

The involvement menu link is disabled, but the tab along the top of the page is still there, and of course nothing stops someone from going to blueprints.launchpad.net/$PILLAR.

Now, I'm open to debate on whether we should just turn off the feature regardless of whether or not blueprints are already being used--I erred on the side of not allowing someone to just delete a bunch of work, but that might not be the decision we want to make here.

>> self.verify_involvment(context)
>
> You didn't introduce it, but please fix the typo of s/verify_involment/verify_involvement/

Uhm, not sure what you mean--looks like it already is verify_involvement?

>> def test_adaptable_to_specificationtarget(self):
>> @@ -87,6 +92,63 @@
>> '<div id="involvement" class="portlet involvement">' in view())
>>
>>
>> +class TestHasSpecificationsTemplates(TestCaseWithFactory):
>> + """Tests the selection of templates based on blueprints usage."""
>> +
>> + layer = DatabaseFunctionalLayer
>> +
>> + def setUp(self):
>> + super(TestHasSpecificationsTemplates, self).setUp()
>> + self.user = self.factory.makePerson()
>> + self.product = self.factory.makeProduct()
>> + self.naked_product = removeSecurityProxy(self.product)
>> + login_person(self.user)
>
> While I'm not a prude, I must ask why all of the nakedness here?
> Couldn't you just make self.user be the owner of the product and
> proceed fully clothed?

I wanted to test what a non-owner user has happen here; that may be the same thing as self.user, but it may not--I've been bitten by using owners/admins in the past.

> Why use 'specifications' just the once? The page says 'blueprints'
> six times and it is unclear that specifications and blueprints are the
> same from the context.
>
> Should we be more frank:
>
> <project> tracks specifications somewhere besides Launchpad, but we
> don't know where. You should check with the project maintainers for
> the location.
>
> I'm just throwing that out for thought. I'm not sure I even like the idea.

I'm playing with this right now related to the UI review; neither blueprints nor specifications are totally right for the copy, per Curtis's comments.

But consider your comments thrown into the mix.

> Thanks for the additional drive-by fixes.

I do what I can. :-P

[Curtis Hovey (sinzui)]

On Mon, 2010-09-13 at 19:54 +0000, j.c.sackett wrote:
>
> The involvement menu link is disabled, but the tab along the top of
> the page is still there, and of course nothing stops someone from
> going to blueprints.launchpad.net/$PILLAR.
>
> Now, I'm open to debate on whether we should just turn off the feature
> regardless of whether or not blueprints are already being used--I
> erred on the side of not allowing someone to just delete a bunch of
> work, but that might not be the decision we want to make here.

The complaint from project owners is that users created blueprints on
Launchpad instead of the upstream wiki. The project owner can enable
blueprints if he chooses to. Blueprints should be off until enabled.

I went to firefox in lp.dev and saw blueprints on. As the owner of the
project I decided to turn blueprints off, so I choses the configure
link, and was surprised that Blueprints was off. More over, Saving the
state of unknown did not disable blueprints. The state of the app does
not work like answers. Remember, we are working on other applications to
ensure all apps have the same kind of behaviours.

--
__Curtis C. Hovey_________
http://launchpad.net/

[j.c.sackett (jcsackett)]

> The complaint from project owners is that users created blueprints on
> Launchpad instead of the upstream wiki. The project owner can enable
> blueprints if he chooses to. Blueprints should be off until enabled.
>
> I went to firefox in lp.dev and saw blueprints on. As the owner of the
> project I decided to turn blueprints off, so I choses the configure
> link, and was surprised that Blueprints was off. More over, Saving the
> state of unknown did not disable blueprints. The state of the app does
> not work like answers. Remember, we are working on other applications to
> ensure all apps have the same kind of behaviours.

I can buy this argument, totally. I've removed the conditional that prioritizes the existence of blueprints over the status of the enum.

[j.c.sackett (jcsackett)]

> Our goal is to communicate to the user where certain kinds of activities are
> performed--which site does the user need to visit to complete his goal.
> Launchpad blueprints is a branded service that provides specifications and
> documentation. The page needs to be talking about "specifications and
> documentation" because other sites, most often wikis, do not use the term
> blueprints.

Given this, I've updated the template to refer to the notion of documentation, and feature planning. In the instance where blueprints is set active, I've left the template alone, as the process of setting it up tells the user that Blueprints is a branded way that Launchpad does feature planning and documentation.

> We want to allow the users to provide a URL when they choose
> external (maybe repurpose the wiki field).

Based on our prior conversation I thought we were going to simply default to "There is a wiki for this project, which may be used for this purpose," with a link to the wiki if it exists, rather than introducing an extra db field to track an external specification tracking url.

I do think it may be worthwhile to circle back and add that field and get that information (for blueprints, answers, and translations) so we can provide a specific external place, but I think those changes are out of scope for this branch.

> The page is not really stating that
> Launchpad Blueprints allows the user to track specifications and
> documentation...I see no reason why I would turn the feature on since it does
> not have a sentence stating the basics of what it is for.

Agreed; I've updated what the page says to address this.

An incremental diff with these changes is attached.

I'll be addressing your other concerns re: specificationtarget next.

[j.c.sackett (jcsackett)]

> My other concern is about what has specifications--a SpecificationTarget. I
> reviewed the bugs branch a few days ago and saw only IProduct was supports
> well.

Valid; I've done some digging and have some explanations below.

> A BugTarget may be a product, projectgroup, distribution, and
> distributionsourcepackage. I think these are also SpediciationTargets, so
> everyone needs to visit an example of each to ensure the message is correct
> and the actions that can be takes are presented. eg, a project group's use of
> an app is implicit in the settings of its products.

So, I think products are now handled right.

Project groups are tricky--right now I have it defaulting to the old style, so that any blueprints made for any project will be shown. Given how the earlier question of whether or not to continue showing blueprints if has_any_specifications was True, I think it is appropriate to only turn this on if at least one product has LAUNCHPAD as its usage setting.

Distributions were mostly handled right; the issue with say, Kubuntu was the configure_blueprints link, which I fixed.

DSPs aren't valid for blueprints; it's always NOT_APPLICABLE and the links are all disabled. You can't even get to it by going to blueprints.launchpad.net for the DSP in question; it takes you to the overview. (see https://blueprints.edge.launchpad.net/ubuntu/+source/firefox or https://blueprints.launchpad.dev/ubuntu/+source/mozilla-firefox)

Attached is a diff of this round of changes.

[Curtis Hovey (sinzui)]

On Tue, 2010-09-14 at 19:16 +0000, j.c.sackett wrote:
> Project groups are tricky--right now I have it defaulting to the old
> style, so that any blueprints made for any project will be shown.
> Given how the earlier question of whether or not to continue showing
> blueprints if has_any_specifications was True, I think it is
> appropriate to only turn this on if at least one product has LAUNCHPAD
> as its usage setting.

I do not this this rule is right. PillarView that renders the
Involvement Portlet and the "Register a Blueprint" link only shows the
link on a project group if a sub project has enabled it. The involvement
portlet is controlled by the pillar owners and its links are enabled to
attack contributors to the applications the pillar uses.

We do not want the Involvement portlet to contradict the app page, which
is the reason we need to disable apps for unknown, not applicable, and
external (most of the time). Answers uses the involvement portlet to
decide the state to ensure it never contradicts. I expect all the apps
do do something similar so that we have a DRY implementation.

        involvement = getMultiAdapter(
            (self.context, self.request), name='+get-involved')
        if service_uses_launchpad(involvement.answers_usage):
            # enable the listing.

--
__Curtis C. Hovey_________
http://launchpad.net/

[j.c.sackett (jcsackett)]

I like the multiAdapter strategy you showed and have put it in place of the for loop.

[Guilherme Salgado (salgado)]

Hi Jon,

This looks good, and I only have a couple suggestions.

s/use// @ "[...] does not track use feature planning or documentation."

And for bonus points you could change the 'Configure blueprints' text according to the state the context is in. For example, in the UNKNOWN state, it could be changed to "Tell us how <project> tracks feature planning and documentation". Similarly, for the EXTERNAL (and maybe NOT_APPLICABLE as well?) state, it could be "Use Launchpad to track feature planning and documentation", although that's a bit of a lie as there are other things you can do by following that link (but then it should be a worthy tradeoff if our goal is to get people to use blueprints).

review: Approve (ui*)

[Curtis Hovey (sinzui)]

I think this is good to land, with the fixing of some link test. I suspect there are some other issues we will see when this feature is used with real data.

Thanks Salgado for seeing the problem in the enums. I see a similar issue with this link test: 'Enable tracking of specifications and meetings'. meetings, AKA sprints do not belong to projects or teams. They are always available because they are a cross-project/cross-team feature. The link is enabling the project to use Launcpads feature planning and documentation tracking features.

[Curtis Hovey (sinzui)]

Doh. My comment was intended to be UI approve.

review: Approve (ui)

=== modified file 'lib/lp/blueprints/browser/configure.zcml'
--- lib/lp/blueprints/browser/configure.zcml	2010-07-27 17:17:59 +0000
+++ lib/lp/blueprints/browser/configure.zcml	2010-09-17 14:23:57 +0000
@@ -53,8 +53,7 @@
             name="+mdz-specs.csv"
             attribute="mdzCsv"/>
         <browser:page
-            name="+specs"
-            template="../templates/hasspecifications-specs.pt"/>
+            name="+specs"/>
         <browser:page
             name="+portlet-latestspecs"
             template="../templates/specificationtarget-portlet-latestspecs.pt"/>
@@ -500,8 +499,7 @@
             class="lp.blueprints.browser.specificationtarget.HasSpecificationsView"
             permission="zope.Public">
             <browser:page
-                name="+specs"
-                template="../templates/hasspecifications-specs.pt"/>
+                name="+specs"/>
         </browser:pages>
         <browser:page
             for="lp.blueprints.interfaces.specificationtarget.ISpecificationGoal"
@@ -532,8 +530,7 @@
             class="lp.blueprints.browser.specificationtarget.HasSpecificationsView"
             permission="zope.Public">
             <browser:page
-                name="+specs"
-                template="../templates/hasspecifications-specs.pt"/>
+                name="+specs"/>
             <browser:page
                 name="+portlet-latestspecs"
                 template="../templates/specificationtarget-portlet-latestspecs.pt"/>
@@ -583,8 +580,7 @@
         facet="specifications"
         permission="zope.Public">
         <browser:page
-            name="+specs"
-            template="../templates/hasspecifications-specs.pt"/>
+            name="+specs"/>
         <browser:page
             name="+portlet-latestspecs"
             template="../templates/specificationtarget-portlet-latestspecs.pt"/>

=== modified file 'lib/lp/blueprints/browser/specificationtarget.py'
--- lib/lp/blueprints/browser/specificationtarget.py	2010-09-14 23:42:27 +0000
+++ lib/lp/blueprints/browser/specificationtarget.py	2010-09-17 14:23:57 +0000
@@ -15,7 +15,11 @@
 
 from operator import itemgetter
 
-from zope.component import queryMultiAdapter
+from z3c.ptcompat import ViewPageTemplateFile
+from zope.component import (
+    getMultiAdapter,
+    queryMultiAdapter,
+    )
 
 from canonical.config import config
 from canonical.launchpad import _
@@ -25,13 +29,19 @@
     canonical_url,
     LaunchpadView,
     )
+from canonical.launchpad.webapp.authorization import check_permission
 from canonical.launchpad.webapp.batching import BatchNavigator
 from canonical.launchpad.webapp.breadcrumb import Breadcrumb
 from canonical.launchpad.webapp.menu import (
     enabled_with_permission,
     Link,
     )
-from canonical.lazr.utils import smartquote
+from canonical.lazr.utils import (
+    safe_hasattr,
+    smartquote,
+    )
+from lp.app.enums import service_uses_launchpad
+from lp.app.interfaces.launchpad import IServiceUsage
 from lp.blueprints.interfaces.specification import (
     SpecificationFilter,
     SpecificationSort,
@@ -131,21 +141,76 @@
     is_project = False
     is_series = False
     is_sprint = False
+    has_wiki = False
     has_drivers = False
 
+    # Templates for the various conditions of blueprints:
+    # * On Launchpad
+    # * External
+    # * Disabled
+    # * Unknown
+    default_template = ViewPageTemplateFile(
+        '../templates/hasspecifications-specs.pt')
+    not_launchpad_template = ViewPageTemplateFile(
+        '../templates/unknown-specs.pt')
+
+    @property
+    def template(self):
+        # Check for the magical "index" added by the browser:page template
+        # machinery. If it exists this is actually the
+        # zope.app.pagetemplate.simpleviewclass.simple class that is magically
+        # mixed in by the browser:page zcml directive the template defined in
+        # the directive should be used.
+        if safe_hasattr(self, 'index'):
+            return super(HasSpecificationsView, self).template
+
+        # Sprints and Persons don't have a usage enum for blueprints, so we
+        # have to fallback to the default.
+        if (ISprint.providedBy(self.context)
+            or IPerson.providedBy(self.context)):
+            return self.default_template
+
+        # ProjectGroups are a special case, as their products may be a
+        # combination of usage settings. To deal with this, check all
+        # products via the involvment menu.
+        if (IProjectGroup.providedBy(self.context)
+            or IProjectGroupSeries.providedBy(self.context)):
+            involvement = getMultiAdapter(
+                (self.context, self.request),
+                name='+get-involved')
+            if service_uses_launchpad(involvement.blueprints_usage):
+                return self.default_template
+            else:
+                return self.not_launchpad_template
+
+        # Otherwise, determine usage and provide the correct template.
+        service_usage = IServiceUsage(self.context)
+        if service_uses_launchpad(service_usage.blueprints_usage):
+            return self.default_template
+        else:
+            return self.not_launchpad_template
+
+    def render(self):
+        return self.template()
+
     # XXX: jsk: 2007-07-12 bug=173972: This method might be improved by
     # replacing the conditional execution with polymorphism.
     def initialize(self):
         if IPerson.providedBy(self.context):
             self.is_person = True
-        elif (IDistribution.providedBy(self.context) or
-              IProduct.providedBy(self.context)):
-            self.is_target = True
-            self.is_pillar = True
+        elif IDistribution.providedBy(self.context):
+            self.is_target = True
+            self.is_pillar = True
+            self.show_series = True
+        elif IProduct.providedBy(self.context):
+            self.is_target = True
+            self.is_pillar = True
+            self.has_wiki = True
             self.show_series = True
         elif IProjectGroup.providedBy(self.context):
             self.is_project = True
             self.is_pillar = True
+            self.has_wiki = True
             self.show_target = True
             self.show_series = True
         elif IProjectGroupSeries.providedBy(self.context):
@@ -170,6 +235,16 @@
             size=config.launchpad.default_batch_size)
 
     @property
+    def can_configure_blueprints(self):
+        """Can the user configure blueprints for the `ISpecificationTarget`.
+        """
+        target = self.context
+        if IProduct.providedBy(target) or IDistribution.providedBy(target):
+            return check_permission('launchpad.Edit', self.context)
+        else:
+            return False
+
+    @property
     def label(self):
         mapping = {'name': self.context.displayname}
         if self.is_person:
@@ -199,7 +274,7 @@
             'distroseries',
             'direction_approved',
             'man_days',
-            'delivery'
+            'delivery',
             ]
         def dbschema(item):
             """Format a dbschema sortably for a spreadsheet."""

=== modified file 'lib/lp/blueprints/browser/tests/test_specificationtarget.py'
--- lib/lp/blueprints/browser/tests/test_specificationtarget.py	2010-09-15 00:07:54 +0000
+++ lib/lp/blueprints/browser/tests/test_specificationtarget.py	2010-09-17 14:23:57 +0000
@@ -1,8 +1,12 @@
-# Copyright 2009 Canonical Ltd.  This software is licensed under the
+# Copyright 2009-2010 Canonical Ltd.  This software is licensed under the
 # GNU Affero General Public License version 3 (see the file LICENSE).
 
 __metaclass__ = type
 
+import unittest
+
+from zope.security.proxy import removeSecurityProxy
+
 from canonical.launchpad.webapp.batching import BatchNavigator
 from canonical.launchpad.testing.pages import find_tag_by_id
 from canonical.testing.layers import DatabaseFunctionalLayer
@@ -10,6 +14,8 @@
     IHasSpecifications,
     ISpecificationTarget,
     )
+from lp.app.enums import ServiceUsage
+from lp.blueprints.browser.specificationtarget import HasSpecificationsView
 from lp.blueprints.publisher import BlueprintsLayer
 from lp.testing import (
     login_person,
@@ -53,7 +59,7 @@
         self.verify_view(context, 'sprints/%s' % context.name)
 
 
-class TestHasSpecificationsView(TestCaseWithFactory):
+class TestHasSpecificationsViewInvolvement(TestCaseWithFactory):
     """Test specification menus links."""
     layer = DatabaseFunctionalLayer
 
@@ -71,10 +77,17 @@
 
     def test_specificationtarget(self):
         context = self.factory.makeProduct(name='almond')
+        naked_product = removeSecurityProxy(context)
+        naked_product.blueprints_usage = ServiceUsage.LAUNCHPAD
         self.verify_involvment(context)
 
     def test_adaptable_to_specificationtarget(self):
+        # A project should adapt to the products within to determine
+        # involvment.
         context = self.factory.makeProject(name='hazelnut')
+        product = self.factory.makeProduct(project=context)
+        naked_product = removeSecurityProxy(product)
+        naked_product.blueprints_usage = ServiceUsage.LAUNCHPAD
         self.verify_involvment(context)
 
     def test_sprint(self):
@@ -128,4 +141,115 @@
             find_tag_by_id(content, 'upper-batch-nav-batchnav-next')['class'])
         self.assertEqual('next',
             find_tag_by_id(content, 'lower-batch-nav-batchnav-next')['class'])
-        
+
+
+class TestHasSpecificationsTemplates(TestCaseWithFactory):
+    """Tests the selection of templates based on blueprints usage."""
+
+    layer = DatabaseFunctionalLayer
+
+    def setUp(self):
+        super(TestHasSpecificationsTemplates, self).setUp()
+        self.user = self.factory.makePerson()
+        login_person(self.user)
+
+    def _test_templates_for_configuration(self, target, context=None):
+        if context is None:
+            context = target
+        naked_target = removeSecurityProxy(target)
+        test_configurations = [
+            ServiceUsage.UNKNOWN,
+            ServiceUsage.EXTERNAL,
+            ServiceUsage.NOT_APPLICABLE,
+            ServiceUsage.LAUNCHPAD,
+            ]
+        correct_templates = [
+            HasSpecificationsView.not_launchpad_template.filename,
+            HasSpecificationsView.not_launchpad_template.filename,
+            HasSpecificationsView.not_launchpad_template.filename,
+            HasSpecificationsView.default_template.filename,
+            ]
+        used_templates = list()
+        for config in test_configurations:
+            naked_target.blueprints_usage = config
+            view = create_view(
+                context,
+                '+specs',
+                layer=BlueprintsLayer,
+                principal=self.user)
+            used_templates.append(view.template.filename)
+        self.assertEqual(correct_templates, used_templates)
+
+    def test_product(self):
+        product = self.factory.makeProduct()
+        self._test_templates_for_configuration(product)
+
+    def test_product_series(self):
+        product = self.factory.makeProduct()
+        product_series = self.factory.makeProductSeries(product=product)
+        self._test_templates_for_configuration(
+            target=product,
+            context=product_series)
+
+    def test_distribution(self):
+        distribution = self.factory.makeDistribution()
+        self._test_templates_for_configuration(distribution)
+
+    def test_distroseries(self):
+        distribution = self.factory.makeDistribution()
+        distro_series = self.factory.makeDistroSeries(
+            distribution=distribution)
+        self._test_templates_for_configuration(
+            target=distribution,
+            context=distro_series)
+
+    def test_projectgroup(self):
+        project = self.factory.makeProject()
+        product1 = self.factory.makeProduct(project=project)
+        product2 = self.factory.makeProduct(project=project)
+        self._test_templates_for_configuration(
+            target=product1,
+            context=project)
+
+
+class TestHasSpecificationsConfiguration(TestCaseWithFactory):
+
+    layer = DatabaseFunctionalLayer
+
+    def test_cannot_configure_blueprints_product_no_edit_permission(self):
+        product = self.factory.makeProduct()
+        view = create_initialized_view(product, '+specs')
+        self.assertEqual(False, view.can_configure_blueprints)
+
+    def test_can_configure_blueprints_product_with_edit_permission(self):
+        product = self.factory.makeProduct()
+        login_person(product.owner)
+        view = create_initialized_view(product, '+specs')
+        self.assertEqual(True, view.can_configure_blueprints)
+
+    def test_cant_configure_blueprints_distribution_no_edit_permission(self):
+        distribution = self.factory.makeDistribution()
+        view = create_initialized_view(distribution, '+specs')
+        self.assertEqual(False, view.can_configure_blueprints)
+
+    def test_can_configure_blueprints_distribution_with_edit_permission(self):
+        distribution = self.factory.makeDistribution()
+        login_person(distribution.owner)
+        view = create_initialized_view(distribution, '+specs')
+        self.assertEqual(True, view.can_configure_blueprints)
+
+    def test_cannot_configure_blueprints_projectgroup(self):
+        project_group = self.factory.makeProject()
+        login_person(project_group.owner)
+        view = create_initialized_view(project_group, '+specs')
+        self.assertEqual(False, view.can_configure_blueprints)
+
+
+def test_suite():
+    suite = unittest.TestSuite()
+    suite.addTest(unittest.TestLoader().loadTestsFromName(__name__))
+    return suite
+
+
+if __name__ == '__main__':
+    unittest.TextTestRunner().run(test_suite())

=== modified file 'lib/lp/blueprints/stories/blueprints/xx-creation.txt'
--- lib/lp/blueprints/stories/blueprints/xx-creation.txt	2010-08-26 02:30:06 +0000
+++ lib/lp/blueprints/stories/blueprints/xx-creation.txt	2010-09-17 14:23:57 +0000
@@ -1,7 +1,26 @@
-= Creating Blueprints =
-
-
-== Introduction ==
+Creating Blueprints
+===================
+
+Set Up
+------
+A number of tests in this need a product with blueprints enabled, so we'll
+enable them on bazaar, firefox, and jokosher.
+
+    >>> from zope.component import getUtility
+    >>> from lp.app.enums import ServiceUsage
+    >>> from lp.registry.interfaces.product import IProductSet
+    >>> login('[e-mail]')
+    >>> bazaar = getUtility(IProductSet).getByName('bzr')
+    >>> bazaar.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> firefox = getUtility(IProductSet).getByName('firefox')
+    >>> firefox.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> jokosher = getUtility(IProductSet).getByName('jokosher')
+    >>> jokosher.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> transaction.commit()
+    >>> logout()
+
+Introduction
+------------
 
 Users can register blueprints from many locations in Launchpad. To start with,
 it's possible to register a blueprint from the Blueprints home page. However,
@@ -15,7 +34,9 @@
  * a sprint
 
 
-== The blueprint registration form ==
+The blueprint registration form
+-------------------------------
+
 
 Launchpad provides a dedicated form page for users to register blueprints.
 Generally speaking, users can navigate to this form from each of the supported
@@ -28,13 +49,15 @@
 we'll use extra care when its necessary to demonstrate that they both exist.
 
 
-== Navigating to the blueprint registration form ==
+Navigating to the blueprint registration form
+---------------------------------------------
 
 We'll start by demonstrating that users can navigate to the blueprint
 registration form from each of the supported locations.
 
 
-=== From the Blueprints home page ===
+From the Blueprints home page
+.............................
 
 Starting from the Blueprints home page:
 
@@ -46,7 +69,8 @@
     <a href="+new" id="addspec"> <img alt="Register a blueprint"...
 
 
-=== From a distribution ===
+From a distribution
+...................
 
 Starting from the Ubuntu distribution page:
 
@@ -68,7 +92,8 @@
        class="menu-link-new...>Register a blueprint</a>
 
 
-=== From a distribution series ===
+From a distribution series
+..........................
 
 Starting from the Ubuntu Hoary distribution series page:
 
@@ -83,7 +108,8 @@
        class="menu-link-new...>Register a blueprint</a>
 
 
-=== From a product ===
+From a product
+..............
 
 Starting from the Bazaar product page:
 
@@ -109,7 +135,8 @@
     >>> print extract_text(find_main_content(user_browser.contents))
     Register a new blueprint...
 
-=== From a product series ===
+From a product series
+.....................
 
 Starting from the Mozilla Firefox product series page:
 
@@ -125,7 +152,8 @@
        class="menu-link-new...>Register a blueprint</a>
 
 
-=== From a project ===
+From a project
+..............
 
 Starting from the Mozilla project page:
 
@@ -140,7 +168,8 @@
        class="menu-link-new...>Register a blueprint</a>
 
 
-=== From a sprint ===
+From a sprint
+.............
 
 Starting from the Future Mega Meeting sprint page:
 
@@ -155,14 +184,16 @@
        class="menu-link-new...>Register a blueprint</a>
 
 
-== Registering a blueprint ==
+Registering a blueprint
+-----------------------
 
 The blueprint registration form allows users to register a blueprint. The
 appearance and behaviour of the form depends on where the user has navigated
 from.
 
 
-=== Registering a blueprint from the Blueprints home page ===
+Registering a blueprint from the Blueprints home page
+.....................................................
 
 We'll start from the default blueprint registration form:
 
@@ -216,7 +247,8 @@
     Network Magic: Auto Network Detection...
 
 
-=== Registering a blueprint from a distribution ===
+Registering a blueprint from a distribution
+...........................................
 
 When a blueprint is registered from a distribution, the new blueprint is
 automatically targeted to the distribution.
@@ -239,7 +271,8 @@
     Network Magic: Auto Network Detection...
 
 
-=== Registering a blueprint from a distribution series ===
+Registering a blueprint from a distribution series
+..................................................
 
 When a blueprint is registered from a distribution series, the new blueprint
 is automatically targeted to the parent distribution. In addition, Launchpad
@@ -326,7 +359,8 @@
     Series goal: Accepted for hoary
 
 
-=== Registering a blueprint from a product ===
+Registering a blueprint from a product
+......................................
 
 When a blueprint is registered from a product, the new blueprint is
 automatically targeted to the product.
@@ -355,7 +389,8 @@
     SVG Support...
 
 
-=== Registering a blueprint from a product series ===
+Registering a blueprint from a product series
+.............................................
 
 When a blueprint is registered from a product series, the new blueprint is
 automatically targeted to the parent product. In addition, Launchpad allows
@@ -437,7 +472,8 @@
     Series goal: Accepted for 1.0
 
 
-=== Registering a blueprint from a project ===
+Registering a blueprint from a project
+......................................
 
 Let's register a blueprint from the Mozilla project:
 
@@ -470,7 +506,8 @@
     SVG Support...
 
 
-=== Registering a blueprint from a sprint ===
+Registering a blueprint from a sprint
+.....................................
 
 When a blueprint is registered from a sprint, the new blueprint is
 automatically proposed as a topic for discussion at the sprint.
@@ -532,7 +569,8 @@
     <...darcs-imports-2...
 
 
-=== Proposing any blueprint as a sprint topic during registration ===
+Proposing any blueprint as a sprint topic during registration
+.............................................................
 
 While blueprints can be registered from sprints directly, it's also possible
 to propose any blueprint for discussion at a sprint during registration.
@@ -559,10 +597,11 @@
     <...spec-for-sprint...>
 
 
-== Restrictions when registering blueprints ==
-
-
-=== Names must be unique ===
+Restrictions when registering blueprints
+----------------------------------------
+
+Names must be unique
+....................
 
 It's not possible to register a blueprint with the same name as an existing
 blueprint.
@@ -602,7 +641,8 @@
     There is 1 error...already in use by another blueprint...
 
 
-=== Names must be valid ===
+Names must be valid
+...................
 
 Blueprint names must conform to a set pattern:
 
@@ -635,7 +675,8 @@
     Network Magic: Automatic Network Detection...
 
 
-=== URLs must be unique ===
+URLs must be unique
+...................
 
 It's not possible to register a blueprint with the same URL as an existing
 blueprint:
@@ -653,7 +694,8 @@
     There is 1 error...already registered by another blueprint...
 
 
-=== Registering blueprints from other locations ===
+Registering blueprints from other locations
+...........................................
 
 There are some locations in Launchpad from which it's not possible to register
 a blueprint. To start with, it's not possible to register a blueprint from an

=== modified file 'lib/lp/blueprints/stories/blueprints/xx-productseries.txt'
--- lib/lp/blueprints/stories/blueprints/xx-productseries.txt	2010-08-26 02:30:06 +0000
+++ lib/lp/blueprints/stories/blueprints/xx-productseries.txt	2010-09-17 14:23:57 +0000
@@ -2,6 +2,18 @@
 Targeting to ProductSeries
 ==========================
 
+A number of tests in this need a product with blueprints enabled, so we'll
+enable them on firefox.
+
+    >>> from zope.component import getUtility
+    >>> from lp.app.enums import ServiceUsage
+    >>> from lp.registry.interfaces.product import IProductSet
+    >>> login('[e-mail]')
+    >>> firefox = getUtility(IProductSet).getByName('firefox')
+    >>> firefox.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> transaction.commit()
+    >>> logout()
+
 In terms of feature management for release series and for distroseriess, we
 want to target one of these specs to the 1.0 series. We will use the "e4x"
 specification.

=== modified file 'lib/lp/blueprints/stories/standalone/xx-batching.txt'
--- lib/lp/blueprints/stories/standalone/xx-batching.txt	2009-09-22 10:48:09 +0000
+++ lib/lp/blueprints/stories/standalone/xx-batching.txt	2010-09-17 14:23:57 +0000
@@ -24,11 +24,25 @@
   >>> browser.url
   'http://launchpad.dev/big-project'
 
-In the beginning, a project has no blueprints:
-
-  >>> browser.open("http://blueprints.launchpad.dev/big-project")
-  >>> print extract_text(find_main_content(browser.contents))
-  Blueprints...Register the first blueprint in this project!...
+In the beginning, a project hasn't had blueprints set up:
+
+  >>> browser.open("http://blueprints.launchpad.dev/big-project")
+  >>> print extract_text(find_main_content(browser.contents))
+  Blueprints...does not know how...Configure blueprints...
+
+But it's easy to change that.
+  
+  >>> browser.open("http://blueprints.launchpad.dev/big-project/+configure-blueprints")
+  >>> browser.getControl(name='field.blueprints_usage').value = ['LAUNCHPAD']
+  >>> browser.getControl('Change').click()
+  >>> browser.url
+  'http://blueprints.launchpad.dev/big-project'
+
+Initially the newly enabled feature has no blueprints.
+
+  >>> browser.open("http://blueprints.launchpad.dev/big-project")
+  >>> print extract_text(find_main_content(browser.contents))
+  Blueprints...first blueprint in this project!...
   
 We'll go ahead and add just a single blueprint:
 

=== modified file 'lib/lp/blueprints/stories/standalone/xx-index.txt'
--- lib/lp/blueprints/stories/standalone/xx-index.txt	2009-09-22 16:42:19 +0000
+++ lib/lp/blueprints/stories/standalone/xx-index.txt	2010-09-17 14:23:57 +0000
@@ -1,6 +1,20 @@
 =====================
 Blueprints index page
 =====================
+Enabling Firefox
+----------------
+
+For a product to work in blueprints, it must be active, so we'll activate
+blueprints for firefox.
+
+    >>> from zope.component import getUtility
+    >>> from lp.app.enums import ServiceUsage
+    >>> from lp.registry.interfaces.product import IProductSet
+    >>> login('[e-mail]')
+    >>> firefox = getUtility(IProductSet).getByName('firefox')
+    >>> firefox.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> transaction.commit()
+    >>> logout()
 
 The blueprints index page allows users to search for blueprints within
 a single Launchpad project or across all projects.

=== modified file 'lib/lp/blueprints/stories/standalone/xx-overview.txt'
--- lib/lp/blueprints/stories/standalone/xx-overview.txt	2009-11-26 03:06:58 +0000
+++ lib/lp/blueprints/stories/standalone/xx-overview.txt	2010-09-17 14:23:57 +0000
@@ -7,6 +7,17 @@
 blueprints, and also other pages where users can browse through complete
 lists of blueprints for a given product or distribution.
 
+A number of tests in this need a product with blueprints enabled, so we'll
+enable them on firefox.
+
+    >>> from zope.component import getUtility
+    >>> from lp.app.enums import ServiceUsage
+    >>> from lp.registry.interfaces.product import IProductSet
+    >>> login('[e-mail]')
+    >>> firefox = getUtility(IProductSet).getByName('firefox')
+    >>> firefox.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> transaction.commit()
+    >>> logout()
 
 Viewing lists of blueprints
 ===========================

=== modified file 'lib/lp/blueprints/stories/standalone/xx-views.txt'
--- lib/lp/blueprints/stories/standalone/xx-views.txt	2009-09-22 10:48:09 +0000
+++ lib/lp/blueprints/stories/standalone/xx-views.txt	2010-09-17 14:23:57 +0000
@@ -1,6 +1,22 @@
-== Blueprint views ==
-
-=== Viewing current blueprints ===
+Blueprint views
+===============
+
+Set Up
+------
+A number of tests in this need a product with blueprints enabled, so we'll
+enable them on firefox.
+
+    >>> from zope.component import getUtility
+    >>> from lp.app.enums import ServiceUsage
+    >>> from lp.registry.interfaces.product import IProductSet
+    >>> login('[e-mail]')
+    >>> firefox = getUtility(IProductSet).getByName('firefox')
+    >>> firefox.blueprints_usage = ServiceUsage.LAUNCHPAD
+    >>> transaction.commit()
+    >>> logout()
+
+Viewing current blueprints
+--------------------------
 
 We should be able to see a "+specs" and a "+portlet-latestspecs" view
 on sprint, product, person, project and distribution.
@@ -143,7 +159,8 @@
     ...Activating Usplash...
 
 
-=== Viewing all blueprints ===
+Viewing all blueprints
+----------------------
 
 From time to time it's useful to review the complete list of all blueprints
 associated with a blueprint target, including those blueprints that have

=== added file 'lib/lp/blueprints/templates/unknown-specs.pt'
--- lib/lp/blueprints/templates/unknown-specs.pt	1970-01-01 00:00:00 +0000
+++ lib/lp/blueprints/templates/unknown-specs.pt	2010-09-17 14:23:57 +0000
@@ -0,0 +1,93 @@
+<html
+  xmlns="http://www.w3.org/1999/xhtml"
+  xmlns:tal="http://xml.zope.org/namespaces/tal"
+  xmlns:metal="http://xml.zope.org/namespaces/metal"
+  xmlns:i18n="http://xml.zope.org/namespaces/i18n"
+  metal:use-macro="view/macro:page/main_side"
+  i18n:domain="launchpad"
+>
+
+<body>
+
+<div metal:fill-slot="main">
+  <div class="top-portlet">
+    <div id="specs-unknown">
+      <strong>
+        <div tal:omit-tag tal:condition="view/is_project">
+          <p>
+            Launchpad does not know how
+            <tal:project replace="view/context/displayname" /> tracks feature
+            planning or documentation.
+          </p>
+        </div>
+        
+        <div tal:omit-tag tal:condition="view/is_series">
+          <div
+            tal:omit-tag
+            tal:define="target python:view.context.product and view.context.product or view.context.distribution;
+                        blueprints_usage target/blueprints_usage"> 
+          <p tal:condition="blueprints_usage/enumvalue:EXTERNAL">
+            <tal:project replace="target/displayname" />'s
+            <tal:project replace="view/context/displayname" /> series does
+            not use Launchpap for planning or documentation.
+          </p>
+          <p tal:condition="blueprints_usage/enumvalue:NOT_APPLICABLE">
+            <tal:project replace="target/displayname" />'s
+            <tal:project replace="view/context/displayname" /> series does not track
+            feature planning or documentation.
+          </p>
+          <p tal:condition="blueprints_usage/enumvalue:UNKNOWN">
+            Launchpad does not know how
+            <tal:project replace="target/displayname" />'s
+            <tal:project replace="view/context/displayname" /> series tracks feature
+            planning or documentation.
+          </p>
+          </div>
+        </div>
+        
+        <div tal:omit-tag
+          tal:condition="python:not (view.is_project or view.is_series)">
+          <div tal:omit-tag tal:define="blueprints_usage view/context/blueprints_usage">
+          <p tal:condition="blueprints_usage/enumvalue:EXTERNAL">
+            <tal:project replace="view/context/displayname" /> does not use launchpad
+            for planning or documentation.
+          </p>
+          <p tal:condition="blueprints_usage/enumvalue:NOT_APPLICABLE">
+            <tal:project replace="view/context/displayname" /> does not track
+            feature planning or documentation.
+          </p>
+          <p tal:condition="blueprints_usage/enumvalue:UNKNOWN">
+            launchpad does not know how
+            <tal:project replace="view/context/displayname" /> tracks feature
+            planning or documentation.
+          </p>
+          </div>
+        </div>
+      </strong>
+
+      <div tal:omit-tag tal:condition="view/has_wiki">
+      <p id="wiki-fallback"
+        tal:define="wiki view/context/wikiurl"
+        tal:condition="wiki">
+        <tal:project replace="view/context/displayname" /> has a wiki, which
+        may be used for feature plannning and documentation.<br />
+        <a tal:attributes="href view/context/wikiurl">
+          <tal:project replace="view/context/displayname" /> wiki
+        </a>
+      </p>
+      </div>
+    </div>
+
+    <p id="configure-support"
+      tal:condition="view/can_configure_blueprints">
+      Launchpad Blueprints allow your project to track feature planning and
+      documentation.<br />
+      <a class="info sprite"
+        href="https://help.launchpad.net/BlueprintDocumentation">
+        Read more about tracking feature planning with blueprints</a><br />
+      <a tal:replace="structure context/menu:overview/configure_blueprints/fmt:link" /><br />
+    </p>
+  </div>
+</div>
+</body>
+</html>

=== modified file 'lib/lp/registry/browser/distribution.py'
--- lib/lp/registry/browser/distribution.py	2010-09-11 19:54:26 +0000
+++ lib/lp/registry/browser/distribution.py	2010-09-17 14:23:57 +0000
@@ -342,6 +342,7 @@
         'announcements',
         'ppas',
         'configure_answers',
+        'configure_blueprints',
         ]
 
     @enabled_with_permission('launchpad.Edit')
@@ -453,6 +454,12 @@
         summary = 'Allow users to ask questions on this project'
         return Link('+edit', text, summary, icon='edit')
 
+    @enabled_with_permission('launchpad.Edit')
+    def configure_blueprints(self):
+        text = 'Configure blueprints'
+        summary = 'Enable tracking of feature planning.' 
+        return Link('+edit', text, summary, icon='edit')
+
 
 class DerivativeDistributionOverviewMenu(DistributionOverviewMenu):
 

=== modified file 'lib/lp/registry/browser/product.py'
--- lib/lp/registry/browser/product.py	2010-09-03 15:02:39 +0000
+++ lib/lp/registry/browser/product.py	2010-09-17 14:23:57 +0000
@@ -547,7 +547,7 @@
     @enabled_with_permission('launchpad.Edit')
     def configure_blueprints(self):
         text = 'Configure blueprints'
-        summary = 'Enable tracking of specifications and meetings'
+        summary = 'Enable tracking of feature planning.'
         return Link('+configure-blueprints', text, summary, icon='edit')
 
     @enabled_with_permission('launchpad.Edit')

=== modified file 'lib/lp/registry/browser/tests/pillar-views.txt'
--- lib/lp/registry/browser/tests/pillar-views.txt	2010-09-14 21:50:32 +0000
+++ lib/lp/registry/browser/tests/pillar-views.txt	2010-09-17 14:23:57 +0000
@@ -36,8 +36,8 @@
     True
     >>> print view.answers_usage.name
     LAUNCHPAD
-    >>> view.translations_usage.name
-    'UNKNOWN'
+    >>> print view.translations_usage.name
+    UNKNOWN
     >>> print view.blueprints_usage.name
     UNKNOWN
     >>> print view.codehosting_usage.name