The big question; GitLab, GitHub, or Bitbucket for future projects. On the one hand, Bitbucket requires open source licenses for every single project, not per company, whereas GitLab is self hosted all the way; you can pay for it if you want to, but that's only if you need larger features sets. I could think of @freemo on this one as a possible knowledgeable suggester?
🇳🇱
@cambridgeport90 I'd rule out bitbucket out of the gate. It isnt very popular and doesnt offer much int he way of features.
If you want to attract interested developers Github is a must. Its where most people just assume all open-source code is going to be. It also helps generate interest through watchers, etc.
In terms of the personal user expiernce I prefer GitLab. It has the container register and its approach to CI is amazing. Similar to travis but integrated into the repo.
What I recommend is using GitLab AND Github and just linking the two such that if you commit to one it automatically updates the other. Make whichever you want the official repo.
@freemo Dang it. I didn't see this until … like now. There was a lot going on that day. But in light of that, I'll discuss it with my friend and consider any future projects that need their own environments to use GitLab. After all, attracting devs is a must, and the way our community is set up right now, that's not happening the way I'd prefer. We essentially just had to initiate our outsider testing team into the dev workflow the other night because all of our previous devs lost interest. LOL