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

Hi,

On Wed, 2024-02-14 at 16:59 +0000, Chris Laplante via
lists.openembedded.org wrote:
> This bug (“A web based playground for experimenting with bitbake variable 
> expansion”) has been preying on my mind ever since I read it on 
> Bugzilla:https://bugzilla.yoctoproject.org/show_bug.cgi?id=14805.


This does sound quite neat and I'm happy to see people experimenting
like this.

[...]

> As far as next steps, I was thinking I would build a simple-ish web app using 
> https://github.com/microsoft/monaco-editor (the editor that powers VS Code). 
> This would let us implement a Rust Playground-type of experience.
>  
> The two main questions in my mind are where to keep the code and where to host it?
>  
> For the code, I lean towards a separate repository. I was just going to put it 
> under my company’s GitHub:https://github.com/Agilent. This is what I’ll do unless
> people feel strongly otherwise. (I’d rather not put it in BitBake itself since due 
> to CORS restrictions I’ll probably need to keep tar.gz copies of BitBake in the 
> repo so the client can fetch it (*3). I also don’t think we want all the webpack 
> and TypeScript clutter in BitBake)

I agree it doesn't belong in bitbake itself. I did wonder about
something like the yoctoproject github if you wanted more exposure
there but I don't have a strong preference either way. 

> For hosting, assuming it goes on our GitHub, I was just going to use GitHub pages.
>  The first iteration will be a client-side only application (*4)(*5), so no server 
> will be required except a static endpoint for serving BitBake source code as mentioned above.
>  
> Does anyone have strong objections to this plan?

No objection, I mainly wanted to reply to show someone read it and
thought it sounds fun :)

Cheers,

Richard



  reply	other threads:[~2024-02-15 15:20 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 ` Richard Purdie [this message]
2024-02-15 15:29   ` [bitbake-devel] " chris.laplante
2024-02-15 17:23     ` Richard Purdie
2024-02-15 17:25       ` chris.laplante
2024-02-15 17:28         ` Richard Purdie
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=4ab357d878fad09b44149179e532608a1c329e81.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=behanw@converseincode.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=chris.laplante@agilent.com \
    /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.