Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Follow up on Tuesday call #154

Open
nembal opened this issue Jul 2, 2021 · 0 comments
Open

Follow up on Tuesday call #154

nembal opened this issue Jul 2, 2021 · 0 comments

Comments

@nembal
Copy link
Member

nembal commented Jul 2, 2021

Dear WG members,

Thank you for joining the call Tuesday.

I hope we were able to clarify some of the misunderstandings and helped to bring everyone up to speed regarding the logistics of voting, the proposed move, and IPR implications of the above. If there is an outstanding question, please do not hesitate to contact me.

  • we agreed that all of you are interested in keeping the community together
  • we discussed the importance and added value of a ratified specification for referenceable IPR protection and recognition towards future implementers, distinct from the prototype codebases that are driving the design process
  • we talked about the differences between a spec and code/implementation
  • we clarified decision-making mechanisms and the importance of the community, and the value of hearing everyone's voice

While I am not an active contributor to the work in KERI WG, in my role as DIF operations lead,I hope we can collaborate closely in the future and be fully transparent and solution-oriented about issues that might arise. What I can do, however, is to pledge to advance in good faith the following initiatives:

  • Work with the Steering Committee & JDF Legal team to implement the Contributor Agreement for individuals (to replace the current Feedback Agreement and provide better protection and better opportunities to our members) as soon as possible.
  • Make sure to hear every individual's case who considers contributing to KERI WG and collaborate with the group and the SC and do our best to enable the person to contribute while maintaining DIF's IPR processes. In the past, our policy was not to entertain additional attestations or affidavits in direct compliance with JDF’s blanket policy on the subject, but we are discussing ways to do so on a case-by-case with JDF counsel.
  • Support the WG to edit the current KIDs into a “beta version” of the specifications and sub-specifications mentioned in the charter work as soon as possible so that all contributors can refer their implementations to a ratified specification hosted in DIF, even if it is partial and only covers base layers of the prototype.
  • Support the WG to make transparent decisions regarding the next steps.

For those who missed the call (2,5 hours), you can find the recording here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant