Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Solidify Digital Ocean Partnership

Offen
  • Stimmt etwas nicht?
#4,499 25 Kommentare 19 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Refactoring
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Bereich
cloud, devops, infrastructure

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Jinja
Sterne
542
Forks
184
Ø Merge
2 T. 23 Std.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nodejs/build

Alle Issues in nodejs/build

Ähnliche Issues

Weitere Issues zu Cloud

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.