On Mon, Oct 31, 2016 at 08:50:53AM -0500, Alex Elder wrote:
> I'm proposing below a few things, which I'll implement this week
> unless I hear people express strong opposition (or clearly better
> suggestions). If you have comments, please say something.
>
> Git repositories. Public git repositories related to Project Ara
> are all hosted here:
> https://github.com/projectara
All but the greybus kernel code, yes.
> Mailing List. Because the Greybus kernel code sits in the staging
> tree, mail about it should go to the driver-devel mailing list
> (de...@driverdev.osuosl.org). I know that some people prefer better
> mail filters rather than more mailing lists, but I think Greybus
> discussion warrants a separate list. Its code spans multiple code
> bases, and I think we're going to need some dedicated and ongoing
> strategy and design discussions. So I'd like to create a Greybus
> mailing list as a home for all Greybus-related discussion, including
> patch traffic. My suggestion is to create a majordomo list:
> grey...@kernel.org
That would be
grey...@vger.kernel.org
> Patchwork. In the past I have found Patchwork to be a very useful
> tool in managing incoming patches. I'd like to set up a patchwork
> instance for Greybus, monitoring the greybus mailing list, again
> at kernel.org.
Not sure this is needed from the outset. Let's see where the discussions
lead first. I'm sure we'll manage to keep track of what's posted until
then.
Johan
_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
