From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-announce@lists.sourceforge.net>
Cc: bluez-users@lists.sourceforge.net, bluez-devel@lists.sourceforge.net
Subject: [BlueZ-Announce] Closing down the mailing lists at SourceForge
Date: Wed, 03 Sep 2008 17:49:56 +0200 [thread overview]
Message-ID: <1220456996.6714.46.camel@californication> (raw)
Hi Folks,
the infrastructure of the BlueZ project has been undergone significant
changes to accommodate the developers needs. This also results in the
fact that the service providing by SourceForge is not really good enough
for us anymore.
The first big step was to finally switch away from CVS as source code
management system. It was clear that I will not switch to Subversion
since that is as broken as CVS. The only real alternative was GIT. So
starting with the bluez-4.0 release everything has been switched over. I
also decided to move the whole repositories over to kernel.org since
their infrastructure is excellent and works very well.
The next step was to move the download repositories over to kernel.org
since they do a really great job at mirroring and have good enough
bandwidth.
The last step is to close down the mailing list served by SourceForge. I
was always disappointed with their email service. It was slow, full of
spam and sometimes broken for days. I simply don't believe in having
subscriber only mailing lists. This is not how open source should be
done. Some time ago we created linux-bluetooth@vger.kernel.org since the
mail admins at kernel.org really know what they are doing. We are
already using this for the kernel development and in the future this
will become the only mailing list.
So it is a good idea to subscribe to linux-bluetooth@vger.kernel.org as
soon as possible since the SourceForge mailing lists will close down end
of the year.
The announcement mailing list has been quiet for some time now. With the
new www.bluez.org website we do have a proper RSS enabled blog. Please
use that one if you wanna stay up-to-date with releases and other
important information.
For everybody who was subscribed to the commit mailing list, you can now
also use RSS from the GIT web interface on kernel.org.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BlueZ-Announce mailing list
BlueZ-Announce@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-announce
next reply other threads:[~2008-09-03 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 15:49 Marcel Holtmann [this message]
2008-09-04 6:11 ` [BlueZ-Announce] Closing down the mailing lists at SourceForge James Cloos
2008-09-09 0:29 ` [Bluez-devel] " Bastien Nocera
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=1220456996.6714.46.camel@californication \
--to=marcel@holtmann.org \
--cc=bluez-announce@lists.sourceforge.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-users@lists.sourceforge.net \
/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