When you want to contribute to a free software project it's often enough to just have a look at issues and support questions. Try to reproduce the issue and offer help. When you run the software yourself anyway, it's a good training to learn your way around it and fixing and optimizing your own setup will become easier.

You don't have to be a programmer to contribute to a project:


Trivial commit. Just exchanging some pictures.

Help us to develop @CodiMD :)

Unit tests are gold.

I just upgraded our ORM 2 major releases and was able to find all broken things by using the Unit tests provided by @amenthes

Thank you so much for that!

Did you know, that I pushed CodiMD 1.4.0 last night? Still noticing the lack of sleep. But it seems to be a good release and not merging some of the PRs and instead moving them to 1.4.1 was the right decision.

Enjoy it :)


Oh, and don't forget to follow @CodiMD and visiting community.codimd.org

Woohoo, H峄搉g translated @CodiMD to Vietnamese! 馃帀

This contribution is on its way into the upcoming release 1.4.0!


If you want to bring CodiMD to your language join us at: translate.codimd.org

The Fedora Magazine provided a new article about using the Fedora Account System (FAS) and how to use the desktop integrated Kerberos Login to have SSO enabled for all Fedora services:


And did you know, that the FAS works with CodiMD when you enabled the OpenID login?

Just sign into: https://<your account name>.id.fedoraproject.org 馃帀

And yes, you can try it on demo.codimd.org

Did you know, that the "source code" link at the bottom of CodiMD will not just send you to our git repository, but to the exact commit this server is running?

This can help you to figure out what version of CodiMD is running there and what repository it was build from.

3 non-coding ways to contribute to CodiMD:

1. Join the forum, tell us your opinion, help organizing the community: community.codimd.org

2. Help us translating, make sure CodiMD is available in your language: translate.codimd.org

3. Spread the word! Share CodiMD and your CodiMD stories with your friends and followers. Let them try CodiMD on demo.codimd.org or your own CodiMD instance :)

We are looking for your CodiMD story. How do you use it? How do you run it? Where do you use it and why?

I wrote my little story about the CodiMD demo instance down:


With the new CodiMD organisation we are working on an upstream-first philosophy in order to move everyone forward, not just us.

Sometimes it's just a tiny push that upstream needs to come back to life:


If you wonder where the CodiMD community channel went, here is a short text explaining it:


TL;DR: Matrix.org is rebuilding their infrastructure from scratch after a security incident.

The whole split up of and showed me how important and powerful is. It's a really great license when you plan to run a project, because it ensures no matter what happens, the community stays in power.

As long as you use the AGPL end-product all features, extensions, 鈥 have to be published and provided to you. Things become a common good and spread knowledge. When you run something on AGPL, don't fall for license changes, it'll only weaken your position.

Did you know that the next version of CodiMD will use @libravatar instead of gravatar?

This will hopefully not only improve privacy a little bit, but also shows our commitment to free software and that we try to create a well-integrated ecosystem 馃憤馃徎

15 Minutes to our first CodiMD community call since we run in own organization, There is a lot to talk about and a lot of things to figure out.

Feel free to read the basics here:


And join us at:


From 0 to 40 in one week. as an own organization is growing 馃殌

It'll definitely need some time to get back to more than 4000 stars, but looking at our activity and work from one week, is leaving a good impression:


Hint: All this work happened in our spare time. No one gets paid for it.

During switching to an own organization CodiMD also switched from Docker Hub to quay.io as container registry. Major improvement: Security scanning for all images by default.

Disadvantage: You have to prepend quay.io to the image.

If you wonder where to find it: quay.io/repository/codimd/serv

If you wonder about the change in general:

We are mostly done with rebuilding missing infrastructure after splitting from the organization.

We went back to zero when it comes to GitHub Stars/Watches/Forks but we have a ton of awesome community members around and look forward to continue our project as before.

Looking for details? github.com/codimd/server/issue

After a long debate we decided to hard fork CodiMD and move into an own repository.

We wrote down our vision on CodiMD and search for your ideas and inspiration:


My take on the recent proposal of the HackMD team about moving CodiMD towards an open core model.

TL;DR: I'm not at all a fan of this idea.


When you run an own CodiMD instance, you are hopefully interested in the future of the project. The team purposed an idea to the community to switch to an Open Core model. It's on you to decide if that will/should happen or not.


Show more

Sheogorath 馃's choices:

Sheogorath's Microblog

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!