How can external contributors help ?

[theobat]

I really like the way this project is beeing written and I share almost all the complaints towards existing DBs, however I feel a bit lost when it comes to a todo list. Would it be possible to either:

• mark the low hanging fruits as such in the given github issues ?
• comment small tasks in given existing PRs to enable new comers (or potential learning contributors) to participate ?

thanks again for this project. And by the way the doc is -already- really good, but mostly for users.

[agentm]

Hi @theobat, thanks for the valuable feedback.

Indeed, I could use some help so it is most welcome. I marked some of the issues as beginner-contributor appropriate with "help wanted" labels, as suggested. In addition, here are some non-coder ways to contribute to Project:M36:

• use Project:M36 and open tickets concerning suggested improvements or for discussion around existing feature- even if a feature is merely difficult to use or understand
• suggest relevant Haskell modules for new or existing feature. For example, distributed-process looked good, but d-p-client-server is not well-maintained, so we can't build on GHC 8.2+ cleanly yet. We should probably drop distributed-process but what's the replacement?
• make or suggest improvements to the documentation
• write a blog post about Project:M36

In addition, I know it can't be clear what I think is important from the github issue list, but I am working on features which I hope will pique the interest of new users:

• commits in constant time (requires storage backend rewrite)
• tuple stream processing so that Project:M36 databases can extend beyond RAM

So far, I have been using the Project:M36 blog to post about existing features. Would it be valuable to post about project status or vaporware features in the blog, too?

As always, I can't know how to grow the community without feedback, so catch me on IRC or here- I'm happy to discuss any topic!