This was a trivial operation: I just did a 'git rm -rf <directories>' in my personal fork, then grepped the entire repo again to ensure that _nothing_ referenced those directories. (They were referencing each other, which is why they didn't appear as leaf nodes in my search). This is all PR #165 now.
Hopefully this can be agreed upon expeditiously, and then I can resume looking for leaf nodes to prune. The ultimate goal of this is to eliminate all the duplicate files (there are like 50 of them) and have only one remaining copy of each file, so we'll have confidence we know which one is the one that shows up on the website, when we go editing stuff like links and copyright notices. Thanks, Jeremy On Fri, Jul 10, 2020 at 1:15 PM Tadd Wood <taddw...@apache.org> wrote: > > +1, Jeremy I’ve noticed the same. I’m ok with moving forward with the > clean-up. > > Thank you, > Tadd Wood > > On Jul 10, 2020, at 10:42 AM, Jeremy Nelson <jer...@digitalminion.com> > wrote: > > Everyone, > > I noticed that in the ONI days, there were some blog posts made with > wordpress. These blog posts live in top level directories (such as > open-network-insight-3-most-asked-questions). > > I noticed that when ONI was made Apache Spot, these things occurred: > > (1) The top level directories were deep copied and were edited from > ONI to Apache Spot, creating additional top level directories such as > "apache-spot-3-most-asked-questions" > > (2) All of these blog posts were deep copied underneath /blog/ when it > was necessary to migrate the Apache Spot website to the Apache format. > > (3) The copied blog posts under /blog/* were edited to point at all > the new apache spot web links. > > What *didn't* happen was these original blog posts (1) nor the > non-migrated deep copy ones (2) were cleaned up. > > I have verified these things: > > (1) Nothing points at these top level blog post directories. > Everything points at /blog/* now. > (2) These top level blog post directories DO NOT POINT at Apache Spot > -- they still point at ONI > (3) Many of these directories contain the only links to files which > have been migrated away from /doc or /wp-content/ into /library > > I am using some tooling look for duplicate files and dead links, and I > believe by removing these abandoned/orphaned directories, I can more > accurately capture what is stale and needing cleanup. > > Does anyone have any concerns with removing directories that have no > inbound links, which do not link to apache spot, and which have been > successfully copied/migrated to another place? > > Thanks, > Jeremy
