Hi,

Many thanks for all the nice comments. I'm very grateful.

Just to clarify the vibe:

If there's ever an official code sharing platform for Trongate, its launch would be the biggest event in the history of the framework. Make no mistake. We'd be going after Composer, NPM and anything else that's out there.

We'd also be making it unique.

In addition, we'd be trying to solve real problems that the existing platforms haven't solved. Nobody wants another "me too" code sharing platform. So if it happens, we play to win.

I've learned the hard way that I cannot guarantee popularity or GitHub stars. However, I can make this promise: if Trongate shows up, we're not just participating. On every metric that matters, what we're doing has to be genuinely better than the alternatives. Nothing less will do.

For that reason, I don't think a GitHub repo, on its own, is something that I would personally want to be involved with.

So, the official position is this: there is currently no official code sharing platform for Trongate.

If somebody out there wants to build one, you're absolutely welcome to do so. For my part, I promise I won't do anything uncool. I'm not going to go after anybody simply for using the Trongate name, the logo or building something for the Trongate community. It's an open source project and, provided everybody is operating within the appropriate terms, I'm happy for people to go forward with those kinds of ideas.

Therefore, if you're thinking about building something - go for it.

I may not promote what you're doing and I may not be involved, but I won't stand in your way.

As always, if anyone out there makes a gazillion with Trongate, all we ask is that you send Team Trongate a postcard with a photo of your superyacht.

DC

I like the idea, although I agree with DC that simply putting a collection of repositories on GitHub wouldn't really solve the whole problem.

A proper module repository could make a lot of sense for Trongate if it handled those things properly.

I'd also be interested in seeing how it could be done without making it unnecessarily complicated. One of the things I like about Trongate is that you don't need a huge amount of machinery just to get a simple application running. I wouldn't want the module system to become the opposite of that.

Martin