-
Notifications
You must be signed in to change notification settings - Fork 54
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
Update billing info for ampproject GitHub org to point to OpenJSF #59
Comments
Hi @mrjoro, yep, this is pretty straightforward. Can you please make me an owner and temporarily set those to me? I'll get them set properly. |
Done! A related question--we are shifting to using GitHub Actions for testing, and there will be a cost of about $40k/year for this. Before the move to OpenJSF we'd talked about how we would handle things like this in the abstract, but now that it's actually happened I'm not sure what the process is to get approval for this expense and to make sure it's properly funded. Can you provide guidance on this? /cc @rsimha and @ampproject/wg-infra as FYI |
Nice |
@brianwarner friendly ping on whether we've resolved how to handle expenses like this (the ~$40k for GitHub Actions). With the billing updated to point to OpenJSF charges like GitHub Actions would presumably be handled by OpenJSF, with Google able to direct funding for this if needed. |
@mrjoro thanks for the reminder. This past week and the coming week are a trainwreck, can we maybe connect over Slack and find a time to talk it through? |
Sorry, this one has slipped through the cracks... :) I did see that I was able to set a "Billing Manager" for ampproject, and I've sent an invite to @brianwarner for this role. I think that should give you enough rights to update whatever billing info should be updated? If not, let me know! |
Although ampproject is on the GitHub Free plan, there are billing settings that still point to Google.
We should update these, though I'm not sure what to set these to for OpenJSF. @brianwarner, @tobie or @jorydotcom do you know what this should be?
The text was updated successfully, but these errors were encountered: