On Tue, Aug 13, 2013 at 12:03 PM, "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote: > One thing I think is really important is respecting the maintainers. If > maintainer said "please send the patch upstream before committing to > cvs", it is _not_ OK to just ignore that. There are other options > available like masking neon.
Also, users running ~arch should know to search bugzilla when they have problems, and there they would find the patch which they could apply. I think it is important to work with maintainers first and foremost. They're the ones with the long-term commitment. Sure, there can be exceptions for simple file additions like init scripts, but certainly random parties shouldn't be adding patches to ebuilds without maintainer agreement unless they're willing to step in and become a committed co-maintainer (with all the responsibilities that entails). If a maintainer is holding something up for months by all means escalate it if you think it is justified, but if a maintainer just wants a few days to look into things, that isn't asking too much. If this were a security patch I might feel differently, or a stable regression (though as has been pointed out that shouldn't happen with reverse dep testing). Rich
