Indeed, we do use both an public and a private issue tracker. While we can't move everything public, as some of the issues may pertain to internal projects/security issues, we're looking at ways to make more of it public. It's
helpful for the community to be able to see and give feedback more easily, and it's also just less overhead on the team to manage two different trackers.
We're also looking to make our design discussions and notes public so that it's easier for the community to jump in. It's largely a historical why we're a little quiet, and we're moving to being more transparent so that we can work with everyone
else more closely.
When we went public, we knew that we were going to be previewing the technology and that it was some of the processes behind the scenes wouldn't be quite ready. Pull requests is another one we knew wasn't going to be quite ready, but we started actively
working towards them. Microsoft is very careful about the intellectual property rights of others, and there were a few steps we needed to take on our side to keep things to a high bar before jumping in and accepting patches.
Lastly, we'll likely not open source the VS add-in. The VS add-in isn't actually all that interesting, as almost all of the smarts are in the language service (minus the debugging support, which is internal). The language service
is open source and you can get it from the source repo.