public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: stephano <stephano.cetola@linux.intel.com>
To: Sean Brogan <sean.brogan@microsoft.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Sat, 17 Nov 2018 11:01:23 -0800	[thread overview]
Message-ID: <7beff8ac-5b54-02ea-d33d-71cd1acb3830@linux.intel.com> (raw)
In-Reply-To: <CY4PR21MB0184DEF1B3355EF33C9D0742E1DE0@CY4PR21MB0184.namprd21.prod.outlook.com>

Hey Sean,

Thank you for your input. I'm going to run some tests with Github's 
discussions feature so that I have a good understanding of how it 
measures up to the offline capabilities of email. I think that was one 
of the only concerns brought up yesterday.

In terms of Phabricator, I'll admit, I'm very new to it and have a lot 
to learn. Could you elaborate a bit on the shortcomings you see, 
specifically integrations and searchability. If you could give specific 
examples that would help a lot in our research.

Thanks!

Cheers,
Stephano

On 11/16/2018 6:42 PM, Sean Brogan wrote:
> Mike,
> 
> I like the github teams option for discussion as it is just there, free, and easy.  It integrates nicely with all other parts of github.  Notifications are supported for those that want email.   Is there any reason this path doesn't get used now as a test since tianocore is already in github?
> 
> I really can't get behind the Phabricator tool suite as it just has too many downsides (self-hosted or pay, lack of integrations, lack of support and limited searchability, poor ci integration, etc).
> 
> Thanks
> Sean
> 
> 
> 
> -----Original Message-----
> From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Kinney, Michael D
> Sent: Friday, November 16, 2018 11:55 AM
> To: stephano <stephano.cetola@linux.intel.com>; Zimmer, Vincent <vincent.zimmer@intel.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Re: [edk2] [edk2-announce][RFC] Collaboration Software
> 
> Hi Stephano,
> 
> GitHub supports discussions for teams.
> 
> If we added a new team to the GitHub TianoCore organization for all developers that want to be involved in community topics and design discussions (which should closely match the current members of
> edk2-devel) then that may be a simple option that uses services that already there.
> 
> Another option is to use discussions for one of the exiting teams (e.g. Tianocore Maintainers) and make posts for these discussion topics public.
> 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.github.com%2F2017-11-20-introducing-team-discussions%2F&amp;data=02%7C01%7Csean.brogan%40microsoft.com%7C90c7b5b8e6544710547308d64bfd68ac%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636779949096981093&amp;sdata=m%2BL8FRVa3yxdwLYUaCF1qC%2FfZ9IUp5kigjiUMJxSzJo%3D&amp;reserved=0
> 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Farticles%2Fabout-team-discussions%2F&amp;data=02%7C01%7Csean.brogan%40microsoft.com%7C90c7b5b8e6544710547308d64bfd68ac%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636779949096991106&amp;sdata=5QLuiHfs%2FmgR3UHC4BeYasDWAkf5zBR5s71ttRmeNAg%3D&amp;reserved=0
> 
> Best regards,
> 
> Mike
> 
> 
> 
> 
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org]
>> On Behalf Of stephano
>> Sent: Friday, November 16, 2018 11:14 AM
>> To: Zimmer, Vincent <vincent.zimmer@intel.com>; edk2-
>> devel@lists.01.org
>> Subject: Re: [edk2] [edk2-announce][RFC] Collaboration Software
>>
>> 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?
>>
>>
>> On 11/16/2018 9:56 AM, Zimmer, Vincent wrote:
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsla
>>> ck.com%2F&amp;data=02%7C01%7Csean.brogan%40microsoft.com%7C90c7b5b8e
>>> 6544710547308d64bfd68ac%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7
>>> C636779949096991106&amp;sdata=flNeQfd9Tq2yX7ZUouV8pkINvofIRjeSoaTB6Y
>>> ojWPg%3D&amp;reserved=0
>>>
>>> -----Original Message-----
>>> From: edk2-devel [mailto:edk2-devel-
>> bounces@lists.01.org] On Behalf Of Kevin D Davis
>>> Sent: Friday, November 16, 2018 9:35 AM
>>> To: stephano <stephano.cetola@linux.intel.com>; edk2-
>> devel@lists.01.org
>>> Subject: Re: [edk2] [edk2-announce][RFC] Collaboration
>> Software
>>>
>>>
>>>
>>>
>>>
>>>
>>>       	If we get to vote, I’d vote against Google
>> Groups.  Their interface is very geared toward their internal work
>> flow and seems to change on a whim.
>> Thanks,Kevin
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Nov 16, 2018 at 11:08 AM -0600, "stephano"
>> <stephano.cetola@linux.intel.com> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> We are looking to augment our current communication
>> methods (mailing list / IRC) with a modern solution for group
>> collaboration. The goal is to allow folks to communicate effectively
>> without interrupting the current patch review system, as well as
>> enabling any future systems with more robust options.
>>>
>>> Specific features we are looking for include
>> attachments (currently blocked by the list), robust logging, modern
>> chat, and integration with tools like bug trackers and source
>> repositories (APIs, or better yet, pre-rolled plugins).
>>>
>>> Our current contenders are Google Groups and Groups.io.
>> This RFC is in hopes of finding other options to evaluate.
>>>
>>> Cheers,
>>> Stephano
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis
>>> ts.01.org%2Fmailman%2Flistinfo%2Fedk2-devel&amp;data=02%7C01%7Csean.
>>> brogan%40microsoft.com%7C90c7b5b8e6544710547308d64bfd68ac%7C72f988bf
>>> 86f141af91ab2d7cd011db47%7C1%7C0%7C636779949096991106&amp;sdata=B147
>>> wIbtDPoPYvHzds53CFlU6BBa9UKjoAuCJ8LMWFc%3D&amp;reserved=0
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis
>>> ts.01.org%2Fmailman%2Flistinfo%2Fedk2-devel&amp;data=02%7C01%7Csean.
>>> brogan%40microsoft.com%7C90c7b5b8e6544710547308d64bfd68ac%7C72f988bf
>>> 86f141af91ab2d7cd011db47%7C1%7C0%7C636779949096991106&amp;sdata=B147
>>> wIbtDPoPYvHzds53CFlU6BBa9UKjoAuCJ8LMWFc%3D&amp;reserved=0
>>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists
>> .01.org%2Fmailman%2Flistinfo%2Fedk2-devel&amp;data=02%7C01%7Csean.brog
>> an%40microsoft.com%7C90c7b5b8e6544710547308d64bfd68ac%7C72f988bf86f141
>> af91ab2d7cd011db47%7C1%7C0%7C636779949096991106&amp;sdata=B147wIbtDPoP
>> YvHzds53CFlU6BBa9UKjoAuCJ8LMWFc%3D&amp;reserved=0
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.01.org%2Fmailman%2Flistinfo%2Fedk2-devel&amp;data=02%7C01%7Csean.brogan%40microsoft.com%7C90c7b5b8e6544710547308d64bfd68ac%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636779949096991106&amp;sdata=B147wIbtDPoPYvHzds53CFlU6BBa9UKjoAuCJ8LMWFc%3D&amp;reserved=0
> 


  parent reply	other threads:[~2018-11-17 19:01 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 [this message]
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=7beff8ac-5b54-02ea-d33d-71cd1acb3830@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