The community call was recorded, you can listen here.
See resources to be released below.
The logo will be published on https://dsccommunity.org with a license granting everyone to use it.
Gael talked about the new organization (listen back to the recording when it is available, and you can read more about it here https://dsccommunity.org/community/)
Read more about it here https://dsccommunity.org/community/committee/
See the RFC here https://github.com/PowerShell/PowerShell-RFC/pull/214
Transfer of the repositories will be made in a way so that we keep the quality and still be secure, and will probably start with the move of UpdateServicesDsc.
Please see the new DSC Community website https://dsccommunity.org. Any contributions are welcome from the community; questions, help, blog articles, design changes, etc. Contribute here: https://github.com/dsccommunity/dsccommunity.org
We are hoping we can release these by the end of next week.
These topics and more can be discussed again on the next community call, or discuss it in the Virtual PowerShell User Group #DSC channel. For information on how to join, see https://dsccommunity.org/community/contact/
It is not a problem leaving PowerShell 4.0 support. It is up to each maintainer if they want to leave PowerShell 4.0.
General consensus was that more frequent releases. Breaking Changes should be handled by semver. There was interest from the community to help build pipelines.