Github's revenue model is comprised of private repos, private teams, and
their enterprise SaaS and enterprise on-prem solutions. Both of which the
last 2 large corporations I've worked for have migrated to. They are not
going to change their open/public model because that is what drives their
primary interest groups. It's the same reason that Microsoft is moving
toward OSS, and companies that have found a lot of enterprise traction have
pursued the model of OSS with enterprise support (Hashicorp, RedHat,
GitHub, Atlassian, Docker, and Google.)
They've been very successful with this approach because it encourages such
open adoption. Github isn't going away from OSS, and since they have
competition from BitBucket and GitLab, among others, they have to stay
ahead of the curve and remain open if they want to succeed long term. They
know this.
On the flip side, SourceForge has struggled over the years to keep up with
Github's fast growth because they have failed to innovate and primarily
rely on advertisements as their main source of revenue, this is inherently
restrictive to their ability to grow as an organization and what gives
companies like Github a significant advantage.
David
On Wed, Nov 22, 2017, 1:31 PM Bryce Harrington <br...@bryceharrington.org>
wrote:
> On Wed, Feb 22, 2017 at 07:37:20AM +1030, Michael T. Pope wrote:
> > On Mon, 20 Feb 2017 10:29:56 +0100
> > Fenyo <feny...@gmail.com> wrote:
> > > I still don't get it, this is way too general.
> > > Could you please be a little more specific?
> >
> > No. I am being deliberately guarded. I was told some things in
> > confidence, and similarly I am not confident I have the whole story.
> >
> > However, from open sources you can verify that github is a classic
> startup
> > which is beholden to venture capital investors, and its revenue model
> > continues to evolve. As I said, they are doing well for now, but I would
> > be hesitant to bet they are immune to failure.
>
> Fwiw, at Inkscape we faced some similar problems in migrating off
> SourceForge for code hosting (we still use it for mailing lists, but
> hope to move that too as it's also not without troubles). We evaluated
> several providers, and finally came to a choice between github and
> gitlab. Technically the choice was a bit of a wash - both are on par
> feature-wise, with most of the deltas being advanced stuff not important
> to us. Socially github had an advantage of a larger community, but
> gitlab had an advantage of being more attuned to the open source 'Way' -
> the gitlab software is itself open source, and allows for free
> self-hosting if you had the druthers to do so.
>
> We ended up selecting gitlab and completed a migration to it earlier
> this year, with a minimal amount of fuss (which was mostly due to
> learning curve issues from simultaneously switching from svg->git).
> There have been some (well publicized) service issues, but otherwise
> it's been an overall good experience. Moving platforms also netted us
> some additional developer interest and involvement. We also set up a
> read-only github mirror, although I can't determine if that brought us
> any benefits; people who like github seem to find gitlab equivalent so
> there's been no issues.
>
> Migration was straightforward, although we were doing an SVN->GIT
> transfer, and had some issues relating to branch porting. A GIT->GIT
> transfer into gitlab would be probably be relatively trivial. Users
> with accounts in the prior hosting system needed to re-register with
> gitlab.
>
> We have not migrated our issues, forums, mailing lists, wiki, etc. to
> gitlab, just the code hosting. However, we've been able to take
> advantage of the CI and other code-related services, so it's been a net
> gain functionality-wise.
>
> I don't know how much is public yet, but I can vaguely say that I know
> of various other large open source projects I'm involved with are also
> looking to gitlab rather than github.
>
> Anyway, if you are looking to (wisely) move off SourceForge but are
> unsure about github, I would strongly encourage looking to gitlab as a
> quite viable alternative.
>
> Bryce
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Freecol-developers mailing list
> Freecol-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freecol-developers
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freecol-developers mailing list
Freecol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freecol-developers
