I’m thinking that we should start writing some documentation for core in the Wiki page.
It’ll be like a small book with 5-15 pages about how core, services, plugins and network and other features of MESG works.
Wiki can get very technical and we can put things about our folder structure, what’s the job of each internal packages, a detailed view of gRPC apis and how all of this, services, applications, plugins and network composite together.
We now have this lack of information about technical side of MESG and not having a good detailed wiki can block us to get contributions from the community. Because right now the only way of understanding MESG is reading lots of source code and some forum posts that might not make sense for devs because they are very specific and requires a lot of knowledge before digging in.
Having a detailed Wiki about MESG is useful for our core team too. Coding is only the small part of the job. Thinking and proposing is a lot important but if we cannot put our thinking to words in an organized and detailed way not everybody can easily follow it. I suggested to put a detailed wiki first before a feature implementation.