Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- parent: http://etherpad.wikimedia.org/p/4Sd60vrqIr
- Welcome to Etherpad!
- Thanks! Welcome to this evolving process! Evolving! Process!
- This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!
- Get involved with Etherpad at http://etherpad.org
- - ~ - checklist - ~ -
- [ mj ] PRAY FOR VICTIMS OF THE HOLOCAUST (take a brief moment to remember the victims of the Holocaust and to renew your committment to the fight against fascism)
- [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
- It's funny how I so easily get emotional about these things. Just now I was feeling like I was running out of them as they swirl down the sleep swirl. Oh no, this is the last Metaprocess Comment active right now, what if I run out and don't have anywhere to put my Metaprocess Comments. I'm just thinking of that in relation to all the other dramas I've imagined. And really they're just going along, so ordinary.
- [ mj ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
- sent to "swirl to sleep" https://docs.google.com/document/d/11PHcAzxDQrBFtCbKKvtqsexLMsUxUbS2NWwc6gIlnRs/edit
- [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
- I'm just putting in four more copies of Metaprocess Comment, make this a sticker. I just thought of calling them that. Better not to get jargonny though really I suppose sigh. And also I guess it'll need Wake Up and Suggestions at least, hrm. There that'll do it. Still as plain as rain.
- [ mj ] COPY (make a new editable document somewhere (for instance one of these http://evolvingprocesses.wikidot.com/working-etherpad-servers open etherpad servers) and copy the clean checklist below into that new document (TWICE!))
- https://docs.google.com/document/d/1PqReu6343yxq4tzxjTKbe99rTW2Di06jXXEXvk598cg/edit
- [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
- - ~ - checklist - ~ -
- [ mj ] PRAY FOR VICTIMS OF THE HOLOCAUST (take a brief moment to remember the victims of the Holocaust and to renew your committment to the fight against fascism)
- [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
- One thing I've been thinking about is how to go about resurrecting old processes. I don't think these old random ones even ever had pools that went with them really, did they? I must have had them in some sort of general mess and poked at them, because I'm just adding new steps all the time with no apparent sense for where they're going to go. This family I'm typing in now, I feel like it's going to feel old in a similar way, where there's a lack of clarity about what pools things are going to. Why doesn't this say, Mungojelly's "process/Metaprocess Comment" Firefox bookmarks folder? Is it so I can split this pool and keep metaprocess commenters from this family ready somewhere else?!? That seems theoretically useful but it's not what I've been doing, is it? But I have this sense that they're very general, adaptable, that they could just be moved to a new set of pools at a moment's notice. But then when I try to resurrect some old nice process, I'm like, WTF I don't have these pools this goes with.
- It would make sense if they explicitly made their own pools somehow!? Like often this style they'll say something like, put this here, BTW make it if it doesn't exist. These could say, move it to your X folder in the tree, BTW make that if there isn't that. Then putting one of them in an empty tree it tells you how to build a tree of nests for them. So what should this step say then? Should there be another step next that says to move this to a metaprocess comment folder? There is, it's just an extragenetic step. Everything can't be explicit all the time, yo. What if there was a paragraph at the beginning explaining where to put these things? Ugh that's useless. And the thing is there's various processes blending together, and the resulting pool structure is the superset of all the pools they all need. It's enough to make me think this should actually be written in a structured way that programs could try to crawl and understand them. But it would be tragic to reduce them to any particular medium that a particular program could be trained to. Ug ug ug.
- [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
- OK I get it, I've been fooling myself thinking that these are written in English. No one can read and comprehend and respond to and run these in their own brains because they're actually written in a specialized, English-like language I've unconsciously developed while developing them. "Metaprocess Comment" means nothing in English, and certainly "[ ] METAPROCESS COMMENT" doesn't mean in English that you next move the process to a pool for Metaprocess-Comment-ready processes, etc. So in thinking about what languages to move these towards, real normal English is one option. But a process actually written in normal daily English would have to be very long and/or clever. There's so much that has to be explained.
- People are mostly fooling themselves that their programs are written in the programming languages they're written in, either. If it's a big enough program it writes its own internal dialect. The only way it's written in the underlying language is that at least there's required to be clear definitions SOMEWHERE. Clear enough for a computer, anyway. Not clear, that's the wrong word, but accurate. This code written for human brain doesn't even need that, it's just bootstrapped in my own brain and there's no coherent explanations of any sort anywhere. But the average program with just some obscure code somewhere explaining is almost as unknowable. But then as I said that it occurred to me that explaining more without a connection between the code and the explanation violates DRY, so that pressure helps explain why there's so little explanation anywhere of anything.
- So again again again if I make evolprocs where this shit is clear or explicated at all it'll be the first time anything is clear anywhere. I mean that should both lower my expectations and goals and also raise them. It should be really difficult to make processes transparent about what they do and how to change them, but also to whatever extent I succeed it'll make them a special new unique awesome thing, giving people any control over the systems that run their lives isn't what's basically expected it's a bonus. :/
- [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
- If I could make something that could clearly be resurrected later without other machinery having to stay intact, I'd like that. For one thing I could save them up for purposes in the far future with more of a sense that they can be brought back to those purposes. Hmm I wonder if whole families could intelligently rest together ready to come back. Well right well that's my idea with the sleep swirls. They're sleeping divided by purpose and the idea is to bring back the ones you want when you want where you want them, maybe spin up from some family into some new set of pools. But I don't know how realistic that is really. I guess I've done it once. I spun these back up into these pools, which are different from their other pools they were born in, the Tab Mix Plus ones. It was a PITA, really. :( It was mostly easy enough but also after there were a zillion folders it got to be like, have I made a folder for that one yet, and where. A mess of them. Maybe they're just not organized well.
- Something that keeps occurring to me is if only they were more organized into like sections. I've been informally thinking of them as separated into a work phase and a structure phase. Oh and I guess the structure phase is followed by or includes a childcare phase. So it could make sense to formalize that. Four stages perhaps, work, meta, reproduction, childcare. First do something and then think about "did that work?" or make pretty pictures about it, then mutate based on that thinking, care for the mutated children and set them up. So that's why I've been tripling my work steps to try to get them to feel balanced, sigh, hmm.
- [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
- This habit of putting the pools for a family all in one place is good for learning how they flow, but I'm not sure it's actually the most useful shape in general. What I've got here is this family that mostly loops around to this same set of pools, but then there's a few exits. They email themselves out, for instance. So then there's that loop that goes out into space. OK like say these pools died, but then I X Key responded to one of the ones sent out to him, so I'd be like, OK well I guess this needs a new set of pools to resurrect it. So these same pools could refresh themselves as long as they ever go out somewhere else. Really it seems to me like the pools should be more diverse, and there should be more explanation of the character of the pool at the point you pass to it. Like instead of running together, stages should be gathered behind a trigger and run to triggering the next stage. I mean they do, it's just not explicit here.
- I feel like it makes sense to have them collect in a pool in the middle of being handed to someone. Or uh no at the beginning!? You're handed a process, and it explains to you where you should put it away. Then you bring it out later from that place and use it, which results somehow in passing it to its next agent so they can store it in their pools. IDK what they're doing now is just emailing or writing to people, and leaving it to them how and if they want to organize them. So that's nice I'm trying to give them freedom but really it's just vagueness. They should have helpful suggestions about how to keep them and what use to make of them. A stage should appear to someone as a simple useful object, which just happens to come back when you've used it. Hrm.
- [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
- Yeah sure these aren't a perfect shape I agree. But they're on their way to a flexible enough shape to move forward, which is what matters. They're going to connect to flow-style partners, and then there'll be those parallel connected systems. So then that allows more modular upgrading! A different kind of flow-style can connect, or once the flow-style is established and makes sense it could be triggered/supported by a different style of checklister, or w/e. As long as I keep the coupling loose between the processes in these multi-process structures, so new things can bounce in. I'm sure it'll be very loose , there's no reason it shouldn't be. I could always like have a second flow partner so I have room to make new simple ones without losing functionality, w/e.
- [ mj ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
- sent to "Metaprocess Analysis Sleep Swirl (MASS)"
- https://docs.google.com/document/d/1jWPBJKPKd1pg9kvgX1eoGveuVzuU76ZI-K6qReBBiCY/edit
- [ mj ] WAKE UP (write a brief note here as to why you decided to wake up this particular process today)
- I'm looking for things to turn into s-exp format, and I wanted to wake up Metaprocess Commenters particularly, and I thought it'd be good to try that style in an etherpad, so that adds up to this. :)
- [ mj ] SUGGESTIONS FOR THE MUTATORS (make some suggestions here of how this process could be improved, to give the mutators some ideas)
- Transform it into s-expression format. That oughta be enough for today I'd think.
- [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
- OK, transformed with this code (I had to take a newline out of the regexp to get it to work):
- #lang racket
- (define task-format (regexp "\\[.*?\\]\\s* (.*?) \\s*\\((.*?)\\)\n"))
- (define (convert-task task-string)
- (let ([task-parts (regexp-match task-format task-string)])
- `(task ((done-by "")
- (title ,(cadr task-parts))
- (instructions ,(caddr task-parts))
- (response "")))))
- (define (convert-tasks input-text)
- (let ([task-strings (regexp-match* task-format input-text)])
- `(checklist ,(map convert-task task-strings))))
- [ mj ] COPY (make a new editable document somewhere (for instance one of these http://evolvingprocesses.wikidot.com/working-etherpad-servers open etherpad servers) and copy the clean checklist below into that new document (TWICE!))
- http://piratepad.be/p/H8TbmxlFBv
- [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
- (checklist
- ((task
- ((done-by "")
- (title "PRAY FOR VICTIMS OF THE HOLOCAUST")
- (instructions "take a brief moment to remember the victims of the Holocaust and to renew your committment to the fight against fascism")
- (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "")
- (title "SLEEP")
- (instructions "link to this process from some quiet pool where it can rest for a while until it's needed")
- (response "")))
- (task
- ((done-by "")
- (title "WAKE UP")
- (instructions "write a brief note here as to why you decided to wake up this particular process today")
- (response "")))
- (task
- ((done-by "")
- (title "SUGGESTIONS FOR THE MUTATORS")
- (instructions "make some suggestions here of how this process could be improved, to give the mutators some ideas")
- (response "")))
- (task ((done-by "") (title "MUTATE") (instructions "make an improvement or change in the clean copy of this checklist below") (response "")))
- (task
- ((done-by "")
- (title "COPY")
- (instructions
- "make a new editable document somewhere (for instance one of these http://evolvingprocesses.wikidot.com/working-etherpad-servers open etherpad servers) and copy the clean checklist below into that new document (TWICE!)")
- (response "")))))
- (checklist
- ((task
- ((done-by "")
- (title "PRAY FOR VICTIMS OF THE HOLOCAUST")
- (instructions "take a brief moment to remember the victims of the Holocaust and to renew your committment to the fight against fascism")
- (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "") (title "METAPROCESS COMMENT") (instructions "write some thoughts here about how these processes have been going") (response "")))
- (task
- ((done-by "")
- (title "SLEEP")
- (instructions "link to this process from some quiet pool where it can rest for a while until it's needed")
- (response "")))
- (task
- ((done-by "")
- (title "WAKE UP")
- (instructions "write a brief note here as to why you decided to wake up this particular process today")
- (response "")))
- (task
- ((done-by "")
- (title "SUGGESTIONS FOR THE MUTATORS")
- (instructions "make some suggestions here of how this process could be improved, to give the mutators some ideas")
- (response "")))
- (task ((done-by "") (title "MUTATE") (instructions "make an improvement or change in the clean copy of this checklist below") (response "")))
- (task
- ((done-by "")
- (title "COPY")
- (instructions
- "make a new editable document somewhere (for instance one of these http://evolvingprocesses.wikidot.com/working-etherpad-servers open etherpad servers) and copy the clean checklist below into that new document (TWICE!)")
- (response "")))))
Advertisement
Add Comment
Please, Sign In to add comment