This sounds good. I would advocate for solution 2 in the long term (post-preview).

There are a lot of tools -- #insert shameless plug for trac# -- that can help us at OSAF and help outside contributors be more productive and efficient. That said, we are getting along alright with what we have and can't really take the time away from working on preview to migrate to something new. This proposal sounds like it's going to get us enough bang for our buck in the short term to satisfy our preview goals and not confuse new people coming on to the wiki.

+1

-Mikeal

GOAL
Our goal is to try and have people pointing to the new wiki before the Preview launch dates. This will help make things easier for people outside the organization to find the most recent information when running searches on the wiki (and in Google).

OPTIONS
The following options have been proposed. The pros and cons of each are listed out on the wiki page: http://wiki.osafoundation.org/bin/ view/Journal/DraftWikiProposal

+ Option 1: Copy all and migrate all the existing files over, ask everyone to go through and deprecate old pages which are no longer useful. + Option 2: Start completely fresh. Perhaps even to use a different wiki. Link back to the old wiki site, but as a read-only view. The old wiki site will not be maintained, only one wiki will be 'in production'. + Option 3: Copy only selected pages over. Link back to the old wiki site, but as a read-only view. So if people would want to move a page over to the new wiki after migration, they would have to create a new page on the new Twiki. Once again only one wiki site is in production and maintained.

PROPOSAL
+ The wiki team will be working on new templates, layout and sections based on the taxonomy work by Ted/Mimi: http:// wiki.osafoundation.org/bin/view/Journal/WikiReTaxonomy + We're deciding to go with option #1: Copy all the wiki pages and migrate all the existing files over to the new server. Excluding some obvious sections ie. trash, other pages which are deprecated. + Locate all the important pages and map them to the new hierarchy. ie. Journal to Notes section, some sections in 'Projects' need to be moved to the new 'Planning' section. + Ask everyone to do some wiki gardening on their own sections and deprecate any pages which are no longer relevant. + Send out a last call to review any last wiki pages left on the old wiki site. + The plan is to only have a single wiki in production, so after the defined 'cut-off' date all the old content will be available under the new UI.
+ Continue to follow up with more wiki pruning into 2007 as needed.

TIMELINE
We're working towards December to update the framework and look-and- feel, then a second round in 2007-Q1 for final wiki pruning.

We'd like to ask if anyone has any concerns before we move forward with the proposal.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

Reply via email to