Summary so far:
1. Community wide announcements and notifications via emails are best.
2. Community engagement on technical topics (stuff that search engines
should be aware of) best done on GitHub Discussions
3. There should be community feedback around how to organize GitHub
Discussions to better
> Currently this is shared in the docs folder in the ozone repo. Maybe you
already talked about this, but once we move the docs content to the
ozone-site repo (afaik that’s the plan) we will share these there, right?
Will we have them published to the site?
Thanks for bringing this up Zita, I have
Thanks for bringing this up! I agree with the ideas shared above. The way
you shared the design proposal for container reconciliation is really good,
it’s easy to give feedback and later to track back why some decisions were
made. Currently this is shared in the docs folder in the ozone repo. Maybe
I tend to think that discussing design documents is absolutely fine in PRs
and that they should be held alongside with the project. I see the benefit
of possibly more effort going into keeping it up to date if it lives with
the codebase.
Still I welcome the suggestion from Ethan, to have an emphasi
Thanks for bringing up this proposal Ritesh. I am +1 for using GitHub
Discussions for user/operational questions and indicating that on our Slack
channel.
I am also +1 for design discussions happening as PRs to markdown documents
as we are doing for container reconciliation. Inline comments make i
Hi Pifta,
Thank you for chiming in.
I have actually not considered how to revive the mailing list for technical and
design discussions.
I am not sure why mailing lists are no longer as popular, in general I see a
decline of
using emails for discussions other than formal one way communication.
Hi Ritesh,
thank you for the proposal, and taking action during the last community
sync.
I support the idea of using GitHub Discussions, but I would like to bring
up one thing with GH Discussions. I am not a fan of Slack either and I
agree Slack is far from optimal and is hard to search.
It did n
