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.
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? Nathan Kennedy wrote: > .coop has come up on the list before. h.coop is not permissible. > hosting.coop was the top contender. However .coop domains are expensive > at $100 per year, and the consensus was to hold off. Besides, we are > established at hcoop.net (and HCoop, Inc. is our legal name as well, > hcoop.coop is kind of redundant), so having an additional .coop domain > name is perhaps somewhat unnecessary. > > David W. Bettis wrote: > >> I think there was discussion about this when we first decided to >> register a domain. The sticking point, I think, was whether we >> *legally* qualified as being a coop. NCBA membership was thrown about, >> but that's expensive. However, we might qualify for a .coop domain >> under "organizations that are committed to the seven cooperative >> principles". >> > We are legally qualified. Their standards are quite permissive, and in > any event we are officially recognized by the IRS as a tax-exempt > cooperative. > > I had looking into NCBA membership before, and the dues are a little > expensive for now. That is definitely something we should look into > when our revenue is higher. > > -ntk > > _______________________________________________ > HCoop-Discuss mailing list > [email protected] > http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-discuss > _______________________________________________ HCoop-Discuss mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-discuss
