python3-qutip: Roadmap and officially discussion

[Dirk Lehmann <debian@dj-l.de>]

Dear Debian Science Maintainers,

I am beginning a Thread here in this mailing list related to
Bug#1098454

  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098454

as I suppose it needs a more longer discussion or (depending on
activity) public status information.

I have read the 'Debian Python Policy' and I am familiar with the
'Debian Developers Reference' in the past.  Currently I am reading the
'Debian Maintainers Guide' and try to become a Debian Maintainer to
solve the Bug#1098454 above itself.

**********************************************************************
* Faster solution

If someone needs it more faster to become solved then let us make a
parallel 'packaging race' xD ...  Otherwise as workaround it is very
easy to check-out the not packaged sources via Git, i.e.

  $> git clone https://github.com/qutip/qutip-qip

then `cd` into it and run in a shell

  qutip-qip$> python3 setup.py build

then `cd` into your project-sources and soft-link the build into it

  project/src$> ln -s ../../qutip-qip/build/lib/qutip_qip

Thats all.  It exist inter-Qutip dependencies, keep track of it.

**********************************************************************
* My changed email

First if all

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

To become a Debian Maintainer I changed my email.  My old email was
<support@dj-l.de> and currently I am working officially with
<debian@dj-l.de>, as soon as for commits <develop@dj-l.de>.
-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEEkEvHOgtY/R9ByrOo4qN2byHwK9UFAmfHNn4PHGRlYmlhbkBk
ai1sLmRlAAoJEOKjdm8h8CvV3VoQAJQ3IYigI1VED89mhQ1cR3P68fAe4Ny4jdOy
X+NR0vS1U35FMcwXWpgb0cggLURUAV602gMcxXgYRj7zgCTXQcajE9dp4qpvg+v7
RT/sRpAsEzF2jmTtGCwhQYLGZsDL0baBFHeHzV5zy9L+j60y/izufilDs8Y8cTnG
sZmx4LrycRRSWl+g9wbxDr/eN/8Niw/CIjVWOoqnXD6imIX9Af2HaqfzdzFXM0mu
BbInwSNaMPZOUm+M7aiT+muV6D1qU3OLytY6f6ji4QL5SU2LaOtnPUmVHYJk2nkB
zP2D6wMlr4MbN+cCZyK18AWC0Ys/BI/kwR4MFV4D6LeoeifMxiaX5R5L5JDC5hGC
qbmy/pV99cUcIi3peQaqV04lJ5/0KGLLPShkRDQAdaNJwipgzTiC3EVkGt8b87lO
ZQSVoloUzxPo/vSvmme8U+GWK89k3c+5aMTeAdN5k3gtlfG4D93d/T2zsBD1O04O
JhfcTJIHF+7FCHXE2QRFjLUf04s64OU8/gtCCIqdDmhCYZXXxeQYAb58lU9ih0oC
KAjfDEJGZwrX2h8kVhWRl2FWgCmsEZCuqoMBlrdLpd40K6Nvw1jfWVhS3qbuM3B3
Wv3+jO5m3og5X28bnjHmSf3JStRTsYckcmnVtmdbRgWY+FLroD4xJWmEHmSbSiBl
fkx3oAfX
=Usgs
-----END PGP SIGNATURE-----

GPG: 0x904BC73A0B58FD1F41CAB3A8E2A3766F21F02BD5
     @ keyserver.ubuntu.com

**********************************************************************
* Roadmap

My current plan is the following, I try to process as fast as
possible for (my) free(-time).

1. Reading the 'Debian Maintainers Guide' a bit more, until I feel
   certain enough for maintaining.

2. In parallel I try to become the 'Debian Maintainer' status in the
   NM process (key signing and so on).

3. The Python library QuTiP (python3-qutip) was split via a kind of
   plugin-system into many splited projects with it's own
   Git-repositories by the developers.

   My plan is to map these plugins to Debian packages.  Maybe
   `python3-qutip-<plugin>` in compliance with the Debian Python
   Policy.

   The current packaged `python3-qutip` (version 5.1.1-1) just
   contains the `core`.  The reason is that the developers have
   "out-sourced" the plugins into fresh repositories.  Therefore, I
   plan to make `python3-qutip` to a pure meta-package, which just
   contain dependencies (see end of this roadmap).

   I don't like to overspecify which QuTiP plugins are needed to be
   packaged for now.  I begin with `python3-qutip-core` and will see
   which are required on-the-fly.

4. I will setup public Git repositories on my Salsa account at

     * https://salsa.debian.org/users/dj-l/projects

   and implement the packaging of the QuTiP packages, beginning with
   `python3-qutip-core`.

5. Now it's time to have access as an Uploader and hopefully have
   finished the NM process.  To test the packages productive in
   Debian Unstable.

   Maybe that I'm wrong at this point, you are welcome for
   false-feedback.

6. Wait until the packages are in Debian Testing and maybe for Bug
   reports.

7. Remove all file contents from package `python3-qutip` and just set
   dependencies, i.e. `python3-qutip-core`, `python3-qutip-qip`, ...,
   to keep `python3-qutip` compatible to earlier Debian versions.

   Current uploader: Drew Parsons <dparsons@debian.org>

I will link this thread to Bug#1098454
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098454>.

Greets, Dirk =)