-
Notifications
You must be signed in to change notification settings - Fork 174
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
Providing free Vercel hosting services to interested OpenJSF projects #1022
Comments
cc @leerob so you can keep track of the conversation here :) |
Congrats on the new site being merged! Are we still on track here? How can I help? |
Hey, @leerob, pretty we're going to meet with the team once again, but not sure how we can proceed without Robin for now. Let me check with the team if there's anything we can do for now, otherwise, we need to wait for Robin. |
This issue title is a bit confusing; you're talking about using vercel for node's website, right? |
@ljharb, afaik, we were discussing something where OpenJS would partner with Vercel so that any member project could use Vercel. |
ahhh gotcha, thanks for clarifying. |
Sure :) |
Can I suggest reframing this (in the title) as something along the lines of "Providing free Vercel hosting services to interested OpenJSF projects?" The current issue title sounds very prescriptive (i.e. suggesting that projects would need to move away from their current solution to using Vercel). Of course this is not the case, but it's not clear from the topic. |
@tobie, I think there's confusion here. This issue concerns the process of OpenJS closing a partnership with Vercel rather than projects needing to adopt Vercel. I believe the title fits its description. Otherwise, it would be written as "Proceed with the adoption of Vercel for the OpenJS Foundation member projects"... But if it was confusing enough for you, let me rephrase it to your suggestion :) (English is not my native language, so I honestly didn't see anything wrong with the current title) |
Everything went well (and we have a Vercel account now and access to resources), but @bensternthal, should we document how member projects might request access to our Vercel account? Should this be part of the Infrastructure Menu? |
Looks like we aren't quite ready to roll out Vercel broadly. We will wait until after the launches of OpenJS and Node on their platform. |
That makes sense! |
What's the status, here? Can we close this issue or spell our next steps? |
Afaik the issue should be closed. We already formed our partnership with Vercel. |
As discussed in previous meetings within the Cross Project Council, we are considering a partnership with Vercel to allow us to use their services.
The talks so far have succeeded, and I'm happy to inform you that the Node.js TSC had no objections to the usage of Vercel for future projects, such as the Website (nodejs.org) transition to their platform and other side-projects, such as downloads CDN on their side, PR previews for the Node.js API docs, and others.
I'm creating this issue as we're having talks internally within the CPC, and a subset of people, that are helping with the coordination of the implementation of Vercel (What the partnership would be about, what we would get, what Vercel possibly want out of us, who would should the credentials, and all other sorts of topics).
The current team handling the partnership
Current Task-list
The text was updated successfully, but these errors were encountered: