Hi,
At present everyone is encouraged to help review stuff and chip in. I have
felt for a good while that it would help encourage people to do so and
generally be good, if we had more explicit inclusion of contributors into
technical oversight of Quagga. There are many, many good people working
on Quagga, with valuable technical abilities. The question is how do we
best organise things to encourage and use them?
I'm wondering if we could try devolve technical oversight to a
tech-{panel,committee,whatever}. Anyone who has contributed to Quagga
could apply and/or be invited in, to join, subject to the panel's
approval.
E.g. a tech-{panel,committee,whatever} with responsibility for technical
oversight, to review contributions, give feedback, and commit approval?
Perhaps initially working on the traditional consensus basis, and evolving
itself to whatever way of working it wanted.
Is that something, or ????
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
I will pop a nasty patch to get you through the almost death, but it is
nasty and not the preferred unknow solution.
- Andre Hedrik on linux-kernel
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
