[edk2-announce][RFC] Collaboration Software

[edk2-announce][RFC] Collaboration Software

[stephano]

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

Re: [edk2-announce][RFC] Collaboration Software

[Kevin D Davis]

  
  
    
    	
    	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://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2-announce][RFC] Collaboration Software

[Zimmer, Vincent]

https://slack.com/

-----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://lists.01.org/mailman/listinfo/edk2-devel





_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

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://slack.com/
> 
> -----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://lists.01.org/mailman/listinfo/edk2-devel
> 
> 
> 
> 
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> 

Re: [edk2-announce][RFC] Collaboration Software

[Kinney, Michael D]

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://blog.github.com/2017-11-20-introducing-team-discussions/

https://help.github.com/articles/about-team-discussions/

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://slack.com/
> >
> > -----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://lists.01.org/mailman/listinfo/edk2-devel
> >
> >
> >
> >
> >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> >
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

This looks great.

I'm going to dig in a bit and see if we can export discussions for 
logging purposes or if they are locked into Github.

git clone git://tianocore.discussion ? :)

On 11/16/2018 11:55 AM, Kinney, Michael D wrote:
> 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://blog.github.com/2017-11-20-introducing-team-discussions/
> 
> https://help.github.com/articles/about-team-discussions/
> 
> 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://slack.com/
>>>
>>> -----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://lists.01.org/mailman/listinfo/edk2-devel
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel
>>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2-announce][RFC] Collaboration Software

[Philippe Mathieu-Daudé]

On 16/11/18 21:46, stephano wrote:
> This looks great.
> 
> I'm going to dig in a bit and see if we can export discussions for 
> logging purposes or if they are locked into Github.

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?

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.

Regards,

Phil.

> 
> git clone git://tianocore.discussion ? :)
> 
> On 11/16/2018 11:55 AM, Kinney, Michael D wrote:
>> 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://blog.github.com/2017-11-20-introducing-team-discussions/
>>
>> https://help.github.com/articles/about-team-discussions/
>>
>> 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://slack.com/
>>>>
>>>> -----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://lists.01.org/mailman/listinfo/edk2-devel
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> edk2-devel mailing list
>>>> edk2-devel@lists.01.org
>>>> https://lists.01.org/mailman/listinfo/edk2-devel
>>>>
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

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?

Re: [edk2-announce][RFC] Collaboration Software

[Rebecca Cran]

On Friday, 16 November 2018 17:34:09 MST stephano wrote:

> 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?

Yes, it can do. From what I posted earlier:

"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."

-- 
Rebecca

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

On 11/16/2018 4:37 PM, Rebecca Cran wrote:
> On Friday, 16 November 2018 17:34:09 MST stephano wrote:
> 
>> 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?
> 
> Yes, it can do. From what I posted earlier:
> 
> "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."
> 

Perfect, thanks!

Re: [edk2-announce][RFC] Collaboration Software

[Tomas Pilar (tpilar)]

All of these reasons (along with scalability) is why the linux kernel development hasn't moved from email mailing lists and they have tried several times.

Cheers,
Tom

On 16/11/2018 22:14, Philippe Mathieu-Daudé wrote:
> On 16/11/18 21:46, stephano wrote:
>> This looks great.
>>
>> I'm going to dig in a bit and see if we can export discussions for logging purposes or if they are locked into Github.
>
> 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?
>
> 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.
>
> Regards,
>
> Phil.
>
>>
>> git clone git://tianocore.discussion ? :)
>>
>> On 11/16/2018 11:55 AM, Kinney, Michael D wrote:
>>> 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://blog.github.com/2017-11-20-introducing-team-discussions/
>>>
>>> https://help.github.com/articles/about-team-discussions/
>>>
>>> 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://slack.com/
>>>>>
>>>>> -----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://lists.01.org/mailman/listinfo/edk2-devel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> edk2-devel mailing list
>>>>> edk2-devel@lists.01.org
>>>>> https://lists.01.org/mailman/listinfo/edk2-devel
>>>>>
>>>> _______________________________________________
>>>> edk2-devel mailing list
>>>> edk2-devel@lists.01.org
>>>> https://lists.01.org/mailman/listinfo/edk2-devel
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2-announce][RFC] Collaboration Software

[Sean Brogan]

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

Re: [edk2-announce][RFC] Collaboration Software

[Rebecca Cran]

On November 16, 2018 at 7:42:51 PM, Sean Brogan via edk2-devel (edk2-devel@lists.01.org(mailto:edk2-devel@lists.01.org)) wrote:

> 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).  
>  






At least with Phabricator you don’t have to pay to self-host it. And look at all the features you don’t get with Github unless you pay them:


https://github.com/pricing






Rebecca

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

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
> 

Re: [edk2-announce][RFC] Collaboration Software

[Rudra ठाकुर]

Hi,
  Discord is way better than slack and it is free.
https://discordapp.com/

It has both web and app interface.

Thanks,
--Rc


On Sat, Nov 17, 2018 at 1:09 PM stephano <stephano.cetola@linux.intel.com>
wrote:

> 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
> >
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>

Re: [edk2-announce][RFC] Collaboration Software

[Rebecca Cran]

On Friday, 16 November 2018 19:42:51 MST Sean Brogan via edk2-devel 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 do wonder why there aren't more _big_ open source projects using Github if 
it _is_ there, free and easy to use. I'm aware lots and lots use it for 
hosting their repositories, but I'm not aware of many that use it for code 
reviews, discussions etc.

I found that CoreBoot uses Gerrit: https://review.coreboot.org/q/status:open

GNOME evaluated Phabricator and GitLab (but not GitHub, because "GitHub is not 
Free Software, of couse, which makes it unacceptable to many in the GNOME 
community") - https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure .
They decided to go with GitLab:
https://mail.gnome.org/archives/desktop-devel-list/2017-May/msg00051.html

One comment from a user on the GNOME evaluation (https://wiki.gnome.org/
Initiatives/DevelopmentInfrastructure/Comments) said:

"We tried migrating libnice to phabricator.freedesktop.org and it was a bit of 
a disaster as the "drive-by" contribution process is horrible with 
Phabricator, requiring to either download a tool or copy-paste patches into a 
webpage. Upstream Phabricator is also very hostile to the github style of 
reviews (where you can review small patches, not everything squashed into one 
SVN style). Even Bugzilla with Splinter is nicer for new contributors.. So 
let's go with GitLab. That said, all of Collabora's Phabricator tools are 
already public. ? OlivieCrete"

-- 
Rebecca

Re: [edk2-announce][RFC] Collaboration Software

[Rebecca Cran]

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

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

On 11/16/2018 12:52 PM, Rebecca Cran wrote:
> 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.

I have found the same situation in other open source communities. We 
want to be sure that our conversations are not lost, so I'm not sure if 
Slack is a viable option.

We certainly open to this idea though, if others have found solutions to 
this issue.

> 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."

This is a great suggestion, thanks! Two questions:

1. Does it allow you to export your conversations in some way?
2. Is there a "file sharing" option if we wanted to, for example, share 
a JPG or ODF file?

Re: [edk2-announce][RFC] Collaboration Software

[Rebecca Cran]

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

Re: [edk2-announce][RFC] Collaboration Software

[stephano]

On 11/16/2018 1:51 PM, Rebecca Cran wrote> 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":

Perfect. As long as we have a way to store history of conversations I 
think we are keeping the best part of the current system.

> 
>> 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.
> 

Also great. I assumed this but thank you for confirming.

Cheers,
Stephano