All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "chris.laplante@agilent.com" <chris.laplante@agilent.com>,
	 "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Cc: "behanw@converseincode.com" <behanw@converseincode.com>,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [bitbake-devel] Online tool for playing with variable expansion - first steps and where to host it
Date: Thu, 15 Feb 2024 17:28:55 +0000	[thread overview]
Message-ID: <65cfd68e97fa5cf84b759a1502b78e92e4d44dbf.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM8PR12MB5430C2D2BAC610486096C7F48B4D2@DM8PR12MB5430.namprd12.prod.outlook.com>

On Thu, 2024-02-15 at 17:25 +0000, chris.laplante@agilent.com wrote:
> > > I also don't have a strong preference. I envision eventually I'll add
> > > little "Run" links in the BitBake manual next to code samples,
> > > especially in the chapter on variable overrides, which will take the
> > > reader directly to the playground. So I think no matter where we host it,
> > people will eventually find it.
> > 
> > That does potentially change things a little as if we want to make links from the
> > official project docs, putting it somewhere with our other project repos does
> > start to make sightly more sense.
> > 
> > I say that as people do move on and do other things and we'd have no way to
> > recover other than changing the links in that case, which we can only do with
> > the newer versions, not retrospectively.
> 
> Works for me. Who do I talk to about getting a repo set up on Yocto's GitHub 
> (or wherever)?

We ask Michael Halstead (copied) who will need your github username and
the name of the repo we want to create.

I'm supposed to agree this with the YP TSC too I think so I'll forward
this to them and check they don't object.

Cheers,

Richard


  reply	other threads:[~2024-02-15 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 16:59 Online tool for playing with variable expansion - first steps and where to host it chris.laplante
2024-02-15 15:20 ` [bitbake-devel] " Richard Purdie
2024-02-15 15:29   ` chris.laplante
2024-02-15 17:23     ` Richard Purdie
2024-02-15 17:25       ` chris.laplante
2024-02-15 17:28         ` Richard Purdie [this message]
2024-02-16 13:46           ` chris.laplante
2024-05-13 14:55 ` BB Datastore Playground preview is now live chris.laplante
2024-05-13 16:06   ` Michael Halstead
2024-05-13 16:19     ` chris.laplante

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=65cfd68e97fa5cf84b759a1502b78e92e4d44dbf.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=behanw@converseincode.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=chris.laplante@agilent.com \
    --cc=mhalstead@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.