Re: joining the science team to package spaCy & gensim

2020-08-27 Thread Paul Wise
On Fri, 2020-08-28 at 02:26 +, Mo Zhou wrote:

> Both NLTK and spaCy suffer from a problem -- they cannot be fully
> functional without pretrained models. And you know this is exactly
> what the ML-Policy is discussing.

Yes, I discovered this while doing the internal packaging. The default
English models I looked at seemed to be quite dubious to me too, both
from a legal perspective and a DFSG/ML-Policy perspective.

> I think you can simply work on the existing repositories. New repos
> can be created under the deep learning team if you like.

I will do that, are there any guidelines for which team to use for
specific packages or should I ask on the list(s) about it?

One other issue I encountered is outdated embedded code copies
(specifically cython-blis has a copy of blis), I'd like to solve that
upstream, do have a GitHub account and would you mind if I CCed you on
any GitHub issues that I file about this?

> Just feel free to go ahead. But you might want to ask Andreas if he has
> any unpushed commits.

OK, hopefully he will see this mail :)

> Debian science team has the maintainer access to Debian Deep Learning
> team by default.

OK, great.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Re: joining the science team to package spaCy & gensim

2020-08-27 Thread Mo Zhou
Hi Paul,

In the past Andreas Tille and I tried to get spaCy into the archive
since it is really useful (in my research projects), and is sometimes
more convenient than NLTK (I'm the uploader).

Both NLTK and spaCy suffer from a problem -- they cannot be fully
functional without pretrained models. And you know this is exactly
what the ML-Policy is discussing.

I think you can simply work on the existing repositories. New repos
can be created under the deep learning team if you like.

On Thu, Aug 27, 2020 at 07:55:09PM +0800, Paul Wise wrote:
> Hi all,
> 
> My employer is interested in having spaCy and gensim in Debian.
> 
> https://spacy.io/
> https://radimrehurek.com/gensim/
> 
> I noticed that there is a spaCy package in the team's repository
> although it is not yet in Debian and gensim is also a natural language
> processing tool so the team seems like the right place for it too.
> 
> https://salsa.debian.org/science-team/spacy
> 
> I have used stdeb to create internal packages of spacy, gensim and
> their missing dependencies. The packages all build, some tests fail and
> the packaging needs cleanup and fixes. I would like to import the
> packages into the team and work on completing them. Some of the
> dependencies are probably more suitable for the general Python team or
> possibly the machine learning team, so I'll import those elsewhere.

Just feel free to go ahead. But you might want to ask Andreas if he has
any unpushed commits.
 
> I've submitted my request to join the salsa project.

Debian science team has the maintainer access to Debian Deep Learning
team by default.
 
> [Please CC me in reply, I'm not subscribed to the list]
> 
> -- 
> bye,
> pabs
> 
> https://wiki.debian.org/PaulWise



Re: Introduction and joining the debian-science/robotics team

2020-08-27 Thread Anton Gladky
Hello Daniele,

welcome to the team!

Feel free to create an account on salsa, request an access to the Science
team and you can safely work on your packages there.

When you are ready or have a question, you can always ask in a team. You
will definitely find someone to communicate. Almost all robotics packages
are successfully maintained in the science team.

Please add your packages on salsa and ask for sponsoring, when you think,
they are ready to be reviewed or/and uploaded.

Best regards

Anton


Daniele E. Domenichelli  schrieb am Mi., 26. Aug.
2020, 17:53:

> Hello everyone,
>
> I'm a technician/developer at Istituto Italiano di Tecnologia (IIT)[1],
> and I'm working mostly on YARP (an open source middleware for
> robotics)[2,3] and in general on the on the software developed in the
> "robotology" GitHub organization[4] and running on the iCub[5] and R1[6]
> robots.
>
> I've been around Debian for a very long time, mostly as a user,
> reporting random bugs and in a few cases helping with a couple of
> packages. I'm also the maintainer of nifti2dicom[7] (which I haven't
> really updated in the last few years, since I'm no longer working in the
> neuroimaging field, but it is still working), and the former maintainer
> of gtkdataboxmm[8] which is no longer in Debian repositories.
>
> I was at the debian-science and debian-med BoFs at DebConf (drdanz),
> since I'm interested in packaging and maintaining a few packages from
> the "robotology" github organization (mostly developed here at IIT), and
> perhaps helping with some other robotics-related packages.
>
> I started working on a few of them but the YARP package turned out to be
> a lot more complicated than what I was expecting (I actually opened the
> original ITP in 2012, and I worked upstream little by little on fixing
> the issues that I found while trying to create the package).
> I now have a few working packages on an Ubuntu PPA[9], but I'm a bit
> stuck because I could not find any sponsor, I have lots of questions,
> and I'm still a bit confused by the Debian workflow.
>
> Therefore I was wondering if there is someone that would be available
> to mentor me through the process.
>
> These are the related bugs that I opened so far:
>
> * #682756: ITP: yarp -- middleware for humanoid robots
> * #934757: ITP: ycm-cmake-modules -- Extra CMake Modules for YARP and
>   friends
> * #966342: RFS: ycm-cmake-modules/0.11.3-1 [ITP] -- Extra CMake Modules
>   for YARP and friends
> * #969037: ITP: robot-testing-framework -- Robot Testing Framework
>
>
>
> I'm also looking for someone that would like to make a talk here at IIT
> (unfortunately online, due to the coronavirus, but we can eventually try
> to organize a visit later, when the pandemic is over), about
> Debian Science, Debian in general, and eventually make a
> small tutorial for beginners about how to start packaging.
> We produce a lot of software and libraries, but unfortunately we tend to
> build everything from sources on all our computers, therefore my goal is
> to persuade the people working here that proper packaging could help a
> lot our workflow.
>
>
> By the way, in case you have never heard about them, iCub is an open
> source (both hardware and software) humanoid robotic platform that we
> produce mostly for research and R1 is a recent effort to produce a "low
> cost" humanoid robot (unfortunately for this robot the hardware is not
> open).
> All the computers onboard and of the cluster connected to the robots run
> either Debian or in same cases ubuntu, with a few exceptions for
> computers running some specific software that runs only on windows,
> and researcher laptops that run whatever operating system the researcher
> chooses.
>
>
> Thanks in advance to anyone who will reply and will help me with the
> packaging.
>
>
> Cheers,
>  Daniele
>
>
> [1]https://www.iit.it/
> [2]http://yarp.it/
> [3]https://github.com/robotology/yarp/
> [4]https://github.com/robotology
> [5]https://icub.iit.it/
> [6]https://icub.iit.it/products/r1-robot
> [7]https://tracker.debian.org/pkg/nifti2dicom
> [8]https://tracker.debian.org/pkg/gtkdataboxmm
> [9]https://launchpad.net/~robotology/+archive/ubuntu/test/+packages
>
>


Bug#969088: ITP: esdm -- Earth System Data Middleware for earth system simulation

2020-08-27 Thread Alastair McKinstry
Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry 

* Package name: esdm
  Version : 0.1.0
  Upstream Author : Julian Kunkel
* URL : https://github.com/ESiWACE/esdm
* License : GPL
  Programming Lang: C
  Description : Earth System Data Middleware for  earth system  simulation

 The middleware for earth system data is a prototype to improve I/O performance
 for earth system simulation as used in climate and weather applications.
 ESDM exploits structural information exposed by workflows, applications as well
 as data description formats such as HDF5 and NetCDF to
 more efficiently organize metadata and data across a variety of storage 
backends.

 It is planned to maintain this within the Debian Science team; it is a growing
 piece of "expected functionality" on systems running climate models.



Re: joining the science team to package spaCy & gensim

2020-08-27 Thread Anton Gladky
Hello Paul!

I have approved your request. Welcome on board! Please contact the team if
you need an assistance or help.

Best regards,

Anton


Paul Wise  schrieb am Do., 27. Aug. 2020, 13:55:

> Hi all,
>
> My employer is interested in having spaCy and gensim in Debian.
>
> https://spacy.io/
> https://radimrehurek.com/gensim/
>
> I noticed that there is a spaCy package in the team's repository
> although it is not yet in Debian and gensim is also a natural language
> processing tool so the team seems like the right place for it too.
>
> https://salsa.debian.org/science-team/spacy
>
> I have used stdeb to create internal packages of spacy, gensim and
> their missing dependencies. The packages all build, some tests fail and
> the packaging needs cleanup and fixes. I would like to import the
> packages into the team and work on completing them. Some of the
> dependencies are probably more suitable for the general Python team or
> possibly the machine learning team, so I'll import those elsewhere.
>
> I've submitted my request to join the salsa project.
>
> [Please CC me in reply, I'm not subscribed to the list]
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>


joining the science team to package spaCy & gensim

2020-08-27 Thread Paul Wise
Hi all,

My employer is interested in having spaCy and gensim in Debian.

https://spacy.io/
https://radimrehurek.com/gensim/

I noticed that there is a spaCy package in the team's repository
although it is not yet in Debian and gensim is also a natural language
processing tool so the team seems like the right place for it too.

https://salsa.debian.org/science-team/spacy

I have used stdeb to create internal packages of spacy, gensim and
their missing dependencies. The packages all build, some tests fail and
the packaging needs cleanup and fixes. I would like to import the
packages into the team and work on completing them. Some of the
dependencies are probably more suitable for the general Python team or
possibly the machine learning team, so I'll import those elsewhere.

I've submitted my request to join the salsa project.

[Please CC me in reply, I'm not subscribed to the list]

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part