Educational Materials

[0x4007]

We should develop educational materials that showcase the system’s features through multimedia elements such as photographs, videos, and a blog-style narrative.

These materials should be integrated into our marketing and sales strategies to effectively communicate the advantages of UbiquityOS.

Given the amount of features that we have, it might make sense to prioritize features that may be more "sexy" and stream out the content over time.

This first task can highlight our AI related features such as:

• talent recommendation
• issue deduplication
• conversation scoring

I also think that we should explain the core architecture of our system and how everything revolves around the concept of "tasks" with associated priority and time labels.

Each post should include images and possibly even a voice over video if it makes sense to.

These can be delivered on our notion at dao.ubq.fi

[minhyeong112]

I think the best way to educate others about the features is to show UbiquityOS in action. Are there any particularly smooth issues (that show many of the awesome features) or shall I look for some?

[0x4007]

particularly smooth issues

Some old ones i have saved for pitching

ubiquity-os-marketplace/command-start-stop#64 (comment)

ubiquity/ubiquity-dollar#611 (comment)

[0x4007]

This is a very rough draft. Normally I would pass it through an LLM to rewrite but I'm in a bit of a transit/rush.

UbiquityOS Overview

Test

UbiquityOS Capabilities

/help

• you can configure your own instance of UbiquityOS with plugins from our marketplace.
• the help menu wil provide you information on the currently configured commands. Eventually it will also provide an overview of all the plugins configured which handle other automations and which may not have direct commands to invoke those tools.
• organization wide defaults with local project overrides is supported.

/wallet

• user wallet registration. this is essential for receiving rewards.
• rewards can be automatically transferred to contributors upon project completion, or offchain payment permits can be generated for later claims (gas claim fee is paid by the contributor)

/start

• this is used to self assign tasks.
• admins can configure the required criteria for the user to self assign tasks.
  • for example, by default only two tasks can be worked on concurrently by contributors in order to promote focus. however, it also accommodates exceptions like if there are delays in the review process, then the contributor can start on an extra task.
• given the collaborator's status (admin/team member/external/XP) task gating can also be configured.
  • for example, high priority tasks can only be worked on core team members, while external contributors can only work on the short and low priority tasks
• we are also doing research around seeing if the contributor has worked on similar type of work in the past and only then to allow self assignment.
  • for example, a user worked on a similar open source project six months prior. we check all of those project specifications and languages they used in order to determine whether they are likely to be a good candidate for the current task.
• this mitigates unqualified candidates from blocking tasks from more qualified ones.

/stop

• self unassignment. this is primarily used to formally give up a project without being punished via docking XP

assistive pricing

• the project specification author should set a course time estimate for any newly posted project in the form of a label prefixed with Time:
• project managers/administrators should set a priority level using a label prefixed with Priority:
• once both labels are set, a configurable lookup of pricing in the form of a label prefixed with Price: will be automatically set
• in the future we are saving all of the previously completed issue labels to help automatically determine pricing for new issues without contributors setting the priority and time label dependencies.

text-conversation-rewards

• UbiquityOS has the ability to compensate team members for their communications related to any project. If contributors are providing high value inputs, such as writing clear specifications, clear work reviews, adding any information or research to clarify the projects, or in general to help other team members complete the task successfully, they will be rewarded accordingly.
• we use AI to determine how relevant a comment is to the task at hand
• we also allow for manual configuration of rewards related to what types of comments they write, for example if they include images, links, and code snippets they would be rewarded more than plaintext comments.
• This incentivizes high quality and productive communications around the DAO in the context of completing tasks.

/query

• this is used to query the stats of any particular contributor. currently this is primarily used to display their registered wallet.
• in the future we will display other metrics like their "XP", total earnings, repository permissions and more.

disqualifier

• in a DAO with many concurrent projects being handled, sometimes its difficult to stay on top of everything. frequently DAO contributors will start on a project, removing it from the open tasks list for others to work on, only to not proceed to do any work on it. This blocks progress and its important to monitor project status.
• disqualifier observes every project for activity in the form of commits and comments from the assignee. if they stop working on the project, UbiquityOS will inquire for an update. If the assignee continues to do nothing, they will be unassigned and disqualified from self assigning on the task again.
• in the future this will dock the assignees XP or DAO reputation

/ask

• This is used to ask context aware questions. UbiquityOS reads the linked and other similar content from any conversation within your organization, and then answers accordingly. For example, if the user is on a pull request, we pass in the full pull request conversation, its review, the diff, the linked issue, and any other linked contents we can find from the conversation.
• This is much faster than pasting in all of the relevant content manually to an LLM

assistive merging

• advanced configuration to set criteria to automatically merge a pull request. by default this will automatically merge approved pulls after a week.

vector-embeddings

• Imagine a super manager that remembers everything inputted into your company: for example every comment, message, meeting, and work deliverable. UbiquityOS then has various applications of this super memory:

issue deduplication

• when contributors create new project proposals, UbiquityOS has the ability to immediately identify similar proposals in the past and which are ongoing and annotate similar parts of the new proposal to indicate their existences. If in general the new proposals are too similar to ongoing ones, they will be automatically closed out and rejected.

task matchmaking

• UbiquityOS has the ability to understand every project that any contributor has ever worked on. When new projects are created, the system will recommend, in order, of who is best qualified for working on the task. It will also link the previous projects entire work contexts (specification, conversation, work deliverable and work review) for team members to check before reaching out to the contributor.

/annotate

• automatically annotate any github comment with footnotes/links to related projects or comments. this is useful to reference other related discussions without having to manually search for them.
• For example, if a project is being discussed by two team members, and they want to review a similar discussion from a previous project, UbiquityOS can immediately recall the original conversation for review. This helps to speed up research and debates as all of the organization's related debates and their conclusions can be summoned, with their full conversation context, on demand.

telegram bridge

• this provides an integration with UbiquityOS to telegram. When a new project is started, UbiquityOS will create a dedicated chatroom and post it under the GitHub issue.
• in the future this will allow rewards to be generated for contributor activities that occur within Telegram in association with the project being completed.

[minhyeong112]

ok great! I'm also bouncing around all day, but can get this done in the timeframe
will take this draft, search for some additional examples, and mix it all into the tg outreach campaign

[minhyeong112]

/start

[gentlementlegen]

@minhyeong112 Sorry today GitHub servers are experiencing quite some problems, looking into it.

[minhyeong112]

/start

[minhyeong112]

@minhyeong112 Sorry today GitHub servers are experiencing quite some problems, looking into it.

no worries! just tried again for fun

@0x4007 what do you think?
UniquityOS OnePager

[0x4007]

Traveling again today so did a quick pass while drinking a morning coffee.

1. Used ChatGPT to rewrite
2. Populated in our Google Doc template

https://docs.google.com/document/d/1jWJiW6yMNDoDN5fU6K5GmPIPfn58qYJ_DkJDSHTQfJY/edit?tab=t.0#heading=h.n1oftyayfp1t

[gentlementlegen]

/start

[ubiquity-os]

! You do not have the adequate role to start this task (your role is: member). Allowed roles are: collaborator, admin.

[gentlementlegen]

@minhyeong112 no problem but obviously it is supposed to work, I am trying to monitor this repo closely to see when it doesn't. Don't hesitate to notify me when something goes wrong!

[minhyeong112]

Updated docs:
UbiquityOS in 1 Minute
UbiquityOS in 10 Minutes

Over to our designer/GreatLeader @0x4007 for approval~
Will integrate these links into the copy as well!

[0x4007]

Made some adjustments to the 1 Minute doc.

I was also thinking about the classic advice of "don't sell features, sell a feeling"

Maybe we should have imagery of managers lounging in beachside chairs and emphasizing how much extra time they will have if they use UbiquityOS etc.

Check out those toes.

Maybe we can also write more content around "selling the feeling" instead of the features?

[minhyeong112]

/start

[ubiquity-os]

! You do not have the adequate role to start this task (your role is: member). Allowed roles are: collaborator, admin.

[minhyeong112]

ahh I think I have the wrong permissions here~

anyway, docs have been updated! over to you for approval @0x4007

links copied here for convenience:
UbiquityOS in 1 Minute
UbiquityOS in 10 Minutes

[gentlementlegen]

@minhyeong112 Sorry this should most likely be fixed once ubiquity-os-marketplace/command-start-stop#119 is merged, because you have elevated rights in this repository.

[0x4007]

One minute document is nice but longer than a one minute read! I like the start with Chad. Maybe we can add another paragraph or so to add to the tone and feeling?

But also reviewing the spec I wonder if it makes sense to expand on those specific features in separate blog posts?

Perhaps writing with a focus on the feeling and then add credibility by lightly touching on the technical details of those features?

[minhyeong112]

/start

[minhyeong112]

• 1-min (now 3-min) doc has been updated (title, caption, formatting)! over to you for approval @0x4007

• could you elaborate on what you're looking for for the separate blog posts? maybe the "3 min" doc stays as-is and then we chop up the existing "10 min" doc into blog articles that each focus on 1 feature? if so, I'm not sure what exact content to include in each blog post (how the need for the feature was discovered iteratively as Ubiquity discovered the use-case internally? a technical description of the codebase for each feature?) without more details of what you're looking for, I would recommend keeping the formats of the 2 educational documents (short and long) but updating the content as you see fit, but standing by for more guidance!

links copied here for convenience:
UbiquityOS in 3 Minutes
UbiquityOS in 10 Minutes

• by the way, can I mix UbiquityOS commands like 'slash start' and other comments? curious if I needed to separate the above message or not.

[ubiquity-os]

Passed the disqualification threshold and no activity is detected, removing assignees: @minhyeong112.

[ubiquity-os]

Important

• Reminders will be sent every 1 day and 18 hours if there is no activity.
• Assignees will be disqualified after 3 days and 12 hours of inactivity.

[minhyeong112]

@0x4007 following up on my last message, when you have a moment~

[ubiquity-os]

Passed the disqualification threshold and no activity is detected, removing assignees: @minhyeong112.

[ubiquity-os]

Important

• Reminders will be sent every 1 day and 18 hours if there is no activity.
• Assignees will be disqualified after 3 days and 12 hours of inactivity.

[ubiquity-os]

Passed the disqualification threshold and no activity is detected, removing assignees: @minhyeong112.

[0x4007]

I sent you some feedback to discuss in DM but haven't heard back.