27 Nov
2012
27 Nov
'12
11:18 a.m.
On 27-11-2012 12:04, Michel Morin wrote:
Considering this situation, I'd like to make a proposal about Boost.Range:
** Adding a sub-maintainer to Boost.Range **
This reduces author's maintenance burden and also helps more stable development of the library.
I would like to see a more liberal policy towards maintenance. For example, there are many people that are knowledgable and responciple, and which can easily apply patches that have been agreed on. Therefore I see a "sub-maintainer" role as too narrow; why should he not be able to patch a different library as long as the ticket has been discussed and the solution approved by the official maintainers? -Thorsten