¿Cómo utiliza Team Discourse Discourse?

[HAWK]

Originally published at: How Does Team Discourse Use Discourse?

As we claim on our website, we use Discourse as our primary team coordination tool to build… Discourse! That means escaping email silos and minimising the number of disparate communication channels required to manage a fully distributed team. We are able to keep distractions like calls and meetings to a minimum and focus on actual…

[8BIT]

holy cow. this is awesome. the idea had crossed my mind to use discourse as a full-bodied business communication and project system… but hearing it from you guys really does make it seem doable.

[mikechristopher]

great insight thanks @HAWK - just shows how flexible it certainly can be if you want it to be!

[oiclid (oïclid)]

So, Discourse is essentially the One Ring. Sauron would be proud. I love how you guys have figured out a way to get rid of all the distractions by building most of the features you need into one app.

[joebuhlig]

I was thinking about this just last week! I remembered @HAWK saying she was working on it. Thrilled to see it come to life. Well, done.

[townsfolk (Eric Berry)]

This is awesome. Thank you very much!

I have a follow up question regarding task management.

Are you tracking commits with tasks for those that have code changes through discourse? Something similar to the way Jira w/ BitBucket or Github works?

I found a couple of plugins and topics that are related:

Introducing GitHub Issues to Discourse

This tool is no longer maintained. Check out Discourse Code Review instead. The Discourse Team and I are pleased to announce our Import GitHub Issues into Discourse tool. The idea behind it is fairly simple, authenticate with GitHub, select the issues you wish to import, and then provide your Discourse credentials and let it do the rest (as shown in the screenshots below)! Authenticate with GitHub [image] Select a Repository [image] Select the Issues you want to Import [ima…

• Seems nice if you are/were using Github issues and want to mirror them in Discourse and use Discourse to further the conversation, but not if you don’t want to use Github issues.

https://meta.discourse.org/t/the-github-linkback-plugin/66081

• Looks for mentions in Discourse and then adds links to GH messages.

I realize that this can be done easily by manually pasting a Github/BitBucket commit into Discourse, but I’m curious if there’s something automatic.

Thank you again for the great post!

[HAWK]

Hey Eric,
We use Github Linkback but we don’t have anything automated.

[Bas (Bas van Leeuwen)]

Very cool!
Currently in the process of weaning people of from Hipchat in my org. and this is some very valuable input.

One question: why are you running two different instances? Wouldn’t it be possible to merge your internal one with meta and use subforums for everything?

Is it a matter of convenience? Was it set up before the tooling was ready? Don’t you trust the authentication/security model completely?

[HAWK]

A couple of reasons.

Our internal instance sits on a different server so if Meta goes down we don’t lose all our runbooks etc.
It also allows us to have very different email and notification settings which means we’re less likely to miss important things in the noise.

[Bas (Bas van Leeuwen)]

Fair and logical reasons

@HAWK

if Meta goes down we don’t lose all our runbooks etc.

That brings up painful memories (we once stored our emergency customer contact list on the wiki, in the datacenter, where all the customer were hosted…)

[sam (Sam Saffron)]

Yeah we do too… but we have a replica in digital ocean and an extensive encrypted backup story

[James_Houston]

the idea had crossed my mind to use discourse as a full-bodied business communication and project system… but hearing it from you guys really does make it seem doable.

[Xavi_Beumala]

Tenemos una instancia de Discourse que estamos utilizando internamente como centro para los equipos. Queremos abrir ciertos aspectos al público y otros a los clientes.

He leído el artículo ¿Cómo usa Team Discourse Discourse? y me preguntaba por qué usan 2 instancias separadas: pública e interna.

Nosotros vamos a usar una única instancia y restringiremos la visibilidad a través de grupos de usuarios. Los beneficios que vemos inicialmente de un enfoque de instancia única son la centralización y el gráfico de enlaces que podemos construir… Pero después de leer el artículo, sería muy interesante si alguien pudiera compartir los pros/contras de 2 instancias y ¿cómo le va a Team Discourse?

¡Muchas gracias!

[Moin]

No fuiste el único con esa pregunta

@Bas

Una pregunta: ¿por qué ejecutas dos instancias diferentes?

How Does Team Discourse Use Discourse?

A couple of reasons. Our internal instance sits on a different server so if Meta goes down we don’t lose all our runbooks etc. It also allows us to have very different email and notification settings which means we’re less likely to miss important things in the noise.

[Falco]

Otra razón es el uso interno (dogfooding) del caso de uso de múltiples instancias, ya que tenemos clientes que alojan docenas de instancias con nosotros.

Tenemos un “oneboxing” especial entre instancias de Discourse, podemos recibir notificaciones centralizadas a través de Web Push, correo electrónico, Discourse Hub, abrir instancias una al lado de la otra en dispositivos móviles a través de PWA, etc.

[justin (Justin DiRose)]

@Xavi_Beumala

Pero después de leer el artículo, sería muy interesante si alguien pudiera compartir los pros/contras de 2 instancias y ¿cómo va para el equipo de Discourse?

El mayor desafío de usar una sola instancia para un lugar de trabajo: podrías compartir accidentalmente algo públicamente que debería ser privado. Solo bastaría con seleccionar la categoría incorrecta o establecer permisos incorrectos en una nueva categoría.

Para resumir cómo va ahora:

1. ¡Genial! Nos ha permitido apoyar y obtener comentarios reales de todos los que usan Discourse en Discourse sin los riesgos descritos anteriormente.
2. Nuestra instancia interna fue una inspiración para Discourse for Teams. Hay mucho potencial para que las empresas utilicen una herramienta como Discourse para construir una comunidad interna.
3. Hay mucha actividad en ambas comunidades, por lo que siempre estamos buscando formas de asegurarnos de conectarnos con ambas a medida que nuestro equipo y Meta crecen.

[Richie (Richie Rich)]

Una lectura fascinante, gracias por compartirla (no estoy seguro de cómo me la perdí hasta ahora).