[Olsr-dev] Maintainership

[Thomas Hühn]

Hi Meshers,

I was happily surprised to see some new discussion on the mailing list of THE routing protocol we started with in 2003 and still use in our ~100 nodes Evernet Mesh over here!
The long planned migration to olsr_v2 is still not done nor tested .. shame on me … since battlemesh in Portugal ferry and henning anounced olsr_v1 is out of maintenance .. and I was convinced to migrate to v2.
So even more surprise that in olsr_v1 there is still something going on to fix compile probs and stuff because … some people I was not aware of are routing on this ;)

ferry/sven/henning … I do know Nick in person … aka PolynomialDivision … I herewith give my ack for his olsr_v1 PR requests … he is those younger FF_generation … those that come after us ;) .. he is an active Freifunka, the right mojo to change things and brake things… and most importantly extend the mesh… link state by link state.

Greetings from the (n)evernet
Bluse

> On 28. May 2021, at 13:43, Nick <(spam-protected)> wrote:
> 
> Instead of making me maintainer, I would also completely fine with someone merging the urgent patches. ;)
> 
> On 5/28/21 1:03 PM, Ferry Huberts wrote:
>> Before I can do that I need github IDs.
>> 
>> And *maybe* some more chiming in that this is a good idea.
>> I do not know you, so I'd appreciate some more vetting :-)
>> 
>> On 28/05/2021 12:58, Mathias Mahnke wrote:
>>> Am 27.05.21 um 21:07 schrieb Nick:
>>>> Philipp is not owner of the repro, so he can not make me maintainer.
>>>> Can someone make me maintainer?
>>> 
>>> Same here. Either Henning or Ferry are able to add you to the "member" role of the project.
>>> 
>>> Regards,
>>> Mathias
>>> 
>> 
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev