7 ms·

I'm not trying to be lazy (ok maybe a little bit), but can someone please provide like a 3-4 sentence summary of what happened? Everything I've seen on this eit

I'm not trying to be lazy (ok maybe a little bit), but can someone please provide like a 3-4 sentence summary of what happened? Everything I've seen on this either assumes you already know, or is very long and rambly, or both.

heavyset_go 5y ago
Project maintainers had their projects moved from their public GitHub accounts to the DNF's GitHub Enterprise account without notice. Some maintainers only found out about the transfers of their projects because of this[1] discussion. [1] https://github.com/dotnet-foundation/Home/discussions/38 https://github.com/dotnet-foundation/Home/discussions/38
- flowerlad 5y ago
  So nothing changed with the source code or its licensing, only the location on github? That seems a bit inconsequential, tbh. Are there strings attached to the new location? If no, then move on.
  - kevin_b_er 5y ago
    You'd not say the same thing if the ownership of a domain changed hands quietly, in the background.
    - quickthrower2 5y ago
      That would be worse though. This is like a subdomain changing hands quietly. E.g. you mypage.github.io.
  - ethbr0 5y ago
    Per post, being part of a GitHub Enterprise organization grants the GEO's owners control over any projects contained in that organization. That's the change.
    - flowerlad 5y ago
      Thank you. That does seem consequential.
      - oaiey 5y ago
        Yeah and is not wrong for the foundation and the projects. It is the absolute lack of community, communication and tone deafness.
        robmen 5y ago
        Exactly.
  - heavyset_go 5y ago
    There were also pull requests that were merged despite maintainers' objections to merging.
    - robmen 5y ago
      That didn't happen to me and there was a pretty comprehensive (IMHO) apology about that issue.
  - arvindamirtaa 5y ago
    There are strings attached to the new location - the maintainers can (in theory) be kicked out of their own repositories.
- robmen 5y ago
  Technically speaking it wasn't that discussion. That discussion was opened after we started realizing what had (and had not) happened. But your summary is otherwise correct. :)
deleted 5y ago
[deleted]
deleted 5y ago
[deleted]
Permit 5y ago
Many projects joined the .NET Foundation after it was created. It didn't really do anything for them (I think they basically sponsor meetups), but it wasn't harming anyone either. The .NET Foundation asked for owner access on the author's repository (for a CLA bot). The author declined and a workaround was organized. Years later the .NET Foundation asked for "owner access" on the author's repository (to allow them enforce Code of Conduct across all repositories). The author declined. The CLA bot stopped working. The author was told it would work if he gave it owner access. The author was annoyed because they previously had a workaround. They gave in and gave @dnfadmin owner access (temporarily, it was later revoked after the CLA bot was set up, thanks /u/ethbr0 for the correction). Some time later the author realized that the project had now been silently moved to GitHub Enterprise (likely in the short window @dnfadmin had owner access). The author states that projects in GitHub Enterprise can be entirely controlled by the owner of the account (the .NET Foundation). This transfer happened silently. Independently, this happened to another project (who had coincidentally had an issue with a Microsoft employee and former contributor force a pull-request into their project: https://github.com/reactiveui/splat/pull/778 https://github.com/reactiveui/splat/pull/778). The change itself seems innocuous, but the approach bothered people. People are upset because of how tone-deaf all of this is. They would like the .NET Foundation to stop trying to gain complete control over the member projects. They would especially like for their projects not to have their ownership changed silently. Edit: For the record, I do not believe this is part of some embrace, extend, extinguish plan on behalf of Microsoft. I think these accusations actually cheapen what has happened here. I suspect this was more of a "can we make this process easier and more convenient for the .NET Foundation"-type thing. The people involved with this will have to do some soul searching. The .NET Foundation should operate in service of its member projects, not the other way around.
- ethbr0 5y ago
  > They gave in and gave @dnfadmin owner access Temporarily gave @dnfadmin access, is my read. > "The .NET Foundation had admin access to the WiX Toolset organization for a week, not more than a week ago"
  - Permit 5y ago
legohead 5y ago
I don't really know anything about this stuff but after reading the blog post I feel like I understand. It's a good read.
- robmen 5y ago
  Thanks, that is good to hear. I wasn't sure I would post it because I was afraid it would actually confuse the issue. Thank you.
robmen 5y ago
Maybe I should have added a tl;dr at the top? Writing the whole entry was challenging because there is a lot of detail I wanted to provide to being everyone along the journey. I've seen some people drop in at any isolated point and say, "Why is this a big deal?" Also I'll be the first to admit that when in story telling mode, I am not particularly terse. :)
Anon4Now 5y ago
Now you know what working with WiX is like.
- robmen 5y ago
  Hah, hah, hah, that's actually pretty good.

heavyset_go 5y ago

Project maintainers had their projects moved from their public GitHub accounts to the DNF's GitHub Enterprise account without notice. Some maintainers only found out about the transfers of their projects because of this[1] discussion. [1] https://github.com/dotnet-foundation/Home/discussions/38 https://github.com/dotnet-foundation/Home/discussions/38

flowerlad 5y ago
So nothing changed with the source code or its licensing, only the location on github? That seems a bit inconsequential, tbh. Are there strings attached to the new location? If no, then move on.
- kevin_b_er 5y ago
  You'd not say the same thing if the ownership of a domain changed hands quietly, in the background.
  - quickthrower2 5y ago
    That would be worse though. This is like a subdomain changing hands quietly. E.g. you mypage.github.io.
- ethbr0 5y ago
  Per post, being part of a GitHub Enterprise organization grants the GEO's owners control over any projects contained in that organization. That's the change.
  - flowerlad 5y ago
    Thank you. That does seem consequential.
    - oaiey 5y ago
      Yeah and is not wrong for the foundation and the projects. It is the absolute lack of community, communication and tone deafness.
      - robmen 5y ago
        Exactly.
- heavyset_go 5y ago
  There were also pull requests that were merged despite maintainers' objections to merging.
  - robmen 5y ago
    That didn't happen to me and there was a pretty comprehensive (IMHO) apology about that issue.
- arvindamirtaa 5y ago
  There are strings attached to the new location - the maintainers can (in theory) be kicked out of their own repositories.
robmen 5y ago
Technically speaking it wasn't that discussion. That discussion was opened after we started realizing what had (and had not) happened. But your summary is otherwise correct. :)

deleted 5y ago

[deleted]

deleted 5y ago

[deleted]

Permit 5y ago

Many projects joined the .NET Foundation after it was created. It didn't really do anything for them (I think they basically sponsor meetups), but it wasn't harming anyone either. The .NET Foundation asked for owner access on the author's repository (for a CLA bot). The author declined and a workaround was organized. Years later the .NET Foundation asked for "owner access" on the author's repository (to allow them enforce Code of Conduct across all repositories). The author declined. The CLA bot stopped working. The author was told it would work if he gave it owner access. The author was annoyed because they previously had a workaround. They gave in and gave @dnfadmin owner access (temporarily, it was later revoked after the CLA bot was set up, thanks /u/ethbr0 for the correction). Some time later the author realized that the project had now been silently moved to GitHub Enterprise (likely in the short window @dnfadmin had owner access). The author states that projects in GitHub Enterprise can be entirely controlled by the owner of the account (the .NET Foundation). This transfer happened silently. Independently, this happened to another project (who had coincidentally had an issue with a Microsoft employee and former contributor force a pull-request into their project: https://github.com/reactiveui/splat/pull/778 https://github.com/reactiveui/splat/pull/778). The change itself seems innocuous, but the approach bothered people. People are upset because of how tone-deaf all of this is. They would like the .NET Foundation to stop trying to gain complete control over the member projects. They would especially like for their projects not to have their ownership changed silently. Edit: For the record, I do not believe this is part of some embrace, extend, extinguish plan on behalf of Microsoft. I think these accusations actually cheapen what has happened here. I suspect this was more of a "can we make this process easier and more convenient for the .NET Foundation"-type thing. The people involved with this will have to do some soul searching. The .NET Foundation should operate in service of its member projects, not the other way around.

ethbr0 5y ago
> They gave in and gave @dnfadmin owner access Temporarily gave @dnfadmin access, is my read. > "The .NET Foundation had admin access to the WiX Toolset organization for a week, not more than a week ago"
- Permit 5y ago

legohead 5y ago

I don't really know anything about this stuff but after reading the blog post I feel like I understand. It's a good read.

robmen 5y ago
Thanks, that is good to hear. I wasn't sure I would post it because I was afraid it would actually confuse the issue. Thank you.

robmen 5y ago

Maybe I should have added a tl;dr at the top? Writing the whole entry was challenging because there is a lot of detail I wanted to provide to being everyone along the journey. I've seen some people drop in at any isolated point and say, "Why is this a big deal?" Also I'll be the first to admit that when in story telling mode, I am not particularly terse. :)

Anon4Now 5y ago

Now you know what working with WiX is like.

robmen 5y ago
Hah, hah, hah, that's actually pretty good.