HackMD
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • 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
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
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
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # [閒聊] 山難部、社外隊與社外資歷 最近耳聞社上有將某隊轉為社外,或以外掛形式處理的傳聞,私以為有違山難部的核心價值,因此冒著被扣上老人干政的風險,在此對此議題發表淺見,若版主認為不適合再煩請刪文。 ## 山難部 小弟私以為山難部核心價值有二 ### 1.把關隊伍安全 這類即是透過審隊、評估隊伍的風險、把關隊員能力,協助留守、於山難發生時開啟山難搜救機制,乃至於登山安全觀念宣導、教導與培養學弟妹。 ### 2.守護社團永續經營 山難部成員皆是社團核心成員,參與社團多年並為社團付出無數心血。山難部亦是守護社團營運的中流砥柱,是抵擋外界壓力的那道防火牆,提供社團安心發展的空間。 大學登山社畢竟是大學社團,社團營運不止得對社員負責,還得對指導老師、學校,或甚至整個社會負責。這些壓力並不是社團或社員所想要的,但卻是跟著台大這塊招牌一併賦予的。學校得保障學生的安全,得向社會與家長負責,相對的學生組織也得向學校負責。 這個部分的體現,則是表現在山難防治體系的制度化,訂定SOP,與師長與學校建立山難共識,以及對於過大風險的活動予以禁止。 ## 山難與社團永續經營 當今天風平浪靜,沒有人會去管社團是怎麼管理的,是否有按照山難細則出隊,審隊有沒有放水,或是有多少社外隊。但,當山難發生,這當中的每一個環節卻會被放大檢視。 台灣人(還有鄉民)就是有種心態,出事了得找個原因,得找個人責怪。長榮機師染疫,就檢討紐西蘭機師趴趴走,檢討他沒配合疫調。就算破口的成因是航空公司規範的問題,但反正找到一個代罪羔羊風向就全去檢討他。大學山社(尤其台大)更是這樣,只要出事就會開始被檢討是否爬黑山、是否沒申請入山證、是否沒有走學校規定的出隊流程、是否有經過社團的標準程序。 雖然我們可能都知道,山難事件發生的原因跟有沒有審隊沒關係、跟有沒有送公文沒關係,但是審隊、送公文、告知指導老師等等,卻是我們給學校的承諾,是我們跟學校的默契,也是出事時我們最佳的擋箭牌。如果真的不幸發生死亡山難事件,在寫山難報告書時(絕對會被各界要求寫),才能夠告訴大家我們該做的準備都做了,有想到的流程都跑了,出事真的是意外。也是這個默契,社團指導老師才願意為我們發聲,台大秘書開記者會、面對社會質疑時才能說台大山社沒有錯,不需要停止營運,才能指著報告書說出事的原因是什麼,而以後因為什麼原因不會再發生。 山難細則的條例就是這樣來的。每次出事,就把記取的教訓納入細則,讓未來的大家有辦法可依循,不要再犯同樣的錯。 ## 社外隊 台大山社可能覺得只有社內隊伍是社團需管理的,但其實外界不管你的隊伍是社內社外,只看這個人是不是台大學生。這裡最好的案例就是2012成大的烏拉孟山難(sttmountain版搜烏拉孟)。三位OB開隊帶兩位在校生,在校生墜崖亡,最終還是回去檢討成大山協。社內總有聲音說這顯非社內隊伍,但山協還是難以脱責。為什麼這支隊伍沒有走社內程序?沒有審核呈報學校是否只是便宜行事想規避責任? 社外隊伍影響的不是該隊隊員的安全,而是社團永續經營的風險。當山難事件發生在社外隊,社團要如何解釋,要如何脫責,會不會被禁山,要如何告訴自己山社沒有錯可以繼續下去? 就是為了守護**社團的永續經營**,山難部應把可以管理的風險拿到體制下管理,只有顯非台大山社活動,實質上無法管理,且表面上也不會被聯想再一起的,才應該任其自然去出社外隊伍。 這也是為什麼山難部要這麼反對社外隊。 成大山協烏拉孟山難後,決定把社外隊伍常規化。凡社員出社外隊,皆需向山防部與指導老師申請,亦須填寫學校表單切結書交給學校備存。如此,就避掉社外隊對於社團的風險。或許這個做法也適合台大山社,但這需要取得老師與學校課活組的共識,出事他們得願意幫我們背書。 近年來社團風調雨順,平平安安。但或許也就失去了點警戒心。如果感覺不出事情的嚴重性,可去P2版按Home看看,或去看看成大山協2012年初的文章。 PS:小弟私以為,無法撇清責任的隊伍可以下判斷 1. 在校生達1/2 2. 曾以台大山社名義找過學員 3. 在校生主辦且隊伍隊員為山社常見組合 如果覺得開社內隊伍程序太累,那是否應該檢討要減少社內隊伍的程序? ## 社外資歷 近期亦有聽聞領隊不想為社外人士留守,而提出讓其變成"外掛"或"巧遇"的人的隊伍。小弟對此非常反對。"外掛"或"巧遇"的人實質上就會影響這支隊伍。不去審核他,只是眼不見為淨,規避責任而已。 為了把關隊伍安全,山難審核應該是要盡其所能的取得資訊,盡量預期所有風險,然後評估再給建議。不審社外人士卻縱容其跟隨隊伍,違背我們審人員的初衷,說更難聽一點,那學員也可以社外獨攀然後湊巧走同一條路線? 小弟完全能夠理解,不想要為不認識,沒有感情的人做留守。但若要砍掉,就應禁止其一同出隊,不要讓他影響隊伍。 但小弟私以為山社不能太過封閉,在近年各類技術慢慢出現斷層的狀況下,未來會有越來越多可以向社外班底學習的機會。社外班底或許有雪地技術,或許有溯溪技術,或許有不同的勘查見解,小弟覺得都應交流學習。 因此,小弟認為不應直接禁止社外班底審核。若領隊有意願找社外班底一起爬,或加強隊伍結構,小弟則認為應該讓其實質審核。山難部可提出要求看社外班底的出隊紀錄,體訓計畫,亦可從與該社外人士一起攀登過的社員了解該社外人士的登山能力與風格。不過,畢竟社外人士並未參與過台大山社的培訓,與山難部沒有默契,也不知道社上緊急處置與山難處理的方法,在危急時刻會是個不確定因素。因此,社外班底頂多能借助其登山技術,但不能取代社團強力班底或是領隊的角色。 最後,山難部是活的,山難細則或有幾處寫死,但不應為了繞掉細則規範而違背山難部的初衷,違背山難部的核心價值。細則不合宜之處,山難部會議皆可修改override。 期許社團居安思危,戰戰兢兢但不要用到山難處置 共勉之 不應關心社務的老人B

    Import from clipboard

    Paste your markdown or webpage here...

    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 lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    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 Sign in with Wallet
    Wallet ( )
    Connect another wallet

    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

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    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 and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    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.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        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
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

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

        Syncing

        Push failed

        Push successfully