[Tracking Issue] Sprint 6

[ekeren]

The primary goal of this sprint is to create a self service journey from someone who doesn't have access to wing repo into someone that has all that she needs in order to contribute or use Wing

This is a tracking issue for sprint 6 story

In the end of the Sprint we would like to Demo the following User stories

• Signup flow - the user journey from winglang.io into github.com/winglang/wing and our slack channel
• Contribution Flow -
  1. Going over the contributing guide
  2. Selecting good first issue
  3. Building
  4. Consulting the SDK docs
• Opening a bug/enhancement

p1

• Wing blog #336
• monadahq/winglang#335
• Remove reference to playground in README #348
• Winglang Slack #342
• Issue templates #347
• good-first-issues review  #346
• Contribution guide #344
• contributing guide QA #345
• Wing logo #337
• Move to winglang Github Org #152
• Signup Process #340
• Working instructions in README.md on how to install the wing VScode extention #363
• monadahq/wing-console#125
• Onboarding form #341

p2

• Releases: add a comment on issues when they are released #404
• REPL simulator #392
• monadahq/winglang#343
• A slack channel to celebrate first time project builders #350
• monadahq/wing-console#124
• Post-onbording survey #367

p3

• Compile the examples as part of the build process #351
• dogfood wing: first respond to an issue/pull request monitor #352
• pull request response monitor #353
• good first issues monitor #354
• onboarding feedback form #355
• README demo video #338
• compiler error for missing winglang implementation  #349

Moved to next sprint

[ekeren]

sprint is finished