public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Philip Balister" <philip@balister.org>
To: Paul Barker <paul@pbarker.dev>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [FOSDEM standholders] FOSDEM 2022 stands - an update
Date: Wed, 22 Dec 2021 11:20:27 -0500	[thread overview]
Message-ID: <49ecafcf-1616-81ef-28c7-106cb7e2735b@balister.org> (raw)
In-Reply-To: <4ec5d14d-577b-dc3c-54ca-b02035d72620@pbarker.dev>

Thanks for all the help with this Paul. Hopefully someone will step up 
and do this. (And hopefully this is the last time we need to worry abot 
a virtual stand)

Philip

On 12/22/21 10:28, Paul Barker wrote:
> Hi all,
> 
> I'm unable to take the lead on organising a virtual stand for 
> OpenEmbedded at FOSDEM 2022. I'm forwarding this mail to the lists to 
> see if anyone else would like to take over - you'll need to review how 
> the virtual stands work, update the website content as detailed below 
> and be around during FOSDEM 2022 to "run" the stand.
> 
> At least one commit to the website content needs to be made before the 
> end of the year to confirm that OpenEmbedded will have a stand. The 
> repositories we used last year were:
> 
>    * https://gitlab.com/openembedded/community/fosdem-stand-content
> 
>    * https://gitlab.com/openembedded/community/fosdem-stand-static
> 
> I can grant permissions on those repositories to whoever needs them. I 
> also recommend we email stands@fosdem.org to let them know who will be 
> running the stand this year so that the standholders mailing list can be 
> updated.
> 
> Thanks,
> Paul
> 
> 
> -------- Forwarded Message --------
> Subject: [FOSDEM standholders] FOSDEM 2022 stands - an update
> Date: Mon, 20 Dec 2021 15:58:21 +0000
> From: Alasdair G Kergon <agk@fosdem.org>
> To: standholders@lists.fosdem.org
> 
> We've decided to streamline the process for the 2022 event by reusing the
> system and data that is already in place.
> 
> The 2021 stands website has been archived into archive.fosdem.org.
> 
> stands.fosdem.org is now available to use again in 2022 and the direct
> links there from fosdem.org have been removed for now.  The front
> page hasn't yet been updated.
> 
> If you had a stand at FOSDEM 2021, and wish to have one at FOSDEM 2022,
> then all you need to do is to start updating your static content the
> same way as you did last year.
> 
> If you don't want a stand, please send an email to stands@fosdem.org and
> we will remove it.  We will also remove stands that haven't had at
> least one change made by 31st December.
> 
> PLEASE MAKE AT LEAST ONE COMMIT BEFORE 31ST DECEMBER.
> 
> If you need metadata updating that you can't change yourself, either
> send pull requests againt the main repository or email stands@fosdem.org.
> 
> The system for videos/events is not ready yet and this won't be set up
> until the final list of stands is confirmed.
> 
> New stands will be by invitation only and limited in number because of
> the amount of manual administration involved.  If you think there's a
> deserving case for an invitation, contact stands@fosdem.org.
> 
> Alasdair
> 
> _______________________________________________
> standholders mailing list
> standholders@lists.fosdem.org
> https://lists.fosdem.org/listinfo/standholders
> 
> 
> 
> 

      reply	other threads:[~2021-12-22 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211220155821.GD27931@alpha.arachsys.com>
2021-12-22 15:28 ` Fwd: [FOSDEM standholders] FOSDEM 2022 stands - an update Paul Barker
2021-12-22 16:20   ` Philip Balister [this message]

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=49ecafcf-1616-81ef-28c7-106cb7e2735b@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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