LinuxSuRen / LinuxSuRen/open-source-best-practice
【开源之夏攻略系列】怎么写好一份项目申请书 (视频提纲)
Nobody has claimed this yet.
- Dominant language
- Smarty
- Stars
- 416
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
# 【开源之夏攻略系列】怎么写好一份项目申请书
## 准备工作：项目申请书的重要性
- 提前在社区中提 PR 有多么重要
- 导师不回邮件我还有接着写吗
- 有的观点说，项目申请书几乎都差不多，最后变成看简历了
## 项目申请书可以有哪些参考
- 参考往期的优秀项目申请书
- 如何有效与如何与导师沟通来书写项目申请书
- 还有其它的参考方式吗？
## 项目申请书要写到什么程度
- 有的人技术细节写了十几页，我也要一起卷吗
- 已经和社区沟通的好了，还要特别的写项目申请书吗
## 开放的问题：您有哪些印象深刻的申请书细节吗（参与 or 听说都可以）
比如特别的社区经历、耳目一新的架构图，或者是一个小小的雏形？
我自己的小亮点：我在项目申请书中还写了一部分的项目后续维护计划。（实际上我也在结项后深夜现场debug了）
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the proposed video outline in the issue and review its open questions about application content, references, communication, and project detail. Confirm whether the video topic is still wanted and define the expected final deliverable; done should be a focused, agreed outline ready for production.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100