From: stephano <stephano.cetola@linux.intel.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Rebecca Cran" <rebecca@bluestop.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Fri, 16 Nov 2018 16:34:09 -0800 [thread overview]
Message-ID: <88894427-2297-8828-e4d3-8478e6d60e5b@linux.intel.com> (raw)
In-Reply-To: <08c22515-92a7-ea6d-0290-5f2490528565@redhat.com>
On 11/16/2018 2:14 PM, Philippe Mathieu-Daudé wrote> For people on the
move, having bad internet (3rd world countries), email
> system is very powerful, you can download once and work offline,
> reading/answering. You can also download the list archive and refers to
> it offline. You also have access to all patches and can apply them
> offline too.
>
> Is this possible with GitHub?
I am going to guess that GitHub assumes a stable internet connection to
participate in discussions. I'll double check this. You bring up a good
point.
>
> Maybe the open source alternative, GitLab, offers a such feature.
>
> Googling "gitlab offline" I get:
>
> "Many of our customers do not have regular Internet access and many of
> them, being highly regulated, cannot install local copies of GitLab to
> be able to run against the provided API. [...] The work, published as
> the gitlab-ci-yaml_lint gem, is my attempt at a start to solving the
> issue."
>
> This is not what I expected, but it confirms some people have troubles
> working with online-only services.
We are currently evaluating Gitlab to improve our code review needs. I
will look into Gitlab as a discussion platform as well. Specifically how
it interacts with email.
Rebecca Cran also brought up that Phabricator allows discussions to be
interacted with via email. A quick search for Phabricator and
"Configuring Inbound Email" it seems that one can both receive and send
discussion messages if configured properly.
Rebecca, can you confirm this?
next prev parent reply other threads:[~2018-11-17 0:34 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 [this message]
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
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=88894427-2297-8828-e4d3-8478e6d60e5b@linux.intel.com \
--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