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-boun...@lists.01.org] > On Behalf Of stephano > Sent: Friday, November 16, 2018 11:14 AM > To: Zimmer, Vincent <vincent.zim...@intel.com>; edk2- > de...@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- > boun...@lists.01.org] On Behalf Of Kevin D Davis > > Sent: Friday, November 16, 2018 9:35 AM > > To: stephano <stephano.cet...@linux.intel.com>; edk2- > de...@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.cet...@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
