Sharing is caring, when the care rules are clear.

Film clubs work better when people can see what is available, who looks after it, how it comes back, and what should never be exposed publicly.

Asset Layer

From what I have to what we can make together.

This page borrows the clean idea from the Straddie Content Assets Kit: make simple Markdown files for personal assets, shared team assets, wish lists, and upgrade paths. For QFF, that becomes a film-club and workshop layer.

Share capacity, not private locations, contact details, logins, protected places, or unapproved cultural permissions.

What can be mapped?

  • Phones, cameras, microphones, tripods, lights, screens, projectors, power, storage, and editing tools.
  • Skills people can offer: filming, interviewing, captions, transport, setup, pack-down, editing, file naming, or youth support.
  • Borrowing rules, asset stewards, safety notes, repair notes, file workflows, and backup habits.

Clean Sharing Pattern

Four Markdown files that keep the kit honest.

asset-list.md

What one person or project already has, can use, can lend, or needs to keep private.

shared-assets.md

What the team can use together, who stewards it, and what care rules apply.

equipment-wishlist.md

What to borrow, buy, sponsor, delay, repair, or train for next.

upgrade-roadmap.md

A staged path from phone-first basics to reliable workshops, screenings, and film club support.

A phone, notebook and planning cards on an outdoor table

QFF Builder

Use one simple builder here first.

The QFF asset-sharing builder makes a single `asset-share.md` file that can later be split into separate asset list, shared asset, wish list, or roadmap files if the film club grows.

Open asset sharing builder

For the dedicated source pattern, visit the Straddie Content Assets Kit.

Boundaries

Good sharing avoids quiet pressure.

A listed asset is not consent to borrow, film, publish, sponsor, sell, store, access, or promote anything. Every shared item still needs a person, a yes, a care rule, and a return path.

  • Keep expensive gear locations, private addresses, logins, account details, and raw contact lists out of public files.
  • Keep protected places, cultural permissions, youth details, and safety-sensitive notes out of public pages unless reviewed.
  • Use public files for capability and approved needs; use private working notes for sensitive detail.