Stream: cds hooks/github
Topic: docs / Issue #336 May 2018 Ballot Comment 130
Github Notifications (May 16 2018 at 23:03):
cds-hooks-bot opened Issue #336
## May 2018 Ballot Comment 130
Submitted by @kensaku-kawamoto on behalf of @gdelfiol from University of Utah
Chapter:
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Comment:
What is the process to review/approve new hooks? Lack of a process can lead to multiple versions of the same hook, compromising interoperability## :de: Köln May 2018 Working Group Vote
@brynrhodes moved the following disposition, seconded by @jmandel.
Disposition: Persuasive with Mod
Disposition Comment:
We agree that such a process needs to be defined; however, this is outside of the spec. We will work on defining this process.We do need to update the hooks.md page (which we will move into the 1.0.md specification file) to update the link to point to the correct location of submitting proposed hooks.
Update line to "We encourage implementers to add new proposed hooks" (or something similar).
:+1: For: 20
:expressionless: Abstain: 2
:-1: Against: 0:tada: The motion passed! :tada:
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 16 2018 at 23:03):
cds-hooks-bot milestoned Issue #336
Github Notifications (May 16 2018 at 23:03):
cds-hooks-bot labeled Issue #336
Github Notifications (May 16 2018 at 23:03):
cds-hooks-bot edited Issue #336
## May 2018 Ballot Comment 130
Submitted by @kensaku-kawamoto on behalf of @gdelfiol from University of Utah
Chapter:
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Comment:
What is the process to review/approve new hooks? Lack of a process can lead to multiple versions of the same hook, compromising interoperability## :de: Köln May 2018 Working Group Vote
@brynrhodes moved the following disposition, seconded by @jmandel.
Disposition: Persuasive with Mod
Disposition Comment:
We agree that such a process needs to be defined; however, this is outside of the spec. We will work on defining this process.We do need to update the hooks.md page (which we will move into the 1.0.md specification file) to update the link to point to the correct location of submitting proposed hooks.
Update line to "We encourage implementers to add new proposed hooks" (or something similar).
:+1: For: 20
:expressionless: Abstain: 2
:-1: Against: 0:tada: The motion passed! :tada:
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (Jun 14 2018 at 13:44):
cds-hooks-bot assigned Issue #336
Github Notifications (Jul 30 2018 at 17:45):
isaacvetter labeled Issue #336
Github Notifications (Aug 06 2018 at 22:06):
isaacvetter commented on Issue #336
See proposed hook maturity model in #195.
Github Notifications (Nov 20 2018 at 20:37):
isaacvetter commented on Issue #336
Resolved in PR #426. Closing.
Github Notifications (Nov 20 2018 at 20:37):
isaacvetter closed Issue #336
Last updated: Apr 12 2022 at 19:14 UTC