Skip to content
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

{Work in Progress} Update faq.md #2431

Closed
wants to merge 9,849 commits into from
Closed

{Work in Progress} Update faq.md #2431

wants to merge 9,849 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Feb 22, 2019

Solving some FAQ issues so users don't have to waste time, think its weird. And developers can develop code.

mjbvz and others added 30 commits January 27, 2019 15:04
Update the gif for Java Test Runner
Updates to tutorial and editing articles
Update unit testing article, adding pytest
Add Python interactive window, fix link
Greg Van Liew and others added 11 commits February 20, 2019 08:58
Add showReuseMessage to Output behavior section
fixed small typo opening => open
fixed small typo opening => open
Java on VS Code Feb updates
The question originally answered nothing. Removed answer.

Add 1question and relevant answer. Done.
@ghost
Copy link

ghost commented Feb 22, 2019

maybe someone of the vscode team could fill in "It is unclear at this stage" with an exact & complete description of what the difference is? @ vs code developers: would be really nice to finally have some voices heard about our concerns with the lack of transparency and misleading statements (e.g. on the main landing page) regarding the two versions

@ghost
Copy link
Author

ghost commented Mar 7, 2019

Sorry. I made a huge mistake in the PR.

snow8gaia added 2 commits March 7, 2019 22:07
correct my mistake.
@msftclas
Copy link

msftclas commented Mar 7, 2019

CLA assistant check
All CLA requirements met.

Correct 2nd mistake.
@ghost ghost changed the title Update faq.md Update faq.md Mar 7, 2019
@ghost
Copy link
Author

ghost commented Mar 7, 2019

Fixed the huge mistake. Found some more.
And then, the CLA bot decided to showed up; signed the CLA.


[](Testing msftclas complexity)

is @msftclas overworked?

Make this helpful for everyone.
@ghost
Copy link

ghost commented Mar 7, 2019

@snow8gaia you appear to be making up statements here in place of Microsoft developers.

Some of these statements seem completely without value until a VS code dev actually says them, like We are dedicated to resolving this as soon as possible. Is anyone dedicated to that?

Even worse, why write something like TL;DR - We started out with this model, thought it would be open-source friendly. when you don't even know what they thought? Why make that up?

I would love to hear some of these things, but until we've had that discussion what you're doing here seems more like a work of wishful fiction than an accurate, useful text. If you got sources for these statements then I take everything back and apologize for the interference. Also, obviously that's just my two cents, I can't accept or reject anything in this repo I'm just a bystander of sorts

@ghost
Copy link
Author

ghost commented Mar 7, 2019

The CLA. It had two pages. Was definitely useless. I signed it because I am stupid sometimes more interested in ensuring that nobody else gets deceived


edit: not in response to JonasT 's post.

@ghost ghost changed the title Update faq.md {Work in Progress} Update faq.md Mar 7, 2019
@ghost
Copy link
Author

ghost commented Mar 11, 2019

@Jonast Thanks for feedback in #2431 (comment).

right now, this PR is like a test for whether or not there is any interest from the devs. Also, feel free to create a new PR to update the FAQ if you want to. And either use this PR as base, or start fresh.

@ghost
Copy link
Author

ghost commented Mar 11, 2019

@Jonast Thanks for feedback in #2431 (comment). I did not intend to make a bad PR.

right now, this PR is flawed. Also, don't hesitate to create a new PR to update the FAQ. And either use this PR as base, or start fresh. Or whatever you decide is best.

link to issues on vscode :- microsoft/vscode#17996
microsoft/vscode#60


I may not be able to keep this updated/complete it.

@gregvanl
Copy link

Hi @snow8gaia Unfortunately your PR was closed during our shrinking of the vscode-docs repo. You will need to re-clone vscode-docs, reapply your changes and submit another PR. Sorry for the inconvenience. The repo is now much smaller and you can use Git LFS if you like. See CONTRIBUTING for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.