Changes between Version 2 and Version 3 of WikiStart
- Timestamp:
- 10/05/2008 10:12:50 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v2 v3 1 1 = Distributed Knowledge System = 2 2 3 == Conversations == 3 DKS is just a working title for this project, and may change. 4 4 5 Mike's original conversation: 5 == Mike's Original Explanation == 6 6 7 7 (10:16:10 AM) Mike Howsden: i want to get at least one of my political type projects off the ground 8 8 9 9 (10:16:30 AM) fugue88@gmail.com/Home: I was going to burn the .org site to (2) dvds for you, if you like that. 10 10 11 11 (10:16:42 AM) Mike Howsden: sure, that sounds good 12 12 13 13 (10:17:28 AM) Mike Howsden: i have about 3 essays to write before i work on other side projects though 14 14 15 15 (10:17:47 AM) fugue88@gmail.com/Home: I've been enjoying your blog posts, btw. 16 16 17 17 (10:17:50 AM) Mike Howsden: and a friend of mine is on Sabbatical this year so if he wants to do something together i'll probably do that next 18 18 19 19 (10:17:59 AM) fugue88@gmail.com/Home: Okay. 20 20 21 21 (10:18:10 AM) fugue88@gmail.com/Home: What's he into? 22 22 23 23 (10:18:29 AM) Mike Howsden: philosophy, Charlie Huenemann 24 24 25 25 (10:19:03 AM) Mike Howsden: the idea i've thought to do with him is build an educational resource around one of his texts 26 26 27 27 (10:19:11 AM) fugue88@gmail.com/Home: Ah! 28 28 29 29 (10:19:16 AM) Mike Howsden: it's a short history of western civilization 30 30 31 31 (10:19:32 AM) Mike Howsden: did i ever show you cnx.org? 32 32 33 33 (10:20:26 AM) Mike Howsden: it allows you to create small educational building blocks that you can connect together with different lenses 34 34 35 35 (10:20:27 AM) fugue88@gmail.com/Home: Yeah, I've still got it bookmarked to "look at later." ;) 36 36 37 37 (10:20:37 AM) Mike Howsden: so i was thinking to build a lens on top of it 38 38 39 39 (10:20:51 AM) Mike Howsden: turn his book into those educational units and build a lens just for him 40 40 41 41 (10:21:11 AM) fugue88@gmail.com/Home: I'd like to see that when you've got something to show. 42 42 43 43 (10:21:40 AM) Mike Howsden: in the end i'd like to make an online book where the first edition can be done by the author and the second edition done by the author and the web 44 44 45 45 (10:21:52 AM) Mike Howsden: so it'd have to build in creative commons licensing and all that 46 46 47 47 (10:22:01 AM) Mike Howsden: there's probably some stuff out there though that i could string together 48 48 49 49 (10:22:03 AM) fugue88@gmail.com/Home: That's an interesting idea. 50 50 51 51 (10:22:20 AM) fugue88@gmail.com/Home: You could probably tie things up so that the web version is also available in print format. 52 52 53 53 (10:22:25 AM) fugue88@gmail.com/Home: Hard-bound or whatever. 54 54 55 55 (10:22:28 AM) Mike Howsden: righ 56 56 57 57 (10:22:29 AM) Mike Howsden: exactly 58 58 59 59 (10:22:35 AM) fugue88@gmail.com/Home: Cool. 60 60 61 61 (10:22:37 AM) Mike Howsden: so they can get the output in whatever form they want 62 62 63 63 (10:22:44 AM) Mike Howsden: latex 64 64 65 65 (10:22:46 AM) Mike Howsden: perhaps 66 66 67 67 (10:22:59 AM) Mike Howsden: whatever lends itself given the other tools i'll be plugging into really 68 68 69 69 (10:23:15 AM) Mike Howsden: so half of the project is making a good tool for the author 70 70 71 71 (10:23:24 AM) fugue88@gmail.com/Home: latex->pdf, then upload to lulu.com and you've got print-on-demand. 72 72 73 73 (10:23:29 AM) Mike Howsden: the other half is making an educational resource that matches what the author is trying to do with that text 74 74 75 75 (10:23:49 AM) Mike Howsden: i'd like every user to have editorial control 76 76 77 77 (10:24:12 AM) Mike Howsden: so say a teacher in New York wants to use the same text but integrate other educational nodes, they could do that 78 78 79 79 (10:24:37 AM) fugue88@gmail.com/Home: Would those changes be on the global copy, or saved as a branch? 80 80 81 81 (10:24:37 AM) Mike Howsden: this would all be open source 82 82 83 83 (10:24:47 AM) Mike Howsden: branch 84 84 85 85 (10:24:52 AM) fugue88@gmail.com/Home: Awesome!! 86 86 87 87 (10:25:02 AM) Mike Howsden: good idea? 88 88 89 89 (10:25:05 AM) fugue88@gmail.com/Home: I'm giddy over this idea! 90 90 91 91 (10:25:21 AM) fugue88@gmail.com/Home: The source code for launchpad is available now. 92 92 93 93 (10:25:22 AM) Mike Howsden: it seems pretty necessary and useful in this day and age 94 94 95 95 (10:25:39 AM) fugue88@gmail.com/Home: It might have some good ideas at a web interface to push and pull between branches. 96 96 97 97 (10:25:59 AM) Mike Howsden: i'll let you know as i start to tackle it 98 98 99 99 (10:26:03 AM) fugue88@gmail.com/Home: Great. 100 100 101 101 (10:26:20 AM) Mike Howsden: his text was exactly what i'd been looking for as the type of text to build form 102 102 103 103 (10:26:22 AM) Mike Howsden: from 104 104 105 105 (10:26:32 AM) Mike Howsden: because each chapter is a pretty isolated unit 106 106 107 107 (10:26:38 AM) Mike Howsden: focused on one or two individuals 108 108 109 109 (10:27:07 AM) Mike Howsden: or a particular common idea (like say, the Renaissance --not sure i can spell that word) 110 110 111 111 (10:27:16 AM) fugue88@gmail.com/Home: I think you got it. 112 112 113 113 (10:27:36 AM) fugue88@gmail.com/Home: That *is* a cool idea. 114 114 115 115 (10:27:49 AM) Mike Howsden: he doesn't have expertise in all of western history (of course) 116 116 117 117 (10:27:54 AM) fugue88@gmail.com/Home: Cherry picking would be essential I think. 118 118 119 119 (10:28:01 AM) Mike Howsden: but say he can collaborate with someone in another state 120 120 121 121 (10:28:05 AM) Mike Howsden: they can work on the parts he doesn't know 122 122 123 123 (10:28:15 AM) Mike Howsden: and their changes become available to him 124 124 125 125 (10:28:30 AM) Mike Howsden: he can publish his updated version incorporating their new content 126 126 127 127 (10:28:39 AM) Mike Howsden: i think you get the idea 128 128 129 (10:28:42 AM) fugue88@gmail.com/Home: Yeah. 129 (10:28:42 AM) fugue88@gmail.com/Home: Yeah. 130 131 == David's Thoughts == 132 133 Definitions: 134 135 module: an article, essay, etc., that may be studied and understood on 136 its own, assuming the reader is familiar with any prerequisites 137 138 collection: a (possibly strictly-ordered) set of modules, to explore a 139 subject in detail 140 141 142 Ideas: 143 144 It seems like a module has a fairly good almost 1-to-1 mapping with a 145 file. The exceptions would be that a module might include an image or 146 other data that would be stored in a separate file. 147 148 Typically, a writer/designer would create an collection as opposed to a 149 single module on a subject. The collection seems to map well with a 150 version-controlled repository. If I were to change a module, I would 151 probably like to make slight adjustments to other modules of my 152 authorship in the same collection, so it makes sense to version them 153 together. 154 155 However, I would like more flexibility than current versioning system 156 offer. First, when branching an existing collection/repository, I would 157 like for that relationship to be selective---ie, only pull in 158 modules/files from the parent that I specify. Second, I would like 159 multiple inheritance, so that I could pull modules from multiple 160 collections and multiple authors to create my own collection. 161 162 So the workflow is something like picking the parent collections, 163 selecting the modules to import, making changes to those modules and 164 writing your own new modules, commit. 165 166 Later on, refresh or pull from the parents, merge, save, commit. 167 168 It's useful to include quotes from other modules without necessarily 169 pulling in the entire module to your collection, so it would be nice if 170 embedding selections from modules were supported too. It should also 171 tie in the the update/merge cycle, so that the quote in your module gets 172 updated (when you're ready for it) when the source module is modified.
