How to request another Fandom wiki be available on breezewiki.com:

1. Press the NEW POST button. It will open your email composer.
2. Write the name of the wiki in the subject line. (e.g. Fire Emblem)
3. Write a link to the wiki in your message. (e.g. fireemblem.fandom.com)
4. Send! It'll show up on this page.

If you are unable to send the email for whatever reason (e.g. the HTML warning) please re-send your message to my personal email: https://cadence.moe/contact

Welcome to the BreezeWiki discussions page!

#How to

You can read, submit, and reply using email, without having to sign up for an account on sourcehut. To get started, compose an email to ~cadence/breezewiki-discuss@lists.sr.ht.

#Reply etiquette

• Your email program will automatically quote the previous message. You must remove this quote before sending.
• Send your reply to the entire list. Use the "reply all" or "reply to list" feature - do not use regular "reply".

#Issues/Feature requests

Is the idea already mentioned here? Try using the search feature to find out!

• Summarise your idea in the email subject line.
• What URL did the problem/feature appear on?
• What did you do to make the problem happen?
• Does the same thing happen every time?

Thank you for improving the project!

#What happens next?

If your report is something that I can track as a specific action item, I'll display it on my todo list here.

Welcome to the CloudTube and NewLeaf mailing list!

#How to

You can read, submit, and reply using email, without having to sign up for an account on sourcehut. To get started, compose an email to ~cadence/tube-devel@lists.sr.ht.

#Reply etiquette

• Your email program will automatically quote the previous message. You must remove this quote before sending.
• Send your reply to the entire list. Use the "reply all" or "reply to list" feature - do not use regular "reply".

#Issues/Feature requests

Is the idea already listed on the plans page?

• Summarise your idea in the email subject line.
• What URL did the problem/feature appear on?
• What did you do to make the problem happen?
• Does the same thing happen every time?

Thank you for improving the project!

#Contributing code

If you need help learning how to send git patchsets to this list, please consult git-send-email.io.

If you don't want to use that guide, or you have problems with it, please just contact me and we'll work it out.

← Back to the main project page

Welcome to the Bibliogram development mailing list.

You can send patchsets here. For help with sending patchsets, see the documentation.

The address of this list is ~cadence/bibliogram-devel@lists.sr.ht.

← Back to the main project page

Welcome to the Bliz development mailing list.

You can send patchsets here. For help with sending patchsets, see the documentation.

The address of this list is ~cadence/bliz-devel@lists.sr.ht.

← Back to the main project page

Welcome to the Bibliogram announcements mailing list.

This is a low-volume list for important announcements relating to Bibliogram.

If you host Bibliogram, or you're interested in what's happening with it, you should subscribe here.

You may not reply to this list. If you'd like to interact back with the project, choose a link from the "navigation" section of the main project page.

← Back to the main project page

Welcome to the Bibliogram translation mailing list.

If you are a translator, you should subscribe to this list to receive an email when new strings are available that can be translated.

Please send completed translations to the development mailing list at ~cadence/bibliogram-devel@lists.sr.ht.

The address of this list is ~cadence/bibliogram-translate@lists.sr.ht. To subscribe to this list, press the blue subscribe button, then send the preset email. The address that you sent the email from will be subscribed, and you'll receive a confirmation immediately after subscribing.

Low-volume mailing list for announcements related to the tube project.

Discussion about Carbon for people who don't want to create accounts.

Send an email to ~cadence/carbon-discuss@lists.sr.ht with a subject and body. If it's an issue report or a feature request, I'll most likely copy it into Carbon's issues section.

#Email etiquette

Please check the plaintext email guide, or you may encounter problems sending.

When replying, please remove the quoted copy of the previous message from the bottom of your message, or that content will be be duplicated into the list.

Be sure to send your reply to the list as a whole rather than just the person who posted last. This is done with the "reply to list" or "reply all" feature - check by starting a reply, then looking at the prefilled list of addresses that the email would be sent to.

Low-volume mailing list for announcements related to the Bliz project.