- We have been chatting async using flipgrid
- Our brainstorm was started in Figjam
- Hackathon planning template
- We can use any channels on the AngellXR discord. I encourage the team to pull in others from our community in the planning and execcution.
- @mrawhite made this website using this repo
- Cross platform
- Device agnostic
- Some association with history
Love explicitly calling out the first two. I actually think that’s something we could improve on from the last hackathon.
- heading into summer isn’t the best time
- is a hackathon in September at schools return good timing?
- can we establish monthly or every 2-3 week touch bases on the planning.
- To learn more about formatting notes like this, look into markdown
- If you want to expand on this readme, by all means please click "edit" in the top right. If you would prefer a GUI, you may visit the connected hackmd doc here This doc is connected to the readme.
- To discuss the eduverse hackathon on Github, please visit our Github discussions section for the hackathon. Discussions are easily used to discuss any and everything related to the repo. I am testing the effectiveness of this strategy in long term. I believe practicing these documetnation habits will help accomodate for a variety of schedules, skillsets, and preferred tools.
- These repos are able to hold links to any other docs or workspaces. So whether its figma or flipgrid, we can link to the places work is happening, and help close some of the gaps. Hopefully, this will help us measure progress, set the right goals, and grow.
- If you want to create a quick note in this repo, click "Add File" and give your new note a name. If you end the name with ".md" it will format the doc as a markdown file. To learn more about markdown, please see the link above.
- Work where you are most comfortable, just hook on your work here in the readme, or in a comment in discussions.🥳
- Placeholder logo
- Placeholder site
- Set up discord for eduverse (hackathon in angell discord, but we can leverage both with a objective of growing both communities)
- What are we missing here?
- Why is this hackathon important?
- How do we want to promote this event?
- Who are potential key partners?
- What do we hope to achieve (objectives)
- Things to avoid
- Begin documentation (establish some curriculum. Let's explore this deeper)
- Review this readme, is there any information we could tell in a better way? How might we iterate on our documentation to ensure it is clear for all who join later?
Largely community driven Accessible by anyone who wants to be part of that How might we ensure that the experiences have a place to live without going broke? Do we follow the showcasexr model?