@serverless-devs/s 2.0.96 → 2.0.97-beta.6

package/CONTRIBUTING.md

@@ -1,189 +0,0 @@
-# Contributing to Serverless Devs
-
-It is warmly welcomed if you have interest to hack on Serverless Devs. First, we encourage this kind of willing very much. And here is a list of contributing guide for you.
-
-## Topics
-
-- [Contributing to Serverless Devs](#contributing-to-serverless-devs)
-  - [Topics](#topics)
-  - [Reporting security issues](#reporting-security-issues)
-  - [Reporting general issues](#reporting-general-issues)
-  - [Code and doc contribution](#code-and-doc-contribution)
-    - [Workspace Preparation](#workspace-preparation)
-    - [Branch Definition](#branch-definition)
-    - [Commit Rules](#commit-rules)
-      - [Commit Message](#commit-message)
-      - [Commit Content](#commit-content)
-    - [PR Description](#pr-description)
-  - [Test case contribution](#test-case-contribution)
-  - [Package contribution](#package-contribution)
-  - [Engage to help anything](#engage-to-help-anything)
-
-
-
-## Reporting security issues
-
-Security issues are always treated seriously. As our usual principle, we discourage anyone to spread security issues. If you find a security issue of Serverless Devs, please do not discuss it in public and even do not open a public issue. Instead we encourage you to send us a private email to  [service@serverlessfans.com](mailto:service@serverlessfans.com) to report this.
-
-## Reporting general issues
-
-To be honest, we regard every user of Serverless Devs as a very kind contributor. After experiencing Serverless Devs, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/Serverless-Devs/Serverless-Devs/issues/new/choose).
-
-Since we collaborate project Serverless Devs in a distributed way, we appreciate **WELL-WRITTEN**, **DETAILED**, **EXPLICIT** issue reports. To make the communication more efficient, we wish everyone could search if your issue is an existing one in the searching list. If you find it existing, please add your details in comments under the existing issue instead of opening a brand new one.
-
-To make the issue details as standard as possible, we setup an [ISSUE TEMPLATE](./.github/ISSUE_TEMPLATE) for issue reporters. Please **BE SURE** to follow the instructions to fill fields in template.
-
-There are a lot of cases when you could open an issue:
-
-* bug report
-* feature request
-* performance issues
-* feature proposal
-* feature design
-* help wanted
-* doc incomplete
-* test improvement
-* any questions on project
-* and so on
-
-Also we must remind that when filling a new issue, please remember to remove the sensitive data from your post. Sensitive data could be password, secret key, network locations, private business data and so on.
-
-## Code and doc contribution
-
-Every action to make project Serverless Devs better is encouraged. On GitHub, every improvement for Serverless Devs could be via a PR (short for pull request).
-
-* If you find a typo, try to fix it!
-* If you find a bug, try to fix it!
-* If you find some redundant codes, try to remove them!
-* If you find some test cases missing, try to add them!
-* If you could enhance a feature, please **DO NOT** hesitate!
-* If you find code implicit, try to add comments to make it clear!
-* If you find code ugly, try to refactor that!
-* If you can help to improve documents, it could not be better!
-* If you find document incorrect, just do it and fix that!
-* ...
-
-Actually it is impossible to list them completely. Just remember one principle:
-
-> WE ARE LOOKING FORWARD TO ANY PR FROM YOU.
-
-Since you are ready to improve Serverless Devs with a PR, we suggest you could take a look at the PR rules here.
-
-* [Workspace Preparation](#workspace-preparation)
-* [Branch Definition](#branch-definition)
-* [Commit Rules](#commit-rules)
-* [PR Description](#pr-description)
-
-### Workspace Preparation
-
-To put forward a PR, we assume you have registered a GitHub ID. Then you could finish the preparation in the following steps:
-
-1. **FORK** Serverless Devs to your repository. To make this work, you just need to click the button Fork in right-left of [Serverless-Devs/Serverless-Devs](https://github.com/Serverless-Devs/Serverless-Devs) main page. Then you will end up with your repository in `https://github.com/<your-username>/Serverless-Devs`, in which `your-username` is your GitHub username.
-
-1. **CLONE** your own repository to develop locally. Use `git clone git@github.com:<your-username>/Serverless-Devs.git` to clone repository to your local machine. Then you can create new branches to finish the change you wish to make.
-
-1. **Set Remote** upstream to be `git@github.com:Serverless-Devs/Serverless-Devs.git` using the following two commands:
-
-```
-git remote add upstream git@github.com:Serverless-Devs/Serverless-Devs.git
-git remote set-url --push upstream no-pushing
-```
-
-With this remote setting, you can check your git remote configuration like this:
-
-```
-$ git remote -v
-origin     git@github.com:<your-username>/Serverless-Devs.git (fetch)
-origin     git@github.com:<your-username>/Serverless-Devs.git (push)
-upstream   git@github.com:Serverless-Devs/Serverless-Devs.git (fetch)
-upstream   no-pushing (push)
-```
-
-Adding this, we can easily synchronize local branches with upstream branches.
-
-### Branch Definition
-
-Right now we assume every contribution via pull request is for [branch develop](https://github.com/Serverless-Devs/Serverless-Devs/tree/develop) in Serverless Devs. Before contributing, be aware of branch definition would help a lot.
-
-As a contributor, keep in mind again that every contribution via pull request is for branch develop. While in project Serverless Devs, there are several other branches, we generally call them release branches(such as 0.6.0,0.6.1), feature branches, hotfix branches and master branch.
-
-When officially releasing a version, there will be a release branch and named with the version number. 
-
-After the release, we will merge the commit of the release branch into the master branch.
-
-When we find that there is a bug in a certain version, we will decide to fix it in a later version or fix it in a specific hotfix version. When we decide to fix the hotfix version, we will checkout the hotfix branch based on the corresponding release branch, perform code repair and verification, and merge it into the develop branch and the master branch.
-
-For larger features, we will pull out the feature branch for development and verification.
-
-
-### Commit Rules
-
-Actually in Serverless Devs, we take two rules serious when committing:
-
-* [Commit Message](#commit-message)
-* [Commit Content](#commit-content)
-
-#### Commit Message
-
-Commit message could help reviewers better understand what is the purpose of submitted PR. It could help accelerate the code review procedure as well. We encourage contributors to use **EXPLICIT** commit message rather than ambiguous message. In general, we advocate the following commit message type:
-
-* docs: xxxx. For example, "docs: add docs about Serverless Devs cluster installation".
-* feature: xxxx.For example, "feature: support oracle in AT mode".
-* bugfix: xxxx. For example, "bugfix: fix panic when input nil parameter".
-* refactor: xxxx. For example, "refactor: simplify to make codes more readable".
-* test: xxx. For example, "test: add unit test case for func InsertIntoArray".
-* other readable and explicit expression ways.
-
-On the other side, we discourage contributors from committing message like the following ways:
-
-* ~~fix bug~~
-* ~~update~~
-* ~~add doc~~
-
-If you get lost, please see [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/) for a start.
-
-#### Commit Content
-
-Commit content represents all content changes included in one commit. We had better include things in one single commit which could support reviewer's complete review without any other commits' help. In another word, contents in one single commit can pass the CI to avoid code mess. In brief, there are three minor rules for us to keep in mind:
-
-* avoid very large change in a commit;
-* complete and reviewable for each commit.
-* check git config(`user.name`, `user.email`) when committing to ensure that it is associated with your github ID.
-* when submitting pr, please add a brief description of the current changes to the X.X.X.md file under the 'changes/' folder
-
-
-In addition, in the code change part, we suggest that all contributors should read the [code style of Serverless Devs](#code-style).
-
-No matter commit message, or commit content, we do take more emphasis on code review.
-
-
-### PR Description
-
-PR is the only way to make change to Serverless Devs project files. To help reviewers better get your purpose, PR description could not be too detailed. We encourage contributors to follow the [PR template](./.github/PULL_REQUEST_TEMPLATE.md) to finish the pull request.
-
-## Test case contribution
-
-Any test case would be welcomed. Currently, Serverless Devs function test cases are high priority.
-
-* For unit test, you need to create a test file named `xxxTest.java` in the test directory of the same module. Recommend you to use the junit5 UT framework
-
-* For integration test, you can put the integration test in the test directory or the Serverless Devs-test module. It is recommended to use the mockito test framework.
-
-## Package contribution
-
-For the development of Serverless Devs Package, please refer to the [development guide](https://github.com/Serverless-Devs/Serverless-Devs/discussions/62). After the development is completed, please refer [PR](https://github.com/Serverless-Devs/package-awesome) to the summary warehouse for more reference.
-
-## Engage to help anything
-
-We choose GitHub as the primary place for Serverless Devs to collaborate. So the latest updates of Serverless Devs are always here. Although contributions via PR is an explicit way to help, we still call for any other ways.
-
-* reply to other's issues if you could;
-* help solve other user's problems;
-* help review other's PR design;
-* help review other's codes in PR;
-* discuss about Serverless Devs to make things clearer;
-* advocate Serverless Devs technology beyond GitHub;
-* write blogs on Serverless Devs and so on.
-
-
-In a word, **ANY HELP IS CONTRIBUTION.**

package/CONTRIBUTORS.md

@@ -1,148 +0,0 @@
-# Serverless Devs Contributors
-
-> Thank you for your support and recognition of serverless devs. Serverless devs is committed to creating an active and open serverless developer ecosystem, providing more simple and easy-to-use serverless developer tools for more serverless developers.
-
-> If you also contributed to this project, but there is no your name below, please add your information at the end in order and submit [Pull Requests](https://github.com/Serverless-Devs/Serverless-Devs/pulls) to us
-
-<center>
-    <table>
-        <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/4457084?s=60&v=4" width="20%" style="min-width: 100px"><br>
-                <p>hanxie-crypto<br><a href="https://github.com/hanxie-crypto"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/46711?v=4" width="20%" style="min-width: 100px"><br>
-                <p>linux-china<br><a href="http://github.com/linux-china">Github</a> | <a href="http://rsocketbyexample.info">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/21079031?v=4" width="20%" style="min-width: 100px"><br>
-                <p>anycodes<br><a href="http://github.com/anycodes">Github</a> | <a href="http://faas.net.cn">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/56686088?v=4" width="20%" style="min-width: 100px"><br>
-                <p>wss-git<br><a href="https://github.com/wss-git">Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/31543505?v=4" width="20%" style="min-width: 100px"><br>
-                <p>hanyang-sh<br><a href="http://github.com/hanyang-sh">Github</a> | <a href="https://hanyang-sh.github.io/">Blog</a></p>
-            </td>
-        </tr>
-        <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/2697433?v=4" width="20%" style="min-width: 100px"><br>
-                <p>dengshenyu<br><a href="https://github.com/dengshenyu"> Github</a> | <a href="http://www.dengshenyu.com">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/52195264?v=4" width="20%" style="min-width: 100px"><br>
-                <p>git-qfzhang<br><a href="http://github.com/git-qfzhang">Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/5129967?v=4" width="20%" style="min-width: 100px"><br>
-                <p>heimanba<br><a href="https://avatars.githubusercontent.com/u/5129967?v=4">Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/10919599?v=4" width="20%" style="min-width: 100px"><br>
-                <p>rsonghuster<br><a href="https://github.com/rsonghuster">Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/5166366?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Tang Xianbin<br><a href="http://github.com/XianB">Github</a> | <a href="https://hanyang-sh.github.io/">Blog</a></p>
-            </td>
-        </tr>
-        <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/13564730?v=4" width="20%" style="min-width: 100px"><br>
-                <p>cong876<br><a href="https://github.com/cong876"> Github</a> | <a href="http://cong876.github.io/">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/43135116?v=4" width="20%" style="min-width: 100px"><br>
-                <p>gongjl88<br><a href="http://github.com/gongjl88">Github</a> | <a href="https://www.blog.loveapple.top"> Blog </a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/21334770?v=4" width="20%" style="min-width: 100px"><br>
-                <p>wangbow<br><a href="http://github.com/wangbow">Github</a> | <a href="https://juejin.im/user/58e8a667ac502e4957bcddbe">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/30379999?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Herbbbb<br><a href="https://github.com/Herbbbb">Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/62200750?v=4" width="20%" style="min-width: 100px"><br>
-                <p>janw<br><a href="http://github.com/jjangww">Github</a> | Blog</p>
-            </td>
-        </tr>
-        <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/48934955?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Ellison<br><a href="https://github.com/coco-super"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/23737468?v=4" width="20%" style="min-width: 100px"><br>
-                <p>黄沐<br><a href="https://github.com/huangfushan"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/84389274?v=4" width="20%" style="min-width: 100px"><br>
-                <p>siyuniuali<br><a href="https://github.com/siyuniuali"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/85347842?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Laura-monkey<br><a href="https://github.com/Laura-monkey"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/85340348?v=4" width="20%" style="min-width: 100px"><br>
-                <p>jingyan0705<br><a href="https://github.com/jingyan0705"> Github</a> | Blog</p>
-            </td>
-        </tr>
-         <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/16363180?v=4" width="20%" style="min-width: 100px"><br>
-                <p>邓超<br><a href="https://github.com/DevDengChao"> Github</a> | Blog</p>
-            </td>
-             <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/24624391?v=4" width="20%" style="min-width: 100px"><br>
-                <p>吴培泽<br><a href="https://github.com/wupz-repo"> Github</a> | <a href="https://wupeize.com">Blog</a></p>
-            </td>
-             <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/18051618?v=4" width="20%" style="min-width: 100px"><br>
-                <p>xiezht<br><a href="https://github.com/xiezht"> Github</a> | <a href="https://wupeize.com">Blog</a></p>
-            </td>
-             <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/10382462?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Bingqing Wang<br><a href="https://github.com/bingtsingw"> Github</a> | Blog </p>
-            </td>
-              <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/7664030?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Wang Gechao<br><a href="https://github.com/GotzeWong"> Github</a> | Blog </p>
-            </td>
-        </tr>
-        <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/6525544?v=4" width="20%" style="min-width: 100px"><br>
-                <p>金炳<br><a href="https://github.com/stone-jin"> Github</a> | <a href="https://www.fedfans.com">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/45506000?v=4" width="20%" style="min-width: 100px"><br>
-                <p>吹风机<br><a href="https://github.com/chuifengji"> Github</a> | <a href="https://ethan.nt-geek.club/">Blog</a></p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/626967?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Haoran Yang<br><a href="https://github.com/hryang"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/53770230?v=4" width="20%" style="min-width: 100px"><br>
-                <p>whaohan<br><a href="https://github.com/whaohan"> Github</a> | Blog</p>
-            </td>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/39087996?v=4" width="20%" style="min-width: 100px"><br>
-                <p>JasonLam<br><a href="https://github.com/JasonLamv-t"> Github</a> | <a href="http://jasonlam.cc/">Blog</a></p>
-            </td>
-        </tr>
-         <tr>
-            <td align="center" width="20%">
-                <img src="https://avatars.githubusercontent.com/u/23239892?v=4" width="20%" style="min-width: 100px"><br>
-                <p>Gao Zhiyuan<br><a href="https://github.com/alapha23"> Github</a> | Blog</p>
-             </td>
-        </tr>
-    </table>
-</center>

package/docs/readme.md

@@ -1,100 +0,0 @@
-<div align=center> <img src="https://images.devsapp.cn/devs-github/logo.jpg" width="100%"/> </div>
-<br>
-<p align="center">
-  <a href="https://www.npmjs.com/package/@serverless-devs/s">
-    <img src="https://img.shields.io/npm/v/@serverless-devs/s" alt="npm version">
-  </a>
-  <a href="https://www.npmjs.com/package/@serverless-devs/s">
-    <img src="https://img.shields.io/npm/dy/@serverless-devs/s" alt="npm download">
-  </a>
-  <a href="https://nodejs.org/en/">
-    <img src="https://img.shields.io/badge/node-%3E%3D%2010.8.0-brightgreen" alt="node.js version">
-  </a>
-  <a href="https://github.com/Serverless-Devs/Serverless-Devs/blob/master/LICENSE">
-    <img src="https://img.shields.io/badge/License-MIT-green" alt="license">
-  </a>
-  <a href="https://github.com/Serverless-Devs/Serverless-Devs/issues">
-    <img src="https://img.shields.io/github/issues/serverless-devs/serverless-devs" alt="issues">
-  </a>
-  <a href="https://github.com/Serverless-Devs/Serverless-Devs/discussions">
-    <img src="https://img.shields.io/github/discussions/serverless-devs/serverless-devs" alt="discussions">
-  </a>
-</p>
-
-<p align="center">
-  <span><b>Serverless 应用全生命周期管理工具</b></span><br>
-</p>
-
-**Serverless Devs** 是一个开源开放的 Serverless 开发者平台，致力于为开发者提供强大的工具链体系。通过该平台，开发者不仅可以一键体验多云 Serverless 产品，极速部署 Serverless 项目，还可以在 Serverless 应用全生命周期进行项目的管理，并且非常简单快速的将 Serverless Devs 与其他工具/平台进行结合，进一步提升研发、运维效能。
-
-![图片alt](https://serverless-article-picture.oss-cn-hangzhou.aliyuncs.com/1635319587379_20211027072627561648.png)
-
-> 更多关于 Serverless Devs 的介绍可以参考[项目介绍文档](./zh/readme.md)
-
-# 快速上手
-
-❶ 安装 Node.js(>=10.8.0) 与 NPM 包管理工具；   
-❷ 安装 Serverless Devs 开发者工具；   
-```shell script
-$ npm install @serverless-devs/s -g
-```
-❸ 在命令行中执行命令`s`，并按回车，开启你的 Serverless 之旅；   
-
-> 更多详细信息可以参考[Serverless Devs 安装文档](./zh/install.md)和[快速入门指南](./zh/quick_start.md)
-
-# 帮助文档
-
-- [安装文档](zh/install.md)
-- [命令行操作](zh/command/readme.md)
-- [Yaml规范](zh/yaml.md)
-- [CI/CD平台集成](zh/cicd.md)
-
-> 如果您想为 Serverless Devs 贡献 Package（包括组件和应用），您可以参考 [Package开发文档](zh/package_dev.md)  
-
-> Serverless Devs 天然支持 Yaml 模式与 Cli 模式，关于两者的区别和试用场景，可以参考文档[ **Yaml 模式 Cli 模式对比**](./zh/yaml_and_cli.md)；关于[**Exit Code 定义**](./zh/tool.md#exit-code-定义)、[**Yaml 文件优先级规范**](./zh/tool.md#yaml-文件优先级规范)、[**密钥使用顺序与规范**](./zh/tool.md#密钥使用顺序与规范)、[**通过环境变量设置密钥**](./zh/tool.md#通过环境变量设置密钥)更多关于项目设计的一些细节可以参考[**开发者工具设计文档**](./zh/tool.md) 
-
-# 相关资源
-
-目前 Serverless Devs 项目已经支持的 FaaS 平台/产品：
-
-- 阿里云函数计算（FC）: [项目仓库](https://github.com/devsapp/fc)
-- AWS Lambda: [项目仓库](https://github.com/devscomp/lambda)
-- 百度智能云函数计算（CFC）: [项目仓库](https://github.com/xinwuyun/cfc)
-- 华为云函数工作流（FG）: [项目仓库](https://github.com/xinwuyun/fg)
-- 腾讯云云函数（SCF）: [项目仓库](https://github.com/devscomp/scf)
-
-> 尽管以上 FaaS 平台/产品已经有人贡献或在持续维护中，但是我们仍然非常欢迎大家可以参与贡献/维护，除此之外，其他的 FaaS 平台/产品（例如 Google Cloud Platform Functions、Azure Functions等），我们也非常期望社区的小伙伴们可以参与开发和贡献。
-
-> 🚀 除此之外 Serverless Devs 项目还拥有很多优秀的组件和应用，可以参考[Awesome](./zh/awesome.md)
-
-# 项目期望
-
-- Serverless Devs 希望可以为 Serverless 开发者们提供一款可以无厂商锁定的，可以在 Serverless 应用全生命周期发挥作用的 Serverless 开发者工具；
-- Serverless Registry 希望可以为 Serverless 生态提供一套完整的包管理规范，与 Python 中的 pypi， Nodejs 中的 npm 等类似，将以此来开放和分享 Serverless Package，建设 Serverless 生态；
-- Serverless Developer Meetup 希望可以打造最符合 Serverless 开发者的社区活动，通过这个活动，我们希望更多人可以一起和我们交流、学习 Serverless 相关的产品；
-
-# 项目贡献
-
-我们非常希望您可以和我们一起贡献这个项目。贡献内容包括不限于代码的维护、应用/组件的贡献、文档的完善等，更多详情可以参考[ 🏆 贡献指南](../CONTRIBUTING.md)。
-
-与此同时，我们也非常感谢所有[ 👬 参与贡献的小伙伴](../CONTRIBUTORS.md)，为 Serverless Devs 项目贡献的努力和汗水。
-
-# 开源许可
-
-Serverless Devs 遵循 [MIT License](../LICENSE) 开源许可。
-
-位于`node_modules`和外部目录中的所有文件都是本软件使用的外部维护库，具有自己的许可证；我们建议您阅读它们，因为它们的条款可能与[MIT License](../LICENSE)的条款不同。
-
-# 交流社区
-
-<p align="center">
-
-| <img src="https://serverless-article-picture.oss-cn-hangzhou.aliyuncs.com/1635407298906_20211028074819117230.png" width="200px" > | <img src="https://serverless-article-picture.oss-cn-hangzhou.aliyuncs.com/1635407044136_20211028074404326599.png" width="200px" > | <img src="https://serverless-article-picture.oss-cn-hangzhou.aliyuncs.com/1635407252200_20211028074732517533.png" width="200px" > |
-|--- | --- | --- |
-| <center>关注微信公众号：`serverless`</center> | <center>联系微信小助手：`xiaojiangwh`</center> | <center>加入钉钉交流群：`33947367`</center> | 
-
-</p>
-
------------
-
-> Serverless Devs 开发者工具遵循 [Serverless Devs Model](../spec/readme.md)，更多模型/规范信息可以参考 [Serverless Registry Model](../spec/zh/0.0.1/serverless_registry_model/readme.md)，[Serverless User Model](../spec/zh/0.0.1/serverless_user_model/readme.md) 以及 [Serverless Package Model](../spec/zh/0.0.1/serverless_pacakge_model/readme.md)；

package/docs/zh/awesome.md

@@ -1,20 +0,0 @@
-# Awesome
-
-## 组件集合
-
-- [阿里云函数计算（FC）](https://github.com/devsapp/fc)
-- [阿里云Serverless应用引擎（FC）](https://github.com/devsapp/sae)
-- [AWS Lambda](https://github.com/devscomp/lambda)
-- [百度智能云函数计算（CFC）](https://github.com/xinwuyun/cfc)
-- [华为云函数工作流（FG）](https://github.com/xinwuyun/fg)
-- [腾讯云云函数（SCF）](https://github.com/devscomp/scf)
-
-## 应用集合
-
-- [阿里云相关应用合集](https://github.com/devsapp/awesome)
-- [AWS Lambda](https://github.com/devscomp/start-lambda)
-- [百度智能云函数计算（CFC）](https://github.com/xinwuyun/start-cfc)
-- [华为云函数工作流（FG）](https://github.com/xinwuyun/start-fg)
-- [腾讯云云函数（SCF）](https://github.com/devscomp/start-scf)
-
-> 如果您有相关的案例，欢迎您提PR到本文件。