Community Bug Bash for Smoke Signal Preview, July 10th, 2025

Smoke Signal’s one year anniversary is coming up, and with it comes the release of the new Smoke Signal website!

We need your help to identify issues with the new Smoke Signal web application, and invite you to participate in this community bug squash event!

On Thursday, July 10th between 4:00 PM and 10:00 PM Eastern, use the https://preview.smokesignal.events/ website and report any bugs you see. Your participation can be simply logging in and browsing the site, or it can be creating and RSVP’ing to events.

Here are some suggestions:

  1. Login and set your timezone, language, and email settings.
  2. Create an event for a public event in your area. Set the start and end time, and if there is a location, set that too!
  3. RSVP “Going”, “Interested”, or “Not Interested” to an event.
  4. RSVP to an event and share your email address with the event organizer.
  5. Click around on the site and find any broken links or unhelpful help content.

If you do find a bug, report it at Site Feedback and be sure to include what you were doing that lead to the issue to help track and resolve it.

You can start by RSVP’ing to the Bug Bash event on the Preview site:

1 Like

One of the major changes is the migration of the old lexicon to the Lexicon Community Calendar lexicon for event and RSVP records.

All legacy records will need to be migrated using the “import” tool. During this bug bash, it would be extremely helpful for people who have previously created events to go through the import process and report any issues migrating events.

  1. Log into https://preview.smokesignal.events/
  2. Go to your profile page via the big blue “Your Profile” button in the top right
  3. Click the green outlined “Import Records” button under your handle.
  4. Click the blue “Start Import” button
  5. Proceed clicking the continue / complete import buttons until you can’t

If you run into an issue or if a record isn’t imported correctly, create a new topic in the Smoke Signal Feedback category:

  1. Have “import failed” in the subject
  2. Add the labels “bug-bash” and “import”
  3. Described where you were in the migration process
  4. Include any AT-URIs for failed imports (if you have them)

Here’s an example: Import failed (an example)