Your experience is not mine. Yes, I see support requests and general chatter on GitHub issue trackers I follow, but the volume is miniscule. In my own projects, I tend to close those down pretty quickly unless I think there's a special circumstance. On Wed, Jun 10, 2020, 12:05 PM chris done wrote:

Hi Gabriel,

I enabled the issue tracker earlier today for those reasons.

Unfortunately, GitHub doesn't distinguish between "mailing list where chat can occur" and "tasks the devs plan to put time and energy into", it's all dumped into one pot. I consider this a shortcoming of GitHub. It actually distorts the meaning of "to maintain" from "keeping the software correct and working" to "responding to and acknowledging any and all commentary by anyone at any time for any duration, teaching fellow developers about how to use Git, GitHub, among other mentorship tasks" the temporary or prolonged neglect of which is deemed to be not putting on a good show, or in your own words, "not maintaining it". The more I reflect on it, the more I see why many project maintainers burn out on GitHub.

I will continue using lucid and patching it to move with the times as GHC's type system moves along and HTML 5 elements/attributes are added, and merge pull requests related to these stated goals, for the foreseeable future, but I plan to do no more than that. If that's not good enough for Dhall, then there are plenty of other options.[1]

Cheers,

Chris

[1]: https://www.reddit.com/r/haskell/comments/h05uwn/experience_report_choosing_...

On Wed, Jun 10, 2020, at 4:26 PM, Gabriel Gonzalez wrote:

Would it be possible to leave the issue tracker on but just disable your own email notifications for the repository if you do not plan to maintain it? The two main reasons I suggest this are:

* We would like a way to be able to petition Oleg for changes (or whoever is the maintainer at the time) * We would like to know if other people share the same problem we do (or vice versa, educate other users of problems we are having and potential workarounds)

On Jun 10, 2020, at 6:23 AM, chris done wrote:

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 documentation generator that is being developed as a part of this year's GSoC.

Thanks! Simon

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Hey Chris, I definitely feel the same way about GitHub sometimes. I think some of this is often fallout from commercial development processes when a product is evolved using the wrong measurements for evaluating success or failures of change over time. I personally find nontechnical discourse beyond positive exhortations on issue trackers stressful and distracting. (This is an issue with linear threading more broadly when there’s any meaningful emotional dimension). Whatever approach (ethically!) facilitates you sustainably working on projects you have generously made open source / or act as the maintainer for, it is entirely your prerogative to work on them however you like. It’s all neat stuff and keep on having fun! Cheers -Carter On Wed, Jun 10, 2020 at 12:07 PM chris done wrote:

Hi Gabriel,

I enabled the issue tracker earlier today for those reasons.

Unfortunately, GitHub doesn't distinguish between "mailing list where chat can occur" and "tasks the devs plan to put time and energy into", it's all dumped into one pot. I consider this a shortcoming of GitHub. It actually distorts the meaning of "to maintain" from "keeping the software correct and working" to "responding to and acknowledging any and all commentary by anyone at any time for any duration, teaching fellow developers about how to use Git, GitHub, among other mentorship tasks" the temporary or prolonged neglect of which is deemed to be not putting on a good show, or in your own words, "not maintaining it". The more I reflect on it, the more I see why many project maintainers burn out on GitHub.

I will continue using lucid and patching it to move with the times as GHC's type system moves along and HTML 5 elements/attributes are added, and merge pull requests related to these stated goals, for the foreseeable future, but I plan to do no more than that. If that's not good enough for Dhall, then there are plenty of other options.[1]

Cheers,

Chris

[1]: https://www.reddit.com/r/haskell/comments/h05uwn/experience_report_choosing_...

On Wed, Jun 10, 2020, at 4:26 PM, Gabriel Gonzalez wrote:

Would it be possible to leave the issue tracker on but just disable your own email notifications for the repository if you do not plan to maintain it? The two main reasons I suggest this are:

* We would like a way to be able to petition Oleg for changes (or whoever is the maintainer at the time) * We would like to know if other people share the same problem we do (or vice versa, educate other users of problems we are having and potential workarounds)

On Jun 10, 2020, at 6:23 AM, chris done wrote:

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 documentation generator that is being developed as a part of this year's GSoC.

Thanks! Simon

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.