Solidify Digital Ocean Partnership
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 重构
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 领域
- cloud, devops, infrastructure
调研方向
The issue does not yet name repository files, tests, or migration entry points. Start by inventorying the 21 DigitalOcean droplets and the associated volumes, snapshots, and backups, then document the migration scope. Done should mean an agreed transition plan and a clear resolution for each listed resource.
由索引模型根据 Issue 内容生成。
描述
Got a very disappointing email yesterday:
We’re reaching out to share an important update regarding the DigitalOcean Open Source Credits Program.
DigitalOcean has decided to sunset the Open Source Credits Program. As part of this change, we are no longer accepting new credit applications or approving credit renewals, extensions, or additional credit requests.
If you currently have Open Source Credits that have already been granted, those credits will continue to be honored according to their existing terms and conditions. No action is required for your existing credit allocation.
Additionally, the dedicated inbox for the Open Source Credits Program will stop being monitored as part of this transition. For any further questions or assistance, please submit your inquiries through our standard support channel: https://www.digitalocean.com/company/contact/support
We appreciate your participation in the DigitalOcean Open Source Credits Program and the work you do to support the open source community. Thank you for being part of the program.
So, we're going to have to figure out what we need to do to transition off of the 21 Digital Ocean droplets we have.
Additionally there are some volumes, snapshots, and backups we'll need to address.
Opening this as a placeholder, I'll edit with more details.
UPDATE: Digital Ocean is going to help us work this out. See below: https://github.com/nodejs/build/issues/4499#issuecomment-5963981861
- 主要语言
- Jinja
- 星标
- 542
- 派生
- 184
- 平均合并
- 2 天 23 小时
- 30 天内合并 PR
- 11
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/build 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 2 天内回复
-
Windows/arm machines unavailable可能已有人在做 @StefanStojanovic 于 1 天前认领。 未关闭incident platform:windows
nodejs/build#4511 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 2 天内回复
-
难度 4/5 一周以上 新手友好度 5/100
维护者通常 2 天内回复
-
build-agenda
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 2 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
[Bug] The Aliyun cloud instance catalog silently truncates on a short page可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
apache/rocketmq-dashboard#6083 ·
维护者通常 4 天内回复
-
Bug Report: S3 device signs content-length on bodyless GET/HEAD, breaks R2 reads (403 SignatureDoesNotMatch)可能已有人在做 @ridhotamma 今天认领。 未关闭product / self-hosted product / storage
难度 2/5 1-3 小时 新手友好度 72/100
appwrite/appwrite#14326 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
awslabs/agentcore-samples#2180 ·
维护者通常 1 天内回复