Haha, yeah I know. I actually once created a gitlab project for a customer on girlab, I just didn't know it was open source. Or I have just forgot . But even if gitlab is open source, what says that their web interface is? How do I know with my data and me, that I can't know? :-) Is it just "open source" or "free" as in fsf free. Anyway, convenience is just one part of equation. The big issue is convenience of group. Everyone is on github. One fork a repo, make a commit and create PR. PR is the new patch. People don't send patches in emails longer (ok kernel a d Emacs folks does), it is kind of getting out of fashion. And github makes that very convenient. Anyway, the forking culture has more to do with business then just for the service providers. Small companies create projects, and let people fork, the more people fork, the better it looks in presentation for in estors: ohook, we ha e 5000 firks and 10 000 downloads, we are popular, grant us funding for next year and we can do this and that.... -------- Originalmeddelande -------- Från: tomas@tuxteam.de Datum: 2020-05-18 14:33 (GMT+01:00) Till: emacs-devel@gnu.org Ämne: Re: "Write a new package" culture instead of patches? On Mon, May 18, 2020 at 02:08:38PM +0200, Arthur Miller wrote: > writes: [on branching vs contributing, Github culture] > That plays role definitely. Familiarity as well. Github is really easy > to work with [...] Yes, the bribe of convenience. > [...] I dont' know is there a free service like github? I have > very modest needs [...] If you are willing to learn a new web interface, there's Gitlab (the server component is umm... somewhat free; more precisely it's "open core", as they say) and there's Gitea. Savannah has a git service too, I don't know very much about the interface they offer. It does take a bit of willpower to leave the plushy universe, but believe me -- it's a great landscape out there! C'm on. Take the red pill ;-D Cheers -- t