AMDG On 02/28/2015 08:37 PM, Edward Diener wrote:
Then who gets to make a change to a library ? Only a person who is wiiling to be the sole maintainer of that library ? Thats seems very limiting to me. If there is a group of maintainers to a library, whether they are members of the community maintenance team or whether they are just those who have been granted write access to that library, and one of those maintainers is willing to make changes and follow it through after getting a consensus of others involved, why should not that be allowed in principle.
I don't object to a library having more than one maintainer, in principle. The trouble is that MPL has none. Like I said, I don't think that the CMT really counts.
MPL may be too big or too difficult to make major changes without a thorough knowledge of the library but in the case of Stephen Kelly's patches to it to remove outdated compiler support I think that was doable without having to understand all the code in the library.
A very dangerous notion. Anyway, making any changes is a risk, and I don't see how there's any real benefit if no one is planning to make any significant changes (which would, of course, require a real maintainer). In Christ, Steven Watanabe