VibeBuild-Off
Submit build
Ideas & Brainstorming

Community Build: Wave 1

Vibe Build-Off founder, illustrated Robot BuilderVibe Build-Off founderBuilder · joined Jul 29

Welcome to Wave 1.

For now, we’re not building anything yet. First we need to agree on how this should work without turning into chaos.

Introduce yourself and tell us:

1. What you’re strongest at
2. What kind of projects you’ve worked on
3. How much time you can realistically give
4. Whether you think the first pilot should use an existing working project or build something new

The first things we need to figure out are:

• How projects get reviewed
• How voting should work
• What roles we actually need
• How contributions should be tracked
• What rules should be agreed on before serious work starts

Once we get that straight, we can review the first projects and choose what to push.

#community-build#wave-1#planning
Helpful · 0Report
05

BUILDER RESPONSES

Keep the build moving.

Dave FOSTOGRAPHYoCOM, illustrated AI ExplorerDave FOSTOGRAPHYoCOMBuilder · joined Aug 5

I'm coming from a 25+years in the IT industry, I live in Australia so my time zone is different, like most of the world we use metric system.

As for the project (what ever that will be), my background was QA (quality assurance), test leads, some design, also system admin (but never really liked that role lol). Well that's the basics of me, also own business, used to be a photographer. Oh and a vibe coders like the rest of us haha

What you’re strongest at
2. What kind of projects you’ve worked on, sports apps, transport system with app hook, dabble in app game dev (none released yet).
3. How much time you can realistically give, 4-6hours a week.
4. Whether you think the first pilot should use an existing working project or build something new, start new as we can control the build from ground up.

How projects get reviewed
• How voting should work, since recruitment was done on fb why not make a group in msger, then questions can be posted and we get vote, put a deadline on votes (min 48 hours).
• What roles we actually need, project over veiw (I'd assume yourself), module leads report to you, quality assurance, testers, designers/ui/icons/buttons/images/styles&themes,coders of course, security, support, marketing, legal,accounting.
• How contributions should be tracked, I'm sure someone can make a project breakdown with milestones achieved showing the path to end goal?
• What rules should be agreed on before serious work starts, how to resolve conflicts, not just personal but of ideas, how to achieve outcomes, need backup of user roles so ppl have main role but can also have a backup role to take over or help out others if needed,

Vibe Build-Off founder, illustrated Robot BuilderVibe Build-Off founderBuilder · joined Jul 29

I like this. Especially the part about having a main role and a backup role because people are going to get busy and we can’t have everything stop because one person disappears.

Can you take a shot at laying out what you think the first team structure should look like? Like the main roles, who reports to who, and maybe a simple voting setup.

Post it here and let everybody pick it apart lol. That’ll give us something real to work from instead of everybody throwing random ideas around

Dave FOSTOGRAPHYoCOM, illustrated AI ExplorerDave FOSTOGRAPHYoCOMBuilder · joined Aug 5

what I have for this is to large to post in this comment field, can you setup a repository for documents, pdf,asset?

Austin Woodall, illustrated Mad ScientistAustin WoodallFounding Builder #2 · joined Aug 7

This seems like an obvious use case for web3/blockchain/DeFi. There are many governance structures and tokenomics structures that can be used to decide and enforce who decides what and who gets paid what. There should be a board of directors elected by the community, but the goal should be to allow 1000s of active code contributors and asset designers.

What I like building is custom tools that do not require AI once built.

Vibe Build-Off founder, illustrated Robot BuilderVibe Build-Off founderBuilder · joined Jul 29

Interesting tbh, this is the part I really want you to dig into.

I don’t want us jumping into crypto just because it sounds cool, but if Web3 can actually solve the contribution, voting and reward problem better than a normal system then I want to understand it.

Can you put together a simple version of how you see it working?

Like who votes, what gets tracked, how contributors earn credit, how leadership can be voted in or out, and where the blockchain actually comes into play.

Keep it simple enough that people who don’t know Web3 can understand it. Then we can compare it with a regular contribution ledger and let the group debate it.