On 12/17/2012 03:22 PM, Matt Wagner wrote:
On Mon, Dec 17, 2012 at 10:44:54AM -0500, Mo Morsi wrote:
> The following is the list of wiki pages grouped by their ultimate
> destination. If there are any errors please reply here. I'll start the
> migration process this week.
> Still need to figure out how to handle images and files that have been
> uploaded and links to other wiki pages.
> to site wiki:
We never found a better place, though the website's wiki feels like an
odd spot. I'd almost be up for just putting these on the Conductor wiki,
since it's sort of been a de facto location for stuff that's
There are a few things on this list that fall into the dated category,
but I agree with matty_dubs -- it is probably better to move them as-is
and enter issues to either update or remove the offending content. In
particular, I'm thinking:
In terms of additions, I think it would be useful to keep the Publicity
Cabal Minutes where we keep the Publicity_Cabal writeup.
> to conductor wiki:
> to other wikis:
> Building_Images_for_RHEL (imagefactory, oz)
> Development_Setup (imagefactory, oz)
> Image_Management_Engine (tim)
> Oz_template_description_language (oz)
Not to complicate things, but some of these (such as the 'Building
Images for RHEL' page) were things meant to be how-to guides for
Conductor users, IIRC. It's interesting to me that there are only four
pages that don't fall into the project-wide or Conductor categories so
far -- it almost makes me wonder if we should just lump everything under
I have similar feelings on this but I think I'd rather see things out of
redmine vs extending the discussion on the theory that it is easier to
move stuff around after the fact (and maintain a record of
addition/removal as well).
> excluding: (Most of these are feature pages, alot of these
are done or no
> longer apply)
Is there historic value in these?
I was looking for this page just the other day, trying to help someone
with a messed-up 1.0 install. I expect this is quite uncommon, but it
kind of makes me wonder if there's more value than meets the eye in
keeping some of these pages around.
> Conductor 2012* (not sure what these are)
> Frequently_Asked_Questions (not much here)
> ICICLE (?)
> OVirt_Setup (empty)
> Publicity cabal minutes*
> Rails_best_practices_output (all but empty)
I'd put this together a while back to help less-technical people. I'm
not sure anyone has used it in a while, though it may still have value.
> V2 Conductor*
This appears to be the main page. Are we just going to rename it?
> Visible links
> 1. GitHub_Branches_and_Tags
> 2. ConductorAPIv1_0
> 3. ConductorAPI
> 4. Document_Conductor_models_and_relationships
> 5. Feature*
Thanks for putting this together, Mo. Seems like we had an awful lot of
stuff on the wiki!
I noted a handful of stuff that I'm not sure we need to delete; every
now and then it's useful to be able to go back and look at old sprint
documents or whatnot. (Case in point, I recently had to help someone
pull a design doc off of the old Mediawiki site.) In general I'd
advocate keeping anything that isn't misleading and wrong, and doesn't
make sense to update. Overall, I think this gets us fairly close,
though. (We can always delete pages _after_ the migration, too -- and in
fact they'll enter git history that way. Hence my thinking that it makes
sense to be quite conservative with what we delete.)
I added a few to the potentially ignore pile but I'd readily agree with
Matt in that it might be better to do some amount of pruning
post-migration. I am not opposed to pruning the obviously irrelevant
The other bit wasn't explicitly mentioned so I thought I would ask. I
think the general consensus was that we should convert the textile to
markdown prior to importing the pages into github. I haven't heard any
dissenting views, but maybe it is worthwhile to explicitly say unless we
hear disagreement on the list by Wednesday 5:00 pm EST everything will
get run through pandoc and be imported as markdown.