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:

community.codimd.org/t/how-do-

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:

github.com/mashpie/i18n-node/p

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

community.codimd.org/t/communi

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:

community.codimd.org/t/codimd-

And join us at:

meet.jit.si/CodiMD

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:

github.com/codimd/server/pulse

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:
github.com/codimd/server/issue

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:

github.com/codimd/server/issue

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.

github.com/hackmdio/codimd/iss

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.

github.com/hackmdio/codimd/iss

And here it is: Version 1.3.0 of CodiMD! 🎉

The build system for the frontend was refactored, added OpenID support, improved auto completion, fixed a ton of bugs and more!

Containers are ready, it's time to upgrade!

github.com/hackmdio/codimd/rel

Did you know that there are around on ?

Go and find them! Would love to see how they fit into your sticker collages. 😉

Sheogorath's Microblog

This instance is the microblog to my blog. You'll probably find more recent content here while finding more elaborated content on the blog.


Impressum / Datenschutz