News for hackers. Stuff that matters.
Re:Getting Forked by Microsoft by lachie83 on Monday April 21, 2025 @03:51PM (#43755745)
Hi Philip, I'm Lachlan from the Cloud Native Ecosystem team at Microsoft. Our team works in the cloud native open-source community with a goal of being great open-source collaborators in these projects and communities, and I’m sorry that this happened.

We appreciate your leadership and collaboration on Spegel and see your project solving a real challenge for the cloud native community. I wanted to thank you for your blog post https://philiplaine.com/posts/getting-forked-by-microsoft/, let you know what we’re doing, and address a few points.

We’ve just raised a pull request https://github.com/Azure/peerd/pull/110 amending the license headers in the source files. We absolutely should have done better here: our company policy is to maintain copyright headers in files – we have added headers to the files to attribute your work.

I also wanted to share why we felt making a new project was the appropriate path: the primary reason peerd was created was to add artifact streaming support. When you spoke with our engineers about implementing artifact streaming you said it was probably out of scope for Spegel at that time, which made sense. We made sure to acknowledge the work in Spegel and that it was used as a source of inspiration for peerd which you noted in your blog but we failed to give you the attribution you, that was a mistake and I’m sorry. We hear you loud and clear and are going to make sure we improve our processes to help us be better stewards in the open-source community.

Thanks again for bringing this to our attention. We will improve the way we work and collaborate in open source and are always open to feedback.

Re:Getting Forked by Microsoft by kyleee on Monday April 21, 2025 @04:13PM (#43755956)
Maybe as a show of good faith you could send the original creator 10 or 20k usd as a thank you. Talk is cheap
Re:Getting Forked by Microsoft by rererereferred on Monday April 21, 2025 @04:47PM (#43756287)
10 or 20k USD for Copyright Violation sounds cheap.
Re:Getting Forked by Microsoft by guywithahat on Monday April 21, 2025 @05:18PM (#43756599)
This sounds like a good idea but getting the checkbook out at a company like Microsoft probably takes 3-5 meetings, and saying you want to donate because you accidentally stole their code and put the company at (theoretical) risk of a lawsuit seems like a bad conversation starter with management.

I like the thought though

Re:Getting Forked by Microsoft by qingcharles on Monday April 21, 2025 @07:26PM (#43757585)
Not my experience with MS. They seemed to be pretty low on the "red tape" scale.

Maybe they should have 3-5 meetings before forking OSS projects though :)

Re:Getting Forked by Microsoft by NoahZuniga on Monday April 21, 2025 @09:46PM (#43758360)
Also it seems like in the original comment they already admitted to breaching the copyright, so sending him money doesn't increase the chance of a lawsuit succeeding.
Re:Getting Forked by Microsoft by dustedcodes on Monday April 21, 2025 @04:04PM (#43755869)
Biggest bs response. Microsoft either creates trash like Windows, WSL and Azure or they steal.
Re:Getting Forked by Microsoft by unixhero on Monday April 21, 2025 @04:28PM (#43756117)
I think the response is sincere and adequate.
Re:Getting Forked by Microsoft by aleph_minus_one on Monday April 21, 2025 @04:46PM (#43756282)
It is indeed sincere:

> We absolutely should have done better here: our company policy is to maintain copyright headers in files – we have added headers to the files to attribute your work.

This is a more than clear corporate statement from Microsoft's side that Microsoft is perfectly fine if copyrights are violated (implicitly including Microsoft's), as long as, if they get caught, people start giving proper credits. This implicitly implies that Microsoft promises that from now on they will only sue for getting proper attribution in case of copyright violations, and not for monetary compensation for damages.

I find this implicit statement really nice from Microsoft's side - actually more than what I could ever have wished for. :-)

Re:Getting Forked by Microsoft by tacker2000 on Monday April 21, 2025 @04:26PM (#43756094)
Now that you got caught you are fixing it and writing fancy PR fluff. An org the size of MS should have clear policies and processes of how to handle open source forks like this. Unless we assume “bad faith” here. This is a pretty bad look.

I wonder how many other projects are not attributed correctly. Are you checking up on them also or just waiting for the next HN post?

That said, the author of Spegel should have used another license if he wanted more “recognition” or the like.

Re:Getting Forked by Microsoft by aleph_minus_one on Monday April 21, 2025 @04:37PM (#43756203)
> I wonder how many other projects are not attributed correctly. Are you checking up on them also or just waiting for the next HN post?

As I wrote in my parallel post (https://news.ycombinator.com/item?id=43756102): these copyright violations (not giving proper attribution of the license requires it is copyright violation) from Microsoft's side (the more, the "better", and the clearer the message) can be considered de-facto, implicitly stated corporate messages from Microsoft's side that they are from now on officially fine with copyright violations, and thus everybody is from now on free to violate the copyright on every software product that Microsoft has ever produced.

Re:Getting Forked by Microsoft by leoqa on Monday April 21, 2025 @08:01PM (#43757766)
Sounds like a very expensive legal gambit.
Re:Getting Forked by Microsoft by xwolfi on Tuesday April 22, 2025 @04:27AM (#43760120)
You have to prove the mens rea, and even then, people committing crimes don't automatically deserve crimes committed upon them.
Re:Getting Forked by Microsoft by johnisgood on Tuesday April 22, 2025 @07:11AM (#43760823)
In reality they do, in some cases, e.g. capital punishment.
Re:Getting Forked by Microsoft by johnisgood on Tuesday April 22, 2025 @11:29AM (#43763344)
I think I am being misunderstood here. I do not agree with it, I am just referring to practices in some countries.
Re:Getting Forked by Microsoft by wilg on Monday April 21, 2025 @06:30PM (#43757219)
I mean what else are they supposed to say or do to correct a mistake other than "sorry, here's what happened, we have fixed it, we are taking steps to reduce the chances of it happening again"? Sometimes you just have to correct an error.
Re:Getting Forked by Microsoft by epanchin on Monday April 21, 2025 @07:17PM (#43757546)
Ideally a list of other projects they have since found and attributed.
Re:Getting Forked by Microsoft by NewsaHackO on Monday April 21, 2025 @07:38PM (#43757652)
From the tone of the response to Microsoft response, people will not be happy unless Microsoft publicly executed the engineers that did it.
Re:Getting Forked by Microsoft by kshahkshah on Monday April 21, 2025 @07:53PM (#43757726)
I think people tend to forget that large companies are made up of flawed individuals and their policies mitigate but don't eliminate mistakes
Re:Getting Forked by Microsoft by oatmeal1 on Tuesday April 22, 2025 @03:11AM (#43759755)
They are also fully funded to compensate when they do something wrong. An apology from a Fortune 500 company with a history of unethical behavior is worthless.
Re:Getting Forked by Microsoft by Fraterkes on Tuesday April 22, 2025 @03:43AM (#43759937)
That would be a start yeah
Re:Getting Forked by Microsoft by wilg on Monday April 21, 2025 @08:02PM (#43757775)
What if there aren't any or they have not yet done that because they wanted to respond to this person first?
Re:Getting Forked by Microsoft by toobulkeh on Friday April 25, 2025 @09:23PM (#43800090)
I think financial damages are realistic here. They materially damaged another brand, it’s all business at the end of the day.
Re:Getting Forked by Microsoft by beefnugs on Monday April 21, 2025 @05:45PM (#43756855)
He is lucky microsoft doesn't have 30,000 ai-agents out there just stealing everything he has ever done and spinning up 10 competitors to each project all with new license and money flow into microsoft in any number of ways.

I mean they made sure to get all the consent from all authors on github before training on it right

Re:Getting Forked by Microsoft by gscott on Tuesday April 22, 2025 @12:05AM (#43758992)
I am on this affiliate list and one of the things they're pitching right now is an AI website cloner. Steals the other person's website switches out their content to something similar with new images... Profit!!!
Re:Getting Forked by Microsoft by arkh on Tuesday April 22, 2025 @02:47AM (#43759638)
> Now that you got caught you are fixing it and writing fancy PR fluff.

Nope, "the revenge of Clippy" is doing the writing.

Re:Getting Forked by Microsoft by averageRoyalty on Tuesday April 22, 2025 @10:16AM (#43762490)
> Now that you got caught you are fixing it and writing fancy PR fluff. An org the size of MS should have clear policies and processes of how to handle open source forks like this. Unless we assume “bad faith” here. This is a pretty bad look.

What would you prefer them do? A public flogging? Bring back the stocks?

I agree with the sentiment with these types of comments (I hate PR fluff too), but the aggression when a company has screwed up and not only admits it but tells you their plan going forward is silly. The best case scenario is it does nothing, worst case it encourages them to ignore it next time it happrns.

Re:Getting Forked by Microsoft by cycomanic on Tuesday April 22, 2025 @11:43AM (#43763493)
Well how does Microsoft react if some company "forgets" to licence windows/office/some other product? Because that is what happened here a clear licence violation so Microsoft essentially pirated the software.
Re:Getting Forked by Microsoft by davidron on Tuesday April 22, 2025 @08:26PM (#43767564)
I bet Microsoft would do something similar. If Microsoft entered an agreement with another company, Apple for instance, to build a version of word for the Mac, a fork, and part of the license has a requirement to attribute in the help file or something like branding requirements, and then Apple doesn't do it right, then Microsoft reaches out to Apple and tells them to fix it else be in breach of the license. They fix it, happy happy. They don't fix it and lawyers get paid.

This was MIT licensed open source software and an attribution clause was not properly respected. Hardly piracy.

Re:Getting Forked by Microsoft by Vegenoid on Tuesday April 22, 2025 @12:23PM (#43763861)
Their plan? “We hear you loud and clear and are going to make sure we improve our processes to help us be better stewards in the open-source community”? That’s not a plan. It’s PR fluff.

Nobody is expecting this one incident to make Microsoft change. It’s about reputation, which can take a long time to shift, but can be important in the long term.

We don’t have to just accept it when a company issues a statement apologizing for their screwup. It’s perfectly acceptable to say “this apology means little to me, and if you want your reputation to change you need to do more”.

Re:Getting Forked by Microsoft by user_7832 on Wednesday April 23, 2025 @01:01AM (#43768740)
I’d like them to explicitly set out how they’re going to avoid such an issue occurring in the future, rather than symptomatically commenting on an HN post that’s now a top post.

They say:

> We hear you loud and clear and are going to make sure we improve our processes to help us be better stewards in the open-source community. Thanks again for bringing this to our attention. We will improve the way we work and collaborate in open source and are always open to feedback.

…which is a lot of nice words with absolutely NO accountability. They could write a sticky note “do better” and technically that’s all that’s required from their side. Is that okay with you?

Re:Getting Forked by Microsoft by mauer1361 on Wednesday April 23, 2025 @10:07AM (#43772406)
>A public flogging? Bring back the stocks? Yes, great idea.
Re:Getting Forked by Microsoft by hmottestad on Wednesday April 23, 2025 @12:35PM (#43773938)
What would Microsoft do if I forked their repo, removed all the licenses and then held talks at conferences about my amazing new tool?

Pretty sure their legal department would have my fork obliterated from the face of the earth and I would be crossing my fingers that all I got was a cease and desist letter instead of a lawsuit in Texas.

Re:Getting Forked by Microsoft by optymizer on Tuesday April 22, 2025 @02:51PM (#43765110)
This tsk-tsk is misguided. There's a time and place to shame companies for acting in bad faith, and we should do it, but I don't think it's the case here. It does not seem like damage control for intentional malice.

The TL on the project should have done better, but it was a good sign that they had originally taken the time to acknowledge Spegel's author's help. It's very likely that someone else dealt with the actual code and license text and didn't know any better.

The PR text is reviewed by lawyers. The default advice from lawyers is "do not admit any wrongdoing". They probably suggested that the license text be fixed silently with no apology. The PR department likely convinced them that a public apology would be good for optics and it doesn't seem soulless either.

They should have done better. They admitted that. They may or may not change their internal processes, but it's now in the record book. Case closed.

And the author of Spegel should not have used a different license if he wanted "more <<recognition>>". He wanted the recognition specified by the MIT license.

Re:Getting Forked by Microsoft by aleph_minus_one on Monday April 21, 2025 @04:27PM (#43756102)
> but we failed to give you the attribution you, that was a mistake and I’m sorry.

In other words: there exists some responsible person at Microsoft who violated the copyright (yes, removing the attribution is also a copyright violation!) for Microsoft.

In consideration how Microsoft has been treating copyyright violators for decades, if Microsoft does not give this responsible person the same crual treatment, it should be considered an honest, clear, implicit official statement from Microsoft's side that they are perfectly fine if hackers violate all of Microsoft's copyright. In other words: it means that all of Microsoft's software now (spiritually!) will become public domain.

Also, if Microsot does not make make this responsible person pay the caused damage from their own pocket to the original author of Spegel with the same monatery magnitude as if Microsoft would sue other entities for a violation of copyyright of Microsoft's software, the same statement applies.

Re:Getting Forked by Microsoft by throwaway642012 on Monday April 21, 2025 @04:44PM (#43756263)
Based on the initial commits and the logs after that surely there’s someone unethical person at MS. This might have been brushed under the carpet and due to sheer luck it reached HN frontpage.

https://github.com/Azure/peerd/commit/64b8928943ddd73691d0b5...

Re:Getting Forked by Microsoft by 9_ZPK7- on Monday April 21, 2025 @05:15PM (#43756578)
> it means that all of Microsoft's software now (spiritually!) will become public domain.

You have said many things like this in this thread. I don't think you understand how laws or courts or legal fees work. Good luck defending yourself against MS's army of lawyers during your court proceedings though!

Re:Getting Forked by Microsoft by aleph_minus_one on Monday April 21, 2025 @06:33PM (#43757247)
> I don't think you understand how laws or courts or legal fees work. Good luck defending yourself against MS's army of lawyers during your court proceedings though!

I have no hope that the courts currently (!) agree with this. But let us spread the gospel so that as many people as possible know how Microsoft's "real" stance on copyright is. If a lot of people become aware of this and this truth stays in lots of people's heads for a sufficiently long time, the public opinion might change so that juries (representing the public opinion in courts) will indeed begin to judge against Microsoft in the way that I described.

Re:Getting Forked by Microsoft by saagarjha on Monday April 21, 2025 @11:38PM (#43758887)
If I accidentally pick up your jacket instead of mine and apologize when you point it out this doesn't mean I give you blanket rights to steal my stuff forever. If I keep doing it, then it's probably worth looking into, but you're going to have to bring up evidence of serial abuse for that.
Re:Getting Forked by Microsoft by Tepix on Tuesday April 22, 2025 @02:01AM (#43759443)
What if someone takes your jacket and removes your name tag and sews his own tag to your jacket though?
Re:Getting Forked by Microsoft by saagarjha on Tuesday April 22, 2025 @06:11AM (#43760571)
You still can't steal their jacket.
Re:Getting Forked by Microsoft by robertlagrant on Tuesday April 22, 2025 @05:37AM (#43760406)
> the public opinion might change so that juries (representing the public opinion in courts) will indeed begin to judge against Microsoft in the way that I described

I'm pretty sure that's exactly how juries shouldn't work.

Re:Getting Forked by Microsoft by RayVR on Monday April 21, 2025 @11:17PM (#43758804)
Re:Getting Forked by Microsoft by deknos on Monday April 21, 2025 @04:27PM (#43756104)
> We hear you loud and clear ..

oh, corporate wording. so you do not really care :D

Re:Getting Forked by Microsoft by aleph_minus_one on Monday April 21, 2025 @04:59PM (#43756395)
> oh, corporate wording. so you do not really care :D

Better do care a lot about it, and use every syllable of the corporate statement against Microsoft. :-)

I.e. the principle of some martial arts: use the force that the opponent applies against himself/herself.

Addendum: In this particular case

> We hear you loud and clear ..

can be considered as a very official statement from Microsoft that from now on, they cannot claim anymore that they didn't know of something ..., i.e. the hangman's noose is slowly closing. :-)

Re:Getting Forked by Microsoft by h4ck_th3_pl4n3t on Monday April 21, 2025 @05:49PM (#43756898)
Probably already approved by the legal department which is working in damage control mode :D
Re:Getting Forked by Microsoft by vvillena on Monday April 21, 2025 @04:37PM (#43756199)
Not good enough. All previous commits still infringe Spegel's copyright, given they are still available and distributed. I would assume the point release also infringes copyright.

You are Microsoft. You can do better.

Re:Getting Forked by Microsoft by wilg on Monday April 21, 2025 @06:32PM (#43757237)
Very silly, they can't rewrite the commit history nor would it be proper to update old packaged releases.
Re:Getting Forked by Microsoft by vvillena on Monday April 21, 2025 @06:35PM (#43757268)
What do you mean they can't rewrite the commits? They can, they should, and it's really easy to do so. As for the packages, they should be taken offline.
Re:Getting Forked by Microsoft by wilg on Monday April 21, 2025 @08:02PM (#43757773)
They should neither rewrite the commits nor take the old packages offline. It's not worth a huge potential clusterfuck when the issue has been fixed on the latest version.
Re:Getting Forked by Microsoft by kassner on Monday April 21, 2025 @08:33PM (#43757967)
They should absolutely do it. They made a serious mistake and should pay for it, even if that means every Microsoft developer having to rebase all their WIP branches. The more expensive it gets the more they’ll pay attention to those things in the future.
Re:Getting Forked by Microsoft by saagarjha on Monday April 21, 2025 @11:40PM (#43758893)
Why not just fire the entire division? Maybe they should shut down the company?
Re:Getting Forked by Microsoft by vvillena on Monday April 21, 2025 @08:49PM (#43758078)
You might be overestimating how hard this is, because it's not hard at all. It takes less than half an hour to create a script that does it.
Re:Getting Forked by Microsoft by Mashimo on Tuesday April 22, 2025 @04:39AM (#43760168)
What is the benefit of re-writing the git history?
Re:Getting Forked by Microsoft by guappa on Tuesday April 22, 2025 @06:30AM (#43760653)
Complying with the terms of use instead of infringing copyright
Re:Getting Forked by Microsoft by wilg on Tuesday April 22, 2025 @05:25PM (#43766462)
The terms of the license don’t require you to modify the git history that’s a goofy interpretation.
Re:Getting Forked by Microsoft by guappa on Wednesday April 23, 2025 @04:26AM (#43769822)
The terms of the license require you to ship the copyright note. Their latest release is in violation…
Re:Getting Forked by Microsoft by miffy900 on Tuesday April 22, 2025 @12:36AM (#43759108)
Rewriting those commits would effectively allow them to erase their mistake, which kind of lets Microsoft off the hook in a way.
Re:Getting Forked by Microsoft by hoseja on Tuesday April 22, 2025 @06:11AM (#43760568)
Git isn't some kind of secure blockchain.
Re:Getting Forked by Microsoft by throwaway642012 on Monday April 21, 2025 @04:39PM (#43756225)
What about the allegations that people in MS did this for personal gains? Will there be any lessons learned from this?
Re:Getting Forked by Microsoft by cmgriffing on Monday April 21, 2025 @05:12PM (#43756540)
I think this is a good case for applying Hanlon's Razor. The person that did the forking and removal of copyright text may simply not know that it needed to stay there.

I would love to know what processes MS is considering to prevent this in the future as well as what kind of auditing might be done to look at other projects that started as forks.

Re:Getting Forked by Microsoft by frumplestlatz on Monday April 21, 2025 @06:08PM (#43757039)
> The person that did the forking and removal of copyright text may simply not know that it needed to stay there.

That person never learned what plagiarism is throughout their entire academic career, much less once they landed at Microsoft?

Re:Getting Forked by Microsoft by isp on Monday April 21, 2025 @06:34PM (#43757255)
There are other possibilities, for example, the person may have thought that they were complying with the MIT licence by releasing the new project under the MIT licence too + including a mention of the original project in the README.

This, of course, is incorrect, and a cursory read of the very short licence text would show it to be incorrect.

But I, too, am strongly favouring Hanlon's razor.

Re:Getting Forked by Microsoft by saagarjha on Monday April 21, 2025 @11:39PM (#43758891)
Hanlon's razor can indicate an absence of malice, but that doesn't mean what they did wasn't wrong, nor should Microsoft skimp on taking steps so it never happens again.
Re:Getting Forked by Microsoft by isp on Tuesday April 22, 2025 @07:32AM (#43760915)
I agree on both points, and with the earlier comment:

> I would love to know what processes MS is considering to prevent this in the future as well as what kind of auditing might be done to look at other projects that started as forks.

In response to:

> ... going to make sure we improve our processes to help us be better stewards in the open-source community.

Re:Getting Forked by Microsoft by palata on Tuesday April 22, 2025 @07:14AM (#43760843)
Most software developers I know have no clue how open source licences work.

Hell, I have been reading a lot about them (including the licences themselves and stuff like the GPL FAQ) many times, and in situations like this it's still not entirely clear to me what Microsoft should do (surely there are different valid ways to handle this).

Would you consider yourself competent as a lawyer regarding open source licences? If not, can I say that "you apparently never learned it" and aren't better than the rest of us?

Re:Getting Forked by Microsoft by frumplestlatz on Tuesday April 22, 2025 @12:48PM (#43764094)
Compliance here is simple — preserve the original license and copyright.

This isn’t complicated, but if you truly don’t understand it then you should speak to a lawyer before incorporating someone else’s code into your or your employer’s project.

Re:Getting Forked by Microsoft by palata on Tuesday April 22, 2025 @01:01PM (#43764191)
> Compliance here is simple

Have you read the threads here? My feeling is that there are many mutually exclusive interpretations of what can/should be done.

I don't know if it's simple or not, but what I see is that it's obviously not 100% clear for everybody (me included).

Re:Getting Forked by Microsoft by frumplestlatz on Tuesday April 22, 2025 @01:31PM (#43764464)
Ignorance is not a surprise or a fault. Anyone choosing to act from ignorance very much is.

I reiterate that this is not complicated. If you still find it complicated, then you need to speak to an attorney or someone else qualified to give you direction before attempting to use someone else’s code.

We have been doing this for nearly 60 years. Correct examples abound if you’re willing to do basic research.

Re:Getting Forked by Microsoft by palata on Tuesday April 22, 2025 @05:14PM (#43766366)
I will reiterate that most developers I know have almost no idea how open source licences work.
Re:Getting Forked by Microsoft by frumplestlatz on Tuesday April 22, 2025 @07:48PM (#43767363)
That’s willful ignorance at this point, and they shouldn’t be incorporating open source code into their projects without speaking to an attorney or someone otherwise qualified to answer their questions.
Re:Getting Forked by Microsoft by Shocka1 on Thursday April 24, 2025 @09:39AM (#43782650)
It wouldn't be surprising to me if an expert Leetcoder simply copy/pasted the code, knowing nothing of licensing. What would surprise me though is the engineering team not having at least one open source expert that didn't intervene.
Re:Getting Forked by Microsoft by DrillShopper on Monday April 21, 2025 @06:45PM (#43757321)
Hey how about doing the right thing first time next time instead of waiting until you get ass-blasted on social media?
Re:Getting Forked by Microsoft by spiritplumber on Monday April 21, 2025 @06:58PM (#43757430)
Do better next time, eh?
Re:Getting Forked by Microsoft by j45 on Monday April 21, 2025 @08:02PM (#43757776)
I might not be up to speed, is naming this behaviour "source of inspiration" a common industry term to accurately represent an unacknowledged fork by the large company over the small?

It seems an option to not take free labour to build a commercial cloud largely as a wrapper of open-source, and maybe find other ways to support the creators.

If one person's labour is that valuable to a company, maybe it will help someone realize that supporting such individuals monetarily might help create the next thing with time that they can't get to today.

Re:Getting Forked by Microsoft by abetancort on Monday April 21, 2025 @08:37PM (#43757995)
Send a big fat cheque to him.
Re:Getting Forked by Microsoft by kjellsbells on Monday April 21, 2025 @08:45PM (#43758049)
Kudos for stepping in here, but I think the team at Microsoft need to do some more investigation, no?

Microsoft is a large, wealthy corporation has a big target painted on its back, and, consequently, CELA (corporate, external, and legal affairs) are, for good reason, a very strong force inside Microsoft. You can't just grab some code from someplace at Microsoft. Your PM has to run it past your division's CELA rep, look at the terms, assess exposure, etc. Did that happen?

If not, that's a big hole and you should probably beg forgiveness from them as you ask for an audit of every other piece of code you've picked up.

If it didn't happen, well, I suspect someone in your group just became the new Nelson, the hapless developer, in Microsoft's Standards of Business Conduct videos. You really don't want to be Nelson.

Re:Getting Forked by Microsoft by bilbo-b-baggins on Tuesday April 22, 2025 @01:09AM (#43759221)
Give him a share of the money you make off of it.
Re:Getting Forked by Microsoft by dontTREATonme on Tuesday April 22, 2025 @03:13AM (#43759770)
60% of $0 is still $0.
Re:Getting Forked by Microsoft by guappa on Tuesday April 22, 2025 @06:32AM (#43760662)
They wouldn't be doing any of this if they thought it's 0$
Re:Getting Forked by Microsoft by philsnow on Tuesday April 22, 2025 @09:32PM (#43767911)
Reducing costs (and then trying to drum up community goodwill by "releasing" an open source tool) is not the same thing as generating revenue. https://github.com/Azure/peerd does not have a "pricing" section.
Re:Getting Forked by Microsoft by lemper on Tuesday April 22, 2025 @01:17AM (#43759257)
yea, sure. but at least pay him for the "discussion". also, next time you people approach opensore maintainers, pay them for their time.
Re:Getting Forked by Microsoft by robertlagrant on Tuesday April 22, 2025 @05:53AM (#43760482)
The maintainers are adults too - they can set their price.
Re:Getting Forked by Microsoft by mixologic on Tuesday April 22, 2025 @01:27AM (#43759303)
> When you spoke with our engineers about implementing artifact streaming you said it was probably out of scope for Spegel at that time, which made sense.

It seems like it would have been a much better strategy to add artifact streaming, submit a pull request and then if the maintainer isn't interested in adding it, proceeding with a fork.

"Probably out of scope" sounds like "I dont have time to implement a feature of that scope"

Re:Getting Forked by Microsoft by dmurray on Tuesday April 22, 2025 @03:13AM (#43759772)
It sounds more like "I don't want to maintain a feature of that scope" or "I don't want to commit to the design decisions this feature would require". Both of those aren't solved by a PR.

If you're discussing with potential collaborators and want to communicate that you don't have time to develop such and such a feature but would be open to accepting a PR, it's very natural to say "I don't have time to develop this feature but would be open to accepting a PR".

Re:Getting Forked by Microsoft by spongebobstoes on Tuesday April 22, 2025 @02:41AM (#43759616)
"probably out of scope" sounds like "there would need to be some major refactors and you're the only user who wants it, so I am turning this down for now"

try to assume good faith :)

Re:Getting Forked by Microsoft by palata on Tuesday April 22, 2025 @07:11AM (#43760825)
> It seems like it would have been a much better strategy

Better for whom? Now there is Peerd and Spegel that are different projects. Imagine if Microsoft had opened PRs into Spegel and the maintainer had merged them. Then at some later point Microsoft had decided that they need to have ownership of that project (maybe because they want to have the control over what gets merged into the project because they depend on it). Imagine this ended up with a Microsoft fork of Spegel, becoming more popular than the original one. What would people say?

Probably something along the lines of "embrace, extend, extinguish", right?

Re:Getting Forked by Microsoft by simultsop on Tuesday April 22, 2025 @02:03AM (#43759457)
These practices have been an ongoing matter since 1975.
Re:Getting Forked by Microsoft by zoobab on Tuesday April 22, 2025 @06:18AM (#43760600)
Considering how Microsoft behaved regarding copyright violations in the past, the original author should at least ask damages in court.

We could even crowdfund the lawsuit, I am sure he will win.