Get ready to share your plugins on the IF Explorer! #717
Replies: 5 comments 14 replies
-
Exciting stuff! Just wanted to confirm, is one plugin per repo preferred or mandatory? I can understand that the form is set up to deal with only one plugin but I wasn't sure if 4 differently named plugins from the same repo would be accepted via multiple form submissions. |
Beta Was this translation helpful? Give feedback.
-
Hey @jmcook1186 (+others), do you have any plans to make this site queryable via API? Asking because @josh-swerdlow and I are working on this VS Code extension for IF and it would be awesome if we had a robust way to list available IF plugins in a sidebar. |
Beta Was this translation helpful? Give feedback.
-
Hi folks, we've got a new Ui for the plugin submission - you can access it here: https://wiki.greensoftware.foundation/how-to-add-plugins The website will be going live soon, so get your plugins submitted asap if you want them to be included on launch day! |
Beta Was this translation helpful? Give feedback.
-
Hey @jmcook1186 @jawache I came across a potential security vulnerability on the plugins site while working on this vscode extension. May be unconcerning in the end but I'd like to be sure. Is there a better (i.e. less public) place to discuss futher? |
Beta Was this translation helpful? Give feedback.
-
Hi @jmcook1186 , I submitted https://github.com/moin-oss/datadog-importer to the IF Explorer last week and haven't seen this posted on the explorer or received any sort of update. What's the turnaround for having a submission posted, or receiving feedback on it? |
Beta Was this translation helpful? Give feedback.
-
Hi plugin builders!
🎉 We are aiming to launch our IF Explorer website by the end of the month! 🎉
This site will be used to share plugins so users can browse or search for your plugins to support their IF use-cases.
You can submit information about your plugin now so that they are listed on launch!
How to submit your plugin
Fill in this form!
Plugin submission form
You can suggest tags, or leave them blank. We might retroactively apply tags from a predefined list shortly before launch.
Providing the requested data will enable us to render a card presenting your plugin in the UI.
You can start gathering these data and/or submit the form now so your plugin is on the UI ready for launch!
Acceptance criteria
As long as you provide valid answers to the questions on the form, we don't see any obviously dishonest behaviour and your plugin seems to work then your plugin will get listed - we are only going to do the minimum of QC for now - but we will not hesitate to delist plugins if they turn out to be broken or somehow malicious.
We also intend to create some badges to highlight projects that have gone the extra mile in testing, documenting and/or providing citations to support their approach - more on that later.
It is really important to have detailed documentation in your README, an example manifest file that runs your plugin successfully, and unit tests.
Your plugin documentation should include the following information:
Plugin repo structure
Please submit the form once for each individual plugin - i.e. do not submit one form for a repo containing multiple plugins - split the plugins across multiple repositories.
We would much prefer each plugin to have its own repository and independent documentation. This means we can provide one card per plugin on the website and users will be able to find the plugin they are looking for more easily.
Hackathon plugins
There were lots of exciting plugins created during the recent hackathon.
Pinging some hackathon plugin builders below!!
@mgriffin-scottlogic
@szm100
@teto1992
@hoernschen
@dukeofjukes
@mgriffin-scottlogic
@jcendava
@moin-oss
@tianbiao
@Kiran-G1
@adamaucamp
@andreic94
@ramgsuri
@srini1978
@ktg9
@pazbardanl
@greenscale-nandesh
@jawache
Beta Was this translation helpful? Give feedback.
All reactions