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

Offboard Lenstra as a sponsor

Offen
#470 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@OliveCannon arbeitet bereits daran.

Seit 21.8.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

ISC OPS

Offboarding Lenstra, which is no longer a Sponsor of InnerSource Commons (Supporter tier, small company - the Jul 2026 - Jun 2027 renewal was declined/lapsed; the renewal outreach was abandoned and the renewal email bounced. See issue #120 for the abandoned renewal).

Follow the full process in the Offboarding a Sponsor checklist (reverse of the Add a new Sponsor template).

Confirm scope
  • Confirm with the Executive Director that Lenstra is no longer a Sponsor
  • Confirm the effective end date of sponsorship
  • Confirm whether Lenstra was a Partner or Supporter
  • Confirm whether any agreed announcements / newsletter placements / event mentions still need to be honoured
Update internal sponsor records
  • In the Sponsor Contact Details sheet, set status to Ended / Former Sponsor
  • Add end date and relevant notes (term completed / early exit / non-renewal)
  • Ensure no pending follow-ups or deliverables remain
Website (Sponsors page)
  • Archive the sponsor logo file locally if needed (do not delete without confirmation)
  • Open content/about/sponsors.md and remove Lenstra's entry from the correct section (Our Partners / Our Supporters)
  • Keep the list alphabetically ordered
  • Test locally to confirm the logo no longer appears
  • Create and merge a PR (coordinate with IT support if needed)
Sponsor slides (Community Calls & events)
  • Remove Lenstra's logo from Community Call opening slides, event decks, and recording templates
  • Confirm the updated slide is used from the next Community Call onward
Scheduled / recurring mentions
  • Check upcoming newsletters for pre-filled mentions
  • Check scheduled social media posts
  • Check recurring slide decks / templates
  • Remove or update references as needed
Communication with the former sponsor (ED handles external comms)
  • Draft a closing-style note (thank them, confirm offboarding complete, keep door open) using Sponsor Comms templates
  • Share the draft with the Executive Director to send
Public announcement (usually none)
  • Confirm with the ED whether any public communication is needed; if not, handle quietly via website/materials updates only
Final checks
  • Website updated
  • Sponsor slides updated
  • Internal records updated
  • Scheduled content reviewed
  • Sponsor notified (if applicable)
  • Executive Director informed the board that offboarding is complete
Vorherrschende Sprache
Keine Sprachdaten
Sterne
9
Forks
1
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

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 InnerSourceCommons/InnerSourceMarketing

Alle Issues in InnerSourceCommons/InnerSourceMarketing

Neue Issues direkt in Ihr Postfach

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