From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth.org membership changes
Date: Mon, 18 Sep 2006 17:05:33 +0200 [thread overview]
Message-ID: <1158591933.25125.18.camel@localhost> (raw)
In-Reply-To: <450EAF18.3070404@xmission.com>
Hi Brad,
> I may have entered the discussion late, but I just got a reply from
> Lindsay Puett at bluetooth.org on why it seems we're being accidentally
> locked out of the bluetooth.org site.
>
> She says bluetooth.org is going to become a "complete member site" (I
> think she meant must-pay-to-use) and that public stuff is going to be on
> bluetooth.com.
actually it is not about paying, because the adopter membership is free.
The problem is that you need to be a legal entity to get the adopter
membership. This means that no individual person can actually get access
to the bluetooth.org website anymore. At the moment this also includes
the Bluetooth assigned numbers document. And this also includes my
account.
We would need to setup a non-profit organization to get access to draft
standards. If someone is volunteering to do so, I happy to help, but for
me it is too much paper work at the moment.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-09-18 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 14:37 [Bluez-devel] bluetooth.org membership changes Brad Midgley
2006-09-18 15:05 ` Marcel Holtmann [this message]
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=1158591933.25125.18.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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