| 1 |
As I was told in my recruiting process we usually don't just fix up |
| 2 |
ebuilds of other devs unless it's trivial, very severe or something. |
| 3 |
|
| 4 |
The usual process is nothing new: try to contact the maintainer, open a |
| 5 |
bug, set a deadline when you will go and fix yourself. |
| 6 |
|
| 7 |
Only question is now what is a sane soft limit, before you go on and fix |
| 8 |
stuff. |
| 9 |
From a discussion in #gentoo-dev we thought 2-4 weeks depending on the |
| 10 |
severity of the bug is fine. Ofc this should exclude major changes or |
| 11 |
delicate packages from base-system/core/toolchain. |
| 12 |
|
| 13 |
I tried to document that a bit: |
| 14 |
https://bugs.gentoo.org/show_bug.cgi?id=445402 |
| 15 |
|
| 16 |
any objections? This is nothing new, just a clarification of already |
| 17 |
existing policy and a reminder. |
Archives