All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Dmitry Kargin <dmitry.n.kargin@gmail.com>,
	Chandana Kalluri <ckalluri@xilinx.com>,
	Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>
Cc: yocto@yoctoproject.org,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Xilinx/meta-jupyter layer
Date: Tue, 01 Oct 2019 11:36:42 +1300	[thread overview]
Message-ID: <2678038.QAzkJJSIsR@linux.fritz.box> (raw)
In-Reply-To: <CAFCaPfyh14v2HPZ8vNDoeVM18XtAiK9zOCJT3_1Wrh5BHOpH-w@mail.gmail.com>

FYI I've just changed the layer index entry to point to the new repo. New 
content should be indexed in a few hours.

Thanks for working this out!

Dmitry: sorry, for clarity did you mean a separate mailing list or one of the 
YP / OE ones ?

Cheers,
Paul

On Saturday, 28 September 2019 9:52:26 AM NZDT Dmitry Kargin wrote:
> Nice job!
> 
> You have my permission, if it is needed to change
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/
> links to your repository.
> 
> >Would you recommend maintaining this layer separately or...
> I'd like to keep it separately from meta- and openembedded.
> 
> >Would you suggest having a separate mailing list
> meta-jupyter mailing list is fine.
> 
> On Fri, 27 Sep 2019 at 23:12, Chandana Kalluri <ckalluri@xilinx.com> wrote:
> 
> > Hello all,
> >
> > https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing
> > recipes for jupyter notebook. The initial recipes are based of Dmitry
> > Kargin's meta-jupyter layer
> > https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/.
> > This layer has not been updated for a while.
> >
> > The Xilinx/meta-jupyter layer also adds recipes for python3 based
> > notebooks apart from existing python2 based notebooks.
> > This layer has been tested using Yocto thud layer and  by running jupyter
> > notebooks on Ultra96 community boards.
> > We would like to maintain Xilinx/meta-jupyter  layer actively and welcome
> > contributions to this layer either through pull requests or via patches
> > sent to meta-xilinx mailing list until a mailing list for meta-jupyter is
> > in place. In the next cycle we will deprecate python2 recipes.
> >
> > A question to community,
> >  - Would you recommend maintaining this layer separately in the current
> > github.com/Xilinx location or be included under meta- openembedded layers.
> > - Would you suggest having a separate mailing list ?
> >
> > Thanks,
> > Chandana
> >
> >
> 


-- 

Paul Eggleton
Intel Open Source Technology Centre




WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Dmitry Kargin <dmitry.n.kargin@gmail.com>,
	Chandana Kalluri <ckalluri@xilinx.com>,
	Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>
Cc: yocto@yoctoproject.org,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Xilinx/meta-jupyter layer
Date: Tue, 01 Oct 2019 11:36:42 +1300	[thread overview]
Message-ID: <2678038.QAzkJJSIsR@linux.fritz.box> (raw)
In-Reply-To: <CAFCaPfyh14v2HPZ8vNDoeVM18XtAiK9zOCJT3_1Wrh5BHOpH-w@mail.gmail.com>

FYI I've just changed the layer index entry to point to the new repo. New 
content should be indexed in a few hours.

Thanks for working this out!

Dmitry: sorry, for clarity did you mean a separate mailing list or one of the 
YP / OE ones ?

Cheers,
Paul

On Saturday, 28 September 2019 9:52:26 AM NZDT Dmitry Kargin wrote:
> Nice job!
> 
> You have my permission, if it is needed to change
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/
> links to your repository.
> 
> >Would you recommend maintaining this layer separately or...
> I'd like to keep it separately from meta- and openembedded.
> 
> >Would you suggest having a separate mailing list
> meta-jupyter mailing list is fine.
> 
> On Fri, 27 Sep 2019 at 23:12, Chandana Kalluri <ckalluri@xilinx.com> wrote:
> 
> > Hello all,
> >
> > https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing
> > recipes for jupyter notebook. The initial recipes are based of Dmitry
> > Kargin's meta-jupyter layer
> > https://layers.openembedded.org/layerindex/branch/master/layer/meta-jupyter/.
> > This layer has not been updated for a while.
> >
> > The Xilinx/meta-jupyter layer also adds recipes for python3 based
> > notebooks apart from existing python2 based notebooks.
> > This layer has been tested using Yocto thud layer and  by running jupyter
> > notebooks on Ultra96 community boards.
> > We would like to maintain Xilinx/meta-jupyter  layer actively and welcome
> > contributions to this layer either through pull requests or via patches
> > sent to meta-xilinx mailing list until a mailing list for meta-jupyter is
> > in place. In the next cycle we will deprecate python2 recipes.
> >
> > A question to community,
> >  - Would you recommend maintaining this layer separately in the current
> > github.com/Xilinx location or be included under meta- openembedded layers.
> > - Would you suggest having a separate mailing list ?
> >
> > Thanks,
> > Chandana
> >
> >
> 


-- 

Paul Eggleton
Intel Open Source Technology Centre




  reply	other threads:[~2019-09-30 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 20:12 Xilinx/meta-jupyter layer Chandana Kalluri
2019-09-27 20:12 ` Chandana Kalluri
2019-09-27 21:52 ` Dmitry Kargin
2019-09-30 22:36   ` Paul Eggleton [this message]
2019-09-30 22:36     ` Paul Eggleton
2019-09-28 22:00 ` Randy MacLeod
2019-09-28 22:00   ` [OE-core] " Randy MacLeod
2019-09-30 14:39 ` [yocto] " Mark Hatle
2019-09-30 14:39   ` Mark Hatle

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=2678038.QAzkJJSIsR@linux.fritz.box \
    --to=paul.eggleton@linux.intel.com \
    --cc=MANJUKUM@xilinx.com \
    --cc=ckalluri@xilinx.com \
    --cc=dmitry.n.kargin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 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.