Re: whither the maintainer for comp-data? request for NMU?
Carter Schonwald <[email protected]> Mon, 13 Mar 2023 16:35:12 -0400
| Newsgroups | gmane.comp.lang.haskell.libraries |
|---|---|
| Message-ID | <CAHYVw0w7vODwJ+a_s8Ap3+R4eRL-=fMTOLz+WHQkxZ9wxyQrUA@mail.gmail.com> |
--===============3447640296979616017== Content-Type: multipart/alternative; boundary="0000000000003ce2cf05f6ce0d2a" --0000000000003ce2cf05f6ce0d2a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable welcome back! ;) On Mon, Mar 13, 2023 at 4:12=E2=80=AFAM Patrick Bahr <[email protected]> wrote: > Andreas, Carter, > > Apologies for neglecting my maintainer duties on comp-data. I will catch > up on it this week. > > I'd happily accept a co-maintainer, but I don't have any candidate. > > -- Patrick > > ________________________________________ > From: Carter Schonwald <[email protected]> > Sent: 01 March 2023 00:32 > To: Andreas Abel > Cc: Haskell Libraries; Patrick Bahr; [email protected] > Subject: Re: whither the maintainer for comp-data? request for NMU? > > Andreas: thanks for ccing Patrick! > > At the very least, data comp is an amazing exploration of pushing data > type a la carte style engineering to its limits and keeping it buildable > seems valuable > > Happily the main issue seems to be a matter of migrating some template > Haskell > > On Tue, Feb 28, 2023 at 11:59 AM Andreas Abel <[email protected] > <mailto:[email protected]>> wrote: > Patrick, maybe you would accept a co-maintainer for comp-data? > > But then, there should also be a co-maintainer wanting to take the job... > > Concerning NMUs, there is info here: > > https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#3= -source-changes-simple-patches > > On 2023-01-23 19:37, Carter Schonwald wrote: > > Hey everyone, > > https://github.com/pa-ba/compdata/issues/36 > > <https://github.com/pa-ba/compdata/issues/36> and many similar issues > > and 1-3 corresponding PRs have been posted to the comp-data repo, whats > > the current process for engaging the trustees in making an NMU that > > handles newer ghc support? (these issues have been standing for ~ a yea= r > > now). > > > > ideally the maintainer surfaces in the near future, but would be great > > to get it buildable again > > > > -Carter > --0000000000003ce2cf05f6ce0d2a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">welcome back! ;) <br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Mar 13, 2023 at 4:12=E2=80=AF= AM Patrick Bahr <<a href=3D"mailto:[email protected]">[email protected]</a>> wrot= e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0= .8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Andreas, Cart= er,<br> <br> Apologies for neglecting my maintainer duties on comp-data. I will catch up= on it this week.<br> <br> I'd happily accept a co-maintainer, but I don't have any candidate.= <br> <br> -- Patrick<br> <br> ________________________________________<br> From: Carter Schonwald <<a href=3D"mailto:[email protected]" ta= rget=3D"_blank">[email protected]</a>><br> Sent: 01 March 2023 00:32<br> To: Andreas Abel<br> Cc: Haskell Libraries; Patrick Bahr; <a href=3D"mailto:[email protected]" tar= get=3D"_blank">[email protected]</a><br> Subject: Re: whither the maintainer for comp-data? request for NMU?<br> <br> Andreas: thanks for ccing Patrick!<br> <br> At the very least, data comp is an amazing exploration of pushing data type= a la carte style engineering to its limits and keeping it buildable=C2=A0 = seems valuable<br> <br> Happily the main issue seems to be a matter of migrating some template Hask= ell<br> <br> On Tue, Feb 28, 2023 at 11:59 AM Andreas Abel <<a href=3D"mailto:andreas= [email protected]" target=3D"_blank">[email protected]</a><mailto:<= a href=3D"mailto:[email protected]" target=3D"_blank">andreas.abel@if= i.lmu.de</a>>> wrote:<br> Patrick, maybe you would accept a co-maintainer for comp-data?<br> <br> But then, there should also be a co-maintainer wanting to take the job...<b= r> <br> Concerning NMUs, there is info here:<br> <a href=3D"https://github.com/haskell-infra/hackage-trustees/blob/master/po= licy.md#3-source-changes-simple-patches" rel=3D"noreferrer" target=3D"_blan= k">https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#= 3-source-changes-simple-patches</a><br> <br> On 2023-01-23 19:37, Carter Schonwald wrote:<br> > Hey everyone,<br> > <a href=3D"https://github.com/pa-ba/compdata/issues/36" rel=3D"norefer= rer" target=3D"_blank">https://github.com/pa-ba/compdata/issues/36</a><br> > <<a href=3D"https://github.com/pa-ba/compdata/issues/36" rel=3D"nor= eferrer" target=3D"_blank">https://github.com/pa-ba/compdata/issues/36</a>&= gt; and many similar issues<br> > and 1-3 corresponding PRs have been posted to the comp-data repo, what= s<br> > the current process for engaging the trustees in making an NMU that<br= > > handles newer ghc support? (these issues have been standing for ~ a ye= ar<br> > now).<br> ><br> > ideally the maintainer surfaces in the near future, but would be great= <br> > to get it buildable again<br> ><br> > -Carter<br> </blockquote></div> --0000000000003ce2cf05f6ce0d2a-- --===============3447640296979616017== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTGlicmFyaWVz IG1haWxpbmcgbGlzdApMaWJyYXJpZXNAaGFza2VsbC5vcmcKaHR0cDovL21haWwuaGFza2VsbC5v cmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL2xpYnJhcmllcwo= --===============3447640296979616017==--