Feature #6051

Migrate master Git repository to immerda

Added by Tails 2013-07-18 07:49:57 . Updated 2014-11-05 11:13:42 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Discuss
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Once the website is split out into its own Git repository (Feature #5506), we can migrate the master Tails Git repository to immerda.

Subtasks

History

#1 Updated by intrigeri 2013-07-19 07:09:39

  • Type of work changed from Wait to Sysadmin

#2 Updated by intrigeri 2013-12-29 03:21:39

  • Subject changed from migrate master Git repository to immerda to Migrate master Git repository to immerda
  • Category set to Infrastructure
  • Starter set to No

#3 Updated by intrigeri 2014-08-02 16:52:18

  • Type of work changed from Sysadmin to Discuss

I’ve no idea if our initial reasons for doing it are still valid: our current master Git repo is automatically mirrored to immerda, so we can do anything we want (IRC commit notification, whatever) there already. Also, it’s not as if we had to change the list of people (and SSH keys) with write access to the master Git repo that often. Therefore, I’m marking this ticket as needing further discussion, and will close it after a month or three unless good reasons to do this work are provided.

#4 Updated by intrigeri 2014-08-02 16:59:03

#5 Updated by intrigeri 2014-11-03 21:23:30

  • Status changed from Confirmed to Rejected

As per monthly meeting.

#6 Updated by sajolida 2014-11-05 11:13:42

Discussed during the November https://tails.boum.org/contribute/meetings/201411/#index3h1.

The only real advantage of moving our master Git repository to immerda would be to have more control on who has commit permissions. But we do that only on very rare occasions. We couldn’t find any good reason to do this work so we rejected this ticket.