I don't know if these are multi-tenant projects but you could certainly explore them: leantime.io and openproject.org. Source: about 1 year ago

I just started messing with OpenProjectOpenProject which seems pretty nice, but I actually bought a lifetime license to Nifty.pm a couple years ago on AppSumo and it is awesome.. Not free or open source or self-hostable though.. :/. Source: over 1 year ago

Openproject.org BIM edition is the closest I got so far, but it lacks the smooth versioning experience of git and the accessibility of a platform like github. Source: almost 2 years ago

I know I am asking for a lot here. I worked for a company that used everything from Atlassian and miss the unified experience. Now I am working for a hospital and we are required by law to keep everything on premise. Atlassian makes it very obvious that they are a "go cloud or gtfo" company so... I am kind of searching or something equivalent. Currently using openproject.org as a JIRA replacement, Mediawiki as a... Source: almost 3 years ago

When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises. For documents, we had to do... - Source: Hacker News / 3 months ago

There is no one-size-fits-all approach to writing descriptions, so you need to figure out what works best for you and your team. However, seeing real-world examples might inspire you to find new ways to write them. Here are some examples from descriptions we have written for Kitemaker. - Source: dev.to / over 1 year ago

Kitemaker.co - Collaborate through all phases of the product development process and keep track of work across Slack, Discord, Figma, and Github. Unlimited users, unlimited spaces. Free plan up to 250 work items. - Source: dev.to / over 1 year ago

At Kitemaker, we recently made the leap to Recoil.js for our React state management needs. Before using Recoil, Kitemaker used a simple state management solution built upon useReducer(). We built Kitemaker to be super fast, responding to every user interaction instantly. However, in organizations with lots of data, we sometimes had a difficult time achieving this due to unnecessary re-renders. Kitemaker has a sync... - Source: dev.to / over 1 year ago

Definitely feel your pain. We did a full OT implementation for our startup [0] and it was a beast. We based it on Slate.js which has a nice concept of operations that maps nicely to OT, but it was still a lot of work to get it working well (and there are still rough edges we try to improve all of the time). We did base it on Postgres in the backend so really looking forward to what the Supabase team comes up with... - Source: Hacker News / almost 2 years ago