[Feature Request] Basic collaboration support

[muldoon2007]

I'm trying to push org-mode within my company as a tool for certain knowledge bases and notes. We can collaborate on coming up with key concepts and facts that are relevant to our work. Some of it is generic domain knowledge in aerospace and computer science, and some is proprietary knowledge within the company. But the whole idea that we can use org-mode and org-fc do both document our knowledge, and help people remember it with SR, is really powerful to me.

One obvious thing that gets in the way with that is the org-fc :REVIEW_DATA, which shouldn't get committed to shared git repositories.

I saw that org-drill has some collaboration support by provided a function to scrub user-specific metadata and then re-apply it, which can be done outside of the mainline git branch. It's described here. But my problem so far with org-drill is the performance degradation with a collection of more than 5,000 org files (I ingested a whole aerospace dictionary from NASA 🤓). On the other hand org-fc has performed great with the big collection.

Have you looked into similar collaboration functions for org-fc? I'm going try out an implementation but it'd be great to know if you've done any thought about this so far. It would be amazing to have a magit-like interface to step people through stripping out the user data, leaving it on a git branch, and then re-applying the user data after a pull.

[l3kn]

This would be a great feature, I saw that org-drill has a way to sync collections of cards but I haven't looked at the implementation yet.

One aspect that's not mentioned in your link is how it deals with suspended cards, e.g. if new cards have been added to the shared collection, should these be imported as suspended into the private collection?

Let me know if you run into any problems with your implementation or if you need help with some org-fc internals.