Creating a contingency plan around download issues

[ZibbyKeaton]

Hey All -

I know we are doing a lot of work in ensuring that we don't have any downtime with Node.js, but I thought if something did happen, we might want to create a mini-contingency plan to help communicate issues out to the community, so they are aware of the issues and how to track the status of issues to resolution.

What does this group think? I can pull something together around this and share it with y'all. I would just ask that you let me know what we have in place currently to ensure zero downtime, so I can start drafting the language correctly.

Zibby

[mscdex]

Is this about nodejs.org? If so, it might be better to submit the issue here?

[Trott]

Is this about nodejs.org? If so, it might be better to submit the issue here instead.

There is this issue already in the build repo as well: nodejs/build#676

[ZibbyKeaton]

Thank you @Trott I will propose what I was thinking about in here.

[Trott]

(Just in case I was unclear: I'm not expressing an opinion as to the "right" or "best" place for the conversation. Just pointing out the conversation that's already happening in case it has useful context or joining it is preferable to starting a different conversation. Do whatever you think makes sense.)

[tniessen]

@ZibbyKeaton If I understand correctly, your goal is to create a strategy for communication in case of an unexpected downtime of the node.js website. Technically, this is not what nodejs/build#676 is about (which is about a strategy to avoid downtime). However, I am closing this issue as it has not made any progress and is not relevant to the node.js core. Maybe nodejs/nodejs.org is a better place to discuss PR work related to the website. Feel free to reopen if you think it is relevant to the node core 😃

[Trott]

Website, evangelism, and commcomm all seem like an imperfect-but-plausible fit for this conversation. For that matter CTC and/or TSC repo might be appropriate too.
¯\(ツ)/¯