Since git repo creation will occur strictly by trigger, anything in contributions/{modules,themes} that doesn't have a corresponding project already is going to be orphaned. So we need to decide prior to pulling the trigger how we'll handle those projects.

Comments

sdboyer’s picture

sdboyer commented

Forgot to mention translations.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Issue tags: +git low hanging fruit

Tagging. This might be a good task for a volunteer to do.

dmitrig01’s picture

dmitrig01 commented

Create an 'unofficial project' page for them with just a title?

sirkitree’s picture

sirkitree commented

So mainly when I wonder how to solve a problem like this I'd actually try to think of how a typical repository browser would handle it. I assume this is different; that we are talking about creating an actual project node for each project automatically? Does the repository browser then link to this? If one is not created could that potentially just be a link to create a project page manually?

dww’s picture

dww
we/he/they
commented

I vote to ignore them. If there's no project node, it's not relevant. The history will still be in CVS if someone wants to get it. I'm assuming we're going to need to have a way to do targeted imports after the One Big Conversion(tm), anyway, so if someone really wants to, they can file an infra issue requesting that their orphaned code gets Git-ified. I'd vastly prefer ignore and handle special cases later (if at all) than bulk creating project nodes for things that are basically abandoned code to begin with.

sdboyer’s picture

sdboyer commented
Title: Determine a course of action for CVS items without corresponding projects » Blow away CVS items (post-migration-scripts) without corresponding projects
Project: Drupal.org infrastructure » The Great Git Migration
Component: Git » Migration scripts
Priority: Normal » Critical

I tend to agree, too. As does webchick. To keep the migration scripts clean, that'll probably mean adding a step in that hudson job which blows away projects after the whole build has taken place if they don't have corresponding entries in the db.

So, since we're decided on that, retitling & marking critical so that this issue can be the place we track actually DOING this.

eliza411’s picture

eliza411 commented
Issue tags: +git sprint 9

Tagging for Git Sprint 9

sdboyer’s picture

sdboyer commented
Issue tags: +tggm db-repo mirroring

one of the mirroring issues

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Assigned: Unassigned » neclimdul

Neclimdul told me I could assign this to him.

neclimdul’s picture

neclimdul
He/Him
commented

This is something I should be able to take a look at.

sdboyer’s picture

sdboyer commented
Status: Active » Postponed
Issue tags: -git sprint 9 +git sprint 10

Postponed till I get to all the mirroring issues next week.

andypost’s picture

andypost
he/him
Primary language Russian
commented

D6 branch has 1 minor bug #1176524: Remove CVS $Id$ tags from core