@@ -121,22 +121,49 @@ repository](https://github.com/scalacenter/tooling-working-groups/blob/master/me
121
121
122
122
I made a proposal during the meeting that the next steps should include the
123
123
election of two working groups to take forward ideas for an implementation of
124
- LSP for Scala, and a second "protocols " group for defining other non-LSP
125
- protocols for Scala. These groups should have,
124
+ LSP for Scala, and a second "Scala Tooling Protocols " group for defining other
125
+ non-LSP protocols for Scala. These groups should have,
126
126
127
- - 6-8 members in each
127
+ - 6-9 members in each
128
128
- some overlap in membership between the two groups
129
129
- a mix of experts (more experience than free time) and enthusiasts (more free
130
130
time than experience)
131
131
- diverse representation of a variety of existing projects
132
- - at least one member from the Scala Center
132
+ - at least one member from the Scala Center, but not overrepresentation
133
133
134
134
As an open-source project, the dynamics of a disparate collection of developers
135
135
is often better suited to innovation than shipping working software by a
136
136
deadline, and a large part of the challenge will be to keep everyone on track,
137
137
despite the freedom that Open Source grants us. We hope that that leadership
138
138
can come from the Scala Center.
139
139
140
+ ## Election Process
141
+
142
+ We want to encourage an open process for discussion of tooling for Scala. We
143
+ want to involve many diverse minds, and we want to be inclusive. In the past,
144
+ it has often been most expedient to invite a selection of known experts to take
145
+ part. This has largely led to technical success, but has made it harder for
146
+ many newcomers to engage with the Scala decision-making process. So to try to
147
+ improve upon this, and to give the working groups greater legitimacy, we will
148
+ be holding elections to choose the members of the LSP and STP working groups.
149
+ This will, in part, be an experiment, but we hope it signals greater openness
150
+ in how decisions which affect the entire Scala community are made.
151
+
152
+ If the Scala community had a list of its members, we could invite each member
153
+ to vote on the makeup of the working groups, but of course, that's not how the
154
+ community works. We also do not want to open an election up to anything that
155
+ could be so trivially compromised as an online poll.
156
+
157
+ We will therefore take an imperfect but pragmatic approach and open voting only
158
+ to those members of the Scala community who are willing to devote a small
159
+ amount of their time to participating in a series of live votes, conducted
160
+ online, which will take place on Wednesday, 28 February starting at 6pm GMT.
161
+ Full details of the rules governing this process are [ described
162
+ here] ( https://github.com/scalacenter/tooling-working-groups/blob/master/nominations/election.md ) .
163
+
164
+ We will announce the composition of the working groups after the voting
165
+ immediately after voting has finished.
166
+
140
167
## Becoming a Working Group Member
141
168
142
169
Sitting as a member on either of the working groups is an opportunity to
@@ -158,20 +185,10 @@ Candidates to the working group should be nominated by opening a pull request
158
185
to the [ scalacenter/tooling-working-groups
159
186
repository] ( https://github.com/scalacenter/tooling-working-groups ) , following
160
187
the [ instructions described
161
- here] ( https://github.com/scalacenter/tooling-working-groups/blob/master/nominations/README.md ) .
162
-
163
- ## Election Process
164
-
165
- If the Scala community had a list of its members, we could invite each member
166
- to vote on the working group members, but of course, that's not how the
167
- community works. Equally, we do not want to open an election up to anything
168
- that could be so trivially compromised as an online poll.
169
-
170
- We will therefore take an imperfect but pragmatic approach and open voting only
171
- to those members of the Scala community who are willing to devote a small
172
- amount of their time to participating in a series of live votes, conducted
173
- online, which will take place on Wednesday, 28 February at 6pm GMT. Full
174
- details of the process will be published on this website, soon.
188
+ here] ( https://github.com/scalacenter/tooling-working-groups/blob/master/nominations/README.md ) ,
189
+ and we strongly encourage anyone with an interest in Scala's tooling, and a
190
+ willingness to devote some time to participating in working group discussions
191
+ to be a candidate.
175
192
176
193
I will be giving a keynote about the future of Scala Tooling at [ Scala
177
194
Sphere] ( http://scala.sphere.it/ ) in April, a large conference in Kraków
@@ -180,10 +197,7 @@ to be making some exciting announcements there about our prospects for vastly
180
197
improved tooling support for Scala! Meanwhile, the working groups will have a
181
198
challenging task ahead of them, but with a their collective experience, the
182
199
energy and enthusiasm Scala's tooling contributors, and the support of the
183
- entire community, we can be more optimistic about that future than ever before.
184
-
185
-
186
-
187
-
200
+ entire community, we can be much more optimistic about that future than ever
201
+ before.
188
202
189
203
0 commit comments