Future of lucid

[Simon Jakobi]

That's good to hear, Chris!

Can I suggest to include a version of this explanation in the README?

Maybe you could also suggest that people post their questions on SO
using the haskell-lucid tag:
https://stackoverflow.com/questions/tagged/haskell-lucid

Cheers!
Simon

Am Mi., 10. Juni 2020 um 15:23 Uhr schrieb chris done
<haskell-cafe at chrisdone.com>:
>
> Hi Simon,
>
> I am still maintaining and actively using the package. Architecture-wise, nothing substantial has changed in the 6 years since its release. Just small additions. This package pretty much maintains itself. PRs come and go.
>
> In fact, any kind of overhauls or user-facing design changes at this stage would cause disruption and I would encourage that to be achieved in a separate package with a new name. In review, I'm very happy with Lucid's design and plan to maintain it long-term into the future for as long as HTML is relevant.
>
> However, I am providing no Q&A or "tech support". Having an issue tracker would say otherwise.
>
> Oleg is also a maintainer.
>
> Cheers,
>
> Chris
>
> On Tue, Jun 9, 2020, at 5:27 AM, Simon Jakobi wrote:
>
> Hi!
>
> I recently noticed that the issue tracker for the lucid package at
>
> https://github.com/chrisdone/lucid
>
> has been disabled. Does this have any implications for the future
> maintenance of the package? Is anyone still committed to maintaining
> the package?
>
> (I've CC'd Oleg who made the most recent commit to the repo.)
>
> The context for my question is that we'd like to use lucid for the
> Dhall documentation generator that is being developed as a part of
> this year's GSoC.
>
> Thanks!
> Simon
>
>