Skip to content

Latest commit

 

History

History
36 lines (22 loc) · 3.06 KB

github-donation.md

File metadata and controls

36 lines (22 loc) · 3.06 KB

Github Donation

Brand Guidelines Style Guide Working Group Lifecycle Work Item Lifecycle Github Donation Spec Tooling Guides Code of Conduct

1.) DIF accepts donations of “clean IPR” only, meaning original work done by member organizations. If a repository, work item or initial work group creation has accepted contributions from non-employees or has concerns regarding prior art, please reach out to working group chairs or DIF staff to discuss; CLAs may be required for any non-employee contributions. Furthermore, if you have any questions about code dependencies or their licensing, also reach out.

2.) Write to the chairs of the DIF group to which you are donating, and CC [email protected] -- email should contain:

  • the github organization that will be transferring a repo to DIF
  • the github handle that will be maintaining the item once it moves to DIF. (This person should have an employment or IPR relationship with a member of that group)
  • a realistic commitment to maintenance/issue triage and bring major issues to WG meetings when they arise
  • A simple one-sentence declaration that this is being donated by a working group member that was the sole contributor.

3.) Particularly if the work item has implications for other DIF work items or ratified specifications (i.e., relies on them, risks market/implementer confusion about dependencies), WG chairs may request changes, implementation guidance, explicit discussion of upstream specifications or dependencies, etc. In some cases, WG chairs may even propose conditions for acceptance analogous to the test vectors required at the WG approval stage of a DIF-native work item, which could include, for example:

  • participation in adjacent or upstream work items to research interoperability and edge-case issues
  • tracking alignment/interop issues with adjacent or upstream work items on a GH issue to ensure alignment over time
  • proven conformance with test suites of an upstream work item

4.) Schedule a time to effect the transfer with DIF staff. (requires Admin approval)

5.) “Transfer” the repository under repository settings, at the end of the general settings in the “Danger Zone”.

6.) Follow the instructions for transfer. The name of the GitHub organization is decentralized-identity

7.) On the “Team access” selection page, please select the team corresponding to the working group to which you are donating the repository and its IPR. The code maintainer listed in 2B should already be a member of that group. Access and other settings can only be set by group chairs, by default.

8.) Done. Your repo is transferred. Congrats, you are officially an open-source hero :)