3 ms·

Open core is definitely a tension (disclosure: I work at Grist). Specifically for Grist, we differentiate by offering data portability and autonomy, and a full-

Open core is definitely a tension (disclosure: I work at Grist). Specifically for Grist, we differentiate by offering data portability and autonomy, and a full-featured open-source app is part of how we do that. I invite you to check the repo out, you'll see we're not holding back. We did want to flag the project as open core from the start, since we will build proprietary services and features around the core app (which again is very featureful!), and don't want that to come as a surprise down the line.

sdesol 5y ago
Hey great product! Wondering if you can provide some development insights. I'm looking at the activity for the grist-core repo https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D120&t=crc-insights&tb=all&v=gristlabs%2Fgrist-core%3A%3Agithub%3Agristlabs%2Fgrist-core%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D... and it looks like not much has changed in the last 4 months. Is development mainly happening on your SAAS product or is there another repo I can analyze?
- paulfitz 5y ago
  Development currently happens on a private mono-repo with all sorts of stuff in it - including for the SaaS environment yes, and bits left over from when Grist started out initially as a stand-alone desktop app, and so on. Commits are pushed to grist-core about once a week, using git subtree. If you look at commit history, you'll see plenty of features going in month after month. Since we currently develop elsewhere, you'll see few pull requests on github. Internally we use phabricator, which is deprecated now, so we'll need to rejigger our setup soon. It would definitely be good to get more of the development process out there, especially now more people have found us!
  - sdesol 5y ago
    Thanks for the insights! I'm trying to support different workflows and hearing about yours helps.
  - manojlds 5y ago
    Oh so it's not even open source core then.
sundarurfriend 5y ago
I appreciate you taking the time to answer this question. Often projects seem to skip over such difficult/awkward questions, but seeing an honest reasonable answer to it makes me want to check out the project and its ecosystem more.

sdesol 5y ago

Hey great product! Wondering if you can provide some development insights. I'm looking at the activity for the grist-core repo https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D120&t=crc-insights&tb=all&v=gristlabs%2Fgrist-core%3A%3Agithub%3Agristlabs%2Fgrist-core%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D... and it looks like not much has changed in the last 4 months. Is development mainly happening on your SAAS product or is there another repo I can analyze?

paulfitz 5y ago
Development currently happens on a private mono-repo with all sorts of stuff in it - including for the SaaS environment yes, and bits left over from when Grist started out initially as a stand-alone desktop app, and so on. Commits are pushed to grist-core about once a week, using git subtree. If you look at commit history, you'll see plenty of features going in month after month. Since we currently develop elsewhere, you'll see few pull requests on github. Internally we use phabricator, which is deprecated now, so we'll need to rejigger our setup soon. It would definitely be good to get more of the development process out there, especially now more people have found us!
- sdesol 5y ago
  Thanks for the insights! I'm trying to support different workflows and hearing about yours helps.
- manojlds 5y ago
  Oh so it's not even open source core then.

sundarurfriend 5y ago

I appreciate you taking the time to answer this question. Often projects seem to skip over such difficult/awkward questions, but seeing an honest reasonable answer to it makes me want to check out the project and its ecosystem more.