Again, as I replied to you on April 15th, if you'd like something to be built by us, you can submit a feature request or become a contributor yourself.

Thanks for the quick response—and I'm sorry if I misunderstood your message. I interpreted your reply as confirming that the grid version history would be proprietary. If I am mistaken, and you plan to stay fully open source, I would definitely get behind the project 100%, ahead of others like Focalboard, Tagspaces, Baserow, Grist, etc! I am sure many others agree.

I have only been asking about a feature that was already marked as "(closed source)" on the roadmap you shared last year, so I assume any new ticket would be redundant to the tasks you are already tracking. Since I did not get a reply for a month on the previous discussion, I tried again here. After another month went by with no reply again, I finally tried discord and I do appreciate that I was able to get some clarity (I thought). I'd been very excited about Appflowy since it hit Hackernews, but I'm just personally much less interested in open core projects, and since others seemed interested in the question, I wanted to link the two together so others have the context too.

As you can check from my remarks on Jan 16, the version history didn't get built at all and is not included in the latest roadmap posted in this thread. You can consider it not planned. And you should see our open-source codebase as a single source of truth and always refer back to it when making claims.

We rely on feature requests and bug reports by the community to guide our direction. The version history has many variations from high-level aggregated actions to very granular transactional operations. Some variations can be beneficial to application users while others can be commercialized by proprietary companies who use our codebase to sell commercial solutions without contributing back. Since we don't receive your feature request, we don't know what problems it would solve, thus good solutions to your needs. Again, I believe you have good intentions. If you can provide us with more context, we will consider prioritizing it.

We'd appreciate more specific use cases, customer needs, and meaningful contributions.

@annieappflowy looking at https://github.com/AppFlowy-IO/AppFlowy-Collab the repository is currently not licensed under an open source license. Will this happen in the future and was just not done at the current state of development or will this incur some kind of non-commercial use licensing?

Thanks @suntorytimed for bringing it up. We forgot to add the license. Now it's under AGPL-3.0