Find an alternative maintainer #79
Comments
|
Ah, was meaning to talk to you about this after reading your comments on
GitHub.
I think this is a good idea.
Thank you for the time and work you've put in thus far. I will begin
looking for a new maintainer. Anyone on the CLC can step in if they want,
at least hopefully as an interim? I have no interest in maintaining
filepath long-term (or even short term) myself. I am not super worried
since filepath is pretty stable.
Looping in phadej and bgamari since they may have good ideas for
maintainers.
…On Mon, Jul 27, 2020, 9:40 AM Neil Mitchell ***@***.***> wrote:
My interest in maintaining this library is waning. There are a bunch of
minor but interesting discussions to be had (e.g. #73
<#73>) and maintenance work to
change or not-change CI (e.g. #77
<#77>). I don't typically follow
the approach or tooling of the other libraries maintained by the CLC, and
have little interest in starting. All these factors combined make me think
that finding a new maintainer is not a bad idea.
CC @haskell/core-libraries-committee
<https://github.com/orgs/haskell/teams/core-libraries-committee>
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#79>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEOIX2ZVM3BMLFOQF2DPTJDR5WUXLANCNFSM4PI7BSYA>
.
|
|
- I'd ask `directory` maintainers. These two libraries are closely related.
- I'd avoid people with opinionated ideas on how path library should
look like (e.g. authors of `path`, `hpath`, `paths`, ...), except if CLC
wants filepaths in base to move into some of the packages' direction
- Windows experience is a plus (4 of 13 of open issues is about that)
- Oleg
…On 27.7.2020 19.52, chessai wrote:
Ah, was meaning to talk to you about this after reading your comments
on GitHub.
I think this is a good idea.
Thank you for the time and work you've put in thus far. I will begin
looking for a new maintainer. Anyone on the CLC can step in if they
want, at least hopefully as an interim? I have no interest in
maintaining filepath long-term (or even short term) myself. I am not
super worried since filepath is pretty stable.
Looping in phadej and bgamari since they may have good ideas for
maintainers.
On Mon, Jul 27, 2020, 9:40 AM Neil Mitchell ***@***.***
***@***.***>> wrote:
My interest in maintaining this library is waning. There are a
bunch of minor but interesting discussions to be had (e.g. #73
<#73>) and maintenance
work to change or not-change CI (e.g. #77
<#77>). I don't typically
follow the approach or tooling of the other libraries maintained
by the CLC, and have little interest in starting. All these
factors combined make me think that finding a new maintainer is
not a bad idea.
CC @haskell/core-libraries-committee
<https://github.com/orgs/haskell/teams/core-libraries-committee>
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#79>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEOIX2ZVM3BMLFOQF2DPTJDR5WUXLANCNFSM4PI7BSYA>.
|
|
Thanks Oleg,
Those are great guidelines.
…On Mon, Jul 27, 2020, 11:20 AM Oleg Grenrus ***@***.***> wrote:
- I'd ask `directory` maintainers. These two libraries are closely related.
- I'd avoid people with opinionated ideas on how path library should look
like (e.g. authors of `path`, `hpath`, `paths`, ...), except if CLC wants
filepaths in base to move into some of the packages' direction
- Windows experience is a plus (4 of 13 of open issues is about that)
- Oleg
On 27.7.2020 19.52, chessai wrote:
Ah, was meaning to talk to you about this after reading your comments on
GitHub.
I think this is a good idea.
Thank you for the time and work you've put in thus far. I will begin
looking for a new maintainer. Anyone on the CLC can step in if they want,
at least hopefully as an interim? I have no interest in maintaining
filepath long-term (or even short term) myself. I am not super worried
since filepath is pretty stable.
Looping in phadej and bgamari since they may have good ideas for
maintainers.
On Mon, Jul 27, 2020, 9:40 AM Neil Mitchell ***@***.***>
wrote:
> My interest in maintaining this library is waning. There are a bunch of
> minor but interesting discussions to be had (e.g. #73
> <#73>) and maintenance work to
> change or not-change CI (e.g. #77
> <#77>). I don't typically follow
> the approach or tooling of the other libraries maintained by the CLC, and
> have little interest in starting. All these factors combined make me think
> that finding a new maintainer is not a bad idea.
>
> CC @haskell/core-libraries-committee
> <https://github.com/orgs/haskell/teams/core-libraries-committee>
>
> —
> You are receiving this because you are on a team that was mentioned.
> Reply to this email directly, view it on GitHub
> <#79>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEOIX2ZVM3BMLFOQF2DPTJDR5WUXLANCNFSM4PI7BSYA>
> .
>
|
|
Any updates on this? |
I've reached out to a potential maintainer just a few moments ago. Waiting to hear back. |
Closed
|
Dear CLC members, as we discussed internally, +1 from myself. |
|
+1 from me!
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Sunday, November 21st, 2021 at 1:31 PM, Bodigrim ***@***.***> wrote:
Dear CLC members, as we [discussed internally](https://groups.google.com/g/haskell-core-libraries/c/Z93zUA_QVw0), filepath still needs a maintainer. ***@***.***(https://github.com/hasufell) has kindly signalled that he could be interested to take on the burden. I suggest we approve him as a new maintainer of filepath, please vote below.
CC ***@***.***(https://github.com/chessai) ***@***.***(https://github.com/cgibbard) ***@***.***(https://github.com/emilypi) ***@***.***(https://github.com/cigsender) ***@***.***(https://github.com/gwils)
---------------------------------------------------------------
+1 from myself.
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#79 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEK2TBY4444VGHRIWPSCGFTUNE3HVANCNFSM4PI7BSYA).
|
|
+1
…On Sun, Nov 21, 2021, 16:03 Melanie Brown ***@***.***> wrote:
+1 from me!
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, November 21st, 2021 at 1:31 PM, Bodigrim ***@***.***> wrote:
> Dear CLC members, as we [discussed internally](
https://groups.google.com/g/haskell-core-libraries/c/Z93zUA_QVw0),
filepath still needs a maintainer. ***@***.***(https://github.com/hasufell)
has kindly signalled that he could be interested to take on the burden. I
suggest we approve him as a new maintainer of filepath, please vote below.
> CC ***@***.***(https://github.com/chessai) ***@***.***(
https://github.com/cgibbard) ***@***.***(https://github.com/emilypi)
***@***.***(https://github.com/cigsender) ***@***.***(
https://github.com/gwils)
>
> ---------------------------------------------------------------
>
> +1 from myself.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, [view it on GitHub](
#79 (comment)), or
[unsubscribe](
https://github.com/notifications/unsubscribe-auth/AEK2TBY4444VGHRIWPSCGFTUNE3HVANCNFSM4PI7BSYA).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEOIX27CAMS4SGS3RBUMCOTUNFUETANCNFSM4PI7BSYA>
.
|
|
+1 here
…On Sun, Nov 21, 2021, 4:44 PM chessai ***@***.***> wrote:
+1
On Sun, Nov 21, 2021, 16:03 Melanie Brown ***@***.***> wrote:
> +1 from me!
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, November 21st, 2021 at 1:31 PM, Bodigrim ***@***.***> wrote:
>
> > Dear CLC members, as we [discussed internally](
> https://groups.google.com/g/haskell-core-libraries/c/Z93zUA_QVw0),
> filepath still needs a maintainer. ***@***.***(
https://github.com/hasufell)
> has kindly signalled that he could be interested to take on the burden. I
> suggest we approve him as a new maintainer of filepath, please vote
below.
> > CC ***@***.***(https://github.com/chessai) ***@***.***(
> https://github.com/cgibbard) ***@***.***(https://github.com/emilypi)
> ***@***.***(https://github.com/cigsender) ***@***.***(
> https://github.com/gwils)
> >
> > ---------------------------------------------------------------
> >
> > +1 from myself.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, [view it on GitHub](
> #79 (comment)),
or
> [unsubscribe](
>
https://github.com/notifications/unsubscribe-auth/AEK2TBY4444VGHRIWPSCGFTUNE3HVANCNFSM4PI7BSYA
).
>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#79 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AEOIX27CAMS4SGS3RBUMCOTUNFUETANCNFSM4PI7BSYA
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPZRTVGERHBC7YVFNXPNWLUNF76BANCNFSM4PI7BSYA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
+1 |
@hasufell you should now have admin rights on this repo. Or at least an invitation to gain them (GitHub didn't make it clear which was the case). |
|
I've added maerwald as a maintainer on hackage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My interest in maintaining this library is waning. There are a bunch of minor but interesting discussions to be had (e.g. #73) and maintenance work to change or not-change CI (e.g. #77). I don't typically follow the approach or tooling of the other libraries maintained by the CLC, and have little interest in starting. All these factors combined make me think that finding a new maintainer is not a bad idea.
CC @haskell/core-libraries-committee
The text was updated successfully, but these errors were encountered: