This is always proposed (fork an app and add nostr to it) and is almost always a bad idea. It would deserve its own clients and web uis without a centralized DB. The goal is to not just rebuild another github, but instead to do it right on top of nostr.
Discussion
That's exactly points 4 and 5 from my OP.
I just want tl fork the frontend part not the backend.
I see no value in starting from scratch when it comes to that. Sure a bunch of useless crap has to be stripped down.
No the plan is the keep git. So itβs not clear to me what nostr adds?
The other stuff. Code review, issues, pull requests, patches, etc
Why so much resistance to just doing it all in nostr?
Seems 100x easier than combining git + nostr.