New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IF plugin registry form proposal #2
base: main
Are you sure you want to change the base?
Conversation
## Define, in your own words, what is(are) the Requirement(s) of your plugin | ||
<!--- I.E what is the basic functionality it must demonstrate. --> | ||
|
||
## Please provide citations, links and references that support the validity of the implementation of your plugin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's actually deal with this by suggesting best practises in the registry docs instead of requiring it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we wanted to have this (and other answers) in this form so that:
- Other ppl in the community can review any registered plugin at any time (transparency)
- We can later review and revisit when we start randomly auditing plugins.
I don't mind citations, links and references being kept somewhere else, but I do think there should be only 1 place for all basic info for each register plugin. WDYT?
## Please provide citations, links and references that support the validity of the implementation of your plugin | ||
<!--- I.E provide reference to sources explaining how this implementation meets the requirement described above. --> | ||
|
||
## Please describe the test cases covered by your plugin's dedicated unit tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Please describe the test cases covered by your plugin's dedicated unit tests |
Again, let's handle this elsewhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
again, I don't mind. just think we need 1 place where all info (that is - the answers to the questions in this form) for all registered plugins reside in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi - left some suggestions. Thinking on this some more, it's best to keep this minimal and have the more detailed guidance coming in the submission guideline docs.
c7a2403
to
f1fb61a
Compare
…istering an IF plugin to the registry website Signed-off-by: Paz Barda <paz.barda@intel.com>
f1fb61a
to
799501b
Compare
Made most of the changes requested, please see my comments on last 2. thanks. |
approving this but also flagging that the website team decided to move this form to a Notion NoteForm form that can auto-populate a db for the website to pull from |
Proposing an issue template for registering an IF plugin to the registry website