-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Absentee Esqueleto maintainer #84
Comments
Additional note: I use Esqueleto at my day job, which is more than I can say for Bloodhound :) |
@bitemyapp btw, as per https://wiki.haskell.org/Taking_over_a_package it's recommended to communicate/broadcast your intention to take over a package over a public medium which has a wide reach, such as haskell-cafe or the libraries mailinglist; have you done that already? |
@bitemyapp let me know if you publicly broadcast your intention to take over the package, I'm 👍 on that. I also want Felipe to come back too though :( |
@hvr I'd discussed it on a public Slack (FPChat, has a couple thousand members, several hundred in #haskell), I'll cross-post to the mailing list. |
For the record, @meteficha last recorded activity on Hackage was back in february:
And GitHub shows the last activity dating back to July 2016. |
Esqueleto is now out-of-date enough that the |
Summoning @hesselink |
@bitemyapp posted his intent to take over to haskell-cafe 25 days ago. The policy at https://wiki.haskell.org/Taking_over_a_package says the admins will wait 2-6 weeks before making the change--any chance we could call it soon? :) (Esqueleto Stackage issues have been ongoing since June 2016--at this point it's the main thing keeping me from upgrading to GHC 8.) |
+1 on moving this along. It's been many weeks now, and Felipe is clearly absentee (as sad as that is). What are the next steps here? Is there someone else that needs to approve? |
+1 in support of @bitemyapp taking it over, or perhaps we at Front Row can help out with it, as it's a critical part of our backends. |
Turns out @snoyberg is a maintainer for esqueleto on hackage. So I'll leave it up to him to decide how to proceed here. I've sent him an email. |
I had no memory of having that, doh! Yup, I have no problem with giving @bitemyapp access, I'll do that now. |
I think this is sorted, closing for now. @jdreaver @akurilin @danpalmer @thomasjm please file your current needs/concerns at https://github.com/bitemyapp/esqueleto the current version has some fixes from @pseudonom - like to get a sense of where things are at and what needs catching up on. (It's a fork right now, I'll make it not a fork in a bit) |
prowdsponsor/esqueleto#137 (comment)
This is first notice for my contact of Prowdsponsor / Lessa.
The text was updated successfully, but these errors were encountered: