Repkironca
    • 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
      • Invitee
    • 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
    • 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 Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync 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
Invitee
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
# 2023 建景送舊檢討 aka Repkironca 碎碎念統整 --- ## Discord 伺服器 ### 頻道太亂,很多頻道沒有意義,命名讓人不知所以 舉例而言,``活動計畫``、``執行細項``之類的東西,實際上並沒有什麼作用,打從一開始的定位就很奇怪 我其實心中大概有一套理想的伺服器架構,但我覺得講出來限制你們也沒什麼意義。不過有幾個算必備的元素,之後肯定會用到,我稍微列舉一下就好 - 報帳區 主要是錢分散在四校,常常需要以私人名義先墊,再拿公款下去補的情況。另外開個頻道讓他們拍發票上來,總務在算錢時也不會有爭議 - 質詢區 白話叫 ``問執秘問題區``,隨著活動規模擴大,一定會常常有工人想提出自己的想法,或溝通上有待釐清之處。然而大量私訊會造成混亂,且一不小心就會有資訊不對等的狀況發生。既然如此乾脆開個全員都看得到的地方處理此情況就好 - 會議紀錄 這邊的會議紀錄是指,你已經打在 ``HackMD``、``Notion``、``google document``,或任何你習慣的平台上,而且有放在雲端或 notion 中,最後為了方便把連結傳上來。請不要直接把紀錄打在這邊,超亂 - 回報區 用最白話的方法講,請每一組工作做完後回報在這邊。不用多打什麼,只要寫出哪一組的什麼東西做完,如果(通常會有)有文件順便附上來。除非有執秘會靈媒,有辦法通靈出大家進度,否則強烈建議創這東西讓他們主動講,這樣 check 死線也比較方便 ### 討論區依據組別分開 對,不然之後會亂到哭出來 ### 不要濫用 ``@Everyone``,也不要都不 tag 人 ``@Everyone`` 的使用時機是這樣的。假設現在是你要開會、會議記錄出來了、開投票、緊急通知等等,你需要全體工人注意的時機,那可以直接在公告 tag 沒差。反之,假設你只想通知景資的,或可能要抓保險組出來,標記所有人就顯得很煩躁 ### 公告 我其實會建議直接把發言權鎖到執秘 only,可能多個小組負責人。確實,可能會有需要根據公告內容繼續討論的情況,此時 discord 的討論串是個好東西,既不會占用公告空間洗版也能達到效果 ## 執秘 ### 分工 你們這次的分工方式比較像,東西擺在這邊你們大家自己認領,其實頗糟的。我枚舉一下自己看過的方式,如果你們想要創新當然更好哇 - 籌會中當場分工 通常是零籌。零籌前執秘先把所有工作列出來,加上一些說明之類。零籌的其中一個程序就是分工,當場找好組員選負責人。效率最高且最無爭議,缺點是沒來籌會的很難搞,你們要想辦法 - 調查表單(志願制) 請每個人把自己想做的工作案意願排序,再由執秘分完後公布。好處是執秘的操作空間比較大,可以排除不適任者(有些人就是特別有自信 you know)。壞處嗎...你永遠找不到完美的分工方式,能者多勞能者過勞死,然後會有人你不知道要怎麼放,最後錄取到志願序超低的工作 - 調查表單(自願制) 請每個人利用單選的方式,先選出兩個自己願意去的組別。選完兩個後會出現邏輯閘,問填表人是否願意再多接比常人分量多的工作。好處是願意做事的人有發揮空間,且絕對出於自願。壞處是可能出現一個人都招不到的組別 - Discord 表符 搭配 reaction roles 使用,可能籌會開完放出來讓他們按。好處是簡單方便,壞處在於先搶先贏並不保證其合理性與適任性 ### 執秘沒有訂死線,更沒有催死線 不是喔呱,其實死線在零籌就該一次性訂完了。就是你們做事要有個規劃,什麼時候要達到什麼樣的進度。而且之後你們活動還會跨越段考等等的活動,沒有規劃最後是很難趕出理想品質的 至於催死線,延續上文的 ``工作回報區``,如果死線到了你沒看到東西,顯然要繼續去追殺對吧:)否則死線形同虛設 ### 籌會日期 我自己決定籌會日期的方式為,先確定執秘夥伴們都能出席,接下來才發投票出去給他們。當然這還會受到一些因素影響,例如 **會議重點對象** 是否有辦法到等等 ### 報名 以你們這次報名的開放日程,放到暑訓大概會有 5 個小隊員。你們之後的報名者可能是外校、甚至北北基國三生喔。算上他們轉帳繳費、正取備取等等的時間,報名最好可以開放一個月左右 不需要多完整的資訊,資訊你可以慢慢補,甚至能拿來在 IG 跟大家互動。重點只有時間地點,以及繳多少錢。上面這些零籌,最晚一籌,就差不多該出來了 ## 籌會 ### 籌會跟小組討論是兩回事 小組討論的話,只要聚集起小組內人員就好,幹嘛大費周章聚集全員?好不容易把所有工人齊聚,通常籌會要做的事情有 - 統一事項宣布:執秘要排細流、排活動人力之類的 - 進度確認:簡單提醒一下就好,其實最主要是,沒做完的要跟他討論死線怎麼處理 - 共同討論與投票:舉例而言,你們活動要收多少錢,你們寒暑訓的舞組要怎麼搞,你們茶會的夜遊要去哪裡,這種屬於全體範疇的事情 ### 籌會要先預告 ### 執秘會議前要先訂完並公布會議大綱 就是,你得先想好在這段寶貴時間內,到底要做什麼東西。到時候照著這張大鋼走,可以有臨時動議,但不是想到什麼講什麼 ### 籌會頻率 承上,籌會要坐的那些事情,很明顯不是天天都有的。一個正式活動大概會有 ``零、一、二、三`` 共四場籌會,要增減也可以,但每週兩次真的太誇張。大家做事也都要時間,不要為了開會而開會 ## 工人 ### **看!訊!息!!!!!!!!** 不多解釋了 ### 想好自己的定位,避免說出"自己什麼都可以做" 太沒主見有時反而是壞事,多分享自己的想法吧。隨遇而安也要看時機,造成他人困擾不太好 ### 表單中記得放收費管道與方式 這次我還沒有看到。順帶一提,之後幾個活動比較麻煩,尤其茶會通常是現場繳費,而暑訓是匯款。在錢進來前會拿社費先墊,此時超級容易混亂,絕對要好好紀錄此時的金流動向,否則之後便無法回頭了 OAO ### 飲食調查問不夠細 舉例來說,不吃牛不吃豬不吃香菜怕辣怕酸怕油,血糖控制之類有的沒的,都會搞爆只問葷素的調查 ### 開社帳創雲端/notion 你們之後會看到成電,他們學長是 notion 控,我猜感染到成楓了。總之開一個社團的 Google 帳號,為所有幹部共有,密碼放在自己的社內群組。舉凡之後要跟學弟妹往來,或辦活動之類,都使用這個帳號 雲端的意義則在於,所有人都能把東西放在那邊。除了自己人要找資訊方便之外,等明年你們爬到我這個位置要做傳承時,就能整盤托出去給他們了。你們也覺得從零開始通靈活動怎麼辦很痛苦吧,那可以用此制度,同時帶給自己跟下一屆方便

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