.

AI Tinkerers City Organizer Quickstart Guide

Organizers
Organizers — AI Tinkerers
March 31, 2023

AI Tinkerers City Organizer Quickstart Guide

Who this guide is for

This guide is for approved or prospective AI Tinkerers city organizers who want to launch and operate a high-signal local chapter.

The goal is simple: create a room where serious AI builders can meet each other, share what they are building, trade notes, and keep coming back. A good chapter is not a generic tech meetup. It is a curated local community for people actively working with AI systems, models, tools, infrastructure, research, and products.

If you're ready to become a city organizer, please apply here.

What is AI Tinkerers?

AI Tinkerers is a global network for active AI builders: engineers, researchers, founders, operators, and technical practitioners building with AI in real systems.

AI Tinkerers events usually center on short technical demos, practical lessons, and open networking. The value comes from the quality of the room. Members should feel that they are surrounded by people who are actually building, not just watching the AI market from the sidelines.

All AI Tinkerers events and community spaces follow the AI Tinkerers Code of Conduct. Organizers should review it and lead by example to embody its principals.

Useful background links:

Why organize an AI Tinkerers chapter?

Organizing a chapter gives you a practical way to strengthen your local AI builder community.

The best reasons to organize are:

  • Build the room you want to be in. You get to convene the active builders, researchers, founders, and technical operators in your city.
  • Become a trusted local connector. A strong chapter makes you a known point of contact for serious AI work in your market.
  • Learn faster. Demos and hallway conversations expose you to what people are actually trying, breaking, shipping, and learning.
  • Join the global organizer network. Organizers are part of a small, high-trust group that shares tactics, sponsor leads, operating patterns, and local context across cities.
  • Get platform support. The AI Tinkerers platform handles much of the operational machinery: event pages, RSVPs, reminders, attendee screening, speaker proposals, surveys, member surfaces, and more.
  • Create opportunities for your city. Strong local chapters can connect into global sponsor programs, hackathons, media channels, and cross-city events.

An AI Tinkerers organizer hosting a meetup

A strong chapter feels like this: a real host, a focused room, demos with substance, and builders who have a reason to talk to each other afterward, where everyone is worth talking to and nobody is pitching, schmoozing, or philosophizing.

Who should be a city organizer?

The lead organizer should be an active builder themselves. AI Tinkerers works best when the person curating the room understands what real AI building looks like and can tell the difference between technical signal and market noise.

Organizers should also be neutral in the local ecosystem. A chapter should not feel owned by a VC firm, recruiting agency, consultancy, or vendor. Sponsors are welcome and important, but the community should remain builder-first.

A good organizer is often someone with a few of these qualities:

  • is personally active in AI, ML, applied AI products, infrastructure, research, or engineering
  • is working on a very early-stage, very cutting-edge startup
  • knows or can reach local builders
  • has enough taste to curate demos and screen attendees
  • can coordinate a venue, sponsor, event page, and event-night flow
  • will protect the room from becoming generic networking, recruiting, or vendor theater

Co-organizers can help, especially in larger cities, but one motivated organizer can run a monthly meetup if the scope is kept practical.

How each city chapter works

Each AI Tinkerers city chapter follows the same basic pattern:

  • in-person meetups, usually monthly
  • a curated audience of hands-on AI builders and practitioners
  • short community demos, usually around five minutes each
  • open networking before, after, and sometimes between demo blocks
  • local sponsors or venues that support the room without taking it over
  • event operations run through the AI Tinkerers platform
  • has a reputation for quality and a waitlist to get in

Local organizers decide the exact cadence, format, speakers, sponsors, and venue choices for their city. The average cadence is about one event per month, but quality matters more than frequency. It is better to run one strong event than to force a weak one onto the calendar.

Choose the chapter geography around the real builder community, not just a municipal boundary. In some markets, a city chapter is the right unit. In others, a broader regional or country-wide chapter may make more sense if the active builders are spread across nearby cities and would realistically travel for a strong event. The goal is to convene the right people, not to make the smallest possible map label.

Some chapters also run spotlight sessions, fireside chats, paper discussions, build nights, hackathons, or special-topic events. Those can work well once the basic community rhythm is established.

Advanced growth: tracks and focused formats

Start with the main monthly AI Tinkerers format first: the Homebrew Computer Club-style room where active builders share short technical demos and meet each other. Do not launch extra formats too early.

Tracks are dedicated subgroups or event streams under the AI Tinkerers brand. They can be useful in very large cities where the main monthly meetup is already operating consistently, has real demand, and often has a waitlist. Before that point, tracks usually create unnecessary operational complexity and split attention away from the core chapter.

Once the main chapter is healthy, tracks can help serve focused communities or formats such as:

Use tracks only when there is both capacity and demand: enough people who want the focused format, enough organizers to run it well, and enough momentum that the main monthly meetup will not suffer. The platform can provision tracks, limit organizer access to specific tracks, and map local tracks to specialized screening rubrics. This makes it easier to recruit additional organizers to run a focused subgroup without giving every organizer access to everything.

For examples and organizer discussion around new event types, use the private Office Hours blog and the organizer boards in Message Center.

How much work is it to be a city organizer?

Being a city organizer requires some time investment to set a date, coordinate sponsors, set up the page, screen members, and host the room. It is not meant to be an overwhelming operational burden: every chapter runs on the AI Tinkerers platform, which centralizes the core workflows and gives organizers support from the global network.

The main tasks left to organizers are:

  • locking in the event date and sponsors
  • setting up the event page
  • recruiting strong speakers and demo presenters
  • reviewing registrations and demo proposals to ensure that genuine AI/ML builders and practitioners are marked as attendees
  • hosting a high-signal room and keeping the local community moving

The platform also gives organizers benefits that are hard to reproduce alone:

  • automated RSVP management, reminders, check-in, attendee screening, and post-event survey feedback
  • support for speaker proposals, attendee directories, and member boards so builders can discover and connect with people locally and around the world
  • post-event media support, including video editing for speakers and short-form clips such as YouTube Shorts
  • access to global sponsor relationships and larger opportunities such as global hackathons, special events, and cross-city programs
  • membership in a small, high-trust global organizer network, which creates real relationships with other organizers and makes it easier to plug into local AI builder communities when traveling

It is usually not difficult to find a co-organizer to share responsibilities; however, it is entirely possible for a single motivated organizer to run a monthly meetup on their own.

How many organizers do you need?

There is no single required model. Different chapters work different ways.

  • Solo lead organizer: it is totally possible for one lead organizer to run a chapter, especially early on. Keep the format simple, use the platform, and do not create more operational surface area than you need.
  • Lead organizer plus volunteers: another common model is one clear lead organizer with a handful of volunteers helping on event night. Volunteers can handle room setup, check-in, QR code scanning, name tags, sponsor setup, photography, or helping speakers get ready.
  • Rotating monthly lead: in some cities, a group of organizers shares ownership and hands off the lead duty from month to month. This can work well once the group is aligned on quality, screening, sponsor expectations, and the basic event format.

The important thing is that one person owns the outcome for each event. Even with volunteers or a rotating organizer group, every meetup should have a clear lead who is responsible for the page, the room, the speaker flow, and the attendee experience.

How to get started: the 5-step launch plan

All organizing flows run through the AI Tinkerers platform, which every chapter uses for events, email, screening, and community operations.

  1. Apply: Fill out the city organizer application.
  2. Plan: Choose a date and secure a sponsor or venue for your first meetup.
  3. Create: Publish the event page so speakers, sponsors, and attendees have something real to respond to.
  4. Recruit: Line up strong demos and personally invite the first serious builders.
  5. Host: Run a focused, demo-driven room and use the platform to screen, email, check in, and follow up.

Launch your first meetup

Your first meetup is mostly about creating proof that the city has a real builder community. Keep the format simple and make the room excellent.

Think of launch as three consecutive monthly events, not one big splash. The first event proves the room exists. The second event shows it was not a one-off. The third event is where momentum, volunteer help, sponsor interest, and word of mouth start to compound.

Do not optimize the first event for maximum attendance. If 5 to 10 people show up and every person is a serious builder, that is a promising start. If 50 people show up but most are not the right fit, the best people may not come back. A small, high-signal room beats a large, unfocused room.

1. Pick a date

Choose a date about four to six weeks out. A date makes the project real and gives sponsors, speakers, and attendees something concrete to react to.

You can tell a sponsor that the date is flexible if needed, but start with a proposed date. Without a date, it is easy for planning to drift.

Once the first date is set, keep tentative holds in mind for the following two months. You do not need every detail locked, but organizers should be thinking in a three-event arc from the beginning.

2. Secure a sponsor and venue

The easiest first sponsor is often a company that already has a suitable office or event space. A sponsor that can provide both venue and food reduces logistics dramatically.

Good sponsor targets include:

  • AI companies with a local office
  • developer tooling companies
  • cloud, infra, and data companies
  • coworking spaces or accelerators with strong technical communities
  • companies that have hosted or sponsored similar events before

Share the Sponsor an AI Tinkerers Meetup page with potential sponsors so they understand the format and audience.

3. Create the event page

Creating the page makes the event real. It gives you a concrete link to share, which makes it easier to recruit speakers, confirm a venue, and bring sponsors along. People respond better to an event that exists than to an abstract plan.

Create a clear event page with:

  • the date, time, venue, and RSVP expectations
  • a short explanation of AI Tinkerers
  • who the event is for
  • the demo-focused format
  • the sponsor or host
  • the agenda
  • any speaker or demo themes you already know

The AI page creator can get you most of the way there: it will generate a roughly 90% usable event page with photos, structure, and editable sections. Treat it as a strong first draft, then revise the details so the page reflects your city, sponsor, venue, speakers, and event theme. Make sure the page clearly explains what AI Tinkerers is and who the event is for so the audience expectation is clear.

The platform mechanics for creating city pages, event pages, RSVPs, email, and attendee management are covered in the separate Organizer Platform Overview.

4. Recruit demos before you promote broadly

The page gets much stronger when it names real demos or at least specific demo themes. Try to line up several builders before you start broad promotion.

Enable speaker proposals on the event page so builders can submit demos with a title, description, and supporting links. Review proposals as they come in, approve the strong ones, sideline the ones that are not a fit, and keep the accepted speakers in a clear order before event night. Approved speakers should be confirmed as attendees and tagged as speakers so they are easy to find, email, and manage.

Once speakers are approved, add the speakers panel tag where you want the lineup to appear on the event page:

{{SPEAKERS_PANEL}}

The platform will automatically render approved public demo presenters with their image, name, talk title, and bio. Keep speaker proposals and approvals up to date before broad promotion so the page shows real people and real talks.

Good demos are technical, specific, and useful. They show what someone built, what worked, what broke, what they learned, and ideally a little of the system behind it. Avoid pitches. Avoid vague thought leadership. The room should learn something concrete.

For a first event, aim for 4 to 6 demos. If the room and schedule are strong, you can grow from there.

The sequence matters: find the right initial speakers first, then use their presence to attract the right attendees. Once quality is established, sponsors, companies, and additional speakers are much easier to recruit.

5. Promote with direct 1:1 outreach

Your first event will probably not grow from generic social posting alone. Direct outreach matters.

Start with people you know are active builders and ask them personally to attend, demo, or introduce you to someone who should be in the room. Once a few respected local builders commit, the event becomes much easier to promote.

6. Screen for the room you want

Treat RSVPs as interest, not guaranteed attendance. The point is not to fill the room with everyone who clicked a button. The point is to get the right people in the room.

Use the information attendees provide, their technical background, their projects, and any public profile links to decide whether they fit the active-builder focus.

When demand exceeds capacity, ask registrants for public profile links such as LinkedIn, GitHub, or X/Twitter. The platform can use those links to surface public signals that make review faster, and attendees can use member surfaces and directories to connect with each other. Treat those signals as inputs, not as an automatic decision: organizers still own the judgment call.

7. Host a simple, high-energy event

Open clearly, thank the sponsor, explain what AI Tinkerers is, keep demos moving, and leave real time for networking. A first meetup does not need to be elaborate. It needs to feel specific, technical, friendly, and worth coming back to.

Promotion and 1:1 outreach

For a new chapter, the most effective promotion is targeted personal outreach to people who can help set the tone of the room.

Before sending messages, map the local AI ecosystem. Every city has a different wedge. One city may be strongest in cybersecurity and defense; another may be stronger in healthcare, universities, startups, applied enterprise AI, open source, robotics, data infrastructure, or creative tools. Start where the serious builders already are.

Make a short target list:

  • the strongest local AI companies and technical teams
  • labs, universities, and research groups doing applied AI work
  • open-source contributors and independent builders
  • founders building AI-native products
  • technical people at accelerators, coworking spaces, and startup communities
  • domain-specific AI groups, such as defense, health, climate, finance, robotics, or developer tools

Then recruit from that list before doing broad public promotion. The first room sets the reputation of the chapter.

Start with:

  • founders or employees at AI startups in your city
  • engineers building with LLMs, agents, evals, infrastructure, data, or model tooling
  • researchers, professors, and students doing applied AI work
  • open-source contributors
  • technical founders, angels, and community leaders who know active builders
  • people from local coworking spaces, accelerators, and technical meetups

Ask for one of three things:

  • attend
  • demo
  • recommend 2 or 3 people who should be there

Example outreach

Use a short, personal note:

Hi Paul, I have been following your work on [company/project] and wanted to let you know that I am launching the [city] chapter of AI Tinkerers. We are bringing together people who are actively building with AI for short technical demos and networking. I would love to have you attend, and if you are open to it, present something you have been working on. Here is the event page: [link].

If they say yes, follow up with a concrete ask:

Thank you. Looking forward to meeting you. If you know 2 or 3 other active AI builders who should be in the room, I would appreciate an intro or recommendation. It would also help if you shared the event with people in your network who are hands-on with AI.

Generic social posts can help, but they should support the direct outreach, not replace it. Ask speakers, sponsors, and early attendees to share the event once the page is credible.

The experience in many cities is that after the first couple of strong meetups, word of mouth starts doing more of the work. Early curation pays off later.

Make an event people want to attend

People show up when the event feels specific, useful, and hard to replace. “AI networking” is not enough. A stronger event promise is something like:

  • live coding with agents
  • MCP demos
  • local builders showing AI products they actually shipped
  • evals, RAG, fine-tuning, voice agents, or inference infrastructure
  • a community demo night with a clear technical bar

A strong event page answers four questions quickly:

  • What will happen in the room?
  • Who is this for?
  • What will someone learn, see, or build?
  • Why is this worth leaving the house for?

Publish the agenda early when you can. Name speakers or demo themes as soon as possible. Make venue and check-in expectations clear. Reinforce that space is limited and that people should cancel if they cannot attend so another builder can take the spot.

Screening attendees

AI Tinkerers is for active builders. The screening process should protect that focus.

What counts as active building?

Look for evidence such as:

  • building applications with AI, ML, or generative AI
  • working on model training, fine-tuning, inference, evals, agents, data pipelines, or AI infrastructure
  • contributing to open-source AI/ML projects
  • doing applied AI research
  • building tools that help other builders create, deploy, evaluate, or operate AI systems
  • serious side projects, hackathon work, or prototypes that show real effort

Active building can happen at work, in research, through open source, or in serious side projects. The key is that the person is doing the work, not merely following the market.

Edge cases

Technical but not obviously AI-focused: look for evidence that they are actively learning, experimenting, or transitioning into AI. Strong software, data, infra, or research backgrounds can be relevant if there is current AI work.

Executives: technical founders and CTOs can be great members when they are close to the work. Non-technical executives without hands-on AI involvement are usually not a fit.

Data professionals: data engineers, ML platform engineers, analytics engineers, and BI professionals may be a fit when their work supports AI systems or they are actively building with AI.

Students: look for coursework plus projects, research, hackathons, open-source work, or other signs of serious initiative.

Investors, recruiters, agencies, and service providers: these people may be valuable sponsors or partners, but they should not be admitted by default unless they are personally active technical builders.

Polite ways to reject people

Keep rejections brief, kind, and focused on fit:

Scenario Example response
Asking why someone is waitlisted when the event is not full Thanks for your interest. There can be a delay between public capacity numbers and attendee review. We review applications to keep the room focused on hands-on AI builders, and we will update your status if there is a fit and space is available.
Non-technical applicant Thanks for your interest. AI Tinkerers is focused on hands-on builders and technical practitioners actively working on AI projects, so we do not think this event is the right fit at this time.
Executive without hands-on AI work We appreciate your interest. This meetup is centered on active, hands-on AI development. If you are working directly on AI projects, feel free to share more context and we can reconsider.
Student without projects yet Thanks for applying. For this group we look for some demonstrated AI project work. We encourage you to build a project, join a hackathon, or contribute to open source and apply again.
Investor or service provider with technical background Thanks for your interest. AI Tinkerers is for people whose work is centered on actively building AI systems. If your main role is investing or services, the best way to support the community is usually as a sponsor or partner rather than as an attendee.
Recruiting or sales motivation Thanks for your interest. AI Tinkerers events are not recruiting or sales events. We keep the room focused on peer learning among active AI builders.
Company asked them to attend for recruiting Thanks for reaching out. These events are not intended for recruiting coverage. If someone from your company is personally building AI systems and wants to participate as a peer builder, they are welcome to apply individually.

Sponsor management and event logistics

Sponsors make local chapters possible, but the event should remain builder-first.

A good sponsor usually provides:

  • venue
  • food and drinks
  • credits, infrastructure, technical expertise, or other useful support
  • optional help promoting the event to relevant builders

In return, the sponsor gets visibility with a highly curated technical audience. They can be thanked on the page, included in email, and given a useful moment at the event.

Sponsors support the community, so it is reasonable to give them more format latitude than an ordinary presenter. Agree on one of two formats:

  1. Sponsor technical demo: a technical person shows something genuinely interesting the team built, where the sponsor’s product is naturally part of the story. The goal is to teach or inspire an audience of builders rather than explain value props, product differentiation or high-level non-technical content.
  2. Short sponsor welcome: a quick elevator pitch, not a presentation, followed by an optional QR code for credits, early access, a giveaway, or another opt-in offer.

If your sponsor contact nominates someone else from the company, brief the actual presenter directly several days before the event and confirm which format they are using. The sponsor liaison and presenter are in the same organizational in-group; the organizer is outside it. A relayed “no company deck” instruction is easily softened into “they prefer fewer slides.” Direct preparation prevents a surprise deck and gives the sponsor a better result.

For sponsor content, keep the page clean:

  • sponsor name linked to their site
  • 2 or 3 lines explaining what they do
  • logo
  • any agreed sponsor language or tracking links

Practical tip: to draft sponsor descriptions quickly, read the sponsor homepage and about page, then ask an AI assistant to write a short, straightforward description for an AI Tinkerers event sponsor section.

For payments, try to have sponsors cover costs up front instead of reimbursing after the event. Send invoices as soon as a sponsor confirms, and assume payment timing will vary: small companies may pay immediately, while larger companies may need procurement time. Confirm who is paying for food, drink, venue costs, signage, security, or cleaning before the page is promoted broadly.

Food and drink budget

Plan food around actual attendance, not just RSVPs. In many cities, actual attendance lands around 50% to 70% of confirmed attendees, depending on the market, venue, weather, and reminder quality.

As a practical baseline, budget around $8 per actual attendee for food and drinks. Pizza and sparkling water are often the best default: they are predictable, inexpensive, and usually get better results than trying to impress people with complicated catering. Beer, soda, and expensive food options often add cost without improving the event.

The key rule is simple: people come for the demos and the room, not the catering. The food only becomes a problem when you run out.

Event-night logistics

Before doors open, assign owners for the practical jobs:

  • room setup, seating, projector, microphones, and Wi-Fi
  • check-in, QR code scanning, and name tags
  • speaker readiness and laptop handoffs
  • sponsor greeting and sponsor introduction
  • food delivery timing and cleanup expectations
  • photography or short video clips if you plan to capture the event

Use volunteers for these jobs when you have them, but keep one person accountable for the full event flow.

Sponsor outreach, sponsor pitch generation, sponsor directories, VIP dinner tools, and invoicing workflows are covered in the Organizer Platform Overview.

Demos, agenda, and event structure

The standard AI Tinkerers format is short technical demos plus networking.

How many demos should we have?

For a three-hour meetup, a good target is 4 to 8 demos of about 5 minutes each. Four to six demos is often better for a first meetup, especially if you want room for questions. More than 8 demos usually makes the event drag.

If you run 8 demos, split them into two sets of 4 with a 10-minute break between sets. If you want the format to be more interactive, allow 1 or 2 quick audience questions after each demo and reduce the count to 4 to 6 demos.

Remember that open networking is also part of the product. Do not pack the agenda so tightly that people lose the time to meet each other.

Prioritize:

  • demos over pitches
  • working systems over concepts
  • technical lessons over marketing
  • specific failures and learnings over polished claims
  • builders who can show what they made

Use speaker order to keep transitions fast. Put speakers in a clear sequence before the event starts and remind them of the time limit.

Optimized event structure

For a larger or more mature meetup, a two-part structure works well:

  • Main stage: open with a short welcome, make the room interactive, then run 3 curated demos or presentations with strict timing and 1 or 2 quick questions after each.
  • Networking and science fair: invite additional builders to demo from tables or stations so people can go deeper on the topics they care about.

If you use the science-fair format, have each table presenter give a 30-second preview from the front of the room before networking starts. That gives attendees a map of what to explore.

Sample first-meetup agenda

  • 5:30 - Doors open and casual networking
  • 6:00 - Welcome, what AI Tinkerers is, sponsor thanks
  • 6:10 - Demo block 1
  • 6:45 - Short break and networking
  • 7:00 - Demo block 2
  • 7:35 - Announcements, next steps, group photo if useful
  • 7:45 - Open networking
  • 8:30 - Close

Adjust the timing to fit your venue. The important parts are a clear opening, tight demos, and enough unstructured time for people to meet each other.

How do I conduct the demo portion of the event?

Keep demos practical, timed, and focused on what was built. A good demo shows the working system, the technical choices behind it, what broke, and what the builder learned. A weak demo turns into a pitch or a vague trend talk.

We made a separate page about this: How to run demos.

Hosting the room

At the event, your job is to set the tone and protect the pace.

How do I conduct the meeting itself?

Open with:

  • what AI Tinkerers is
  • who the room is for
  • thanks to the sponsor and venue
  • the demo format and time limit
  • how people should participate

Make it interactive early. Ask quick show-of-hands questions:

  • Who is here for the first time?
  • Who is building with agents?
  • Who has shipped something using open-source models?
  • Who is working on evals, RAG, voice, data, or infra?

This helps people locate others with shared interests and makes the room feel alive before demos begin.

During demos, keep time. If a speaker drifts into a pitch, gently bring it back to what they built and what the room can learn from it. Leave enough networking time. Many attendees value the conversations as much as the talks.

Keep the room moving, but do not over-script the evening. The best meetings feel hosted, not controlled.

After the meetup

The best time to build momentum for the next event is immediately after a good one.

After the meetup:

  • thank the sponsor and speakers
  • review survey feedback
  • note which demo topics landed well
  • identify strong attendees who could present next time
  • ask speakers for links or follow-up materials
  • share photos or recap notes if useful
  • start looking for the next sponsor, venue, and date

The AI Tinkerers platform can support post-event surveys, speaker media workflows, edited videos, short clips, attendee records, and member connections. Those details are covered in the Organizer Platform Overview.

Media and amplification

Strong local demos can travel beyond the room. When practical, record presentations, take photos, and capture enough context that speakers and sponsors can share the event afterward. The platform can help route speaker media, edited videos, and short clips.

Use the broader AI Tinkerers media channels when the quality is there:

  • nominate standout demos for Post Training
  • encourage strong founders or builders to appear on One-Shot
  • point researchers and paper-heavy talks toward Paper Club
  • use Virtual Events for topics that deserve a cross-city audience

Platform overview

Every AI Tinkerers chapter is required to use the platform. It’s how we maintain a consistent, high-signal experience across all cities and equip organizers with tools to operate as one global community of builders.

The platform supports:

  • city pages and publishing
  • event pages and RSVPs
  • confirmation and reminder emails
  • attendee screening and waitlists
  • QR code check-in
  • attendee tags and management
  • speaker proposals
  • post-event survey feedback
  • member boards and attendee directories
  • sponsor tools and sponsor workflows
  • media support and video editing
  • global programs such as hackathons and special events

This quickstart intentionally avoids explaining every platform feature. For tool-by-tool instructions, use the separate Organizer Platform Overview.

Questions

If you are an approved organizer, use the in-app Support button for platform questions, bugs, or anything that needs HQ help.

For organizer-to-organizer questions, use Message Center, especially the All Organizers board. That is the right place to compare notes, ask how other chapters handle something, and keep the discussion visible to the organizer network.

If you need HQ in the loop, use the Support button or post in Message Center so the conversation stays on the platform.

If you are not yet an organizer, start with the city organizer application.

If you're ready to become a city organizer, please apply here.

Ready for more?

Check out other posts from this blog.

View all posts