On Tue, 27 May 2025, RAGINI wrote:
Ragini, this is an excellent point of view.
What i'd like to emphasise is the following
- entire DODG space must be terrained.
- every DODG project is a one-trick pony
- only the command line interface and the client should be the focus
- all the goodies, bells and whistles should be cut out
- every DODG project should be compiled from the source
- eliminate all optionals
- CodeRead the DODG project source
- Isolate the key idea, interface and discard everything else
- focussed session to investigate the DODG project bugs (closed and open)
- document the key findings.
This will cut down the effort drastically and help us identify the key
features that are absolutely essential for a SBOM.
In addition, since DODG projects are implemented in Google's programming
language, i'd suggest a 3-day refresher program before the end of this
month.
What do you think ?
Yes, I think this is a good idea to start with.
As the refresher would help us see the projects that we are already aware of
and the news ones that have come up or have been incubated.
+1 from my side.
Go
2025-06-01 Sun 1800hrs (UTC+0300) core features
2025-06-02 Mon 1800hrs (UTC+0300) goroutines
2025-05-03 Tue 1800hrs (UTC+0300) generics
warm regards
Saifi.
