Mungojelly

Untitled

Oct 14th, 2014
253
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.33 KB | None | 0 0
  1. Welcome to Etherpad!
  2. Thanks! Welcome to this evolving process.
  3. 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!
  4. Get involved with Etherpad at http://etherpad.org
  5. - ~ - checklist - ~ -
  6. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  7. Hmm, interesting, I had a bunch of these building up in my tab mix plus groups, but just now I decided to push them out of there into social media to ask for colors, and just drop them maybe if no one answers. It really is difficult to get any basic little help or feedback, isn't it? I just ask for a random color or anything and I don't get that help quickly because it's nothing, often it doesn't come at all. I wonder if there are any more coherent ways to ask for particular bits of help that I'm missing!? No I don't think so. it's just not very helpful on the web these days. People just help with things for ego. I can't very well ask on Quora "what's a random color?" can I? Maybe I could but it's not what Quora's for, Quora is for boasting that you know something by answering it. Boasts and prancing and no actual help for even the littlest asks, sigh.
  8. Presumably also though if people started to respond to a certain type and character of ask then they'd start to habitually and it'd get easier. I hope? One would hope there'd be some way to get anything done or get any basic information flows started at all. Geez. What should I start over with new social media accounts and have a persona that people engage with for some superficial reason or another!? :/ OK well I'll just keep being persistent and these processes can probably find some crack to grow into somewhere, I'll keep hoping.
  9. [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  10. I added an asychronous Solicit Metaprocess Comments step that asks for comments but doesn't wait on that, it just asks and then continues with the process.
  11. [ 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!))
  12. https://pad.systemli.org/p/c3Po6Upy9bJS
  13. [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  14. - ~ - checklist - ~ -
  15. [ mj ] SOLICIT METAPROCESS COMMENTS (ask somewhere for some comments or feedback on how these processes are going generally -- then continue with this process immediately without waiting for a response -- when or if there happen to be any responses then please paste them here then)
  16. https://plus.google.com/115207639490096731393/posts/CeHNWxqNEKG
  17. Brett WilliamsShared publicly - 2:43 AM
  18. #evolvingprocesses
  19.  
  20. Hello, I'm running this process here https://tihlde.org/etherpad/p/4tKgrdJ12u and it's wondering if anyone has any thoughts or questions about evolving processes generally. This is a mutated version of a process step I've been putting into processes for years in my own pools, called "Metaprocess Comment" for some reason, where I've been talking to myself about the qualities and development of my processes generally. Now I'm opening that conversation up to you. What do you think of evolving processes? What do they seem like to you? #evolvingprocesses ?
  21. Etherpad
  22. tihlde.org
  23. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  24. It just occurred to me more somehow that I have a bootstrapping problem. It wouldn't be difficult at all (very theoretically) to get new processes started in a context where everything's processes. Heck, that's not even how you have to think about it, you can just gently bend and repurpose and fit into the flow of it. But engaging in these existing systems there's a type mismatch. In terms of communication structures it doesn't accord properly, and in terms of people's reaction to it it's like huh? what's this going across at angles? and you can barely see it.
  25. [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  26. I added the good old Recently Active Processes list. IDK why it hadn't occurred to me to put that standard one in this strain, hmm, forgetful.
  27. [ 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!))
  28. https://pad.odoo.com/p/g7OJAmfSqr
  29. [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  30. - ~ - checklist - ~ -
  31. [ mj ] RECENTLY ACTIVE PROCESSES LIST (please lInk to this process at the top of the list of recently active processes at http://piratenpad.de/p/RecentlyActiveProcesses with a brief description of how it's going)
  32. https://tihlde.org/etherpad/p/4tKgrdJ12u - finally added Recently Active Processes back to this still-newish from-scratch strain of simple infinite rollers
  33. [ mj ] SOLICIT METAPROCESS COMMENTS (ask somewhere for some comments or feedback on how these processes are going generally -- then continue with this process immediately without waiting for a response -- when or if there happen to be any responses then please paste them here then)
  34. https://www.facebook.com/mungojelly/posts/10152687670513232
  35. Brett Douglas 'Mungojelly' Williams
  36. Just now ·
  37. I'm writing on behalf of this process here https://tihlde.org/etherpad/p/4tKgrdJ12u which would like to know what you think of evolving processes. Have you heard of them? Have you noticed them? Have you noticed this one? Does this seem familiar?
  38. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  39. My plan now is to swirl them all out of Tab Mix Plus and then back into it, to break that stiffness out of them. I've thought of various sensible ways to do that but the one I thought of just now is to put a Sleep step. That makes sense to me not so much in terms of what's going on here now, but just that's an orderly organized way to go about it, and then from there I could make sense of it and like write the timing of them, where they come out of sleep for certain periods of time in some coherent way. So yeah, sleep. Then I'll put them all to sleep and wake them back up. :)
  40. [ mj ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  41. OK well I put the Sleep step in right before the Mutate, because that seems healthy to me. You get to wake something up and then choose its direction. So it sleeps things ready to spring into action in various directions. Mildly annoying maybe here since I have to cycle through to it. I guess I need to cycle all of these through as much probably to do it all this way. I wonder should I put them all in front of the Mutate steps?? I'm going to play it by ear and see if that's what fits. I'm going to try to put in a Sleep step along with every mutation I do here until they're all swirled into that!
  42. [ 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!))
  43. https://pad.okfn.org/p/16fqcK6lXj
  44. [ mj ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  45. - ~ - checklist - ~ -
  46. [ mj ] RECENTLY ACTIVE PROCESSES LIST (please lInk to this process at the top of the list of recently active processes at http://piratenpad.de/p/RecentlyActiveProcesses with a brief description of how it's going)
  47. https://tihlde.org/etherpad/p/4tKgrdJ12u - going to sleep into the sleep swirl for a while soon after a bit of metaprocess commenting
  48. [ mj ] SOLICIT METAPROCESS COMMENTS (ask somewhere for some comments or feedback on how these processes are going generally -- then continue with this process immediately without waiting for a response -- when or if there happen to be any responses then please paste them here then)
  49. https://www.facebook.com/mungojelly/posts/10152689490258232
  50. Brett Douglas 'Mungojelly' Williams
  51. Just now ·
  52. This https://tihlde.org/etherpad/p/4tKgrdJ12u is a strange annoying repetitive process that's just asking you again what you think about evolving processes. Have you noticed them? Do they seem to exist? Does this post seem to exist? How do you think I should mutate it so it's less annoying?
  53. [ mj ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  54. It's not actually that things don't happen when you do them with evolprocs, it's that they take a moment. You put in a request and send it down the conveyor belt. Heck IDK maybe that's just because it's only me running them. Maybe in the future you could give a suggestion to an active flock of processes and then they could be making it into complicated reality in minutes. Huh, that seems plausible. It works fine even just with me doing them. There's a proposal and then it takes a while to put it together and make it happen. But it's very effective, it thinks about things and accomplishes them. I think it works great.
  55. [ mj ] SLEEP (put this process away in a quiet pool for a while, then wake it when you need it)
  56. sent to "swirl to sleep" https://docs.google.com/document/d/11PHcAzxDQrBFtCbKKvtqsexLMsUxUbS2NWwc6gIlnRs/edit
  57. [ ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  58. I put Check for Comments after Solicit.
  59. I added Wake Up after Sleep.
  60. I added in Link Child to Parent.
  61. I made a new Associate Flow-Style Partner Process with Child step Now it just needs a couple steps to relate to it.
  62. I added Suggestions for the Mutators which seems to have been missing, and also Flow in from Flow-Style Partner.
  63. And finally Flow Out to Flow-Style Partner.
  64. I also made a folder in my bookmarks with three subfolders to pool processes at those three steps. I've been much more cautious these days about adding more pools but I thought this was worth the risk/expense because it seems like a very viable idea for how to build larger structures and it lets me have my cake and flow it too. ;)
  65. [ ] 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!))
  66. [ ] LOOP (copy the clean checklist again below itself so this process can continue in a loop)
  67. - ~ - checklist - ~ -
  68. [ ] RECENTLY ACTIVE PROCESSES LIST (please lInk to this process at the top of the list of recently active processes at http://piratenpad.de/p/RecentlyActiveProcesses with a brief description of how it's going)
  69. [ ] SOLICIT METAPROCESS COMMENTS (ask somewhere for some comments or feedback on how these processes are going generally -- then continue with this process immediately before waiting for a response)
  70. [ ] CHECK FOR COMMENTS (check for any new responses to the earlier posts asking for comments)
  71. [ ] METAPROCESS COMMENT (write some thoughts here about how these processes have been going)
  72. [ ] SLEEP (put this process away in a quiet pool for a while, then wake it when you need it)
  73. [ ] WAKE UP (write a brief note here as to why you decided to wake up this particular process today)
  74. [ ] SUGGESTIONS FOR THE MUTATORS (make some suggestions of how this process could be improved, to give the mutators some ideas)
  75. [ ] 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)
  76. [ ] MUTATE (make an improvement or change in the clean copy of this checklist below)
  77. [ ] 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)
  78. [ ] 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!))
  79. [ ] LINK CHILD TO PARENT (put a note at the top of this child's document that says "parent:" and then a link back here)
  80. [ ] 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)
  81. [ ] 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