mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
commit
0b6335a530
@ -0,0 +1,106 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11835-1.html)
|
||||
[#]: subject: (Get started with this open source to-do list manager)
|
||||
[#]: via: (https://opensource.com/article/20/1/open-source-to-do-list)
|
||||
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
|
||||
|
||||
开始使用开源待办事项清单管理器
|
||||
======
|
||||
|
||||
> 待办事项清单是跟踪任务列表的强大方法。在我们的 20 个使用开源提升生产力的系列的第七篇文章中了解如何使用它。
|
||||
|
||||
|
||||
|
||||
去年，我在 19 天里给你介绍了 19 个新（对你而言）的生产力工具。今年，我换了一种方式：使用你在使用或者还没使用的工具，构建一个使你可以在新一年更加高效的环境。
|
||||
|
||||
### 使用 todo 跟踪任务
|
||||
|
||||
任务管理和待办事项清单是我非常喜欢0的东西。我是一位生产效率的狂热粉丝（以至于我为此做了一个[播客][2]），我尝试了各种不同的应用。我甚至为此[做了演讲][3]并[写了些文章][4]。因此，当我谈到提高工作效率时，肯定会出现任务管理和待办事项清单工具。
|
||||
|
||||
![Getting fancy with Todo.txt][5]
|
||||
|
||||
说实话，由于简单、跨平台且易于同步，用 [todo.txt][6] 肯定不会错。它是我不断反复提到的两个待办事项清单以及任务管理应用之一（另一个是 [Org 模式][7]）。让我反复使用它的原因是它简单、可移植、易于理解，并且有许多很好的附加组件，并且当一台机器有附加组件，而另一台没有，也不会破坏它。由于它是一个 Bash shell 脚本，我还没发现一个无法支持它的系统。
|
||||
|
||||
#### 设置 todo.txt
|
||||
|
||||
首先，你需要安装基本 shell 脚本并将默认配置文件复制到 `~/.todo` 目录：
|
||||
|
||||
```
|
||||
git clone https://github.com/todotxt/todo.txt-cli.git
|
||||
cd todo.txt-cli
|
||||
make
|
||||
sudo make install
|
||||
mkdir ~/.todo
|
||||
cp todo.cfg ~/.todo/config
|
||||
```
|
||||
|
||||
接下来，设置配置文件。一般，我想取消对颜色设置的注释，但必须马上设置的是 `TODO_DIR` 变量：
|
||||
|
||||
```
|
||||
export TODO_DIR="$HOME/.todo"
|
||||
```
|
||||
|
||||
#### 添加待办事件
|
||||
|
||||
要添加第一个待办事件，只需输入 `todo.sh add <NewTodo>` 就能添加。这还将在 `$HOME/.todo/` 中创建三个文件：`todo.txt`、`done.txt` 和 `reports.txt`。
|
||||
|
||||
添加几个项目后，运行 `todo.sh ls` 查看你的待办事项。
|
||||
|
||||
![Basic todo.txt list][8]
|
||||
|
||||
#### 管理任务
|
||||
|
||||
你可以通过给项目设置优先级来稍微改善它。要向项目添加优先级，运行 `todo.sh pri # A`。数字是列表中任务的数量，而字母 `A` 是优先级。你可以将优先级设置为从 A 到 Z，因为这是它的排序方式。
|
||||
|
||||
要完成任务，运行 `todo.sh do #` 来标记项目已完成并将它移动到 `done.txt`。运行 `todo.sh report` 会向 `report.txt` 写入已完成和未完成项的数量。
|
||||
|
||||
所有这三个文件的格式都有详细的说明，因此你可以使用你的文本编辑器修改。`todo.txt` 的基本格式是：
|
||||
|
||||
```
|
||||
(Priority) YYYY-MM-DD Task
|
||||
```
|
||||
|
||||
该日期表示任务的到期日期（如果已设置）。手动编辑文件时，只需在任务前面加一个 `x` 来标记为已完成。运行 `todo.sh archive` 会将这些项目移动到 `done.txt`，你可以编辑该文本文件，并在有时间时将已完成的项目归档。
|
||||
|
||||
#### 设置重复任务
|
||||
|
||||
我有很多重复的任务，我需要以每天/周/月来计划。
|
||||
|
||||
![Recurring tasks with the ice_recur add-on][9]
|
||||
|
||||
这就是 `todo.txt` 的灵活性所在。通过在 `~/.todo.actions.d/` 中使用[附加组件][10]，你可以添加命令并扩展基本 `todo.sh` 的功能。附加组件基本上是实现特定命令的脚本。对于重复执行的任务，插件 [ice_recur][11] 应该符合要求。按照其页面上的说明操作，你可以设置任务以非常灵活的方式重复执行。
|
||||
|
||||
![Todour on MacOS][12]
|
||||
|
||||
在该[附加组件目录][10]中有很多附加组件，包括同步到某些云服务，也有链接到桌面或移动端应用的组件，这样你可以随时看到待办列表。
|
||||
|
||||
我只是简单介绍了这个代办事项清单功能，请花点时间深入了解这个工具的强大！它确实可以帮助我每天完成任务。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/1/open-source-to-do-list
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/checklist_todo_clock_time_team.png?itok=1z528Q0y (Team checklist)
|
||||
[2]: https://productivityalchemy.com/
|
||||
[3]: https://www.slideshare.net/AllThingsOpen/getting-to-done-on-the-command-line
|
||||
[4]: https://opensource.com/article/18/2/getting-to-done-agile-linux-command-line
|
||||
[5]: https://opensource.com/sites/default/files/uploads/productivity_7-1.png
|
||||
[6]: http://todotxt.org/
|
||||
[7]: https://orgmode.org/
|
||||
[8]: https://opensource.com/sites/default/files/uploads/productivity_7-2.png (Basic todo.txt list)
|
||||
[9]: https://opensource.com/sites/default/files/uploads/productivity_7-3.png (Recurring tasks with the ice_recur add-on)
|
||||
[10]: https://github.com/todotxt/todo.txt-cli/wiki/Todo.sh-Add-on-Directory
|
||||
[11]: https://github.com/rlpowell/todo-text-stuff
|
||||
[12]: https://opensource.com/sites/default/files/uploads/productivity_7-4.png (Todour on MacOS)
|
||||
@ -0,0 +1,71 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (NSA cloud advice, Facebook open source year in review, and more industry trends)
|
||||
[#]: via: (https://opensource.com/article/20/1/nsa-facebook-more-industry-trends)
|
||||
[#]: author: (Tim Hildred https://opensource.com/users/thildred)
|
||||
|
||||
NSA cloud advice, Facebook open source year in review, and more industry trends
|
||||
======
|
||||
A weekly look at open source community and industry trends.
|
||||
![Person standing in front of a giant computer screen with numbers, data][1]
|
||||
|
||||
As part of my role as a senior product marketing manager at an enterprise software company with an open source development model, I publish a regular update about open source community, market, and industry trends for product marketers, managers, and other influencers. Here are five of my and their favorite articles from that update.
|
||||
|
||||
## [Facebook open source year in review][2]
|
||||
|
||||
> Last year was a busy one for our [open source][3] engineers. In 2019 we released 170 new open source projects, bringing our portfolio to a total of 579 [active repositories][3]. While it’s important for our internal engineers to contribute to these projects (and they certainly do — with more than 82,000 commits this year), we are also incredibly grateful for the massive support from external contributors. Approximately 2,500 external contributors committed more than 32,000 changes. In addition to these contributions, nearly 93,000 new people starred our projects this year, growing the most important component of any open source project — the community! Facebook Open Source would not be here without your contributions, so we want to thank you for your participation in 2019.
|
||||
|
||||
**The impact**: Facebook got ~33% more changes than they would have had they decided to develop these as closed projects. Organizations addressing similar challenges got an 82,000-commit boost in exchange. What a clear illustration of the business impact of open source development.
|
||||
|
||||
## [Cloud advice from the NSA][4]
|
||||
|
||||
> This document divides cloud vulnerabilities into four classes (misconfiguration, poor access control, shared tenancy vulnerabilities, and supply chain vulnerabilities) that encompass the vast majority of known vulnerabilities. Cloud customers have a critical role in mitigating misconfiguration and poor access control, but can also take actions to protect cloud resources from the exploitation of shared tenancy and supply chain vulnerabilities. Descriptions of each vulnerability class along with the most effective mitigations are provided to help organizations lock down their cloud resources. By taking a risk-based approach to cloud adoption, organizations can securely benefit from the cloud’s extensive capabilities.
|
||||
|
||||
**The impact**: The Fear, Uncertainty, and Doubt (FUD) that has been associated with cloud adoption is being debunked more all the time. None other then the US Department of Defense has done a lot of the thinking so you don't have to, and there is a good chance that their concerns are at least as dire as yours are.
|
||||
|
||||
## [With Kubernetes, China Minsheng Bank transformed its legacy applications][5]
|
||||
|
||||
> But all of CMBC’s legacy applications—for example, the core banking system, payment systems, and channel systems—were written in C and Java, using traditional architecture. “We wanted to do distributed applications because in the past we used VMs in our own data center, and that was quite expensive and with low resource utilization rate,” says Zhang. “Our biggest challenge is how to make our traditional legacy applications adaptable to the cloud native environment.” So far, around 20 applications are running in production on the Kubernetes platform, and 30 new applications are in active development to adopt the Kubernetes platform.
|
||||
|
||||
**The impact**: This illustrates nicely the challenges and opportunities facing businesses in a competitive environment, and suggests a common adoption pattern. Do new stuff the new way, and move the old stuff as it makes sense.
|
||||
|
||||
## [The '5 Rs' of the move to cloud native: Re-platform, re-host, re-factor, replace, retire][6]
|
||||
|
||||
> The bottom line is that telcos and service providers will go cloud native when it is cheaper for them to migrate to the cloud and pay cloud costs than it is to remain in the data centre. That time is now and by adhering to the "5 Rs" of the move to cloud native, Re-platform, Re-host, Re-factor, Replace and/or Retire, the path is open, clearly marked and the goal eminently achievable.
|
||||
|
||||
**The impact**: Cloud-native is basically used as a synonym for open source in this interview; there is no other type of technology that will deliver the same lift.
|
||||
|
||||
## [Fedora CoreOS out of preview][7]
|
||||
|
||||
> Fedora CoreOS is a new Fedora Edition built specifically for running containerized workloads securely and at scale. It’s the successor to both [Fedora Atomic Host][8] and [CoreOS Container Linux][9] and is part of our effort to explore new ways of assembling and updating an OS. Fedora CoreOS combines the provisioning tools and automatic update model of Container Linux with the packaging technology, OCI support, and SELinux security of Atomic Host. For more on the Fedora CoreOS philosophy, goals, and design, see the [announcement of the preview release][10].
|
||||
|
||||
**The impact**: Collapsing these two branches of the Linux family tree into one another moves the state of the art forward for everyone (once you get through the migration).
|
||||
|
||||
_I hope you enjoyed this list of what stood out to me from last week and come back next Monday for more open source community, market, and industry trends._
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/1/nsa-facebook-more-industry-trends
|
||||
|
||||
作者：[Tim Hildred][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/thildred
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/data_metrics_analytics_desktop_laptop.png?itok=9QXd7AUr (Person standing in front of a giant computer screen with numbers, data)
|
||||
[2]: https://opensource.com/article/20/1/hybrid-developer-future-industry-trends
|
||||
[3]: https://opensource.facebook.com/
|
||||
[4]: https://media.defense.gov/2020/Jan/22/2002237484/-1/-1/0/CSI-MITIGATING-CLOUD-VULNERABILITIES_20200121.PDF
|
||||
[5]: https://www.cncf.io/blog/2020/01/23/with-kubernetes-china-minsheng-bank-transformed-its-legacy-applications-and-moved-into-ai-blockchain-and-big-data/
|
||||
[6]: https://www.telecomtv.com/content/cloud-native/the-5-rs-of-the-move-to-cloud-native-re-platform-re-host-re-factor-replace-retire-37473/
|
||||
[7]: https://fedoramagazine.org/fedora-coreos-out-of-preview/
|
||||
[8]: https://www.projectatomic.io/
|
||||
[9]: https://coreos.com/os/docs/latest/
|
||||
[10]: https://fedoramagazine.org/introducing-fedora-coreos/
|
||||
@ -1,109 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (One open source chat tool to rule them all)
|
||||
[#]: via: (https://opensource.com/article/20/1/open-source-chat-tool)
|
||||
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
|
||||
|
||||
One open source chat tool to rule them all
|
||||
======
|
||||
BitlBee brings multiple chat applications into a single interface. Find
|
||||
out how to set up and use BitlBee in the ninth in our series on 20 ways
|
||||
to be more productive with open source in 2020.
|
||||
![Person using a laptop][1]
|
||||
|
||||
Last year, I brought you 19 days of new (to you) productivity tools for 2019. This year, I'm taking a different approach: building an environment that will allow you to be more productive in the new year, using tools you may or may not already be using.
|
||||
|
||||
### Bring all your chats into one interface with BitlBee
|
||||
|
||||
Instant messaging and chat have become a staple of the online world. And if you are like me, you probably have about five or six different apps running to talk to your friends, co-workers, and others. It really is a pain to keep up with it all. Thankfully, you can use one app (OK, two apps) to consolidate a lot of those chats into a single point.
|
||||
|
||||
![BitlBee on XChat][2]
|
||||
|
||||
[BitlBee][3] is an application that you run as a service that can bridge a standard IRC client with a whole bunch of messaging services. And since it is essentially an IRC server, you have a wealth of clients to choose from.
|
||||
|
||||
BitlBee is included with almost all Linux distributions. Installing on Ubuntu (my Linux desktop of choice) goes something like this:
|
||||
|
||||
|
||||
```
|
||||
`sudo apt install bitlbee-libpurple`
|
||||
```
|
||||
|
||||
On other distributions, the name of the package may be slightly different, but a search for _bitlbee_ should reveal your options.
|
||||
|
||||
You'll notice I use the libpurple version of BitlBee. This version allows me to use all the protocols available in the [libpurple][4] instant messaging library, which was originally developed for [Pidgin][5].
|
||||
|
||||
Once the package is installed, the service should start automatically. Now, using an IRC client ([XChat][6] in these pictures), I can connect to the service on port 6667 (the standard IRC port).
|
||||
|
||||
![Initial BitlBee connection][7]
|
||||
|
||||
You will be automatically connected to the control channel **&bitlbee**. This channel is unique to you—every person gets their own on multi-user systems. This is where you can configure the services.
|
||||
|
||||
The full documentation is available at any time by typing **help** in the control channel. Explore here, then register an account on the server with the **register** command.
|
||||
|
||||
|
||||
```
|
||||
`register <mypassword>`
|
||||
```
|
||||
|
||||
Now, any configuration changes you make on the server—IM accounts, settings, etc.—will be saved when you type **save**. Whenever you connect, use **identify <mypassword>** to connect to your account and load all those settings.
|
||||
|
||||
![purple settings][8]
|
||||
|
||||
The command **help purple** will show you all the available protocols that libpurple provides. For example, I've installed the [**telegram-purple**][9] package, which adds the ability to connect to Telegram. I can add an account by using my phone number with the **account add** command.
|
||||
|
||||
|
||||
```
|
||||
`account add telegram +15555555`
|
||||
```
|
||||
|
||||
BitlBee will show that it has added the account. You can list your accounts with **account list**. Since I only have one account, I can log into it with **account 0 on**, and it will go through the Telegram login process, list all my friends and chats, and I am good to go.
|
||||
|
||||
But what about Slack, one of the most common chat systems out there? Well, you can install the [**slack-libpurple**][10] plugin, and do the same for Slack. If you aren't comfortable compiling and installing things, this may not be for you.
|
||||
|
||||
Follow the instructions on the plugin page, and after you have installed it, restart the BitlBee service. Now when you run **help purple**, Slack should be listed. Adding a Slack account happens the same as with all the other protocols.
|
||||
|
||||
|
||||
```
|
||||
account add slack [ksonney@myslack.slack.com][11]
|
||||
account 1 set password my_legcay_API_token
|
||||
account 1 on
|
||||
```
|
||||
|
||||
And what do you know? You're connected to Slack, and you can add the Slack channels you're interested in with the **chat add** command. For example:
|
||||
|
||||
|
||||
```
|
||||
`chat add 1 happyparty`
|
||||
```
|
||||
|
||||
adds the Slack channel happyparty as the local channel #happyparty. You can use the standard IRC **/join** command to access the channel now. Pretty cool.
|
||||
|
||||
BitlBee and an IRC client help me keep (most of) my chats and instant messages in a single place and reduces my distractions because I no longer have to find and switch to whichever app just pinged me.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/1/open-source-chat-tool
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/laptop_screen_desk_work_chat_text.png?itok=UXqIDRDD (Person using a laptop)
|
||||
[2]: https://opensource.com/sites/default/files/uploads/productivity_9-1.png (BitlBee on XChat)
|
||||
[3]: https://www.bitlbee.org/
|
||||
[4]: https://developer.pidgin.im/wiki/WhatIsLibpurple
|
||||
[5]: http://pidgin.im/
|
||||
[6]: http://xchat.org/
|
||||
[7]: https://opensource.com/sites/default/files/uploads/productivity_9-2.png (Initial BitlBee connection)
|
||||
[8]: https://opensource.com/sites/default/files/uploads/productivity_9-3.png (purple settings)
|
||||
[9]: https://github.com/majn/telegram-purple
|
||||
[10]: https://github.com/dylex/slack-libpurple
|
||||
[11]: mailto:ksonney@myslack.slack.com
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -1,107 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Get started with this open source to-do list manager)
|
||||
[#]: via: (https://opensource.com/article/20/1/open-source-to-do-list)
|
||||
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
|
||||
|
||||
开始使用开源待办清单管理器
|
||||
======
|
||||
Todo 是跟踪任务列表的强大方法。在我们的 20 个使用开源提升生产力的系列的第七篇文章中了解如何使用它。
|
||||
![Team checklist][1]
|
||||
|
||||
去年，我在 19 天里给你介绍了 19 个新（对你而言）的生产力工具。今年，我换了一种方式：使用你在使用或者还没使用的工具，构建一个使你可以在新一年更加高效的环境。
|
||||
|
||||
### 使用 todo 跟踪任务
|
||||
|
||||
任务和待办事项列表离我很近。我是生产力的狂热粉丝（以至于我为此做了一个[播客][2]），我尝试了各种不同的应用。我甚至为此[做了演讲][3]并[写了些文章][4]。因此，当我谈到提高工作效率时，肯定会出现任务和待办事项清单工具。
|
||||
|
||||
![Getting fancy with Todo.txt][5]
|
||||
|
||||
说实话，由于简单、跨平台且易于同步，你用 [todo.txt][6] 不会错。它是两个我经常使用的待办列表以及任务管理应用之一（另一个是 [Org mode][7]）。让我继续使用它的原因它简单、便携、易于理解，并且有许多很好的附加组件，并且当一台机器有附加组件，而另一台没有，也不会破坏程序。由于它是一个 Bash shell 脚本，我还没发现一个无法支持它的系统。
|
||||
|
||||
#### 设置 todo.txt
|
||||
|
||||
首先，你需要安装基本 shell 脚本并将默认配置文件复制到 **~/.todo** 目录：
|
||||
|
||||
|
||||
```
|
||||
git clone <https://github.com/todotxt/todo.txt-cli.git>
|
||||
cd todo.txt-cli
|
||||
make
|
||||
sudo make install
|
||||
mkdir ~/.todo
|
||||
cp todo.cfg ~/.todo/config
|
||||
```
|
||||
|
||||
接下来，设置配置文件。此时，我想取消注释颜色设置，但必须马上设置的是 **TODO_DIR** 变量：
|
||||
|
||||
|
||||
```
|
||||
`export TODO_DIR="$HOME/.todo"`
|
||||
```
|
||||
|
||||
#### 添加待办事件
|
||||
|
||||
要添加第一个待办事件，只需输入 **todo.sh add <NewTodo>** 就能添加。这还将在 **$HOME/.todo/** 中创建三个文件：todo.txt、todo.txt 和 reports.txt。
|
||||
|
||||
添加几个项目后，运行 **todo.sh ls** 查看你的待办事项。
|
||||
|
||||
![Basic todo.txt list][8]
|
||||
|
||||
#### 管理任务
|
||||
|
||||
你可以通过给项目设置优先级来稍微改善它。要向项目添加优先级，运行 **todo.sh pri # A**。数字是列表中任务的数量，而字母 ”A“ 是优先级。你可以将优先级设置为从 A 到 Z，因为这是它的排序方式。
|
||||
|
||||
要完成任务，运行**todo.sh do #** 来标记项目已完成，并将项目移动到 done.txt。运行 **todo.sh report** 会向 report.txt 写入已完成和未完成项的数量。
|
||||
|
||||
所有三个文件的格式都有详细记录，因此你可以选择自己的文本编辑器修改。todo.txt 的基本格式是：
|
||||
|
||||
|
||||
```
|
||||
`(Priority) YYYY-MM-DD Task`
|
||||
```
|
||||
|
||||
如果设置了任务，那么日期表示任务的到期日期。手动编辑文件时，只需在任务前面加一个 ”x“ 来标记为已完成。运行 **todo.sh archive** 会将这些项目移动到 done.txt，你可以在该文本文件编辑，并在有时间时将已完成的项目归档。
|
||||
|
||||
#### 设置重复任务
|
||||
|
||||
我有很多重复任务，我需要以每天/周/月来计划。
|
||||
|
||||
![Recurring tasks with the ice_recur add-on][9]
|
||||
|
||||
这就是 todo.txt 的灵活性所在。通过在 **~/.todo.actions.d/** 中使用[附加组件][10]，你可以添加命令并扩展基本 todo.sh 的功能。附加组件基本上是实现特定命令的脚本。对于重复执行的任务，插件 [ice_recur][11] 可以满足。按照页面上的说明操作，你可以以非常灵活的方式设置要重复处理的任务。
|
||||
|
||||
![Todour on MacOS][12]
|
||||
|
||||
目录中有很多附加组件，包括同步到某些云服务。也有链接到桌面或移动端应用的组件，这样你可以随时看到待办列表。
|
||||
|
||||
我只介绍了这个 todo 功能的表面，所以请花点时间深入了解这个工具的强大！它真的帮助我跟上每天的任务。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/1/open-source-to-do-list
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/checklist_todo_clock_time_team.png?itok=1z528Q0y (Team checklist)
|
||||
[2]: https://productivityalchemy.com/
|
||||
[3]: https://www.slideshare.net/AllThingsOpen/getting-to-done-on-the-command-line
|
||||
[4]: https://opensource.com/article/18/2/getting-to-done-agile-linux-command-line
|
||||
[5]: https://opensource.com/sites/default/files/uploads/productivity_7-1.png
|
||||
[6]: http://todotxt.org/
|
||||
[7]: https://orgmode.org/
|
||||
[8]: https://opensource.com/sites/default/files/uploads/productivity_7-2.png (Basic todo.txt list)
|
||||
[9]: https://opensource.com/sites/default/files/uploads/productivity_7-3.png (Recurring tasks with the ice_recur add-on)
|
||||
[10]: https://github.com/todotxt/todo.txt-cli/wiki/Todo.sh-Add-on-Directory
|
||||
[11]: https://github.com/rlpowell/todo-text-stuff
|
||||
[12]: https://opensource.com/sites/default/files/uploads/productivity_7-4.png (Todour on MacOS)
|
||||
@ -0,0 +1,107 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (One open source chat tool to rule them all)
|
||||
[#]: via: (https://opensource.com/article/20/1/open-source-chat-tool)
|
||||
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
|
||||
|
||||
一个管理所有聊天的开源聊天工具
|
||||
======
|
||||
BitlBee 将多个聊天应用集合到一个界面中。在我们的 20 个使用开源提升生产力的系列的第九篇文章中了解如何设置和使用 BitlBee。
|
||||
![Person using a laptop][1]
|
||||
|
||||
去年，我在 19 天里给你介绍了 19 个新（对你而言）的生产力工具。今年，我换了一种方式：使用你在使用或者还没使用的工具，构建一个使你可以在新一年更加高效的环境。
|
||||
|
||||
### 将所有聊天都放到 BitlBee 中
|
||||
|
||||
即时消息和聊天已经成为网络世界的主要内容。如果你像我一样，你可能打开五六个不同的应用与你的朋友、同事和其他人交谈。跟上所有聊天真的很痛苦。谢天谢地，你可以使用一个应用（好吧，是两个）将这些聊天整个到一个地方。
|
||||
|
||||
![BitlBee on XChat][2]
|
||||
|
||||
[BitlBee][3] 是作为服务运行的应用，它可以将标准的 IRC 客户端与大量的消息服务进行桥接。而且，由于它本质上是 IRC 服务器，因此你可以选择很多客户端。
|
||||
|
||||
BitlBee 几乎包含在所有 Linux 发行版中。在 Ubuntu 上安装（我选择的 Linux 桌面），类似这样：
|
||||
|
||||
|
||||
```
|
||||
`sudo apt install bitlbee-libpurple`
|
||||
```
|
||||
|
||||
在其他发行版上，包名可能略有不同，但搜索 _bitlbee_ 应该就能看到。
|
||||
|
||||
你会注意到我用的 libpurple 版的 BitlBee。这个版本能让我使用 [libpurple][4] 即时消息库中提供的所有协议，该库最初是为 [Pidgin][5] 开发的。
|
||||
|
||||
安装完成后，服务应会自动启动。现在，使用一个 IRC 客户端（图片中为 [XChat][6]），我可以连接到端口 6667（标准 IRC 端口）上的服务。
|
||||
|
||||
![Initial BitlBee connection][7]
|
||||
|
||||
你将自动连接到控制频道和 **bitlbee**。此频道对于你是独一无二的，每个人在多用户系统上都有自己的频道。在这里你可以配置服务。
|
||||
|
||||
在控制频道中输入 **help**，你可以随时获得完整的文档。浏览它，然后使用 **register** 命令在服务器上注册帐户。
|
||||
|
||||
|
||||
```
|
||||
`register <mypassword>`
|
||||
```
|
||||
|
||||
现在，你在服务器上所做的任何配置更改（IM 帐户、设置等）都将在输入 **save** 时保存。每当你连接时，使用 **identify <mypassword>** 连接到你的帐户并加载这些设置。
|
||||
|
||||
![purple settings][8]
|
||||
|
||||
命令 **help purple** 将显示 libpurple 提供的所有可用协议。例如，我安装了 [**telegram-purple**][9] 包，它增加了连接到 Telegram 的能力。我可以使用 **account add** 命令将我的电话号码作为帐户添加。
|
||||
|
||||
|
||||
```
|
||||
`account add telegram +15555555`
|
||||
```
|
||||
|
||||
BitlBee 将显示它已添加帐户。你可以使用 **account list** 列出你的帐户。因为我只有一个帐户，我可以通过 **account 0 on** 登录，它会进行 Telegram 登录，列出我所有的朋友和聊天，接下来就能正常聊天了。
|
||||
|
||||
但是，对于 Slack 这个最常见的聊天系统之一呢？你可以安装 [**slack-libpurple**][10] 插件，并且对 Slack 执行同样的操作。如果你不愿意编译和安装这些，这可能不适合你。
|
||||
|
||||
按照插件页面上的说明操作，安装后重新启动 BitlBee 服务。现在，当你运行 **help purple** 时，应该会列出 Slack。像其他协议一样添加一个 Slack 帐户。
|
||||
|
||||
|
||||
```
|
||||
account add slack [ksonney@myslack.slack.com][11]
|
||||
account 1 set password my_legcay_API_token
|
||||
account 1 on
|
||||
```
|
||||
|
||||
你知道么，你已经连接到 Slack 中，你可以通过 **chat add** 命令添加你感兴趣的 Slack 频道。比如：
|
||||
|
||||
|
||||
```
|
||||
`chat add 1 happyparty`
|
||||
```
|
||||
|
||||
将 Slack 频道 happyparty 添加为本地频道 #happyparty。现在可以使用标准 IRC **/join** 命令访问该频道。这很酷。
|
||||
|
||||
BitlBee 和 IRC 客户端帮助我的（大部分）聊天和即时消息保存在一个地方，并减少了我的分心，因为我不再需要查找并切换到任何一个刚刚找我的应用上。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/1/open-source-chat-tool
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/laptop_screen_desk_work_chat_text.png?itok=UXqIDRDD (Person using a laptop)
|
||||
[2]: https://opensource.com/sites/default/files/uploads/productivity_9-1.png (BitlBee on XChat)
|
||||
[3]: https://www.bitlbee.org/
|
||||
[4]: https://developer.pidgin.im/wiki/WhatIsLibpurple
|
||||
[5]: http://pidgin.im/
|
||||
[6]: http://xchat.org/
|
||||
[7]: https://opensource.com/sites/default/files/uploads/productivity_9-2.png (Initial BitlBee connection)
|
||||
[8]: https://opensource.com/sites/default/files/uploads/productivity_9-3.png (purple settings)
|
||||
[9]: https://github.com/majn/telegram-purple
|
||||
[10]: https://github.com/dylex/slack-libpurple
|
||||
[11]: mailto:ksonney@myslack.slack.com
|
||||
Loading…
Reference in New Issue
Block a user