Assigned to myself, we have a great foundation from our previous meetings.

key words: grinding and treasure-hunt

To assist in Rapid Application Development, I have downloaded RPGMaker MZ.
I'm not sure how to split our work up on this project anymore until we find a reliable way to async communicate.

Which would you prefer?

Storyline about the birds being erased?
Who is the enemy (ourselves?)?

1 or 2 sentences for each one of our platforms

ranking and evaluating each one.

why we chose Jira / github / discord?

I think the simplest way to give something for everyone is

1. Admins/Organizers can influence the settings of a deployed WOHW from our factory. They can access all flows.
2. Players/Hackers cannot influence the settings, but experience the true environment. They can also access the Sponsor/Normies flow.
3. Sponsor/Normies choose not to experience the environment, but can influence the future of this project with their power. They are presented a high level overview, interactive and rewarding treasure hunt through our assembled documents, and encouraged to try the tutorial or contact us.

Shouldn't we have a written statement of the rules for the game?

such as, each round of PvP requires you to work together with random strangers, complete an agreed mission, and then give honors to outstanding teammates (signifying their skills and building their profile).

What are the illegal actions, what we expect everyone to do etc

After the mini hackathon experience, should the organizers review the mini projects or should it be something done more for fun and learning?
@tippi-fifestarr

I've always wanted a teambird to work with me on this one, seems like a great technology and skill to have for an Owl and Support

https://www.youtube.com/watch?v=SF-XOwWIwRo
Learn how to use different cryptographic tools using ECDSA and ERC712 signatures, along with merkle-tree generation.

Workshop includes:

• ECDSA signatures generation and verification
• ERC712 signatures generation and verification
• Merkle-tree generation and usage
• ERC721 minting

Led by Hadrien Croubois - Smart Contract Engineer at OpenZeppelin.

instead of just 5 minutes of consensus and team name roles choosing (basically make a github repo and everybody makes an issue with their role or whatever), then 55 minutes of building whatever, then 5 minutes honoring and leaving comments

we also have different distributions of time, but I invented a new "mode"
the SyncSenses method, where a team takes turns reading out loud from brillant.org (or whatever) and collaboratively solving simple/fun warmup exercises.

my Ecuadorian teammate mentioned that he thought this was super helpful for his listening and understanding, and it clicked that maybe, just maybe, spending some time at first syncing ears to pronunciation via reading out loud could make later collaboration way more fluent (testable hypothesis: adding 10-15 minutes of sync and lowering the "building time" and see if the results are about equal)

I'd like to spend one pomodoro of time making a scavenger hunt through our assorted documents.

the plan would be:
0. set up access control to anyone can comment, but limited editing for us

1. structure it so there are two types of experience
   ---a: "scan through (this link) and find one sentence or phrase that you imagine (currentBirdName) would like, or press X for '(currentBirdName) does not like this document' = return false"
   --------i: optional: which bird do you think wrote this document, or is most represented in this document, or another way to say it is: which bird wrote most of this document?
   ---b: "here is a list of links to different documents in our scavenger hunt (maybe these are at x,y points on a MainMap), go find evidence of (currentBirdName)'s influence or mark the document as (!) missing proof that (currentBirdName) spent time on it."
2. this could fit the functional requirements for Phase 0.5 (be the entire tutorial minigames)
3. imply that using create issues and communicating on github should be a functional requirement for completing the tutorial and playing in PvP (mission 0 being reach team consensus on roles and project title as defined as having created a github repo and added all the players)

It's also not easily accessible via our demo video...