Commit graph

33 commits

Author SHA1 Message Date
965535133d
📝 docs(AGENTS): Document 50/72 Git commit rule
Add the 50/72 rule to the Git conventions section of `AGENTS.md`. This
guideline establishes that commit subjects must not exceed 50 characters
for conciseness and clarity, while commit body lines must not exceed 72
characters to maintain readability in terminal pagers and git log views.

Assisted-by: gemini-3.8-flash (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-09-11 16:01:31 -04:00
587b71bbf3
📝 docs(AGENTS): Align with current repository and project memory
Update `AGENTS.md` to incorporate institutional knowledge and
conventions established across the Flock 2026 planning cycle. Add
explicit repository writing conventions contrasting one-sentence-per-
line prose for documentation with flowing paragraphs for Forgejo issue
comments. Document pre-event venue capacity messaging principles,
Forgejo Projects API limitations, and issue consolidation workflows.
Expand key platform references to include design tickets and the photo
gallery, and record the upcoming Fedora Community Architect transition.

Assisted-by: gemini-3.8-flash (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-09-11 15:54:08 -04:00
53473711ea
📝 survey(2027): Make session rating question non-mandatory
Address feedback from @py0xc3 about G2Q02 ("Rate each type of session
from 1-5"). The question previously forced all in-person attendees to
rate every session type, including ones they did not attend (e.g.,
workshops, BoFs, social events). This created a false choice: either
give a misleading rating or abandon the survey entirely.

Making the question non-mandatory and adding help text ("Rate only the
session types you attended. Leave blank any you did not attend.") allows
respondents to skip session types they did not experience, improving
data quality by eliminating forced ratings that do not reflect actual
attendance.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-29 17:56:39 -04:00
bccc374cd4
✨ gallery: Add pagination and floating navigation
Replace the all-at-once thumbnail grid with JS-driven pagination showing
24 photos per page (6x4 grid), based on feedback from @glb on issue #83.
This reduces initial load from 643 simultaneous image requests to 24,
significantly improving page load time.

Key changes:
- Floating prev/next buttons in the side margins for page navigation
- Day headers appear inline when crossing day boundaries within a page
- Compact page counter with ellipsis (first, last, and 2 pages around
  current)
- Day nav in the header jumps to the page where that day starts
- Arrow keys navigate pages when the lightbox is closed
- File size reduced from 182KB to 68KB by replacing 643 hardcoded
  gallery-item elements with dynamic JS rendering

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 23:18:42 -04:00
c37e144344
📝 survey(2027): Normalize 2024 Rochester location format in G1Q03
Add "USA" to the 2024 attendance history option to match the format used
by the 2015 entry: "Rochester, New York, USA".

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:56:50 -04:00
44b6a954e5
🐛 survey(2027): Move G1Q01 "Other" option to end of list
The "Other" option for question G1Q01 ("What are your current role(s) in
Fedora Project?") was positioned at the beginning of the answer list,
appearing before all standard choices. Move it to the end where
respondents expect to find it.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:53:51 -04:00
f9be49ab68
🔧 survey(2027): Make virtual and non-attendance exclusive in G1Q02
Set `exclude_all_others` to SQ002 (Virtual attendee) and SQ006 (Did not
attend) on question G1Q02. Selecting either of these options now
automatically unchecks and disables all other role selections, since
virtual-only attendance and non-attendance are mutually exclusive with
in-person roles like Speaker, Volunteer, and Organizer.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:49:36 -04:00
d51d19d725
📝 survey(2027): Add routing help text to G1Q02 participation question
Add help text explaining that the respondent's selections control which
survey sections they will see. This sets expectations upfront so
respondents understand why they are asked about their role and are not
surprised when different question groups appear based on their answers.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:47:18 -04:00
509de9be8f
🔧 survey(2027): Allow partial ranking for location & timing preferences
Configure G5Q01 (location) and G5Q02 (timing) to allow partial ranking
so respondents can rank only the options they care about. Unranked
options indicate no preference, which produces cleaner data than forcing
respondents to rank every item including ones they have no opinion on.

Changes per question: set `mandatory` to off, set `min_answers` to 1,
and add help text explaining not every item needs to be prioritized.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:45:05 -04:00
70f517da84
📝 survey(2027): Future-date Group 5 as "Future Changes"
Rename Group 5 from "2027 Changes" to "Future Changes" and reword all
year-specific references in the group description and questions to be
forward-looking. This makes the section reusable across years without
requiring year-specific edits, and avoids confusion since the survey
itself is for the 2027 event.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:38:29 -04:00
9f0a69d988
🔧 survey(2027): Make G1Q05 volunteer gateway question mandatory
The Yes/No volunteer gateway question must be mandatory so that all
respondents provide an answer, ensuring the Getting Involved section is
reliably shown or hidden based on their selection.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:36:11 -04:00
d3a4f989cc
📝 survey(2027): Update all text and settings from 2026 to 2027
Update all survey text, question wording, group descriptions, and
settings to reflect Flock 2027 instead of 2026:

- Survey title, alias, and description updated to 2027
- Group descriptions for In-Person Attendees and Speakers simplified to
  remove the 2026 Prague location and dates (TBD for 2027)
- Nine question texts updated from "Flock 2026" to "Flock 2027"
- Start date and expiration date cleared (TBD for 2027)
- Description changed from "influence 2027 planning" to "influence
  future planning" to stay generic

The SQ012 "2026 (Prague, Czechia)" attendance history option is
intentionally preserved — it records past attendance, not current.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:33:50 -04:00
5e0fca6772
🔧 survey(2027): Make "Getting Involved" questions mandatory
Set G6Q01 (volunteer interest), G6Q02 (organizing roles), and G6Q04
(contact email) as mandatory questions. G6Q03 (FAS username) remains
optional since not all potential volunteers may have a Fedora Account.

These questions are only shown to respondents who select "Yes" on the
G1Q05 volunteer gateway, so the mandatory requirement only applies to
people who have already expressed interest in getting involved.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:25:58 -04:00
2d136c69eb
🔧 survey(2027): Add 2026 Prague to previous attendance history
Add SQ012 "2026 (Prague, Czechia)" to question G1Q03 ("Have you attended
previous in-person Flock to Fedora events?"), placed at the top of the
list above the existing 2025 entry. All subsequent subquestion display
orders were incremented by 1 to maintain correct sequential ordering
from newest to oldest.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:18:47 -04:00
f0acd617cf
🔧 survey(2027): Add volunteer gateway question to control G6 visibility
Add a Yes/No question G1Q05 ("Are you interested in volunteering for
Flock 2027?") to the Introduction section, placed after G1Q03. Set Group
6 ("Getting Involved") `grelevance` to (`(G1Q05.NAOK == "Y")`) so the
volunteering questions only appear for respondents who opt in.

This fixes the recurring issue from 2025 and 2026 where the Getting
Involved section was either hidden from everyone (broken condition
referencing a free-text field) or shown to everyone (condition removed
as a workaround). The new Yes/No gateway provides the intended
conditional behavior with a question type that LimeSurvey can reliably
evaluate.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:11:33 -04:00
f5e7eddf42
🔧 survey(2027): Set chart types for multiple statistics_graphtype
Choose appropriate chart types for six questions based on their data
characteristics:

- G2Q01 ("How valuable were the sessions?"): Bar → Pie. Single-select
  question where responses represent parts of a whole.
- G2Q35 ("Did you participate in Mentor Summit?"): Bar → Pie. Yes/No
  question, naturally a proportion.
- G5Q01 ("Where should Flock go?"): Pie → PolarArea. Ranked preference
  data across independent geographic options. Polar area charts show
  relative preference without implying false adjacency between locations.
- G5Q02 ("When should Flock be held?"): Pie → PolarArea. Same reasoning
  as G5Q01 — ranked preference across independent time options.
- G6Q01 ("Interested in volunteering?"): Bar → Pie. Simple selection
  between two volunteer teams.
- G6Q02 ("What organizing roles interest you?"): Bar → Pie. Small set
  of role categories best shown as proportions.

G1Q02, G1Q03, G2Q02, and G5Q03 are left as bar charts because they are
multiple-choice "check all that apply" questions whose values do not
sum to a whole.

LimeSurvey `statistics_graphtype` codes:

* 0=Bar
* 1=Pie
* 2=Radar
* 3=Line
* 4=PolarArea
* 5=Doughnut

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 22:05:48 -04:00
be0e3796ef
🔧 survey(2027): Add photographer and CfP reviewer volunteer roles
Add two new answer choices to question G6Q02 ("What type of event
organizing roles are most interesting to you?") in the Getting Involved
section: SQ004 "Event photographer" and SQ005 "Call for Proposals
reviewer". Both are placed after the existing SQ003 ("Event support").

These roles reflect specific volunteer needs identified during Flock
2026 planning — photo collection required ad-hoc coordination, and CfP
review benefits from a broader pool of committed reviewers.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 21:53:08 -04:00
f3feabaec4
📝 AGENTS: Add LimeSurvey .lss editing guide & repo structure updates
Document that LimeSurvey structure files must be edited surgically at
the text level, never through XML parsers, to keep git diffs readable.
Also add the 2027 survey and deploy script to repo structure listing.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 21:48:51 -04:00
da47219e6b
🔧 survey(2027): Add "nearby location" option to attendance barriers Q
Add SQ005 "A more convenient and nearby location" as a new answer choice
for question G4Q03 ("What types of support would make it more likely for
you to attend in person?"). This option appears after SQ004 ("Quality of
programming/content") and captures geographic proximity as a factor in
attendance decisions, which is relevant data for choosing future Flock
locations.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 21:47:40 -04:00
04562a44c4
🔧 survey(2027): Simplify timezone question to UTC offsets
Replace the 102 IANA timezone options in question `G1Q34` with 31 UTC
offset options, each listing recognizable example cities. This change
improves data quality by eliminating duplicative entries that map to the
same offset, and avoids collecting specific location data that could
expose a respondent's city.

Offsets are calibrated to the June-August survey window (DST-aware), so
respondents see the UTC offset that matches their actual clock during
that period. For example, New York appears under UTC-4 (EDT) rather than
UTC-5 (EST).

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 21:37:34 -04:00
64fa235bb2
🍴 survey: Fork Flock 2026 survey structure as 2027 baseline
Add the unmodified Flock 2026 LimeSurvey structure as the starting point
for the Flock 2027 post-event survey. Committing the 2026 structure
first under `survey/2027/` establishes a clean baseline so that
subsequent edits to the 2027 survey are visible as diffs against the
original.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 20:58:41 -04:00
9a6d6db49b
📝 scripts: Add Flock 2026 gallery deployment script for Fedora People
Add a simple SCP-based script to deploy the Flock 2026 photo gallery to
jflory7.fedorapeople.org. Automated deployment via cron was not possible
because PAM restricts crontab access on the fedorapeople.org server, so
this script provides a lightweight manual alternative.

The script resolves the gallery file relative to the repo root, ensures
the remote directory exists, and copies the file over SSH. The remote
user is configurable via `REMOTE_USER` for other contributors' accounts.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 20:54:48 -04:00
ffd5252fe8
🤖 AGENTS: Add AI agent guidance for repository workflows
Create an `AGENTS.md` file following the https://agents.md convention to
guide AI coding agents working on this repository as a project
management tool.

The file covers the Forgejo REST API (authentication, endpoints,
pagination, known limitations), issue tracker conventions (the Summary-
Background-Details-Outcome template, label taxonomy, milestone
structure), comment authoring rules (first-person voice, flowing prose,
approval workflow), confidentiality guidelines, Fedora terminology
(OSAIPO, FOA, FCA, FPL), git commit conventions with a real example from
the repo log, and links to key platforms (Pretalx, Pretix, LimeSurvey).

This complements the `README.md` (which is aimed at human planners) with
agent-specific guidance that would otherwise clutter the README or need
to be rediscovered each session.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 20:37:04 -04:00
80635225db
📝 README: Post-event accuracy updates and new resources
Update the README to reflect the current post-event state of Flock 2026:

- Fix tense: "will be held" → "was held" (the event is complete)
- Mark the June 14-16: Event milestone as Closed
- Add photo gallery, survey archives, and AGENTS.md to "What lives here"
- Add post-event resources to "What lives elsewhere": the deployed photo
  gallery, community Google Photos album, and post-event survey link

These are factual corrections to keep the README accurate as the
repository transitions from active event planning to post-event
follow-up work.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 20:34:56 -04:00
f6424f1e78
📦 survey: Reorganize survey archives and add Flock 2025 structure
Move the Flock 2026 LimeSurvey structure export from the repo root into
a year-based directory structure under `survey/2026/`, and add the Flock
2025 survey structure at `survey/2025/`. This organization makes it
easier to compare survey designs across years and provides a reusable
reference for future editions.

The Flock 2026 survey structure also includes the fix for the Section 6
"Getting Involved" relevance condition bug, which was broken in both
2025 and 2026 due to a free-text question being referenced with a radio-
button value.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-26 20:33:50 -04:00
2515461dce
✨ gallery: Add Flock 2026 photo gallery page
Create a self-contained HTML photo gallery for the 643 community photos
from Flock to Fedora 2026. The gallery is hosted on Fedora People at
jflory7.fedorapeople.org/flock-2026-gallery/ as a shareable, Google-free
alternative to the community Google Photos album.

The page is a single `index.html` with all CSS and JS inline — no build
step, no server-side dependencies. Photos are loaded directly from the
existing upload directory on the same server. Key features:

- 3-day chronological grouping (EXIF-verified dates for all 643 photos)
- Responsive thumbnail grid with lazy loading
- Lightbox viewer with keyboard navigation and loading transitions
- Sticky header with day navigation that compacts on scroll
- Active section highlighting as the user scrolls
- OpenGraph and Twitter Card metadata for rich social sharing previews
- Fedora brand theming (Montserrat/Open Sans typography, Fedora Blue
  palette from the 2024 Brand Guidelines)

HEIC files (21) and 1 MP4 video are excluded from the gallery grid since
browsers cannot render HEIC in <img> tags. The footer links to the raw
photos directory for access to these originals.

This gallery supports issue council/flock#83 (Publish event photos).

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-25 23:35:07 -04:00
ef9311bee7
📦 survey: Add Flock 2026 LimeSurvey structure export
Add a full LimeSurvey survey structure file (`.lss`) for the Flock 2026
post-event feedback survey. This XML export captures all 35 questions
across 6 sections, including conditional routing logic, answer options,
and question attributes.

The survey is live at fedoraproject.limequery.com/flock-2026 and covers:
Introduction (routing), In-Person Attendees, Speakers, Online Attendees,
2027 Changes (location/timing rankings), and Getting Involved.

This export includes a fix for a recurring bug from 2025 where Section 6
("Getting Involved") was hidden from all respondents due to a broken
relevance condition that referenced a free-text question with a radio-
button value. The condition has been removed so the section is now
always shown.

Committing the `.lss` file provides a reusable reference for future
survey iterations and ensures the structure is discoverable alongside
the issue tracker documentation (see council/flock#82).

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-20 17:10:00 -04:00
833218406d
📝 README: Post-event updates for Flock 2026
Flock 2026 (June 14-16, Prague) is now complete. This commit updates the
`README.md` to reflect the post-event state of the project, by adding
information that was confirmed during the event planning cycle from
April through June 2026.

Key changes:
- Confirm sponsor dinner date as Saturday, 13 June (previously TBD)
- Add @amoloney (Fedora Operations Architect) to the planning team,
  recognizing her significant contributions to volunteer coordination,
  speaker communications, and on-site operations
- Update Design Team link from the old GitLab epic to the new Forgejo
  tickets repository, reflecting the team's migration to Fedora Forge
- Add the complete Flock 2026 sponsor roster by tier (11 sponsors across
  Gold, Silver, and Bronze)
- Update the milestones table with current status (3 closed, 2 open)
- Remove the "slipped; in progress" annotation from the schedule
  publication date, as the schedule was published in May

These updates were deferred until after the event to avoid mid-planning
churn in the `README.md`. Post-event follow-up work (survey, recordings,
retrospective, budget reconciliation) continues to be tracked in the
issue tracker under the Post-Event milestone.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-06-19 22:44:04 +02:00
77d95f70ae
🔧 README: Fix venue URL, sponsor dinner date, and schedule status
Three accuracy corrections identified during a documentation review:

1. The venue changed ownership from Wyndham to Orea Hotels in January
   2026. Updated the link to the working orea.cz URL and noted the
   former name for continuity with existing contracts and references.

2. The sponsor dinner was listed on Day 2 (Tuesday) as if confirmed, but
   the April 8 planning call revealed a miscommunication about Tuesday
   vs. Sunday. Moved it out of the schedule table into a separate TBD
   line until the team confirms the date asynchronously.

3. The "Publish initial schedule" milestone (Mar 23-27) has slipped.
   Annotated the timeline to reflect current reality rather than the
   original plan, since the schedule is still being finalized as of
   April 9.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-04-09 02:09:25 -04:00
1fe035c72d
👥 README: Add Ananya Nalavathu to planning team
Ananya Nalavathu was introduced at the April 8 planning call as the
newest Marketing and Community Intern in OSAIPO, reporting to Jason,
Justin, and Shaun. She will assist with content and promotion for Flock
and is based in Cork, Ireland, which is beneficial for coordination with
European team members.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-04-09 01:55:26 -04:00
728a70638f
👥 README: Replace planning team table with RASCI-based matrix
The previous planning team section was a simplified role/lead table that
did not accurately reflect the division of labor. Several
responsibilities were misattributed or missing entirely (e.g., Lidija's
role in sponsor contracting, Jason's AV oversight, Shaun's broad
accountability scope across most workstreams).

This replaces it with three subsections derived from the team's RASCI
matrix: a team members table (with affiliations and focus areas), a 33-
row responsibility-by-workstream table showing Responsible and
Accountable parties for every deliverable, and the existing comms
channels. Items flagged "discussion needed" in the RASCI are preserved
as-is. Affiliations corrected to use OSAIPO (Open Source & AI Program
Office) throughout.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-04-09 00:36:05 -04:00
323f6acaf0
📝 README: Add comprehensive Flock 2026 planning guide
Establishes the README as the central reference document for the Flock
to Fedora 2026 planning effort. This was drafted after reviewing the
full history of bi-weekly planning call notes (Aug 2025 -- Apr 2026),
the event checklist, timeline, and the 37 legacy Flock 2024 issues
migrated from GitLab.com.

The README covers the event overview (dates, venue, schedule, CfP
themes), the planning team and their role assignments, a complete guide
to the issue tracker's label taxonomy and milestones, the planning
timeline and its six phases, sponsorship information, and contribution
guidelines.

The label taxonomy documented here reflects a deliberate redesign: repo-
specific `area/*` labels (non-exclusive, for workstream tagging) and
`priority/*` labels (exclusive) complement the inherited org-level
labels from the Fedora Council organization on Forgejo. This replaces
the original flat label set carried over from GitLab.com.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-04-09 00:13:23 -04:00
55a315d0d9
📄 LICENSE: Add CC BY-SA 4.0 license text
The Flock planning repository contains event documentation, checklists,
and planning reference material that should be freely reusable by other
open source event organizers. CC BY-SA 4.0 aligns with the Fedora
Project's broader preference for Creative Commons licensing of non-code
content, and the ShareAlike clause ensures derivative planning resources
remain open.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
2026-04-09 00:12:30 -04:00