New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding commerical products to the list #222
Comments
Hi @lannonbr, I agree with you - we don't have any direct rule about commercial products. However, awesome lists are for awesome stuff, and for something commercial it's tough to understand the quality. We've rushed addition a bit + we didn't include the commercial badge, and that's why I pulled it. My suggestion:
|
@ #1. url `) |
On Sat, Feb 1, 2020 at 2:01 AM udaytejareddy ***@***.***> wrote:
[__](`
-
@ #1 <#1>. url
Duplicate of #
`) come on
—
… You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#222?email_source=notifications&email_token=AK5I6OGKLISFLW33KGAQOR3RAUM33A5CNFSM4GGFB4J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQWFII#issuecomment-581001889>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK5I6OBCDKJ5PM2VCRMF2EDRAUM33ANCNFSM4GGFB4JQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There may be paid VS Code extensions or content that could be beneficial to list here. Currently there is no direct notice in the contributing guide that submissions should only be publicly available / free resources, so I think at least it would be good to update the guide with our stance on it.
I do think pushing free resources first should be a priority, but if there is a paid resource that could bring benefits to the greater VS Code community by putting it in the list, it could at least be discussed if it should be added between the repo maintainers and if accepted be extremely blatant in the list that it is a commercial resource.
What does everyone else think about this?
The text was updated successfully, but these errors were encountered: