Welcome to Etherpad!
Thanks, welcome to this 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!
Okie dokie, cool.
Etherpad on Github: http://j.mp/ep-lite
- ~ - checklist - ~ -
[ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
Oh OK good I found a plain one. I made some tab groups for activities I'm doing unprocessedly, watching videos and reading articles specifically. So then I was trying to find something to mutate over to them, but all the threads here have things they're doing! :o That's good, I guess, lots of stuff getting built. Maybe I'm trying to do to much at once again, yeah probably, probably.
[  mj  ] SILLY SUGGESTIONS FOR THE MUTATORS (make some silly useless   impractical suggestions for how to improve this process, just to get us   thinking creatively)
Do each step a random number of times. A step saying to go out and look at the stars. Put them on paper and mail them to yourself.
[  mj  ] SUGGESTIONS FOR THE MUTATORS (make some vague suggestions of how this  process could possibly be improved, to give the mutators some ideas)
What I'm actually looking for is some sort of Explain About Processes step.  Explain Evolving Processes.
[ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
Yay done, this is a quite plain simple strand right now, so that was easy. I decided to leave in Metaprocess Comment because I think that's the right balance and it didn't seem entirely unrelated. But it might also be wise to make one without that in case that becomes a bottleneck or extraneous.
[ 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/196wXgPIsOv0fgX1ADLx-6havXoM3_VK3KmOLByDa1f8/edit
[ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
- ~ - checklist - ~ -
[ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
There's a lot of things I've gradually learned that are actually pretty subtle, or nebulous. I'm swirling these processes in a certain way right now, and I have some sense of how long it'll take and the flow of it. Before I would have gotten upset with them I feel like, for having this slow flow to them. But that's their rhythm, they have various rhythms, they have rhythm to them. I've learned to feel the rhythms of them. That's why I'm swirling them now is because that's the rhythm they need. Swirl down, swirl up, that bobbing rhythm, along with their other rhythms, their flow, their swirl, their magic.
[ mj ] EXPLAIN EVOLVING PROCESSES (post somewhere on social media explaining something about evolving processes)
https://plus.google.com/115207639490096731393/posts/VXgr1HHLENX
Brett WilliamsShared publicly  -  5:06 AM
 #evolproc


Evolving processes often seem to be repeating "the same thing" but actually the context is always changing. Something else is changing each time somewhere else in the process.
So  you see a repeated action or quality, like you might notice soon many  repetitions of this sort of step like this one I'm doing now from https://etherpad.fr/p/ZS2OS51hq1 that says to explain about evolving processes. It's always the same thing, explain explain explain.
But  it's also different because the context is changing. Maybe it's  different how I prepare to explain, or how I think about it afterwards.  It has a different feeling than an ordinary repetitive activity, which  is only comfortable in a repetitive context and tries to maintain  stability. Evolving processes have a feeling of flow.
 #evolvingprocesse   #evolproc  ?
Etherpad.fr
etherpad.fr
[ mj ] SILLY SUGGESTIONS FOR THE MUTATORS (make some silly useless impractical suggestions for how to improve this process, just to help us think creatively)
A process for processing every step of every process such that there's an infinite regression of them that can only be solved with calculus.
Write the process out in chocolate syrup and eat it.
A point system where processes win the right to have children.
[ mj ] SUGGESTIONS FOR THE MUTATORS (make some vague suggestions of how this  process could possibly be improved, just to give the mutators some ideas)
It needs Sleep. Also it needs more content and less structure. Trim Metaprocess Comment entirely, and then make more evolproc explaining, double that step or add another version, w/e.
[ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
OK I made another Silly explain step here, and I copied in that same Sleep step but hmm it seems to have lost its "somewhere" somewhere, i'll put that back in this one.
[ 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/1Z1w6XUtDnUusZA_c9X2J9koNo-EqK04kjddWmcU2oog/edit
[ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
- ~ - checklist - ~ -
[ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
Dropping threads sometimes is inherent to this metaprocess. But also it's against my nature. I guess that part of my nature is part of what evolprocs are designed to counter. I never want to throw away anything, so these produce too too much. They make you choose. So there's a little pain or tension whenever it gets to that choice, when I realize that I've set myself more theoretical work than is really possible at all. Right now I'm choosing by spinning them down, and pretending that I could spin them all back up, but I know that some will interest me more than others and some threads will advance further than others.
I also select them by letting them go into vulnerable places. I make them dangerous and fragile on purpose, knowing that I have extra. It's freeing in a way I guess. It's hard actually to find things that are fragile in the right way. Most things are either pretty stable and certain or else they're completely uncertain, unlikely even. There's not that much that breaks a third of the time, say. Hmm.
[ mj ] EXPLAIN EVOLVING PROCESSES (post somewhere on social media explaining something about evolving processes)
https://www.facebook.com/mungojelly/posts/10152701645093232
Brett Douglas 'Mungojelly' Williams
1 min ·
You  can't mostly follow evolving processes by following a particular  process. I suppose that's part of how it's confusing enough that no  one's been able to follow it.
 I often link to a particular process when I talk about them, in this case it's https://etherpad.fr/p/ZS2OS51hq1  the process that instigated this post, but following that link and  paying attention to that process won't especially help you understand  them. That process is just posting this explanation, and then it's  posting a sillier explanation somewhere, and then it's going to sleep  for a while.
 If you watched that etherpad absolutely nothing  would happen except sometime when I do the silly explanation, sometime  later when I put it to sleep, and then much much later when I wake this  family up again and cycle it around it again. So there's no point to  paying attention to that particular process.
 I include the link  to the process I'm doing just so you have access to that information  about what you're involved with. I just think it's polite to be open  with someone about the nature of a system as much as possible if that  system is going to affect them somehow. So that link is to explain to  you the whys of this particular event of this explanation being sent to  you, but it won't explain especially about processes in general, the  whole big flow of them.
 You can only really watch processes move  by watching them flow through a pool. A "pool" is what I call it when  various processes all list themselves somehow in the same place. There's  various ways they can pool together, like hashtags or listing  themselves on documents or printing themselves out on paper and sorting  themselves into envelopes, etc. So for instance here's a pool on Twitter  on the hashtag ?#?evolproc?: https://twitter.com/search?f=realtime&q=%23evolproc&src=typd  If you go to a particular process nothing will happen there most of the  time, or maybe ever. You have to go to a pool to catch the processes  that are alive and swimming.
Etherpad.fr
etherpad.fr
LikeLike ·  · Share

    Write a comment...

[ mj ] SILLY EXPLAiN EVOLPROCS (post somewhere on social media explaining something about evolving processes in a silly way)
https://twitter.com/mungojelly/status/517530610706165760
    Mungojelly     ?@mungojelly
Evolving processes are like wheeeeeeeeee ploop and then they're like wookawookawooka zoink shaZAM bloorrp. https://etherpad.fr/p/ZS2OS51hq1  #evolproc
[ mj ] SLEEP (link to this process from some quiet pool somewhere where it can rest for a while until the next time it's needed)
sent to "swirl to sleep" https://docs.google.com/document/d/11PHcAzxDQrBFtCbKKvtqsexLMsUxUbS2NWwc6gIlnRs/edit
[ mj ] SILLY SUGGESTIONS FOR THE MUTATORS (make some silly useless impractical suggestions for how to improve this process, just to help us think creatively)
walk around the block for every other step
put hashtags in front of the process names to make them cooler
make a charity step that just goes to whatever pool is lonliest
[ mj ] SUGGESTIONS FOR THE MUTATORS (make some vague suggestions of how this  process could possibly be improved, just to give the mutators some ideas)
Needs Wake Up after sleep.
Also, one other little thing, find somewhere all the Flow Connection steps and put all of those in a new childcare section also Link Child to Parent please, and applesauce. Never mind about the applesauce?
[ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
I added Wake Up.
I copied in the flow connection creation, also link child to parent and then I wrote a new Archive for it.
And then I put in the flowing steps on either side of Mutate.
There, that wasn't too hard, another strain to populate those new flow pools, phew. :)
[  ] 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!))
[  ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
- ~ - checklist - ~ -
[  ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
[  ] EXPLAIN EVOLVING PROCESSES (post somewhere on social media explaining something about evolving processes)
[  ] SILLY EXPLAiN EVOLPROCS (post somewhere on social media explaining something about evolving processes in a silly way)
[  ] SLEEP (link to this process from some quiet pool somewhere where it can rest for a while until the next time it's needed)
[  ] WAKE UP (write a brief note here as to why you decided to wake up this particular process today)
[   ] SILLY SUGGESTIONS FOR THE MUTATORS (make some silly useless  impractical suggestions for how to improve this process, just to help us  think creatively)
[   ] SUGGESTIONS FOR THE MUTATORS (make some vague suggestions of how  this  process could possibly be improved, just to give the mutators some  ideas)
[  ] FLOW IN FROM FLOW-STYLE PARTNER (consider flowing in a step from this process's flow-style partner process into the clean copy of this checklist below)
[  ] MUTATE (make an improvement or change in the clean copy of this checklist below)
[   ] FLOW OUT TO FLOW-STYLE PARTNER (consider flowing out a step from the clean copy of this checklist below into this process's flow-style partner 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!))
[  ] ARCHIVE (copy the whole text of this document and paste it to http://pastebin.com/ or anywhere else it might persist if this document vanishes)
[  ] LINK CHILD TO PARENT (put a note at the top of this child's document that says "parent:" and a link back here and then "parent archive:" with a link to the new archive)
[  ] ASSOCIATE FLOW-STYLE PARTNER PROCESS WITH CHILD (choose or create a flow-style process to associate with this child, and link to it from the top of this child's document)
[  ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)