Skip to content
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

Marketplace #6

Closed
rndquu opened this issue Sep 17, 2024 · 8 comments
Closed

Marketplace #6

rndquu opened this issue Sep 17, 2024 · 8 comments

Comments

@rndquu
Copy link
Member

rndquu commented Sep 17, 2024

Depends on #1

The ubiquity-os-plugin-installer repository is basically one of the core features of ubiquibot plugins marketplace. We can transform current repository in a plugin marketplace.

All plugins will reside in the https://github.com/ubiquity-os-marketplace organization:

What should be done:

  1. Create a new UI page that will:
    a) Fetch all available plugins from the https://github.com/ubiquity-os-marketplace organization
    b) Fetch plugins' manifests from the manifest.json file located in a plugin github repository (example)
    c) Display all available plugins
  2. Implement a caching mechanism (similar to the one in work.ubq.fi) so that target github users are not rate limited by github

In the end we should support this flow:

  1. User opens the marketplace UI
  2. User selects a plugin that he wants to install or edit
  3. User clicks the "Install" or "Edit" button and user's ubiquibot-os config is updated
@0x4007
Copy link
Member

0x4007 commented Sep 17, 2024

I feel like the more straightforward answer actually would be if we just have a dedicated organization and then we fork the plugins we want.

Or in our case for the "official" plug-ins we just transfer them to that organization.

So in conclusion our marketplace is a UI on top of a GitHub organization

@0x4007
Copy link
Member

0x4007 commented Sep 24, 2024

https://github.com/ubiquity-os-marketplace

@rndquu
Copy link
Member Author

rndquu commented Sep 24, 2024

https://github.com/ubiquity-os-marketplace

Updated description

@0x4007
Copy link
Member

0x4007 commented Sep 30, 2024

@gentlementlegen rfc on the manifest stuff. Anything else we need to prepare?

@gentlementlegen
Copy link
Member

gentlementlegen commented Sep 30, 2024

No, but ubiquity-os/ubiquity-os-kernel#80 should be merged for the User clicks the "Install" or "Edit" button and user's ubiquibot-os config is updated so it can be validated and the proper values exposed. I am confident there are tools to transform JSON 7 to html forms out there.

@0x4007
Copy link
Member

0x4007 commented Oct 5, 2024

My https://github.com/0x4007/sync-configs-agent.git can already generate accurate configs because it has the ability to parse the plugin URLs and read their manifests. We just need to feed it the repository URLs and a preference of what to add and how to configure them in plain English.

Expensive approach with Claude 3.5 Sonnet but it works quite well.

I think it can certainly be the backbone of natural language to bot config in several contexts, including, but not limited to a future plugin that will allow users to adjust their UbiquityOS settings as simply as:

@UbiquityOS change the follow up times to 1 day from 3.5 days.

In the background this script can run and link back to the comment thread for review/debugging.

@Keyrxng
Copy link
Member

Keyrxng commented Nov 9, 2024

#13 meets the requirements of this spec

  1. Fetches marketplace plugins and official URLs then displays all via dropdown to install
  2. Cache system implemented for both manifests and worker/action urls.
  3. Suggested flow is currently implemented (requires input on UI design and config option display but business logic is implemented)

@rndquu
Copy link
Member Author

rndquu commented Nov 15, 2024

Closing in favor of #3

@rndquu rndquu closed this as not planned Won't fix, can't repro, duplicate, stale Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants