use .gitkeep instead of .gitignore as empty dir placeholder

RESOLVED FIXED in 1.3

Status

RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: groovecoder, Assigned: groovecoder)

Tracking

unspecified
Other
Mac OS X

Details

(Whiteboard: c=infrastructure u=it p=1)

(Assignee)

Description

7 years ago
From MDN:
./django/developer.mozilla.org.old/mdn/vendor/src/django-mozilla-product-details/product_details/json
./django/developer.mozilla.org.old/mdn.backup/vendor/src/django-mozilla-product-details/product_details/json
./django/developer.mozilla.org/kuma/lib/product_details_json
./django/developer.mozilla.org/kuma/vendor/src/django-mozilla-product-details/product_details/json
./dekiwiki/ControlPanel
./dekiwiki/bin/cache/luceneindex/devmo.dekiwiki.mozilla.org
./devedge/viewsource/2002/xslt
./devedge/library/manuals/2002/ncadm/70pr1/relnotes
(Assignee)

Updated

7 years ago
Assignee: nobody → lcrouch
(Assignee)

Comment 1

7 years ago
Jake,

Can you check - I think we can throw away developer.mozilla.org.old now. I updated our vendor/src/django-mozilla-product-details, and I assume kuma/lib/product_details_json is a sym-link?

I think the dekiwiki repos is under IT control?

Finally, devedge is defunct I believe. Jay - can you confirm? If so, let's throw it a going-away party and delete it.

Comment 2

7 years ago
Not sure about devedge.  I've cc'd Sheppy and Janet in case they can authorize the removal of that section.

FWIW: I know devnews is still needed for the project team updates... but we should find a home for that somewhere in the future.
(Assignee)

Updated

7 years ago
Target Milestone: 1.2 → 1.3
(Assignee)

Comment 3

7 years ago
Jake,

What do you see about developer.mozilla.org.old? I think we kept it as a backup of an old copy of MDN before we the whole mdn->kuma merge. We can probably trash it now.

Also, I think the dekiwiki repos is in IT land? If so, IT will have to change the .gitignore files to .gitkeep.

Janet and/or Sheppy,

Do you know anything about devedge? Can we retire it?
I think you can delete devedge -- but could you make a tarball if it that I can download? It would be nice to have a copy to go through and look for stuff that's worth saving and copying over to devmo.
(Assignee)

Comment 5

7 years ago
Can we also write a little post-mortem for devedge? I was inspired by Mitchell's history talk at all-hands. I want to know what was devedge? Why was it created? How did it go? Just a paragraph or so on https://wiki.mozilla.org/MDN/Past_Completed_Projects so we can email/store it.

Comment 6

7 years ago
(In reply to Luke Crouch [:groovecoder] from comment #1)
> Can you check - I think we can throw away developer.mozilla.org.old now. I
> updated our vendor/src/django-mozilla-product-details, and I assume
> kuma/lib/product_details_json is a sym-link?

Correct on the first point... that's when this was created. Sorry, I didn't filter the overall list when I sent it out, or I would have pruned this. In fact I've been meaning to get rid of it for quite some time, so... deleted!

kuma/lib/product_details_json is not a symlink, it's a real directory containing just a .gitignore file. you're correct though in that the actual product_details jsons file are not there... they're in a developer.mozilla.org/product_details_json, right beside developer.mozilla.org/kuma.

The kuma/lib/product_details_json dir should be safe to remove altogether.


> I think the dekiwiki repos is under IT control?

Also correct... those 2 have been fixed.

> Finally, devedge is defunct I believe. Jay - can you confirm? If so, let's
> throw it a going-away party and delete it.

Looks like a separate bug was opened for this: Bug 689027.
(Assignee)

Comment 7

7 years ago
removed lib/mdc_pages and lib/product_details_json since they both contained .gitignore files and have both moved out of the repos. stage9 still looks good.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Version: MDN → unspecified
Component: Website → Landing pages
Product: Mozilla Developer Network → Mozilla Developer Network
You need to log in before you can comment on or make changes to this bug.