3 ms·
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 o
by 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. :)