You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed on the FreeBSD Discord server, promoting major releases and educating community members on what's improved could be effective for catching up, advocating the project, representing the project's core values broadly, and developing the community.
We need to establish a sustainable procedure to host and finally archive formally scheduled live streams. On the other hand, community members are always welcome to stream on Discord (preferably by letting admins know beforehand - to avoid collisions), and there'll be no need to archive them.
The following checklist might take some time to finish, and any assistance you can provide would be greatly appreciated.
Develop a scheduling strategy (Release date 2021-12-06 Unknown time)
Hands up for promoting the event from now onward on Twitter, IRC, elsewhere ...
Dedicate a Discord channel for Release & Upgrade Party
Enrol Release & Upgrade Talks Speakers (might require an online form for accepting/reviewing applications)
This needs an owner champion
Decide on the streaming platform and the streaming procedure (YouTube, Twitch, Discord, etc. - and integrations if any required)
Setup Discord music bot for background/ambient music
Probably need an MC/DJ for this, but full time not needed
Document all of the above
Note, this item is to document what we do this time, so we can do it consistently in the future (and not have to repeat this issue)
The text was updated successfully, but these errors were encountered:
Holding off running this for the 12.3-RELEASE since we're behind a few days since release. Convert this issue into create and document a process for future releases.
As discussed on the FreeBSD Discord server, promoting major releases and educating community members on what's improved could be effective for catching up, advocating the project, representing the project's core values broadly, and developing the community.
We need to establish a sustainable procedure to host and finally archive formally scheduled live streams. On the other hand, community members are always welcome to stream on Discord (preferably by letting admins know beforehand - to avoid collisions), and there'll be no need to archive them.
The following checklist might take some time to finish, and any assistance you can provide would be greatly appreciated.
The text was updated successfully, but these errors were encountered: