> “because it avoids creating yet another isolated patch of weeds”

Pitching in to existing projects actually brings MORE people into MORE and different and DEEPER weed patches BECAUSE each project has their “own way” to see the “problem” and to implement a “solution”. 

Code repos are ALL about implementation. There is ZERO room in a repo to back out and discuss the bigger problem BECAUSE it only ends up in YA issue, pr delegation, forked project, or abandoned #wontfix thread. 

ALSO, because these siloed “repo discussions” are all happening on GitHub, then there’s even less opportunity for the rest of Nostr to contribute to maybe keeping them alive and connecting dots for us developers who ARE “in the weeds”. 

nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl may be onto something when she pitches bringing these repo convos into Nostr. This may help, but still … we need time and space for dev realignment. Nostr doesn’t have this. 
nostr:note1affw8xlq26aulc5u93293vhempxzgj3w44x7gxz2xl89ftsd7m6qyfx4hf