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

Community and why we need to improve #156

Open
1 task
Keyrxng opened this issue Feb 12, 2025 · 4 comments
Open
1 task

Community and why we need to improve #156

Keyrxng opened this issue Feb 12, 2025 · 4 comments

Comments

@Keyrxng
Copy link

Keyrxng commented Feb 12, 2025

Time Estimate

  • I have added a time estimate label

Background Information

Leveraging Community for Growth

Case Study: ElizaOS (formerly AI16Z)

Web3 startups thrive on strong community engagement, a key driver of growth. ElizaOS exemplifies this by effectively leveraging community dynamics, something UbiquityOS has yet to fully capitalize on. Despite having a competitive tech stack, our exposure remains limited.

ElizaOS benefits from:

  • A robust AI agent framework that attracts developers.
  • An engaging and interactive Discord community that fosters connections, collaboration, and organic growth.
  • A culture where employers scout contributors via commit history or scanning their contributor leaderboards, leading to job opportunities.

In contrast, UbiquityOS lacks an equally vibrant community. While our model includes financial incentives, a sense of belonging and engagement could significantly boost retention and participation.

The Value of Community in Web3

A highly active and welcoming community is critical for long-term success. Web3 projects have proven that fostering interactivity, meme culture, and casual networking contributes to:

  • Higher retention rates among contributors.
  • Greater organic exposure and word-of-mouth marketing.
  • A collaborative environment where members help each other, enhancing project development.

While UbiquityOS offers paid tasks, ElizaOS and similar projects implement a retroactive airdrop system, rewarding past contributions. A similar approach to our intended airdrop—alongside building a strong community—could enhance loyalty and participation.

UbiquityOS as an Agency Model

Although UbiquityOS is technically a B2B startup, our operational model aligns more with an agency, relying on a loyal pool of contributors. Financial incentives alone may not ensure long-term engagement, especially given competition from external recruiters and job offers.

A vibrant community can:

  • Increase contributor retention through a fun and interactive environment.
  • Offer additional value beyond financial compensation (networking, collaboration, learning opportunities).
  • Ensure a steady pipeline of developers to handle an increasing workload as partnerships grow.
  • Help prevent contributors from just using their time/experience at UbiquityOS as a springboard into bigger opportunities, thereby reducing attrition and increasing retention.

Strategic Implementation: Discord as a Community Hub

Currently, UbiquityOS prioritizes "signal over noise," maintaining a formal and minimal engagement Telegram. This approach serves business needs but fails to foster a developer-friendly atmosphere.

To bridge this gap, I'm proposing we establish Discord as the primary community platform. Key benefits:

  • A structured environment for discussions, support, and networking.
  • Bot moderation to maintain quality while ensuring engagement.
  • A scalable solution to accommodate future growth and evolving needs.

Social Media Integration

In parallel with Discord, expanding our presence on Reddit, X (Twitter), and other social platforms can further boost community-driven growth. However, this requires a dedicated strategy separate from Discord’s community-building role.

Conclusion

By embracing a community-first approach, UbiquityOS can:

  • Enhance contributor retention and engagement.
  • Build a reputation as a collaborative and engaging platform.
  • Ensure a sustainable pipeline of skilled developers to meet growing demand.

Investing in community-building, starting with Discord, is a low-cost yet high-impact strategy to drive long-term success.

Completion Criteria

I can create completion criteria or someone else can depending on how this proposal is received.

Relevant Links

No response

@0x4007
Copy link
Member

0x4007 commented Feb 12, 2025

Thanks for the proposal. I'm on board with building a social discord but can you detail all of the steps to properly set up a community discord? I imagine there are bots and configs and whatnot. I ask to set an accurate time estimate

@Keyrxng
Copy link
Author

Keyrxng commented Feb 12, 2025

  • I don't have direct experience with this, but I've observed how some startups and their Discord communities operate.

  • Fundamentally, it's about creating a collection of "topics" or rooms, similar to Telegram, but with a stronger focus on community.

    • Channels for general discussions, memes, asking for help, and sharing projects.
    • A place for finding teammates to collaborate on tasks.
    • A chatbot-integrated room where it can interject in conversations.
    • Other channels based on what we think works well.
  • Additionally, we should have business-focused channels aimed at fostering a vibrant, engaging, and welcoming atmosphere.

  • Ideally, a community manager (or someone experienced in setting this up from the ground up) should handle this.

    • The key question:
      • Is this an internal task, or do we first need to bring in a community manager or leave this until one (someone) stumbles across it with experience?
    • Internally, we could do it, but it would involve trial and error and extensive research.
      • Research tasks are often separate from implementation, so this needs further discussion.

@0x4007
Copy link
Member

0x4007 commented Feb 12, 2025

We have an old discord which could be taken over but yes this would definitely require somebody to take the helm and I don't think anybody in house is suited for it.

Personally I despise Discord. I think it's a bad product. But I understand that it's popular so that's why I'm open to this. I definitely don't want to be managing it.

We could model ours off of the Cline discord

@Keyrxng
Copy link
Author

Keyrxng commented Feb 12, 2025

Yeah I don't think anyone has adequate knowledge but I'm sure there is one or two that would be willing to undertake such a responsibility initially or indefinitely. Likely best to do a bit of outreach and bring someone in for it if this task holds any weight and they can spec it and it'll be their first task etc.

  1. Manual outreach: via going into discords and asking to speak with the moderators etc would be effective and likely the quickest route to getting this task actively worked on.
  2. Programmatic outreach: I've seen some of the outreach stuff going on but doubt that would be of any use here although I'm not 100%.
  3. Official/Freelance Job Posting: web3.careers/fiverr or some other job board would draw a lot in although then you are weighing people up etc so idk what's best for the business in that sense regarding personnel and hiring.

We could model ours off of the Cline discord

As good a start as any I guess.

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

2 participants