Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Create an infrastructure file #324

Open
bjohansebas opened this issue Jan 17, 2025 · 9 comments
Open

Proposal: Create an infrastructure file #324

bjohansebas opened this issue Jan 17, 2025 · 9 comments
Labels
discuss meeting top priority Issues which the TC deem our current highest priorities for the project

Comments

@bjohansebas
Copy link
Member

It would be very useful to document in detail which resources Express is using and who is providing them. This would not only ensure greater transparency in resource management but also be extremely helpful for future maintainers of the project. Having a clear record would allow them to easily understand the current infrastructure.

For example:

@wesleytodd
Copy link
Member

I like this idea alot! I think it would live in this repo under ./docs. There are a bunch of things I can add.

@bjohansebas bjohansebas added meeting top priority Issues which the TC deem our current highest priorities for the project labels Jan 20, 2025
@UlisesGascon
Copy link
Member

Oh yeah! Great idea and very related to #244 cc: @vvalderrv

@jonchurch
Copy link
Member

We've got netlify deploy previews on the website, under an account I own right now.

@bjohansebas
Copy link
Member Author

Is there an Algolia account, or did they just give us the API keys for the search to work?

@wesleytodd
Copy link
Member

Is there an Algolia account, or did they just give us the API keys for the search to work?

I believe they did the integration work and gave an api key.

Things I know of:

  1. We have a CloudFlare account. We need to finish transferring things over to it.
  2. The DNS for the website is managed by the LFX
  3. We have have an assortment of email lists and meetings also managed by the LFX
  4. A coveralls account (not sure who owns that, but not sure if we care to keep it either)
  5. A travis ci account, also not sure who owns that or if we want to keep it
  6. An Open Collective (the TC members should all be added on that)
  7. I applied for two OSS accounts this week: Digital Ocean & DataDog (both are things I am hoping we can use for the Perf WG)

I will continue to think on it in case I forgot something, but I believe this is all of it.

@bjohansebas
Copy link
Member Author

We should add social media, right? It's part of the project.

@wesleytodd
Copy link
Member

Ah right! I have both a twitter and a bluesky. Thanks, forgot about those. That topic brings me to one we should also have: a password manager. There are some platforms that allow account sharing but not all, and for those we would either need to have one individual in charge or share the passwords. I don't want to open that conversation here really, as it is a large one, but it is one where I don't think we can easily just "add the TC onto it" like we can with the rest.

@wesleytodd
Copy link
Member

Oh! And this reminds me we also have the youtube.

@bjohansebas
Copy link
Member Author

Also all the organizations we have between GitHub and npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss meeting top priority Issues which the TC deem our current highest priorities for the project
Projects
None yet
Development

No branches or pull requests

4 participants