Share the control of the project with the community

Question

Share the control of the project with the community

Closed this issue 7 years ago · 13 comments

abatishchev commented 7 years ago

Hi,
I'm eager to pick it up and become a community maintainer for this project.
Please respond.
Thanks!

Answer 1 · 2017-09-21T23:12:21.000Z

It looks like Noah has been silent on github for almost 2 years. Shall we fork this?

Answer 2 · 2017-09-21T23:58:48.000Z

It's probably the safest, or go poke someone on Visual Studio to actually add this as an option :)

FYI, since it's never been explicitly discussed here: my problem with updating the project definitions at this point is it breaks back-compat, and I'm not really excited about any of the options there. It's probably time to just let VS2010 go, but it's a hard one.

Answer 3 · 2017-09-22T00:03:55.000Z

More importantly: there's a twitter thread discussing passing ownership of one of my extensions to someone else. I'd like to pass them all to someone, though I'm not sure who in particular.
https://twitter.com/Nick_Craver/status/879058897335660546

There was also a thread where someone told me they could pass ownership, but I can't find it anymore. It's a one-off thing the marketplace people can do.

Answer 4 · 2017-09-22T00:04:45.000Z

Yes, that's what I observed too. Packages built from the manifest schema v1 still shows an incompatibility warning. But v2 would likely break the backward compatibility.

I'd go ahead, fork it if you don't mind and build from v2. Or break it without forking. I think many people still use VS 2015 but not 2010-2013. Anyway it's a one time installation, you don't need to update this extension over time, or anything like that.

Answer 5 · 2017-09-22T00:06:30.000Z

Looks like this has been brought up on uservoice multiple times. I found one that hasn't been closed by admins yet. Vote for it people!

https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/19411234-provide-an-option-to-lock-or-disable-text-zoom-in

Answer 6 · 2017-09-22T00:15:22.000Z

It needs to be updated with each release of Visual Studio (or has in the past) to add the new supported version to the manifest. That's mostly what I've gotten tired of: getting my windows VM all working again with a new version of visual studio just to rebuild and test it :-/

Answer 7 · 2017-09-28T10:23:31.000Z

or go poke someone on Visual Studio to actually add this as an option :)

Unfortunately that's been tried. All of the UserVoice suggestions I could find have been closed or ignored.

I'd like to pass them all to someone, though I'm not sure who in particular.

I don't know about all of your extensions, but I think this one would fit nicely in Productivity Power Tools. Sadly that repository doesn't seem to be very active and they only accept bug fixes. 😞

That's mostly what I've gotten tired of: getting my windows VM all working again with a new version of visual studio just to rebuild and test it :-/

If that's all that's stopping you, then I'd be happy to build and test it, and let you publish it.

As far as backwards compatibility is concerned, you could always give the extension a new identifier and publish it as a new extension. That would at least keep the VS 2015 and lower versions working and in the marketplace.

Answer 8 · 2017-09-30T18:47:11.000Z

If you’d test and confirm it works, I can upload the new version.

…

On Thu, Sep 28, 2017 at 3:23 AM reduckted ***@***.***> wrote: or go poke someone on Visual Studio to actually add this as an option :) Unfortunately that's been tried. All of the UserVoice suggestions I could find have been closed <https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/4301986-allow-user-to-deactivate-ctrl-mousewheel-for-zoo> or <https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/3381468-setting-to-disable-scroll-wheel-font-size-zoom> ignored <https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/19411234-provide-an-option-to-lock-or-disable-text-zoom-in> . I'd like to pass them all to someone, though I'm not sure who in particular. I don't know about all of your extensions, but I think this one would fit nicely in Productivity Power Tools <https://github.com/Microsoft/VS-PPT>. Sadly that repository doesn't seem to be very active and they only accept bug fixes. 😞 That's mostly what I've gotten tired of: getting my windows VM all working again with a new version of visual studio just to rebuild and test it :-/ If that's all that's stopping you, then I'd be happy to build and test it, and let you publish it. As far as backwards compatibility is concerned, you could always give the extension a new identifier and publish it as a new extension. That would at least keep the VS 2015 and lower versions working and in the marketplace. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGn8sr6EMcPO8AYQ_Y5rKP5eXvKj1jAks5sm3OjgaJpZM4O6nTD> .

Answer 9 · 2017-09-30T19:01:49.000Z

Also turns out I already have VS2015 installed from the last time I updated, so I can at least rebuild the release vsix myself. And I may have to explicitly remove 10.0 support, I'm not sure what the gallery requires.

Answer 10 · 2017-10-02T03:16:29.000Z

I've just made PR #8 that adds full support for VS 2017. PR #5 that was merged recently didn't allow the extension to be installed in 2017 (it said it wasn't compatible). Perhaps things have changed in VS since that PR was opened.

Anyway, as I say in the PR, I've made it work back to VS 2013 (as far as I'm aware), but I don't actually have VS 2013 installed to test that out. If anyone does want to test it out in VS 2013 that would be great.

Alternatively, if you wanted to drop support for older Visual Studio versions, but still make the extension available, you could always upload the old extension file as a "release" in this project.

Answer 11 · 2017-10-05T02:50:33.000Z

I've updated the gallery, it hasn't gone live yet though. Please let me know if it works for you.

I installed it locally on VS2013 and it seems fine. My installer refused to install on VS2017, said it had missing prerequisites.

Answer 12 · 2017-10-05T03:20:04.000Z

I've installed it in Visual Studio 2017 (via the Extensions and Updates dialog). It installed fine and works perfectly. It also installed in Visual Studio 2015 and works fine in that too.

Thank you @NoahRic! I'm sure I speak for everyone here when I say that I really appreciate this.

Answer 13 · 2017-10-06T16:59:06.000Z

Worked for me for both 2015 and 2017. Thank you very much!

P.S.
What would we decide on the ownership? Are you interested in continuing solely maintain it? Or rather would prefer some community members to do that with you?