Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: akuster <akuster808@gmail.com>
Cc: Philip Balister <philip@balister.org>,
	Adrian Bunk <bunk@stusta.de>,
	Stephen Jolley <sjolley.yp.pm@gmail.com>,
	yocto@yoctoproject.org
Subject: Re: [yocto] Yocto Project Status WW04'20
Date: Mon, 3 Feb 2020 16:05:29 -0500	[thread overview]
Message-ID: <20200203210529.GS4735@denix.org> (raw)
In-Reply-To: <5b2ce739-c2f3-acad-24c2-797a4b63e6c4@gmail.com>

On Mon, Feb 03, 2020 at 08:16:47AM -0800, akuster wrote:
> 
> 
> On 2/2/20 10:18 AM, Philip Balister wrote:
> > On 2/2/20 2:28 PM, Adrian Bunk wrote:
> >> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
> >>> ...
> >>> *	We have created a "documentation" list and a "licensing" list on the
> >>> yocto project mailing list infrastructure. We believe these topics would
> >>> benefit from dedicated discussions, the people involved usually aren't
> >>> interested in bulk email as would be found on other lists. The new lists can
> >>> be found at:  <https://lists.yoctoproject.org/g/licensing/join>
> >>> https://lists.yoctoproject.org/g/licensing/join and
> >>> <https://lists.yoctoproject.org/g/docs/join>
> >>> https://lists.yoctoproject.org/g/docs/join 
> >>> ...
> >> Would it be possible to also create a yocto-devel or yocto-core
> >> mailing list for discussing development of Yocto?
> >>
> >> Currently the yocto list is a mixture of core development list and forum 
> >> for newbie user questions, with no easy way to have them separate.
> > We have openembedded-architecture for this.
> >
> > http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
> 
> Also openembedded-core

Also openembedded-devel

> > Philip
> >
> >> Thanks
> >> Adrian
> >>
> >>
> >>
> >>
> >>
> >> 
> 

> 


  reply	other threads:[~2020-02-03 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 16:01 Yocto Project Status WW04'20 Stephen Jolley
2020-02-02 13:28 ` [yocto] " Adrian Bunk
2020-02-02 14:09   ` Alexander Kanavin
2020-02-02 18:48     ` Chuck Wolber
2020-02-02 19:36     ` Josef Holzmayr
2020-02-02 15:16   ` Ross Burton
2020-02-02 18:10     ` Adrian Bunk
2020-02-02 18:18   ` Philip Balister
2020-02-03 16:16     ` akuster
2020-02-03 21:05       ` Denys Dmytriyenko [this message]
2021-03-16 14:05     ` DUDZIAK Krzysztof

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-all 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=20200203210529.GS4735@denix.org \
    --to=denis@denix.org \
    --cc=akuster808@gmail.com \
    --cc=bunk@stusta.de \
    --cc=philip@balister.org \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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