Hello Fellow D'ers,

As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.

Additionally, until I cease working for Microsoft, I will no longer be contributing code to projects hosted on GitHub, including DLang and it's related projects. I will continue to contribute bug reports and post to the forums.

I will post a link to the new SecureD repo on this thread and update the DUB links once I have everything setup correctly post-move.

DISCLAIMER: The actions described herein are the result of my specific situation and not intended as a larger commentary on recent events. This message should not be considered legal advice in any way. Any Microsoft employees reading this thread should refer to their lawyers about their specific situation or concerns.

-- 
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;

On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
> Hello Fellow D'ers,
>
> As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.
>
> [...]

This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?

On 06/04/2018 11:55 PM, Joakim wrote:
> On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
>> Hello Fellow D'ers,
>>
>> As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.
>>
>> [...]
> 
> This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?

And this reads like someone who has never talked to a lawyer. :)

I am intentionally keeping this ambiguous as possible so that others don't try to take this as legal advice.

I'm guessing you live somewhere outside the US? For reference, I do live in the US.

-- 
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;

On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
> On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
>> Hello Fellow D'ers,
>>
>> As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.
>>
>> [...]
>
> This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?

Yes!
We support Github.

On 06/05/2018 12:28 AM, Brian wrote:
> On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
>> On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
>>> Hello Fellow D'ers,
>>>
>>> As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.
>>>
>>> [...]
>>
>> This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?
> 
> Yes!
> We support Github.

Note that I am not saying that this is bad move for Microsoft of GitHub. Elsewhere on these forums I have defended the move as the best possible outcome for GitHub.

-- 
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;

On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
>
> This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?

If you read between the lines, you can 'kinda' get the message.

A Microsoft employee.
A Microsoft platform.
Encryption.
U.S Export Controls.

How they all come together is anyones guess though ;-)

That's why we have lawyers.

On Tuesday, June 05, 2018 10:34:54 ExportThis via Digitalmars-d-announce wrote:
> On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
> > This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?
>
> If you read between the lines, you can 'kinda' get the message.
>
> A Microsoft employee.
> A Microsoft platform.
> Encryption.
> U.S Export Controls.
>
> How they all come together is anyones guess though ;-)
>
> That's why we have lawyers.

Given that he works on SecureD, that could be part of it, but I don't think that exporting encryption is the problem that it once was in the US, and I'd think that the issue was more likely related to what Microsoft can claim to own. In general in the US, if your employer can claim that what you're doing in your free time is related to what you do for work, then they can claim that they own it. And if you're in a state with fewer employee protections, they can even claim to own everything you do in your free time regardless of whether it really has anything to do with any company intellectual property (e.g. a coworker at a previous company told me of a coworker who had gone to work at Bloomberg in NY after the division he was in was laid off, but he quit Bloomberg soon therefafter, because Bloomberg was going to claim to own everything he did in his free time - and he was a Linux kernel developer, so that would have caused serious problems for him). What paperwork you signed for your employer can also affect this. So, the exact situation you're in can vary wildly depending on where you live, who you work for, what exactly you do at work, and what exactly you do in your free time. If you want to sort out exactly what situation you're in, you do potentially need to see a lawyer about it.

That whole set of issues may or may not be why Adam is moving his stuff to gitlab, but it does mean that you have to tread carefully when doing anything that relates at all to your employer or what you do for work. So, I can easily see it as a good idea to avoid doing anything in your free time with a site that is owned or operated by your employer. It may or may not actually be necessary, but playing it safe can avoid legal problems down the road, and typically, employees are going to have a _very_ hard time winning against employers in court, even if the employee is clearly in the right, simply because the legal fees stand a good chance of destroying the employee financially, whereas the employer can typically afford it. You simply don't want to be in a situation where your employer ever might try and do anything to you with the legal system - and of course, you don't want to be in a position where your employer fires you. So, an abundance of caution is sometimes warranted even if it arguably shouldn't need to be.

- Jonathan M Davis

On Tuesday, 5 June 2018 at 06:55:42 UTC, Joakim wrote:
> On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
>> Hello Fellow D'ers,
>>
>> As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.
>>
>> [...]
>
> This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?

I think it's the case of possible "use of company assets for non work related purposes", even if Github still remains open for everyone.

On Tue, Jun 05, 2018 at 06:55:42AM +0000, Joakim via Digitalmars-d-announce wrote:
> On Tuesday, 5 June 2018 at 06:45:48 UTC, Adam Wilson wrote:
> > Hello Fellow D'ers,
> > 
> > As some of you know I work for Microsoft. And as a result of the recent acquisition of GitHub by Microsoft, I have decided, out of an abundance of caution, to move all of my projects that currently reside on GitHub to GitLab.
> > 
> > [...]
> 
> This reads like a joke, why would it matter if you contributed to open source projects on an open platform that your employer runs?

Remember this phrase: conflict of interest.

It can land you in serious legal trouble when it involves your employer.


T

-- 
If it's green, it's biology, If it stinks, it's chemistry, If it has numbers it's math, If it doesn't work, it's technology.

On Tuesday, 5 June 2018 at 11:09:31 UTC, Jonathan M Davis wrote:
> [...]

Very informative. I don't live in the US, but this gives me a feeling of how tough life can be over there for everyone, except lawyers.