public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: edk2-devel@lists.01.org
Cc: stephano <stephano.cetola@linux.intel.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Fri, 16 Nov 2018 13:52:16 -0700	[thread overview]
Message-ID: <3042685.gzUHUCRiql@photon.int.bluestop.org> (raw)
In-Reply-To: <b94ec094-1072-3fd8-6805-732a9a4bc8af@linux.intel.com>

On Friday, 16 November 2018 12:13:37 MST stephano wrote:
> The only reason I didn't include Slack is that it will only log so much
> information before things start falling off into the ether.
> 
> Does anyone in the community currently use Slack and know of an easy way
> of archiving conversations publicly?

I'm in several Slack teams: it seems to be the go-to solution for persistent 
chat nowadays. None of those pay (i.e. they're on the free tier), so are 
subject to its 10,000 message history limit.

Another option may be Conpherence, which comes with Phabricator: https://
www.phacility.com/phabricator/conpherence/ :

"Conpherence is a group messaging application integrated into Phabricator. 
Message one-on-one or with a group of people, name your room, and keep a 
history of everything in one place. Reply via email, on the web, or on your 
mobile device.

Conpherence supports Remarkup that makes it easy to link to Maniphest tasks 
and code reviews, share code snippets, format tables, and share memes. 
Conpherence even has a persistent chat sidebar built-in, so you don't need to 
keep another tab open."

-- 
Rebecca




  parent reply	other threads:[~2018-11-16 20:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:59 [edk2-announce][RFC] Collaboration Software stephano
2018-11-16 17:35 ` Kevin D Davis
2018-11-16 17:56   ` Zimmer, Vincent
2018-11-16 19:13     ` stephano
2018-11-16 19:55       ` Kinney, Michael D
2018-11-16 20:46         ` stephano
2018-11-16 22:14           ` Philippe Mathieu-Daudé
2018-11-17  0:34             ` stephano
2018-11-17  0:37               ` Rebecca Cran
2018-11-17  1:36                 ` stephano
2018-11-19 10:46             ` Tomas Pilar (tpilar)
2018-11-17  2:42         ` Sean Brogan
2018-11-17  4:58           ` Rebecca Cran
2018-11-17 19:01           ` stephano
2018-11-17 21:22             ` Rudra ठाकुर
2018-11-17 22:03           ` Rebecca Cran
2018-11-16 20:52       ` Rebecca Cran [this message]
2018-11-16 21:42         ` stephano
2018-11-16 21:51           ` Rebecca Cran
2018-11-17  0:22             ` stephano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3042685.gzUHUCRiql@photon.int.bluestop.org \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox