Closed larsrh closed 8 years ago
I'm really not in favour of a move. For better or worse we've established communities around gitter and I don't think we should change unless there's something very concrete and very significant to be gained from moving.
As far as I can tell one of the advantages is that it offers a long-term solution for storing discussions; in fact, this feature is even built in. There's no such thing for Gitter. And in my personal experience, searching Discourse is easier than searching Gitter.
The other day i wanted to find some old posts on docker from this channel:
docker site:https://gitter.im/typelevel/general/archives
Seems OK to me
I don't know when typelevel/general started, but I found the initial message from another chat in January 2015. I think the archives are fine until Gitter dies or turns heel. To protect our history without upsetting the established community, maybe something like a backup with archive-gitter, or some other API solution?
I didn't know that existed, but it seems like a reasonable solution for permanent archival.
On 4 October 2016 16:57:29 CEST, "Ross A. Baker" notifications@github.com wrote:
I don't know when typelevel/general started, but I found the initial message from another chat in January 2015. I think the archives are fine until Gitter dies or turns heel. To protect our history without upsetting the established community, maybe something like a backup with archive-gitter, or some other API solution?
You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/typelevel/general/issues/41#issuecomment-251413307
I like that's it is libre, and not some proprietary vaporware like gitter. Still, it's not a replacement for gitter it's a different medium and would perhaps allow longer discussions around individual topics. Arguably that could also happen on tickets.
This seems to be overwhelmingly not desired. Closing this for now.
There are plans to consider this in Ensime (ensime/ensime.github.io#171), but this actually makes sense as a central Typelevel "service" too.
Clarification: This is a ticket for discussion. It's not a done deal.