Matthew Revell wrote: > [...] I'm putting together a panel of Launchpad users, whom I can contact for > complaints, new ideas and other feedback. It wouldn't be hard work, only > a few emails every now and then. > This is great news. We are using Launchpad as a team management tool while leading the ubuntu-co (Colombian) team. I would like to be part of that panel.
Is it possible to also invite one of my team members as a user (as opposed to owner/admin) of Launchpad in this panel ? > - what you use Launchpad for > Right now, personal tracking of activity, membership approval for our loco team. > - what you most like about Launchpad > Its tracking of activity and Kharma. That's how I define launchpad, as a tool to measure participation. I also like the OpenPGP integration, although I'd like to see it used in more ways. > - what you most dislike about Launchpad. > There's not much I don't like :) but a lot I would like to see improved. Lots of it is described in specifications. I 'd suggest looking at current specs related to launchpad. So #1 for me would be the ability for the launchpad registered users that are Ubuntu members to be able to vote for specs: https://blueprints.launchpad.net/products/launchpad/+spec/whats-new My holiday shopping list would look like this (URLs at the end of this email): - Launchpad in spanish and french (for me) but also other languages[1], perhaps most importantly the login workflow but also the support tracker/requests, Code of Conduct [2], [3], [8] - A clear process to submit bugs / requests for enhancements so they don't take ages to be adressed. Historically, non-critical bugs and feature requests are very low priority but they affect greatly how team leaders may manage their team effectively. - localizable templates for email notification when membership of a team is accepted/refused. - ability to restrict some activities ( poll-voting ) to members only - https://launchpad.net/products/launchpad/+bug/76620 - Another column in the members report to see who has signed the CoC - see https://launchpad.net/products/launchpad/+bug/74667 - RSS feeds/API access to different information: bug reports by team/member, translations by team/member, historic data... stuff that we can use to tell people what is going on in a team using plain cold numbers (and links). The spec at [5] is private, apparently. [5][9] - Hooks to other systems to measure participation and get notification: forums, IRC, Wiki(s), blogs. Not sure how to go about this, just an idea. Perhaps this is best explained in the "Unifying LoCo Team Resources" spec [6][7][10][11] [1] https://blueprints.launchpad.net/products/launchpad/+spec/localized-login-workflow [2] https://blueprints.launchpad.net/products/launchpad/+spec/launchpad-i18n [3] https://blueprints.launchpad.net/products/launchpad-support-tracker/+spec/localized-support-tracker [4] https://blueprints.launchpad.net/products/launchpad-support-tracker/+spec/localized-support-requests [5] https://blueprints.launchpad.net/products/launchpad/+spec/rss-feeds/ [6] https://blueprints.launchpad.net/distros/ubuntu/+spec/unifying-loco-resources-with-launchpad [7] https://blueprints.launchpad.net/products/launchpad/+spec/irc-notifications [8] https://blueprints.launchpad.net/products/launchpad/+spec/code-of-conduct-translation [9] https://blueprints.launchpad.net/products/malone/+spec/bug-searches-as-rss [10] https://blueprints.launchpad.net/products/launchpad/+spec/launchpad-forum-integration [11] https://blueprints.launchpad.net/products/launchpad/+spec/loco-teams -- loco-contacts mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/loco-contacts
