salsa-import script

[Filippo Rusconi <lopippo@debian.org>]

Greetings, Fellow Debianites,

I was willing to test the script that Anton kindly posted and that I reproduce
here:

8< ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

$ cat salsa-import
#!/bin/sh

set -eux

PROJECT="${1%.git}"
DESCRIPTION="$PROJECT packaging"
ALIOTH_URL="https://anonscm.debian.org/git";
ALIOTH_GROUP="collab-maint"
SALSA_URL="https://salsa.debian.org/api/v4";
SALSA_NAMESPACE="2" # 2 is "debian"
SALSA_TOKEN="yourcryptictokenhere"

curl -f "$SALSA_URL/projects?private_token=$SALSA_TOKEN" \
 --data "path=$PROJECT&namespace_id=$SALSA_NAMESPACE&description=$DESCRIPTION&import_url=$ALIOTH_URL/$ALIOTH_GROUP/$PROJECT&visibility=public"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>8

I would like to ask some questions:

1. if I wanted to import in salsa a debian-science team-packaged software,
should I put the value "2" as SALSA_NAMESPACE ? I thought I would put the value
corresponding to the science-team?

2. but then, looking at the list of ids for the various teams, debian-science
comes out nowhere. I used the one-liner posted by Anton, also:

curl https://salsa.debian.org/api/v4/groups | jq . | less

When I look at the obtained list I see a number of teams mentioned, like, for
example:

"id": 2359,
   "name": "Debian Edu Packaging Team",

"id": 2035,
   "name": "Debian Emacsen Packaging Team",

So, another question would be: the projects in salsa.d.o/science-team, like
yade, have been imported using the script or not?  In other words, what if I ran
the script and the package would land in "Debian" at large, and not
science-team?

Thank you for your enlightening remarks,

Cheers,
Filippo

--
⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD   
⣾⠁⢰⠒⠀⣿⡁  public crypto key B053 304E 17D6 D419 DD9B 4651 41AB 484D 7694 CF42 @ pgp.mit.edu 
⢿⡄⠘⠷⠚⠋
⠈⠳⣄⠀⠀⠀⠀