Xilinx/meta-jupyter layer

Xilinx/meta-jupyter layer

[Chandana Kalluri]

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

Re: Xilinx/meta-jupyter layer

[Randy MacLeod]

On 9/27/19 4:12 PM, Chandana Kalluri 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.
I suppose a seperate layer since jupyter isn't typically used
but I don't have a strong opinion either way.

> - Would you suggest having a separate mailing list ?

Using the Yocto email list would be my preference.
That way, I'd keep on eye on Jupyter from time to time
whereas if it's a separate list, I likely would not subscribe.
I'm assuming that there will be less than few 100 emails per year.

../Randy


> 
> Thanks,
> Chandana
> 


-- 
# Randy MacLeod
# Wind River Linux

Re: [yocto] Xilinx/meta-jupyter layer

[Mark Hatle]

On 9/27/19 3:12 PM, Chandana Kalluri 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 ?

I'd suggest that you should consider either keeping it on github, or offering it
to the git.yoctoproject.org.  I can assist with this if you need.

Since this is pretty targeted to a specific use-case, either would make sense to me.

--Mark

> Thanks,
> Chandana
> 

Re: [yocto] Xilinx/meta-jupyter layer

[Paul Eggleton]

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