# \[ANNOUNCE\] elm-community status changed to "sunset"

**URL:** <https://discourse.elm-lang.org/t/announce-elm-community-status-changed-to-sunset/8883>\
**Category:** Show and Tell\
**Created:** [January 13, 2023, 1:41pm UTC](https://discourse.elm-lang.org/t/announce-elm-community-status-changed-to-sunset/8883 "2023-01-13T13:41:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rupert](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/rupert/32/1775_2.png) [@rupert](https://discourse.elm-lang.org/u/rupert)\
**Post date:** [January 13, 2023, 1:41pm UTC](https://discourse.elm-lang.org/t/announce-elm-community-status-changed-to-sunset/8883/1 "2023-01-13T13:41:44Z")

</div>

It was decided by approximate concensus that the `elm-community` GitHub org, should not take on any new packages. Instead, if an important package becomes unmaintained, users should just fork it themselves if they want to continue maintaining it. This could make it harder to find the right package amongst many clones, but has other advantages as a more asynchronous way of working.

It seemed generally accpeted that the various `*-extra` packages that exist in elm-community, are a good set to keep there, and should continue to be maintained there.

You can find the discussion (temporarily) on the Elm Slack #elm-community channel, if you wish.

The guidelines have been updated to reflect this new status, and Evan provided a short history and summary of the GitHub org.

> **[GitHub - elm-community/guidelines: guidelines for \*-extra contributors](https://github.com/elm-community/guidelines)**
>
> guidelines for \*-extra contributors. Contribute to elm-community/guidelines development by creating an account on GitHub.

> <https://github.com/elm-community/guidelines/blob/master/history.md>

---

<div class="post-metadata">

**Author:** ![rupert](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/rupert/32/1775_2.png) [@rupert](https://discourse.elm-lang.org/u/rupert)\
**Post date:** [January 13, 2023, 1:46pm UTC](https://discourse.elm-lang.org/t/announce-elm-community-status-changed-to-sunset/8883/2 "2023-01-13T13:46:41Z")

</div>

I was maintainer of `elm-community/typed-svg`, I will now fork that as `the-set/typed-svg`. My thinking is that whilst typed-svg is useful, its also not the easiest thing to use. Someone could conceivably come up with a better SVG package that is also typed - some kind of DSL or better concept for dealing with the large size of SVG.

So there is no particular reason for typed-svg to be considered special, or the default option to pick here.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [January 23, 2023, 1:47pm UTC](https://discourse.elm-lang.org/t/announce-elm-community-status-changed-to-sunset/8883/3 "2023-01-23T13:47:15Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.