Debian开发者参考手册

5星 · 超过95%的资源需积分: 6 113 浏览量更新于2024-07-27 收藏 209KB PDF 举报

"Debian开发者参考指南" Debian Developer's Reference 是一本由 Debian 社区官方编写的详尽手册，旨在帮助潜在和现有的 Debian 开发者理解项目的工作流程、规范和最佳实践。该手册由 Adam DiCarlo（当前的维护者，aph@debian.org）、Christian Schwarz（schwarz@debian.org）和 Ian Jackson（ijackson@gnu.ai.mit.edu）等人共同编写，最新版本为2.8.8，发布于2001年7月20日。手册的版权遵循 GNU General Public License v2 或更高版本，这意味着任何人都可以自由地分发和修改这份文档，只要符合 GPL 的条款。GPL 是一个广泛使用的开源软件许可证，旨在保护软件的自由使用、分发和改进的权利。内容涵盖的范围非常广泛，包括但不限于以下几个关键知识点： 1. **文档的适用范围**：这部分解释了文档的目标读者群体，主要是那些希望成为 Debian 开发者或者已经参与 Debian 项目的人。它将引导读者了解 Debian 社区的规则、流程和技术细节。 2. **申请成为维护者**：这部分详细介绍了成为 Debian 软件包的维护者的步骤，包括如何提交申请、如何证明自己的技术能力以及如何与社区互动。这通常涉及对 Debian 社区规则的理解，对软件包维护的承诺，以及一定的编程和打包技能。 3. **开发流程**：手册会深入讨论 Debian 的软件打包过程，包括源码获取、修改、编译、测试和创建 Debian 包的详细步骤。此外，还会介绍如何使用 Debian 的工具如 dpkg 和 apt 进行软件管理。 4. **Debian 社区和贡献**：讲解如何参与到 Debian 社区的讨论、问题解决和决策过程中，包括邮件列表、IRC 频道和开发者的责任。 5. **质量控制和发布政策**：这部分阐述了 Debian 的质量保证体系，如 Debian Bug Tracking System ( BTS ) 的使用，以及软件包的生命周期和发布周期，包括 Debian 稳定版、测试版和不稳定版的差异。 6. **版本控制和源代码管理**：Debian 使用版本控制系统如 Git 来管理软件包源代码，这部分会解释如何使用这些工具进行协作和代码管理。 7. **版权和许可证**：在 Debian 中处理软件的版权和许可证是极其重要的，手册会指导开发者如何正确处理软件的版权信息和许可证兼容性问题。 8. **解决冲突和社区行为**：Debian 社区有其独特的社交规范，这部分会讲解如何处理潜在的冲突，以及如何维持一个积极和谐的开发环境。通过阅读 Debian Developer's Reference，开发者不仅可以学习到 Debian 系统的技术细节，还能深入了解开源社区的运作方式，这对于任何想要参与 Debian 项目或者对开源软件开发感兴趣的人员来说都是宝贵的资源。

Chapter 2. Applying to Become a Maintainer 4

several very important places we have to be careful about being compromised. Therefore, we need to verify

new maintainers before we can give them accounts on our servers and letting them upload packages.

Registration requires that the following information be sent in appropriate steps described at Checklist for

applicants (http://www.debian.org/devel/join/nm-checklist) after the initial contact to

<new-maintainer@debian.org>:

• Your name.

• Your preferred login name on master (eight characters or less), as well as the email address at which

you’d prefer to be subscribed to <debian-private@lists.debian.org> (typically this will

be either your primary mail address or your new debian.org address).

• A phone number where we can call you. Remember that the new maintainer team usually calls during

evening hours to save on long distance tolls. Please do not give a work number, unless you are

generally there in the evening.

• A statement of intention, that is, what package(s) you intend to work on, which Debian port you will

be assisting, or how you intend to contribute to Debian.

• A statement that you have read and agree to uphold the Debian Social Contract (http://www.

debian.org/social_contract).

• Some mechanism by which we can verify your real-life identity. For example, any of the following

mechanisms would sufﬁce:

– An OpenPGP key signed by any well-known signature, such as:

∗ Any current Debian developer you have met in real life.

∗ Any formal certiﬁcation service (such as Verisign, etc.) that veriﬁes your identity. A certi-

ﬁcation that veriﬁes your email address, and not you identity, is not sufﬁcient.

– Alternatively, you may identify yourself with a scanned (or physically mailed) copy of any

formal documents certifying your identity (such as a birth certiﬁcate, national ID card, U.S.

Driver’s License, etc.). If emailed, please sign the mail with your OpenPGP key.

If you do not have an OpenPGP key yet, generate one. Every developer needs a OpenPGP key in order to

sign and verify package uploads. You should read the manual for the software you are using, since it has

much important information which is critical to its security. Many more security failures are due to human

error than to software failure or high-powered spy techniques. See ‘Maintaining Your Public Key’ on page 7

for more information on maintaining your public key.

Debian uses the GNU Privacy Guard (package gnupg version 1 or better as its baseline standard. You

can use some other implementation of OpenPGP as well. Note that OpenPGP is a open standard based on

RFC 2440 (http://www.gnupg.org/rfc2440.html).

Chapter 2. Applying to Become a Maintainer 5

The recommended public key algorithm for use in Debian development work is the DSA (sometimes call

“DSS” or “DH/ElGamal”). Other key types may be used however. Your key length must be at least 1024

bits; there is no reason to use a smaller key, and doing so would be much less secure. Your key must be

signed with at least your own user ID; this prevents user ID tampering. gpg does this automatically.

Also remember that one of the names on your key must match the email address you list as the ofﬁcial main-

tainer for your packages. For instance, I set the maintainer of the developers-reference package to

“Adam Di Carlo <aph@debian.org>”; therefore, one of the user IDs on my key is that same value, “Adam

Di Carlo <aph@debian.org>”.

If your public key isn’t on public key servers such as pgp5.ai.mit.edu, please read the documentation

available locally in /usr/doc/pgp/keyserv.doc. That document contains instructions on how to put

your key on the public key servers. The New Maintainer Group will put your public key on the servers if it

isn’t already there.

Due to export restrictions by the United States government some Debian packages, including gnupg, are

located on ftp sites outside of the United States. You can ﬁnd the current locations of those packages at

ftp://ftp.debian.org/debian/README.non-US.

Some countries restrict the use of cryptographic software by their citizens. This need not impede one’s ac-

tivities as a Debian package maintainer however, as it may be perfectly legal to use cryptographic products

for authentication, rather than encryption purposes (as is the case in France). The Debian Project does not

require the use of cryptography qua cryptography in any manner. If you live in a country where use of cryp-

tography even for authentication is forbidden then please contact us so we can make special arrangements.

Once you have all your information ready, and your public key is available on public key servers, send a

message to <new-maintainer@debian.org> to register as an ofﬁcal Debian developer so that you

will be able to upload your packages. This message must contain your name and your valid e-mail address.

All the information discussed above is required after your Application Manager is assigned. Application

Manager is your agent in the registration process, and you can always ask him about the status of your

application. You can check the Application StatusBoard (http://nm.debian.org/) as well.

For more details, please consult New Maintainer’s Corner (http://www.debian.org/devel/join/

newmaint) at the Debian web site.

Once this information is received and processed, you should be contacted with information about your new

Debian maintainer account. If you don’t hear anything within a month, please send a followup message

asking if your original application was received. Do not re-send your original application, that will just con-

fuse the New Maintainer Group. Please be patient, especially near release points; mistakes do occasionally

happen, and people do sometimes run out of volunteer time.

2.3 Debian Mentors

The mailing list <debian-mentors@lists.debian.org> has been set up for novice maintainers

who seek help with initial packaging and other developer-related issues. Every new developer is invited to

剩余58页未读，继续阅读

kingarthor

粉丝: 0
资源: 3

Debian开发者参考手册

debian-8.11.1-amd64-DVD-1

Debian11-zsh-std-80g.ova

debian-reference.debian11.zh-cn.pdf

debian-reference.pdf

debian-reference.zh-cn.rar_debian

debian-reference.zh-cn.rar_Debian linux_debian

Debian Reference-开源

debian--code::blocks

debian-tor-hidden-service:debian-tor-隐藏服务

java红酒网站源码-debian-10-install-history:debian-10-install-history

最新资源