mirror of
https://github.com/LCTT/TranslateProject.git
synced 2026-08-23 04:03:29 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu.Wang
@@ -1,34 +1,35 @@
|
||||
IssueHunt：一个新的开源软件打赏平台
|
||||
======
|
||||
许多开源开发者和公司都在努力解决的问题之一就是资金问题。社区中有一种假想，甚至是期望，必须免费提供自由和开源软件。但即使是 FOSS 也需要资金来继续开发。如果我们不建立让软件持续开发的系统，我们怎能期待更高质量的软件？
|
||||
|
||||
我们已经写了一篇关于[开源资金平台][1]的文章来试图解决这个缺点，截至今年 7 月，市场上出现了一个新的竞争者，旨在帮助填补这个空白：[IssueHunt][2] 。
|
||||
![IssueHunt][4]
|
||||
|
||||
许多开源开发者和公司都在努力解决的问题之一就是资金问题。社区中有一种假想，甚至是期望，必须免费提供自由开源软件（FOSS）。但即使是 FOSS 也需要资金来继续开发。如果我们不建立让软件持续开发的系统，我们怎能期待更高质量的软件？
|
||||
|
||||
我们已经写了一篇关于[开源资金平台][1]的文章来试图解决这个缺点，截至今年 7 月，市场上出现了一个新的竞争者，旨在帮助填补这个空白：[IssueHunt][2]。
|
||||
|
||||
### IssueHunt: 开源软件打赏平台
|
||||
|
||||
![IssueHunt website][3]
|
||||
|
||||
IssueHunt 提供了一种服务，支付自由开发者对开源代码的贡献。它通过所谓的赏金来实现：给予解决特定问题的任何人财务奖励。这些奖励的资金来自任何愿意捐赠以修复任何特定 bug 或添加功能的人。
|
||||
IssueHunt 提供了一种服务，对自由开发者的开源代码贡献进行支付。它通过所谓的赏金来实现：给予解决特定问题的任何人财务奖励。这些奖励的资金来自任何愿意捐赠以修复任何特定 bug 或添加功能的人。
|
||||
|
||||
如果你想修复的某个开源软件存在问题，你可以根据自己选择的方式提供奖励金额。
|
||||
|
||||
想要自己的产品被争抢解决么？在 IssueHunt 上向任何解决问题的人提供奖金就好了。就这么简单。
|
||||
|
||||
如果你是程序员，则可以浏览未解决的问题。解决这个问题（如果你可以的话），在 GitHub 存储库上提交 pull request，如果你的 pull request 被合并，那么你就会得到了钱。
|
||||
如果你是程序员，则可以浏览未解决的问题。解决这个问题（如果你可以的话），在 GitHub 存储库上提交拉取请求，如果你的拉取请求被合并，那么你就会得到了钱。
|
||||
|
||||
#### IssueHunt 最初是 Boostnote 的内部项目
|
||||
|
||||
![IssueHunt][4]
|
||||
|
||||
当笔记应用 [Boostnote][5] 背后的开发人员联系社区为他们的产品做出贡献时，该产品出现了。
|
||||
|
||||
在使用 IssueHunt 的前两年，Boostnote 通过数百名贡献者和压倒性的捐款收到了超过 8,400 个 Github star。
|
||||
|
||||
该产品非常成功，团队决定将其开放给社区的其他成员。
|
||||
|
||||
今天，[列表中在使用这个服务的项目][6]提供了数千美元的赏金。
|
||||
如今，[列表中在使用这个服务的项目][6]提供了数千美元的赏金。
|
||||
|
||||
Boostnote 号称有 [$2,800 的总赏金] [7]，而 Settings Sync，以前称为 Visual Studio Code Settings Sync，提供了[超过 $1,600 的赏金][8]。
|
||||
Boostnote 号称有 [$2,800 的总赏金][7]，而 Settings Sync，以前称为 Visual Studio Code Settings Sync，提供了[超过 $1,600 的赏金][8]。
|
||||
|
||||
还有其他服务提供类似于 IssueHunt 在此提供的内容。也许最引人注目的是 [Bountysource][9]，它提供与 IssueHunt 类似的赏金服务，同时还提供类似于 [Librepay][10] 的订阅支付处理。
|
||||
|
||||
@@ -36,7 +37,7 @@ Boostnote 号称有 [$2,800 的总赏金] [7]，而 Settings Sync，以前称为
|
||||
|
||||
在撰写本文时，IssueHunt 还处于起步阶段，但我非常高兴看到这个项目在这些年里的成果。
|
||||
|
||||
我不了解你，但我非常乐意为 FOSS 付款。如果产品质量高，并为我的生活增添价值，那么我很乐意向开发者支付产品费用。特别是 FOSS 的开发者正在创造尊重我自由的产品。
|
||||
我不知道你会怎么看，但我非常乐意为 FOSS 付款。如果产品质量高，并为我的生活增添价值，那么我很乐意向开发者支付产品费用。特别是 FOSS 的开发者正在创造尊重我自由的产品。
|
||||
|
||||
话虽如此，我一定会关注 IssueHunt 的继续前进，我可以用自己的钱或者在需要贡献的地方传播这个它来支持社区。
|
||||
|
||||
@@ -49,15 +50,15 @@ via: https://itsfoss.com/issuehunt/
|
||||
作者：[Phillip Prado][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/phillip/
|
||||
[1]: https://itsfoss.com/open-source-funding-platforms/
|
||||
[2]: https://issuehunt.io
|
||||
[3]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/issuehunt-website.png
|
||||
[4]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/issuehunt.jpg
|
||||
[3]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2018/09/issuehunt-website.png?w=799&ssl=1
|
||||
[4]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2018/09/issuehunt.jpg?w=800&ssl=1
|
||||
[5]: https://itsfoss.com/boostnote-linux-review/
|
||||
[6]: https://issuehunt.io/repos
|
||||
[7]: https://issuehunt.io/repos/53266139
|
||||
@@ -1,15 +1,15 @@
|
||||
什么是 SRE？它和 DevOps 是怎么关联的？
|
||||
=====
|
||||
|
||||
大型企业里 SRE 角色比较常见，不过小公司也需要 SRE。
|
||||
> 大型企业里 SRE 角色比较常见，不过小公司也需要 SRE。
|
||||
|
||||
|
||||
|
||||
虽然站点可靠性工程师（SRE）角色在近几年变得流行起来，但是很多人 —— 甚至是软件行业里的 —— 还不知道 SRE 是什么或者 SRE 都干些什么。为了搞清楚这些问题，这篇文章解释了 SRE 的含义，还有 SRE 怎样关联 DevOps，以及在工程师团队规模不大的组织里 SRE 该如何工作。
|
||||
虽然<ruby>站点可靠性工程师<rt>site reliability engineer</rt></ruby>（SRE）角色在近几年变得流行起来，但是很多人 —— 甚至是软件行业里的 —— 还不知道 SRE 是什么或者 SRE 都干些什么。为了搞清楚这些问题，这篇文章解释了 SRE 的含义，还有 SRE 怎样关联 DevOps，以及在工程师团队规模不大的组织里 SRE 该如何工作。
|
||||
|
||||
### 什么是站点可靠性工程？
|
||||
|
||||
谷歌的几个工程师写的《 [SRE：谷歌运维解密][1]》被认为是站点可靠性工程的权威书籍。谷歌的工程副总裁 Ben Treynor Sloss 在二十一世纪初[创造了这个术语][2]。他是这样定义的：“当你让软件工程师设计运维功能时，SRE 就产生了。”
|
||||
谷歌的几个工程师写的《[SRE：谷歌运维解密][1]》被认为是站点可靠性工程的权威书籍。谷歌的工程副总裁 Ben Treynor Sloss 在二十一世纪初[创造了这个术语][2]。他是这样定义的：“当你让软件工程师设计运维功能时，SRE 就产生了。”
|
||||
|
||||
虽然系统管理员从很久之前就在写代码，但是过去的很多时候系统管理团队是手动管理机器的。当时他们管理的机器可能有几十台或者上百台，不过当这个数字涨到了几千甚至几十万的时候，就不能简单的靠人去解决问题了。规模如此大的情况下，很明显应该用代码去管理机器（以及机器上运行的软件）。
|
||||
|
||||
@@ -19,13 +19,13 @@
|
||||
|
||||
### SRE 和 DevOps
|
||||
|
||||
站点可靠性工程的核心，就是对 DevOps 范例的实践。[DevOps 的定义][3]有很多种方式。开发团队（“devs”）和运维（“ops”）团队相互分离的传统模式下，写代码的团队在服务交付给用户使用之后就不再对服务状态负责了。开发团队“把代码扔到墙那边”让运维团队去部署和支持。
|
||||
站点可靠性工程的核心，就是对 DevOps 范例的实践。[DevOps 的定义][3]有很多种方式。开发团队（“dev”）和运维（“ops”）团队相互分离的传统模式下，写代码的团队在将服务交付给用户使用之后就不再对服务状态负责了。开发团队“把代码扔到墙那边”让运维团队去部署和支持。
|
||||
|
||||
这种情况会导致大量失衡。开发和运维的目标总是不一致 —— 开发希望用户体验到“最新最棒”的代码，但是运维想要的是变更尽量少的稳定系统。运维是这样假定的，任何变更都可能引发不稳定，而不做任何变更的系统可以一直保持稳定。（减少软件的变更次数并不是避免故障的唯一因素，认识到这一点很重要。例如，虽然你的 web 应用保持不变，但是当用户数量涨到十倍时，服务可能就会以各种方式出问题。）
|
||||
|
||||
DevOps 理念认为通过合并这两个岗位就能够消灭争论。如果开发团队时刻都想把新代码部署上线，那么他们也必须对新代码引起的故障负责。就像亚马逊的 [Werner Vogels 说的][4]那样，“谁开发，谁运维”（生产环境）。但是开发人员已经有一大堆问题了。他们不断的被推动着去开发老板要的产品功能。再让他们去了解基础设施，包括如何部署、配置还有监控服务，这对他们的要求有点太多了。所以就需要 SRE 了。
|
||||
|
||||
开发一个 web 应用的时候经常是很多人一起参与。有用户界面设计师，图形设计师，前端工程师，后端工程师，还有许多其他工种（视技术选型的具体情况而定）。如何管理写好的代码也是需求之一（例如部署，配置，监控）—— 这是 SRE 的专业领域。但是，就像前端工程师受益于后端领域的知识一样（例如从数据库获取数据的方法），SRE 理解部署系统的工作原理，知道如何满足特定的代码或者项目的具体需求。
|
||||
开发一个 web 应用的时候经常是很多人一起参与。有用户界面设计师、图形设计师、前端工程师、后端工程师，还有许多其他工种（视技术选型的具体情况而定）。如何管理写好的代码也是需求之一（例如部署、配置、监控）—— 这是 SRE 的专业领域。但是，就像前端工程师受益于后端领域的知识一样（例如从数据库获取数据的方法），SRE 理解部署系统的工作原理，知道如何满足特定的代码或者项目的具体需求。
|
||||
|
||||
所以 SRE 不仅仅是“写代码的运维工程师”。相反，SRE 是开发团队的成员，他们有着不同的技能，特别是在发布部署、配置管理、监控、指标等方面。但是，就像前端工程师必须知道如何从数据库中获取数据一样，SRE 也不是只负责这些领域。为了提供更容易升级、管理和监控的产品，整个团队共同努力。
|
||||
|
||||
@@ -37,7 +37,7 @@ DevOps 理念认为通过合并这两个岗位就能够消灭争论。如果开
|
||||
|
||||
让开发人员做 SRE 最显著的优点是，团队规模变大的时候也能很好的扩展。而且，开发人员将会全面地了解应用的特性。但是，许多初创公司的基础设施包含了各种各样的 SaaS 产品，这种多样性在基础设施上体现的最明显，因为连基础设施本身也是多种多样。然后你们在某个基础设施上引入指标系统、站点监控、日志分析、容器等等。这些技术解决了一部分问题，也增加了复杂度。开发人员除了要了解应用程序的核心技术（比如开发语言），还要了解上述所有技术和服务。最终，掌握所有的这些技术让人无法承受。
|
||||
|
||||
另一种方案是聘请专家专职做 SRE。他们专注于发布部署、配置管理、监控和指标，可以节省开发人员的时间。这种方案的缺点是，SRE 的时间必须分配给多个不同的应用（就是说 SRE 需要贯穿整个工程部门）。 这可能意味着 SRE 没时间对任何应用深入学习，然而他们可以站在一个能看到服务全貌的高度，知道各个部分是怎么组合在一起的。 这个“ 三万英尺高的视角”可以帮助 SRE 从系统整体上考虑，哪些薄弱环节需要优先修复。
|
||||
另一种方案是聘请专家专职做 SRE。他们专注于发布部署、配置管理、监控和指标，可以节省开发人员的时间。这种方案的缺点是，SRE 的时间必须分配给多个不同的应用（就是说 SRE 需要贯穿整个工程部门）。 这可能意味着 SRE 没时间对任何应用深入学习，然而他们可以站在一个能看到服务全貌的高度，知道各个部分是怎么组合在一起的。 这个“三万英尺高的视角”可以帮助 SRE 从系统整体上考虑，哪些薄弱环节需要优先修复。
|
||||
|
||||
有一个关键信息我还没提到：其他的工程师。他们可能很渴望了解发布部署的原理，也很想尽全力学会使用指标系统。而且，雇一个 SRE 可不是一件简单的事儿。因为你要找的是一个既懂系统管理又懂软件工程的人。（我之所以明确地说软件工程而不是说“能写代码”，是因为除了写代码之外软件工程还包括很多东西，比如编写良好的测试或文档。）
|
||||
|
||||
@@ -54,7 +54,7 @@ via: https://opensource.com/article/18/10/sre-startup
|
||||
作者：[Craig Sebenik][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[BeliteX](https://github.com/belitex)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@@ -0,0 +1,86 @@
|
||||
如何更换 Ubuntu 系统的 GDM 登录界面背景
|
||||
======
|
||||
|
||||
|
||||
|
||||
Ubuntu 18.04 LTS 桌面系统在登录、锁屏和解锁状态下，我们会看到一个纯紫色的背景。它是 GDM（<ruby>GNOME 显示管理器<rt>GNOME Display Manager</rt></ruby>）从 ubuntu 17.04 版本开始使用的默认背景。有一些人可能会不喜欢这个纯色的背景，想换一个酷一点、更吸睛的！如果是这样，你找对地方了。这篇短文将会告诉你如何更换 Ubuntu 18.04 LTS 的 GDM 登录界面的背景。
|
||||
|
||||
### 更换 Ubuntu 的登录界面背景
|
||||
|
||||
这是 Ubuntu 18.04 LTS 桌面系统默认的登录界面。
|
||||
|
||||
|
||||
|
||||
不管你喜欢与否，你总是会不经意在登录、解屏/锁屏的时面对它。别担心！你可以随便更换一个你喜欢的图片。
|
||||
|
||||
在 Ubuntu 上更换桌面壁纸和用户的资料图像不难。我们可以点击鼠标就搞定了。但更换解屏/锁屏的背景则需要修改文件 `ubuntu.css`，它位于 `/usr/share/gnome-shell/theme`。
|
||||
|
||||
修改这个文件之前，最好备份一下它。这样我们可以避免出现问题时可以恢复它。
|
||||
|
||||
```
|
||||
$ sudo cp /usr/share/gnome-shell/theme/ubuntu.css /usr/share/gnome-shell/theme/ubuntu.css.bak
|
||||
```
|
||||
|
||||
修改文件 `ubuntu.css`：
|
||||
|
||||
```
|
||||
$ sudo nano /usr/share/gnome-shell/theme/ubuntu.css
|
||||
```
|
||||
|
||||
在文件中找到关键字 `lockDialogGroup`，如下行：
|
||||
|
||||
```
|
||||
#lockDialogGroup {
|
||||
background: #2c001e url(resource:///org/gnome/shell/theme/noise-texture.png);
|
||||
background-repeat: repeat;
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
可以看到，GDM 默认登录的背景图片是 `noise-texture.png`。
|
||||
|
||||
现在修改为你自己的图片路径。也可以选择 .jpg 或 .png 格式的文件，两种格式的图片文件都是支持的。修改完成后的文件内容如下：
|
||||
|
||||
```
|
||||
#lockDialogGroup {
|
||||
background: #2c001e url(file:///home/sk/image.png);
|
||||
background-repeat: no-repeat;
|
||||
background-size: cover;
|
||||
background-position: center;
|
||||
}
|
||||
```
|
||||
|
||||
请注意 `ubuntu.css` 文件里这个关键字的修改，我把修改点加粗了。
|
||||
|
||||
你可能注意到，我把原来的 `... url(resource:///org/gnome/shell/theme/noise-texture.png);` 修改为 `... url(file:///home/sk/image.png);`。也就是说，你可以把 `... url(resource ...` 修改为 `.. url(file ...`。
|
||||
|
||||
同时，你可以把参数 `background-repeat:` 的值 `repeat` 修改为 `no-repeat`，并增加另外两行。你可以直接复制上面几行的修改到你的 `ubuntu.css` 文件，对应的修改为你的图片路径。
|
||||
|
||||
修改完成后，保存和关闭此文件。然后系统重启生效。
|
||||
|
||||
下面是 GDM 登录界面的最新背景图片：
|
||||
|
||||
|
||||
|
||||
是不是很酷，你都看到了，更换 GDM 登录的默认背景很简单。你只需要修改 `ubuntu.css` 文件中图片的路径然后重启系统。是不是很简单也很有意思.
|
||||
|
||||
你可以修改 `/usr/share/gnome-shell/theme` 目录下的文件 `gdm3.css` ，具体修改内容和修改结果和上面一样。同时记得修改前备份要修改的文件。
|
||||
|
||||
就这些了。如果有好的东东再分享了，请大家关注！
|
||||
|
||||
后会有期。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/how-to-change-gdm-login-screen-background-in-ubuntu/
|
||||
|
||||
作者：[SK][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[Guevaraya](https://github.com/guevaraya)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
@@ -1,3 +1,5 @@
|
||||
[#]: translator: (oneforalone)
|
||||
|
||||
Emacs #1: Ditching a bunch of stuff and moving to Emacs and org-mode
|
||||
======
|
||||
I’ll admit it. After over a decade of vim, I’m hooked on [Emacs][1].
|
||||
|
||||
@@ -0,0 +1,96 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (Easily Fund Open Source Projects With These Platforms)
|
||||
[#]: via: (https://itsfoss.com/open-source-funding-platforms/)
|
||||
[#]: author: ([Ambarish Kumar](https://itsfoss.com/author/ambarish/))
|
||||
[#]: url: ( )
|
||||
|
||||
Easily Fund Open Source Projects With These Platforms
|
||||
======
|
||||
|
||||
**Brief: We list out some funding platforms you can use to financially support open source projects. **
|
||||
|
||||
Financial support is one of the many ways to [help Linux and Open Source community][1]. This is why you see “Donate” option on the websites of most open source projects.
|
||||
|
||||
While the big corporations have the necessary funding and resources, most open source projects are developed by individuals in their spare time. However, it does require one’s efforts, time and probably includes some overhead costs too. Monetary supports surely help drive the project development.
|
||||
|
||||
If you would like to support open source projects financially, let me show you some platforms dedicated to open source and/or Linux.
|
||||
|
||||
### Funding platforms for Open Source projects
|
||||
|
||||
![Open Source funding platforms][2]
|
||||
|
||||
Just to clarify, we are not associated with any of the funding platforms mentioned here.
|
||||
|
||||
#### 1\. Liberapay
|
||||
|
||||
[Gratipay][3] was probably the biggest platform for funding open source projects and people associated with the project, which got shut down at the end of the year 2017. However, there’s a fork – Liberapay that works as a recurrent donation platform for the open source projects and the contributors.
|
||||
|
||||
[Liberapay][4] is a non-profit, open source organization that helps in a periodic donation to a project. You can create an account as a contributor and ask the people who would really like to help (usually the consumer of your products) to donate.
|
||||
|
||||
To receive a donation, you will have to create an account on Liberapay, brief what you do and about your project, reasons for asking for the donation and what will be done with the money you receive.
|
||||
|
||||
For someone who would like to donate, they would have to add money to their accounts and set up a period for payment that can be weekly, monthly or yearly to someone. There’s a mail triggered when there is not much left to donate.
|
||||
|
||||
The currency supported are dollars and Euro as of now and you can always put up a badge on Github, your Twitter profile or website for a donation.
|
||||
|
||||
#### 2\. Bountysource
|
||||
|
||||
[Bountysource][5] is a funding platform for open source software that has a unique way of paying a developer for his time and work int he name of Bounties.
|
||||
|
||||
There are basically two campaigns, bounties and salt campaign.
|
||||
|
||||
Under the Bounties, users declare bounties aka cash prizes on open issues that they believe should be fixed or any new features which they want to see in the software they are using. A developer can then go and fix it to receive the cash prize.
|
||||
|
||||
Salt Campaign is like any other funding, anyone can pay a recurring amount to a project or an individual working for an open source project for as long as they want.
|
||||
|
||||
Bountysource accepts any software that is approved by Free Software Foundation or Open Source Initiatives. The bounties can be placed using PayPal, Bitcoin or the bounty itself if owned previously. Bountysource supports a no. of issue tracker currently like GitHub, Bugzilla, Google Code, Jira, Launchpad etc.
|
||||
|
||||
#### 3\. Open Collective
|
||||
|
||||
[Open Collective][6] is another popular funding initiative where a person who is willing to receive the donation for the work he is doing in Open Source world can create a page. He can submit the expense reports for the project he is working on. A contributor can add money to his account and pay him for his expenses.
|
||||
|
||||
The complete process is transparent and everyone can track whoever is associated with Open Collective. The contributions are visible along with the unpaid expenses. There is also the option to contribute on a recurring basis.
|
||||
|
||||
Open Collective currently has more than 500 collectives being backed up by more than 5000 users.
|
||||
|
||||
The fact that it is transparent and you know what you are contributing to, drives more accountability. Some common example of collective include hosting costs, community maintenance, travel expenses etc.
|
||||
|
||||
Though Open Collective keeps 10% of all the transactions, it is still a nice way to get your expenses covered in the process of contributing towards an open source project.
|
||||
|
||||
#### 4\. Open Source Grants
|
||||
|
||||
[Open Source Grants][7] is still in its beta stage and has not matured yet. They are looking for projects that do not have any stable funding and adds value to open source community. Most open source projects are run by a small community in a free time and they are trying to fund them so that the developers can work full time on the projects.
|
||||
|
||||
They are equally searching for companies that want to help open source enthusiasts. The process of submitting a project is still being worked upon, and hopefully, in coming days we will see a working way of funding.
|
||||
|
||||
### Final Words
|
||||
|
||||
In the end, I would also like to mention [Patreon][8]. This funding platform is not exclusive to open source but is focused on creators of all kinds. Some projects like [elementary OS have created their accounts on Patreon][9] so that you can support the project on a recurring basis.
|
||||
|
||||
Think Free Speech, not Free Beer. Your small contribution to a project can help it sustain in the long run. For the developers, the above platform can provide a good way to cover up their expenses.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/open-source-funding-platforms/
|
||||
|
||||
作者：[Ambarish Kumar][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://itsfoss.com/author/ambarish/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://itsfoss.com/help-linux-grow/
|
||||
[2]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2018/03/Fund-Open-Source-projects.png?resize=800%2C450&ssl=1
|
||||
[3]: https://itsfoss.com/gratipay-open-source/
|
||||
[4]: https://liberapay.com/
|
||||
[5]: https://www.bountysource.com/
|
||||
[6]: https://opencollective.com/
|
||||
[7]: https://foundation.travis-ci.org/grants/
|
||||
[8]: https://www.patreon.com/
|
||||
[9]: https://www.patreon.com/elementary
|
||||
@@ -1,3 +1,5 @@
|
||||
translating---geekpi
|
||||
|
||||
A Free Guide for Setting Your Open Source Strategy
|
||||
======
|
||||
|
||||
|
||||
@@ -1,72 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (How to use multiple programming languages without losing your mind)
|
||||
[#]: via: (https://opensource.com/article/18/11/multiple-programming-languages)
|
||||
[#]: author: (Bart Copeland https://opensource.com/users/bartcopeland)
|
||||
[#]: url: ( )
|
||||
|
||||
How to use multiple programming languages without losing your mind
|
||||
======
|
||||
A polyglot environment is a double-edged sword, bringing benefits along with complexities that may threaten the organization.
|
||||
|
||||
|
||||
|
||||
With all the different programming languages available today, many organizations have become digital polyglots. Open source opens up a world of languages and technology stacks developers can use to accomplish their tasks, including developing and supporting legacy and modern software applications.
|
||||
|
||||
Polyglots can talk with millions more people than those who only speak their native language. In software environments, developers don't introduce new languages to achieve specifc ends, not to communicate better. Some languages are great for one task but not another, so working with multiple programming languages enables developers to use the right tool for the job. In this way, all development is polyglot; it's just the nature of the beast.
|
||||
|
||||
The creation of a polyglot environment is often gradual and situational. For example, when an enterprise acquires a company, it takes on the company's technology stacks—including its programming languages. Or as tech leadership changes, new leaders may bring different technologies into the fold. Technologies also fall in and out of fashion, expanding the number of programming languages and technologies an organization has to maintain over time.
|
||||
|
||||
A polyglot environment is a double-edged sword for enterprises, bringing benefits but also complexities and challenges. Ultimately, if the situation remains unchecked, polyglot will kill your enterprise.
|
||||
|
||||
### Tricky technical tongue-twisters
|
||||
|
||||
Where there are multiple different technologies—programming languages, legacy tools, and up-and-coming technology stacks—there is complexity. Engineering teams spend more time wrestling to retrofit programming languages with licenses, security, and dependencies. At the same time, management lacks oversight on code compliance and can't gauge risk.
|
||||
|
||||
What happens is that enterprises have varying degrees of programming language quality and high variability in tooling support. It's hard to become an expert in one language when you're required to work with a dozen. There's a big difference in skill level between a person who speaks French and Italian fluently and a person who can string a few sentences together in eight languages. The same is true for developers and programming languages.
|
||||
|
||||
The difficulties only increase with the addition of more programming languages, leading to a digital Tower of Babel.
|
||||
|
||||
The answer is not to take away the tools your developers need for the job. Adding new programming languages builds their skill base and empowers them with the right equipment to fulfill their craft. So, you want to say "yes" to your developers, but as more and more programming languages are added to the enterprise, they impose a drag on your software development lifecycle (SDLC). At scale, all these languages and tools can kill the enterprise.
|
||||
|
||||
There are three main issues enterprises should pay attention to:
|
||||
|
||||
1. **Visibility:** Teams come together for a project, then disband. Applications are released and never updated—why fix what's not broken? As a result, when a critical vulnerability is discovered, the enterprise may not have visibility into which applications are affected, which libraries those applications contain, or even what languages they were built with. This can result in costly "exploration projects" to ensure the vulnerability is properly addressed.
|
||||
2. **Updating or coding:** Some enterprises centralize the updating and fixing function in a single team. Others require that each "pizza team" manage its own development tools. In either case, the engineering team and management pay an opportunity cost: rather than coding new features, these teams are constantly updating and fixing libraries in their open source tools since they move so quickly.
|
||||
3. **Reinventing the wheel:** Since code dependencies and library versions are constantly being updated, the artifacts associated with the original build of an application may no longer be available when a vulnerability is found. As a result, many development cycles are wasted trying to recreate an environment in which the vulnerability can be fixed.
|
||||
|
||||
|
||||
|
||||
Multiply each programming language in your organization by these three issues, and what started out as a molehill suddenly looks like Mount Everest. And just like a mountain climber, you won't survive without the proper equipment and tools.
|
||||
|
||||
### Finding your Rosetta Stone
|
||||
|
||||
A comprehensive solution that serves the needs of the enterprise and its individual stakeholders in the SDLC is in order. Enterprises can create this solution using these best practices:
|
||||
|
||||
1. Monitor code running in production and respond based on risk of flagged components (e.g., common vulnerabilities and exposures components) used in your applications.
|
||||
2. Receive regular updates to keep code current and bug-free.
|
||||
3. Use commercial open source support to get help with programming language versions and platforms that are near end-of-life and not supported by the community.
|
||||
4. Standardize specific programming language builds across your enterprise to enable consistent environments across teams and minimize dependencies.
|
||||
5. Set thresholds for when to trigger an update, alarm, or another kind of event based on dependencies.
|
||||
6. Create a single source of truth for your package management; this may require the assistance of a knowledgeable technology provider.
|
||||
7. Get smaller build distributions with only the packages you need, based on your specific criteria.
|
||||
|
||||
|
||||
|
||||
Using these best practices, developers can maximize their time to create more value for the enterprise instead of doing basic tooling or build-engineering tasks. This will create code consistency in all environments in the software development life cycle (SDLC). It will also create greater efficiency and cost savings as fewer resources are needed to maintain programming languages and package distributions. This new way of operating will make the lives of both technical staff and management easier.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/11/multiple-programming-languages
|
||||
|
||||
作者：[Bart Copeland][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/bartcopeland
|
||||
[b]: https://github.com/lujun9972
|
||||
@@ -1,3 +1,5 @@
|
||||
translating by lixinyuxx
|
||||
|
||||
My personal Email setup - Notmuch, mbsync, postfix and dovecot
|
||||
======
|
||||
I've been using personal email setup for quite long and have not documented it anywhere. Recently when I changed my laptop (a post is pending about it) I got lost trying to recreate my local mail setup. So this post is a self documentation so that I don't have to struggle again to get it right.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
translating by lixinyuxx
|
||||
|
||||
27 open solutions to everything in education
|
||||
======
|
||||
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
Translating by Guevaraya
|
||||
|
||||
'Getting to Done' on the Linux command line
|
||||
======
|
||||
|
||||
|
||||
@@ -1,91 +0,0 @@
|
||||
translating----geekpi
|
||||
|
||||
How to Set Different Wallpaper for Each Monitor in Linux
|
||||
======
|
||||
**Brief: If you want to display different wallpapers on multiple monitors on Ubuntu 18.04 or any other Linux distribution with GNOME, MATE or Budgie desktop environment, this nifty tool will help you achieve this.**
|
||||
|
||||
Multi-monitor setup often leads to multiple issues on Linux but I am not going to discuss those issues in this article. I have rather a positive article on multiple monitor support on Linux.
|
||||
|
||||
If you are using multiple monitor, perhaps you would like to setup a different wallpaper for each monitor. I am not sure about other Linux distributions and desktop environments, but Ubuntu with [GNOME desktop][1] doesn’t provide this functionality on its own.
|
||||
|
||||
Fret not! In this quick tutorial, I’ll show you how to set a different wallpaper for each monitor on Linux distributions with GNOME desktop environment.
|
||||
|
||||
### Setting up different wallpaper for each monitor on Ubuntu 18.04 and other Linux distributions
|
||||
|
||||
![Different wallaper on each monitor in Ubuntu][2]
|
||||
|
||||
I am going to use a nifty tool called [HydraPaper][3] for setting different backgrounds on different monitors. HydraPaper is a [GTK][4] based application to set different backgrounds for each monitor in [GNOME desktop environment][5].
|
||||
|
||||
It also supports on [MATE][6] and [Budgie][7] desktop environments. Which means Ubuntu MATE and [Ubuntu Budgie][8] users can also benefit from this application.
|
||||
|
||||
#### Install HydraPaper on Linux using FlatPak
|
||||
|
||||
HydraPaper can be installed easily using [FlatPak][9]. Ubuntu 18.04 already provides support for FlatPaks so all you need to do is to download the application file and double click on it to open it with the GNOME Software Center.
|
||||
|
||||
You can refer to this article to learn [how to enable FlatPak support][10] on your distribution. Once you have the FlatPak support enabled, just download it from [FlatHub][11] and install it.
|
||||
|
||||
[Download HydraPaper][12]
|
||||
|
||||
#### Using HydraPaper for setting different background on different monitors
|
||||
|
||||
Once installed, just look for HydraPaper in application menu and start the application. You’ll see images from your Pictures folder here because by default the application takes images from the Pictures folder of the user.
|
||||
|
||||
You can add your own folder(s) where you keep your wallpapers. Do note that it doesn’t find images recursively. If you have nested folders, it will only show images from the top folder.
|
||||
|
||||
![Setting up different wallpaper for each monitor on Linux][13]
|
||||
|
||||
Using HydraPaper is absolutely simple. Just select the wallpapers for each monitor and click on the apply button at the top. You can easily identify external monitor(s) termed with HDMI.
|
||||
|
||||
![Setting up different wallpaper for each monitor on Linux][14]
|
||||
|
||||
You can also add selected wallpapers to ‘Favorites’ for quick access. Doing this will move the ‘favorite wallpapers’ from Wallpapers tab to Favorites tab.
|
||||
|
||||
![Setting up different wallpaper for each monitor on Linux][15]
|
||||
|
||||
You don’t need to start HydraPaper at each boot. Once you set different wallpaper for different monitor, the settings are saved and you’ll see your chosen wallpapers even after restart. This would be expected behavior of course but I thought I would mention the obvious.
|
||||
|
||||
One big downside of HydraPaper is in the way it is designed to work. You see, HydraPaper combines your selected wallpapers into one single image and stretches it across the screens giving an impression of having different background on each display. And this becomes an issue when you remove the external display.
|
||||
|
||||
For example, when I tried using my laptop without the external display, it showed me an background image like this.
|
||||
|
||||
![Dual Monitor wallpaper HydraPaper][16]
|
||||
|
||||
Quite obviously, this is not what I would expect.
|
||||
|
||||
#### Did you like it?
|
||||
|
||||
HydraPaper makes setting up different backgrounds on different monitors a painless task. It supports more than two monitors and monitors with different orientation. Simple interface with only the required features makes it an ideal application for those who always use dual monitors.
|
||||
|
||||
How do you set different wallpaper for different monitor on Linux? Do you think HydraPaper is an application worth installing?
|
||||
|
||||
Do share your views and if you find this article, please share it on various social media channels such as Twitter and [Reddit][17].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/wallpaper-multi-monitor/
|
||||
|
||||
作者：[Abhishek Prakash][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/abhishek/
|
||||
[1]:https://www.gnome.org/
|
||||
[2]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/multi-monitor-wallpaper-setup-800x450.jpeg
|
||||
[3]:https://github.com/GabMus/HydraPaper
|
||||
[4]:https://www.gtk.org/
|
||||
[5]:https://itsfoss.com/gnome-tricks-ubuntu/
|
||||
[6]:https://mate-desktop.org/
|
||||
[7]:https://budgie-desktop.org/home/
|
||||
[8]:https://itsfoss.com/ubuntu-budgie-18-review/
|
||||
[9]:https://flatpak.org
|
||||
[10]:https://flatpak.org/setup/
|
||||
[11]:https://flathub.org
|
||||
[12]:https://flathub.org/apps/details/org.gabmus.hydrapaper
|
||||
[13]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/different-wallpaper-each-monitor-hydrapaper-2-800x631.jpeg
|
||||
[14]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/different-wallpaper-each-monitor-hydrapaper-1.jpeg
|
||||
[15]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/different-wallpaper-each-monitor-hydrapaper-3.jpeg
|
||||
[16]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/hydra-paper-dual-monitor-800x450.jpeg
|
||||
[17]:https://www.reddit.com/r/LinuxUsersGroup/
|
||||
@@ -1,5 +1,3 @@
|
||||
translating by Flowsnow
|
||||
|
||||
Build an interactive CLI with Node.js
|
||||
======
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (chenxinlong)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (How To Configure IP Address In Ubuntu 18.04 LTS)
|
||||
@@ -7,6 +7,8 @@
|
||||
[#]: author: (SK https://www.ostechnix.com/author/sk/)
|
||||
[#]: url: ( )
|
||||
|
||||
翻译中 ...
|
||||
|
||||
How To Configure IP Address In Ubuntu 18.04 LTS
|
||||
======
|
||||
|
||||
|
||||
@@ -0,0 +1,126 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (Building custom documentation workflows with Sphinx)
|
||||
[#]: via: (https://opensource.com/article/18/11/building-custom-workflows-sphinx)
|
||||
[#]: author: ([Mark Meyer](https://opensource.com/users/ofosos))
|
||||
[#]: url: ( )
|
||||
|
||||
Building custom documentation workflows with Sphinx
|
||||
======
|
||||
Create documentation the way that works best for you.
|
||||
|
||||
|
||||
[Sphinx][1] is a popular application for creating documentation, similar to JavaDoc or Jekyll. However, Sphinx's reStructured Text input allows for a higher degree of customization than those other tools.
|
||||
|
||||
This tutorial will explain how to customize Sphinx to suit your workflow. You can follow along using sample code on [GitHub][2].
|
||||
|
||||
### Some definitions
|
||||
|
||||
Sphinx goes far beyond just enabling you to style text with predefined tags. It allows you to shape and automate your documentation by defining new roles and directives. A role is a single word element that usually is rendered inline in your documentation, while a directive can contain more complex content. These can be contained in a domain.
|
||||
|
||||
A Sphinx domain is a collection of directives and roles as well as a few other things, such as an index definition. Your next Sphinx domain could be a specific programming language (Sphinx was developed to create Python's documentation). Or you might have a command line tool that implements the same command pattern (e.g., **tool <command> \--args**) over and over. You can document it with a custom domain, adding directives and indexes along the way.
|
||||
|
||||
Here's an example from our **recipe** domain:
|
||||
|
||||
```
|
||||
The recipe contains `tomato` and `cilantro`.
|
||||
|
||||
.. rcp:recipe:: TomatoSoup
|
||||
:contains: tomato cilantro salt pepper
|
||||
|
||||
This recipe is a tasty tomato soup, combine all ingredients
|
||||
and cook.
|
||||
```
|
||||
|
||||
Now that we've defined the recipe **TomatoSoup** , we can reference it anywhere in our documentation using the custom role **refef**. For example:
|
||||
|
||||
```
|
||||
You can use the :rcp:reref:`TomatoSoup` recipe to feed your family.
|
||||
```
|
||||
|
||||
This enables our recipes to show up in two indices: the first lists all recipes, and the second lists all recipes by ingredient.
|
||||
|
||||
### What's in a domain?
|
||||
|
||||
A Sphinx domain is a specialized container that ties together roles, directives, and indices, among other things. The domain has a name ( **rcp** ) to address its components in the documentation source. It announces its existence to Sphinx in the **setup()** method of the package. From there, Sphinx can find roles and directives, since these are part of the domain.
|
||||
|
||||
This domain also serves as the central catalog of objects in this sample. Using initial data, it defines two variables, **objects** and **obj2ingredient**. These contain a list of all objects defined (all recipes) and a hash that maps a canonical ingredient name to the list of objects.
|
||||
|
||||
```
|
||||
initial_data = {
|
||||
'objects': [], # object list
|
||||
'obj2ingredient': {}, # ingredient -> [objects]
|
||||
}
|
||||
```
|
||||
|
||||
The way we name objects is common across our extension. For each object created, the canonical name is **rcp. <typename>.<objectname>**, where **< typename>** is the Python type of the object, and **< objectname>** is the name the documentation writer gives the object. This enables the extension to use different object types that share the same name.
|
||||
|
||||
Having a canonical name and central place for our objects is a huge advantage. Both our indices and our cross-referencing code use this feature.
|
||||
|
||||
### Custom roles and directives
|
||||
|
||||
In our example, **.. rcp:recipe::** indicates a custom directive. You might think it's overly specific to create custom syntax for these items, but it illustrates the degree of customization you can get in Sphinx. This provides rich markup that structures documents and leads to better docs. Specialization allows us to extract information from our docs.
|
||||
|
||||
Our definition for this directive will provide minimal formatting, but it will be functional.
|
||||
|
||||
```
|
||||
class RecipeNode(ObjectDescription):
|
||||
"""A custom node that describes a recipe."""
|
||||
|
||||
required_arguments = 1
|
||||
|
||||
option_spec = {
|
||||
'contains': rst.directives.unchanged_required
|
||||
}
|
||||
```
|
||||
|
||||
For this directive, **required_arguments** tells Sphinx to expect one parameter, the recipe name. **option_spec** lists the optional arguments, including their names. Finally, **has_content** specifies that there will be more reStructured Text as a child to this node.
|
||||
|
||||
We also implement multiple methods:
|
||||
|
||||
* **handle_signature()** implements parsing the signature of the directive and passes on the object's name and type to its superclass
|
||||
* **add_taget_and_index()** adds a target (to link to) and an entry to the index for this node
|
||||
|
||||
|
||||
|
||||
### Creating indices
|
||||
|
||||
Both **IngredientIndex** and **RecipeIndex** are derived from Sphinx's **Index** class. They implement custom logic to generate a tuple of values that define the index. Note that **RecipeIndex** is a degenerate index that has only one entry. Extending it to cover more object types—and moving from a **RecipeDomain** to a **CookbookDomain** —is not yet part of the code.
|
||||
|
||||
Both indices use the method **generate()** to do their work. This method combines the information from our domain, sorts it, and returns it in a list structure that will be accepted by Sphinx. See the [Sphinx Domain API][3] page for more information.
|
||||
|
||||
The first time you visit the Domain API page, you may be a little overwhelmed by the structure. But our ingredient index is just a list of tuples, like **('tomato', 'TomatoSoup', 'test', 'rec-TomatoSoup',...)**.
|
||||
|
||||
### Referencing recipes
|
||||
|
||||
Adding cross-references is not difficult (but it's also not a given). Add an **XRefRole** to the domain and implement the method **resolve_xref()**. Having a custom role to reference a type allows us to unambiguously reference any object, even if two objects have the same name. If you look at the parameters of **resolve_xref()** in **Domain** , you'll see **typ** and **target**. These define the cross-reference type and its target name. We'll use **target** to resolve our destination from our domain's **objects** because we currently have only one type of node.
|
||||
|
||||
We can add the cross-reference role to **RecipeDomain** in the following way:
|
||||
|
||||
```
|
||||
roles = {
|
||||
'reref': XRefRole()
|
||||
}
|
||||
```
|
||||
|
||||
There's nothing for us to implement. Defining a working **resolve_xref()** and attaching an **XRefRole** to the domain is all you need to do.
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/11/building-custom-workflows-sphinx
|
||||
|
||||
作者：[Mark Meyer][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/ofosos
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: http://www.sphinx-doc.org/en/master/
|
||||
[2]: https://github.com/ofosos/sphinxrecipes
|
||||
[3]: https://www.sphinx-doc.org/en/master/extdev/domainapi.html#sphinx.domains.Index.generate
|
||||
@@ -0,0 +1,87 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (Turn an old Linux desktop into a home media center)
|
||||
[#]: via: (https://opensource.com/article/18/11/old-linux-desktop-new-home-media-center)
|
||||
[#]: author: ([Alan Formy-Duval](https://opensource.com/users/alanfdoss))
|
||||
[#]: url: ( )
|
||||
|
||||
Turn an old Linux desktop into a home media center
|
||||
======
|
||||
Repurpose an outdated computer to browse the internet and watch videos on your big screen TV.
|
||||
|
||||
|
||||
My first attempt to set up an "entertainment PC" was back in the late 1990s, using a plain old desktop computer with a Trident ProVidia 9685 PCI graphics card. I used what was known as a "TV-out" card, which had an extra output to connect to a standard television set. The onscreen result didn't look very nice and there was no audio output. And it was ugly: I had an S-Video cable running across my living room floor to my 19" Sony Trinitron CRT TV set.
|
||||
|
||||
I had the same sad result from Linux and Windows 98. After struggling with systems that never looked right, I gave up for a few years. Thankfully, today we have HDMI with its vastly better performance and standardized resolution, which makes an inexpensive home media center a reality.
|
||||
|
||||
My new media center entertainment computer is actually my old Ubuntu Linux desktop, which I recently replaced with something faster. The computer became too slow for work, but its AMD Phenom II X4 965 processor at 3.4GHz and 8GB of RAM are good enough for general browsing and video streaming.
|
||||
|
||||
Here are the steps I took to get the best possible performance out of this old system for its new role.
|
||||
|
||||
### Hardware
|
||||
|
||||
First, I removed unnecessary devices including a card reader, hard drives, DVD drive, and a rear-mounted USB card, and I added a PCI-Express WiFi card. I installed Ubuntu to a single solid-state drive (SSD), which can really improve the performance of any older system.
|
||||
|
||||
### BIOS
|
||||
|
||||
In the BIOS, I disabled all unused devices, such as floppy and IDE drive controllers. I disabled onboard video because I installed an NVidia GeForce GTX 650 PCI Express graphics card with an HDMI output. I also disabled onboard audio because the NVidia graphics card chipset provides audio.
|
||||
|
||||
### Audio
|
||||
|
||||
The Nvidia GeForce GTX audio device is listed in the GNOME Control Center's sound settings as a GK107 HDMI Audio Controller, so a single HDMI cable handles both audio and video. There's no need for an audio cable connected to the onboard audio output jack.
|
||||
|
||||
![Sound settings screenshot][2]
|
||||
|
||||
HDMI audio controller shown in GNOME sound settings.
|
||||
|
||||
### Keyboard and mouse
|
||||
|
||||
I have a wireless keyboard and mouse, both from Logitech. When I installed them, I plugged in both peripherals' USB receivers; they worked, but I often had signal-response problems. Then I discovered one was labeled a Unifying Receiver, which meant it can handle multiple Logitech input devices on its own. Logitech doesn't provide software to configure Unifying Receivers in Linux; fortunately, the open source utility [Solaar][3] does. Using a single receiver solved my input performance issues.
|
||||
|
||||
![Solaar][5]
|
||||
|
||||
Solaar Unifying Receiver interface.
|
||||
|
||||
### Video
|
||||
|
||||
It was initially hard to read fonts on my 47" flat-panel TV, so I enabled "Large Text" under Universal Access. I downloaded some wallpapers matching the TV's 1920x1080 resolution that look fantastic!
|
||||
|
||||
### Final touches
|
||||
|
||||
I needed to balance the computer's cooling needs with my desire for unimpeded entertainment. Since this is a standard ATX mini-tower computer, I made sure I had just enough fans with carefully configured temperature settings in the BIOS to reduce fan noise. I also placed the computer behind my entertainment console to further block fan noise but positioned so I can reach the power button.
|
||||
|
||||
The result is a simple machine that is not overly loud and uses only two cables—AC power and HDMI. It should be able to run any mainstream or specialized media center Linux distribution. I don't expect to do too much high-end gaming because that may require more processing horsepower.
|
||||
|
||||
![Showing Ubuntu Linux About page onscreen][7]
|
||||
|
||||
Ubuntu Linux About page.
|
||||
|
||||
![YouTube on the big screen][9]
|
||||
|
||||
Testing a YouTube video on the big screen.
|
||||
|
||||
I haven't yet installed a dedicated media center distribution of Linux like [Kodi][10]. For now, it is running Ubuntu Linux 18.04.1 LTS and is very stable.
|
||||
|
||||
This was a fun challenge to make the best of what I already had rather than buying new hardware. This is just one benefit of open source software. Eventually, I will probably replace it with a smaller, quieter system with a media-center case or another small box, but for now, it meets my needs quite well.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/11/old-linux-desktop-new-home-media-center
|
||||
|
||||
作者：[Alan Formy-Duval][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/alanfdoss
|
||||
[b]: https://github.com/lujun9972
|
||||
[2]: https://opensource.com/sites/default/files/uploads/soundsettings.png (Sound settings screenshot)
|
||||
[3]: https://pwr.github.io/Solaar/
|
||||
[5]: https://opensource.com/sites/default/files/uploads/solaar_interface.png (Solaar)
|
||||
[7]: https://opensource.com/sites/default/files/uploads/finalresult1.png (Showing Ubuntu Linux About page onscreen)
|
||||
[9]: https://opensource.com/sites/default/files/uploads/finalresult2.png (YouTube on the big screen)
|
||||
[10]: https://kodi.tv/
|
||||
@@ -0,0 +1,87 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (heguangzhi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (How to use multiple programming languages without losing your mind)
|
||||
[#]: via: (https://opensource.com/article/18/11/multiple-programming-languages)
|
||||
[#]: author: (Bart Copeland https://opensource.com/users/bartcopeland)
|
||||
[#]: url: ( )
|
||||
|
||||
How to use multiple programming languages without losing your mind
|
||||
======
|
||||
|
||||
如何使用多种编程语言而又不失理智
|
||||
======
|
||||
|
||||
多语言编程环境是一把双刃剑，既带来好处，也带来可能威胁组织的复杂性。
|
||||
|
||||
|
||||
|
||||
|
||||
如今，随着各种不同的编程语言的出现，许多组织已经变成了数字多语种组织。开源打开了一个语言和技术堆栈的世界，开发人员可以使用这些语言和技术堆栈来完成他们的任务，包括开发、支持遗留和现代软件应用。
|
||||
|
||||
与那些只说母语的人相比，通晓多种语言的人可以与数百万人交谈。在软件环境中，开发人员不会引入新的语言来达到特定的目的，也不会更好地交流。一些语言对于一项任务来说很棒，但是对于另一项任务来说却不行，因此使用多种编程语言可以让开发人员使用合适的工具来完成这项任务。这样，所有的开发都是多语种的；这只是野兽的本性。
|
||||
|
||||
|
||||
多语种环境的创建通常是渐进的和情景化的。例如，当一家企业收购一家公司时，它承担了公司的技术堆栈——包括其编程语言。或者，随着技术领导的改变，新的领导者可能会将不同的技术纳入其中。技术也有过时的时候，随着时间的推移，增加了组织必须维护的编程语言和技术的数量。
|
||||
|
||||
|
||||
多语言环境对企业来说是一把双刃剑，既带来好处，也带来复杂性和挑战。最终，如果这种情况得不到控制，多语言将会扼杀你的企业。
|
||||
|
||||
### Tricky technical tongue-twisters
|
||||
### 狡猾的技术绕口令
|
||||
|
||||
如果有多种不同的技术——编程语言、遗留的工具和新兴的技术堆栈——就有复杂性。工程师团队花更多的时间努力改进编程语言，包括许可证、安全性和依赖性。与此同时，管理层缺乏对代码合规性的监督，无法衡量风险。
|
||||
|
||||
|
||||
发生的情况是，企业有不同程度的编程语言质量和工具支持的高度可变性。当你需要和十几个人一起工作时，很难成为一种语言的专家。一个能流利地说法语和意大利语的人和一个能用八种语言串成几个句子的人在技能水平上有很大差异。开发人员和编程语言也是如此。
|
||||
|
||||
|
||||
随着更多编程语言的加入，困难只会增加，导致数字巴别塔的出现。
|
||||
|
||||
|
||||
答案是不要拿走开发人员工作所需的工具。添加新的编程语言可以建立他们的技能基础，并为他们提供合适的设备来完成他们的工作。所以，你想对你的开发者说“是”，但是随着越来越多的编程语言被添加到企业中，它们会拖累你的软件开发生命周期(SDLC)。在规模上，所有这些语言和工具都可能扼杀企业。
|
||||
|
||||
|
||||
企业应注意三个主要问题:
|
||||
|
||||
|
||||
1. **可见性:** 团队聚在一起进行项目，然后解散。应用程序已经发布，但从未更新——为什么要修复那些没有被破坏的东西？因此，当发现一个关键漏洞时，企业可能无法了解哪些应用程序受到影响，这些应用程序包含哪些库，甚至无法了解它们是用什么语言构建的。这可能导致昂贵的“勘探项目”，以确保漏洞得到适当解决。
|
||||
|
||||
2. **更新或编码:** 一些企业将更新和修复功能集中在一个团队中。其他人要求每个“比萨团队”管理自己的开发工具。无论是哪种情况，工程团队和管理层都要付出机会成本:这些团队没有编码新特性，而是不断更新和修复开源工具中的库，因为它们移动得如此之快。
|
||||
|
||||
3. **重新发明轮子:** 由于代码依赖性和库版本不断更新，当发现漏洞时，与应用程序原始版本相关联的工件可能不再可用。因此，许多开发周期都被浪费在试图重新创建一个可以修复漏洞的环境上。
|
||||
|
||||
|
||||
将你组织中的每种编程语言乘以这三个问题，开始时被认为是分子的东西突然看起来像珠穆朗玛峰。就像登山者一样，没有合适的设备和工具，你将无法生存。
|
||||
|
||||
|
||||
### 找到你的罗塞塔石碑
|
||||
|
||||
|
||||
一个全面的解决方案可以满足 SDLC 中企业及其个人利益相关者的需求。企业可以使用以下最佳实践创建解决方案:
|
||||
|
||||
|
||||
1. 监控生产中运行的代码，并根据应用程序中使用的标记组件(例如，常见漏洞和暴露组件)的风险做出响应。
|
||||
2. 定期接收更新以保持代码的最新和无错误。
|
||||
3. 使用商业开源支持来获得编程语言版本和平台的帮助，这些版本和平台已经接近尾声，并且不受社区支持。
|
||||
4. 标准化整个企业中的特定编程语言构建，以实现跨团队的一致环境，并最大限度地减少依赖性。
|
||||
5. 根据相关性设置何时触发更新、警报或其他类型事件的阈值。
|
||||
6. 为您的包管理创建一个单一的真相来源；这可能需要知识渊博的技术提供商的帮助。
|
||||
7. 根据您的特定标准，只使用您需要的软件包获得较小的构建分发。
|
||||
|
||||
使用这些最佳实践，开发人员可以最大限度地利用他们的时间为企业创造更多价值，而不是执行基本的工具或构建工程任务。这将在软件开发生命周期( SDLC )的所有环境中创建代码一致性。由于维护编程语言和软件包分发所需的资源更少，这也将提高效率和节约成本。这种新的操作方式将使技术人员和管理人员的生活更加轻松。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/11/multiple-programming-languages
|
||||
|
||||
作者：[Bart Copeland][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[heguangzhi](https://github.com/heguangzhi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/bartcopeland
|
||||
[b]: https://github.com/lujun9972
|
||||
@@ -0,0 +1,89 @@
|
||||
如何在 Linux 中为每个屏幕设置不同的壁纸
|
||||
======
|
||||
**简介：如果你想在 Ubuntu 18.04 或任何其他 Linux 发行版上使用 GNOME、MATE 或 Budgie 桌面环境在多个显示器上显示不同的壁纸，这个小工具将帮助你实现这一点。**
|
||||
|
||||
多显示器设置通常会在 Linux 上出现多个问题，但我不打算在本文中讨论这些问题。我有一篇关于 Linux 上多显示器支持的文章。
|
||||
|
||||
如果你使用多台显示器，也许你想为每台显示器设置不同的壁纸。我不确定其他 Linux 发行版和桌面环境，但是 [GNOME 桌面][1] 的 Ubuntu 本身并不提供此功能。
|
||||
|
||||
不要烦恼！在本教程中，我将向你展示如何使用 GNOME 桌面环境为 Linux 发行版上的每个显示器设置不同的壁纸。
|
||||
|
||||
### 在 Ubuntu 18.04 和其他 Linux 发行版上为每个显示器设置不同的壁纸
|
||||
|
||||
![Different wallaper on each monitor in Ubuntu][2]
|
||||
|
||||
我将使用一个名为 [HydraPaper][3] 的小工具在不同的显示器上设置不同的背景。HydraPaper 是一个基于 [GTK][4] 的应用，用于为 [GNOME 桌面环境][5]中的每个显示器设置不同的背景。
|
||||
|
||||
它还支持 [MATE][6] 和 [Budgie][7] 桌面环境。这意味着 Ubuntu MATE 和 [Ubuntu Budgie][8] 用户也可以从这个应用中受益。
|
||||
|
||||
#### 使用 FlatPak 在 Linux 上安装 HydraPaper
|
||||
|
||||
使用 [FlatPak][9] 可以轻松安装 HydraPaper。Ubuntu 18.04已 经提供对 FlatPaks 的支持，所以你需要做的就是下载应用文件并双击在 GNOME 软件中心中打开它。
|
||||
|
||||
你可以参考这篇文章来了解如何在你的发行版[启用 FlatPak 支持][10]。启用 FlatPak 支持后，只需从 [FlatHub][11] 下载并安装即可。
|
||||
|
||||
[Download HydraPaper][12]
|
||||
|
||||
#### 使用 HydraPaper 在不同的显示器上设置不同的背景
|
||||
|
||||
安装完成后，只需在应用菜单中查找 HydraPaper 并启动应用。你将在此处看到“图片”文件夹中的图像，因为默认情况下，应用会从用户的“图片”文件夹中获取图像。
|
||||
|
||||
你可以添加自己的文件夹来保存壁纸。请注意，它不会递归地查找图像。如果你有嵌套文件夹，它将只显示顶部文件夹中的图像。
|
||||
|
||||
![Setting up different wallpaper for each monitor on Linux][13]
|
||||
|
||||
使用 HydraPaper 很简单。只需为每个显示器选择壁纸，然后单击顶部的应用按钮。你可以轻松地用 HDMI 标识来识别外部显示器。
|
||||
|
||||
![Setting up different wallpaper for each monitor on Linux][14]
|
||||
|
||||
你还可以将选定的壁纸添加到“收藏夹”以便快速访问。这样做会将“最喜欢的壁纸”从“壁纸”选项卡移动到“收藏夹”选项卡。
|
||||
|
||||
![Setting up different wallpaper for each monitor on Linux][15]
|
||||
|
||||
你不需要在每次启动时启动 HydraPaper。为不同的显示器设置不同的壁纸后，设置将被保存，即使重新启动后你也会看到所选择的壁纸。这当然是预期的行为，但我想特别提一下。
|
||||
|
||||
HydraPaper 的一大缺点在于它的设计工作方式。你可以看到，HydraPaper 将你选择的壁纸拼接成一张图像并将其拉伸到屏幕上，给人的印象是每个显示器上都有不同的背景。当你移除外部显示器时，这将成为一个问题。
|
||||
|
||||
例如，当我尝试使用没有外接显示器的笔记本电脑时，它向我展示了这样的背景图像。
|
||||
|
||||
![Dual Monitor wallpaper HydraPaper][16]
|
||||
|
||||
很明显，这不是我所期望的。
|
||||
|
||||
#### 你喜欢它吗？
|
||||
|
||||
HydraPaper 使得在不同的显示器上设置不同的背景变得很方便。它支持超过两个显示器和不同的显示器方向。只有所需功能的简单界面使其成为那些总是使用双显示器的人的理想应用。
|
||||
|
||||
如何在 Linux 上为不同的显示器设置不同的壁纸？你认为 HydraPaper 是值得安装的应用吗？
|
||||
|
||||
请分享您的观点，另外如果你看到这篇文章，请在各种社交媒体渠道上分享，如 Twitter 和 [Reddit][17]。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/wallpaper-multi-monitor/
|
||||
|
||||
作者：[Abhishek Prakash][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/abhishek/
|
||||
[1]:https://www.gnome.org/
|
||||
[2]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/multi-monitor-wallpaper-setup-800x450.jpeg
|
||||
[3]:https://github.com/GabMus/HydraPaper
|
||||
[4]:https://www.gtk.org/
|
||||
[5]:https://itsfoss.com/gnome-tricks-ubuntu/
|
||||
[6]:https://mate-desktop.org/
|
||||
[7]:https://budgie-desktop.org/home/
|
||||
[8]:https://itsfoss.com/ubuntu-budgie-18-review/
|
||||
[9]:https://flatpak.org
|
||||
[10]:https://flatpak.org/setup/
|
||||
[11]:https://flathub.org
|
||||
[12]:https://flathub.org/apps/details/org.gabmus.hydrapaper
|
||||
[13]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/different-wallpaper-each-monitor-hydrapaper-2-800x631.jpeg
|
||||
[14]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/different-wallpaper-each-monitor-hydrapaper-1.jpeg
|
||||
[15]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/different-wallpaper-each-monitor-hydrapaper-3.jpeg
|
||||
[16]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/05/hydra-paper-dual-monitor-800x450.jpeg
|
||||
[17]:https://www.reddit.com/r/LinuxUsersGroup/
|
||||
@@ -1,83 +0,0 @@
|
||||
如何更换Ubuntu系统的GDM登录界面背景
|
||||
======
|
||||
Ubuntu 18.04 LTS桌面系统在登录，锁屏和解锁状态下，我们会看到一个纯紫色的背景。它是GDM(GNOME Display Manager)从ubuntu 17.04版本开始使用的默认背景。有一些人可能会不喜欢这个纯色的背景，想换一个酷一点,更吸睛的！如果是这样，你找对地方了。这篇简文将会告诉你如何更换Ubuntu 18.04 LTS的GDM登录界面的背景。
|
||||
### 更换Ubuntu的登录界面背景
|
||||
|
||||
这是Ubuntu 18.04 LTS桌面系统默认的登录界面
|
||||
|
||||
|
||||
不管你喜欢还是不喜欢，你总是会不经意在登录，解屏/锁屏的时面对它。别担心！你可以随便更换一个你喜欢的图片。
|
||||
|
||||
在Ubuntu上更换桌面壁纸和用户的资料图像不难。我们可以点击鼠标就搞定了。但更换解屏/锁屏的背景则需要修改文件 **ubuntu.css** 位于 **/usr/share/gnome-shell/theme**。
|
||||
|
||||
修改这个文件之前，最好备份一下它。这样我们可以避免出现问题时可以恢复它。
|
||||
|
||||
```
|
||||
$ sudo cp /usr/share/gnome-shell/theme/ubuntu.css /usr/share/gnome-shell/theme/ubuntu.css.bak
|
||||
```
|
||||
|
||||
修改文件ubuntu.css ：
|
||||
|
||||
```
|
||||
$ sudo nano /usr/share/gnome-shell/theme/ubuntu.css
|
||||
```
|
||||
在文件中找到关键字 **“lockDialogGroup”** ，如下行：
|
||||
|
||||
|
||||
```
|
||||
#lockDialogGroup {
|
||||
background: #2c001e url(resource:///org/gnome/shell/theme/noise-texture.png);
|
||||
background-repeat: repeat;
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
可以看到，GDM默认登录的背景图片是 **noise-texture.png**
|
||||
|
||||
现在修改为你自己的图片路径。也可以选择.jpg或.png格式的文件，两种格式的图片文件都是支持的。修改完成后的文件内容如下：
|
||||
|
||||
```
|
||||
#lockDialogGroup {
|
||||
background: #2c001e url(file:///home/sk/image.png);
|
||||
background-repeat: no-repeat;
|
||||
background-size: cover;
|
||||
background-position: center;
|
||||
}
|
||||
```
|
||||
|
||||
请注意ubuntu.css文件里这个关键字的修改，我把修改点加粗了.
|
||||
|
||||
你可能注意到，我原来的“… **url(resource:///org/gnome/shell/theme/noise-texture.png);** ” 修改为“ **…url(file:///home/sk/image.png);”**。也就是说，你可以把“… **url(resource** …” 修改为to “… **url(file**..”。
|
||||
|
||||
同时，你可以把参数“background-repeat:” 的值 **“repeat”** 修改为 **“no-repeat”** 来增加多行。你可以直接复制上面几行的修改到你的ubuntu.css文件，对应的修改为你的图片路径。
|
||||
|
||||
修改完成后，保存和关闭此文件。然后系统重启生效。
|
||||
|
||||
下面是GDM登录界面的最新背景图片：
|
||||
|
||||
|
||||
|
||||
|
||||
是不是很酷，你都看到了，更换GDM登录的默认背景很简单。你只需要修改ubuntu.css 文件中图片的路径然后重启系统。是不是很简单也很有意思.
|
||||
|
||||
你可以修改 **/usr/share/gnome-shell/theme** 目录下的文件 **gdm3.css** ，具体修改内容和修改结果和上面一样。同时记得修改前备份要修改的文件。
|
||||
|
||||
就这些了。如果有好的东东再分享了，请大家关注！
|
||||
|
||||
后会有期
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/how-to-change-gdm-login-screen-background-in-ubuntu/
|
||||
|
||||
作者：[SK][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[Guevaraya](https://github.com/guevaraya)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
92
选题模板.txt
92
选题模板.txt
@@ -1,43 +1,65 @@
|
||||
选题标题格式:
|
||||
选题标题格式：
|
||||
|
||||
原文日期 标题.md
|
||||
```
|
||||
原文日期 标题.md
|
||||
```
|
||||
|
||||
正文内容:
|
||||
其中：
|
||||
|
||||
标题
|
||||
=======
|
||||
|
||||
### 子一级标题
|
||||
|
||||
正文
|
||||
|
||||
#### 子二级标题
|
||||
|
||||
正文内容
|
||||
|
||||
|
||||
|
||||
### 子一级标题
|
||||
|
||||
正文内容 ： I have a [dream][1]。
|
||||
- 原文日期为该文章发表时的日期，采用 8 位数字表示
|
||||
- 标题需去除特殊字符，使用 `_` 替换。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: 原文地址
|
||||
|
||||
作者：[作者名][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: 作者介绍地址
|
||||
[1]: 引文链接地址
|
||||
正文内容：
|
||||
|
||||
说明:
|
||||
1. 标题层级很多时从 “##” 开始
|
||||
2. 引文链接地址在下方集中写
|
||||
```
|
||||
[#]: collector: (选题人 GitHub ID)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: subject: (文章标题)
|
||||
[#]: via: (原文 URL)
|
||||
[#]: author: (作者名 作者链接 URL)
|
||||
[#]: url: ( )
|
||||
|
||||
标题
|
||||
=======
|
||||
|
||||
### 子一级标题
|
||||
|
||||
正文
|
||||
|
||||
#### 子二级标题
|
||||
|
||||
正文内容
|
||||
|
||||
![][1]
|
||||
|
||||
### 子一级标题
|
||||
|
||||
正文内容 ： I have a [dream][2]。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: 原文 链接 URL
|
||||
|
||||
作者：[作者名][a]
|
||||
译者：[选题 ID][b]
|
||||
译者：[译者 ID](https://github.com/译者 ID)
|
||||
校对：[校对 ID](https://github.com/校对 ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: 作者链接 URL
|
||||
[b]: 选题链接 URL
|
||||
[1]: 图片链接地址
|
||||
[2]: 文内链接地址
|
||||
```
|
||||
|
||||
说明：
|
||||
|
||||
1. 标题层级很多时从 `##` 开始
|
||||
2. 图片链接和引文链接地址在下方集中写
|
||||
3. 因为 Windows 系统文件名有限制，所以文章名不要有特殊符号，如 `\/:*"<>|`，同时也不推荐全大写，或者其它不利阅读的格式
|
||||
4. 正文格式参照中文排版指北(https://github.com/LCTT/TranslateProject/blob/master/%E4%B8%AD%E6%96%87%E6%8E%92%E7%89%88%E6%8C%87%E5%8C%97.md)
|
||||
5. 我们使用的 markdown 语法和 github 一致，具体语法可参见 https://github.com/guodongxiaren/README 。而实际中使用的都是基本语法，比如链接、包含图片、标题、列表、字体控制和代码高亮。
|
||||
5. 我们使用的 markdown 语法和 GitHub 一致。而实际中使用的都是基本语法，比如链接、包含图片、标题、列表、字体控制和代码高亮。
|
||||
6. 选题的内容分为两类： 干货和湿货。干货就是技术文章，比如针对某种技术、工具的介绍、讲解和讨论。湿货则是和技术、开发、计算机文化有关的文章。选题时主要就是根据这两条来选择文章，文章需要对大家有益处，篇幅不宜太短，可以是系列文章，也可以是长篇大论，但是文章要有内容，不能有严重的错误，最好不要选择已经有翻译的原文。
|
||||
|
||||
Reference in New Issue
Block a user