我剛讀到一篇關於僅對專案部分內容進行 S/R（傳送/接收）可能性的不同文章。
（部分傳送/接收的可能性 - sflint 的第 3 點）
我理解 james_post 提到的問題，即人們容易忘記上傳整個專案。
然而，我認為增加「傳送」和「接收」按鈕會很有益處。
團隊經常一起編輯一本書（透過面對面或視訊會議）。為了確保每個人都有最新版本，整個團隊必須定期進行兩輪 S/R。第一輪實際上只是傳送。第二輪實際上只是接收。
如果我們能建立這些按鈕該怎麼辦？
「僅傳送」
功能：
僅傳送專案。傳送後五分鐘內，如果使用者未提前啟動，它也會自動接收。
「僅接收」
功能：
僅接收專案。但如果專案在過去五分鐘內未傳送，則執行常規的傳送和接收。
每個人先點擊「僅傳送」。完成後，他們都點擊「僅接收」。
這可以為團隊節省大量等待時間，並減少伺服器負擔。
當然，缺點是會增加額外的複雜性和所需的額外培訓。
這只是我想了很久的一個想法！我理解這可能不切實際，但還是想分享出來。
I just read a different about the possiblity of doing S/R of just part of a project.
(Partial send/receive possibility - #3 by sflint)
I understand the issues james_post mentions with people forgetting to upload their entire project.
However, I have thought that it would be beneficial to have additional “send” and “receive” buttons.
Oftentimes a team is editing a book together (in person or via videocall). In order to ensure everyone had the most up-to-date version, the entire team must periodically do two rounds of S/R. The first round is really just to send. The second round is really just to receive.
What if these buttons could be created?
“Just Send”
Function:
Just sends the project. Five minutes after sending it will also receive, if not initiated sooner by the user.
“Just Receive”
Function:
Just receive the project. But if the project hasn’t been sent within the last five minutes, do a regular send and receive.
Everyone would hit “Just Send” first. Once that is done, they all hit “Just Receive.”
This could save teams a lot of waiting time and reduce burdens on the servers.
Of course, a disadvantage would be the extra complexity and extra training needed.
Just an idea I’ve had for a while! I understand it might not be practical, but wanted to share it anyway.
機器翻譯自 English
