In order to have a great and efficient DevCamp we are trying to give you as much space and autonomy as possible, but we also want to have kind of a "plan" for what should happen … so here you go …
Upfront I want to mention that it definitely is a DevCamp aka Hackathon, so there is coding involved. Which doesn't mean that each team doesn't need a decent tester or UX designer for mockups or stuff like that.
But the main part is definitely writing code and therefore participants will have to come up with amazing and cool ideas, that all of you will be able to work on.
The DevCamp is a 2-day all-hands-on-deck event, which means that the teams are being created on Tuesday and work in those teams until Wednesday afternoon. You can join on Wednesday but please be aware that you might not be able to get the full MoodleMoot DACH DevCamp experience by missing the first day.
Pitching your ideas!
The main part that you can prepare already upfront is the pitching session which involves brainstorming some cool ideas.
Please pitch each idea in a separate post, so that we can keep a better overview of all the exciting incoming ideas.
Try to think of something that
- would be useful for the community
- you would be able to finish in 1-2 days
- is original
- you would be able to make user-friendly (UX)
- follows the Moodle Coding Guidelines
- doesn't exist yet
In future posts we will be following up on the agenda for the Moodle DevCamp, some further details … and some surprises we have for you.
Anything you want to share?
If you have any questions or any suggestions, please feel free to share them with us here.
I wish you a great day and I am looking forward to our MoodleMoot DACH DevCamp in Lübeck.
Stay tuned & curious 🤓
Kasia 🏝️