Taking over maintenance?

[ChrisChinchilla]

@dfinke For some time I've wanted to create a VS Code extension as good as this old one for Atom, which was one of the only reason I kept Atom installed on my machine.

I came across your VSC extension, which is a really great start, but misses all the options that Pandoc offers and it looks like you're not maintaining this anyway.

So do you mind if I make a fork? Either to update this extension with new features, or take over maintenance of this one?

[dfinke]

Sounds great @ChrisChinchilla. Go for it.

[ChrisChinchilla]

@dfinke Thanks! In the space of an hour I've already managed to add many more options. I'll be in touch with a PR soon and we can talk about if the "official" extension becomes a new fork, or just merge my PRs, or whatever suits you.

[ChrisChinchilla]

@dfinke I made a PR for now, but let me know if you'd rather I took some of the other steps I mentioned above instead, whatever you want is fine with me.

[dfinke]

Thanks @ChrisChinchilla. I haven't touched this project in a number of years. I don't have the time to work with it, and figure out how to publish it etc. Happy to let you take it and run with it. Happy to have you pick it up and run with it from here.

[ChrisChinchilla]

@dfinke OK, no worries, the easiest way I have found to do this, is you unpublish your extension and add a depreciation warning, and then I republish a fork. I'll update the read me to acknowledge your work etc and then publish it again asap.

I haven't found a better way to do this yet sadly :/

I'll get my side ready now

[dfinke]

Yeah, not sure when I'll be able to get thru that.

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: Chris Chinchilla notifications@github.com Sent: Wednesday, April 22, 2020 10:52:23 AM To: dfinke/vscode-pandoc vscode-pandoc@noreply.github.com Cc: Doug Finke finked@hotmail.com; Mention mention@noreply.github.com Subject: Re: [dfinke/vscode-pandoc] Taking over maintenance? (#41)

@dfinkehttps://github.com/dfinke OK, no worries, the easiest way I have found to do this, is you unpublish your extension and add a depreciation warning, and then I republish a fork. I'll update the read me to acknowledge your work etc and then publish it again asap.

I haven't found a better way to do this yet sadly :/

I'll get my side ready now

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dfinke/vscode-pandoc/issues/41#issuecomment-617827959, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAQNOWRYG5GIOTQUTCJIUDRN4ACPANCNFSM4MFONWZA.

[ChrisChinchilla]

It takes a couple of minutes, in the meantime I can publish my fork anyway for anyone who finds it.

[dfinke]

Unfortunately, I don't have my key, I have a new box without the cli for that, so ...

[ChrisChinchilla]

Ahhh, hmm, maybe I'll see if there's someone I can ask about it 🤔

[l3d00m]

I added a big notice to the Readme about this fork in #43, I'd be great if you could find the time to merge @dfinke. Otherwise a lot of people won't find the actively maintained fork.

After that you could also archive this repository so that you won't get anymore issues/PRs here: https://docs.github.com/en/free-pro-team@latest/github/creating-cloning-and-archiving-repositories/archiving-repositories

[orschiro]

@l3d00m thanks for continue maintaining! Where can I find and install your fork?

[l3d00m]

@orschiro I'm not the maintainer, @ChrisChinchilla is it. You can find his extension on the marketplce though :) https://marketplace.visualstudio.com/items?itemName=chrischinchilla.vscode-pandoc

[orschiro]

Thanks @l3d00m :)

[goyalyashpal]

https://github.com/ChrisChinchilla/vscode-pandoc/issues/16