Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] General assembly of the Buildroot Association
Date: Wed, 11 Jan 2023 23:03:29 +0100	[thread overview]
Message-ID: <20230111230329.5f68a75b@windsurf> (raw)

Hello,

As a president of the Buildroot Association, the legal entity set up in
France that supports the Buildroot project, I would like to announce
that the next General Assembly of the Buildroot Association will take
place on February 6, 2023 at 4 PM UTC+1.

The General Assembly will take place during the Buildroot Developers
Meeting, and therefore the physical meeting will take place at The
Nestwork, Avenue de Broqueville, 12, 1150 Bruxelles. Remote
participation will be possible through video-conferencing.

The agenda for the General Assembly is:

 - Presentation and approval of the moral report for 2022
 - Presentation and approval of the financial report for 2022
 - Election of the Buildroot Association board
 - Discussion on the next actions of the Buildroot Association

Voting rights are granted to people who are members of the association,
with a membership up-to-date for 2023.

We can provide the moral report and financial report ahead of the
General Assembly to anyone who requests them. Please note that due to
the Buildroot Association being legally installed in France, those
documents are in French.

Let us know if you have any question.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

                 reply	other threads:[~2023-01-11 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230111230329.5f68a75b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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