What Is Open, What Is Planned, What Is Missing

What Is Open, What Is Planned, What Is Missing

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

Where the software stands: meant to be published under open licenses (MIT, CC BY-SA 4.0, AGPL-3.0), none of it published yet; the child's path and the guide's class view built, while the parents' view and several school-office functions exist only as a demonstration or not at all. Closes with links to the rest of the series.

The software is meant to be open. The whole stack that runs a Fido school is to be published, so that other schools and researchers can use, change, and run it. The plan fixes the licenses: the MIT license for the code that displays content and for the explorer, CC BY-SA 4.0 for the curriculum, and AGPL-3.0 for the app, the server, and the mastery engine. Under the AGPL, anyone who runs a changed version as a service must publish the changes. What stays private is data: children's records, passwords, and keys.

None of it is published yet. The code lives in a private repository. The first step, making the display code usable on its own, is partly done. Publishing that code comes next, then the curriculum, the explorer, and finally the app and the server.

What runs today is mainly the child's path: articles, reading, practice, the mastery engine on the tablet, sign-in, and a class view for guides with real data, including a list of the children who need a look. Measured against the full plan, much is still missing.

  • The parents' view of a child's progress, and the guide's tool for handing out Fido Bucks, run only in a demonstration mode, with sample data. Children already earn Fido Bucks by practicing; the Fido Store, where they are to spend them, is not built.
  • Calls with outside subject tutors, the planning of workshops, and the curriculum report for the school authority are not built.
  • Nor are the timing of the short practice blocks, notifications to parents, or a termly summary that could stand in for a report card.

Five more articles take the software further: Curriculum as Data, Rendered Anywhere, The Mastery Engine, The App, the Server, and Where a Child's Work Lives, How We Know It Works, and How a Small Team Builds Fido's Software with AI. Three more look beyond the software: Fido's Bet and How We Will Know, How Fido Is Meant to Reach Beyond One School, and How Fido Is Meant to Be Paid For. Two tell whom Fido serves: Who Fido Is For, and What It Owes and Fido Between Two Kinds of School.

Questions, objections, or keen to help build it? Write to us.

Keine Aufgaben fĂĽr dieses Thema.