[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Request to join the Debian Science Team on Salsa

Hello Debian Science Team,

in relation to the current thread

  * https://lists.debian.org/debian-science/2025/03/msg00002.html

of this mailing list, I would like to

  * join the Debian Science Team on Salsa

to provide the `python-qutip-*` source repositories in your teams
namespace.  Currently I'm developing under my users namespace at

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

The packages are currently not yet ITP'd.  Also, in parallel I'm in a
NM (New Member) process, which is currently not yet finished.

I have read 'Debian Science Policy Manual' and have technically
requested to join the team on salsa.debian.org .

Thanks and greets,
Dirk =)


On 3/4/25 7:19 PM, Dirk Lehmann wrote:

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

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>.

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 =)

Attachment: OpenPGP_0xE2A3766F21F02BD5.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply to: