Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

FYI - Node.js calendar lost - possibly gmail cleanup

Open
#923 25 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale

Research direction

Review the calendar-maintainers guidance at https://github.com/nodejs/admin#calendar-maintainers and compare it with the current shared-calendar access list. The issue reports that the calendar was restored and access details were still being worked out, so confirm with the maintainers whether any documentation update remains before starting.

Written by the indexing model from the issue text.

Description

The Node.js calendar and all entries disapeared over the weekend.

We are not sure why, possibly due to gmail cleanup.

Turns out we did not have the credentials for the user who had created the calendar anywhere I could find (build secrets, 1 password).

The foundation has now created a shared calender under their account and I've repopulated the calender entries. If I've missed any please let us know and I'll add them.

There may be a small tweak to https://github.com/nodejs/admin#calendar-maintainers in terms of how we manage access for those who can add/edit/delete entries but @bensternthal is still figuring that out.

I did take the opportunity to given @bensternthal a different list than was on the admin page to have access as it was quite out of date and had people I know no longer had access and was missing some who did. If I missed including you in the new list just let me know and we'll get that fixed up.

Dominant language
JavaScript
Stars
202
Forks
183
Avg merge
13d 12h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/admin

All issues in nodejs/admin

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.