Difference between revisions of "Main Page"
(→Badges) |
(→Badges) |
||
(43 intermediate revisions by 24 users not shown) | |||
Line 1: | Line 1: | ||
− | == | + | == Introduction == |
[[File:Badge Selection.png|frame|right]] | [[File:Badge Selection.png|frame|right]] | ||
− | Welcome to badge.team wiki for all info on [https://badge.team badge.team] compatible badges :) | + | Welcome to badge.team wiki for all info on [https://badge.team badge.team] compatible badges :). Badge.team is a project with the aim of providing a reliable off-the-shelf firmware for electronic event badges, with easy creation of MicroPython badge apps known as eggs and their deployment to end users through an app store known as the hatchery. It has its roots in the team responsible for the successful badge at the [https://sha2017.org/ SHA2017 hacker camp] in the Netherlands. Currently (Q1 2019) the badge.team firmware supports ESP32 platforms, and the team have produced firmware for three event badges with another in development. |
=== Badges === | === Badges === | ||
− | [[SHA2017Badge]] released at [https://sha2017.org/ Still Hacking Anyway] August 2017 | + | * [[SHA2017Badge]] released at [https://sha2017.org/ Still Hacking Anyway] August 2017 |
− | [[Disobey2019Badge]] released at [https://disobey.fi/ Disobey] January 2019 | + | * [[Disobey2019Badge]] released at [https://disobey.fi/ Disobey] January 2019 |
+ | * [[HackerHotel2019Badge]] released at [https://hackerhotel.nl/ Hacker Hotel] February 2019 | ||
− | + | ==== Future badge projects ==== | |
− | + | * [[CZ19]] CampZone 2019 | |
+ | * [[AnOtter_Watch]] to be released summer 2019 | ||
+ | * [https://twitter.com/card10badge card10] cccamp19 | ||
+ | Your badge? Join us on [http://webchat.freenode.net/?channels=%23badgeteam%2C%23badgeteam-dev&uio=d4 IRC] or [https://t.me/joinchat/AMG-ZhQQ9cE1KAAbQozy5Q Telegram]! | ||
− | + | === Getting started with badge development === | |
+ | |||
+ | Our firmware supports apps, which we refer to as eggs. We encourage you to write your own eggs in MicroPython, and to that end we've produced [[Tutorials/|some tutorials]] aimed at the first-time egg developer. | ||
+ | |||
+ | * [[Tutorials/Your_First_Egg_(for_uGFX_badges)|Your first egg]]. Step-by-step, writing a simple Hello World egg. | ||
+ | * [[Simple_Egg_Deployment| Egg deployment for beginers]]. How to connect to your badge, and put code on it. | ||
+ | |||
+ | We also have a reference for [[MicroPython|the badge-specific MicroPython functions]] on your badge. | ||
== Why badge.team == | == Why badge.team == | ||
Line 37: | Line 48: | ||
* Thomas Roos | * Thomas Roos | ||
* Kliment | * Kliment | ||
+ | * Ikmaak (on-site support) |
Revision as of 16:47, 21 July 2019
Contents
Introduction
Welcome to badge.team wiki for all info on badge.team compatible badges :). Badge.team is a project with the aim of providing a reliable off-the-shelf firmware for electronic event badges, with easy creation of MicroPython badge apps known as eggs and their deployment to end users through an app store known as the hatchery. It has its roots in the team responsible for the successful badge at the SHA2017 hacker camp in the Netherlands. Currently (Q1 2019) the badge.team firmware supports ESP32 platforms, and the team have produced firmware for three event badges with another in development.
Badges
- SHA2017Badge released at Still Hacking Anyway August 2017
- Disobey2019Badge released at Disobey January 2019
- HackerHotel2019Badge released at Hacker Hotel February 2019
Future badge projects
- CZ19 CampZone 2019
- AnOtter_Watch to be released summer 2019
- card10 cccamp19
Your badge? Join us on IRC or Telegram!
Getting started with badge development
Our firmware supports apps, which we refer to as eggs. We encourage you to write your own eggs in MicroPython, and to that end we've produced some tutorials aimed at the first-time egg developer.
- Your first egg. Step-by-step, writing a simple Hello World egg.
- Egg deployment for beginers. How to connect to your badge, and put code on it.
We also have a reference for the badge-specific MicroPython functions on your badge.
Why badge.team
Long-term support on event badges #aftercare
It's sad to see these things become e-waste in no-time.
Who are badge.team
This is not a complete or ordered list, feel free to add yourself if you think you belong to our merry band of badge hackers :)
- Sebastian Oort
- Anne Jan Brouwer
- Bas van Sisseren
- Renze Nikolai
- Markus Bechtold
- Jeroen Domburg
- Niek Blankers
- Tom Clement
- Arnout Engelen
- Mendel Mobach
- Thomas Roos
- Kliment
- Ikmaak (on-site support)