Move bnb/join to nodejs/join or nodejs/meet

檢視現有的 bnb/join repository，特別是 template/meetings.json 及其產生的 /docs 頁面，接著評估如何將其移轉至 nodejs/join 或 nodejs/meet 底下，或在那裡重新建立。確認 GitHub Pages URL、重新導向行為及選用的 CNAME 方案；當組織擁有一個持續維護的永久會議連結網站，且已設定的會議可供使用時，即視為完成。

I've gotten a bit tired of having to open up the GItHub issue for meetings just to access the join link, and I'd rather not fill up my bookmarks bar with random join links.

Inspired by a single page that @davidguttman made for the Mentorship meeting, I've built out bnb/join. I suppose could it be considered a tiny static site generator, but its purpose is to automatically build an index and individual redirect pages for every project defined in a JSON config file that can easily be deployed to GitHub Pages so we can have permalinks for each meeting.

Here's what the config looks like (and here's a link to the whole config):

    {
      "name": "Technical Steering Committee (TSC)",
      "filename": "tsc",
      "link": "https://zoom.us/j/611357642"
    },

And it builds (where nodejs is the GItHub org and join is the repo name):

• A page called tsc.html, published to /docs. When used in conjunction with GitHub pages this would be published to https://nodejs.github.io/join/tsc. That link would redirect to whatever the value of link is in the object.
• A list entry in the /docs/index.html file so if someone goes to https://nodejs.github.io/join they can launch from there.

You can see this at work right now:

• Any of the following links work:
  • https://bnb.github.io/join
  • https://bnb.github.io/join/commcomm
  • https://bnb.github.io/join/tsc
  • https://bnb.github.io/join/modules
  • https://bnb.github.io/join/website-redesign

For initial landing, this could simply be a repo in the org and we could use the nodejs.github.io/<repo> links. If we wanted to add something like meet.nodejs.org, meeting.nodejs.org/join, or join.nodejs.org we could very easily do that with a CNAME file/setting in the repo.

What problems does this solve? These are the ones that I see it solving:

• One permanent link, forever. We won't have to switch Zoom links in calendar entries, in meeting automation tooling templates, nor anywhere else. If the Zoom link needs to be updated, it's a simple PR. If we move off of Zoom to whatever the next cool meeting platform is, we can update the link through tooling. This also enables project members to get this work done themselves without needing to ask a Calendar maintainer to do it for them.
• Memorable links. The various options we have to implement this are all actually memorable, allowing us to lower the barrier to hopping on a call. It's a tiny improvement, but it's one I get caught on a lot. I'm generally a fan of reducing the burden on us as maintainers wherever possible 😊