From: Daniel Ostrow <dostrow@gentoo.org>
To: Grant Goodyear <g2boojum@gentoo.org>
Cc: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] trademark protection
Date: Fri, 21 Oct 2005 15:31:01 -0400 [thread overview]
Message-ID: <1129923062.7867.27.camel@Memoria.anyarch.net> (raw)
In-Reply-To: <20051021192407.GJ11687@bmb24.uth.tmc.edu>
On Fri, 2005-10-21 at 14:24 -0500, Grant Goodyear wrote:
> Deedra,
> Could you check with our lawyers what it is that we actually need to
> do to protect the Gentoo® trademark? One question is do we need to add
> the ® mark to all of our ebuilds in our Copyright statement? The other
> (at least at the moment) is if there are things that we have to be
> careful not to refer to as "Gentoo foo"? Presumably Gentoo Linux,
> Gentoo BSD, etcetera should be reasonable, but what about "the Gentoo
> init/runscripts system"?
>
> Also, where are we on the copyright issue? Last I heard there was a
> tentative document being put forward, and I suggested that we make it
> available for comments from our devs, but I believe that it was not yet
> ready for public scrutiny at that time. Has anything changed there?
>
> Dostrow, any results from sifting through the various Delaware holding
> companies (or whatever those organizations are called that can act as an
> in-state presence for a corporation)?
I am awaiting literature from the few I selected...they are all pretty
much the same but some looked more seedy then others (just a general
feeling from the various websites). I also sent out a letter asking for
any bad stuff about the few I chose to Delaware's Better Business
Bureau. Once I get the stuff in the mail and I see what they have got
I'll send a note to the foundation.
The incorporation itself is going to cost somewhere between $200 and
$300 depending on what options we choose...with 1/3 to 1/2 of that cost
recurring every year. Some of these companies also offer other services
that I think we most likely don't need but would also add to the cost.
These are things like shared office space for corporate meetings and
such.
> Am I currently holding things up where shifting our banking to BofA is
> concerned? If so, please let me know, and I'll do my best to get that
> fixed.
>
> We just received our first $500 check, by the way. I haven't sent it
> off to Netbank yet, but I'll get that done shortly.
>
> We're currently running with the "proposed bylaws", but they've never
> been confirmed. Do we want a general, foundation-wide vote on accepting
> them? If so, does anybody want to propose changes first?
I'd like to see this put to a vote yes...I'm pretty comfortable with the
wording but I'd like the lawyers to give it a once-over if they haven't
already.
> Okay, that's my thoughts for the day.
>
> Best,
> g2boojum
--
Daniel Ostrow
Gentoo Foundation Board of Trustees
Gentoo/{PPC,PPC64,DevRel}
dostrow@gentoo.org
--
gentoo-trustees@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-21 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 19:24 [gentoo-trustees] trademark protection Grant Goodyear
2005-10-21 19:31 ` Daniel Ostrow [this message]
2005-10-21 19:33 ` Donnie Berkholz
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=1129923062.7867.27.camel@Memoria.anyarch.net \
--to=dostrow@gentoo.org \
--cc=g2boojum@gentoo.org \
--cc=gentoo-trustees@lists.gentoo.org \
/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