Como a Team Discourse usa o 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]

Temos uma instância do Discourse que estamos usando internamente como um centro para as equipes. Queremos abrir certos aspectos ao público e outros para os clientes.

Li o artigo Como o Team Discourse usa o Discourse e estava me perguntando por que vocês usam 2 instâncias separadas: pública e interna?

Estamos optando por 1 instância única e restringindo a visibilidade através de grupos de usuários. Os benefícios que inicialmente vemos de uma abordagem de instância única são a centralização e o gráfico de links que podemos construir… Mas depois de ler o artigo, seria muito interessante se alguém pudesse compartilhar os prós/contras de 2 instâncias e como está indo para o Team Discourse?

Muito obrigado!

[Moin]

Você não foi o único com essa pergunta

@Bas

Uma pergunta: por que você está executando duas instâncias 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]

Outro motivo é o uso interno (dogfooding) do caso de uso de múltiplas instâncias, pois temos clientes que hospedam dezenas de instâncias conosco.

Temos um oneboxing especial entre instâncias do Discourse, podemos obter notificações centralizadas via Web Push, E-mail, Discourse Hub, abrir instâncias lado a lado em dispositivos móveis via PWA, etc.

[justin (Justin DiRose)]

@Xavi_Beumala

Mas depois de ler o artigo, seria muito interessante se alguém pudesse compartilhar os prós/contras de 2 instâncias e como está indo para a Equipe Discourse?

O maior desafio de usar uma única instância para um local de trabalho: você poderia muito facilmente compartilhar acidentalmente algo publicamente que deveria ser privado. Bastaria selecionar a categoria errada ou definir permissões incorretas em uma nova categoria.

Para resumir como está indo agora:

1. Ótimo! Isso nos permitiu apoiar e obter feedback real de todos que usam o Discourse no Discourse sem os riscos descritos acima.
2. Nossa instância interna foi uma inspiração para o Discourse for Teams. Há muito potencial para empresas usarem uma ferramenta como o Discourse para construir uma comunidade interna.
3. Há muita atividade acontecendo em ambas as comunidades, então estamos sempre procurando maneiras de garantir que nos conectemos com ambas à medida que nossa equipe e a Meta crescem.

[Richie (Richie Rich)]

Uma leitura fascinante, obrigado por compartilhar (não tenho certeza de como perdi antes).