[HCoop-Discuss] .coop tld?

[leitgebj at hcoop.net]

Welcome to the list, Ketty!

I wrote to the list a few months ago in support of moving to a .coop TLD. 
Some of the same issues with cost were brought up at that time, as well as
the fact that our legal name is HCoop, Inc.

Despite these concerns, I think that the benefits of moving to a name like
hosting.coop would offset the disadvantages.  Specifically, I like the
facts that: it would be easier to relay in communication, it emphasizes
what we do (i.e., hosting), and that it emphasizes our established
organizational status as a cooperative.

Along with the benefits mentioned above, I also think that it would help
to strengthen relationships to other cooperatives who have already jumped
on the .coop bandwagon such as my local grocery store, the  The Lexington
Real Foods Community Co-op (http://www.lexington.coop).

I think that we should do it in conjunction with the server move if at all
possible.  Let me know if I can help out in any way, e.g., by filling out
the necessary paperwork.

Justin


> Hi, this is my first time posting here :)
>
> On 10/15/06, David W. Bettis <dwb at hcoop.net> wrote:
>>
>> When we get our new server setup, having hosting.coop might increase our
>> visibility.  I've been using "hcoop.net" as the domain for my email
>> address, and when I write it down for people, most of them say "what?  h
>> coop?" (as in a bird coop).  Hosting.coop would stick in people's minds
>> better.  Moreover, what if -another- hosting.coop comes along?  That
>> would be confusing.
>
>
> Another posibility is webhost.coop, that would be even more self
> explanatory
> :)
>
> Since we have more members now, it wouldn't be quite as painful to cough
>> up $100/yr.  That's what, $1 or $2 extra per member per year?
>
>
> I too think it is reasonable.
> _______________________________________________
> HCoop-Discuss mailing list
> HCoop-Discuss at hcoop.net
> http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-discuss
>