action #118882
openaction #154777: [saga][epic] Shareable os-autoinst and test distribution plugins
coordination #108527: [epic] os-autoinst wheels for scalable code reuse of helper functions and segmented test distributions
coordination #117673: [epic][tools] sporadic "Unable to clone Git repository" for wheels
Make available wheels more discoverable and share knowledge size:S
0%
Description
Motivation¶
During the workshop we were talking about existing plans to use and create more wheels. How do we know that a wheel provides a feature? Is there a plan for a new wheel? Can we avoid looking into the same idea by making it easy to discover wheel repositories on GitHub?
Acceptance criteria¶
- AC1: Available wheels can easily be discovered
Suggestions¶
- Come up with a convention to use a topic on GitHub, see jQuery for a nice example. This could be added to repos and automatically make them searchable.
- Mention the link in the openQA documentation where we document wheels (assuming we already document them)
- Add a note how one can make wheels show up on the same page
- Open a github issue for existing wheels repos to add the topic
Updated by livdywan over 1 year ago
- Copied from action #118633: Re-try on cloning of wheel repositories size:M added
Updated by szarate over 1 year ago
Do involve and take into account the intended audience and users for/of the plugin system, wheels or whatever you want to call it, otherwise you will end up with multiple approaches for the same problem, specially if nobody is curating the GH topic, or somebody decides not to use GH for their plugin.
Two other ideas are:
- Create a base repository to be used as a template, like obsidian-plugins where almost all plugins are actually a fork of the example provided by obsidian.
- Add a section in the openQA documentation about the plugins, and how to make use of them.
Updated by livdywan over 1 year ago
szarate wrote:
Do involve and take into account the intended audience and users for/of the plugin system, wheels or whatever you want to call it, otherwise you will end up with multiple approaches for the same problem, specially if nobody is curating the GH topic, or somebody decides not to use GH for their plugin.
Two other ideas are:
Updated by livdywan over 1 year ago
- Related to action #115001: Add documentation how to use/develop wheels visible on open.qa/docs added
Updated by livdywan over 1 year ago
- Related to coordination #117097: Evaluate GitHub template repositories for wheels added
Updated by tinita over 1 year ago
- Subject changed from Make available wheels more discoverable and share knowledge to Make available wheels more discoverable and share knowledge size:S
- Description updated (diff)
- Status changed from New to Workable