Support Articles
Start with the knowledge base for practical guidance and known procedures:
youtrack.reeflogic.org/projects/SUP/articles
Support and Communication
This page explains where to request technical support for deployed ReefLogic instances, how to subscribe to news emails, and how to join the ReefLogic community and development mailing lists.
Support and Helpdesk
Use the ReefLogic YouTrack support project for technical incidents and support requests. For how-to questions, check the support articles first to get faster answers.
Start with the knowledge base for practical guidance and known procedures:
youtrack.reeflogic.org/projects/SUP/articles
Search existing issues, view status, comment, or create a new technical ticket:
youtrack.reeflogic.org/projects/SUP/tickets
Add clear steps, expected result, actual result, screenshots, and timestamp. This makes triage faster and avoids back-and-forth.
Read the project direction and phased development overview:
ReefLogic Development Plan
News Email List
ReefLogic news is managed on the public list service and provides project updates, roadmap highlights, and important announcements.
Go to the registration form and enter your email address. Name is optional.
Send the form. Your request will stay pending until you confirm ownership of the email address.
Open the confirmation email and click the confirmation link to activate your subscription.
You will receive new announcements, and each email includes a direct unsubscribe link.
Open any ReefLogic news email and click the unsubscribe link in the footer. Then confirm the unsubscribe request.
If you unsubscribe by mistake, use the same registration form again and confirm from the new confirmation email.
If the confirmation email does not appear quickly, check your junk or spam folder. Low-volume domains are sometimes filtered by Outlook and similar providers.
Community Mailing Lists
ReefLogic uses Mailman with Postorius for web subscription/management and HyperKitty for searchable archives. Choose the list that matches your topic.
Best for field usage, deployment feedback, configuration practices, stories/photos, and feature suggestions from operational teams.
Join with browser: users.lists.reeflogic.org.
Join by email (optional): send to
users-join [at] lists.reeflogic.org
with subject subscribe.
Contact list owners: users-owner [at] lists.reeflogic.org.
Best for API questions, code-level issues, integrations, architecture discussions, and release coordination.
Join with browser: devel.lists.reeflogic.org.
Join by email (optional): send to
devel-join [at] lists.reeflogic.org
with subject subscribe.
Contact list owners: devel-owner [at] lists.reeflogic.org.
Read previous discussions in HyperKitty: lists.reeflogic.org/hyperkitty/.
Use Postorius list pages to subscribe/unsubscribe, update password, and manage delivery or digest preferences.
Use support tickets for deployed-instance incidents. Use mailing lists for best practices, usage questions, and collaboration.
Mailing List 101
Mailing lists require confirmation to protect users and prevent abuse. You confirm both subscription and unsubscribe actions.
Use the Postorius list page or send a subscribe email command to a list join address.
Open the confirmation email and follow the confirmation link or reply instruction.
After joining, use Postorius or email footer links to update delivery mode, digest options, and account settings.
Use the unsubscribe link in any list email or the list page, then confirm removal when prompted.
Send subject subscribe to the list join address to start the signup process.
Send subject unsubscribe to start list removal, or use the unsubscribe footer link in list emails.
Send subject help to request available command instructions if command mode is enabled on that list.
If confirmation does not arrive, check junk or spam. Low-volume sender domains can be filtered by Outlook and similar providers.
List email addresses are displayed in a protected format and converted to mail links only when you click. This reduces basic address scraping while keeping the workflow simple for users.
For Developers
Developers, contributors, and integrators can request access by contacting the list owners with a short introduction and your use case.
Include your name, organization, intended contribution area, integration scope, and expected repository access level so maintainers can route your request quickly.
FAQ
Support tickets should stay focused on technical requests for deployed instances. Use support articles and mailing lists for general how-to discussions.
Addresses are shown in protected format and converted into mail actions only when clicked, reducing simple harvesting by basic scrapers.
Use the public archive page or RSS feed to browse and follow updates.
Use the technical development list and contact devel-owner for contributor onboarding.