...
- The contributor/author must have already submitted the OpenSocial Foundation's Contribution Licensing Agreement which licenses his/her contributions and indicates his/her intent to non-assert the final resultant specification. In the case of corporate contributions, the proper document is the OpenSocial Foundation's Corporate Contribution Licensing Agreement.
- The proposal must be listed on the "current proposals" page of wiki http://docs.opensocial.org and have a corresponding page on the wiki doc with the proposal details.
- For clarity, the subject line for the forum thread should clearly indicate the area of the specification impacted as well as the type of change being proposed.
- Areas of the specification: OpenSocial JavaScript, gadget JavaScript, gadget XSD, markup, templates, REST, etc.
- Types of changes: addition, clarification, breaking change
- NOTE: Given the issues associated with introducing breaking changes, any proposals that involve a breaking change to an API that existed in the prior version MUST indicate "Breaking Change" in the subject as well.
Panel A few examples:
- New Feature Proposal: OpenSocial Templates
- Clarification Proposal - gadget XSD - lifecycle events
- OpenSocial REST Proposal - alignment with Portable Contacts schema - Breaking Change
...