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.

最重要的是，必須深思熟慮并向社區提供一些崇拜。成為潛在的維護者并非總是那么簡單，但是它將為您的項目帶來回報。