5 ms·

"Note that this repository currently contains a subset of all extensions in Productivity Power Tools for Visual Studio 2015. This subset represents extensions w

"Note that this repository currently contains a subset of all extensions in Productivity Power Tools for Visual Studio 2015. This subset represents extensions which we believe can serve as great real world samples of extending Visual Studio." [0] Yep. There's the rub. Also, as a bit of trivia, the first substantial commit was back in December [1]. The next commit was ~5 days ago. Edit: Additionally, this is their committer policy: "Contributions beyond the level of a bug fix are reserved for Microsoft PPT members or they will be declined." [2] So, if you've something substantial to add, you don't get to actually contribute to the repo. [0] https://github.com/Microsoft/VS-PPT/wiki/Overview https://github.com/Microsoft/VS-PPT/wiki/Overview [1] https://github.com/Microsoft/VS-PPT/commit/a243e09441d29b9f4c42f4a4ea653329dd8ca8d7 https://github.com/Microsoft/VS-PPT/commit/a243e09441d29b9f4... [2] https://github.com/Microsoft/VS-PPT/blob/a243e09441d29b9f4c42f4a4ea653329dd8ca8d7/CONTRIBUTING.md https://github.com/Microsoft/VS-PPT/blob/a243e09441d29b9f4c4...

francium_ 11y ago
well your fork will still have the feature, regardless of whether M$ accepts the pull request or not
- simoncion 11y ago
  > ...regardless of whether M$ accepts the pull request or not They've already said that they won't accept the pull request, so... > well your fork will still have the feature... ...we're left with what will potentially be a sea of forks, with no clear "best fork". Some might say that this isn't a big deal, but it is a significant point of friction.
  - nurettin 11y ago
    I'm sorry if this comes through as offensive, but I would very much like to see all your points and research about the subject of this matter condensed into a single concise blog post and submitted to HN (if you've not already done so) instead of reading it from sporadic replies throughout the comments section of the related article(s).
jabits 11y ago
No rub. The code is there, legally usable, and demonstrates useful examples.
- simoncion 11y ago
  MSFT is currently engaged in a PR war. This offering is significantly less substantial than it would appear at first glance... the sort of first and only glance a harried tech reporter would make.
  - taspeotis 11y ago
    > This offering is significantly less substantial than it would appear at first glance https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/open-sourcing-the-visual-studio-productivity-power-tools/ https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/ope... > The repository currently contains a subset of all extensions in Productivity Power Tools for Visual Studio 2015. Some extensions are not yet ready to be open-sourced, but we’re working on making all of them available over time.
    - ChristianGeek 11y ago
      Are you guys serious? While you all are bitching about the fact that less than half the extensions are currently missing, the rest of us are going to enjoy playing with and learning from the ones that are there.
      - taspeotis 11y ago
        > Are you guys serious? While you all are bitching... Uh, there's only one user bitching. Everybody else seems fine with it.
        simoncion 11y ago
        > Uh, there's only one user bitching. I'm not bitching about anything. I'm providing a contrary view to the effusive and largely uncritical praise that much of the tech press spews whenever MSFT announces that they've open sourced this tiny thing, or ported a part of that thing to a non-Windows OS. If you read my other comments elsewhere on this page, it becomes clear that I very much want for MSFT to have stopped bullying, subverting (and impeding the function of) standards bodies, engaging in anticompetitive lock-out, and other such shady backroom dealings. MSFT is a big company that hires rather smart people. They could use their money and collective brainpower to do really great things for the computing community. Thing is, those of us who've been around for at least the past twenty years have seen the "Good Microsoft" act, and we remember how that act was rather short-lived. If MSFT were to do something substantially significant (such as joining the OIN [0], making a public promise to remain a member and substantially participate in its proceedings for the next twenty years, as well as a public promise to never tamper with it or its proceedings [1]) before many of us old hands start thinking that this is an actual change in corporate direction. [0] http://www.openinventionnetwork.com/ http://www.openinventionnetwork.com/ [1] That is, to never, ever do anything even remotely like the shit they did at ISO.
timsneath 11y ago
Sorry about the contributions text - that's a little unartfully expressed. Our plan in open sourcing these extensions was both to provide some useful examples of extending Visual Studio and to be a starting point for others to create and manage new extensions based on this work. We wanted to get these out as open source first and foremost, and we're really interested in learning how people use them. Our conservatism in accepting contributions springs out of that goal. If it's clear that there's strong interest in developing these further, we're willing to revisit that. And just in response to the trivia, we switched the entire Visual Studio repo to git, hosted on Visual Studio Team Services, after we shipped Visual Studio 2015. We've been developing VS-PPT in that repo before moving it to GitHub, so hopefully that explains the long gap in the commit history. We're listening! Thanks, Tim Sneath | Visual Studio Team
- simoncion 11y ago
  > And just in response to the trivia... Oh, that wasn't directed at you, it was directed at the HN submitter and his choice of title. The history of my project repos is shot through with huge sections where nothing at all happens. That's just how these things go. > We're listening! Good! I hope your corporate overlords let you meaningfully act on the feedback that you receive and -more crucially- continue to act on that feedback for decades after the PR halo subsides. I guess we'll see what happens in the upcoming half-decade or two. :)
deleted 11y ago
[deleted]
GFK_of_xmaspast 11y ago
> "Contributions beyond the level of a bug fix are reserved for Microsoft PPT members or they will be declined." [2 What's so wrong about that?

francium_ 11y ago

well your fork will still have the feature, regardless of whether M$ accepts the pull request or not

simoncion 11y ago
> ...regardless of whether M$ accepts the pull request or not They've already said that they won't accept the pull request, so... > well your fork will still have the feature... ...we're left with what will potentially be a sea of forks, with no clear "best fork". Some might say that this isn't a big deal, but it is a significant point of friction.
- nurettin 11y ago
  I'm sorry if this comes through as offensive, but I would very much like to see all your points and research about the subject of this matter condensed into a single concise blog post and submitted to HN (if you've not already done so) instead of reading it from sporadic replies throughout the comments section of the related article(s).

jabits 11y ago

No rub. The code is there, legally usable, and demonstrates useful examples.

simoncion 11y ago
MSFT is currently engaged in a PR war. This offering is significantly less substantial than it would appear at first glance... the sort of first and only glance a harried tech reporter would make.
- taspeotis 11y ago
  > This offering is significantly less substantial than it would appear at first glance https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/open-sourcing-the-visual-studio-productivity-power-tools/ https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/ope... > The repository currently contains a subset of all extensions in Productivity Power Tools for Visual Studio 2015. Some extensions are not yet ready to be open-sourced, but we’re working on making all of them available over time.
  - ChristianGeek 11y ago
    Are you guys serious? While you all are bitching about the fact that less than half the extensions are currently missing, the rest of us are going to enjoy playing with and learning from the ones that are there.
    - taspeotis 11y ago
      > Are you guys serious? While you all are bitching... Uh, there's only one user bitching. Everybody else seems fine with it.
      - simoncion 11y ago
        > Uh, there's only one user bitching. I'm not bitching about anything. I'm providing a contrary view to the effusive and largely uncritical praise that much of the tech press spews whenever MSFT announces that they've open sourced this tiny thing, or ported a part of that thing to a non-Windows OS. If you read my other comments elsewhere on this page, it becomes clear that I very much want for MSFT to have stopped bullying, subverting (and impeding the function of) standards bodies, engaging in anticompetitive lock-out, and other such shady backroom dealings. MSFT is a big company that hires rather smart people. They could use their money and collective brainpower to do really great things for the computing community. Thing is, those of us who've been around for at least the past twenty years have seen the "Good Microsoft" act, and we remember how that act was rather short-lived. If MSFT were to do something substantially significant (such as joining the OIN [0], making a public promise to remain a member and substantially participate in its proceedings for the next twenty years, as well as a public promise to never tamper with it or its proceedings [1]) before many of us old hands start thinking that this is an actual change in corporate direction. [0] http://www.openinventionnetwork.com/ http://www.openinventionnetwork.com/ [1] That is, to never, ever do anything even remotely like the shit they did at ISO.

timsneath 11y ago

Sorry about the contributions text - that's a little unartfully expressed. Our plan in open sourcing these extensions was both to provide some useful examples of extending Visual Studio and to be a starting point for others to create and manage new extensions based on this work. We wanted to get these out as open source first and foremost, and we're really interested in learning how people use them. Our conservatism in accepting contributions springs out of that goal. If it's clear that there's strong interest in developing these further, we're willing to revisit that. And just in response to the trivia, we switched the entire Visual Studio repo to git, hosted on Visual Studio Team Services, after we shipped Visual Studio 2015. We've been developing VS-PPT in that repo before moving it to GitHub, so hopefully that explains the long gap in the commit history. We're listening! Thanks, Tim Sneath | Visual Studio Team

simoncion 11y ago
> And just in response to the trivia... Oh, that wasn't directed at you, it was directed at the HN submitter and his choice of title. The history of my project repos is shot through with huge sections where nothing at all happens. That's just how these things go. > We're listening! Good! I hope your corporate overlords let you meaningfully act on the feedback that you receive and -more crucially- continue to act on that feedback for decades after the PR halo subsides. I guess we'll see what happens in the upcoming half-decade or two. :)

deleted 11y ago

[deleted]

GFK_of_xmaspast 11y ago

> "Contributions beyond the level of a bug fix are reserved for Microsoft PPT members or they will be declined." [2 What's so wrong about that?