On Mon, Jun 20, 2016 at 06:07:59PM -0400, Peter Colberg wrote: > That said, I can think of quite a few metrics to evaluate maintainer > ability based on golang packaging:
[ reflowing the text… ]
> to which extent has the maintainer collaborated with upstream,
> e.g., to motivate them to tag releases, to file pull requests
> for forked packages so that the original packages can be used in Debian,
> to fix their test suite, to ask for license clarification, etc.
these are all social abilities more than anything.
> how carefully has debian/copyright been composed;
These are not really something that would give me an idea of the
techinical knowledge somebody has. Licenses foo is surely something
important, but how do I know that you're able to fix bugs in your
package to a certain extent _correctly_. Part of what a sponsor
(usually) does is reviewing the changes, and see if they makes sense,
and avoid to upload clearly buggy things.
Mind you: I don't want to discurage you, just that I feel much more
confident with people who open themselves to other parts of debian work.
But then, a the DM status is thought for people who are only interested
in the restricted circle of their packages, and are not interested in
the bigger world; that's cool, but *I* still need more proof :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
_______________________________________________ Letsencrypt-devel mailing list [email protected] https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
