I think GitHub discussions is the way to go for discussing small ideas /
changes.
That would be a good forum, possibly inviting more interaction between
contributors and also be a good place for tracking the same.
Thanks
On Wed, 14 May 2025 at 14:39, Sumit Agrawal
wrote:
> There are few challe
Thanks for the proposal Ritesh.
I think the docs module is not as actively contributed to and it would be
good to move towards adding design docs to this - as we can integrate it
directly with the Ozone website as well.
This would also give users an idea of what is planned for the product
roadmap
Thanks Attila for your input.
While this has been there - I am not sure if it is being actively followed.
I think it might be better in such a case, to enforce checks for design
changes so that devs mandatorily update design docs as part of such PRs.
Thanks
On Sat, 15 Mar 2025 at 23:43, Attila D
Thank you for starting this discussion.
I actually had a proposal for this scenario.
For large projects like Typescript and React which are always changing,
they maintain a separate repository for tracking design documents.
This is really useful in:
1. A single place for tracking every design deci
Hello Ozone devs.
I want to propose enabling Github issues for the Ozone repository.
Currently the only way to report any bug or suggest any new feature is via
JIRA which is not accessible to everybody. You need to apply for the
account, wait for approval and then you would be able to open tickets
This sounds good to me.
Thanks for the initiative Swami
On Fri, 8 Nov 2024 at 22:54, swaminathan balachandran <
swamirishi...@gmail.com> wrote:
> Hi,
>
> I hope this message finds you well. With the recent change in Daylight
> Saving Time, our scheduled US community sync at 9 AM PST which is 10:3
> According to https://protobuf.dev/programming-guides/proto2/#enum , we
should add [deprecated=true] to each field instead of removing the old
protos. Please try.
It seems in the current proto2 version we are using deprecated fields are
not being supported in enums.
Also the reserved keyword tha
Hi Ethan,
Thanks for taking up this initiative.
While this is not a problem for existing committers, I do believe people
who are new to the repo might have some confusion with the current
branching and how GitHub actions builds the site.
I give a +1 vote for this change.
Though we are eventually sh
Hello Ozone devs.
I am starting this discussion to get inputs of removing react-app-rewired
as a dependency from the Recon Webapp.
*Overview*
Recon uses *react-app-rewired *to provide custom configs and overrides
without requiring us to eject our react app.
Why is this important ?
- Usually a R
