Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
1–10 of 73 posts
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#2Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a busy community outweigh the drawbacks of too many PRs in my opinion
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#3The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#4Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#5But the network effect could lead to something like the next xz backdoor
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#6The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#7Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#8The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…
Why wouldn't this possible on, say, GitLab or Bitbucket?
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#9The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…
Shouldn't we call it a "network prison" in that case? :)
Re: Re: Why Host Emacs Packages on GitHub? (Microsoft vs Freedom)
#10The network effect really is important if you don't use email for patches and want to capture an audience greater than your typical zealot coder (of which I am one). Github makes it easy for non-coders to submit documentation, test their changes, and genuinely be part of something that they are not an expert in. Sure there are disadvantages there too in terms of the quality of the submissions, but the benefits of a b…
Why wouldn't this possible on, say, GitLab or Bitbucket?