clarify wording for trojan horsen

pull/977/head
Matthew Hodgson 7 years ago
parent 822d84e50c
commit cc6b6ea021

@ -173,13 +173,13 @@ toxic culture of bullying or competitive infighting. Folks need to be able to
compromise; we are not building a culture of folks pushing their personal compromise; we are not building a culture of folks pushing their personal
agendas at the expense of the overall project. agendas at the expense of the overall project.
We are particularly vigilant against 'trojan horse' additions to the spec - The team should be particularly vigilant against 'trojan horse' additions to the
features which only benefit particular players, or are designed to somehow spec - features which only benefit particular players, or are designed to
cripple or fragment the open protocol and ecosystem in favour of competitive somehow cripple or fragment the open protocol and ecosystem in favour of
advantage. Commercial players are of course free to build proprietary competitive advantage. Commercial players are of course free to build
implementations, or use custom event types, or even custom API extensions (e.g. proprietary implementations, or use custom event types, or even custom API
more efficient network transports) - but implementations must fall back to extensions (e.g. more efficient network transports) - but implementations must
interoperating correctly with the rest of the ecosystem. fall back to interoperating correctly with the rest of the ecosystem.
### Spec Core Team logistics ### Spec Core Team logistics

Loading…
Cancel
Save