Re: Best scheme for teams and Maintainer/Uploaders fields ?
Pierre Habouzit wrote:
> in the KDE Team we use: Maintainer <the list>, Uploaders <the
> responsible for the packages>. The list beeing email@example.com or
The Java team uses the same method, but it has IMHO the huge drawback
that "uploaders" sometimes stop paying attention to a package without
notice, and are never unlisted from the Uploaders field , until the
package is effectively orphaned. This scheme does not discourage
such "fire-and-forget" behaviour. I think it's a very good idea to have a
single lead Maintainer.