Hello Paul, all,
Well, I have this in mind for a while and I would take the opportunity
of your mail to discuss this suggestion.
The Quagga code is hard to understand for a novice / beginner as other
open-source project that have a long story. In addition, as Quagga is
aiming to implement network protocols, this required additional
competencies in networking. These 2 requirements made contributors /
developers / code reviewers very rare.
Thus, why not specialize code reviewer per protocol ?
Taking my own experiences and competencies, I could help on Traffic
Engineering of course, but also on ISIS and OSPF for code review. But,
even if I know the protocols, I have no particular competencies for BGP,
PIM and RIP.
By making a short inventory, or asking to fulfil a simple table, perhaps
we could identity key peoples per protocol and/or set of RFCs that will
be in charge to review the code for which they have competencies. Of
course, we also need to identify key peoples for the general Quagga
architecture / principle as well as the Zebra itself, but I think today
maintainers fit in this category.
I hope this way we could attract more peoples as code review will be
directly rely on their competencies and thus will be less afraid to
propose their help. This will contribute to share the code review effort.
Comments ?
Regards,
Olivier
Le 26/04/2016 17:50, Paul Jakma a écrit :
On Mon, 25 Apr 2016, Paul Jakma wrote:
- More people involved to spread the load, find and squash
person-specific habits, and avoid burn-out. I was hoping we'd have had
more people involved and passed the 'patch herder' role around a bit
more quickly by now.
Oh, and another reason for this is to ensure regular contributers who
help with patch-herding also regularly experience the same process
everyone else does, so they're motivated to make it better.
regards,
--
logo Orange <http://www.orange.com>
Olivier Dugeon
Senior research engineer in QoS and network control
Open Source Referent
Orange/IMT/OLN/WTC/IEE/OPEN
fixe : +33 2 96 07 28 80
mobile : +33 6 82 90 37 85
[email protected] <mailto:[email protected]>
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
