Earlier quoted context omitted.
I can figure out how to send you a patch set via email (see my Linux kernel contributions), but if I can avoid doing that, sure as heck I will. Your project must be really important to me, or I have to get paid. As for the reason, it's simple: the process of submitting patches sucks. I wrote about it: https://dcz_self.gitlab.io/posts/git-botch-email
Seconded. It can be a lot of effort to just set up a client which won’t mangle patchset emails. Maybe Mutt etc. users get that for free, though.
Give up GitHub: The time has come
261–270 of 585 posts
Re: Give up GitHub: The time has come
#262Earlier quoted context omitted.
Perhaps because there is a (small) risk of leaking confidential information through its output. But that's not as damning as it sounds. First, we know Copilot, if given the right prompt and told to autocomplete repeatedly without any manual input, can regurgitate bits of code seen many times in many different repositories, like the famous Quake fast inverse square root function and the text of licenses. That doesn't…
> Perhaps because there is a (small) risk of leaking confidential information through its output. If Microsoft/Github ever made that argument, that also means that when Copilot is using GPL software as input, the output can only be released under the GPL.
Re: Give up GitHub: The time has come
#263Earlier quoted context omitted.
The boring answer is probably something along the lines of “copilot was trained by employees of OpenAI who aren’t technically MS employees”. When I worked at MS you had to jump through all sorts of hoops to get access to code from other orgs. I can’t imagine what BS you’d need to do to give access to a vendor.
> you had to jump through all sorts of hoops to get access to code from other orgs This may be the dumbest move from M$ that I have read on this thread! Sure, companies need to protect their private IP, but this really feels like creating unnecessary friction for no good reason...
That's definitely something that most large corporations do.
Re: Give up GitHub: The time has come
#264Earlier quoted context omitted.
Generally the ones I don't mind losing. If anyone can't figure out how to send a git pull request or patchset by email, I'm happy for them to email me with questions on how to, which I will answer as best I can.
Drew DeVault created this[1] to help people start using git send-email. I'm not sure if it works for the purpose of contributing to your project, but it may save you from having to explain the same thing repeatedly :) [1] https://git-send-email.io/
[1] https://www.kernel.org/doc/html/latest/process/submitting-pa...
Re: Give up GitHub: The time has come
#265Re: Give up GitHub: The time has come
#266Earlier quoted context omitted.
Not sure I'd agree, every CS student at my school had to take a class where one of the projects was implementing a mini version of git from scratch. And even before that class there was at least one lecture dedicated to git in the intro class.
the only significant difference I've seen in brand-new devs from bootcamps vs CS programs is the devs from bootcamps are somewhat aware that they have a lot of learning to do
Re: Give up GitHub: The time has come
#267> If it is, as you claim, permissible to train the model (and allow users to generate code based on that model) on any code whatsoever and not be bound by any licensing terms, why did you choose to only train Copilot's model on FOSS? For example, why are your Microsoft Windows and Office codebases not in your training set? This is my favorite question about Copilot ever.
Perhaps because there is a (small) risk of leaking confidential information through its output. But that's not as damning as it sounds. First, we know Copilot, if given the right prompt and told to autocomplete repeatedly without any manual input, can regurgitate bits of code seen many times in many different repositories, like the famous Quake fast inverse square root function and the text of licenses. That doesn't…
Re: Give up GitHub: The time has come
#268Earlier quoted context omitted.
Seconded. It can be a lot of effort to just set up a client which won’t mangle patchset emails. Maybe Mutt etc. users get that for free, though.
You could mail patches as plain text attachments, if there are concerns about the clients mangling them. You could also try some easier plain-text clients instead of mutt. Claws mail is a simple GUI based one. [1] https://www.claws-mail.org/
Re: Give up GitHub: The time has come
#269> For its part, Git was designed specifically to make software development distributed without a centralized site. Just yesterday I had to explain the basic premise/history of Git to a young intern. I had asked him if he was using Git to manage his little pet project the company gave him to play with. “No”, he replied, he didn’t know what the company’s policy was to posting code in public on GitHub. As I explained to…
Re: Give up GitHub: The time has come
#270Earlier quoted context omitted.
My favorite answer is: if you included Microsoft source code the quality of suggestions drops below viable product.
The reasons that Windows is awful have nothing to do with code quality. Windows is awful because of intentional choices Microsoft made (e.g., bloatware that gets reinstalled with every update, mandatory Microsoft accounts, and mandatory telemetry).