[boost] [lexical-cast] New maintainer

Subject: [boost] [lexical-cast] New maintainer
From: Antony Polukhin (antoshkka_at_[hidden])
Date: 2011-05-09 04:44:54

Alexander Nasonov and Kevlin Henney gave me their permissions to
become a new maintainer of Boost.LexicalCast library.

Plans for the nearest future:
1) fix inspection program warnings (missing licenses, copyrights, non
ascii chars ...)
2) contact with bug reporters, and fix bugs if they still exist
3) add unit tests and performance optimizations

If somebody has some advices, comments or wishes, I would be glad to hear them.

2011/5/9 Kevlin Henney <kevlin_at_[hidden]>:
> Antony Polukhin <antoshkka_at_[hidden]:
>> There are some bug fixes in trunk and performance optimizations, that
>> can not make their way to release. And there is no accepted
>> Boost.Convert library, that can do better than lexical_cast.
>>
>> Alexander Nasonov, the current maintainer of lexical_cast, wrote that
>> he has no time for maintaining lexical_cast and that he has no
>> objections against new maintainer.( That was in thread '[boost]
>> [lexical-cast] version of lexical_cast in 1.46.1 is quite older than
>> in trunk').
>>
>> If you don`t mind, I`d like to become a new maintainer of
>> lexical_cast. I`ve already talked with Alexander, he gave me a short
>> introduction of how to maintain and what changes can be accepted into
>> the library. He also advised to talk to you.
>
> Yes, I would be happy for you to do this, if you want to run initial changes
> by me and/or Alexander.
>
>  Antony Polukhin <antoshkka_at_[hidden]:
>> Would you be so kind to give me some advises and tell more, about the
>> official procedure of becoming a maintainer?
>
> I don't think there is an official process for becoming maintainer, other
> than the original author and/or the current maintainer saying "You are now
> the maintainer!" :-)
>
> And please feel free to ask me any questions about the requirements or
> design intent.
>
> Antony Polukhin <antoshkka_at_[hidden]:
>> Is there some requirements, not described in N1973 that the library
>> must follow to?
>
> No, we had no plans for any additional features, only fixes to bugs and
> improvements in performance. The functionality is at a point where it is
> stable.
>
> So, congratulations: You are now the maintainer!
>
> Regards,
>
> Kevlin