Recent blog posts
-
14 weeks 5 days ago
-
38 weeks 6 days ago
-
44 weeks 5 days ago
-
46 weeks 3 days ago
-
47 weeks 4 days ago
-
48 weeks 2 days ago
How can we help you?
To learn more about our work, how we can work with you, or to request an estimate or quote, just call us at
0049-721-3525-6868
or drop us an email.
User login
Recent comments
- Thanks! Added Taxonomy Intro
3 days 3 hours ago - Taxonomy Introduction
3 days 3 hours ago - Cool agency
5 days 39 min ago - @ Alex
There are many books
2 weeks 3 days ago - Cant wait
2 weeks 5 days ago - module-developer
4 weeks 20 hours ago - I have to second that,
5 weeks 2 days ago - Does anyone happen to know a
5 weeks 3 days ago - We're commin' along...
8 weeks 11 hours ago - which opensource software did
8 weeks 2 days ago
One small edge-case scenario problem
One problem I just realized - and we indeed have that problem already - is that when a sub-system maintainer AND a code gardener are working on a patch, they will have hard times to find someone for peer-reviews, because already two people of a very small group of people being able to do quality reviews basically cannot really sign off that patch.
Additionally, there is very likely a too high trust-level for any peer-reviewers in the game - because both a sub-system maintainer and code gardener worked on a patch - so how bad and wrong can it really be...? :-/
Hence, that is clearly the scenario where a patch may only get peer-reviews from people that worked on the patch, and core branch maintainers may be involved too early.
Not really sure whether that is really an edge-case scenario or perhaps even happens way too often.