Visual Studio Productivity Power Tools Open-Sourced
1–10 of 23 posts
Re: Visual Studio Productivity Power Tools Open-Sourced
#2"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
[1] https://github.com/Microsoft/VS-PPT/commit/a243e09441d29b9f4...
[2] https://github.com/Microsoft/VS-PPT/blob/a243e09441d29b9f4c4...
Re: Visual Studio Productivity Power Tools Open-Sourced
#3"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 com…
well your fork will still have the feature, regardless of whether M$ accepts the pull request or not
Re: Visual Studio Productivity Power Tools Open-Sourced
#4"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 com…
No rub. The code is there, legally usable, and demonstrates useful examples.
Re: Visual Studio Productivity Power Tools Open-Sourced
#5"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 com…
well your fork will still have the feature, regardless of whether M$ accepts the pull request or not
> ...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.
Re: Visual Studio Productivity Power Tools Open-Sourced
#6"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 com…
No rub. The code is there, legally usable, and demonstrates useful examples.
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.
Re: Visual Studio Productivity Power Tools Open-Sourced
#7"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 com…
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
Re: Visual Studio Productivity Power Tools Open-Sourced
#8Earlier quoted context omitted.
No rub. The code is there, legally usable, and demonstrates useful examples.
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.
> This offering is significantly less substantial than it would appear at first glance
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.
Re: Visual Studio Productivity Power Tools Open-Sourced
#9Earlier quoted context omitted.
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.
> This offering is significantly less substantial than it would appear at first glance 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.
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.
Re: Visual Studio Productivity Power Tools Open-Sourced
#10"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 com…
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…
> 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. :)