parent: http://etherpad.wikimedia.org/p/4Sd60vrqIr
parent archive: http://pastebin.com/cqT4ZUQV
- ~ - 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)
Hmm, I've been doing whichever pool has the most in it, sometimes they've had five lately but mostly they just get up to four. There's enough to put three in most of these pools so far, still some empty ones near the ends of the cycles. So I'm doing this pool now because it has five metaprocess commenters ready. But some of them are really sticky on this step! :o This one just has a few but I think there's a couple with five! :o So um I don't want to just spin around here until they run out so I might need to change that algorithm of going to the pool with the most. That's great! I've been trying to get that to happen more, that's hardly ever happened before that it's been difficult to drain pools. I've been specifically trying to do that with the silly little Do Something pool, in fact that's about all I made the Do Something pool for even. The processes there have like a zillion steps in that pool, so now there's just none there with two or four on the way I forget but soon it'll be a bunch of them stuck there. So then I'll have to keep them asleep so they're not stuck there, and there's something pushing it, it all stacks up and pushes through right, hopefully. (o(:
[ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
I've been trying to comprehend how much overhead there is really in this style of process. They're not too heavy to use them for lots of things, obviously, sure. They're not too heavy for what they are. But I guess the truth is that I trim them to fit into this shape. I limit a little bit my imagination of how they can flow. But it's been invaluable to watch them slowly manually flow through these pools because now I have any sense for it. If I'm going to write things to go through and use pools in autonomous complicated ways, I need to understand it. I need to understand more about it still even. A lot of thoughts I have about how pools flow together are just totally theoretical. They've only been run in my head for a second by imagining some particles that are supposedly processes and flowing them through simplified head models and seeing how those particles flow. But processes don't flow like particles at all, they have intention to them. You can tell them what forms to flow into, they're not just a mechanism where you have to wait to see how they flow. I could tell this process right now to flow through these pools in various ways, not even just within this style but I could have them hover in pools in a new way, or I could actually make that step that goes to the lonliest pool, and so the "problems" that emerge from allowing them to take a particular physicality for a moment is really a decision, you can decide any moment to flow them into a different shape. I guess maybe it could be possible to build up inertia with actual resources that are held that can't be reshaped quickly, but that's not these now.
[ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
My intuitions are distorted I think by the smallness of the shapes I've been able to make. These have that physicality to them that emerges, because they're such simple springy shapes. This particular etherpad springs to sleep next, then springs awake, boing sproing. So if there's just a few of those little springs bouncing then sure, the shape of the spring matters a bunch. But if you have larger complicated systems I don't think the shape of each part has that same effect. The whole thing is bounded, controlled, ordered, purposeful. So if some little spring sproings out of that stream, so long spring. The more things you join together the more they're unsteerable oceanliners instead. But also it's possible for it to be clear in a larger structure how it's directed, and for it to be a nice democratic smooth useful unstuck system. Theoretically. ;)
Finally this is sleeping so finally this Metaprocess Comment pool won't have four in it still, so then I'll start squishing down the pools that just have three. I was just pushing them down and then I encountered this resistance from this pile of structure-light metaprocessers, and part of me thought I should just go do other stuff anyway because that would make sense. But I'm not mostly making sense, I'm experimenting. And it makes experimenting sense to just slowly push through this pile and feel that resistance. I like it, it's sproingy! I've been putting that sproing into various pools here, trying to make them all that consistency. I've thought a lot about how it might be necessary to make pools that somehow have backup bottom basic maybe even just fixed in place default options, so there's just no way to push down to nothing. If you're having a program automatically draw from a pool to do something, that certainly might be wise. But so far instead with these pools I've been playing with what I'm doing instead is just feeling what it's like to push down into them, sometimes bottoming out, sometimes unexpected resistence, different feelings. Smoothing this family over this set of pools has been a really good learning experience in terms of texture. I'm also squirting new bursts sometimes from the sleep swirls up over them and smoothing those down into it, feeling the textures, feeling the flow.
[ mj ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
bonus archive: http://pastebin.com/hypa6i2n
um what is this
oh a metaprocess commenter i guess
um i don't think i have a sleep swirl pool for those ?!
yay a new sleep swirl
Metaprocess Analysis Sleep Swirl (MASS): https://docs.google.com/document/d/1jWPBJKPKd1pg9kvgX1eoGveuVzuU76ZI-K6qReBBiCY/edit
[ mj ] WAKE UP (write a brief note here about why you decided to wake this particular process up today)
I'm waking up pretty much everything I can find, to try to really fill in these pools.
[ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
OK well I put Suggestions for the Mutators. I don't click on this pool when I'm in a thinking mood. :P
Other than that, hmm, well. I've been thinking of putting in this new step, think about this child's direction, I found it somewhere. I'll flow that in. :) Needs some style changes, hurm.
OK that'll do. No reason not to leave some stuff plain. Be plain, plain process.
[  ] 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!))
[  ] LINK CHILD TO PARENT (at the top of this child's document write "parent:" and then a link back here)
[  ] MEMORABLE URL FOR CHILD (use http://muse.dillfrog.com/random_words/ to generate some random words, choose two or three of them, then use http://tinyurl.com/ to make them into a link to this child's document)
[  ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
- ~ - checklist - ~ -
[  ] 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)
[  ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
[  ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
[  ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
[  ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
[  ] WAKE UP (write a brief note here about why you decided to wake this particular process up today)
[  ] SUGGESTIONS FOR THE MUTATORS (write some suggestions here of how this process could be improved, to give the mutators some ideas)
[  ] MUTATE (make an improvement or change in the clean copy of this checklist below)
[  ] 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!))
[  ] LINK CHILD TO PARENT (at the top of this child's document write "parent:" and then a link back here)
[  ] MEMORABLE URL FOR CHILD (use http://muse.dillfrog.com/random_words/ to generate some random words, choose two or three of them, then use http://tinyurl.com/ to make them into a link to this child's document)
[ ] CONSIDER POSSIBLE DIRECTIONS FOR THIS CHILD'S DEVELOPMENT (write a few thoughts here about what uses this child might be put to or what directions it might develop in)
[  ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)