Hi Paul, On 6/23/2016 12:41 PM, Paul Jakma wrote: > On Thu, 23 Jun 2016, Paul Jakma wrote: > >> In general, stuff should just go through that process ASAP. > And that larger stuff hasn't is due to a back log. > > To the extent that's my fault for not having much time for Quagga for a > good number of years, I apologise. But, it was being dealt with (and we > *HAD* dealt with incoming) up till late last year, and it will be dealt > with pretty much completely, quite soon. I think this goes to the root of the recent discussions: - Is Quagga a community project, or a project reliant and owned by a single person?
My understanding was that the Zebra to Quagga branch occurred largely because Zebra was really a single person controlled/owned project and there was a desire (amount *all* working Quagga at it's start) to have a community controlled version. One really important implication of this, is that the project should continue to thrive even if/when a key contributor/maintainer disappears or is overloaded with their "day job" for a time. I've only been using / developing against Quagga since '09 and publicly pushing code out for the last couple of years, so may have it wrong, but have always viewed Quagga as a community driven / controlled project. Do you think I have this wrong? Lou > regards, _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
