u盘启动iso 开源_启动和维护开源项目

u盘启动iso 开源

Let's talk about how to start an open-source project? The process can be classified as in three phases,

让我们谈谈如何启动一个开源项目？ 该过程可以分为三个阶段，

Individual senses the need of the project: This is the phase when a developer thinks about developing open-source software that is required by the people in the community, by the corporates or by day to day users. He/She senses the need for a certain kind of software that should be available in the market so that everyone can benefit from the development.
个人感觉到项目的需要 ：这是开发人员考虑开发社区人员，公司或日常用户所需的开源软件的阶段。他/她感觉到需要市场上应有的某种软件，以便每个人都可以从开发中受益。
Announcing the intent to develop it to public: When a developer thinks of developing certain software there are multiple hurdles he might face and also have lack of resources; here resources can be termed as the time to invest, Tools Required and the utilities that might help for the development. In such cases, the developer thinks of releasing the Idea to the public wherein he proposes the technologies required, are of specialization and also the tools that are required to develop that particular idea into a fully functional project.
宣布有意向公众开发它 ：当开发人员想到开发某些软件时，他可能会面临多个障碍，也缺乏资源。这里的资源可以称为投资时间，所需的工具以及可能有助于开发的实用程序。在这种情况下，开发人员会考虑将创意发布给公众，在此他提出所需的技术，专业技术以及将特定创意发展为功能完善的项目所需的工具。
Source Code of a mature software is made available to the Public: No one is going to contribute until you show some intent and approach towards the development of the software. The developer tries to build software which will be modified and updated by the people in Community and the one who use it.
公开发布了成熟的软件的源代码 ：在您显示出开发软件的意图和方法之前，没有人会做出贡献。开发人员尝试构建软件，该软件将由社区中的人员和使用该软件的人员进行修改和更新。

Now, Let's talk about maintaining an Open-Source Project. This is a vast topic and needs to be understood very clearly.

现在，让我们谈谈维护一个开源项目。这是一个广泛的话题，需要非常清楚地理解。

Introduction:

介绍：

At the point when you maintain an open-source project, you're taking on an influential position. Regardless of whether you're the sole developer of an idea who released it to people in general for use and commitments, or you're dealing with a group and are maintaining one explicit part of the undertaking, you will be giving significant support of the larger developer community network.

在您维护一个开源项目时，您将发挥重要作用。无论您是某个创意的唯一开发者，是将其发布给一般人以供使用和承诺，还是与一个团队打交道并维护一项明确的事业，您都将为该创意提供大力支持更大的开发者社区网络。

While open-source contributions through demands from the community are vital for guaranteeing that product is as helpful as it tends to be for end clients, maintainers effect forming the general task. project maintainers are very engaged with the open-source software they oversee, from everyday association and advancement to interfacing with people in general and giving brief and successful feedback to the contributors.

尽管通过社区的需求来进行开源贡献对于保证产品像最终用户一样有用，但维护者却是总体任务。项目维护者非常喜欢他们所监管的开源软件，从日常关联和发展到与一般人进行交互，并向贡献者提供简短而成功的反馈。

This article will take you through certain tips for maintaining open source projects. Being a leader of an open-source project accompanies both specialized and non-specialized obligations to help encourage a client base and network around your undertaking. Assuming the job of a maintainer is a chance to gain from others, get involved in the venture the board, and watch your undertaking develop and change as your clients become potential contributors.

本文将带您了解维护开源项目的某些技巧。成为开源项目的负责人要承担专门和非专门的义务，以帮助鼓励您的客户群和围绕您的事业建立网络。假设维护人员的工作是从他人那里获利的机会，可以参与风险投资委员会，并在您的客户成为潜在的贡献者时观察您的事业发展和变化。

维护文件 (Maintain Documentation)

Documentation that is careful, efficient, and serves the expected communities of your project will help grow your client base. After some time, your client base will turn into the contributors to your open-source software.

谨慎，高效且可为项目预期社区提供服务的文档将有助于扩大客户群。一段时间后，您的客户群将成为您的开源软件的贡献者。

Since you'll be thoroughly considering the code you are making at any rate, and may even be writing down notes, it tends to be beneficial to fuse documentation as a feature of your advancement procedure while it is crisp in your psyche. You may even need to think about composing the documentation before the code, following the way of thinking of a documentation-driven advancement approach that document includes first and builds up those highlights after working out what they will do.

由于您将不惜一切代价来仔细考虑您正在编写的代码，甚至可能会写下笔记，因此将文档融合为升级过程的一个功能可能会有所帮助，而这却会使您的头脑清晰。您甚至可能需要考虑在代码之前编写文档的方式，遵循对文档驱动的高级方法的思考方式，该方法首先包括文档，然后在制定出重点之后将其突出显示。

Documentation can come in numerous structures and can target various crowds. As a component of your documentation, and relying upon the extent of your work, you may choose to do at least one of the accompanying,

文档可以采用多种结构，并且可以针对各种人群。作为文档的组成部分，并根据您的工作范围，您可以选择执行至少一项随附的内容，

A guide that will introduce the project to the public that you have developed.
将您开发的项目介绍给公众的指南。
You can even design tutorials to give people a brief walkthrough of what you’ve developed.
您甚至可以设计教程，以向人们简要介绍您所开发的内容。
The most required document is the one that contains the Frequently Asked Questions.
最需要的文件是包含“ 常见问题”的文件 。
There should be a document that must help the user Troubleshoot the errors.
应该有一个文档，必须帮助用户对错误进行故障排除 。
Video Tutorials can be of a plus point if provided.
如果提供了视频教程，可以加分。

These few documents will make your client base very strong.

这几份文件将使您的客户群非常强大。

整理反馈 (Organize Feedbacks)

Feedbacks are normally an approach to monitor or report bugs, or to demand new highlights to be added to the code. Open-source projects facilitating services like GitHub, GitLab and Bitbucket will give you an interface for yourself as well as other people to monitor feedbacks inside your vault. When discharging open-source code to people in general, you ought to hope to have feedbacks opened by the network of clients. Arranging and organizing feedbacks will give you a decent guide for upcoming work on your task.

反馈通常是一种监视或报告错误或要求将新的要点添加到代码中的方法。诸如GitHub，GitLab和Bitbucket之类的促进服务的开源项目将为您自己以及其他人提供一个界面，以监控您保管库内的反馈。通常，在向人们发布开源代码时，您应该希望能得到客户网络的反馈。安排和组织反馈将为您提供有关即将完成的任务的指导。

Since any client can record feedback, not all feedbacks will report bugs or be include demands; you may get questions using the feedback tracker tool, or you may get demands for littler improvements to the UI, for instance. It is ideal to arrange these feedbacks however much as could reasonably be expected and to be open to the clients who are making these feedbacks.

由于任何客户都可以记录反馈，因此并非所有反馈都会报告错误或包含需求。例如，您可能会使用反馈跟踪器工具来提问，或者可能需要对UI进行一些改进。理想的方式是尽可能合理地安排这些反馈，并向正在提供这些反馈的客户开放。

Feedbacks ought to speak to a solid task that should be done on the source code, and you should organize them as needs be. You and your community of developers will have a comprehension of the measure of time and can dedicate to documented feedbacks, and together you can work cooperatively to settle on choices and make a noteworthy updating. At the point when you realize you won't have the option to find a workable pace issue inside a brisk period, you can even now remark on the feedback to tell the client that you have perused the feedback and that you'll find a workable pace you can, and on the off chance that you can give a normal course of events to when you can take a step on the feedbacks once more.

反馈应该表明应该在源代码上完成的一项艰巨任务，并且您应该根据需要进行组织。您和您的开发人员社区将了解时间量度，并可以专门记录记录下来的反馈，并且您可以一起努力确定各种选择并进行重要的更新。当您意识到自己无法选择在快速的时间内找到可行的步调问题时，您甚至可以在反馈上注明，告诉客户您已经仔细阅读了反馈，就会发现可行的尽可能加快步伐，并在可能的情况下提供正常的活动，以便您可以再次采取措施。

For issues that are highlight requests or upgrades, you can ask the individual who recorded the feedback whether they can contribute code themselves. You can guide them to the CONTRIBUTORS.md record and some other significant documentation.

对于突出显示请求或升级的问题，您可以询问记录反馈的个人是否可以自己编写代码。您可以将它们引导至CONTRIBUTORS.md记录和一些其他重要文档。

维护社区 (Maintaining your Community)

Users are empowered through documentation, being receptive to feedback, and urging them to participate in the development, you are as of now well on your approach to working out the community around your open-source project. Users that you keep glad and who you treat as contributors will thus advance your project.

通过文档授权用户，接受反馈并敦促他们参与开发，到目前为止，您已经很好地掌握了围绕开源项目建立社区的方法。您感到高兴的用户以及将您视为贡献者的用户将因此促进您的项目。

Moreover, you can work to advance your project through different roads:

此外，您可以通过不同的途径来推进您的项目：

Blogging
写博客
Various diagrams
各种图
Walkthroughs
演练
Keeping up a mailing list
保持邮件列表
Being dynamic via web-based networking media channels
通过基于Web的网络媒体渠道保持动态
Working together with comparative or related projects
与比较或相关项目合作

You'll need to tailor your advancement to the extent of your task and the number of active team members and contributors you have working with you.

您需要根据任务的范围以及与您合作的活跃团队成员和贡献者的数量来调整自己的晋升。

As your community develops, you can give more spaces to contributors, users, and maintainers to connect.

随着社区的发展，您可以为贡献者，用户和维护者提供更多空间以进行连接。

Consider your user base and the extent of your project — including the number of individuals who are maintaining the project and the assets you have accessible — before revealing these potential spaces, and look for feedback from your community about what works for them.

在揭示这些潜在空间之前，请考虑您的用户群和项目范围(包括正在维护该项目的人员数量以及您可以访问的资产)，并从社区中获取对他们有用的反馈。

Most importantly, it is imperative to be thoughtful and give some adoration to the community. Being a potential maintainer isn't in every case simple, yet it will pay off for your project down the line.

最重要的是，必须深思熟虑并向社区提供一些崇拜。成为潜在的维护者并非总是那么简单，但是它将为您的项目带来回报。