mjcrouch
Thanks
Hey Matt, thanks for taking over of this extension. I've look at the changelog, and I see you have pull a lot of work over the last few months.
Would you be interested in taking over the ownership and the active development of this project ?
Let me know what you think. We can discuss in https://gitter.im/stef-levesque/vscode-perforce
Hi, Thanks for getting in touch - I wasn't sure you would return :)
This is something I've been wondering about - on one hand I did fork the extension thinking it could be merged back in. Your extension is listed in various places such as on the vscode source control page and somewhere on the perforce website, so on balance it would probably be beneficial for all the existing users and people coming to vs code who might not be aware of this one
On the other hand there is more new code than original (the *.ts files are about 3x the number of characters, and that's excluding the tests!). From mainly a selfish perspective I quite like having the 'clean slate' of this repo, which also has my name on it :). It would be a not insignificant (though on the scale of things relatively small) bit of work to pull everything over, clean up some references to my repo, rewrite parts of the readme, set up the CI etc. The organic growth means I have been less concerned about breaking things or introducing larger changes as if I had picked up x0,000 existing users in one day as I know people installing the fork are consciously making that decision. Actually I was surprised at how quickly the number of installs has grown
Overall I should probably say yes but I'm not fully decided as I'm rather attached to this one :D - will consider some more
No problem, take your time to think about it.
Le 5 mai 2020 à 02:58, Matt Crouch [email protected] a écrit :
Hi, Thanks for getting in touch - I wasn't sure you would return :)
This is something I've been wondering about - on one hand I did fork the extension thinking it could be merged back in. Your extension is listed in various places such as on the vscode source control page and somewhere on the perforce website, so on balance it would probably be beneficial for all the existing users and people coming to vs code who might not be aware of this one
On the other hand there is more new code than original (the *.ts files are about 3x the number of characters, and that's excluding the tests!). From mainly a selfish perspective I quite like having the 'clean slate' of this repo, which also has my name on it :). It would be a not insignificant (though on the scale of things relatively small) bit of work to pull everything over, clean up some references to my repo, rewrite parts of the readme, set up the CI etc. The organic growth means I have been less concerned about breaking things or introducing larger changes as if I had picked up x0,000 existing users in one day as I know people installing the fork are consciously making that decision. Actually I was surprised at how quickly the number of installs has grown
Overall I should probably say yes but I'm not fully decided as I'm rather attached to this one :D - will consider some more
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Hi! I have a third option here. I'm the current maintainer of vscode-hg, which provides Mercurial SCM extension for vscode.
I was wondering if it would be beneficial for us SCM extension developers to have a common github organization, something like 'vscode-scm-extensions'. We could then propose this idea to other SCM extension devs, like https://github.com/JohnstonCode/svn-scm/ and https://github.com/OpenNingia/vscode-clearcase
What do you think?
