I consider myself competent to serve maintain Data.Sequence and Data.Tree. I am much less familiar with the other modules in the package. I would particularly like to serve as co-maintainer if anyone else is interested. Alternatively (and better, in my opinion), the package could be split. Data.Sequence is barely connected to the rest of the package, and the only other module that depends on it doesn't need to. Running under GHC, Data.Graph depends only on Data.Tree (in a hypothetical ST-free system, it also depends on Data.IntSet). So I think it makes sense to have three packages: one for Data.Sequence, one for Data.Tree and Data.Graph, and one for Data.Map, Data.Set, Data.IntMap, and Data.IntSet (which share most of their API and are therefore a sensible package, though generally independent). I see no reason not to divide these three portions among three maintainers.

On Apr 3, 2016 7:18 PM, "Milan Straka" <milan@strakovi.com> wrote:

Hi all,

I am writing to let you know that I am no longer able to maintain the
containers package.

I have enjoyed working on containers for several years, but I can no
longer find the time needed for the job (with two little kids
and building a house).

I am not sure what is the best future of the containers package -- it
could go to CLC, or it could get a new maintainer. If you look at the
commit logs and on the github issues/requests, you will find out that
David Feuer has a thorough understanding of the package (notably
Data.Sequence) and has been competently moderating the issues/requests
for some time now, so he would be the first choice. (I did not contact
him sooner, so it is surprise for him as well -- sorry, David :-)

Could I humbly ask David/CLC members/anyone for comments?

Cheers,
Milan Straka