├── .editorconfig ├── .markdownlint.json ├── .vscode └── settings.json ├── LICENSE ├── README.md ├── google-season-of-docs ├── 2021 │ └── README.md └── README.md ├── google-summer-of-code ├── 2021 │ ├── README.md │ ├── application-instructions.md │ ├── long-description.md │ ├── organization-application.md │ └── project-ideas.md ├── 2022 │ ├── README.md │ ├── organization-profile.md │ ├── organization-questionnaire.md │ ├── program-application.md │ └── project-ideals.md ├── README.md ├── proposing-new-project-ideas.md └── wechaty-gsoc.png └── iscas-open-source-promotion-plan ├── 2020 ├── README.md └── apply.md ├── 2021 ├── README.md ├── apply-en.md ├── apply.md ├── mentor-final-term.md ├── mentor-mid-term.md ├── mentor-plan.md ├── org-admin-be-better.md ├── org-admin-final-term.md ├── org-admin-first-meeting.md ├── org-admin-mid-term.md ├── org-admin-prepare.md ├── project-application-template.md ├── student-final-term.md ├── student-mid-term.md └── student-plan.md ├── 2022 ├── mentors.md ├── profile.md ├── projects.md ├── screenshot_add_new_mentor.png └── screenshot_add_new_project.png ├── README.md └── template ├── announcement-mid-term-meeting-template.txt ├── announcement-mid-term-report-template.txt ├── fan-tan-mid-report-mentor-template.txt ├── fan-tan-mid-report-student-template.txt ├── fan-tan-mid-report-video-template.txt ├── final-term-template.md ├── mentor-final-term-template.md ├── mentor-mid-term-template.md ├── mentor-weekly-report-template.md ├── mid-term-template.md └── student-weekly-report-template.md /.editorconfig: -------------------------------------------------------------------------------- 1 | # Editor configuration, see http://editorconfig.org 2 | root = true 3 | 4 | [*] 5 | charset = utf-8 6 | indent_style = space 7 | indent_size = 2 8 | end_of_line = lf 9 | insert_final_newline = true 10 | trim_trailing_whitespace = true 11 | 12 | [*.md] 13 | max_line_length = 0 14 | trim_trailing_whitespace = false 15 | 16 | # 4 tab indentation 17 | [Makefile] 18 | indent_style = tab 19 | indent_size = 4 20 | -------------------------------------------------------------------------------- /.markdownlint.json: -------------------------------------------------------------------------------- 1 | { 2 | "default": true, 3 | "no-trailing-punctuation": { 4 | "punctuation": ".,;:!" 5 | }, 6 | "MD013": false, 7 | "MD033": { 8 | "allowed_elements": ["dl", "dt", "dd", "code", "var", "cite"] 9 | }, 10 | "first-line-h1": false, 11 | "no-hard-tabs": true, 12 | "no-trailing-spaces": { 13 | "br_spaces": 2 14 | } 15 | } 16 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "typescript.tsdk": "./node_modules/typescript/lib", 3 | 4 | "editor.fontFamily": "'Fira Code iScript', Consolas, 'Courier New', monospace", 5 | "editor.fontLigatures": true, 6 | 7 | "editor.tokenColorCustomizations": { 8 | "textMateRules": [ 9 | { 10 | "scope": [ 11 | //following will be in italics (=Pacifico) 12 | "comment", 13 | // "entity.name.type.class", //class names 14 | "keyword", //import, export, return… 15 | "support.class.builtin.js", //String, Number, Boolean…, this, super 16 | "storage.modifier", //static keyword 17 | "storage.type.class.js", //class keyword 18 | "storage.type.function.js", // function keyword 19 | "storage.type.js", // Variable declarations 20 | "keyword.control.import.js", // Imports 21 | "keyword.control.from.js", // From-Keyword 22 | "entity.name.type.js", // new … Expression 23 | "keyword.control.flow.js", // await 24 | "keyword.control.conditional.js", // if 25 | "keyword.control.loop.js", // for 26 | "keyword.operator.new.js", // new 27 | ], 28 | "settings": { 29 | "fontStyle": "italic", 30 | }, 31 | }, 32 | { 33 | "scope": [ 34 | //following will be excluded from italics (My theme (Monokai dark) has some defaults I don't want to be in italics) 35 | "invalid", 36 | "keyword.operator", 37 | "constant.numeric.css", 38 | "keyword.other.unit.px.css", 39 | "constant.numeric.decimal.js", 40 | "constant.numeric.json", 41 | "entity.name.type.class.js" 42 | ], 43 | "settings": { 44 | "fontStyle": "", 45 | }, 46 | } 47 | ] 48 | }, 49 | 50 | "files.exclude": { 51 | "dist/": true, 52 | "doc/": true, 53 | "node_modules/": true, 54 | "package/": true, 55 | }, 56 | "alignment": { 57 | "operatorPadding": "right", 58 | "indentBase": "firstline", 59 | "surroundSpace": { 60 | "colon": [1, 1], // The first number specify how much space to add to the left, can be negative. The second number is how much space to the right, can be negative. 61 | "assignment": [1, 1], // The same as above. 62 | "arrow": [1, 1], // The same as above. 63 | "comment": 2, // Special how much space to add between the trailing comment and the code. 64 | // If this value is negative, it means don't align the trailing comment. 65 | } 66 | }, 67 | "editor.formatOnSave": false, 68 | "python.pythonPath": "python3", 69 | "eslint.validate": [ 70 | "javascript", 71 | "typescript", 72 | ], 73 | "cSpell.words": [ 74 | "Gitter", 75 | "Wechaty", 76 | "appid", 77 | "botie", 78 | "huan", 79 | "ioscat", 80 | "ipad", 81 | "lcov", 82 | "lijiarui", 83 | "logonoff", 84 | "padchat", 85 | "padplus", 86 | "padpro", 87 | "pagepath", 88 | "portfinder", 89 | "qrcode", 90 | "removee", 91 | "ruirui", 92 | "thumbnailurl", 93 | "wechat", 94 | "weixin", 95 | "wxwork", 96 | "zbeekman", 97 | "zixia" 98 | ], 99 | } 100 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright 2020 Wechaty Contributors 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Summer of Wechaty 2 | 3 | Summer of Wechaty is ... an community event organized by Wechaty organization for students oss coders, tech writers, mentored by community contributors to join the following summer programs: 4 | 5 | 1. [Google Summer of Code (GSoC)](google-summer-of-code/) 6 | 1. [Google Season of Docs (GSoD)](google-season-of-docs/) 7 | 1. [ISCAS Open Source Promotion Plan](iscas-open-source-promotion-plan/) 8 | 9 | ### Resource 10 | 11 | - [Wechaty Introdcution](https://docs.google.com/presentation/d/1u5I0fUG5Fb1mnTLphDTckACJIdxGkuWXDai0Oo4vJvs/edit#slide=id.gfac80a92a2_0_0) 12 | - [Wechaty Best Practice](https://docs.google.com/presentation/d/1rWd7aLozgPFyPiSbyxqw1GeGV2-NCGRKvDOUcq9VYcw/edit#slide=id.gec336ad374_1_0) 13 | - [Wechaty 社区开源协作最佳实践指南](https://wechaty.js.org/2021/06/23/the-wechaty-way/) 14 | - [OSPP（开源之夏）指导手册 - 2021](https://wechaty.js.org/2021/06/24/summer-wechaty-guide/) 15 | - [Google Season Of Docs (GSoD) Guide](https://wechaty.js.org/2021/07/10/google-season-of-docs-guide/) 16 | 17 | ## Apply Mentor & Publish Projects (Ideas List) 18 | 19 | Google Form: 20 | 21 | Any [Wechaty Contributors](https://wechaty.js.org/contributors/) are welcome to apply! 22 | 23 | ## Select Students 24 | 25 | - Google Summer of Code Guides - Selecting a Student - 26 | - Tips for finding the “right” GSoC student for your org - 27 | 28 | ## WeChat Room 29 | 30 | 1. 不同年份的入选同学、未入选同学、社区导师均共用此群。 31 | 1. 所有技术相关问题全部在此群内讨论，鼓励未入选同学也能以个人开发者的身份参与到对应项目中。 32 | 1. 所有社区活动、沙龙分享等信息均在此群内向同学们同步。 33 | 1. 后续SoC相关Issue和PR将会由OSS BOT转发到群中。 34 | 1. 群内由社区工作人员同步活动奖金、提交代码规范、答辩规范等重要信息，并可针对这些问题进行讨论和答疑。 35 | 1. 每年 Summer of Wechaty 活动继续将其作为核心讨论群，不另外设置新群，旨在让往届校友同学也能参与提出意见或指导开发。 36 | 1. 此群长期存在。 37 | 38 | > Drafted by [@rickyyin98](https://github.com/rickyyin98) 39 | 40 | ## OSPP 学生开发者工作指导 41 | 42 | 原始博客见： [OSPP（开源之夏）指导手册 - 2021](https://wechaty.js.org/2021/06/24/summer-wechaty-guide/) 43 | 44 | Wechaty 的项目 Issue 作为本次同学和导师通知的主要渠道，请所有同学在入选后，务必完成第一件事： 45 | **在项目清单 Issue 下面，把所有同学和导师需要完成的工作，以 checklist 的形式回复到 Issue 下面，方便后续同学和导师完成相关工作，完成后在 Comment 中打钩确认** 46 | 47 | Wechaty 社区秉持开源开放的的原则，所有会议记录、在线会议、阶段性报告等视频、文档资料都会对社区完全开放。对自己的视频、文档资料介意开放的同学，请谨慎考虑加入。 48 | 49 | 参与项目的同学完成 **日常工作** 和 **阶段性工作**，具体如下： 50 | 51 | ### 学生日常工作 52 | 53 | 学生每周在 issue 下回复进度报告。 54 | 55 | 日常工作以 OSPP 2020 的优秀学生突出贡献奖获得者[江姗姗](https://wechaty.js.org/contributors/univerone/)的周报告和导师总结为例，详见[编写一个“每日一句”插件](https://github.com/wechaty/summer-of-wechaty/issues/10) 56 | 57 | 报告模板参考：[student-weekly-report-template](iscas-open-source-promotion-plan/template/student-weekly-report-template.md) 58 | 59 | ### 学生阶段性工作 60 | 61 | - [期初报告要求](iscas-open-source-promotion-plan/2021/student-plan.md) 62 | - [期中报告要求](iscas-open-source-promotion-plan/2021/student-mid-term.md) 63 | - 期中答辩(Mid-term Demo Day) 64 | - [期末报告要求](iscas-open-source-promotion-plan/2021/student-final-term.md) 65 | - 期末答辩(Final-term Demo Day) 66 | 67 | ## OSPP 导师工作指导 68 | 69 | 参与项目的导师需要分别完成 **日常工作** 和 **阶段性工作**，具体如下： 70 | 71 | ### 导师日常工作 72 | 73 | 导师每周在 issue 下根据学生的进度报告进行评分。 74 | 75 | 日常工作以 OSPP 2020 的优秀学生突出贡献奖获得者[江姗姗](https://wechaty.js.org/contributors/univerone/)的周报告和导师总结为例，详见[编写一个“每日一句”插件](https://github.com/wechaty/summer-of-wechaty/issues/10) 76 | 77 | 报告模板参考：[mentor-weekly-report-template](iscas-open-source-promotion-plan/template/mentor-weekly-report-template.md) 78 | 79 | ### 导师阶段性工作 80 | 81 | - [期初报告评审](iscas-open-source-promotion-plan/2021/mentor-plan.md) 82 | - [期中报告评审](iscas-open-source-promotion-plan/2021/mentor-mid-term.md) 83 | - 期中答辩(Mid-term Demo Day) 84 | - [期末报告评审](iscas-open-source-promotion-plan/2021/mentor-final-term.md) 85 | - 期末答辩(Final-term Demo Day) 86 | 87 | ## Organization Administrators 工作指导 88 | 89 | ### 工具包 90 | 91 | 1. 社区 Repo: 92 | 1. 社区通知 Issue： 93 | 1. 社区微信群：***Summer of Wechaty - SoW*** 94 | 1. 社区 Org Admin 组委会群：***Summer of Wechaty Org Admin SoW*** 95 | 1. Wechaty Contributor 群：***Wechaty Contributors*** 96 | 1. 所有发布到 Wechaty 的博客需要打上如下标签： 97 | - ospp-admin 98 | - summer-202X （202X 改为当前的年份） 99 | - summer-of-wechaty 100 | - ospp 101 | - ospp-202X （202X 改为当前的年份） 102 | 103 | ### Org Admin 阶段性工作 104 | 105 | - [筹备阶段](iscas-open-source-promotion-plan/2021/org-admin-prepare.md) 106 | - [期初见面会](iscas-open-source-promotion-plan/2021/org-admin-first-meeting.md) 107 | - [期中报告状态收集 & 答辩](iscas-open-source-promotion-plan/2021/org-admin-mid-term.md) 108 | - [期末报告状态收集 & 答辩](iscas-open-source-promotion-plan/2021/org-admin-final-term.md) 109 | - [复盘 & 展望](iscas-open-source-promotion-plan/2021/org-admin-be-better.md) 110 | 111 | ## Contact us 112 | 113 | You can [join our Gitter](https://gitter.im/wechaty/wechaty) network if you aren’t already a member 114 | 115 | ## Organization Administrators 116 | 117 | - [Huan](https://wechaty.js.org/contributors/huan), Tencent TVP of Chatbot, Creator of Wechaty 118 | - [Rui](https://pre-angel.com/peoples/jiarui-li/), Microsoft AI [MVP](https://mvp.microsoft.com/en-us/PublicProfile/5003226), Co-creator of Wechaty 119 | - [Jing](https://wechaty.js.org/contributors/wj-mcat), Author of [Python Wechaty](https://github.com/wechaty/python-wechaty) 120 | - [Yuan](https://wechaty.js.org/contributors/windmemory), CTO of Juzi.BOT, Creator of Wechaty Puppet [WXWork](https://wechaty.js.org/docs/puppet-services/wxwork) 121 | - [Hao](https://wechaty.js.org/contributors/rickyyin98), CMO of Juzi.BOT 122 | 123 | ## Copyright & License 124 | 125 | - Code & Docs © 2020-now Wechaty Contributors 126 | - Code released under the Apache-2.0 License 127 | - Docs released under Creative Commons 128 | -------------------------------------------------------------------------------- /google-season-of-docs/2021/README.md: -------------------------------------------------------------------------------- 1 | ## Google Season of Docs 2 | 3 | - [GitHub Milestone](https://github.com/wechaty/summer-of-wechaty/milestone/4) 4 | 5 | TBW 6 | -------------------------------------------------------------------------------- /google-season-of-docs/README.md: -------------------------------------------------------------------------------- 1 | ## Google Season of Docs 2 | 3 | Google Season of Docs (GSoD) bring open source and technical writer communities together, to the benefit of both. Together we raise awareness of open source, of docs, and of technical writing. 4 | 5 | > Fostering open source collaboration with technical writers 6 | 7 | - 8 | 9 | ## Years 10 | 11 | - [2021](2021/) 12 | 13 | ## Issues 14 | 15 | - Google Season of Docs Application [#72](https://github.com/wechaty/summer-of-wechaty/issues/72) 16 | 17 | ## Links 18 | 19 | - [Five web analytics metrics for technical writers](https://techwhirl.com/five-web-analytics-metrics-for-technical-writers/) 20 | - [How to Become a Technical Writer: A Beginner’s Guide](https://www.instructionalsolutions.com/blog/become-a-technical-writer) 21 | - [Google Technical Writing Courses for Engineers](https://developers.google.com/tech-writing/overview) 22 | - [The documentation system](https://documentation.divio.com/) 23 | -------------------------------------------------------------------------------- /google-summer-of-code/2021/README.md: -------------------------------------------------------------------------------- 1 | ## Google Summer of Code in Wechaty 2021 2 | 3 | - Project Ideas List: [project-ideas.md](project-ideas) 4 | - Organization Application: [organization-application.md](organization-application) 5 | - Google Summer of Code (GSoC) 2021: 6 | -------------------------------------------------------------------------------- /google-summer-of-code/2021/application-instructions.md: -------------------------------------------------------------------------------- 1 | ## Prerequisites 2 | 3 | 1. Read [Six Lines Of Code. Two MVPs. One Chatbot.](https://wechaty.js.org/2020/11/10/six-lines-code-two-ai-mvps-one-chatbot/) 4 | 1. [Get started with Wechaty](https://wechaty.js.org/2021/02/06/wechaty-getting-started-without-leave-your-browser/) 5 | 1. [Join our Gitter Channel](https://gitter.im/wechaty/wechaty) 6 | 1. [Run Wechaty with Whatsapp](https://wechaty.js.org/2021/02/15/publishment-of-wechaty-whatapp-puppet/) 7 | 1. Read [Introducing Wechaty Puppet Service (Providers)](https://wechaty.js.org/2021/01/14/wechaty-puppet-service/) 8 | 1. Read [Gource Visualization for Wechaty](https://wechaty.js.org/2021/02/14/gource-visualizing-wechaty-history/) 9 | 10 | ## About You 11 | 12 | 1. Who are you? What are you studying? 13 | 1. What exactly do you intend to do? What will not be done? 14 | 1. Why are you the right person for this task? 15 | 1. To what extent are you familiar with the software you’re proposing to work with? Have you used it? Have you read the source? Have you modified the source? 16 | 1. How many hours are you going to work on this a week? 10? 20? 30? 40? 17 | 1. Do you have other commitments that we should know about? If so, please suggest a way to compensate if it will take much time away from Summer of Code. 18 | 19 | ## Proposed Schedule 20 | 21 | During each phase, please make it clear whether the code will be ready to be submitted for inclusion. Also, ensure that your code will be available for review almost every day. Do not work long periods (more than 2-3 days) without submitting code to the git repository for your project. You should normally commit code to Github every day or almost every day (except weekends). 22 | 23 | Write down your plan in detail about what will you do during the following periods? 24 | 25 | 1. March (Application Period) 26 | 1. April (Acceptance Waiting Period) 27 | 1. May (Community Bonding Period) 28 | 1. June (Coding period 1) 29 | 1. July (Coding period 2) 30 | 1. Aug (Coding period 3) 31 | -------------------------------------------------------------------------------- /google-summer-of-code/2021/long-description.md: -------------------------------------------------------------------------------- 1 | ## Why Wechaty? 2 | 3 | Chatbot applications streamline interactions between people and services, enhancing customer experience. At the same time, they offer companies new opportunities to improve the customer engagement process and operational efficiency by reducing the typical cost of customer service. 4 | 5 | ## Chatbot SDK 6 | 7 | Wechaty is a Conversational RPA (Robotic Process Automation) SDK for Chatbot Makers which can create a bot in 6 lines of JavaScript, Python, Go, Java, .NET, PHP, and Scala, with cross-platform support including Linux, Windows, macOS, and Docker, on top of the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 8 | 9 | ## Voice of Developers 10 | 11 | "Wechaty is a great solution, I believe there would be much more users recognize it." [link](https://github.com/Wechaty/wechaty/pull/310#issuecomment-285574472) 12 | — @Gcaufy, Tencent Engineer, Author of [WePY](https://github.com/Tencent/wepy) 13 | 14 | "太好用，好用的想哭" 15 | — @xinbenlv, Google Engineer, Founder of HaoShiYou.org 16 | 17 | "最好的微信开发库" [link](http://weibo.com/3296245513/Ec4iNp9Ld?type=comment) 18 | — @Jarvis, Baidu Engineer 19 | 20 | "Wechaty让运营人员更多的时间思考如何进行活动策划、留存用户，商业变现" [link](http://mp.weixin.qq.com/s/dWHAj8XtiKG-1fIS5Og79g) 21 | — @lijiarui, Founder & CEO of Juzi.BOT. 22 | 23 | "If you know js ... try Wechaty, it's easy to use." 24 | — @Urinx Uri Lee, Author of [WeixinBot(Python)](https://github.com/Urinx/WeixinBot) 25 | 26 | "Wechaty is a good project, I hope it can continue! Therefore, I became a contributor in the open collective." 27 | — [@Simple](https://github.com/mrwhh) 28 | 29 | ### Join Us 30 | 31 | Wechaty is used in many Chatbot projects by thousands of developers. If you want to talk with other developers, please feel free to join [Gitter](https://gitter.im/wechaty/wechaty) 32 | -------------------------------------------------------------------------------- /google-summer-of-code/2021/organization-application.md: -------------------------------------------------------------------------------- 1 | ## GSoC 2021 Organization Application 2 | 3 | - [Org Application](https://google.github.io/gsocguides/mentor/org-application) 4 | 5 | > Complete the Organization Application to let Google administrators know why Wechaty would be a good fit for this year's Google Summer of Code. 6 | 7 | ## Public Profile 8 | 9 | ### Website URL 10 | 11 | 12 | 13 | ### Tagline 14 | 15 | Conversational RPA SDK for building WeChat/Whatsapp chatbots in 6 lines of code. 16 | 17 | ### Short description 18 | 19 | Wechaty is a Conversational RPA SDK for chatbot makers that can create a bot in 6 lines of code with the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 20 | 21 | ### Long description 22 | 23 | #### Why Wechaty? 24 | 25 | Chatbot applications streamline interactions between people and services, enhancing customer experience. At the same time, they offer companies new opportunities to improve the customer engagement process and operational efficiency by reducing the typical cost of customer service. 26 | 27 | ### Chatbot SDK 28 | 29 | Wechaty is a Conversational RPA (Robotic Process Automation) SDK for Chatbot Makers which can create a bot in 6 lines of JavaScript, Python, Go, Java, .NET, PHP, and Scala, with cross-platform support including Linux, Windows, macOS, and Docker, on top of the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 30 | 31 | ### Logo 32 | 33 | [![Wechaty](https://wechaty.js.org/img/wechaty-logo.svg)](https://github.com/wechaty) 34 | 35 | ```md 36 | [![Wechaty](https://wechaty.js.org/img/wechaty-logo.svg)](https://github.com/wechaty) 37 | ``` 38 | 39 | ### Primary Open Source License 40 | 41 | Apache-2.0 42 | 43 | ### Organization Category 44 | 45 | Social / Communications 46 | 47 | ### Technology Tags 48 | 49 | - TypeScript 50 | - gRPC 51 | - Node.js 52 | - Reverse Engineering 53 | - Cloud 54 | 55 | ### Topic Tags 56 | 57 | - Robotics Process Automation 58 | - Conversational User Interface 59 | - Instant Messaging 60 | - Machine Learning 61 | - Chatbot 62 | 63 | ### Ideas List 64 | 65 | 66 | 67 | ## Descriptions 68 | 69 | ### Short Description 70 | 71 | Wechaty is a Conversational RPA SDK for chatbot makers that can create a bot in 6 lines of code with the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 72 | 73 | ### [Long Description](long-description.md) 74 | 75 | Wechaty is a Conversational RPA (Robotic Process Automation) SDK for Chatbot Makers which can create a bot in 6 lines of JavaScript, Python, Go, Java, .NET, PHP, and Scala, with cross-platform support including Linux, Windows, macOS, and Docker, on top of the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 76 | 77 | ## Proposals 78 | 79 | ### Application Instructions 80 | 81 | [Application Instructions](application-instructions.md) 82 | 83 | ### Proposal Tags 84 | 85 | - puppet 86 | - machine-learning 87 | - rust 88 | - restful-api 89 | - cli 90 | - angular 91 | - assistant 92 | - database 93 | - conversational-user-interface 94 | - gaming 95 | 96 | ## Contact Methods 97 | 98 | ### Chat 99 | 100 | 101 | 102 | ### Mailing List 103 | 104 | 105 | 106 | ### General Email 107 | 108 | 109 | 110 | ## Links 111 | 112 | ### Twitter URL 113 | 114 | 115 | 116 | ### Blog URL 117 | 118 | 119 | 120 | ### Why does your org want to participate in Google Summer of Code? 121 | 122 | GSoC has attracted many students to join the open-source project like Wechaty, and they may become long-term contributors. Open-source projects always require both of new and old developers, so GSoC is a important program for us to recruiting young developers. 123 | 124 | ### What would your org consider to be a successful summer? 125 | 126 | Most projects could be completed successfully. The students are happy to work on Wechaty and would love to tell their friends. The user community is excited about the results, and at least one newcomer continues to contribute after the GSoC summer. 127 | 128 | ### How many potential mentors have agreed to mentor this year? 129 | 130 | 20+ 131 | 132 | ### How will you keep mentors engaged with their students? 133 | 134 | We use Gitter, WeChat, and GitHub as our main communication channels with Zoom meetings when needed. In order to monitor the whole process, we will have meeting once a week to discuss GSoC, so that problems can be discovered as early as possible. Each student will have at least two mentors to avoid problems of disappearing mentors. In addition, the GSoC administrator will supervise the entire project. 135 | 136 | Many of the mentors have 2+ years of experiences of the Wechaty project, they would love to have new and young contributors to join. 137 | 138 | ### How will you help your students stay on schedule to complete their projects? 139 | 140 | Our mentors are usually on our Gitter channel (We have connected the Gitter with WeChat) and they can be reached at most of the time, so it will not be hard to schedule communications between mentors and students. Our GSoC administrators (some are also mentors) will track the progress of each project at a higher level. We use GitHub for code management so we can easily monitor progress by Issues and PRs. 141 | 142 | In order to be selected, students need to complete an basic task from GitHub. This requires them to build and start looking at the code, which makes students more confident about future tasks, and our mentors also have the opportunity to understand how students work. 143 | 144 | All students are required to submit progress reports on the GitHub issues under their projects every week, and to submit/update GitHub Issues/PRs every week. This will help find difficulties before the student is really lost. 145 | 146 | ### How will you get your students involved in your community during GSoC? 147 | 148 | Before students apply for GSoC, they are welcome to join our contributor program. In the contributor program, we encourage students to participate in discussions on Gitter and WeChat, creating their own open-source project for a MVP, or post blogs to share their thoughts about our project. 149 | 150 | Our mentors will encourage students to introduce their ideas to the community to get involved. We believe that students need to do more than just write code. They need to interact with the community by proposing solutions and iterating them until they reach a community consensus. 151 | 152 | ### How will you keep students involved with your community after GSoC? 153 | 154 | We are always encourage new contributors to play more with our project because it will be a funny journey for chatbot builders. If a contributor start using Wechaty as their chatbot SDK solution, they will mostly like to find new feature request, and bugs. 155 | 156 | Our contributors/committers community have 160+ peoples and it's a great place to sharing ideas, talking about the new features, and bug fixes. All GSoC students will be part of the community, and we will try to help them stay motivated. We believe that an open and active community is one of the best assets to retain contributors. 157 | 158 | ### Has your org been accepted as a mentor org in Google Summer of Code before? 159 | 160 | No 161 | 162 | ### What year was your project started? 163 | 164 | 2016 165 | 166 | ### Where does your source code live? 167 | 168 | 169 | 170 | ### Is your organization part of any government? 171 | 172 | No 173 | 174 | > Inspired by [LibreOffice at Google Summer of Code](https://wiki.documentfoundation.org/Development/GSoC) 175 | -------------------------------------------------------------------------------- /google-summer-of-code/2021/project-ideas.md: -------------------------------------------------------------------------------- 1 | # GSoC 2021 Wechaty Ideas Page 2 | 3 | ![Wechaty GSoC](../wechaty-gsoc.png) 4 | 5 | This page aggregates project ideas for Google Summer of Code 2021. See more information about this project and applications on the [Wechaty Google Summer of Code page](../). 6 | 7 | ## Introduction 8 | 9 | Below you can find project ideas which have been proposed for this year. New ideas may be proposed by interested mentors or students. Project ideas without potential mentors will be considered though applicants may need to work with the community and GSoC org admins to find mentors. To add a new project idea, see: [proposing project ideas](../proposing-new-project-ideas.md) . 10 | 11 | This ideas page was moved to 12 | -------------------------------------------------------------------------------- /google-summer-of-code/2022/README.md: -------------------------------------------------------------------------------- 1 | ## Google Summer of Code in Wechaty 2022 2 | 3 | - Organization Profile: [organization-profile.md](organization-profile.md) 4 | - Organization Questionnaire: [organization-questionnaire.md](organization-questionnaire.md) 5 | - Organization Application: [program-application.md](program-application.md) 6 | - Project Ideas List: [project-ideals.md](project-ideals.md) 7 | 8 | ## Wechaty Organization Administrators 9 | 10 | - [Huan](https://wechaty.js.org/contributors/huan), Tencent TVP of Chatbot, Creator of Wechaty 11 | - [Rui](https://pre-angel.com/peoples/jiarui-li/), Microsoft AI [MVP](https://mvp.microsoft.com/en-us/PublicProfile/5003226), Co-creator of Wechaty 12 | - [Xiaoquan](https://www.xiaoquankong.ai/), [Google Developer Expert in Machine Learning](https://developers.google.com/community/experts/directory/profile/profile-xiaoquan-kong) 13 | - [Rohitesh Kumar Jain](https://github.com/Rohitesh-Kumar-Jain), CSE Junior | GSoC'21 | GSoD'20 14 | -------------------------------------------------------------------------------- /google-summer-of-code/2022/organization-profile.md: -------------------------------------------------------------------------------- 1 | ## Website URL for organization 2 | 3 | https://wechaty.js.org/ 4 | 5 | ## Logo 6 | 7 | > Your organization logo must be a PNG, with a minimum height and width of 256 pixels. 8 | 9 | https://wechaty.js.org/img/wechaty-logo.svg 10 | 11 | ## Tagline 12 | 13 | > Describe the organization's mission. This is often the only thing a participant will read about your org, be sure to make it clear and concise. 50 characters maximum. 14 | 15 | Code less works more, that's Wechaty! 16 | 17 | ## Primary Open Source License 18 | 19 | Apache 2.0 20 | 21 | ## What year was your project started? 22 | 23 | 2016 24 | 25 | ## Organization Categories 26 | 27 | > Select which categories fit your organization best. You may select up to 2 categories. This helps GSoC contributors filter the large list of organizations by their interests. 28 | 29 | * [ ] Data (databases, analytics, visualization, AI/ML, etc) 30 | * [X] Development tools (version control systems, CICD tools, text editors, issue managers, q/a tools, etc) 31 | * [ ] End user applications 32 | * [ ] Infrastructure and cloud (hardware, software defined infrastructure, cloud native tooling, orchestration and automation, etc) 33 | * [ ] Media (graphics, video, audio, VR, streaming, gaming, content management, etc) 34 | * [ ] Operating systems 35 | * [ ] Programming languages (libraries, package managers, testing tools, etc) 36 | * [ ] Science and medicine (healthcare, biotech, life sciences, academic research, etc) 37 | * [ ] Security (tools and frameworks) 38 | * [X] Social and communications (Blog, chat, forums, wikis, etc) 39 | * [ ] Web (tools and frameworks) 40 | * [ ] Other 41 | 42 | ## Organization Technologies 43 | 44 | > Enter up to 5 keywords for the primary specific technologies your organization uses. Examples: Python, Javascript, MySQL, Hadoop, OpenGL, Arduino 45 | 46 | * Python 47 | * TypeScript 48 | * JavaScript 49 | * Conversational AI 50 | * RPA 51 | 52 | ## Organization Topics 53 | 54 | > Enter keywords for general topics that describe your organization. Examples: Robotics, Cloud, Graphics, Web, etc. Select up to 5. 55 | 56 | * conversational-user-interface 57 | * machine-learning 58 | * assistant 59 | * angular 60 | * instance-message 61 | 62 | ## Organization Description 63 | 64 | > Describe what it is your organization does. This information will also be included in the archive once the program has ended. 65 | 66 | Wechaty is an Open Source software application for building chatbots. It is a modern Conversational RPA SDK which Chatbot makers can use to create a bot in a few lines of code. 67 | 68 | You can use Wechaty to build a chatbot which automates conversations and interact with people through instant messaging platforms such as WhatsApp, WeChat, WeCom, Gitter and Lark among others. 69 | 70 | ## [Optional] Contributor Guidance 71 | 72 | > Provide your potential contributors with a page containing tips on how to write a successful proposal for your organization. Let them know what you want included, how you want it structured, and how to best get in touch. [Examples](https://developers.google.com/open-source/gsoc/help/contributor-guidance). 73 | 74 | [blank: we did not fill in this field] 75 | 76 | ## Communication Methods 77 | 78 | > How do you want potential contributors to interact with your organization? Select methods that your community uses daily as you will receive many inquiries if your org is selected. 79 | 80 | * Mailing List / Forum: https://gitter.im/wechaty/wechaty 81 | * Mailing List / Forum: wechaty@googlegroups.com 82 | -------------------------------------------------------------------------------- /google-summer-of-code/2022/organization-questionnaire.md: -------------------------------------------------------------------------------- 1 | ## Why does your organization want to participate in Google Summer of Code? 2 | 3 | GSoC has attracted many contributors to open source projects like Wechaty. Through GSoC, we hope to let contributors understand Wechaty, improve Wechaty, and actually use Wechaty to complete some projects that are very valuable to the society. In this way, we can realize the vision of Wechaty: our technology makes society better. 4 | 5 | ## What would your organization consider to be a successful GSoC program? 6 | 7 | Most projects are completed successfully. Contributors are happy to work on their projects and are more than willing to recommend them to classmates, friends or colleagues. Our projects can have long-lasting benefits to the community as well as to society. 8 | 9 | ## How will you keep mentors engaged with their GSoC contributors? 10 | 11 | Our mentors are core members of the community. They have a rich history of contribution and experience, and a strong team spirit to trust each other. On top of that, we have established some management rules to ensure the success of the projects: we use email as the main communication channel and hold Zoom meetings when necessary. To monitor the entire process, we will meet once a week to discuss GSoC so that issues can be identified early. Each contributor will have at least two mentors to avoid the problem of disappearing mentors. In addition, the GSoC administrator will oversee the entire program. 12 | 13 | ## How will you keep your GSoC contributors on schedule to complete their projects? 14 | 15 | Our GSoC administrators (some are also mentors) will track the progress of each project at a higher level. We use GitHub for code management so we can easily monitor progress by Issues and PRs. 16 | 17 | In order to be selected, contributors need to complete an basic task from GitHub. This requires them to build and start looking at the code, which makes contributors more confident about future tasks, and our mentors also have the opportunity to understand how contributors work. 18 | 19 | All contributors are required to submit progress reports on the GitHub issues under their projects every week, and to submit/update GitHub Issues/PRs every week. This will help find difficulties before the contributor is really lost. 20 | 21 | ## How will you get your GSoC contributors involved in your community during GSoC? 22 | 23 | In the contributor program, we encourage contributors to participate in discussions on email and Zoom, creating their own open-source project or post blogs to share their thoughts about our project. 24 | 25 | Our mentors will encourage contributors to introduce their ideas to the community to get involved. We believe that contributors need to do more than just write code. They need to interact with the community by proposing solutions and iterating the projejcts until they are good enough. 26 | -------------------------------------------------------------------------------- /google-summer-of-code/2022/program-application.md: -------------------------------------------------------------------------------- 1 | ## Ideas List 2 | 3 | https://wechaty.js.org/docs/gsoc/2022/ 4 | 5 | ## Mentors 6 | 6 7 | -------------------------------------------------------------------------------- /google-summer-of-code/2022/project-ideals.md: -------------------------------------------------------------------------------- 1 | ## Project 1: Create a Web Component for a Chat UI for Wechaty 2 | 3 | Create a Web Component in Angular for a Chat UI for Wechaty. 4 | 5 | Useful Links: 6 | 1. [Fiora](https://fiora.suisuijiang.com/) is an interesting chat application power by socket.io, koa, MongoDB and React. (See: https://github.com/yinxin630/fiora/issues/185) 7 | 2. [Aurora IMUI](https://github.com/jpush/aurora-imui) is a general IM UI components library, which does not depend on any specific IM SDK. 8 | 3. [Chatvia](https://themeforest.net/item/chatvia-angular-chat-app-template/28316331) - Angular Chat App Template 9 | 10 | * Potential Mentor(s): lijiarui, Huan 11 | * Category: Core development 12 | * Skills Required: TypeScript (programming language), Angular 13 | * Difficulty Level: Medium 14 | 15 | ## Project 2: Wechaty Rust 16 | 17 | Rust is a new programming language with increasing popularity for its performance, memory safety and extensibility with existing systems. 18 | 19 | Wechaty will benefit from a Rust Core module that interfaces with its original TypeScript code base for performance boost, and a potential to ship to browser and Native apps by building to binary and webAssembly. 20 | 21 | * Potential Mentor(s): Simon LIANG, Zihua WU 22 | * Category: Core development 23 | * Skills Required: Rust (programming language) 24 | * Difficulty Level: Medium 25 | 26 | ## Project 3: Implement Wechaty Rasa Plugin 27 | 28 | Rasa is a popular task-oriented dialogue system which can be a pipeline in IM platform. What's more, wechaty is an unifiy conversation AI SDK for chatbot. So Wechaty + Rasa will be the perfect project that developer can easily deploy their chatbot on multi-platforms. 29 | 30 | 1. Running Rasa Server. When you run the rasa server, it will expose the message service with http protocol. 31 | 2. Communicating with Rasa Server. This process is a simple work which will send the request to the server and receive the message sending the wechaty end account. 32 | 33 | * Potential Mentor(s): @wj-Mcat, Xiaoquan Kong 34 | * Category: Core development 35 | * Skills Required: Python (programming language), Natural Language Processing, Rasa 36 | * Difficulty Level: Medium 37 | 38 | ## Project 4: Implement "Twitter" Puppet 39 | 40 | We want Wechaty to be the universal instant messaging SDK on all IM platforms for chatbot makers to build their great conversational user interface, so while these are our ideas of what we think would make good projects for the summer, we're eager to hear your ideas and proposals as well. 41 | 42 | Implement Twitter Puppet. The Puppet abstraction allows Wechaty to provide a consisting API on all IM platforms for build a chatbot. We are supporting WeChat, WeCom, Whatsapp already, and we want to support Twitter so that our developers can run their chatbots on Twitter to serve users from Twitter. 43 | 44 | * Potential Mentor(s): Huan 45 | * Category: Core development 46 | * Skills Required: TypeScript (programming language), Twitter API 47 | * Difficulty Level: Medium 48 | 49 | ## Project 5: Conversational robot that provides COVID-19 information services for elderly groups 50 | 51 | The elderly population is more susceptible to COVID-19 virus infection and has a very high mortality rate. At the same time, the elderly population has barriers in accessing information: devices such as smartphones are not friendly to the elderly population. Many parts of the world have a high level of population aging and therefore have a large number of elderly populations. Society should pay more attention to the health of these elderly people and act quickly. Let's make a voice-based intelligent assistant to help the elderly population get information to protect themselves from COVID-19 virus infection. 52 | 53 | We will use [Rasa](https://rasa.com) as the backend engine to provide conversational AI experience. And, we will use Wechaty to provide the frontend. Wechaty has the ablility to connect with lots of IM in different countries, so we can serve as many elders as possible. 54 | 55 | * Potential Mentor(s): Xiaoquan Kong 56 | * Category: Public welfare 57 | * Skills Required: Python (programming language), Rasa framework 58 | * Difficulty Level: Medium 59 | -------------------------------------------------------------------------------- /google-summer-of-code/README.md: -------------------------------------------------------------------------------- 1 | ## Google Summer of Code in Wechaty 2 | 3 | ![Google Summer of Code in Wechaty](wechaty-gsoc.png) 4 | 5 | Google Summer of Code (GSoc) is a global program focused on bringing more student developers into open source software development. Students work with an open source organization on a 10 week programming project during their break from school. 6 | 7 | - 8 | 9 | > Previous iterations of Google Summer of Code: 10 | 11 | Wechaty is applying to join GSoC in 2021 as its first time. 12 | 13 | ## Iterations of Summer of Wechaty for GSoC 14 | 15 | - [2021](2021/) 16 | 17 | ### Useful links 18 | 19 | - HOWTO: Propose a project idea: [proposing-new-project-ideas.md](proposing-new-project-ideas.md) 20 | - Mentor Registration: 21 | 22 | ## For Mentors 23 | 24 | - GSoC Mentor Guide 25 | - Mentor Participant Agreement 26 | - Mentor Responsibilities 27 | > OSPP 中文版： 28 | - Defining a Project (Ideas List) 29 | - How to Choose a Google Summer of Code Student 30 | - Being a Great Google Summer of Code Mentor 31 | - Tips for finding the “right” GSoC student for your org 32 | 33 | ## For Org Admin 34 | 35 | - Org Application: 36 | - Making Your Ideas Page: 37 | 38 | ## Other Org Useful Links 39 | 40 | - [OpenMRS - Come be a mentor for the Google Summer of Code (GSOC) program!](https://talk.openmrs.org/t/come-be-a-mentor-for-the-google-summer-of-code-gsoc-program/9671) 41 | - [OpenMRS - GSoC 2021- Guidelines for interested students](https://talk.openmrs.org/t/gsoc-2021-guidelines-for-interested-students/32149) 42 | - [Jenkins - Google Summer of Code. Information for mentors](https://www.jenkins.io/projects/gsoc/mentors/) 43 | - [Jenkins - Google Summer of Code. Information for students](https://www.jenkins.io/projects/gsoc/students/) 44 | - [Jenkins - GSoC 2020 Project Ideas](https://www.jenkins.io/projects/gsoc/2020/project-ideas/) 45 | - [Jenkins - GSOC2020_LASTNAME_ProposalName](https://docs.google.com/document/d/1dIlPLXfLbFsvcaHFuwmH9_lSCVm9m6-SgNYTNAnSZpY/edit?usp=sharing) 46 | 47 | ## FAQ 48 | 49 | ### 1. What is Google Summer of Code (GSoC) 50 | 51 | Google Summer of Code (GSoc, ) is a global program focused on bringing more student developers into open source software development. Students work with an open source organization on a 10 week programming project during their break from school. 52 | 53 | 每年 GSoC 都会组织世界顶级开源项目来发布任务给全世界的同学，吸引同学加入开源开发，同时会支付给同学奖学金。像 ffmpeg / debian / git / graphql 等等都有参与。 54 | 55 | ### What is the Mentor of GSoC 56 | 57 | Wechaty Organization 的 mentor ，需要发布 1-3 个项目给这个暑期的同学。挖掘更多的 Chatbot 想法，如果能结合上 Google 的这个活动，带几个同学做,尝试更多的点子落地。 58 | 59 | Wechaty Org 的任何点子，都可以通过发布 Issue 的方法记录累了 里面（多多益善） 60 | 61 | 然后，我们每位 Mentor 选出 1-3 个自己认为合适的项目，整理描述后，通过 Wechaty Org 申报给 Google ，并最终发布给同学。可以参考 Matrix 2020年的例子： 62 | 63 | ### Categories 64 | 65 | There are many ways to define a good GSoC project–probably as many ways as there are student-mentor pairings. Here are just a few: 66 | 67 | - **Low-hanging fruit**: These projects require minimal familiarity with the codebase and basic technical knowledge. They are relatively short, with clear goals. 68 | - **Risky/Exploratory**: These projects push the scope boundaries of your development effort. They might require expertise in an area not covered by your current development team. They might take advantage of a new technology. There is a reasonable chance that the project might be less successful, but the potential rewards make it worth the attempt. 69 | - **Fun/Peripheral**: These projects might not be related to the current core development focus, but create new innovations and new perspective for your project. 70 | - **Core development**: These projects derive from the ongoing work from the core of your development team. The list of features and bugs is never-ending, and help is always welcome. 71 | - **Infrastructure/Automation**: These projects are the code that your organization uses to get its development work done; for example, projects that improve the automation of releases, regression tests and automated builds. This is a category in which a GSoC student can be really helpful, doing work that the development team has been putting off while they focus on core development. 72 | 73 | ## Wechaty Organization Administrators 74 | 75 | - [Jing](https://wechaty.js.org/contributors/wj-mcat), Author of [Python Wechaty](https://github.com/wechaty/python-wechaty) 76 | - [Huan](https://wechaty.js.org/contributors/huan), Tencent TVP of Chatbot, Creator of Wechaty 77 | - [Yuan](https://wechaty.js.org/contributors/windmemory), CTO of Juzi.BOT, Creator of Wechaty Puppet Service [WXWork](https://wechaty.js.org/docs/puppet-services/wxwork) 78 | - [Rui](https://pre-angel.com/peoples/jiarui-li/), Microsoft AI [MVP](https://mvp.microsoft.com/en-us/PublicProfile/5003226), Co-creator of Wechaty 79 | -------------------------------------------------------------------------------- /google-summer-of-code/proposing-new-project-ideas.md: -------------------------------------------------------------------------------- 1 | # Proposing New Project Ideas 2 | 3 | Wechaty is maintaining Ideas in our [wishlist](https://github.com/wechaty/wishlist) repo to continually recruit new ideas at anytime. 4 | 5 | In order to proposing a new project idea, you need to: 6 | 7 | 1. File an issue under [wishlist repo issues](https://github.com/wechaty/wishlist/issues/) to describe what you want to propose, and mention the `@wechaty/summer` so that our team can get notified. 8 | 1. Send your new issue link url to our Gitter Chat at so that more developers can see it and talk about your idea. 9 | -------------------------------------------------------------------------------- /google-summer-of-code/wechaty-gsoc.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/wechaty/summer/996f9316096674fd5fc81dd1ec9200f2011d23d5/google-summer-of-code/wechaty-gsoc.png -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2020/README.md: -------------------------------------------------------------------------------- 1 | # 开源软件供应链点亮计划-暑期2020 2 | 3 | - [Wechaty 暑期2020 - 开源软件供应链点亮计划官网](https://isrc.iscas.ac.cn/summer2020/#/organisations/wechaty) 4 | - [Wechaty Summer of Code Tasks Slides](https://docs.google.com/presentation/d/1ZLH37rQyRgChGqFCUDjA5rbVgBuRkVM4Tys-_ls0gs0/edit?usp=sharing) 5 | - [暑期2020 - 活动宣讲直播方案](https://shimo.im/docs/T9pTD3PRWQKjtwgh/read) 6 | - [GitHub Milestone](https://github.com/wechaty/summer-of-wechaty/milestone/1) 7 | 8 | ## 开源软件供应链点亮计划-暑期2020”是什么 9 | 10 | “开源软件供应链点亮计划-暑期2020”（以下简称 暑期2020）是由中科院软件所与 openEuler 社区共同举办的一项面向高校学生的暑期活动，旨在鼓励在校学生积极参与开源软件的开发维护，促进国内优秀开源软件社区的蓬勃发展。 11 | 12 | 该计划将联合各大开源社区，针对重要开源软件的开发与维护提供 mini 项目，并向全国高校学生开放报名。学生可自主选择感兴趣的项目进行申请，并在中选后获得该软件资深维护者（社区导师）亲自指导的机会。根据项目的难易程度和完成情况，参与者还可获取“开源软件供应链点亮计划-暑期2020”活动奖金和奖杯。 13 | 14 | “暑期2020”项目在今年（2020）首次举办，与Google Summer of Code类似，不同点是“暑期2020”只允许中国学生参加，可以看做中国版的GSoC。 15 | 16 | - 官网： 17 | - 官方新闻： 18 | 19 | ## 活动的主要参与方有哪些 20 | 21 | 活动组织方：中国科学院软件研究所、openEuler 社区主办，中国科学院软件研究所中国科学院软件研究所南京软件技术研究院，华为技术有限公司、中科软科技股份有限公司、深圳华锐金融技术股份有限公司等公司协办，此外，活动组组委会还联合国内公司、科研院所和各大高校共同推广此次活动。 22 | 23 | 活动参与方主要角色为学生、社区和导师。 24 | 25 | 学生：学生自由选择项目，与导师沟通实现方案并撰写项目计划书。被选中的学生将在导师指导下，按计划完成开发工作，并将成果贡献给社区。社区评估学生的完成度，主办方根据评估结果发放资助金额给学生。 26 | 社区：社区提供项目列表和描述，并安排项目对应的导师，导师与申请者沟通方案、并从申请者中选中一位承接项目。在为期三个月的开发周期中，导师指导学生进行对应项目的开发工作。 27 | 导师：社区针对每一个项目指定一个导师，与学生一起制定合适的开发计划和方案，指导学生按计划完成开发。 28 | 项目的奖金额度是多少？ 29 | 项目难度分为高、中、低三档，对应税前奖金分别为高（12000 元）、中（9000 元）、低（6000 元）。 30 | 31 | ## Wechaty Code in Summer 2020 32 | 33 | [Wechaty 社区暑期2020点亮计划](https://github.com/wechaty/summer-of-code) 34 | 35 | ### Wechaty 是什么 36 | 37 | Wechaty 是一个开源聊天机器人框架SDK，具有高度封装、高可用的特性，支持NodeJs, Python, Go 和Java 等多语言版本。在过去的4年中，服务了数万名开发者，收获了 Github 的 8000 Star。同时配置了完整的 DevOps 体系并持续按照 Apache 的方式管理技术社区。 38 | 39 | [![Wechaty](https://wechaty.github.io/wechaty/images/wechaty-logo-green-en.png)](https://github.com/wechaty/wechaty) 40 | 41 | [![Downloads](https://img.shields.io/npm/dm/wechaty.svg?style=flat-square)](https://www.npmjs.com/package/wechaty) 42 | [![GitHub stars](https://img.shields.io/github/stars/wechaty/wechaty.svg?label=github%20stars)](https://github.com/wechaty/wechaty) 43 | [![Docker Pulls](https://img.shields.io/docker/pulls/zixia/wechaty.svg?maxAge=2592000)](https://hub.docker.com/r/zixia/wechaty/) 44 | [![TypeScript](https://img.shields.io/badge/%3C%2F%3E-TypeScript-blue.svg)](https://www.typescriptlang.org/) 45 | [![Gitter](https://badges.gitter.im/Chatie/wechaty.svg)](https://gitter.im/Chatie/wechaty?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) 46 | 47 | ### Connecting Chatbots 48 | 49 | Wechaty is a Conversational AI RPA Chatbot SDK for Wechat **Individual** Account which can help you create a bot in 6 lines of [JavaScript](https://GitHub.com/Wechaty/wechaty), [Python](https://GitHub.com/Wechaty/python-wechaty/), [Go](https://GitHub.com/Wechaty/go-wechaty/), and [Java](https://GitHub.com/Wechaty/java-wechaty/), with cross-platform support including [Linux, Windows, MacOS](https://github.com/wechaty/wechaty/actions?query=workflow%3ANPM), and [Docker](https://github.com/wechaty/wechaty/actions?query=workflow%3ADocker). 50 | 51 | :octocat: 52 | :beetle: 53 | :book: 54 | :whale: 55 | 56 | ### Voice of Developers 57 | 58 | > "Wechaty is a great solution, I believe there would be much more users recognize it." [link](https://github.com/Wechaty/wechaty/pull/310#issuecomment-285574472) 59 | > — @Gcaufy, Tencent Engineer, Author of [WePY](https://github.com/Tencent/wepy) 60 | > 61 | > "太好用，好用的想哭" 62 | > — @xinbenlv, Google Engineer, Founder of HaoShiYou.org 63 | > 64 | > "最好的微信开发库" [link](http://weibo.com/3296245513/Ec4iNp9Ld?type=comment) 65 | > — @Jarvis, Baidu Engineer 66 | > 67 | > "Wechaty让运营人员更多的时间思考如何进行活动策划、留存用户，商业变现" [link](http://mp.weixin.qq.com/s/dWHAj8XtiKG-1fIS5Og79g) 68 | > — @lijiarui, Founder & CEO of Juzi.BOT. 69 | > 70 | > "If you know js ... try Wechaty, it's easy to use." 71 | > — @Urinx Uri Lee, Author of [WeixinBot(Python)](https://github.com/Urinx/WeixinBot) 72 | > 73 | > "Wechaty is a good project, I hope it can continue! Therefore, I became a contributors in open collective." 74 | > — [@Simple](https://github.com/mrwhh) 75 | 76 | ### Wechaty 希望实现的新进展及可选项目列表 77 | 78 | Wechaty 希望实现多平台、多语言、多功能三个层次，成为易用度最高、可迁移性最强的聊天机器人框架。 79 | 80 | 多平台是指，在现有的基于微信个人号的聊天机器人框架基础上，逐渐覆盖包括企业微信、钉钉、飞书的多个IM，并通过封装同一套应用层代码的形式，仅更改一个变量就将同一套聊天机器人代码迁移到多个平台中。 81 | 82 | 多语言是指，针对同一套功能，能使用多种编程语言调用不同功能、不同平台的微信机器人，并通过打通多语言之间的通路，实现针对每门语言开发的功能都能同步到其余所有语言中。 83 | 84 | 多功能是指，在 Wechaty 已经上线的插件系统的基础上，将特定功能按一定形式封装成接口，让其他开发者可以以仅添加短至一行代码的方式，使用原有数百行代码才能完成的功能。 85 | 86 | #### 多平台（Multi-Plat） 87 | 88 | - （难度：高）基于开放 API 封装 Wechaty 接口下的企业微信聊天机器人 89 | - （难度：高）基于开放 API 封装 Wechaty 接口下的钉钉聊天机器人 90 | - （难度：高）基于开放 API 封装 Wechaty 接口下的飞书聊天机器人 91 | - （难度：高）基于 RPA 封装 Wechaty 接口下的抖音聊天机器人 92 | - （难度：高）基于 RPA 封装 Wechaty 接口下的快手聊天机器人 93 | 94 | #### 多语言（Multi-Lang） 95 | 96 | - （难度：中）为 go-wechaty 设计实现 插件体系 97 | - （难度：中）Go-wechaty Github Action optimization 98 | - （难度：低）Wechaty Java 移植组件开发 99 | 100 | #### 多功能（Plugin） 101 | 102 | - （难度：中）基于python-wechaty的群聊助手机器人 103 | - （难度：中）基于Python-wechaty建立一个斗图机器人 104 | - （难度：低）编写一个“每日一句”插件 105 | 106 | ### 投递要求 107 | 108 | 申请学生需要同时完成以下“联系社区”和“官网投递”两个环节： 109 | 110 | 1. 联系社区（2020年5月15日至6月20日） 111 | 扫描二维码添加 Wechaty 社区官方机器人 Friday BOT 112 | 113 | ![Friday BOT](https://https://wechaty.js.org/img/friday-qrcode.svg) 114 | 115 | 确定认领项目后，由社区官方机器人拉群，开始任务推进。 116 | 117 | 2. 官网投递（2020年6月1日至6月20日） 118 | 119 | 详见： 120 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2020/apply.md: -------------------------------------------------------------------------------- 1 | 2 | ## 社区报名_Wechaty 3 | 4 | - 社区或开源项目名称： Wechaty 5 | - 社区官网网址 6 | - 联系人：李卓桓 7 | - 联系方式： 8 | - 邮箱：huan@chatie.io 9 | - 电话: 10 | 11 | 1. 社区名称：Wechaty 社区 12 | 13 | 2. 社区官方网址： 14 | 15 | 3. 社区 Logo 文件： 16 | 17 | 4. 社区简短描述（30 字以内）：Wechaty is a Conversational RPA SDK for Chatbot Makers to build WeChat and Whatsapp bots with ease. 18 | 19 | 5. 社区成段描述： 20 | 21 | Conversational RPA SDK Wechaty 是一个开源聊天机器人框架SDK，于 2016 年发布于 GitHub，是一个基于 Apache-2.0 许可证的开源项目，具有高度封装、高可用的特性，支持 NodeJs, Python, Go 和 Java 等多语言版本。 22 | 23 | 经过4年多的发展，现在 Wechaty 开源社区已经拥有数十位 Committers，百余位 Contributors ，并被近万名 GitHub 开发者 Star 。使用 Wechaty 的开发者已覆盖数万人，并拥有基于微信群的数千人活跃开发者群。Wechaty 社区的 Contributors 遍布全球多个国家地区，和各大互联网公司，职业背景从程序员到设计师，从大学教授到创业者，非常多样化。GitHub 上有千余个开源项目基于 Wechaty 构建了聊天机器人，这些开发者用户也极大地促进了社区的活跃和发展。 24 | 25 | Wechaty自身对代码质量的管理，使用了 GitHub Actions 的 DevOps 工具完成了 CI/CD 工作流，从自动化单元测试到自动打包集成测试，从自动发布 NPM 包到自动构建和发布对应版本的 Docker Image ，实现了全自动的社区代码发布，极大的提高了社区的协同效率。在开源社区管理上，Wechaty 遵循 The Apache Way ，拥有 PMC / Committer 管理制度，和完善的 Issue / PR / Release 等管理制度。 26 | 27 | 截止2020年，Wechaty 已经有近百万次 NPM 安装下载，并由社区自发推动了 Python, Go, Java, Scala, CSharp, PHP 等语言的适配和发布，是国内最活跃的 Conversational AI Chatbot 开发者社区。 28 | 29 | Wechaty 支持的功能包括：接收消息，发送消息、添加好友、为好友备注、接受好友请求、发起群聊、加人入群等功能。只需要6行代码，你就可以 通过个人号 搭建一个 微信机器人功能 ，用来自动管理微信消息。 30 | 31 | 更多功能包括： 32 | - 消息处理：关键词回复 33 | - 群管理：自动入群，拉人，踢人 34 | - 自动处理好友请求 35 | - 智能对话：通过简单配置，即可加入智能对话系统，完成指定任务 36 | 37 | 6. 社区邮件列表（用于帮助学生了解社区，一般为开发者邮箱列表）： 38 | 39 | 40 | 41 | Gitter: 42 | 43 | 7. 社区官方公共联系邮箱：wechaty@chatie.io 44 | 45 | 8. 社区 “暑期2020” 项目列表页面链接（可选，可在页面准备好后再告知，应在 5 月 15 日之前提供） 46 | 47 | 48 | 49 | 9. 技术标签：Conversational, AI, RPA, NLP, TypeScript, Docker, DevOps, Node.js 50 | 51 | 10. 专注领域：Chatbot, Conversational AI, NLP 52 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/README.md: -------------------------------------------------------------------------------- 1 | # 开源软件供应链点亮计划 - 暑期2021 2 | 3 | 开源软件供应链点亮计划鼓励大家关注开源软件和开源社区，致力于培养和发掘更多优秀的开发者。 4 | 活动将在暑期进行，我们将与开源社区紧密合作，提供一对一的导师指导，邀请技术大牛开展线上免费讲座。 5 | 我们鼓励研究人员、开源爱好者、在校师生参与开源软件的开发与维护，促进开源软件的发展和优秀开源软件社区建设， 6 | 增加开源项目的活跃度，推进开源生态的发展。 7 | 8 | - 官网： 9 | - 启动新闻： 10 | - 详细介绍： 11 | - [GitHub Milestone](https://github.com/wechaty/summer-of-wechaty/milestone/2) 12 | 13 | ## 暑期 2021 14 | 15 | 开源软件供应链点亮计划 - 暑期 2021（以下简称 暑期 2021）是由 中国科学院软件研究所 与 openEuler 社区 共同举办的一项面向高校学生的暑期活动，旨在鼓励在校学生积极参与开源软件的开发维护，促进优秀开源软件社区的蓬勃发展。我们将联合各大开源社区，针对重要开源软件的开发与维护提供项目，并向全球高校学生开放报名。 16 | 17 | 学生可自主选择感兴趣的项目进行申请，并在中选后获得该软件资深维护者（社区导师）亲自指导的机会。根据项目的难易程度和完成情况，参与者还将获取 开源软件供应链点亮计划-暑期2021 活动奖杯和奖金。 18 | 19 | ### 支持项目的难度范围更广 20 | 21 | 项目资助金额根据项目难度分为 12000 元、9000 元和 6000 元（注：奖金数额为税前人民币金额），支持更多不同难度的项目是为了满足社区发展的不同需求，同时也有利于更多学生的参与。 22 | 23 | ### 支持更多类型的开源项目 24 | 25 | 本次活动除支持采用 OSI 组织认证的开源协议 的开源软件项目外，同时支持采用 ODI 组织认证的推荐的开放知识协议 的开源知识类项目，如技术文档汉化、知识文档等。 26 | 27 | ### 活动组织形式更多样 28 | 29 | 除了鼓励学生为社区提交贡献，组委会希望为广大在校学生介绍开源理念，帮助在校学生深入了解开源文化、参与开源社区的方式方法。 30 | 31 | ### 活动的组织方有哪些 32 | 33 | 本次活动由中国科学院软件研究所、openEuler 社区主办，当前是第二届，欢迎更多机构参与。 34 | 35 | ### 活动的参与方以及角色有哪些 36 | 37 | 活动参与方主要角色为学生、社区和导师。 38 | 39 | #### 学生 40 | 41 | 学生自由选择项目，与社区导师沟通实现方案并撰写项目计划书。被选中的学生将在社区导师指导下，按计划完成开发工作，并将成果贡献给社区。社区评估学生的完成度，主办方根据评估结果给学生发放奖金。 42 | 43 | #### 社区 44 | 45 | 社区提供项目列表和描述，并安排项目对应的导师，导师与申请者沟通方案、并从申请者中选中一位承接项目。在为期三个月的开发周期中，导师指导学生进行对应项目的开发工作。 46 | 47 | #### 导师 48 | 49 | 社区针对每一个项目指定一个社区导师，与学生一起制定合适的开发计划和方案，指导学生按计划完成开发。 50 | 51 | ### 项目的奖金是多少 52 | 53 | 每个项目难度分为高、中、低三档，对应税前奖金分别为高（12000 元）、中（9000 元）、低（6000 元）。（注：奖金数额为税前人民币金额）。 54 | 55 | 难度分级由社区根据项目任务决定。 56 | 57 | ## Wechaty 开源软件供应链点亮计划 - 暑期2021 58 | 59 | [Wechaty 社区暑期2021点亮计划](https://github.com/wechaty/summer-of-code/summer-ospp/2021/) 60 | 61 | ### Wechaty 是什么 62 | 63 | Wechaty 是一个开源聊天机器人框架SDK，具有高度封装、高可用的特性，支持NodeJs, Python, Go 和Java 等多语言版本。在过去的4年中，服务了数万名开发者，收获了 Github 的 8000 Star。同时配置了完整的 DevOps 体系并持续按照 Apache 的方式管理技术社区。 64 | 65 | [![Wechaty](https://wechaty.github.io/wechaty/images/wechaty-logo-green-en.png)](https://github.com/wechaty/wechaty) 66 | 67 | [![Downloads](https://img.shields.io/npm/dm/wechaty.svg?style=flat-square)](https://www.npmjs.com/package/wechaty) 68 | [![GitHub stars](https://img.shields.io/github/stars/wechaty/wechaty.svg?label=github%20stars)](https://github.com/wechaty/wechaty) 69 | [![Docker Pulls](https://img.shields.io/docker/pulls/zixia/wechaty.svg?maxAge=2592000)](https://hub.docker.com/r/zixia/wechaty/) 70 | [![TypeScript](https://img.shields.io/badge/%3C%2F%3E-TypeScript-blue.svg)](https://www.typescriptlang.org/) 71 | [![Gitter](https://badges.gitter.im/Chatie/wechaty.svg)](https://gitter.im/Chatie/wechaty?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) 72 | 73 | ### Connecting Chatbots 74 | 75 | Wechaty is a Conversational AI RPA Chatbot SDK for Wechat **Individual** Account which can help you create a bot in 6 lines of [JavaScript](https://GitHub.com/Wechaty/wechaty), [Python](https://GitHub.com/Wechaty/python-wechaty/), [Go](https://GitHub.com/Wechaty/go-wechaty/), and [Java](https://GitHub.com/Wechaty/java-wechaty/), with cross-platform support including [Linux, Windows, MacOS](https://github.com/wechaty/wechaty/actions?query=workflow%3ANPM), and [Docker](https://github.com/wechaty/wechaty/actions?query=workflow%3ADocker). 76 | 77 | :octocat: 78 | :beetle: 79 | :book: 80 | :whale: 81 | 82 | ### Voice of Developers 83 | 84 | > "Wechaty is a great solution, I believe there would be much more users recognize it." [link](https://github.com/Wechaty/wechaty/pull/310#issuecomment-285574472) 85 | > — @Gcaufy, Tencent Engineer, Author of [WePY](https://github.com/Tencent/wepy) 86 | > 87 | > "太好用，好用的想哭" 88 | > — @xinbenlv, Google Engineer, Founder of HaoShiYou.org 89 | > 90 | > "最好的微信开发库" [link](http://weibo.com/3296245513/Ec4iNp9Ld?type=comment) 91 | > — @Jarvis, Baidu Engineer 92 | > 93 | > "Wechaty让运营人员更多的时间思考如何进行活动策划、留存用户，商业变现" [link](http://mp.weixin.qq.com/s/dWHAj8XtiKG-1fIS5Og79g) 94 | > — @lijiarui, Founder & CEO of Juzi.BOT. 95 | > 96 | > "If you know js ... try Wechaty, it's easy to use." 97 | > — @Urinx Uri Lee, Author of [WeixinBot(Python)](https://github.com/Urinx/WeixinBot) 98 | > 99 | > "Wechaty is a good project, I hope it can continue! Therefore, I became a contributors in open collective." 100 | > — [@Simple](https://github.com/mrwhh) 101 | 102 | ### Wechaty 希望实现的新进展及可选项目列表 103 | 104 | To be listed 105 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/apply-en.md: -------------------------------------------------------------------------------- 1 | # Template for Community Application 2 | 3 | ## Message Header and Format 4 | 5 | Message Header: Community Application_{Name of Community} 6 | 7 | - Name of Community or Open Source Project：Wechaty 8 | - Official Website: 9 | - Contact: Fan Rui 10 | - E-mail: froxanne1024@gmail.com 11 | 12 | Please send e-mail to summer@iscas.ac.cn 13 | 14 | ## Information 15 | 16 | 1. Community name:Wechaty 17 | 2. Website URL:[https://wechaty.js.org](https://wechaty.js.org) 18 | 3. Upload Logo:[wechaty-logo](https://wechaty.js.org/img/wechaty-logo.svg) 19 | 4. Descriptions 20 | 21 | - Short Description (up to 180 characters): Wechaty is a Conversational RPA SDK for chatbot makers that can create a bot in 6 lines of code with the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 22 | 23 | - Long Description (may include limited Markdown up to 2000 characters):Wechaty is a Conversational RPA (Robotic Process Automation) SDK for Chatbot Makers which can create a bot in 6 lines of JavaScript, Python, Go, Java, .NET, PHP, and Scala, with cross-platform support including Linux, Windows, macOS, and Docker, on top of the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, etc. 24 | 25 | 5. Mailing List (In order to help students know more about the community, please fill the developers mailing list.): 26 | 27 | 6. Offical Contact E-mail:wechaty@chatie.io 28 | 29 | 7. Technology Tags:Conversational, AI, RPA, NLP, TypeScript, Python, MachineLearning, DeepLearning, Docker, DevOps, Node.js 30 | 31 | 8. Topics Tags:Chatbot, Conversational AI, NLP 32 | 33 | 9. The open source project maintained by community 34 | 35 | - Name of project: wechaty 36 | - Project repository link: 37 | - Open source license: Apache-2.0 38 | - Name of project: python-wechaty 39 | - Project repository link: 40 | - Open source license: Apache-2.0 41 | - Name of project: java-wechaty 42 | - Project repository link: 43 | - Open source license: Apache-2.0 44 | - Name of project: go-wechaty 45 | - Project repository link: 46 | - Open source license: Apache-2.0 47 | - Name of project: php-wechaty 48 | - Project repository link: 49 | - Open source license: Apache-2.0 50 | - Name of project: wechaty-puppet-official-account 51 | - Project repository link: 52 | - Open source license: Apache-2.0 53 | 54 | ## Application Questionnaire 55 | 56 | 1. What would you like to gain from "Summer 2021"? 57 | 58 | 'Summer 2021' is a strong appeal of the development of summer camp activities, able to bring together the country's outstanding student developers. The Wechaty community needs young blood to join, and I believe that with their participation, the Wechaty community will have a rapid development. 59 | 60 | Several students from the Wechaty community have become contributors during the 'Summer 2020' event, while three students have entered Wechaty Summer Admin. It is believed that more outstanding students will join the Wechaty community at this year's event, bringing more possibilities. 61 | 62 | 2. What would your org consider to be a successful summer? (New contributors, new features completed, more code written, better being able to guide new developers into open source world, etc.) 63 | 64 | For students: 65 | - Skilled use of community-related tool chains 66 | - Be familiar with the community's code specifications and develop good coding habits 67 | 68 | For the community: 69 | - More active student developers who become contributors 70 | - Optimising existing problems in the community 71 | - Implement new features to the community 72 | 73 | 3. How many potential mentors have agreed to mentor this year? 74 | This year, 21 potential mentors agreed to participate in mentoring different projects, as detailed: 75 | 76 | 4. How will you keep mentors engaged with their students? 77 | In order for students to learn more and maintain high-frequency interaction between mentors and students, we have the following programs: 78 | - The Student should submit a weekly report to give the tutor control of the student's weekly workload. 79 | - Mentors should review each line of student code and give their own advice. 80 | - Mentors should discuss solutions with students in the issue list and are open to the entire open source community. 81 | - Students can also review the tutor's code to enhance the student's sense of accomplishment. 82 | In addition, our Admin team this year is made up of outstanding mentors and students from Summer 2020, who are experienced contributors who coordinate their exchanges with students and are confident that they will be able to achieve good results 83 | 84 | 5. How will you help your students stay on schedule to complete their projects? 85 | The community will establish medium-term, closing goals, complete checks of all project completion rates by the deadline, and provide corresponding encouragements and reminders. If some students do not complete the project due to non-subjective wishes, a special discussion meeting between the tutor and the student will be arranged, and Wechaty Admin will track the progress. 86 | 87 | 6. Have your community ever participated om "Summer 2020"? Yes 88 | 89 | - How many students did your community accept for 2020? 90 | 11 91 | 92 | - How many of your community’s 2020 students have been active in your community in the last 60 days? 93 | 4 94 | 95 | ## Example for community application 96 | 97 | 1. Community name: openEuler Community 98 | 2. Website URL: 99 | 3. Upload Logo 100 | 4. Descriptions 101 | These descriptions will be displayed on the organization list page (Short Description) and on your organization's page (Long Description). 102 | - Short Description 103 | An open source and a free platform for Linux released edition. 104 | - Long Description (may include limited Markdown up to 2000 characters) 105 | An open source and a free platform for Linux released edition, which aims to build an open, diversified and architecture inclusive software ecosystem with global developers through openEuler community. At the same time, it is also an innovative platform, which encourages anyone to put forward new ideas, develop new ideas and practice new schemes 106 | 5. Mailing List: 107 | 6. Offical Contact E-mail： 108 | 7. Technology Tags: Linux、Git、GCC、RPM 109 | 8. Topics Tags: Operating System, kernel 110 | 9. The open source project maintained by community 111 | - Name of project: iSulad 112 | - Project repository link: 113 | - Open Source License: MulanPSL-2.0 114 | 115 | - Name of project: A-Tune 116 | - Project repository link: 117 | - Open Source License: MulanPSL-2.0 118 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/apply.md: -------------------------------------------------------------------------------- 1 | # 社区报名模板 2 | 3 | ## 邮件标题格式： 4 | 5 | 注：邮件标题需要采用此格式：社区报名_{社区名称} （填写示例请见文末） 6 | 7 | 邮件发送至 summer@iscas.ac.cn 。 8 | 9 | ## 报名信息摘要 10 | 11 | - 社区或开源项目名称：Wechaty 12 | - 社区官方网址： 13 | - 联系人：范蕊 14 | - 联系方式： 15 | - 邮箱：froxanne1024@gmail.com 16 | 17 | ## 社区基本信息 18 | 19 | 1. 社区名称：Wechaty 社区 20 | 2. 社区官方网址：[https://wechaty.js.org](https://wechaty.js.org) 21 | 3. 社区Logo文件：[wechaty-logo](https://wechaty.js.org/img/wechaty-logo.svg) 22 | 4. 社区简短描述（30 字以内）：Wechaty is a Conversational RPA SDK for Chatbot Makers to build WeChat and Whatsapp bots with ease. 23 | 5. 社区成段描述： 24 | 25 | Conversational RPA SDK Wechaty 是一个开源聊天机器人框架SDK，于 2016 年发布于 GitHub，是一个基于 Apache-2.0 许可证的开源项目，具有高度封装、高可用的特性，支持 NodeJs, Python, Go 和 Java 等多语言版本。 26 | 27 | 经过4年多的发展，现在 Wechaty 开源社区已经拥有数十位 Committers，百余位 Contributors ，并被近万名 GitHub 开发者 Star 。使用 Wechaty 的开发者已覆盖数万人，并拥有基于微信群的数千人活跃开发者群。Wechaty 社区的 Contributors 遍布全球多个国家地区，和各大互联网公司，职业背景从程序员到设计师，从大学教授到创业者，非常多样化。GitHub 上有千余个开源项目基于 Wechaty 构建了聊天机器人，这些开发者用户也极大地促进了社区的活跃和发展。 28 | 29 | Wechaty自身对代码质量的管理，使用了 GitHub Actions 的 DevOps 工具完成了 CI/CD 工作流，从自动化单元测试到自动打包集成测试，从自动发布 NPM 包到自动构建和发布对应版本的 Docker Image ，实现了全自动的社区代码发布，极大的提高了社区的协同效率。在开源社区管理上，Wechaty 遵循 The Apache Way ，拥有 PMC / Committer 管理制度，和完善的 Issue / PR / Release 等管理制度。 30 | 31 | 截止2020年，Wechaty 已经有超百万次 NPM 安装下载，并由社区自发推动了 Python, Go, Java, Scala, CSharp, PHP 等语言的适配和发布，是国内最活跃的 Conversational AI Chatbot 开发者社区。 32 | 33 | Wechaty 支持的功能包括：接收消息，发送消息、添加好友、为好友备注、接受好友请求、发起群聊、加人入群等功能。只需要6行代码，你就可以 通过个人号 搭建一个 微信机器人功能 ，用来自动管理微信消息。 34 | 35 | 更多功能包括： 36 | - 消息处理：关键词回复 37 | - 群管理：自动入群，拉人，踢人 38 | - 自动处理好友请求 39 | - 智能对话：通过简单配置，即可加入智能对话系统，完成指定任务 40 | 41 | 6. 社区邮件列表（用于帮助学生了解社区，一般为开发者邮箱列表）： 42 | 43 | 44 | 45 | Gitter: 46 | 47 | 7. 社区官方公共联系邮箱：wechaty@chatie.io 48 | 8. 技术标签：Conversational, AI, RPA, NLP, TypeScript, Python, MachineLearning, DeepLearning, Docker, DevOps, Node.js 49 | 9. 专注领域：Chatbot, Conversational AI, NLP 50 | 10. 社区维护的开源项目 51 | 52 | - 项目名称：wechaty 53 | 项目仓库地址： 54 | 开源协议：Apache-2.0 55 | - 项目名称：python-wechaty 56 | 项目仓库地址： 57 | 开源协议：Apache-2.0 58 | - 项目名称：java-wechaty 59 | 项目仓库地址： 60 | 开源协议：Apache-2.0 61 | - 项目名称：go-wechaty 62 | 项目仓库地址： 63 | 开源协议：Apache-2.0 64 | - 项目名称：php-wechaty 65 | 项目仓库地址： 66 | 开源协议：Apache-2.0 67 | - 项目名称：wechaty-puppet-official-account 68 | 项目仓库地址： 69 | 开源协议：Apache-2.0 70 | 71 | ## 报名问卷调查 72 | 73 | 1. 您的社区参加“暑期2021”希望有什么样的收获？ 74 | 75 | `暑期2021` 是一个拥有强大号召力的开发夏令营活动，能够汇聚全国优秀学生开发者。Wechaty社区需要年轻的血液加入，相信有他们的加入，wechaty社区将会拥有一个快速的发展。 76 | 77 | 在`暑期2020`的活动中，Wechaty社区已有多名学生成为contributor，同时有3名学生进入Wechaty Summer Admin。相信在今年的活动中会有更多优秀学生加入Wechaty社区，带来更多的可能性。 78 | 79 | 2. 您的社区认为一个成功的“暑期2021”是什么样的？ 80 | 81 | 对于学生而言： 82 | 83 | - 熟练使用社区相关工具链 84 | - 熟悉社区的代码规范，并培养优秀的编码习惯 85 | 86 | 对于社区而言： 87 | 88 | - 有多名活跃的学生开发者成为contributor 89 | - 优化社区现存的问题 90 | - 给社区引入新的特性 91 | 92 | 3. 今年有多少潜在导师同意参与指导该项目？ 93 | 94 | 今年有21位潜在导师同意参与指导不同项目，详细可看： 95 | 96 | 4. 您的社区将如何让导师与学生保持互动？ 97 | 98 | 为了让学生学到更多的东西，保持导师和学生的高频互动，我们有以下计划： 99 | 100 | - 学生会提交周报，让导师掌握学生每周的工作量。 101 | - 导师会review学生每一行代码，并给出自己的建议。 102 | - 导师会在issue列表中与学生讨论相关解决方案，且是open给整个开源社区。 103 | - 学生也可以review导师的代码，提升学生的成就感。 104 | 105 | 此外，我们今年的Admin团队由暑期2020的优秀导师和学生组成，由这些有经验的贡献者来协调导师和学生的交流，相信可以取得很好的效果 106 | 107 | 5. 您的社区将如何帮助中选学生按时完成他们的项目？ 108 | 109 | 社区将建立中期、结项目标，在截止日期之前会完成所有项目完成率的检查，并进行对应的鼓励和提醒。如有部分学生由于非主观意愿未完成项目，会安排导师与学生的专项讨论会议，同时Wechaty Admin 会跟踪进度。 110 | 111 | 6. 您的社区是否参与了“暑期2020”？是 112 | 113 | - 您的社区在“暑期2020”吸引了多少学生参与？ 共11人 114 | 115 | - 在过去的60天里，参与暑期2020的学生中有多少人活跃在您的社区？4人 116 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/mentor-final-term.md: -------------------------------------------------------------------------------- 1 | # 期末报告评审指南 2 | 3 | ## 1. “暑期2021”组委会期末评审 4 | 5 | 10月1日 - 10月14日期间，将评审报告在组委会的 Gitlab 上的 Issue 中提交，并配合组委会进行结项审核。 6 | 7 | ## 2. Wechaty 社区期末博客评审 8 | 9 | 在10月14日前以Pull Requests形式在 [wechaty.js.org](https://github.com/wechaty/wechaty.js.org) Repo 的学生对应博客下，补充评审结果的相关信息。 10 | 11 | 同时，按照社区博客提交规范，对学生提交的博客进行审核，审核通过后，在 GitHub **Approve** 这个 PR，然后交由 Wechaty PMC 进行博客审核。注意，社区导师一定要**提前、优先 Approve** 自己同学的 PR。 12 | 13 | 评审模板参考：[mentor-final-term-template](../template/mentor-final-term-template.md) 14 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/mentor-mid-term.md: -------------------------------------------------------------------------------- 1 | # 期中报告评审指南 2 | 3 | ## 1. “暑期2021”组委会期中评审 4 | 5 | 08月16日 - 08月22日期间，将评审报告在组委会的 Gitlab 上的 Issue 中提交，并配合组委会进行中期审核。 6 | 7 | ## 2. Wechaty 社区中期博客评审 8 | 9 | 在8月30日前以 Pull Requests 形式在 [wechaty.js.org](https://github.com/wechaty/wechaty.js.org) Repo 的学生对应博客下，补充评审结果的相关信息。 10 | 11 | 同时，按照社区博客提交规范，对学生提交的博客进行审核，审核通过后，在 GitHub **Approve** 这个 PR，然后交由 Wechaty PMC 进行博客审核。注意，社区导师一定要**提前、优先 Approve** 自己同学的 PR。 12 | 13 | 评审模板参考：[mentor-mid-term-template](../template/mentor-mid-term-template.md) 14 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/mentor-plan.md: -------------------------------------------------------------------------------- 1 | # 期初报告评审指南 2 | 3 | 按照社区博客提交规范，对学生提交的博客进行审核，审核通过后，在 GitHub **Approve** 这个 PR，然后交由 Wechaty PMC 进行博客审核。注意，社区导师一定要**提前、优先 Approve** 自己同学的 PR。 4 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/org-admin-be-better.md: -------------------------------------------------------------------------------- 1 | # 复盘 & 展望 2 | 3 | 1. 根据今年完成情况，整理第二年的手册，包括： 4 | - 学生工作 5 | - 导师工作 6 | - Org Admin 工作 7 | 1. 发布一个第二年的 OSPP 活动通知 Issue ，并把项目信息、期初、期中、期末的关键通知的模板创建好。 8 | 1. 向社区同步今年整体情况，并开始收集大家的 wish list, 发布到 [Summer Repo Issue](https://github.com/wechaty/summer/issues) 中 9 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/org-admin-final-term.md: -------------------------------------------------------------------------------- 1 | # 期末报告状态收集 & 答辩 2 | 3 | TBW 4 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/org-admin-first-meeting.md: -------------------------------------------------------------------------------- 1 | # 期初见面会 2 | 3 | - [ ] 在 `Summer of Wechaty Org Admin |SoW` 群中和所有 Org Admin 确认期初见面会的时间，并给所有参与的 Org Admin 期初见面会的日历邀请。 4 | - [ ] 组织导师和同学完成见面会，在 [Meeting Notes](https://docs.google.com/document/d/1fVCk8qRYc4RKGMf2UY5HOe07hEhPUOpGC34v88GEFJg/edit) 中创建见面会的会议，并引导同学完成注册，**注意要填写姓名、一句话介绍和邮箱，一定要有邮箱！**，参考 2021 年的会议信息： [Kick off OSPP First Meeting with Students](https://docs.google.com/document/d/1fVCk8qRYc4RKGMf2UY5HOe07hEhPUOpGC34v88GEFJg/edit#heading=h.ufupcyw9mp0h), 同时在见面会中向社区同步至少以下三项信息： 5 | - 当年的关键时间点，包括组委会报告提交、社区博客提交、社区答辩时间等 6 | - [OSPP（开源之夏）指导手册](https://wechaty.js.org/2021/06/24/summer-wechaty-guide/) 7 | - [Wechaty 社区开源协作最佳实践指南](https://wechaty.js.org/2021/06/23/the-wechaty-way/) 8 | - 每个同学的工作进度，回复到自己项目的 Issue 下方 9 | - [ ] 在 Wechaty OSPP 的官方微信群中 （`Summer of Wechaty - SoW`）发布公告，往届参与者也可以旁听期初见面会，了解当年项目。 10 | - [ ] 把所有入选的同学邀请到 Wechaty OSPP 的官方微信群中： `Summer of Wechaty - SoW` 11 | - [ ] 在期初见面会结束之后发布期初博客，参考 [Wechaty Open Source Promotion Plan 2021 Kickoff Meeting](http://wechaty.js.org/2021/06/24/wechaty-soc-kick-off-meeting/) 12 | - [ ] 推进所有同学提交社区的期初报告博客，并在当年 **OSPP 项目通知** 的 issue 下面同步期初博客完成进度，参考 [2021 年 OSPP 期初博客进度完成情况](https://github.com/wechaty/summer/issues/79#issuecomment-882059181)。同时可以在对应的微信群中向同学发起接龙。 13 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/org-admin-mid-term.md: -------------------------------------------------------------------------------- 1 | # 期中报告状态收集 & 答辩 2 | 3 | ## 1. 确认时间 4 | 5 | - [ ] 在 `Summer of Wechaty Org Admin |SoW` 群中和所有 Org Admin 确认期中见面会的时间，并给所有参与的 Org Admin 期初见面会的日历邀请，时间最好选为 6 | - [ ] 期中答辩日的时间在组委会要求提交中期报告至少提前5天 7 | - [ ] 对应的向社区通知期中报告的时间，最好在期中答辩日前2-3周 8 | 9 | ## 2. 发布期中报告和答辩通知 10 | 11 | - [ ] 确认时间后，在 [Meeting Notes](https://docs.google.com/document/d/1fVCk8qRYc4RKGMf2UY5HOe07hEhPUOpGC34v88GEFJg/edit) 中创建期中答辩会议，参考 2021 年的会议信息： [Wechaty OSPP(开源之夏) Midterm Demo Day](https://docs.google.com/document/d/1fVCk8qRYc4RKGMf2UY5HOe07hEhPUOpGC34v88GEFJg/edit#heading=h.5ztnno5qivcb) 12 | - [ ] 在 **OSPP 项目通知**的 issue 下面发布期中答辩通知，参考 [Wechaty 社区期中答辩（Mid-term Demo Day）通知](https://github.com/wechaty/summer/issues/79#issuecomment-899086777)，至少包括以下内容： 13 | - [ ] 同步给导师和同学期中答辩的时间，并引导所有导师和同学在 **Meeting Notes** 中完成注册，**注意要填写姓名、一句话介绍和邮箱，一定要有邮箱！** 14 | - [ ] 要求同学录制期中答辩的视频，包括**答辩视频**和 **Live Coding** 两个视频，并将对应的 YouTube 链接和国内视频网站的链接在 **答辩日前2天** 回复在自己项目的 Issue 下面。 15 | - [ ] 要求同学完成期中报告的博客，以被社区 Merge 为完成标准。 16 | - [ ] 在 Wechaty OSPP 的官方微信群中 （`Summer of Wechaty - SoW`）发布公告，公告内容参考 [Wechaty 社区期中答辩和期中报告通知](../template/announcement-mid-term-report-template.txt) 17 | - [ ] 在当年 **OSPP 项目通知**的 issue 下以回复的方式创建*组委会中期报告和社区中期博客完成进度表*，参考 [2021 年 OSPP 期中博客进度完成情况](https://github.com/wechaty/summer/issues/79#issuecomment-899023310)。并推进所有同学提交组委会和社区要求的的期中报告博客，根据同学和导师的接龙情况（下面会介绍接龙内容）、提交 PR 情况更新进度表。 18 | 19 | ## 3. 群内发起接龙 20 | 21 | - [ ] 在 Wechaty OSPP 的官方微信群中 （`Summer of Wechaty - SoW`）发起接龙，已提交完*组委会中期报告*的**同学**完成接龙，接龙内容参考 [组委会期中报告完成情况接龙](../template/fan-tan-mid-report-student-template.txt)。根据接龙情况，更新*组委会中期报告和社区中期博客完成进度表*，推进同学按时提交组委会要求的期中报告。 22 | - [ ] 在 Wechaty OSPP 的官方微信群中 （`Summer of Wechaty - SoW`）发起接龙，已在组委会完成*中期报告审核*的**导师**完成接龙，接龙内容参考 [导师期中报告审核完成情况接龙](../template/fan-tan-mid-report-mentor-template.txt)。根据接龙情况，更新*组委会中期报告和社区中期博客完成进度表*，推进导师按时完成组委会要求期中报告审核。 23 | - [ ] 在 Wechaty OSPP 的官方微信群中 （`Summer of Wechaty - SoW`）发起接龙，已在 Issue 下回复完*视频链接*的**同学**完成接龙，接龙内容参考 [视频完成情况接龙](../template/fan-tan-mid-report-video-template.txt)。根据接龙情况，更新 *Wechaty Meeting Notes* 中的 Agenda，确认所有同学完成 Wechaty 社区要求的两个视频。可参考 2021 年的会议信息： [Wechaty OSPP(开源之夏) Midterm Demo Day](https://docs.google.com/document/d/1fVCk8qRYc4RKGMf2UY5HOe07hEhPUOpGC34v88GEFJg/edit#heading=h.5ztnno5qivcb)。 Agenda 中至少包括如下内容： 24 | - [同学姓名] 项目名称 25 | - 答辩视频：https://答辩视频链接 26 | - Live Coding 视频：https://在线 Live Coding视频链接 27 | 28 | ## 4. 再次告知答辩时间 & 组织答辩 29 | 30 | - [ ] 在 Wechaty OSPP 的官方微信群中 （`Summer of Wechaty - SoW`）发布公告，引导同学在 *Wechaty Meeting Notes* 中完成中期答辩的会议注册，**注意要填写姓名、一句话介绍和邮箱，一定要有邮箱！**，公告内容参考 [Wechaty 社区中期答辩信息注册通知](../template/announcement-mid-term-meeting-template.txt) 31 | - [ ] 在答辩日，组织导师和同学完成期中答辩，答辩日程可参考 2021 年的会议信息： [Wechaty OSPP(开源之夏) Midterm Demo Day](https://docs.google.com/document/d/1fVCk8qRYc4RKGMf2UY5HOe07hEhPUOpGC34v88GEFJg/edit#heading=h.5ztnno5qivcb) 32 | 33 | ## 5. 中期答辩会议博客 34 | 35 | - [ ] 在期中答辩结束之后发布期中博客，参考 [暑期2020中期路演日（Mid-Term Demo Day）](https://wechaty.js.org/2020/08/22/summer-2020-wechaty-soc-midterm-demo-day/) 36 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/org-admin-prepare.md: -------------------------------------------------------------------------------- 1 | # 筹备阶段 2 | 3 | - [ ] 向 Wechaty Contributor 群中发起号召，号召 Wechaty 的 Contributor 成为当年开源之夏的 Mentor，并让 Mentor 在 [Wechaty Summer Of Code Repo](https://github.com/wechaty/summer) 中以 Issue 的方式发布任务。 4 | - [ ] 将所有有意向参加的 Mentor 邀请到 Wechaty OSPP 的官方微信群中： `Summer of Wechaty - SoW` 5 | - [ ] 在收集完所有的 OSPP 项目后，并发布项目清单 Issue，当年所有的重要通知，都在此 Issue 下以回复的形式通知社区，参考 2021 年的项目清单：[OSPP 项目通知 （ “暑期2021” ）- 2021](https://github.com/wechaty/summer/issues/79) 6 | - [ ] 筹备 OSPP 的报名和相关安排，至少参加(举办)一场会议，参考 2021 年的筹备会内容： 7 | - [Summer of Wechaty, 我们来啦](http://wechaty.js.org/2021/03/14/summer-2021-kick-off-meeting/) 8 | - [OSPP 2021 Project Status](http://wechaty.js.org/2021/06/11/ospp-startup-discussion/) 9 | - [ ] 完成当年的 OSPP 指导手册，并发布博客，参考 [OSPP（开源之夏）指导手册 - 2021](https://wechaty.js.org/2021/06/24/summer-wechaty-guide/) 10 | - [ ] 在项目清单 Issue 下面，把所有 Org Admin 需要完成的工作，以 checklist 的形式复制回复到 Issue 下面，方便后续 Wechaty Org Admin 完成相关工作，完成后在 Comment 中打钩确认 11 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/project-application-template.md: -------------------------------------------------------------------------------- 1 | ## OSPP 项目申请书模板 2 | 3 | 下面给出的申请书模板中被"[]"包围的部分需要替代为项目相关内容，请各位导师在2021.4.7 20:00(UTC+8)前在[本仓库Issue页面](https://github.com/wechaty/summer-of-wechaty/issues)修改或创建对应的Issue，内容为以下面内容为模板的项目申请书。导师们构思时，可以参考[暑期2020项目申请书](https://github.com/wechaty/summer-of-wechaty/issues?q=is%3Aissue+is%3Aclosed)的内容。 4 | 5 | ## 开源软件供应链点亮计划 6 | 7 | “开源软件供应链点亮计划-暑期2021”（以下简称 暑期2021）是由中科院软件所与 openEuler 社区共同举办的一项面向高校学生的暑期活动，旨在鼓励在校学生积极参与开源软件的开发维护，促进国内优秀开源软件社区的蓬勃发展。 8 | 9 | 根据项目的难易程度和完成情况，参与者还可获取“开源软件供应链点亮计划-暑期2021”活动奖金和奖杯。 10 | 11 | 官网：[summer.iscas.ac.cn](https://summer.iscas.ac.cn/) 12 | 13 | ## Wechaty 14 | 15 | Wechaty 是一个开源聊天机器人框架SDK，具有高度封装、高可用的特性，支持NodeJs, Python, Go 和Java 等多语言版本。在过去的4年中，服务了数万名开发者，收获了 Github 的 8000 Star。同时配置了完整的DevOps体系并持续按照Apache 的方式管理技术社区。 16 | 17 | # [项目名称] 18 | 19 | ## 背景介绍 20 | 21 | [背景介绍，可以在此介绍项目的具体背景] 22 | 23 | ## 需求介绍 24 | 25 | [需求介绍，可以分点介绍具体需求] 26 | 27 | ## 项目难度 28 | 29 | [可选项为：高（奖金：12000元）/中（奖金：9000元）/低（奖金：6000元）] 30 | 31 | > 根据组委会的建议，优化类的工作属于经典的高难度工作；中难度工作对应研一、研二计算机专业学生的开发能力；低难度工作对应大三、大四计算机专业学生的开发能力。 32 | 33 | ## 导师联系方式 34 | 35 | - [导师A]：[导师A身份1]、[导师A身份2]、...（[导师A邮箱]） 36 | - [导师B]：[导师B身份1]、[导师B身份2]、...（[导师B邮箱]） 37 | 38 | ## 项目产出目标 39 | 40 | [分点介绍项目产出目标，这是社区完成中期/结项考核的重要评判依据] 41 | 42 | ## 项目技术栈 43 | 44 | [在此按点提出对申请学生的技术栈要求] 45 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/student-final-term.md: -------------------------------------------------------------------------------- 1 | # 期末报告提交指南 2 | 3 | 期末报告提交后会有一个 OSPP 的 Final-term Demo Day， 导师和学生会在线上进行期末汇报。提交的期末报告包括 Final-term Demo Day 的视频和期末报告内容总结。 4 | 5 | 期末报告要**以博客的方式提交到 [wechaty.js.org](https://github.com/wechaty/wechaty.js.org) Repo** 中，在提交报告之前，可以先阅读 [Wechaty 社区规范](https://wechaty.js.org/2021/06/23/the-wechaty-way/), 至少了解下面内容： 6 | 7 | 1. Wechaty 的介绍 8 | 1. 社区沟通渠道 9 | 1. 会议规范 10 | 1. 博客发布规范 11 | 1. Issue 发布规范 12 | 1. PR 发布规范 13 | 14 | 尤其要注意的是在博客发布规范中详细的介绍了如何提交博客、如何在博客中嵌入视频等，在期末中会用到，具体要求如下： 15 | 16 | ## 1. 期末视频 17 | 18 | - 视频需要上传到 youtube 中，并联系 [Huan](https://wechaty.js.org/contributors/huan/) 添加到 wechaty 的 playlist 中。 19 | - 考虑到国内用户，可以上传到 bilibili 或者腾讯视频中。 20 | 21 | 可以参考去年飞书项目参与学生，今年飞书项目导师[范蕊](https://wechaty.js.org/contributors/roxanne718/)的视频： 22 | 23 | - [SOC-基于开放 API 封装 Wechaty 接口下的飞书聊天机器人-结项汇报](https://www.youtube.com/watch?v=eutz5EMlJCI) 24 | - [SOC-基于开放 API 封装 Wechaty 接口下的飞书聊天机器人-Demo演示](https://www.youtube.com/watch?v=_y5DktHdL9U) 25 | 26 | ## 2. 期末报告 27 | 28 | - 标题： `OSPP 2021-结项报告-你的标题` 29 | - 文件名： `2021-XX-XX-ospp-final-term-XX` 30 | - 报告 category 为：`project`, `ospp` 31 | - 报告 tag 至少包括：`summer-of-wechaty`,`summer-2021`,`ospp`,`ospp-2021`,`final-term` 32 | - 报告内容至少包括： 33 | - 项目信息 34 | - 项目名称 35 | - 方案描述 36 | - 时间规划 37 | - 项目总结 38 | - 项目成果 39 | - 期末汇报视频 40 | - 期末汇报 PPT 41 | - 遇到的问题及解决方案 42 | - 导师审核 43 | - 评审对象 44 | - 评审结果 45 | 46 | **提交PR时请注意：为这个 PR 打上 `ospp` 的标签，并在 PR 中填写自己项目的 GitHub Issue 链接，方便组委会进行审核。** 47 | 48 | 报告模板参考：[final-term-template](../template/final-term-template.md) 49 | 50 | ## 3. OSPP 2020 学生期末报告参考 51 | 52 | - [暑期2020 编写一个“每日一句”插件 结项报告](https://wechaty.js.org/2020/09/26/wechaty-words-per-day-plugin-final/) 53 | - [基于开放 API 封装 Wechaty 接口下的飞书聊天机器人：期末](https://wechaty.js.org/2020/09/30/wechaty-puppet-lark-final-blog/) 54 | - [暑期2020 基于python-wechaty的群聊助手机器人 结项成果展示](https://wechaty.js.org/2020/09/26/chassist-bot-final/) 55 | - [暑期2020 为 go-wechaty 设计实现插件体系 结项报告](https://wechaty.js.org/2020/09/27/go-wechaty-plugin/) 56 | - [基于Python-wechaty建立一个斗图机器人 POC 结项博客](https://wechaty.js.org/2020/09/27/python-wechaty-meme-bot-final/) 57 | - [基于RPA封装的Wechaty接口下的抖音聊天机器人结项报告](https://wechaty.js.org/2020/10/13/wechaty-puppet-douyin-final-term/) 58 | - [暑期2020 基于开放 API 封装 Wechaty 接口下的企业微信聊天机器人 终结成果展示](https://wechaty.js.org/2020/09/28/puppet-work-final/) 59 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/student-mid-term.md: -------------------------------------------------------------------------------- 1 | # 期中报告提交指南 2 | 3 | 期中报告提交后会有一个 OSPP 的 Mid-term Demo Day， 导师和学生会在线上进行期中汇报。提交的期中报告包括 Mid-term Demo Day 的视频和期中报告内容总结。[点击这里查看暑期2020中期路演日（Mid-Term Demo Day）会议实况](https://wechaty.js.org/2020/08/22/summer-2020-wechaty-soc-midterm-demo-day/) 4 | 5 | 期中报告要**以博客的方式提交到 [wechaty.js.org](https://github.com/wechaty/wechaty.js.org) Repo** 中，在提交报告之前，可以先阅读 [Wechaty 社区规范](https://wechaty.js.org/2021/06/23/the-wechaty-way/), 至少了解下面内容： 6 | 7 | 1. Wechaty 的介绍 8 | 1. 社区沟通渠道 9 | 1. 会议规范 10 | 1. 博客发布规范 11 | 1. Issue 发布规范 12 | 1. PR 发布规范 13 | 14 | 尤其要注意的是在博客发布规范中详细的介绍了如何提交博客、如何在博客中嵌入视频等，在期中博客中会用到，具体要求如下： 15 | 16 | ## 1. 期中 Demo Day 视频 17 | 18 | 每位开发者需要进行中期的展示，视频将添加至博客、提交到组委会中，并剪辑成完成的路演日视频，向全社区展示，吸引更多的开发者参与到对应的项目中： 19 | 20 | - 提交3-5分钟的、有真人出镜（视频会议软件录制）的、基于PPT的展示。 21 | - 提交不限时长的、有真人出镜（视频会议软件录制）的 Live Code。 22 | 23 | 学生要在8月26日之前将视频链接回复在对应项目的 Github Issue 下面进行提交，视频由同学们直接上传到Youtube / B站中，并直接将视频的链接和将视频以iframe方式附在各个博客中： 24 | 25 | - 视频需要上传到 youtube 中，并联系 [Huan](https://wechaty.js.org/contributors/huan/) 添加到 wechaty 的 playlist 中。 26 | - 考虑到国内用户，可以上传到 bilibili 或者腾讯视频中 27 | 28 | 可以参考去年优秀学生突出贡献奖获得者[江姗姗](https://wechaty.js.org/contributors/univerone/)的视频： 29 | 30 | - [期中汇报视频](https://www.bilibili.com/video/BV1vT4y157x5/) 31 | - [Live Coding 视频](https://www.bilibili.com/video/BV1ih411d75h) 32 | 33 | ## 2. 期中报告 34 | 35 | 在8月30日前，以Pull Requests形式在[wechaty.js.org Repo](https://github.com/wechaty/wechaty.js.org)中提交博客。 36 | 37 | - 标题： `OSPP 2021-期中报告-你的标题` 38 | - 文件名： `2021-XX-XX-ospp-mid-term-XX` 39 | - 报告 category 为：`project`, `ospp` 40 | - 报告 tag 至少包括：`summer-of-wechaty`,`summer-2021`,`ospp`,`ospp-2021`,`mid-term`，`ospp` 41 | - 报告内容至少包括： 42 | - 项目信息 43 | - 项目名称 44 | - 方案描述 45 | - 时间规划 46 | - 项目进度 47 | - 已完成工作 48 | - 遇到的问题及解决方案 49 | - 后续工作安排 50 | - 项目成果 51 | - 期中汇报的视频，可以参考 [使用jekyll include在wechaty博客中快速插入视频](https://wechaty.js.org/2020/08/24/add-video-to-wechaty-blog/) 52 | - Live Coding/Demo 视频 53 | 54 | **提交PR时请注意：为这个 PR 打上 `ospp` 的标签，并在 PR 中填写自己项目的 GitHub Issue 链接，方便组委会进行审核。** 55 | 56 | 报告模板参考：[mid-term-template](../template/mid-term-template.md) 57 | 58 | ## 3. OSPP 2020 学生期中报告参考： 59 | 60 | - [基于开放 API 封装 Wechaty 接口下的飞书聊天机器人：期中](https://wechaty.js.org/2020/08/19/wechaty-puppet-lark-mid-term-blog/) 61 | - [暑期2020 编写一个“每日一句”插件 POC 成果展示](https://wechaty.js.org/2020/08/15/wechaty-words-per-day-plugin-mid-term/) 62 | - [暑期2020 基于python-wechaty的群聊助手机器人 POC 成果展示](https://wechaty.js.org/2020/08/14/python-wechaty-groupchat-assistant-bot-poc/) 63 | - [暑期2020 基于 RPA 封装 Wechaty 接口下的快手聊天机器人 中期报告](https://wechaty.js.org/2020/08/20/wechaty-puppet-kuaishou-mid-term/) 64 | - [Wechaty Java 移植组件开发](https://wechaty.js.org/2020/08/17/java-wechaty-transplant-midpoc/) 65 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2021/student-plan.md: -------------------------------------------------------------------------------- 1 | # 期初报告提交指南 2 | 3 | 期初报告要**以博客的方式提交到 [wechaty.js.org](https://github.com/wechaty/wechaty.js.org) Repo** 中，在提交报告之前，可以先阅读 [Wechaty 社区规范](https://wechaty.js.org/2021/06/23/the-wechaty-way/), 至少了解下面内容： 4 | 5 | 1. Wechaty 的介绍 6 | 1. 社区沟通渠道 7 | 1. 会议规范 8 | 1. 博客发布规范 9 | 1. Issue 发布规范 10 | 1. PR 发布规范 11 | 12 | 尤其要注意的是在博客发布规范中详细的介绍了如何提交博客、如何在博客中嵌入视频等，在期初中会用到，具体要求如下： 13 | 14 | ## 1. 个人介绍 15 | 16 | 请将自己的介绍以 markdown 的方式提交到 [wechaty.js.org](https://github.com/wechaty/wechaty.js.org) Repo 的 `jekyll/_contributors` 目录下。 17 | 18 | 可以参考以下的开发者介绍内容编写页： 19 | 20 | - [吴京京, wj-mcat, Creator of python-wechaty](https://raw.githubusercontent.com/wechaty/wechaty.js.org/master/jekyll/_contributors/wj-mcat.md) 21 | - [江姗姗, univerone, OSPP 2020的优秀学生突出贡献奖获得者](https://raw.githubusercontent.com/wechaty/wechaty.js.org/master/jekyll/_contributors/univerone.md) 22 | 23 | ## 2. 期初报告 24 | 25 | - 标题： `OSPP 2021-期初报告-你的标题` 26 | - 文件名： `2021-XX-XX-ospp-plan-XX` 27 | - 报告 category 为：`project`, `ospp` 28 | - 报告 tag 至少包括：`summer-of-wechaty`,`summer-2021`,`ospp`,`ospp-2021`,`plan` 29 | - 报告内容至少包括： 30 | - 项目名称 31 | - 合作者介绍 32 | - 导师 33 | - 项目介绍 34 | - 项目计划 35 | 36 | **提交PR时请注意：为这个 PR 打上 `ospp` 的标签，并在 PR 中填写自己项目的 GitHub Issue 链接，方便组委会进行审核。** 37 | 38 | ## 3. OSPP 2020 学生期初报告参考： 39 | 40 | - [暑期2020 为 go-wechaty 设计实现插件体系 计划书](https://wechaty.js.org/2020/07/19/go-wechaty-plugin-dev-plan/) 41 | - [基于python-wechaty的群聊助手机器人](https://wechaty.js.org/2020/07/18/python-wechaty-groupchat-assistant-bot/) 42 | - [基于开放 API 封装 Wechaty 接口下的飞书聊天机器人：期初](https://wechaty.js.org/2020/07/29/wechaty-puppet-lark-plan-blog/) 43 | - [基于Python-wechaty建立一个斗图机器人](https://wechaty.js.org/2020/07/18/python-wechaty-meme-bot/) 44 | - [暑期2020 编写一个“每日一句”插件 计划书](https://wechaty.js.org/2020/07/18/wechaty-words-per-day-plugin-plan/) 45 | - [暑期2020[基于 RPA 封装 Wechaty 接口下的快手聊天机器人]计划书](https://wechaty.js.org/2020/07/28/wechaty-rpa-kuaishou-plan/) 46 | - [基于RPA封装的Wechaty接口下的抖音聊天机器人](https://wechaty.js.org/2020/07/28/wechaty-puppet-douyin/) 47 | - [暑期2020 基于开放 API 封装 Wechaty 接口下的企业微信聊天机器人 计划书](https://wechaty.js.org/2020/08/19/puppet-work-plan/) 48 | - [暑期2020 Go-wechaty Github Action optimization 计划书](https://wechaty.js.org/2020/07/30/go-wechaty-gh-optimization-poc/) 49 | - [Wechaty Java 移植组件开发](https://wechaty.js.org/2020/07/27/java-wechaty-transplant/) 50 | - [基于开放 API 封装 Wechaty 接口下的钉钉聊天机器人 具体计划](https://wechaty.js.org/2020/07/19/wechaty-puppet-dingtalk/) 51 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2022/mentors.md: -------------------------------------------------------------------------------- 1 | # 导师列表 2 | 3 | ## #1 4 | 5 | ### 导师姓名 6 | 7 | xxx 8 | 9 | ### 导师邮箱 10 | 11 | xxx 12 | 13 | ### 导师在社区贡献时使用的邮箱 14 | 15 | xxx 16 | 17 | ### 导师贡献的社区仓库地址 18 | 19 | **NOTE**：可以多个 20 | 21 | xxx 22 | 23 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2022/profile.md: -------------------------------------------------------------------------------- 1 | # 组织详情 2 | 3 | ## 组织名称 4 | 5 | Wechaty 6 | 7 | ## 组织类型 8 | 9 | 开源社区 10 | 11 | ## 官网地址 12 | 13 | https://wechaty.js.org/ 14 | 15 | ## 组织logo 16 | 17 | https://wechaty.js.org/img/wechaty-logo.svg 18 | 19 | ## 公共邮箱 20 | 21 | wechaty@googlegroups.com 22 | 23 | ## 编程语言标签 24 | 25 | Python,Go,JavaScript,Java 26 | 27 | ## 涉及技术领域标签 28 | 29 | NodeJS,NLP,AI, RPA; Conversational AI 30 | 31 | ## 组织简介 32 | 33 | Wechaty是一个用于构建聊天机器人的开源软件。它是一个现代的对话式RPA SDK，聊天机器人开发者可以用仅仅几行代码来创建一个机器人。 34 | 35 | ## 详细介绍 36 | 37 | Wechaty 是一个开源聊天机器人框架SDK，具有高度封装、高可用的特性，支持NodeJs, Python, Go 和Java 等多语言版本。在过去的4年中，服务了数万名开发者，收获了 Github 的 8000 Star。同时配置了完整的 DevOps 体系并持续按照 Apache 的方式管理技术社区。 -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2022/projects.md: -------------------------------------------------------------------------------- 1 | # 项目列表 2 | 3 | 本届可以提交 4 个项目 4 | 5 | ## 项目1 6 | 7 | ### 项目名称 8 | 9 | xxx 10 | 11 | ### Project Name 12 | 13 | xxx 14 | 15 | ### 项目支持报名语言/Project Support Language 16 | 17 | 三选一： 18 | 19 | * 中英文均可(Both Chinese and English) 20 | * 仅中文(Chinese only) 21 | * 仅英文(English only) 22 | 23 | ### 项目主导师/Project Mentor 24 | 25 | NOTE：仅可选择一位/Only one can be selected 26 | 27 | ### 项目描述 28 | 29 | xxx 30 | 31 | ### Project Description 32 | 33 | xxx 34 | 35 | ### 难度/Difficulty 36 | 37 | 二选一： 38 | 39 | * 基础/Basic 40 | * 进阶/Advanced 41 | 42 | ### 涉及技术领域标签/Labels of Technical Field 43 | 44 | NOTE：非以上标签，请输入；多个标签以英文逗号','分割/If the label does not exist, please enter it by yourself. Multiple labels are separated by ',' comma 45 | 46 | ### 编程语言标签/Labels of Programming Language 47 | 48 | NOTE：非以上标签，请输入；多个标签以英文逗号','分割/If the label does not exist, please enter it by yourself. Multiple labels are separated by ',' comma 49 | 50 | ### 项目产出要求/Project Output Requirements 51 | 52 | | 产出要求概述 | 具体产出细节 | 53 | | ------------ | ------------ | 54 | | | | 55 | | | | 56 | | | | 57 | 58 | ### 项目技术要求/Project Technical Requirements 59 | 60 | | 技术要求概述 | 技术要求细节 | 61 | | ------------ | ------------ | 62 | | | | 63 | | | | 64 | | | | 65 | 66 | ### 项目成果仓库/Project Repository 67 | 68 | | 最终成果仓库 | 69 | | ------------ | 70 | | | 71 | | | 72 | | | 73 | 74 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2022/screenshot_add_new_mentor.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/wechaty/summer/996f9316096674fd5fc81dd1ec9200f2011d23d5/iscas-open-source-promotion-plan/2022/screenshot_add_new_mentor.png -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/2022/screenshot_add_new_project.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/wechaty/summer/996f9316096674fd5fc81dd1ec9200f2011d23d5/iscas-open-source-promotion-plan/2022/screenshot_add_new_project.png -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/README.md: -------------------------------------------------------------------------------- 1 | # 开源软件供应链点亮计划 2 | 3 | Institute of Software Chinese Academy of Sciences (ISCAS) Open Source Promotion Plan (OSPP) encourages everyone to pay close attention to open source software and open source community, aiming to cultivate and explore more outstanding developers. ‘Summer 2021’ will be held in this summer. We will collaborate closely with the open source community to provide one-to-one mentor guidance and invite some specialists to conduct free online lectures. In order to promote the development of open source software and facilitate the construction of excellent open source software community, we encourage researchers, open source enthusiasts, professors as well as students to participate in the development and maintenance of open source software. Furthermore, ‘Summer 2021’ is supposed to increase the activity of open source projects, and promote the development of open source ecology. 4 | 5 | 开源软件供应链点亮计划鼓励大家关注开源软件和开源社区，致力于培养和发掘更多优秀的开发者。 6 | 活动将在暑期进行，我们将与开源社区紧密合作，提供一对一的导师指导，邀请技术大牛开展线上免费讲座。 7 | 我们鼓励研究人员、开源爱好者、在校师生参与开源软件的开发与维护，促进开源软件的发展和优秀开源软件社区建设， 8 | 增加开源项目的活跃度，推进开源生态的发展。 9 | 10 | - 官网： 11 | - 详细介绍： 12 | - GitHub: 13 | 14 | ## Years 15 | 16 | 1. [2021](2021/) 17 | 1. [2020](2020/) 18 | 19 | ## Organization Administrator 20 | 21 | ### 2020 22 | 23 | - [Yuan](https://wechaty.js.org/contributors/windmemory), CTO of Juzi.BOT, Creator of Wechaty Puppet Service [WXWork](https://wechaty.js.org/docs/puppet-services/wxwork) 24 | - [Bohao](https://wechaty.js.org/contributors/rickyyin98/), CMO of Juzi.BOT 25 | - [Jing](https://wechaty.js.org/contributors/wj-mcat), Author of [Python Wechaty](https://github.com/wechaty/python-wechaty) 26 | - [Huan](https://wechaty.js.org/contributors/huan), Tencent TVP of Chatbot, Creator of Wechaty 27 | - [Rui](https://pre-angel.com/peoples/jiarui-li/), Microsoft AI [MVP](https://mvp.microsoft.com/en-us/PublicProfile/5003226), Co-creator of Wechaty 28 | 29 | ### 2021 30 | 31 | - [Jing](https://wechaty.js.org/contributors/wj-mcat), Author of [Python Wechaty](https://github.com/wechaty/python-wechaty) 32 | - [Fairy](https://github.com/Roxanne718), Author of [Lark Puppet](https://github.com/wechaty/wechaty-puppet-lark) 33 | - [Huan](https://wechaty.js.org/contributors/huan), Tencent TVP of Chatbot, Creator of Wechaty 34 | - [Rui](https://pre-angel.com/peoples/jiarui-li/), Microsoft AI [MVP](https://mvp.microsoft.com/en-us/PublicProfile/5003226), Co-creator of Wechaty 35 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/announcement-mid-term-meeting-template.txt: -------------------------------------------------------------------------------- 1 | 📢 我们将在 【X月X日（周X）晚 XX:00】进行 Wechaty 的中期 Demo Day，每个学生进行 Wechaty 的中期答辩。社区导师、同学们请尽快到 Meeting Notes 中完成参会注册！ 2 | 3 | Meeting Notes 信息：https://bit.ly/MeetingNotes地址短连接 4 | 5 | 注册注意要填写姓名、一句话介绍和邮箱，一定要有邮箱，方便后续信息通知。 6 | 7 | 预祝同学们中期 Demo Day 答辩顺利！ 8 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/announcement-mid-term-report-template.txt: -------------------------------------------------------------------------------- 1 | 📢 我们将在 【X月X日（周X）晚 XX:00】进行 Wechaty 的中期 Demo Day，每个学生进行Wechaty的中期答辩。社区导师、同学们有以下工作需要完成，以满足 Wechaty 社区和 OSPP 组委会的要求。 2 | 3 | 学生需要完成： 4 | 1. X.XX号之前完成【组委会中期报告提交】 5 | 2. X.XX号之前完成【期中 Demo Day 视频】 6 | 3. X.XX号之前完成【Wechaty 社区期中报告博客】 7 | 8 | 导师需要完成： 9 | 1. X.XX号之前完成【组委会中期报告评审】 10 | 2. X.XX号之前完成【Wechaty 社区期中报告导师评审】 11 | 12 | 请各位同学和导师把提交给组委会的中期报告和评审内容同步回复到自己项目的issue下面，因为这样可以开放给社区所有人看到。 13 | 14 | 关于期中内容请看 https://github.com/wechaty/summer/issues/XX#issuecomment-期中报告issue通知 15 | 去年期中Demo Day 会议博客在这里：https://wechaty.js.org/2020/08/22/summer-2020-wechaty-soc-midterm-demo-day/ 16 | 更多详细信息可以看 Wechaty 开源之夏指导手册：https://wechaty.js.org/2021/06/24/summer-wechaty-guide/ 17 | 18 | X月X日会议议程信息在这里，参加的同学也请提前注册：https://bit.ly/MeetingNotes地址短连接 19 | 20 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/fan-tan-mid-report-mentor-template.txt: -------------------------------------------------------------------------------- 1 | #接龙 2 | 『暑期2021中期导师审核完成确认』 3 | 4 | 组委会要求 XX（时间）之前完成审核。若导师未在截止日期前在系统内完成评审，该项目将被视为自动放弃，组委会将不再支持此项目。 5 | 6 | 请各个项目的 mentor ，在确认完成审核后，接龙确认。（同时更新对应的 GitHub Issue） 7 | 例 姓名/项目简称/Issue# 8 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/fan-tan-mid-report-student-template.txt: -------------------------------------------------------------------------------- 1 | 接龙 2 | 『暑期2021中期学生报告提交确认』 3 | 4 | 组委会要求 XX (时间) 之前提交报告。若同学未在截止日期前在系统内提交报告，该项目将被视为自动放弃，组委会将不再支持此项目。 5 | 6 | Wechaty OSPP'21 中期需提交内容包括： 7 | 1、组委会要求提交的报告 8 | 2、Wechaty社区要求提交的博客 9 | 10 | 请各个项目的同学，在确认已经完成后，接龙确认。（同时更新对应的 GitHub Issue） 11 | 例 姓名/项目简称/Issue# 12 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/fan-tan-mid-report-video-template.txt: -------------------------------------------------------------------------------- 1 | #接龙 2 | 『暑期2021中期 Demo Day 视频完成确认』 3 | 4 | [烟花]XX（时间）[烟花] 将会进行 Wechaty 的中期 Demo Day 展示，每个学生进行Wechaty的中期答辩。 5 | 6 | 期中 Demo Day 视频需要2个视频： 7 | 1. 期中汇报视频 （3-5分钟的、有真人出镜的、基于PPT的展示） 8 | 2. Live Coding 视频（不限时长的、有真人出镜的 Live Coding） 9 | 10 | 可以参考去年@范蕊 的视频： 11 | 1. 答辩视频：https://www.bilibili.com/video/BV1n54y1U7Fn 12 | 2. Live Coding: https://www.bilibili.com/video/BV1v54y1e7LM 13 | 14 | 视频提交截止日期： 15 | [爆竹] XX（时间） [爆竹] 16 | 请及时提交，或者会影响项目评分。 17 | 18 | 各个项目的同学 ，在完成视频录制后，接龙确认。（同时将视频链接更新到对应的 GitHub Issue） 19 | 20 | 1. 姓名/项目简介/Issue# 21 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/final-term-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "OSPP 2021-期中报告-项目名称" 3 | author: XXXX 4 | categories: 5 | - project 6 | - ospp 7 | image: /assets/date/image.webp 8 | tags: 9 | - summer-of-wechaty 10 | - summer-2021 11 | - ospp 12 | - ospp-2021 13 | - final-term 14 | --- 15 | 16 | 17 | 21 | 22 | ## [项目名称]信息 23 | 24 | - 导师：[导师名称] 25 | - 学生：[学生名称] 26 | - 项目名称：XXXX 27 | - 项目介绍：填写Github Issue 链接，如 28 | - 方案描述： 29 | 30 | ## 时间规划 31 | 32 | ### 1. 内容摘要 33 | 34 | - 时间：XXXX 35 | - 内容：详细内容描述 36 | 37 | ### 2. 内容摘要 38 | 39 | - 时间：XXXX 40 | - 内容：详细内容描述 41 | 42 | ## 项目成果 43 | 44 | - 项目仓库: 45 | - npm package： 46 | 47 | ### 遇到的问题及解决方案 48 | 49 | 1. 问题1概要 50 | - 问题描述：XXXXXXX 51 | - 解决方案：XXXXXXX 52 | 1. 问题2概要 53 | - 问题描述：XXXXXXX 54 | - 解决方案：XXXXXXX 55 | 56 | ### Live Coding视频 57 | 58 | {% raw %} 59 | {% include iframe.html src="视频链接" %} 60 | 61 | > 国内链接：<国内视频的链接> 62 | 63 | {% endraw %} 64 | 65 | ### 期中答辩视频 66 | 67 | {% raw %} 68 | {% include iframe.html src="视频链接" %} 69 | 70 | > 国内链接：<国内视频的链接> 71 | 72 | {% endraw %} 73 | 74 | ### 项目 PPT 75 | 76 | {% raw %} 77 | {% include iframe.html src="pdf链接" %} 78 | {% endraw %} 79 | 80 | ## 联系我们 81 | 82 | - 项目链接：GitHub Issue 链接，如 83 | - 联系方式：XXX 84 | 85 | “[开源软件供应链点亮计划-暑期2021](https://summer.iscas.ac.cn)”（以下简称 暑期2021）是由中科院软件所与 openEuler 社区共同举办的一项面向高校学生的暑期活动。旨在鼓励在校学生积极参与开源软件的开发维护，促进国内优秀开源软件社区的蓬勃发展。活动联合各大开源社区，针对重要开源软件的开发与维护提供项目，并向全球高校学生开放报名。 学生可自主选择感兴趣的项目进行申请，并在中选后获得该软件资深维护者（社区导师）亲自指导的机会。 根据项目的难易程度和完成情况，参与者还可获取“开源软件供应链点亮计划-暑期2021”活动奖金和奖杯。 86 | 87 | 本项目 [项目名称] 系 暑期2021 支持的开源项目。 88 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/mentor-final-term-template.md: -------------------------------------------------------------------------------- 1 | ## 评审对象 2 | 3 | - 评审内容：*结项报告* 4 | - 提交人：*学生姓名* 5 | 6 | ## 评审结果 7 | 8 | - 项目完成度：*评价学生是否按照原定方案实施项目，以及完成情况如何* 9 | - 学生参与度：*评价学生在项目实施过程中是否积极参与* 10 | - 代码贡献量：*评价学生在该项目中，为开源项目贡献的代码量* 11 | - 综合评价及建议：*总结性评价，并给出改进建议* 12 | - 最终评审结果：“通过” 或者 “不通过” （“不通过” 意为着项目终止，且学生将无法获得相应的奖金） 13 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/mentor-mid-term-template.md: -------------------------------------------------------------------------------- 1 | ## 评审对象 2 | 3 | - 评审内容：*中期报告|结项报告* 4 | - 提交人：*学生姓名* 5 | 6 | ## 评审结果 7 | 8 | - 项目完成度：*评价学生是否按照原定方案实施项目，以及完成情况如何* 9 | - 学生参与度：*评价学生在项目实施过程中是否积极参与* 10 | - 代码贡献量：*评价学生在该项目中，为开源项目贡献的代码量* 11 | - 综合评价及建议：*总结性评价，并给出改进建议* 12 | - 最终评审结果：“通过” 或者 “不通过” （“不通过” 意为着项目终止，且学生将无法获得相应的奖金） 13 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/mentor-weekly-report-template.md: -------------------------------------------------------------------------------- 1 | # [项目名称] 导师评分 2 | 3 | 日期：XXXX-XX-XX 4 | 5 | ## 本周进度报告的评分 6 | 7 | - [ ] 1: Deliverable not acceptable 8 | - [ ] 2: Deliverable is below expectations 9 | - [ ] 3: Deliverable is OK 10 | - [ ] 4: Deliverable is above expectations 11 | - [ ] 5: Deliverable is perfect 12 | 13 | ## 其他需要说明和同步的事项 14 | 15 | XXX 16 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/mid-term-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "OSPP 2021-期中报告-项目名称" 3 | author: XXXX 4 | categories: 5 | - project 6 | - ospp 7 | image: /assets/date/image.webp 8 | tags: 9 | - summer-of-wechaty 10 | - summer-2021 11 | - ospp 12 | - ospp-2021 13 | - mid-term 14 | --- 15 | 16 | 17 | 21 | 22 | ## [项目名称]信息 23 | 24 | - 导师：[导师名称] 25 | - 学生：[学生名称] 26 | - 项目名称：XXXX 27 | - 项目介绍：填写Github Issue 链接，如 28 | - 方案描述：XXXXXXXXX 29 | 30 | ## 时间规划 31 | 32 | ### 1. 内容摘要 33 | 34 | - 时间：XXXX 35 | - 内容：详细内容描述 36 | 37 | ### 2. 内容摘要 38 | 39 | - 时间：XXXX 40 | - 内容：详细内容描述 41 | 42 | ## 项目进度 43 | 44 | ### 已完成工作 45 | 46 | 47 | 1. 成果1 48 | 详细信息 49 | 1. 成果2 50 | 详细信息 51 | 52 | ### 遇到的问题及解决方案： 53 | 54 | 55 | 1. 问题1概要 56 | - 问题描述：XXXXXXX 57 | - 解决方案：XXXXXXX 58 | 1. 问题2概要 59 | - 问题描述：XXXXXXX 60 | - 解决方案：XXXXXXX 61 | 62 | ### 后续工作安排： 63 | 64 | 65 | XXXXXXX 66 | 67 | ## 项目成果 68 | 69 | - 项目仓库: 70 | - npm package： 71 | 72 | ### Live Coding视频 73 | 74 | {% raw %} 75 | {% include iframe.html src="视频链接" %} 76 | 77 | > 国内链接：<国内视频的链接> 78 | 79 | {% endraw %} 80 | 81 | ### 期中答辩视频 82 | 83 | {% raw %} 84 | {% include iframe.html src="视频链接" %} 85 | 86 | > 国内链接：<国内视频的链接> 87 | 88 | {% endraw %} 89 | 90 | ### 项目 PPT 91 | 92 | {% raw %} 93 | {% include iframe.html src="pdf链接" %} 94 | {% endraw %} 95 | 96 | ## 联系我们 97 | 98 | - 项目链接：GitHub Issue 链接，如 99 | - 联系方式：XXXXX 100 | 101 | “[开源软件供应链点亮计划-暑期2021](https://summer.iscas.ac.cn)”（以下简称 暑期2021）是由中科院软件所与 openEuler 社区共同举办的一项面向高校学生的暑期活动。旨在鼓励在校学生积极参与开源软件的开发维护，促进国内优秀开源软件社区的蓬勃发展。活动联合各大开源社区，针对重要开源软件的开发与维护提供项目，并向全球高校学生开放报名。 学生可自主选择感兴趣的项目进行申请，并在中选后获得该软件资深维护者（社区导师）亲自指导的机会。 根据项目的难易程度和完成情况，参与者还可获取“开源软件供应链点亮计划-暑期2021”活动奖金和奖杯。 102 | 103 | 本项目 [项目名称] 系 暑期2021 支持的开源项目。 104 | -------------------------------------------------------------------------------- /iscas-open-source-promotion-plan/template/student-weekly-report-template.md: -------------------------------------------------------------------------------- 1 | # [项目名称] 进度报告 2 | 3 | 日期：XXXX-XX-XX 4 | 5 | ## 本周完成的成果 6 | 7 | 1. XX 8 | 1. XX 9 | 10 | ## 本周遇到的困难和需要配合的地方 11 | 12 | 1. XX 13 | 14 | ## 下周的开发计划和预计成果 15 | 16 | 1. XX 17 | 18 | ## 其他需要说明和同步的事项 19 | 20 | 1. XX 21 | --------------------------------------------------------------------------------