Tectonic shift think tank/Tech requirements/Versioning

Problem phases

 * 1) Defining a section and breaking it off
 * 2) * Required actions:
 * 3) ** Built-in 'spidering' to include required images and templates
 * 4) ** Come up with some kind of multi-page module selection metadata to easily select pages/chapters/books
 * 5) Attaching that to a second wiki
 * 6) * Required actions:
 * 7) ** Import should store metadata allowing one-click update (resynch)
 * 8) *** record branch points
 * 9) ** conceptual: draft vs final publishing spaces
 * 10) ** conceptual: trusting working with remote people?
 * 11) Reattaching it to the original as a branch
 * 12) * Required actions:
 * 13) ** Short-term: push back on trunk, leaving local history local
 * 14) *** "What happens in the gated community stays in the gated community"
 * 15) ** Short-term: import with name suffix, etc to sit alongside
 * 16) ** Long-term: explicit branching support in the history information
 * 17) Merging of branches

Forces

 * Downstream/offline copying, similar to "cvs checkout"
 * Customization, localization of resources
 * Upstream publishing
 * Private development before publication "Gated community"
 * eg East Asia strong cultural preference to develop privately

http://www.oeforum.org/collabtools.html#ToolFeatureSet

Structured export

 * 1) Take a page and its resources - by spidering
 * 2) * Templates
 * 3) * Images/media
 * 4) Multipage structured modules
 * 5) * chunks: sections - chapters - books
 * 6) * enough structure to identify useful semantic page groups
 * 7) * How to arrange this?
 * 8) ** machine-readable metadata?
 * 9) ** human-directed (drag-n-drop UI)
 * 10) Select/spider additional linked resources
 * 11) * optionally!

Offline issues

 * different offline forces
 * intermittent offline (development / on a plane)
 * permanent offline (village w/ no net)
 * Links to upstream/offline site... how to handle properly
 * style them?
 * Please take a look at this DOJO tool kit http://www.sitepen.com/blog/2007/01/02/the-dojo-offline-toolkit Mpal

Gated community development

 * grab some stuff from a central site
 * add new information to it...
 * new body of work local to those profs
 * use that localized work in teaching
 * like a customized book
 * and can publish that to let others use it
 * it's public
 * it's got your name on it!
 * incentive - openness, fame, all that that academics love :)
 * How does publishing work?
 * checkout/push checkin -> to public site

Formats

 * Wiki export/import
 * online, intranet, offline interactive development
 * Additional output formats for offline use
 * HTML flat or .zip archive
 * online or intranet
 * Word/RTF/ODT/etc
 * printing or easy offline customization
 * Latex/PDF/etc
 * printing only

Offline editor tools

 * Self-contained wiki app?
 * 'wiki-on-a-stick' style?
 * + ability to sync down/up

Merging

 * Offline editing that's meant to go back to a central place needs to deal with merging a lot better than what we have now
 * is there a good FOSS HTML-level and/or prose-level diff/merge tool?
 * is there a good FOSS HTML-level and/or prose-level diff/merge tool?