# Transition plan from Google Groups

**URL:** <https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20>\
**Category:** Show and Tell\
**Created:** [November 30, 2017, 8:22pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20 "2017-11-30T20:22:47Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [November 30, 2017, 8:22pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/1 "2017-11-30T20:22:47Z")

</div>

**TL;DR:** I’d like us to do a trial run for 30 days, then shutter Google Groups.

Steps:

1. Announce to elm-discuss that we’re trying to find alternatives. ([done](https://groups.google.com/d/msg/elm-discuss/ItctWqp1S3o/Cef47TLQAwAJ))
2. Allow existing threads to conclude but ask that all new posts be redirected here.
3. After 30 days, put elm-discuss in read-only mode.
4. Change elm-discuss links everywhere to point here.

If there are any problems with _that plan_, sound off in the replies. If you’re reading this and you’re part of trial, please create new threads so we can solve individual issues in individual threads.

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [November 30, 2017, 8:48pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/2 "2017-11-30T20:48:29Z")

</div>

Oh yeah, if I don’t hear any nays by tomorrow morning CST, I’m going to post on elm-discuss and start step #2. 🙂

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [November 30, 2017, 9:16pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/3 "2017-11-30T21:16:23Z")

</div>



---

<div class="post-metadata">

**Author:** ![splodingsocks](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/splodingsocks/32/26_2.png) [@splodingsocks](https://discourse.elm-lang.org/u/splodingsocks)\
**Post date:** [November 30, 2017, 11:14pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/4 "2017-11-30T23:14:48Z")

</div>

This looks great, @brian! Thank you for taking this initiative.

---

<div class="post-metadata">

**Author:** ![Steve\_Schafer](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@Steve\_Schafer](https://discourse.elm-lang.org/u/Steve_Schafer)\
**Post date:** [December 4, 2017, 2:03pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/5 "2017-12-04T14:03:14Z")

</div>

One thing that I’ve never understood about Discourse is that it both nests replies and also shows them linearly at the top level, at the same time. So you can easily end up seeing two copies of a single message (see screenshot). Does anyone think that this is a Good Thing? It makes no sense to me, and makes it difficult to follow the message hierarchy.

![seeingDouble](https://cdck-file-uploads-canada1.s3.dualstack.ca-central-1.amazonaws.com/flex035/uploads/elm_lang/original/1X/e678a820c95218df625708e3c6a916e14ba8b93c.png)

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [December 4, 2017, 2:17pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/6 "2017-12-04T14:17:15Z")

</div>

Yes, we’ve been talking about that in [Test help code doesn’t compile](https://discourse.elm-lang.org/t/test-help-code-doesnt-compile/18/16?u=brian). I will be monkeying around with the settings to see if we can alleviate how awkward this is. But I don’t think it’s a deal-breaker.

---

<div class="post-metadata">

**Author:** ![Steve\_Schafer](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@Steve\_Schafer](https://discourse.elm-lang.org/u/Steve_Schafer)\
**Post date:** [December 4, 2017, 4:04pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/7 "2017-12-04T16:04:14Z")

</div>

The thing that puzzles me is how anyone can think that this is a good way to present the info.

---

<div class="post-metadata">

**Author:** ![inder](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/inder/32/139_2.png) [@inder](https://discourse.elm-lang.org/u/inder)\
**Post date:** [December 5, 2017, 10:31am UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/8 "2017-12-05T10:31:14Z")

</div>

Here’s an official tutorial about migrating from google groups to discourse. Not sure how helpful but worth a look.

> **[Migration of Google Groups to Discourse](https://meta.discourse.org/t/migration-of-google-groups-to-discourse/48012?u=erlend_sh&source_topic_id=24695)**
>
> ⚠ This Howto is out-of-date. Please check out Importing mailing lists (mbox, Listserv, Google Groups, emails, ...) for updated instructions. Here is a ‘working prototype’ of a google group migration script that attempts to be more ‘all-in-one’...

---

<div class="post-metadata">

**Author:** ![igray](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/igray/32/117_2.png) [@igray](https://discourse.elm-lang.org/u/igray)\
**Post date:** [December 5, 2017, 3:45pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/9 "2017-12-05T15:45:19Z")

</div>

@brian, I’m [trying to add](https://github.com/oakesja/elm-news/pull/6) Discourse to the [elm-news](http://elm-news.com/) aggregator.

Unfortunately, the [API request](https://discourse.elm-lang.org/latest.json) throws a CORS error because the “access-control-allow-origin” header sent from the server is blank.

Would you be willing to allow either all servers (\*) CORS access, or at least [elm-news.com](http://elm-news.com)? I believe it’s a configuration called “cors\_origin” in the app.yml file.

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [December 5, 2017, 4:14pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/10 "2017-12-05T16:14:56Z")

</div>

@inder: Thanks for finding that, but I think we’re going to change elm-discuss to read-only and start fresh here. We’d have to categorize every single post ever over there. It’ll be available as long as Google still hosts groups so that discussions don’t get lost.

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [December 5, 2017, 4:15pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/11 "2017-12-05T16:15:51Z")

</div>

@igray I’ve added `http://elm-news.com` to the CORS origins. Please let me know if you run into any more trouble in a private message.

Edit: realized what a big hole that creates and turned it off again. Please message me and we’ll figure something out that will work for you without creating a vulnerability.

---

<div class="post-metadata">

**Author:** ![ldesgoui](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/ldesgoui/32/1000_2.png) [@ldesgoui](https://discourse.elm-lang.org/u/ldesgoui)\
**Post date:** [December 7, 2017, 12:42pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/13 "2017-12-07T12:42:30Z")

</div>

Hello, thanks for taking the time to do this.  
What would happen to r/elm in your best case scenario ?

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [December 7, 2017, 1:24pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/14 "2017-12-07T13:24:15Z")

</div>

I don’t see why anything should need to happen to it. People enjoy themselves there. It’s out of scope.

---

<div class="post-metadata">

**Author:** ![christian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/christian/32/1384_2.png) [@christian](https://discourse.elm-lang.org/u/christian)\
**Post date:** [December 11, 2017, 10:18pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/15 "2017-12-11T22:18:27Z")

</div>

Great choice with Discourse! A lot of features and functionality that make it far superior to Google Groups. Thank you for putting the time and effort in to guide this transition @brian.

---

<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:** [December 13, 2017, 2:33pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/16 "2017-12-13T14:33:28Z")

</div>

Hi Brian, Thanks for sorting out Discourse, this is much better than the google group.

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [December 26, 2017, 10:59pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/17 "2017-12-26T22:59:52Z")

</div>

We’re going to proceed with this migration by making Elm Discuss on Google Groups read-only on January 1, 2018. Most discussion has already migrated over to Discourse. We will be repointing links as we find them, please help out by moving any you control and letting me know about any we miss.

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [January 1, 2018, 7:20pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/18 "2018-01-01T19:20:38Z")

</div>

Google Groups is now read-only. Long live Discourse! 😛

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian/32/2180_2.png) [@brian](https://discourse.elm-lang.org/u/brian)\
**Post date:** [January 1, 2018, 7:20pm UTC](https://discourse.elm-lang.org/t/transition-plan-from-google-groups/20/19 "2018-01-01T19:20:44Z")

</div>