EFI: Working with the ecosystem
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- node.js
调研方向
首先审查参与 Node.js Web 服务器框架组、CPC/OpenJS 和 WinterCG 的提案。明确如何协调 Express 代表、性能或下载指标以及生态系统沟通；当组织就这些职责和实施计划达成一致时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Motivation
Express (organization) is one if not the largest project part of the Node.js ecosystem. As such, we impact and can be impacted by the full ecosystem, from specific projects using us (like sails or nest.js) or projects that we use (like node.js)
By working with the ecosystem, providing feedback and being provided with feedback we can operate at a better efficiency
Expectation
Have some members of the Express Organization be part of key initiatives from other ecosystem
Implementation
Officialise some members to represent the Express Organization in the Node.js webserver framework group
Officialise some members to represent the Express Organization in the CPC / OpenJS
Officialise some members to represent the Express Organization in other groups (WinterCG for example...?)
Find a good way to share metrics that we can have, from specific builds (performance) or usage based on downloads
Communicate about the initiative, and express as a whole, and be relayed by the ecosystem
Status
Part: Organization
Draft
Express is - and has been - the main Node.js framework for the past decade, and even if REST APIs are still used (and are the norm), some changes happened in how we work around APIs, with new versions of HTTP, GraphQL, gRPC and other technologies like WebSocket.
To stay relevant, Express should be part of initiative like the Node.js web server framework
By having modules covering a vast range of use cases, the benchmarks of all packages can also be used to test regressions (or optimization) part of Node.js
- 主要语言
- 没有语言数据
- 星标
- 74
- 派生
- 26
- 平均合并
- 3 天 5 小时
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
expressjs/discussions 的其他 Issue
-
meeting
难度 1/5 1 小时以内 新手友好度 1/100
expressjs/discussions#534 ·
-
tc agenda top priority
难度 4/5 3-5 天 新手友好度 25/100
expressjs/discussions#533 ·
-
meeting
难度 1/5 1 小时以内 新手友好度 20/100
expressjs/discussions#532 ·
-
难度 5/5 一周以上 新手友好度 25/100
expressjs/discussions#522 · 6 条评论 · 1 个 reaction ·
-
discuss
难度 5/5 一周以上 新手友好度 25/100
expressjs/discussions#515 · 1 条评论 ·
查看 expressjs/discussions 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
JuliusBrussee/caveman#1449 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
GiganticMinecraft/seichi-playguide#183 ·
维护者通常 1 天内回复
-
devex good first issue
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
triage
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
good first issue laravel-appointment-reminders
难度 2/5 1-3 小时 新手友好度 92/100