Add structural subscription to blueprints

This will be implemented shortly after 2.0

I am looking forward to this as well! I have definitely missed ideas contributed by users, and was late in responding when I noticed them only inadvertently later. It is challenging to appear as a responsive project maintainer without this.

I also very much look forward to this. I think such a functionality is essential to all project coordinators to stay updated on all ideas and suggestions from the community.

BUT, could you please provide an update on this work, and more specifically; when will it be released?

On Sun, May 17, 2009 at 9:36 AM, Curtis Hovey <email address hidden> wrote:
> ** Changed in: blueprint
>   Importance: High => Low

Seriously? Launchpad provides no way for project leaders to know when
people create new ideas for their project. This is really an important
feature that project owners/drivers absolutely NEED. Otherwise it is
very easy to at worst completely miss a useful idea or at best not
respond to it in a timely manner and give a bad impression to a
contributor.

I agree that this is essential, but there has not been anyone working on blue prints for more than a year. No one is scheduled to work on blueprint issues. There are many issues regarding how communication works in Blueprints that I think contributors can help fix when Launchpad is open sourced.

Now that Launchpad is open-source, is there anyone willing to mentor someone such as myself in this?

Hi Michael.

I can help. Some work has already been done. StructuralSubscriptions already know about BlueprintNotificationLevel. I have not looked into this matter in detail, but I can point you to where the code must change.

Model branch:
StructuralSubscriptionTargetMixin provides all the major objects with the subscription feature. There are some special methods for bugs. We need similar methods for blueprints. Adding them to the mixin will enable all the model objects to support structural subscriptions.

Email branch:
Email probably needs to be it own branch because I suspect the email handlers need a lot of work. We need a BlueprintNotificationRecipientSet object. I do not see one. We may need to fix some old email rules to. In summary, a NotificationRecipientSet collects every user who must be notified, and why they must be notified. the email headers and the foot of the email must state why the email was sent to the user.

View branch:
Update the UI. Show structural subscribers on each blueprint. Add links to subscribe/unsubscribe to blueprints from each major model's view.

The code you want to look at is old:
lib/canonical/launchpad/interfaces/structuralsubscriptions.py
lib/canonical/launchpad/database/structuralsubscriptions.py
lib/canonical/launchpad/mailnotification.py
lib/lp/blurprints/*

I can help you with pre-implementation plans so that the code you write is what a reviewer will accept.

Michael, I am also happy to help with this. Other relevant reference code is the bugs application structural subscriptions code. I believe quite a lot of it can be shared.