Make clearer the people involved in BSP

Author: jvican

blog/_posts/2018-06-15-bsp.md

@@ -1,24 +1,23 @@
 ---
 layout: blog-detail
 post-type: blog
-by: Jorge Vicente Cantero
+by: Jorge Vicente Cantero, Justin Kaeser and Ólafur Páll Geirsson
 title: "Announcing the Build Server Protocol v1.0.0"
 ---
 
-I've always been convinced that the choice of an editor, IDE or build tool is
-personal and, therefore, asking you to go out of your way to learn a new tool
-to write Scala is not a viable solution. First, because changing people's
-habits is difficult and takes time. Second, it frustrates beginners who just
-want to learn the language. Last, it distracts seasoned developers from
-writing good Scala code until they master their toolchain. In the worst case,
-people will give up and not learn the language because the "cognitive
-overhead" would be too high.
+The choice of an editor, IDE or build tool is personal and, therefore, asking
+you to go out of your way to learn a new tool to write Scala is not a viable
+solution. First, because changing people's habits is difficult and takes time.
+Second, it frustrates beginners who just want to learn the language. Last, it
+distracts seasoned developers from writing good Scala code until they master
+their toolchain. In the worst case, people will give up and not learn the
+language because the "cognitive overhead" would be too high.
 
 Instead it is much better if we, tooling developers, can bear the burden of
 shipping tools that integrate with your existing workflow and you, as a user,
 can just install them with a quick search and a single click.
 
-Today, I introduce the Build Server Protocol, a project that I believe plays
+Today, we introduce the Build Server Protocol, a project that we believe plays
 a fundamental role in bringing us closer to making this vision a reality.
 
 ## Any IDE, Any Build Tool
@@ -81,20 +80,18 @@ alongside LSP.
 
 ## The Build Server Protocol v1.0.0
 
-Today I'd like to announce `v1.0.0` of the Build Server Protocol. This
-version has been the result of a fruitful collaboration between the Scala
-Center (me and [Ólafur Páll Geirsson][olafurpg]) and [Justin
-Kaeser][jastice], the [JetBrains] developer responsible for sbt support in
-[IntelliJ IDEA].
+Today we have released `v1.0.0` of the Build Server Protocol. This version has
+been the result of a fruitful collaboration between the Scala Center ([Jorge
+Vicente Cantero][jvican] and [Ólafur Páll Geirsson][olafurpg]) and JetBrains
+([Justin Kaeser][jastice]).
 
-Justin and I have spent the past months implementing a prototype of the Build
-Server Protocol between [IntelliJ IDEA] (client) and [Bloop] (server). Bloop
-is a build-tool-agnostic compilation server that integrates with build tools
-such as [sbt], [mill] or [Maven] to allow you [to compile, test and run your
+We have spent the past months implementing a prototype of the Build Server
+Protocol between [IntelliJ IDEA] (client) and [Bloop] (server). Bloop is
+a build-tool-agnostic compilation server that integrates with build tools such
+as [sbt], [mill] or [Maven] to allow you [to compile, test and run your
 applications much faster and outside of your stock build
-tool](https://www.scala-lang.org/blog/2017/11/30/bloop-release.html). Bloop
-has a client-server architecture, so it is the perfect project to implement
-BSP.
+tool](https://www.scala-lang.org/blog/2017/11/30/bloop-release.html). Bloop has
+a client-server architecture, so it is the perfect project to implement BSP.
 
 The goal of this prototype was two-fold. On the one hand, we wanted to
 experience first-hand the challenges of implementing BSP and learn new
@@ -174,7 +171,7 @@ IntelliJ's BSP import for Bloop and other build tools. The goal is to bring
 BSP import to a production-ready level where users can benefit from a
 build-tool-agnostic import project that is both faster and more reliable.
 
-Second, I'd like to invest some resources in creating a better synergy
+Second, we'd like to invest some resources in creating a better synergy
 between build tool authors and IDE implementors. The [Scala Tooling Protocols
 Working Group](https://github.com/scalacenter/tooling-working-groups/)
 created by [Jon
@@ -183,18 +180,17 @@ ago will help us discuss and refine the protocol so that all tooling
 developers in our community can implement the protocol at scale and gain more
 experience from this process.
 
-Third, I'd like to collaborate more closely with developers working on Scala
+Third, we'd like to collaborate more closely with developers working on Scala
 language servers like [Metals] or [Dotty IDE] to bring Scala support to all
 editors. There is a big chunk of Scala developers that don't use IntelliJ and
-I'd like to make sure that they benefit from a smooth developer experience
+we'd like to make sure that they benefit from a smooth developer experience
 too.
 
-
-Last but not least, I'd like to reach out to folks in other programming
+Last but not least, we'd like to reach out to folks in other programming
 language communities to find out ways we can pull our efforts together.
 The Build Server Protocol is **a language-agnostic protocol that can be
-modified to add support for any programming language** and I would love to
-see other communities improving the future of the build tools and IDE
+modified to add support for any programming language** and we would love to see
+other communities improving the future of the build tools and IDE
 communication.
 
 ## How to get involved
@@ -211,17 +207,6 @@ like to help test the integrations, join our
 [`scalacenter/bsp`](https://gitter.im/scalacenter/bsp) Gitter channel and
 let's discuss ways we can work together.
 
-## Acknowledgements
-
-I'd like to thank my colleague at the Scala Center, Ólafur Páll Geirsson, for
-being the co-author of the Build Server Protocol. His help and insights, as
-well as his detailed understanding of [LSP], have been fundamental in
-designing BSP and focusing on the ergonomics of the clients (IDEs) first.
-
-Finally, I'd like to thank Justin Kaeser and, more broadly, JetBrains for
-being part of this initiative. I am optimistic our collaboration can lead to
-better and faster developer tools for the broad of the Scala community.
-
 [sbt]: https://www.scala-sbt.org/
 [Maven]: http://maven.apache.org/
 [Bazel]: https://bazel.build
@@ -237,4 +222,4 @@ better and faster developer tools for the broad of the Scala community.
 [Metals]: https://github.com/scalameta/metals
 [Dotty IDE]: https://dotty.epfl.ch/docs/usage/ide-support.html
 [olafurpg]: https://github.com/olafurpg
-[bloop-instructions]: https://scalacenter.github.io/bloop/docs/installation/#generate-configuration-files-for-your-project
+[bloop-instructions]: https://scalacenter.github.io/bloop/docs/installation/#generate-configuration-files-for-your-project