Peeragogy Monthly Wrap: 2020-05

Mixtape

1. Portugal. The Man – Feel It Still

“Peeragogy Monthly Wrap” Working Group Meeting Wrap

“Peeragogy Monthly Wrap” Working Group Meeting Wrap: 2020-05-06

Wish list for how people could support for wrap:

• Share with course: where are problems / pain points?
• Get people’s input into wrap itself earlier in month
• Add multiple perspectives on the answer to the “what’s happening” question (coming to concensus sometimes leads to lack of diversity)

Have a Peeragogical Action Review specific repository?

• Make it easier for people to contribute
• Make it more of a data project, like mix tape, so new entries can flow automatically into the wrap for the month?
• Similar to pattern repository?

Future:

• Procedure guides for how people can write and contribute technically
• Source people who get involved
• People writing wraps at other places from where we source them together

Put it somewhere else? Who do we want to read this? Be aware of these practices?

• Archive.org - a leader of it (Carl Malamud) is also a player in open knowledge scene
• Maybe just send someone who we want to read this an email
• Distribution

Add RSS to wrap (using Hypothes.is).

“Peeragogy Monthly Wrap” Working Group Meeting Wrap: 2020-05-20

Patterns

• Create template and repository for patterns
• Pattern template could be used to create cards, games, a catalog, etc.
• Scenario: at an unconference, you could introduce patterns as a tool (not that they necessarily need to be used, more of a toolbox to choose from)
• Make it easier to apply them, like a pattern practice
• Universal tools that can be used on all kinds of patterns
• PAR itself should be a pattern

Why do you need patterns? Answer: They should be used/applied. Patterns for architecture exist for being used in the field (for planning and constructing buildings). Other patterns, for example some textile coloring patterns, may only serve the purpose of being nice to look at.

Roadmap

• General roadmap tool that could be in its own repository so you could see the current situation and future directions
• Every two months a reminder to see if roadmap is outdated?
• Or offering it for mapping if a project doesn’t have a roadmap?
• If you don’t have a methodological or tool way to do this, it’s down to discpline and harder within unstrucutured peer learning scenario

PAR

PAR should have a naming convention so you could have more than one in a month and software would be able to organize them. PARs could flow automatically into wrap. Same with mixtape.

“Peeragogy Monthly Wrap” Working Group Meeting Wrap: 2020-05-27

• How does it make sense for everyone to have their own corona research?
• How can we hope to cure cancer? We don’t have tools.
• Actionism – what happens when people lose interest following an initial excitement about a project?
• Writing up patterns is nice, but how are we using them? What software is using/supporting/implementing them?

Common to create solutions or software but then not openly licensed or behind a pay wall – may provide some advantages to the founders, but how can that help wider community? Is that a bad thing that interest of owners or founders diverge from community? Good thing? Inevitable? What are other approaches?

Made me think of this paper on modular politics: https://docs.google.com/document/d/1c4vp4HQFYHNsFzm4rNo2uh4fU8Gonfu9nJOLpasel5I

Blog post I mentioned that I wrote: https://www.foresee.com/blog/retail-trends-and-recommendations-on-our-way-to-the-next-normal