Project outline:

1. Identify target audience (teachers, parents, kiosk administrators and such)

2. Gather requirements

   1. Ask users for user input

   2. Look into Pessulus features

   3. Read Pessulus feature requests

3. Write application that implements existing lockdown features in GNOME

   1. Dummy interface with no functionality

   2. Fancy gsettings key on-off switching

   3. Working presets for different use cases

4. Implement lacking lockdown features in GNOME software

   1. Negotiate with respective software developer and design team if/how the feature should be implemented

   2. Try to convince the developer, to implement the feature

   3. If the developer refuses to implement the feature, try to write it myself

5. Implement import/export of lockdown settings

6. Polish the lockdown editor

   1. Add i18n support

   2. Verify a11y

   3. Verify, if documentation is up to date

Project schedule:

May 21:

Gathering requirements and ideas for the functionality and UI.

Deliver feature list and UI sketches.

June 4:

Discuss the implementation of lockdown with respective software developers.

Start writing wire-frame of the software.

Deliver mock-up of the software, no functionality so far.

June 18:

Write front-end implementation of existing lockdown features.

Discuss with other GNOME software developers how to develop missing lockdown features and who should do that

July 2:

Finish writing functional part of the software.

Deliver functional (albeit unpolished) lockdown editor.

July 16:

Write patches for for missing lockdown features in GNOME software.

Visit GUADEC.

August 2:

Continue writing patches.

Implement import/export of lockdown settings.

Polish the lockdown editor.

August 13:

Finish polishing.