| | 62 | **How to integrate all of this into the Developer community:** |
| | 63 | |
| | 64 | This would require a number of approaches and mechanisms, including: |
| | 65 | |
| | 66 | New functions: |
| | 67 | |
| | 68 | Creating a wp_setcookie(); function in PHP and a corresponding function in JavaScript that checks for consent before placing a cookie; |
| | 69 | Use of wp_setcookie(); can then be required for new plugin submissions to the WordPress.org repository. |
| | 70 | |
| | 71 | Updating existing functions: |
| | 72 | |
| | 73 | Updating other functions like wp_mail(); and the HTTP and REST APIs to check for the appropriate consent. |
| | 74 | In the case of wp_mail(); for example, this can be done by adding a new parameter variable for $consent_purpose. |
| | 75 | We can add a _doing_it_wrong(); if this variable is not present. |
| | 76 | In the case of the REST API, consent could possibly be integrated into a permission callback, but that is something we'd need Timothy's (and others) input on. |
| | 77 | |
| | 78 | Education drive: |
| | 79 | |
| | 80 | Voluntary compliance is preferred. By providing documentation, resources and discussing with as many stakeholders as we can (primarily on Slack), we can encourage adoption through education. |