Skip to content
Rémy HUBSCHER edited this page Oct 26, 2016 · 62 revisions

This is a rough roadmap for the future of Kinto. At the end of each item, you can find which project it is attached to, and which use-case it is serving.

Ordered by importance:

#P1

#P2

Not prioritised:

  • Document how to map from an email to a FxA id kinto (required for perms in kinto.js)
  • Handle permissions in kinto.js kinto.js
  • Sync over WebRTC
  • Synchronise existing IndexedDB
  • Bridge between offline-first protocols on client side.

2017

#1

  • Partial collection signing / sync
  • Scaling production

2016

#1

#2

#3

  • Size quotas plugin kinto
  • Permissions in kinto-admin
  • History / review changes kinto-admin
  • Plugin system for kinto-admin
  • Move Gecko storage adapter to mercurial kinto.js
  • Attachments helpers kinto-http.js

#4

  • Notifications by email plugin kinto
  • WebPush integration plugin kinto
  • Honour Backoff and Retry After headers on client side
  • → Authorship on records (via history)

2015

#1

  • Rename cliquetis to kinto.js kinto.js
  • Implicit creation of collections in personal buckets kinto
  • fix compatibility with kinto kinto.js kinto
  • Add default user buckets kinto

#2

  • Add service to service authentication kinto kinto.py (basic auth works)
  • Have a python client kinto.py payments
  • create a cliquet backend for sync cliquet sync
  • handle conflict/validation errors (on uniqueness for batch) kinto.js
  • Add pagination + batch limit on the client + server kinto kinto.js

#3

  • write demonstration applications (kept for firefox os) kinto community
  • improve documentation and tutorials kinto cliquet community
  • Add schema validation kinto
  • Permissions on records + GET collection cliquet payments
  • Allow storing data on collections go faster kinto
  • Modify collection attributes kinto.js AMO

#4

  • Notifications kinto sync go faster browser.html
  • kinto web admin console kwac
  • file attachments
  • formbuilder (lib)

Protocol v2

  • Split attributes and metadata (id, last_modified, schema, attachment)
  • Switch timestamp from integer to string
  • Timestamps should not be based on current clock, use a safe and robust sequence
  • Rename last_modified to timestamp in records
  • Hide permissions when to permission to read
  • Batch response status and transaction rollback
  • Existing record in conflict responses should be nested in data