Would a "project audit 'jury'" be a good implementation for Kas-Smiths at this time?

The issue: a bunch of folks have been building from various perspectives, backgrounds, and experiences. There could be potential discoveries and concepts that are in the blind spot of the core team.

A possible solution: A jury pool that includes at least 1 high level dev and other volunteers could audit projects and then…; 1. point out design flaws 2. share knowledge like planned upgrades that will affect a project/ecosystem 3. help builders who are stuck 4. develop a community of knowledgeable builders… Plus (I think most important) learn of any novel ideas/tools/workflows that should shape the standards being discussed currently. Concurrently, the non-high level devs on the jury would learn in the intimate setting of a project audit. Rising seas raise all ships and in this case it’s vital IMO as more knowledgeable ambassadors = more onboarding = more ambassadors = more onboarding…

2 Likes

Nice idea. The thing is that most projects are not built by humans, and the humans behind them do not have good understanding of the tech and challenges.

If builders would face challenges worth discussing, I’d hope they would open a topic and we could discuss and learn together.
Auditing, specifically in LLM era is a huge time & energy consuming task.

1 Like