Specification feature should support multiple assignee/drafter/reviewer

Working on it atm, will present a mock-up here soon :) Thanks.

Alright so I do have a mock-up here, but I am not quite sure how the changes in the database are going to work out, is it going to affect anything else?

Blueprints roles are autonomous from other apps This would require 1-3 tables to move the roles from Specification to separate tables: replacing the 1-to-1 (from Specification-Person) to 1-* (Specification-SpeficationRole-Person).

No changes are need for the page shown in the mockup. The user will still want to go to an edit screen where they manage the list of assignees for each role. We need that page designed to to decide what schema changes are needed.

I see what you are saying Curtis, that page will be like the one that
shows up when you click "Link to a bug report" so I could port some
code from that to here, after that we will see what schema and
database changes will be needed. Thanks for the guidelines :)

--
Regards,
Vikram Dhillon

~~~
There are lots of Linux users who don't care how the kernel works, but
only want to use it. That is a tribute to how good Linux is.
-- Linus Torvalds

On Thu, Feb 4, 2010 at 5:47 AM, Curtis Hovey <email address hidden> wrote:
> Blueprints roles are autonomous from other apps This would require 1-3
> tables to move the roles from Specification to separate tables:
> replacing the 1-to-1 (from Specification-Person) to 1-* (Specification-
> SpeficationRole-Person).
>
> No changes are need for the page shown in the mockup. The user will
> still want to go to an edit screen where they manage the list of
> assignees for each role. We need that page designed to to decide what
> schema changes are needed.
>
> --
> Specification feature should support multiple assignee/drafter/reviewer
> https://bugs.launchpad.net/bugs/2040
> You received this bug notification because you are a bug assignee.
>
> Status in The Launchpad Blueprint Tracker: Triaged
>
> Bug description:
> In most of the cases specifications are done by multiple people, we should be able to assign more than one person for the fields assignee/drafter/reviewer.
>
> Ok, they could be a team, which is fair enough for the distribution team, for instance, but for Launchpad Team and other huge projects it's possibly to have people cooperating only in the specification context and not having strong relation enough to justify a new team. in my understand it falls in the same old  problem of not having a reliable widget to group multiple entity instances in the same form.
>
>
>