HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
      • Create new note
      • Create a note from template
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    Write
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- title: Scrapbook --- ## Scrapbook ### Motivation This pattern describes a way to make the project meaningful. ### Context We have been working together for a while now. We have maintained and revised our pattern catalog, and we are achieving some of the “What’s Next” steps associated with some of the patterns. ### Forces > ![image](images/attention.png) **Attention**: due to limited energy, we need to ask: where should we set the focus? > ![image](images/interest.png) **Interest**: new experiences catch our attention. > ![image](images/meaning.png) **Meaning**: shared history makes things meaningful. ### Problem Not all of the ideas we’ve come up with have proved workable. Not all of the patterns we’ve noticed remain equally relevant. In particular, some patterns no longer lead to concrete next steps. ### Solution In order to maintain focus, is important to “tune” and “prune” the things we give our attention to. We can connect this understanding to any actions undertaken in the project by asking questions like these: > \(1) Review what was supposed to happen. (2) Establish what is > happening/happened. (3) Determine what’s right and wrong with what we > are doing/have done. (4) What did we learn or change? (5) What else > should we change going forward? <span class="citation">\[9\]</span>, > after <span class="citation">\[10\]</span>. Other review processes have been formalized, including the design review in architecture and the postmortem in theater and other teamwork settings <span class="citation">\[7,8\]</span>. The review process may benefit from having an experienced facilitator on board <span class="citation">\[6\]</span>. As current priorities become clearer, we decide where to focus. Anything that isn’t receiving active attention should be moved to a <span><span>Scrapbook</span></span>. This may encompass: - *Retired patterns* that are tabled or completed (no more next steps); - *Proto-patterns* made of problems, issues, and concerns; - *A back-catalog* of publications, reports, or other artifacts. In the Peeragogy project, alongside our patterns we initially maintained a collection of antipatterns (like ‘<span><span>Magical thinking</span></span>’) but the next steps coming from these seemed particularly convoluted and abstract. So, we archived them.[^fn1] problems – without known solutions – right up front in the Introduction to the *Peeragogy Handbook* <span class="citation">\[9\]</span>. Other proto-patterns include ‘<span><span>Onboarding</span></span>’ and ‘<span><span>Don’t quit your day job</span></span>’, which arose in our review of this paper (see “Emergent Roadmap”, below). Our back-catalog includes academic papers <span class="citation">\[14\]</span> and a thesis <span class="citation">\[5\]</span>. Everyone can maintain their own personal <span><span>Scrapbook</span></span> as along with a communal one. Furthermore, you don’t need to limit yourself to *your own* creativity: include interesting ideas from other sources (see <span><span>Reduce, reuse, recycle</span></span>). In some cases a designated <span><span>Wrapper</span></span> may have to do further work to elicit and organize contributions. ### Rationale We want to keep attention focused on the most relevant issues. If a pattern, task, or concern does not lead to concrete “next steps” at the moment, sufficient time for reflection may offer a better understanding, and it may prove useful and actionable in a different context. ### Resolution Judicious use of the <span><span>Scrapbook</span></span> can help focus project participants’ **attention** on current concerns, without losing grasp of items of **interest**. The currently active pattern catalog is leaner and more action-oriented as a result. If the <span><span>Roadmap</span></span> shows where we’re going, it is the <span><span>Scrapbook</span></span> that shows most clearly where we’ve been, and collects the observations that are most **meaningful** to us. ### Example 1 The history of the Wikimedia Foundation, and of Wikipedia, are maintained as wiki pages.[^fn2]<sup>,</sup>[^fn3] Wikipedia details outstanding issues, in the form of critiques.[^fn4] available to help facilitate the process of vetting proposed fine-grained changes to articles.[^fn5]<sup>,</sup>[^fn6] typically discussed at the Village Pump, and there are mechanisms in place for settling disputes.[^7^]<sup>,</sup>[^fn8] ![image](images/ChristsPieces.jpg) *Park: Christ’s Pieces, Cambridge, UK* ### Example 2 Just as a university campus grows and changes over time, future peeragogues will be drawn to new problems and patterns. They will trace new paths and build new emergent structures (Figure \[christs-pieces\]). ### What’s Next in the Peeragogy Project After pruning back our pattern catalog, we want it to grow again: new patterns are needed. One strategy would be to turn the whole *Peeragogy Handbook* into design patterns. ### References 1. J Corneli, A Keune, A Lyons, and CJ Danoff. 2013. Peeragogy in Action. In *The Open Book*, Kaitlyn Braybrooke, Jussi Nissilä and Timo Vuorikivi (eds.). The Finnish Institute, London, 80–87. 2. J. Corneli. 2012. Paragogical praxis. *E-Learning and Digital Media* 9, 3: 267–272. Retrieved from <http://paragogy.net/ParagogicalPraxisPaper> 3. J. Corneli and C.J. Danoff. 2011. Paragogy. *Proceedings of the 6th Open Knowledge Conference*. Retrieved from <http://ceur-ws.org/Vol-739/paper+5.pdf> 4. Joseph Corneli, Dorota Marciniak, Charles Jeffrey Danoff, et al. 2014. Building the Peeragogy Accelerator. *Proceedings of OER14: Building communities of open practice*. Retrieved from <http://metameso.org/~joe/docs/Building_the_Peeragogy_Accelerator.pdf> 5. Joseph Corneli. 2014. Peer produced peer learning: A mathematics case study. Retrieved from <http://oro.open.ac.uk/40775/> 6. Richard P Gabriel. 2002. *Writer’s Workshops and the Work of Making Things: Patterns, Poetry.* Addison-Wesley Longman Publishing Co., Inc. 7. Norman Kerth. 2001. *Project retrospectives: A handbook for team reviews*. Dorset House. 8. John Mathers, Sue Illman, Angela Brady, and Peter Geraghty. 2013. Design Review: Principles and Practice. Retrieved from <http://www.rtpi.org.uk/media/11214/dc_cabe_design_review_13_w__1_.pdf> 9. H. Rheingold and others. 2015. *The Peeragogy Handbook*. PubDomEd/Pierce Press, Chicago, IL./Somerville, MA. Retrieved from <http://peeragogy.org> 10. US Army. 1993. A Leader’s Guide to After-Action Reviews (TC 25-20). Retrieved from <http://www.au.af.mil/au/awc/awcgate/army/tc_25-20/tc25-20.pdf> ------------------------------------------------------------------------ [^fn1]: <http://paragogy.net/Scrapbook> [^fn2]: <https://wikimediafoundation.org/wiki/History_of_the_Wikimedia_Foundation> [^fn3]: <https://en.wikipedia.org/wiki/Wikipedia> [^fn4]: <https://en.wikipedia.org/wiki/Criticism_of_Wikipedia> [^fn5]: <https://en.wikipedia.org/wiki/Special:RecentChanges> [^fn6]: <https://en.wikipedia.org/wiki/Wikipedia:Recent_changes_patrol#Tools> [^fn7]: <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(policy)> [^fn8]: <https://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment>

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully