Reinhard Tartler wrote: > Recently, I uploaded wpasupplicant to dapper, with a new Maintainer > field, pointing to "Debian/Ubuntu wpasupplicant Maintainers > <[EMAIL PROTECTED]>". This caused a new person to be > created in launchpad: > > https://launchpad.net/people/pkg-wpa-devel > > I was thinking about changing this to a group, so that others can join > here, particiape in bug squashing and so on. > > Is it possible at all in launchpad that a package is maintained by a > group rather than a person? What would need to be done to have this > 'converted'? > > Please note that this is not an urgent request. I'm rather curious if > this is possible at all, as I think this would resemble reality more > accurately.
The data model supports this quite easily. Designing the workflow and implementing the UI to do this is the only problematic bit. I think the series of events you describe gives us a valid use case for implementing this at some point. > Currently, I have to create a group manually and make that new group a > primary bug contact for that package. Then there would be some confusion > about having 2 entities in Launchpad: one 'Person' 'pkg-wpa-devel' and a > 'Group' calld 'wpa-packaging-team'. I was rather thinking about the > concept of having packages maintained by a group, and how this could be > expressed and displayed within launchpad. -- Stuart Bishop <[EMAIL PROTECTED]> http://www.canonical.com/ Canonical Ltd. http://www.ubuntu.com/
signature.asc
Description: OpenPGP digital signature
-- launchpad-users mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/launchpad-users
