From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: Reminder: Sign Up to our new Account System
Date: Tue, 10 Dec 2019 10:33:33 +0000 [thread overview]
Message-ID: <mailman.146.1575974047.775.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
Hello,
we have recently launched our new IPFire Community Portal [1] with that, we also launched our new account system at people.ipfire.org [2].
Some of you have already signed up there, but many of you didn't, yet.
To stay in touch with us and to keep updated on everything that happens inside the project, please sign up now:
https://people.ipfire.org/register
Your team from IPFire!
[1] https://blog.ipfire.org/post/the-new-ipfire-community-portal
[2] https://people.ipfire.org/
reply other threads:[~2019-12-10 10:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.146.1575974047.775.ipfire-announce@lists.ipfire.org \
--to=ipfire-announce@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