Maintainership of rank1dynamic and distributed-static
2 views
Skip to first unread message
Tim Watson
Dec 1, 2014, 9:36:22 AM12/1/14
to cloud-haskell-developers, parallel-haskell, distribut...@googlegroups.com
Hi all,
As you might have noticed, I've been pretty terrible at responding to pull requests and issues around cloud haskell since the last release. That's partly because I stupidly tagged some github post as spam in the murky past and what with a new job keeping me away from hacking the last months, I didn't realise people were actually using this and trying to get things done and sorted. I feel very strongly about supporting commercial users so....
Firstly, my profuse apologies for the delays. I'm ramping back up on cloud haskell and hoping to start doing some consulting around it in the coming months so I'm very very keen to make sure everything is working properly and releases getting uploaded promptly.
Secondly, since I have somewhat limited time, I am going to be handing over maintainership responsibility for the rank1dynamic and distributed-static libraries to tweag.io and specifically Facundo, who is working hard on the static pointers proposal at the same time. Facundo and I will work together to identify the changes necessary to all of cloud haskell in order to support static pointers when the extension is made available.
Thirdly, I am really keen to find a maintainer for the tcp network transport backend. I really need/wish to focus in the coming year on stability issues, eeking out and fixing any concurrency bugs (tweag have apparently found some races introduced as regressions which I'm keen to understand and fix) and making performance improvements. The tcp nt backend is a massively complex beast and I don't have time to give it the attention it needs. I'd also like to better support the other backends but need more hands on deck to do so.
Comments and feedback on these proposals, as well as any other general bike shedding around cloud haskell are as always, most welcome.
Cheers,
Tim
As you might have noticed, I've been pretty terrible at responding to pull requests and issues around cloud haskell since the last release. That's partly because I stupidly tagged some github post as spam in the murky past and what with a new job keeping me away from hacking the last months, I didn't realise people were actually using this and trying to get things done and sorted. I feel very strongly about supporting commercial users so....
Firstly, my profuse apologies for the delays. I'm ramping back up on cloud haskell and hoping to start doing some consulting around it in the coming months so I'm very very keen to make sure everything is working properly and releases getting uploaded promptly.
Secondly, since I have somewhat limited time, I am going to be handing over maintainership responsibility for the rank1dynamic and distributed-static libraries to tweag.io and specifically Facundo, who is working hard on the static pointers proposal at the same time. Facundo and I will work together to identify the changes necessary to all of cloud haskell in order to support static pointers when the extension is made available.
Thirdly, I am really keen to find a maintainer for the tcp network transport backend. I really need/wish to focus in the coming year on stability issues, eeking out and fixing any concurrency bugs (tweag have apparently found some races introduced as regressions which I'm keen to understand and fix) and making performance improvements. The tcp nt backend is a massively complex beast and I don't have time to give it the attention it needs. I'd also like to better support the other backends but need more hands on deck to do so.
Comments and feedback on these proposals, as well as any other general bike shedding around cloud haskell are as always, most welcome.
Cheers,
Tim
Reply all
Reply to author
Forward
0 new messages