public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: stephano <stephano.cetola@linux.intel.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Fri, 16 Nov 2018 14:51:20 -0700	[thread overview]
Message-ID: <1995822.3V7qYkmoPJ@photon.int.bluestop.org> (raw)
In-Reply-To: <2d27a65c-2eb9-6d68-baba-3cbca98561c9@linux.intel.com>

On Friday, 16 November 2018 14:42:44 MST stephano wrote:

> This is a great suggestion, thanks! Two questions:

> 1. Does it allow you to export your conversations in some way?

Conversations can followed via email, so that's one way of 'exporting' them. 
But otherwise, I suspect you'd need to either query the database directly or 
use "./bin/storage dump":

DUMP WORKFLOW

dump [options]
Dump all data in storage to stdout.

      --compress
          With --output, write a compressed file to disk instead of a
          plaintext file.

      --for-replica
          Add --master-data to the mysqldump command, generating a CHANGE
          MASTER statement in the output.

      --no-indexes
          Do not dump data in rebuildable index tables. This means backups
          are smaller and faster, but you will need to manually rebuild
          indexes after performing a restore.

      --output file
          Write output directly to disk. This handles errors better than
          using pipes. Use with --compress to gzip the output.

      --overwrite
          With --output, overwrite the output file if it already exists.


> 2. Is there a "file sharing" option if we wanted to, for example, share
> a JPG or ODF file?

Yes: Phabricator has a general file storage service, and files can be uploaded 
via that and shared in Conpherence.

-- 
Rebecca




  reply	other threads:[~2018-11-16 21:51 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
2018-11-16 21:42         ` stephano
2018-11-16 21:51           ` Rebecca Cran [this message]
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=1995822.3V7qYkmoPJ@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