Re: Add packages to the GNOME group to get them updated faster

--0000000000009c97500652e39f4d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you for the reply.

I packaged gaphor which is a GNOME Circle app.

https://salsa.debian.org/gnome-team/gaphor

Of course I sent another email with my primary email address (
[email protected]) to find a sponsor for it.

On Fri, May 22, 2026 at 1:56=E2=80=AFAM Jeremy B=C3=ADcha <[email protected]=
g> wrote:

> On Thu, May 21, 2026 at 3:12=E2=80=AFPM masume dehghan
> <[email protected]> wrote:
> > Can I add my packages to the GNOME group so they get updated faster?
>
> Yes. Welcome! Thank you for helping to make Debian better! I have
> added you to the Salsa team. I think that gives you enough permission
> to move your projects with Settings > General > Transfer project.
>
> GNOME Core and GNOME Circle apps and libraries should be in the
> regular Debian GNOME team, while other apps and libraries for GNOME
> are handled in the Extras subteam.
>
> Please take time to read through https://wiki.debian.org/Gnome/Git .
> In particular, we use a DEP-14 style layout with git-buildpackage.
> That means the default branch is debian/latest and there is also an
> upstream/latest branch.
>
> Converting the upstream branch is a little complicated. Basically it
> requires first renaming upstream to a temporary branch and then
> renaming the temporary branch to upstream/latest since git won't allow
> branches named upstream & upstream/latest to exist simultaneously.
> This also means that it is probably easiest for people who have a
> local copy of these repos to just do a new git clone afterwards. Let
> me know if you want me to rename the branches for you after the repos
> are moved to the Debian GNOME team on Salsa.
>
> We also use the full upstream git history so there will be one extra
> step when importing new upstream versions:  git fetch --all  (or
> sometimes also  git fetch --all --tags  ) assuming you have the
> upstreamvcs git remote. One way to get that remote is with gbp clone
> --add-upstream-vcs when doing the initial git clone.
>
> Thank you,
> Jeremy B=C3=ADcha
>

--0000000000009c97500652e39f4d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thank you for the reply.</div><div><br></div><div>I p=
ackaged gaphor which is a GNOME=C2=A0Circle app.</div><div><br></div><div><=
a href=3D"https://salsa.debian.org/gnome-team/gaphor">https://salsa.debian.=
org/gnome-team/gaphor</a></div><div><br></div><div>Of course I sent another=
 email with my primary=C2=A0email address (<a href=3D"mailto:modaresisoftha=
[email protected]">[email protected]</a>) to find a sponsor for it.</di=
v></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"lt=
r" class=3D"gmail_attr">On Fri, May 22, 2026 at 1:56=E2=80=AFAM Jeremy B=C3=
=ADcha &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Ma=
y 21, 2026 at 3:12=E2=80=AFPM masume dehghan<br>
&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">masumede=
[email protected]</a>&gt; wrote:<br>
&gt; Can I add my packages to the GNOME group so they get updated faster?<b=
r>
<br>
Yes. Welcome! Thank you for helping to make Debian better! I have<br>
added you to the Salsa team. I think that gives you enough permission<br>
to move your projects with Settings &gt; General &gt; Transfer project.<br>
<br>
GNOME Core and GNOME Circle apps and libraries should be in the<br>
regular Debian GNOME team, while other apps and libraries for GNOME<br>
are handled in the Extras subteam.<br>
<br>
Please take time to read through <a href=3D"https://wiki.debian.org/Gnome/G=
it" rel=3D"noreferrer" target=3D"_blank">https://wiki.debian.org/Gnome/Git<=
/a> .<br>
In particular, we use a DEP-14 style layout with git-buildpackage.<br>
That means the default branch is debian/latest and there is also an<br>
upstream/latest branch.<br>
<br>
Converting the upstream branch is a little complicated. Basically it<br>
requires first renaming upstream to a temporary branch and then<br>
renaming the temporary branch to upstream/latest since git won&#39;t allow<=
br>
branches named upstream &amp; upstream/latest to exist simultaneously.<br>
This also means that it is probably easiest for people who have a<br>
local copy of these repos to just do a new git clone afterwards. Let<br>
me know if you want me to rename the branches for you after the repos<br>
are moved to the Debian GNOME team on Salsa.<br>
<br>
We also use the full upstream git history so there will be one extra<br>
step when importing new upstream versions:=C2=A0 git fetch --all=C2=A0 (or<=
br>
sometimes also=C2=A0 git fetch --all --tags=C2=A0 ) assuming you have the<b=
r>
upstreamvcs git remote. One way to get that remote is with gbp clone<br>
--add-upstream-vcs when doing the initial git clone.<br>
<br>
Thank you,<br>
Jeremy B=C3=ADcha<br>
</blockquote></div>

--0000000000009c97500652e39f4d--