Skip to content

Latest commit

 

History

History
189 lines (140 loc) · 4.59 KB

2024_09_29.md

File metadata and controls

189 lines (140 loc) · 4.59 KB

TinyShed 2024-09-29 20:00UTC

Agenda

  • review Actions from Last Time
    • Michael
      • book October meetup? -> send flight dates to the Signal group
    • CFT
      • request more input from others -> non yet
    • Nanomonkey
      • post up proposal work
      • set up grant conversation with Mix
  • git org / repo (see suggestion below)
  • follow up on the DB schema, suggestion for doing a "traditional" (=non log) strawman SW
  • propose message types
  • complete the walk-through of requirements, synthesis
  • back-casting?
  • grant money - needs story/ goals

Suggestions for a "Git Repo- and Directory Structure for TinySched" (cft 2024-09-29)

TinySched is a placeholder, replace with what we will converge on (S4 = Secure Scuttlebutt Scheduling System etc)

Approach

  • go for a minimum of repos i.e., two
  • separate release-worthy code from development that includes UI and experiments with traditional DBs etc

Repo 1 (SW for Android and ESP32)

Reuse https://github.com/ssbc/tinySSB

Repo 2: "sandbox" (prepare and try out)

Suggestion1 = https://github.com/ssbc/S4-sandbox

Suggestion2 = https://github.com/S4-sandbox

Repo/directory structure for the sandbox

root
 ├── README.md
 │
 ├── minutes
 │
 ├── db
 │   ├── py
 │   │   ├── demo-Jan25
 │   │
 │   ├── ...
 │
 ├── ui
 │   ├── wireframes
 │   │   ├── ...
 │   │
 │   ├── node
 │   │   ├── demo-Jan25

Option B - new org

  • github.com/tiny-ssb/prod
  • github.com/tiny-ssb/notes
  • github.com/tiny-ssb/design

Name of the Org:

daitom
tiny-butt
EventYawl  (nautical theme)
SchedSweeper (analogous to Minesweeper)

Relational Database schema

follow up reflection from CFT:

  • should we start with a relational schema
    • can we decouple append-only log + relational db?
    • aim could be to get towards a demo + discussable

Message Types (contributed by Nanomonkey)

Person

  • name
  • ? phone (optional)
  • ? email (optional)
  • ? pronouns (optional)
  • ? address
  • ? image

contact info could be encrypted for e.g. just organisers to have access to.

Location

  • name
  • geo <float, float> [latititue||longitude] (third option: altitude)
  • timezone (+/- integer from UTC)
  • address
    • optionally break out:
      • POBox
      • street-address
      • locality (city)
      • region (state, provence)
      • postal (postal-code)
      • country
  • ? sublocations (list of Locations)
  • ? access list (list of Persons)
    • people who are allowed to go to that location?
  • ? tags (optional)

Event (bundle into Listing/Booking?)

  • location (contains timezone, etc.)
  • organizers (Group|Person)
  • interval (ISO8601?) optionally break out:
    • start - the event starts
    • end - the event ends
    • duration (seconds, or valid W3C duration string)
    • repeating (Rn)
  • schedule

Listing (or Booking, or Event (with above rolled in?))

  • name - event name (or title)
  • summary - short summary of the listing
  • description - more detailed description of the event
  • event - (optionally embed event fields)
  • ? url - permalink for the event
  • ? media -
  • ? tags (category?) [, …] optional, zero or more (could include session)
  • tags/category - event category(ies)/tag(s)
  • type: [sell|rent|trade|meet|announce|offer|wanted|event|service]
  • lister: (inherent in feed id)
  • listed: (inherent in SSB feeds, optionally added in tinySSB?)
  • ? expires: (optional)
  • ? price: { - amount: (ints of cents?)
  • currency: (iso 4217 currency code)}

RSVP

  • event

for attendance. the author is implicit in the message

Money agreements

Nano to work on:

  • paid hourly rate: $50 USD
  • paid hours per week: upper bound of 10 hours a week
  • working on:
    • participate in meetings
    • documentation
    • workflow / user journey / UX design
  • update when:
    • grants change
    • work changes

Mix + CFT

  • contribute hours - 1/2 a day a week or fortnight

Add HERE a link to the main document that keeps a list of URLs to all minutes/agendas (including this one)

Actions

  • Mix

    • progress the Github org + repos
    • post to SSB about OC funding this work

  • CFT

    • invite others to contribute Work Flows

  • Nano