Offer to help maintain this package

[mitchellwrosen]

Hey! I'd like to offer to help maintain this package, if you are interested.

[mitchellwrosen]

Friendly ping

[andreasabel]

@mitchellwrosen : This is very much appreciated, I think a version of unix-compat working with unix-2.8 is urgently needed.

I sent the following email now (2023-01-18) to jacob stanley io:

Dear Jacob,

thank you for maintaining unix-compat!

The current unix-compat-0.6 does not work together with unix-2.8 which will soon become mandatory (GHC 9.6 alpha is already out).

Would you be able to release unix-compat-0.7 which works with unix-2.8 soon? This would greatly help the Haskell community to prepare for GHC 9.6!

If you are not available now, maybe you can accept help? It has been offered here:

#63

There is also already a PR fixing the problem:

#62

The minimal action needed to get a co-maintainer going is to add them on Hackage:

https://hackage.haskell.org/package/unix-compat/maintainers/

(But preferably also give them write access to github.com/jacobstanley/unix-compat.)

Best regards,
Andreas

[mitchellwrosen]

Thanks for doing that @andreasabel, any response?

[andreasabel]

Thanks for doing that @andreasabel, any response?

No. I think you can go to step 2 of the takeover recipe:

State your intention to take over the package in a public forum (we recommend the haskell-cafe and/or libraries list). CC the maintainer.

[mitchellwrosen]

Thanks for the link, I've sent an email to [email protected]

[mitchellwrosen]

... well, I tried to, but I don't see my email anywhere in the archives: https://mail.haskell.org/pipermail/haskell-cafe/2023-February/thread.html

So maybe it has to be manually approved by someone first, or maybe I don't understand how mailing lists work. 🤷‍♂️

[andreasabel]

I didn't receive your email either on haskell-cafe.
But you had posts there previously, last in 2016, with id: Mitchell Rosen (mitchellwrosen gmail com).

[mitchellwrosen]

I'm not sure what to make of that. Here's a screenshot of the email I sent, which didn't bounce or anything.

[andreasabel]

Maybe just resend it, to both the cafe and the libraries list. I also looked at https://discourse.haskell.org/ but it seems takeover requests are not published there.

[andreasabel]

Takeover request announced 2023-02-04 on Haskell cafe: https://mail.haskell.org/pipermail/haskell-cafe/2023-February/135910.html

unix-compat has ~4000 indirect dependencies according to Hackage:

79 direct, 3945 indirect [details]

[andreasabel]

@mitchellwrosen proceeded with the next step on 2023-02-21.

Send an email to the hackage administrators ([email protected]), with a link to the public email thread.

[mitchellwrosen]

Hehe, thanks for taking the minutes during all of this @andreasabel

[gbaz]

added to maintainers. 👍

[mitchellwrosen]

Excellent, thank you!

[andreasabel]

@mitchellwrosen : You can do a hackage upload now. But hopefully @jacobstanley will show up for one of these:

1. Take up maintenance again.
2. Add you as co-maintainer here on this repo with write access.
3. Transfer this repo to a new location where you have write & admin access.

This is to ensure the continuity of issue numbers, for instance.

[mitchellwrosen]

Indeed, that would be great. However, in the meantime, I don't see a great path forward other than forking the repo and pointing people away from this one.

[andreasabel]

@mitchellwrosen : Consider moving it to an organization like unix-compat or unix-compat-hs or so. Like I did in https://github.com/blaze-builder/blaze-builder . Then you can have co-maintainers on par. Having fallback maintainers for important packages like this one is anyway a good idea.

[mitchellwrosen]

@andreasabel Good idea. What do you think about making an org to house both of these orphaned packages, and possibly others? Something like haskell-community/?

[andreasabel]

In this case, it could maybe go directly to https://github.com/haskell (it already has unix).

Or, if you prefer a less ambitious home, https://github.com/orgs/haskell-pkg-janitors . This one started out great, but currently only has haskell-src actively maintained (and lots of passive founding members).
I would prefer reactivating haskell-pkg-janitors over making a new organisation with similar goals.

Btw. see discussion at

• Introduce Haskell Party proposal haskellfoundation/stability#12

@mitchellwrosen : I sent you an invitation to haskell-pkg-janitors in case you choose this one.

[mitchellwrosen]

Great, haskell-pkg-janitors sounds like an excellent home for now.

[mitchellwrosen]

@andreasabel Can you please make me an owner of haskell-pkg-janitors? As a member, I can't make a new repo

[andreasabel]

Ok, did that!