whube-core team mailing list archive

[Thomas Plastino Martin <thomas@xxxxxxxxxxxxxxxxx>]

I can tackle the team tools.  Here's what I was thinking, in no real order
as of yet:

Assuming projects can be assigned to a team and/or individual (but not both
simultaneously?):
* Teams page will show an overview of the team and projects/bugs they're
working on.
* Hit lists and what not will be contracted by default, and can be expanded
by being selected instead of using multiple pages for simple data.
* A more detailed hit list would be easily viewable, perhaps the bug number
and name with a short description/excerpt under it.
* Individual items on the hit list would reference and navigate to their
respective bug entry / wish list (or whatever else we decide to 'allow' on
hit lists)

That list bullet brings a question to mind: team hit list - AFAIK it is just
a bug list, for now?

Thomas Plastino Martin
https://launchpad.net/~tenach
http://tenach.net


On Mon, Aug 9, 2010 at 6:22 AM, Paul Tagliamonte <paultag@xxxxxxxxxx> wrote:

> Hey  guise!
>
> So, it's getting to be that time.
>
> We *need* to get the last bits of Whube done.
>
> *critical* items follow:
>
>  * Admin Interface ( for r00t )
>  * User Management Interface ( for managing personal settings )
>  * COMMENTS!
>  * Team Tools ( Team hit-lists, I added in the SQL table for groups,
> don't think it's used yet ) -- also make sure the role of "team
> member" grants access
>  * Full UX audit, round corners polish the rough spots
>  * Full security audit
>  * Email updates on updated bugs
>
> -Tag
>
> --
> #define sizeof(x) rand()
> :wq
>
> _______________________________________________
> Mailing list: https://launchpad.net/~whube-core<https://launchpad.net/%7Ewhube-core>
> Post to     : whube-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~whube-core<https://launchpad.net/%7Ewhube-core>
> More help   : https://help.launchpad.net/ListHelp
>