PageAccueil Plan du Site Modifications Récentes ModificationsRécentesDeProximité Comment Faire 2012-05-21 fr | 2012-05-20 fr |

Matching Pages:

RSS

2006-05-09

I haven’t posted much lately, for many reasons:

  • I’ve been busy.
  • I’ve been having a ton of epiphanies.
  • I have so much to say.

Right now, I’m ordering what I want to say.

I need to announce something first, though: A few weeks ago, I asked HansWobbe for some help in sorting out various things. I was surprised when he gave me a ticket to Toronto, to talk with him for more than a full weekend, at his place. When I was there, I saw and learned a lot of amazing things, from the intensely digital (he’s got an amazing personal intelligence system on his computer, that he’s hand-coded over decades, that includes a number of ideas from both HyperText & APL; I’m amazed he hasn’t spoken louder about it..!,) to the very worldly (how corporations work, how businesses are made, and so on.) This (relatively) sudden event left me with a lot to think about, and a lot to explore, and a lot to do.

Where does this leave me, with respect to CommunityWiki? Well, in the short term: I feel even greater urgency to write, but (right now) less time to do it. I believe those two forces will balance each other out: I will write about the same.

I’m still working out goals. I want to reassure you that: I’m committed to CommunityWiki, that I’m not going to dissappear on you. It’s possible that, with time, my goals may pull me from CommunityWiki. But (A) I will resist that, tooth and nail, and (B) I don’t think that’s very likely. Further, (C,) it’s possible, even, that my goals will take me straight through (or “into”) CommunityWiki. That is, they may involve you, personally, and directly.

Any actions or goals that I set that have anything to do with CommunityWiki will, absolutely, be described here, first, and put up for review and consideration by the CommunityWiki, before I go through with anything. I just want that to be totally clear. I’m not going to act unilaterally. Just in case anybody is wondering.

But again: I’m still sorting out goals. This is very abstract right now.

One thing I’m thinking about right now, is dramatically increasing the bandwidth to/from CommunityWiki. (That is, “you.”)

Consider this possibility, which integrates several lines of thinking such as: CommunityProgrammableWiki, Hans’ system, personal intelligence systems, group intelligence systems, SocialSoftware, distributed server, component wiki, etc., etc.,…

Turn CommunityWiki into something that doesn’t exist yet:

  • content stored in a SubversionServer?
  • content turned into HTML, nightly, by way of scripts
  • the scripts themselves are kept in the SVN server
  • very simple permission systems (perhaps just 2 roles)
  • directory tree, special directory for files (images)
  • we install ourselves (all of us) with the software to perform commits and checkouts, and walk each of us through the process
  • general public interacts with us by way of a simple web interface
  • RecentChanges constructed from the SVN server change log
  • we use EMACS modes to manipulate the files, follow hyperlinks in the text form, and so on

The shortest version would be to make something we might call “CommunitySvn?,” or something like that.

We would keep both our personal stuff (personal notes, personal files, personal thoughts and meanderings and whatever) in individual folders, and negotiate a public space, where things are presented for group consideration.

Directory tree may look something like:

  • banking/
  • groups/
    • cf/ (oforum)
    • cw/
      • images/
      • renderer/
    • gw/ (gründerwiki)
    • mb/ (meatball)
    • ww/ (wikiwiki.de)
  • personal/
    • alex/
    • bayle/
    • christophe/
    • david/
    • emile/
    • hans/
    • helmut/
    • lion/
    • mattis/
    • mark/
    • ted/
  • wikilog/

“Pages” would go into “cw/”, and the images to go with them into “cwimages”. For SVG, we’d ONLY put SVG into images; The .PNGs would be programmatically generated via inkscape.exe by the renderer. The renderer is all the code that generates the HTML for public display.

The renderer would be edited by us.

We might want the “public” side, where anybody can edit, to be an actual seperate branch, that we selectively merge in, or something, with some special tools.

Or perhaps the public just edits “cw/” pages, but not cwrenderer pages. Not sure.

This idea should probably be split to another page, perhaps “CommunitySvn?,” or “CommunityIntelligenceSystem?” or something. I’ll wait for someone to think that this is interesting, rather than do it myself, though.

i extended the tree above . it’s so easy to unify our wikis . each directory may have its own recent changes . i offer my 500 € from CommunityWikiBank for that .

SamRose, I wanted to look at your pages this last weekend, but I was busy entertaining a very close friend who I haven’t seen in more than a year, and who is about to join a monastary for at least 5 years, and won’t be able to see often.

But I’ve got a bullet point in my list to read through your pages and think about them for (at least!) a few hours.

If you’d like to talk soon, please, I invite the conversation: My phone number is 206.427.2545. (Any time.)

Lion, I have very little idea what you’re talking about, but it sounds exciting!

Heh! If we do it, you’ll be hand-walked through how to do it, and how it works.

We can do this a number of ways; Going straight to SVN is not a requirement.

Perhaps some Python scripts to automate transfers to/from wiki, via the ZergCreep, or something. But I do think we need a shared technical platform. And I’ll probably end up scheduling appointments, making phone calls, to make sure we’re all on the same page, somewhere down the line.

One of the general motivations for doing this, is that if you ever get an idea, you could put it into the the system, and tag it.

We (any of us, who knows how to program,) could automate the collection of ideas of related tags, and output an SVG from it. Then you would arrange the tags in InkScape, spatially, and we would have a store of maps.

We can’t capture ideas very easily right now, because of the entry time. The ContentRouting simply takes way too long right now.

I’m totally in, whatever this is. :-)

Same here. Not sure of what it’s going to end up looking like, but I like Python, SVG and Lion’s notebook system …

Does this mean I have to re-learn how to use emacs? I probably should anyway :P

(Oh and warning: Most things I do online I have to do through a http proxy, which can be a nuisance for SVN and the like)

Lion, I totally understand. Something about the spring makes it a busy time for almost everyone, it seems. (I am getting married on May 27, so I am busy with planning that and a honeymoon, for instance.) I will definitely give you a call when I have a chance!

Define external redirect: CommunityIntelligenceSystem SubversionServer CommunitySvn

ModifierLiensDeProximité: MeatballWiki HyperText WikiMatrix PatrickAnderson

Langues :