From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Add IPFire to Discourse Discover?
Date: Thu, 20 Jun 2024 09:26:46 +0100 [thread overview]
Message-ID: <0255FB46-BA66-459B-B5F6-D2CDA38BB78F@ipfire.org> (raw)
In-Reply-To: <26762E1F-39BB-409C-8262-B8AC152586C1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
Great idea! I have turned it on…
> On 20 Jun 2024, at 00:58, jon <jon.murphy(a)ipfire.org> wrote:
>
> Michael, et al.,
>
> Could you, would you, add the IPFire Community to Discourse Discover?
>
> A little advertisement on Discourse might help with new members!
>
>
> Jon
>
> ---
>
> https://discover.discourse.org/
>
>
> Discover FAQs
>
> Discourse Discover is a directory of communities built using the open-source Discourse discussion platform. You can start your own community using our official hosting, or install it yourself!
>
>
> How do I get my community listed?
> To submit your Discourse community, it must be publicly accessible and have the admin setting "include in discourse discover" enabled.
>
> We will not approve any communities displaying content we find objectionable. This includes anything that is illegal, discriminatory, or inappropriate for a general audience in a public space.
>
> Appearing in Discourse Discover is at the discretion of the Discourse team.
>
>
> What data is my community sharing?
> The include in discourse discover site setting collects basic statistics from your community's /about page, as well as its:
>
> url
> title
> language
> logo
>
>
> My community is in the wrong category, how do I fix it?
> Discourse Discover is reviewed and categorized by the Discourse team. You can request changes by sending a message to team(a)discourse.org.
>
>
> How do I contact you?
> If you have a question that's not answered here, feel free to send a message to team(a)discourse.org.
>
parent reply other threads:[~2024-06-20 8:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <26762E1F-39BB-409C-8262-B8AC152586C1@ipfire.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0255FB46-BA66-459B-B5F6-D2CDA38BB78F@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox