All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/website: add page for the Buildroot Association
Date: Fri, 8 Feb 2019 08:53:34 +0100	[thread overview]
Message-ID: <20190208085334.7332651e@windsurf> (raw)
In-Reply-To: <f8b4c0fe-5cde-185d-6aaf-949c1c082f85@mind.be>

Hello,

Thanks for the review. I obviously agree on all points, except one
where I have a comment (not really a full disagreement).

On Fri, 8 Feb 2019 00:19:08 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:

> > diff --git a/docs/website/foundation.html b/docs/website/foundation.html
> > new file mode 100644
> > index 0000000000..c25eb42f96
> > --- /dev/null
> > +++ b/docs/website/foundation.html  
>                      ^^^^^^^^^^association + in other places

Actually, it was intentional to use the term "foundation" in as many
places as possible. Even if the french authorities rejected the legal
name "Buildroot Foundation", because "foundation" has a very specific
meaning in terms of legal entity in France, I thought "foundation" was
the english word that carried best what this organization was. Is
"association" really the proper word in english to describe a
not-for-profit legal entity ?

> > +	  <p>To become a member, an individual or a company simply has
> > +	  to pay its yearly membership. For an individual, the minimum  
> 
>  Should we mention somewhere that the board can veto that?

I don't think it's really needed. It's pretty common for
associations/foundations to have the possibility of vetoing
memberships, and it's a sufficiently rare event that it's probably not
worth mentioning on this page.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-02-08  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 22:09 [Buildroot] [PATCH] docs/website: add page for the Buildroot Association Thomas Petazzoni
2019-02-07 23:19 ` Arnout Vandecappelle
2019-02-08  7:53   ` Thomas Petazzoni [this message]
2019-02-08  9:05     ` Arnout Vandecappelle

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=20190208085334.7332651e@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.