OpenAstro — Community Building Playbook¶

This is the operational document for building and sustaining the volunteer observer community. It covers where to find people, how to communicate with them, what infrastructure to build, and how comparable projects handled the same problems.

The existing "Getting People" file in this vault has a good foundation for recruitment mechanics. This document focuses on community architecture — the structural decisions that determine whether OpenAstro grows to 50 active observers or 500.

Part 1: Comparable Project Case Studies (Deep Dives)¶

ExoClock¶

URL: https://www.exoclock.space
Scale: Grew from 140 to 300+ observers in approximately 14 months (2021-2022). The 2022 ExoClock paper listed 160+ amateur co-authors.
Structure: The project is scientifically led by Anastasia Kokori and Georgios Tsiaras at UCL. It is not fully autonomous citizen science — it has professional leadership and a defined mission (refining exoplanet transit ephemerides for the Ariel mission).
Why it grew: Four structural decisions drove growth:
Institutional anchor: The Ariel ESA mission gave participants a concrete destination for their data. "Your transit times will be used to plan JWST follow-up" is motivating in a way that "contributing to science" is not.
HOPS (Holomon Photometric Software): A purpose-built, easy-to-use photometric pipeline that any observer could install and use without knowing professional photometry tools. Reducing the technical barrier was the primary growth driver.
Direct co-authorship: Papers explicitly listed every contributor. The 2022 publication in Monthly Notices of the RAS had 160+ named co-authors, many of them amateurs. This circulated heavily in amateur astronomy communities.
Regular feedback: Monthly newsletters with "what the network achieved this month" and acknowledgment of individual contributions.
What OpenAstro can replicate: The HOPS model maps directly to the OpenAstro client software. If the client is as easy to use as HOPS, the friction barrier drops to near-zero. The institutional anchor equivalent for OpenAstro is not a space mission (no ESA anchor exists) but could be constructed through a professional collaborator — a faculty member at any university who needs the kind of data OpenAstro produces.

AAVSO Campaign System¶

URL: https://www.aavso.org/alert-notices
How it works: When a professional astronomer needs multi-epoch photometry of a specific target, they contact AAVSO, who issues an "Alert Notice." This goes to all AAVSO observers matching the equipment requirements. Data is submitted to the AAVSO International Database, the requesting astronomer accesses it, and the result is published.
The community architecture: AAVSO maintains a Discussion Group (email list, now also web forum), a Mentor Program (new observers are paired with experienced ones), and the Variable Star Index (VSX) where observers contribute discovery and classification data. These three components create a community of practice rather than just a data submission queue.
Lesson: The distinction between a data pipeline and a community of practice is critical. A data pipeline retains people only as long as they are technically engaged. A community of practice retains people through social capital — relationships, reputation, identity. OpenAstro needs to build both, and treat them as separate products.

Global Meteor Network (Community Mechanics)¶

URL: https://globalmeteornetwork.org, Discord: actively maintained
Discord structure: The GMN Discord (~1,000 members) has channels by region, by meteor shower, for equipment support, and for data analysis discussion. Critically, the leaders of the network are active in Discord, answer questions personally, and participate in the community rather than just broadcasting announcements.
What motivated GMN participants (anecdotal, from public forum posts):
"My station caught the Leonid outburst" — event-specific pride
"I solved a trajectory calculation problem that showed this meteor came from outside the solar system" — technical problem-solving satisfaction
"I know Denis [Vida, lead scientist] personally from Discord" — relational connection to the science leadership
Lesson: Community leaders who are personally accessible are disproportionately powerful retention tools. The founder of OpenAstro being personally reachable on Discord — answering equipment questions, commenting on a participant's light curve, acknowledging a particularly good night's data — is worth more than any automated system.

PANOPTES (What Didn't Work for Community)¶

PANOPTES struggled to build community precisely because the product was hardware-first. Participants were unit hosts, not active observers. They didn't make nightly decisions. The result was that most PANOPTES units were deployed at schools or institutions where the "community" was the institution, not individuals. The online community never developed strong social bonds because there was nothing to discuss nightly — the unit either worked or it didn't.

OpenAstro's model is different (active observers making scheduling decisions, receiving alerts, choosing targets) but the lesson is: design for regular, frequent interaction points, not just deployment and monitoring.

Part 2: Where to Find People¶

Tier 1 — Highest Conversion Rate¶

These channels reach people who already have appropriate equipment and scientific motivation.

AAVSO - Approach: Contact the AAVSO Executive Director (direct email via aavso.org/about/staff) to discuss a formal data partnership. The AAVSO-OpenAstro relationship should be symbiotic: OpenAstro observers contribute to AAVSO's database; AAVSO observers are notified of OpenAstro campaigns. This is not recruiting from AAVSO — it is aligning with them. - Separately, post in the AAVSO Discussion Group (https://www.aavso.org/forums) introducing the project. The AAVSO community is sophisticated enough to engage technically. - AAVSO Sections most relevant: Photometry (for transit/variable star work), High Energy (for transient follow-up), Exoplanet (for TTV campaigns).

Cloudy Nights — Targeted Subforums - "Science! Imaging/Photometry/Spectroscopy" subforum: The highest-value subforum. People here are already doing calibrated science. - "CMOS Astrophotography" subforum: Many participants are doing sub-arcsecond guided imaging that would meet OpenAstro data quality standards. - Initial post strategy: Post a technical question ("What zero-point calibration method are people using with gain-boosted CMOS sensors?"). Engage in the thread. Two weeks later, mention you're building a pipeline for this. Three weeks later, invite interested people to test it. This is a 6-week engagement arc, not a single announcement.

Society for Astronomical Sciences (SAS) - Annual symposium (usually May, held in Ontario CA area). Focused entirely on professional-amateur collaboration in photometry. URL: https://socastrosci.org - This is the single highest-concentration venue for exactly the type of observer OpenAstro needs: people already doing science-grade photometry with calibrated equipment. - Target: Present a 15-minute talk at SAS. The abstract deadline is typically February. The talk should be about the calibration methodology, not about recruiting.

IOTA (International Occultation Timing Association) - URL: https://occultations.org - 600+ active members globally. These are the people who do the exact type of coordinated, time-critical observation that OpenAstro Stage 2 science (asteroid occultations, lunar grazing occultations) requires. - Approach: IOTA already has a campaign system and reporting infrastructure. OpenAstro should frame itself as compatible with IOTA, not competing. A joint observation campaign where OpenAstro handles the scheduling and IOTA provides the observer network is an ideal early Stage 2 collaboration.

Tier 2 — Medium Conversion¶

Cloudy Nights (Broader Subforums) - "General Observing" and "Equipment" forums. Lower conversion than Science subforum, but much larger audience.

BAA Variable Star Section - URL: https://britastro.org/vss - Directly analogous to the AAVSO photometry community, UK-based. The BAA VSS coordinator is typically reachable and interested in partnerships.

AstroBin - URL: https://www.astrobin.com - 60,000+ users who post astrophotography images. Many are doing calibrated imaging with guide cameras — they have the equipment. AstroBin has a forum component. More importantly, observers who publish on AstroBin have public equipment lists that indicate their capabilities.

BAA Asteroids and Remote Planets Section - For asteroid astrometry and occultation observers.

MPC Observers - The Minor Planet Center maintains a list of active amateur observers submitting astrometry. These are exactly the technically capable amateurs OpenAstro needs for asteroid occultation campaigns. The MPC observer list is public (https://minorplanetcenter.net/iau/lists/ObsCodes.html). Many observers have public contact information through their affiliated observatories. This list is a cold-outreach goldmine for Stage 2.

Tier 3 — Long-Term Community Building¶

Reddit — covered in Marketing Strategy doc. Content-first, recruiting-second.

YouTube — the OpenAstro channel should document science results, not the project itself. "Here is the light curve from 12 stations during last night's occultation" is a video. "Here is what OpenAstro is" is not.

Twitter/X - Follow and engage with the #proamastronomy, #citizenscience, and #astrophotography hashtags. - The goal is not advertising but genuine engagement with the community. Retweet good science results from comparable projects. Post your own results. Be a good citizen of the astronomy Twitter community before asking anything of it. - Account: @OpenAstro or equivalent. Set up early, post consistently, do not use it as a press release feed.

Star Parties - Texas Star Party (annual, May): ~500 attendees, mostly serious observers. - Stellafane (annual, August, Vermont): 700+ attendees, very technical. - Oregon Star Party (annual, August): Pacific Northwest focus. - Northeast Astronomy Forum (annual, April, New York): Large, commercially focused but good for visibility. - Cost: Registration + travel. High in-person conversion rate. One star party appearance + 20 good conversations = 3-5 long-term active contributors.

Part 3: Communication Infrastructure¶

Minimum Viable Communication Stack¶

The communication infrastructure should be operational before any public recruitment begins. A project that recruits people and then has no organized communication channel is worse than having no project.

Discord Server (primary real-time community)

Required channels at launch:

#announcements       — one-way, admins only, major updates
#introductions       — new member self-introductions
#general             — open conversation
#observing-tonight   — real-time coordination, cleared at midnight UTC
#tech-support        — equipment and software help
#data-submissions    — automated bot posts when observations are received
#science-results     — light curves, discoveries, analysis
#campaigns           — active campaign coordination
#off-topic           — keeps off-topic conversation out of science channels

Optional at scale:

#regional-[name]     — regional coordination channels (Europe, Americas, Pacific)
#equipment-[type]    — type-specific channels (CMOS, CCD, OSC)
#mentor-program      — pairing channel

Rules for Discord moderation: - The founder/leader should be active daily, at minimum reading every channel. Not necessarily posting, but present. - A pinned FAQ in every channel reduces repeated questions. - Bots: Use Carl-bot or similar for role assignment. Consider a welcome bot that auto-assigns a region role based on member self-selection.

Email List / Newsletter - Platform: Buttondown (https://buttondown.email) or Substack for simplicity. Mailchimp for scale. - Cadence: Monthly digest. No more, no less at Stage 1-2. Increase to bi-weekly at Stage 3 if there is enough content. - Content formula for each issue: 1. Network status (current active sites, observation count this month) 2. One result or science highlight (what did we learn from last month's data) 3. Upcoming campaign preview (what to observe next month) 4. Technical tip or tutorial 5. Contributor spotlight (named individual with their permission) 6. Any news (paper published, partnership, grant award)

Forum Thread (Cloudy Nights / IceInSpace) - Maintain one active "project thread" on each major forum. Update it with results. Respond to every question within 24 hours. - This is time-consuming but high-value for community credibility.

GitHub - All pipeline code open source from day one. This is non-negotiable for credibility with the technical astronomy community. - The README should explain the science context, not just the code. - Issues and pull requests from community contributors should be acknowledged and merged (or declined with explanation) promptly.

The Feedback Loop (Critical for Retention)¶

The single biggest retention driver, consistently across all citizen science research, is whether participants feel their data mattered. The feedback loop must be automated and immediate.

Level 1 (seconds after submission): Automated acknowledgment. "Observation received. Quality score: [score]. [N] observations needed to complete this light curve." This tells the observer immediately that (a) it worked, (b) their observation was good, and (c) what remains.

Level 2 (next morning): Automated digest email. "Last night's network: [N] observations from [N] sites. Your contribution: [X] observations, [Y]% of total coverage for [target name]."

Level 3 (campaign completion): When a campaign's data is complete and the light curve is published to the data archive, every contributing observer receives a personal email linking to their contribution.

Level 4 (paper submission): Personal email from the lead author (or a template that feels personal) informing the observer that their data is included in a submitted paper. Include a draft citation they can use immediately.

Level 5 (paper published): Another email with the DOI. This is the culminating moment. Every person who contributed should know the paper exists and be able to find their name in it.

Missing Level 4 and 5 is the most common failure mode in citizen science projects. The paper gets published and participants never hear about it.

Part 4: The Mentor Program¶

A mentor program is a force multiplier for onboarding. It has two benefits: it helps new members succeed technically (reducing support load), and it gives experienced members a valued role that increases their own retention.

Structure: - Mentors are volunteers who have submitted at least 200 accepted observations and have been in the network for at least 6 months. - Each mentor is assigned 2-3 new members per cohort (each calendar quarter). - Mentor responsibilities: welcome message within 24 hours, offer a video call for equipment setup, respond to the mentee's technical questions in Discord for the first 30 days. - Mentors are listed on the website and acknowledged in annual reports. - There is no compensation. The incentive is recognition and the satisfaction of passing on knowledge. This is consistent with AAVSO's mentor program model.

How to recruit first mentors: The first few will be from personal contacts or early adopters who self-identify as wanting to help. Make the ask explicit: "You've been contributing for 6 months and clearly know what you're doing. Would you be willing to mentor new observers?" Personal asks are more effective than open calls.

Part 5: Recognition and Incentive Architecture¶

Milestone Structure¶

The following milestones should generate an automatic notification to the observer (email or Discord DM) and be visible on their profile:

Milestone	Name	Action Triggered
First accepted observation	First Light	Welcome DM, profile update
10 observations	Consistent Observer	Profile badge
First time-critical event contribution	Event Responder	Personal email from lead scientist
50 observations	Active Observer	Profile update, newsletter mention
First co-authorship threshold crossed	Collaborating Scientist	Personal email confirming co-author status
100 observations	Century Observer	Leaderboard entry
200 observations	Core Contributor	Named co-author status, profile highlight
500 observations	Network Pillar	Named acknowledgment in grant applications

Leaderboards¶

Leaderboards are a double-edged tool. They motivate the top ~10% of contributors and potentially demotivate casual contributors who see they will never rank highly. The solution is to scope leaderboards to specific timeframes and campaigns:

Monthly leaderboard: Resets monthly. Anyone can rank highly in a good month. Reduces demotivation.
Campaign leaderboard: Ranks contributors within a specific campaign. More meaningful than all-time totals.
All-time leaderboard: Exists for transparency and history but is not the primary display.

"Adopt-a-Target" Program¶

From the Roadmap in this vault: assign each observer as the "primary observer" for a specific target. This creates ownership. The observer gets a small profile element showing their target, and when that target appears in a paper, they are specifically credited as the primary observer.

This is implementable in Stage 2. It requires tracking in the scheduler (who is the primary observer for target X) and one extra sentence in the paper's data section ("Photometry of [target] was led by [observer name], primary observer for this target in the OpenAstro network").

Part 6: Online Presence Strategy¶

What to Build and When¶

Before Stage 1 is complete: - Static website (Hugo, Jekyll, or similar — nothing database-backed). Pages needed: About, Science, How to Join, FAQ, GitHub link. - SciStarter listing. - Discord server (invite-only until Stage 2). - arXiv author profile for the project.

At Stage 1 paper submission: - Make the GitHub repo public. - Post on Cloudy Nights. - Begin building the email list.

At Stage 2 launch (network live): - Add the live status map. - Add a Participants page listing current observers (with their permission). - Add a Publications page. - Make Discord public. - Begin monthly newsletter.

At Stage 3: - Add the hardware page showing owned nodes. - Consider a proper database-backed webapp for observer dashboards.

Content Calendar (Monthly Minimum)¶

Each month, produce: 1. One newsletter issue. 2. One Cloudy Nights thread update. 3. One substantive Discord announcement. 4. One social media post (Twitter/X) with a result or visualization.

If capacity allows, also produce: 5. One YouTube/video short of a light curve or result visualization. 6. One IceInSpace forum update. 7. One blog post on the project website.

The content calendar should be treated as a commitment, not optional. Silence is interpreted as project abandonment.

Part 7: Preventing Common Failure Modes¶

Failure Mode 1: The "Undead Project"¶

Symptoms: Irregular updates, no clear status on whether the project is active, unanswered questions in forums and Discord.

Prevention: The monthly newsletter and monthly forum update are non-negotiable commitments. Even if there is nothing to report, report that nothing is happening and why. Transparency about slow periods is better than silence.

Failure Mode 2: The "No Feedback" Death Spiral¶

Symptoms: Observers submit data, hear nothing, stop submitting.

Prevention: The automated feedback loop (Level 1-5 above) is engineering infrastructure, not a nice-to-have feature. It should be built before the network goes live.

Failure Mode 3: The "Too Technical to Join" Barrier¶

Symptoms: Interested observers who have read about the project but never submit a first observation.

Prevention: "Getting Started in 30 Minutes" as a document and potentially a video. A real human available on Discord to help with setup. The PANOPTES unit model (hardware is provided) eliminates this for owned hardware but the software client must also be trivially installable.

Failure Mode 4: "The Founder Is the Community"¶

Symptoms: Everything depends on the founder being available. Community cannot function if they're busy.

Prevention: Identify and empower community managers early. These are active observers who are given moderator permissions, included in decisions, and publicly identified as part of the team. At minimum, one person other than the founder should be able to run the Discord, send the newsletter, and answer forum questions.

Failure Mode 5: "Moving Goalposts on Authorship"¶

Symptoms: Authorship criteria change after observers have already contributed. Retroactive rule changes.

Prevention: The written co-authorship policy (see Marketing Strategy doc) is versioned. Any change to criteria applies only to contributions made after the change date, never retroactively. This is both fair and standard practice in large collaborations.

Part 8: International Community Considerations¶

OpenAstro's scientific value is inherently geographic — different longitudes matter. This means the community must be international from the start, not US/UK-centric with international participants added later.

Language: English is the working language but onboarding documentation should eventually be translated to Spanish, German, and French (which covers the majority of the European and South American amateur astronomy communities). Community members who speak these languages natively should be invited to contribute translations. This is a Stage 2 task.

Time zones: Discord observing channels ("observing-tonight") should note the UTC offset explicitly. Campaigns and alerts should always display times in UTC.

Geographic priorities: Stage 2 should specifically target observers in the following underserved longitudes for typical Northern Hemisphere networks: - Southern South America (Chile, Argentina) — critical for occultation coverage - East Africa / Middle East — underrepresented in most networks - Southeast Asia (India, Thailand, Australia) — sparse but improving - Southern Africa — underrepresented

Specific outreach for these regions: IceInSpace for Australia, BAA and Cloudy Nights have Indian and South African subpopulations, the Indian Planetary Society (https://www.goa.gov.in/ips) for India, and the Astronomical Society of Southern Africa (https://assa.saao.ac.za) for South Africa.

Part 9: Recruitment Mechanics — Full Detail (from `Logistics and Marketing/Getting people.md`)¶

This section consolidates the detailed recruitment research from the Logistics and Marketing folder.

Target Market Size¶

Segment	Estimated Numbers	Notes
Amateur astronomers worldwide	~1,000,000	IAU estimate
Active US telescope users	100,000–300,000
US astronomy clubs	600+	Average 30–100 members each
Cloudy Nights registered users	190,000+	World's largest astronomy forum
AAVSO members	2,000+, 108 countries	23M+ observations on record
ExoClock participants	280+	Grew from 140 in 7 months

Realistic first-year target: 20–50 active contributors.

Recruitment Channel Tiers¶

Tier 1 (highest conversion): - Cloudy Nights "Amateur Contributions to Science" subforum - AAVSO community — pre-qualified audience already doing variable star photometry - Direct outreach to astronomy clubs (600+ in US alone) — offer 20-minute virtual presentation

Tier 2 (medium conversion): - Reddit: r/astrophotography (1.4M), r/telescopes (215K), r/Astronomy (2.5M) - University astronomy departments with teaching observatories (10–20" scopes) - Twitter/X astronomy community — 6+ month time investment to build following

Tier 3 (longer-term): - Conferences: SAS annual meeting, AAVSO meetings, Texas/Oregon Star Party - YouTube tutorials on photometry (4–10 hrs/video investment) - SciStarter.org, Zooniverse, NASA Citizen Science listings

Value Propositions by Audience¶

For experienced imagers: "You've mastered pretty pictures. Ready for real science? Same equipment, different purpose, real impact."

For equipment-rich, time-poor: "Instead of wondering what to image, get assigned a target that matters. 15 minutes of observation = contribution to real science."

For beginners: "You don't need a PhD to do astronomy research. We'll teach you the techniques. You provide the clear nights."

Milestone Badge System¶

First Light       — First observation submitted
Night Owl         — 10 observations
Century Club      — 100 observations
Longitude Coverage — Observed from 3+ time zones
Event Hunter      — Caught a time-critical event
Published         — Contributed to a peer-reviewed paper

Anti-Patterns (What Kills Projects)¶

Spray-and-pray forum posting simultaneously — results in ban, reputation damage
Leading with technical specs — people disengage
Over-promising ("discover exoplanets from your backyard!") — disappointed users
Silent periods after signup — people assume the project is dead
Ignoring support requests >48 hours — "this project is abandoned"
Guilt-tripping ("we need more observations!") — resentment and unsubscribes

Growth Timeline Benchmarks¶

Month 1–6: 10–20 active observers (personal contacts, 1–2 forum posts, 3–5 club presentations)
Month 7–12: 50+ active observers (AAVSO partnership, first paper submitted)
Year 2+: 200+ observers (word-of-mouth, press coverage from discoveries, institutional partnerships)

ExoClock took 3 years to reach 300+ participants. AAVSO took 100+ years to reach 2,000 members. OpenAstro will not have 500 observers in Year 1. The question is whether the network is scientifically valuable with 20–50 committed observers — if yes, the network effect kicks in once publications start appearing.

Teammates Needed¶

Database manager
Website / front-end manager
Outreach and participant support
Science lead (professional collaborator or experienced amateur)

Finding teammates: Open-source (GitHub), Build in Public (Twitter/IndieHackers), niche Discord servers / r/cofounder. Reduce documentation barrier — strangers need to understand how to help within 5 minutes of reading the repo.