Good luck, but I don't think you'll be successful with that, because I think notability is an extremely important part of the glue that holds the Wikipedia project together. Without it you not only get a torrent of pointless, trivial content that readers have to sift through to find the real stuff, but you also lose
the critical factor that makes the editorial challenge of Wikipedia tractable; without notability, you simply have too many potential articles to fact-check, and no way to fact-check them.
About 15 years ago some friends and I started a company whose technical premise boiled down to taking IRC and replacing the static tree-based "routing" system it has with a real dynamic routing protocol. No more netsplits! Arbitrary topologies! It was so simple! Why would anyone want anything other than a biconnected IRC? It turns out that the moment you lose the static tree property, the whole system goes to hell. All the sudden, messages aren't (and can't be) reliable, because the network can change out from under them while they're being forwarded. So you figure you'll just build a simple reliability scheme for messages to ride on. Oh, wait: IRC is a group messaging system, and not only is the distributed systems GMS problem not particularly easy to build in a "realistic" network, but providing reliability on it is essentially the multicast reliability problem, which is itself so annoying that it's part of why IP multicast failed.
My long-winded point is, sometimes something that seems like an obvious weakness of an existing system is actually fundamental to that system's viability.