Come utilizza 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]

Abbiamo un’istanza di Discourse che stiamo utilizzando internamente come hub per i team. Vogliamo aprire alcuni aspetti al pubblico e altri ai clienti.

Ho letto l’articolo Come Team Discourse utilizza Discourse e mi stavo chiedendo perché utilizzate 2 istanze separate: pubblica e interna?

Noi opteremo per 1 unica istanza e limiteremo la visibilità tramite gruppi di utenti. I vantaggi che vediamo inizialmente da un approccio a istanza unica sono la centralizzazione e il grafico di collegamenti che possiamo costruire… Ma dopo aver letto l’articolo, sarebbe molto interessante se qualcuno potesse condividere i pro/contro di 2 istanze e come sta andando per Team Discourse?

Molte grazie!

[Moin]

Non sei stato l’unico ad avere quella domanda

@Bas

Una domanda: perché stai eseguendo due istanze diverse?

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]

Un altro motivo è il dogfooding del caso d’uso di istanze multiple, poiché abbiamo clienti che ospitano decine di istanze con noi.

Abbiamo un oneboxing speciale tra istanze di Discourse, possiamo ricevere notifiche centralizzate tramite Web Push, Email, Discourse Hub, aprire istanze side-by-side sui dispositivi mobili tramite PWA, ecc.

[justin (Justin DiRose)]

@Xavi_Beumala

Ma dopo aver letto l’articolo sarebbe molto interessante se qualcuno potesse condividere i pro/contro di 2 istanze e come sta andando per il Team Discourse?

La sfida più grande dell’utilizzo di una singola istanza per un luogo di lavoro: potresti molto facilmente condividere accidentalmente qualcosa pubblicamente che dovrebbe essere privato. Basterebbe selezionare la categoria sbagliata o impostare permessi errati su una nuova categoria.

Per riassumere come sta andando ora:

1. Fantastico! Ci ha permesso di supportare e ottenere feedback reali da tutti coloro che utilizzano Discourse su Discourse senza i rischi sopra descritti.
2. La nostra istanza interna è stata d’ispirazione per Discourse for Teams. C’è molto potenziale per le aziende nell’utilizzare uno strumento come Discourse per costruire una community interna.
3. C’è molta attività in entrambe le community, quindi stiamo sempre cercando modi per assicurarci di connetterci con entrambe man mano che il nostro team e Meta crescono.

[Richie (Richie Rich)]

Una lettura affascinante, grazie per averla condivisa (non sono sicuro di come mi sia sfuggita prima d’ora).