Re: Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds)

[Ian Stakenvicius <axs@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/12/12 10:27 AM, Peter Stuge wrote:
> [ Snip! ] In the last 15 hours I've dealt with several trivial bugs
> that I've found fixes for in bugzilla but which were not committed
> anywhere.
> 
> I've committed them to my overlay and that's fine for me, but if I 
> were a developer I would find it super lame to have to stop there
> and wait for $otherguy to take time to look at "his" bugs. [ Snip!
> ]
> 
> I would expect to fix the bugs, and then email patches to whoever
> is the maintainer. It would be worthwhile to have automatic
> extraction of who needs to get that email based on what files were
> touched. No bug needed, if maintainers get perfect patches in email
> they can review them quickly and simply push them into the tree.

There's a bit of an issue with this, though -- for many projects, and
many bugs, patches are not committed to the tree until that bug and
patch has been submitted upstream (job of the maintainer) and upstream
has approved or accepted that patch.  I think quite often this is why
patches sit in bugs instead of getting to the tree.

Essentially, if the problem is with the ebuild or the way the package
is integrated into gentoo, then fixing it immediately is fine.  If the
problem is with the software itself, then usually upstream needs to be
involved before the fix will occur in gentoo.

Also, Emailing patches to the maintainer is much less
acceptable/desirable than filing them through bugzilla.  As a
developer, I find it much easier to grab patches from this nice
centralized bug-tracking filing system than to have to organize them
in email, and git integration is not something I see changing this.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlDAv7EACgkQ2ugaI38ACPCQ/QEAmYjna1exh9qxqptbdB08Hvoo
TzJi72ux2nf9edZsR3IA+wXENBA1EDuc/8JDN74aJ0/iFdhL1yG2CxJ515tNDxxX
=4d2v
-----END PGP SIGNATURE-----