In <x44qa89n2v(_dot_)fsf(_at_)footbone(_dot_)schlitt(_dot_)net> wayne
<wayne(_at_)schlitt(_dot_)net> writes:
Motion: I move that if the transfer of the openspf.org domain has not
started by this coming Friday, Aug 5, that we give up on it.
Ok. The motion passed, and the deadline has expired. I still haven't
heard anything from James.
As far as I'm concerned, we can move on. I understand that some
people are still working on trying to get James to deliver on his
promises, and if they do, fine, if they don't fine. I see no reason
to even worry about what happens or waste any more time on the
subject.
I, for one, will assume that openspf.org will be unlikely to
immediately fall into the wrong hands, but who knows about a few years
down the road. I don't want to end up in the same situation with
spamcop.net and spamcop.com, where spamcop.com was originally
controlled by a friendly party, but now is controlled by, well, no one
is really sure who controls spamcop.com.
Discussion: If we are forced to give up on openspf.org, should we
a) go with something like openspf.net or openspf.info?
I would like to suggest that maybe we can go with something like
open-spf.net. We have all of the open-spf.{org,net,com,info} domains,
so people would need to make *two* typos to get to openspf.org. Think
this would satisfy the desire by most people to select from the top
vote getter, but also the desire to have a well protected domain name.
b) go with the runner-up, spf-classic.org?
This is always an option. Some people feel strongly that it should be
chosen, others feel strongly that it shouldn't. Personally, I think
the short term advantages of the spf-classic brand outweigh the long
term problems with "what if we release a new version of SPF?" By
then, we may have control over openspf.org. Having both Mozilla.org and
getfirefox.org seem to be acceptable to most people, I don't see why
spf-classic.org now, and later <new-brand>.org in the future.
What do people think?