Mungojelly

Untitled

Oct 23rd, 2014
205
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.02 KB | None | 0 0
  1. parent: https://pad.systemli.org/p/c3Po6Upy9bJS
  2. - ~ - checklist - ~ -
  3. [ 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)
  4. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  5. This has been a really tremendously successful family, just because I'm feeling better now about life in general. I'm trying to do too many things at once though. Now that I've moved a lot to google docs I should probably kill a lot of these etherpad threads, or find someplace to sleep them that they could be sensibly resurrected from I guess. It's gotten to the point where I can't keep this whole family around in tab groups, it's beginning to strain that. So I need to rest them somewhere, lists in google docs or something. The thing is that most any list format I can think to store them in is rather a lot of work. Everything wants to be permanent. I want to move things around, I want to take this process and say, welp, done with metaprocess commenting, get out of here, no more mess, move along. But the shape of all these tools is that I'm going to want to make lists of things that are metaprocess commenty, always, that just have that attribute, and no. These are living things whose attributes change as they go along. So I need tools with a sense of space to them, a sense of physics, things you can move and they're moved. Or else I have to bother to delete things from documents and lists when I'm done with them, but that's a backup plan, come on computers, do something for me for once. :/
  6. [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  7. I added Sleep, the fad these days.
  8. [ 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!))
  9. http://notas.dados.gov.br/p/sx5qEXzmi9
  10. [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  11. - ~ - checklist - ~ -
  12. [ 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)
  13. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  14. I feel like I'm such a beginner at this. Once there are advanced processers and I'm one of the most advanced there'll also be beginners and they'll be like I'm now. Spinning up too many processes at once, with no clear idea why. Ahh, processes, how do those work. And don't you tell me to ask a processist. They go and are lying and making me to be pissed. Okiedoke, goodnight process. <3
  15. [ mj ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
  16. sent to "swirl to sleep" https://docs.google.com/document/d/11PHcAzxDQrBFtCbKKvtqsexLMsUxUbS2NWwc6gIlnRs/edit
  17. [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  18. Shit well I don't always have Metaprocess Comment handy, these would be good for that, if they're junky throw-away ideas. I'll triple that, and add Wake Up.
  19. Also I found another random words page for the children's memorable urls. :)
  20. [ 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!))
  21. https://pad.odoo.com/p/g3CAdElf0t
  22. [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  23. - ~ - checklist - ~ -
  24. [ 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)
  25. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  26. Even with just me processing I'm always playing with the strange balance between controlling processes and being controlled by them. Or really it's between being controlled by my past self and controlling my future self. That doesn't really make sense even or does it? Right now I'm doing this step because this is the pool in this tree of pools with the most processes in it. So I'm letting my hand be guided by the shape of them. What feels strange about it I guess is that the shape of them isn't just my conscious plans for them but my uncconscious shaping of them as well and also random magnifications and also, to some extent, slightly, their own real selection. So there's this presence that builds in them. As care is given to them, and as they're selected for survival, they become a place with some meaning and purpose. So then there's something there to have a relationship with, but it's not always an entirely congenial relationship. They quite want to survive, which means shaping a particular attitude towards their pools. Or rather, to turn the usual confusing evolutionary language inside-out, all the pools and processes elsewhere that didn't get my attention don't have these presently compelling qualities. Yay, life.
  27. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  28. When the processes start to seem to have an existence and needs external to myself is when I forget enough, when they go beyond my understanding. I'm trying to give them transparency, some sensible sort of transparency. But being potentially readable isn't even the most important transparency. These ones have no way I can investigate them myself either except reading them and trying to remember what's up with them. The older families when I go to find out what they were up to, there's no way to ask, there's no summaries or sense, there's just you could theoretically read the whole past and then you'd understand the sense of it. But that's no good. That's transparent and open source in the same way all these fucking open source programs are, in this utterly theoretical useless way. So I need some more actually useful way of looking into them, some way you can come upon a process and ask, what's this, what's its context, how do I use it, how do I relate to it, where do I pick it up, what should I expect from it.
  29. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  30. The question really is what am I building here? Am I building processes that are supposed to open up and involve various people in their guts? Or is the idea of this family that I mostly just run them by myself and they have occasional outside connections? It's not clear, and those paths would require very different attitudes towards the transparency of particular parts, wouldn't they? I keep feeling like it is important though for people to have deep access to information about even processes that touch them only slightly. But is anyone interested? Or do they have the energy to read all of this? Perhaps they should try representing themselves some other way than by their entire histories and guts, sigh, but that's another complexity, sigh, sigh, complexity.
  31. [mj ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
  32. https://docs.google.com/document/d/1jWPBJKPKd1pg9kvgX1eoGveuVzuU76ZI-K6qReBBiCY/edit
  33. sent to the new Metaprocess Analysis Sleep Swirl (MASS): https://docs.google.com/document/d/1jWPBJKPKd1pg9kvgX1eoGveuVzuU76ZI-K6qReBBiCY/edit
  34. [ mj ] WAKE UP (write a brief note here about why you decided to wake this particular process up today)
  35. I've been waking up pretty much everything today, still working on filling in all these pools I made, still not having any sense of how many pools is too many. :)
  36. [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  37. I just bothered to put the flow connection stuff into Good Mutations. Okie dokie, so.
  38. I brought in Suggestions for the Mutators from "first flow connection child" since I'm there anyway.
  39. I wrote a new Link Child to Itself wording here.
  40. And I flowed in the flow connection steps. Well I guess that's gotta do it for this generation, roll on my friend.
  41. [ ] 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!))
  42. https://docs.google.com/document/d/1S8xgJszkd_3QvN3P_-P8nqGY45wPdwH9e2YiO4-TEeA/edit
  43. [ mj ] LINK CHILD TO PARENT (at the top of this child's document write "parent:" and then a link back here)
  44. [ ] 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)
  45. [ ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  46. - ~ - checklist - ~ -
  47. [ ] 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)
  48. [ ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  49. [ ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  50. [ ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  51. [ ] SLEEP (link to this process from some quiet pool where it can rest for a while until it's needed)
  52. [ ] WAKE UP (write a brief note here about why you decided to wake this particular process up today)
  53. [ ] SUGGESTIONS FOR THE MUTATORS (make some suggestions of how this process could be improved, to give the mutators some ideas)
  54. [ ] 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)
  55. [ ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  56. [ ] 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)
  57. [ ] 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!))
  58. [ ] LINK CHILD TO PARENT (at the top of this child's document write "parent:" and then a link back here)
  59. [ ] MEMORABLE URL FOR CHILD (use http://muse.dillfrog.com/random_words/ to generate some random words, choose two or three of them to make a unique name for this child, then use http://tinyurl.com/ to make that name into a link to this child's document)
  60. [ ] LINK CHILD TO ITSELF (at the very top of this child's document write its new name, in large type or bold if possible, and then immediately under that its new URL)
  61. [ ] ASSOCIATE FLOW-STYLE PARTNER PROCESS WITH CHILD (choose or create a flow-style process to associate with this child, and link to it near the top of this child's document)
  62. [ ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
Advertisement
Add Comment
Please, Sign In to add comment