Tails

#2 Updated by nodens 2017-11-18 22:30:09

I’m fine with gitlab.com, however it’d be worth it to see if salsa.debian.org ends up having tickets enabled, since the upstream web page is supposed to migrate from alioth to there.

Or, I propose we migrate everything on gitlab.com, including the homepage - but there is still the issue of the mailing list.

#3 Updated by nodens 2017-11-18 22:34:59

So apparently the issue tracker is enabled.
I created https://salsa.debian.org/openpgp-applet/openpgp-applet to test a bit. Beware, the data will probably be reset at least once before salsa enter the “beta” stage.

In any case, we’ll want to recreate issues on gitlab, and refer to them here (leaving a link to the new issue).

#4 Updated by intrigeri 2017-11-19 07:39:29

> So apparently the issue tracker is enabled.
> I created https://salsa.debian.org/openpgp-applet/openpgp-applet to test a bit. Beware, the data will probably be reset at least once before salsa enter the “beta” stage.

OK, then let’s wait a bit for salsa.d.o to enter production state.
Is there any ETA?

#5 Updated by intrigeri 2017-11-19 07:45:16

Also, what will be the steps for a pass-by contributor to create an account and fork a repo in order to submit a MR?

#6 Updated by nodens 2017-11-19 11:28:54

> OK, then let’s wait a bit for salsa.d.o to enter production state.
> Is there any ETA?

Last time I talked about it with formorer, it was supposed to be before the end of 2017 (actually, it should have happened already actually).
I think the self-registration page for guest account isn’t quite ready, hence the delay.

> Also, what will be the steps for a pass-by contributor to create an account and fork a repo in order to submit a MR?

There will be a self-registration page to create guest (i.e. non debian) account. Mine was created manually but that’s not the definitive process of course :)

Once you have an account, you have your own namespace to create projects, and you can even create groups (that’s how I created the test project linked above, I also gave you access using your debian account).

So the steps would be:

• register if needed
• fork

that’s pretty much it. Of course forking elsewhere (gitlab.com, github…) is possible as well, but less straightforward.

#7 Updated by intrigeri 2017-11-19 12:09:23

> So the steps would be:
> * register if needed
> * fork

Perfect, as long as the registration is smooth (e.g. does not require to wait for a human to accept it).

#8 Updated by Anonymous 2017-12-04 18:58:16

We should define a better workflow - might be cheaper than moving around the repository.
I volunteered to explain to nodens how we do it with other Tails specific packages.

#9 Updated by intrigeri 2017-12-05 09:00:03

> I volunteered to explain to nodens how we do it with other Tails specific packages.

Note one important difference:

• These other Tails specific packages are always updated in Tails first (via our custom APT repo), so the workflow we generally use on Redmine works just fine: ticket “upstream” status == ticket status in Tails.
• We install OpenPGP Applet from Debian, so wrt. bug/feature tracking it is more like any other package that we install from Debian, regardless of the fact we happen to be upstream for this one; this is the mismatch that makes it hard to track OpenPGP Applet status here (e.g. does “Fix committed” mean “there’s a fix in upstream Git” or “the fix has been applied in current Tails devel branch somehow”?), which prompted me to create this ticket in the first place (see Bug #6398 whose current status is correct from an upstream PoV, but wrong from a Tails PoV, because we’re trying to track both with a single metadata field, which of course is problematic).

This is why I doubt the solutions that work for other Tails specific packages would work for OpenPGP Applet. I’d be happy to be proven wrong though :)