-
Notifications
You must be signed in to change notification settings - Fork 2
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
Clarify contribution guidelines #30
Comments
One other thing that I think we'll need to do is to standardize the contribution policies across Privacy Sandbox repos - each of the BA, KV, and data-plane-shared repos have slightly different language about this right now and it's confusing. I don't think that's deliberate, it's more that we haven't needed to figure this out until now and this is a good reason to prioritize doing that work. |
There're a few related things that I think we should figure out (and which I'll put on the agenda for the next WICG call):
|
Just so that I don't forget: we talked about design review processes in the call on the 17th January. I'm going to follow up and do some research on how other Open Source projects handle doing design reviews (including privacy and security evaluations) in public and then come back to the group to see whether there's a process that we can borrow and customize. |
As some background, this is how the Chromium Open Source project handles public design reviews:
|
The contribution guidelines in the B&A repo currently state that the project is not accepting contributions. At least from the Azure side, we would like to start contributing to add support for deployments in Azure. And I am sure there are other looking to contribute too.
The text was updated successfully, but these errors were encountered: