Add a section about language development #1052

josevalim · 2017-10-22T10:23:32Z

No description provided.

ericmj · 2017-10-22T10:52:54Z

development.markdown

+The language development is also becoming more focused. We believe there is a limited amount of features a language can provide without hindering its learning and without causing fragmentation in the community. Therefore the Elixir team focuses on language features that:
+
+  1. are necessary for developing the language itself
+  2. or bring important concepts/features to the community in a way its effect can only be maximized or leveraged by making it part of the language


Drop initial "or".

ericmj · 2017-10-22T10:53:41Z

development.markdown

+
+# {{ page.title }}
+
+In this section we outline the language past and future developments.


In this section we outline the language's past and future development.

ericmj · 2017-10-22T11:02:24Z

development.markdown

+
+Elixir also relies on a vibrant community to support its growth. The community is behind the meetups, events, learning resources, open source projects, and more. See the sidebar, the [Learning Resources](/learning.html) and [the Hex Package Manager website](https://hex.pm/) for some examples and more information.
+
+The best way to get involved into the language development is by supporting its ecosystem and joining its community.


I think this could be reworded as "The best way to support the language is by getting involved in its community and helping develop the ecosystem", wdyt?

What about "The best way to support the language is by getting involved in its community and contributing to the ecosystem"?

whatyouhide · 2017-10-22T15:42:24Z

development.markdown

+
+In this section we outline the language's past and future development.
+
+Elixir was created by José Valim as a Research and Development effort at [Plataformatec, a consultancy based in Brazil](http://plataformatec.com.br/), back in 2012. Elixir's goal is to be a productive language for writing maintainable and reliable software.


Personal take but I would only make "Plataformatec" a link (looks neater IMO :)!).

whatyouhide · 2017-10-22T15:43:12Z

development.markdown

+
+Elixir was created by José Valim as a Research and Development effort at [Plataformatec, a consultancy based in Brazil](http://plataformatec.com.br/), back in 2012. Elixir's goal is to be a productive language for writing maintainable and reliable software.
+
+Elixir runs on top of the Erlang Virtual Machine, known as Erlang VM and sometimes as BEAM VM, which provides a scalable and fault-tolerant foundation. Elixir was designed to leverage this foundation without performance costs and aims to contribute to the wider ecosystem whenever possible.


Do we need to say what the BEAM is? Can we only say something like "Elixir runs on top of the Erlang Virtual Machine. It was designed to leverage this foundation without performance ...".

whatyouhide · 2017-10-22T15:44:49Z

development.markdown

+
+Elixir runs on top of the Erlang Virtual Machine, known as Erlang VM and sometimes as BEAM VM, which provides a scalable and fault-tolerant foundation. Elixir was designed to leverage this foundation without performance costs and aims to contribute to the wider ecosystem whenever possible.
+
+Elixir source code is under the [Apache 2 License](https://github.com/elixir-lang/elixir/blob/master/LICENSE) and is maintained by the Elixir Core team, composed of 5 members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, James Fish, and José Valim. The source code can be found on [GitHub](https://github.com/elixir-lang/elixir). The Elixir team works towards an even understanding of the Elixir codebase across all members so it never depends on a single person.


Not a native speaker but reading "Elixir source code" makes me thing of source code written in Elixir, while "Elixir's source code" makes me think of the source code of Elixir. Makes sense? 🤔

Since it's prose, I'd go with "composed of five members" instead of "composed of 5 members"

Micro-detail but maybe add the members in order of joining the team?

whatyouhide · 2017-10-22T15:45:37Z

development.markdown

+
+Elixir source code is under the [Apache 2 License](https://github.com/elixir-lang/elixir/blob/master/LICENSE) and is maintained by the Elixir Core team, composed of 5 members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, James Fish, and José Valim. The source code can be found on [GitHub](https://github.com/elixir-lang/elixir). The Elixir team works towards an even understanding of the Elixir codebase across all members so it never depends on a single person.
+
+The language development is open, both in terms of source code and of collaborations. All features and bug fixes planned for the next release can be found [in the issues tracker](https://github.com/elixir-lang/elixir/issues). Features that may cause a larger impact on the language are first proposed to the community in [Elixir mailing list](https://groups.google.com/group/elixir-lang-core) as well as in [the "Elixir News" section in the Elixir Forum](https://elixirforum.com/c/elixir-news).


"are first proposed to the community in Elixir mailing list" -> "are first proposed to the community in the Elixir mailing list"

josevalim · 2017-10-22T18:23:08Z

❤️ 💚 💙 💛 💜

josevalim force-pushed the jv-development branch from db81720 to 5a7de5b Compare October 22, 2017 10:29

Add a section about language development

66857c3

josevalim force-pushed the jv-development branch from 5a7de5b to 66857c3 Compare October 22, 2017 10:29

ericmj reviewed Oct 22, 2017

View reviewed changes

Add dates and mention elixir's release cycle

3aeacef

whatyouhide reviewed Oct 22, 2017

View reviewed changes

ericmj approved these changes Oct 22, 2017

View reviewed changes

Address Andrea's feedback

8991989

josevalim merged commit 68ab2fa into master Oct 22, 2017

josevalim deleted the jv-development branch October 22, 2017 18:23

vladdu pushed a commit to vladdu/elixir-lang.github.com that referenced this pull request Jan 26, 2021

Add a section about language development (elixir-lang#1052)

ce73485

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add a section about language development #1052

Add a section about language development #1052

josevalim commented Oct 22, 2017

ericmj Oct 22, 2017

ericmj Oct 22, 2017

ericmj Oct 22, 2017

josevalim Oct 22, 2017

ericmj Oct 22, 2017

whatyouhide Oct 22, 2017

whatyouhide Oct 22, 2017

whatyouhide Oct 22, 2017

whatyouhide Oct 22, 2017

josevalim commented Oct 22, 2017


		# {{ page.title }}

		In this section we outline the language past and future developments.


		Elixir also relies on a vibrant community to support its growth. The community is behind the meetups, events, learning resources, open source projects, and more. See the sidebar, the [Learning Resources](/learning.html) and [the Hex Package Manager website](https://hex.pm/) for some examples and more information.

		The best way to get involved into the language development is by supporting its ecosystem and joining its community.


		In this section we outline the language's past and future development.

		Elixir was created by José Valim as a Research and Development effort at [Plataformatec, a consultancy based in Brazil](http://plataformatec.com.br/), back in 2012. Elixir's goal is to be a productive language for writing maintainable and reliable software.


		Elixir was created by José Valim as a Research and Development effort at [Plataformatec, a consultancy based in Brazil](http://plataformatec.com.br/), back in 2012. Elixir's goal is to be a productive language for writing maintainable and reliable software.

		Elixir runs on top of the Erlang Virtual Machine, known as Erlang VM and sometimes as BEAM VM, which provides a scalable and fault-tolerant foundation. Elixir was designed to leverage this foundation without performance costs and aims to contribute to the wider ecosystem whenever possible.


		Elixir runs on top of the Erlang Virtual Machine, known as Erlang VM and sometimes as BEAM VM, which provides a scalable and fault-tolerant foundation. Elixir was designed to leverage this foundation without performance costs and aims to contribute to the wider ecosystem whenever possible.

		Elixir source code is under the [Apache 2 License](https://github.com/elixir-lang/elixir/blob/master/LICENSE) and is maintained by the Elixir Core team, composed of 5 members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, James Fish, and José Valim. The source code can be found on [GitHub](https://github.com/elixir-lang/elixir). The Elixir team works towards an even understanding of the Elixir codebase across all members so it never depends on a single person.


		Elixir source code is under the [Apache 2 License](https://github.com/elixir-lang/elixir/blob/master/LICENSE) and is maintained by the Elixir Core team, composed of 5 members: Aleksei Magusev, Andrea Leopardi, Eric Meadows-Jönsson, James Fish, and José Valim. The source code can be found on [GitHub](https://github.com/elixir-lang/elixir). The Elixir team works towards an even understanding of the Elixir codebase across all members so it never depends on a single person.

		The language development is open, both in terms of source code and of collaborations. All features and bug fixes planned for the next release can be found [in the issues tracker](https://github.com/elixir-lang/elixir/issues). Features that may cause a larger impact on the language are first proposed to the community in [Elixir mailing list](https://groups.google.com/group/elixir-lang-core) as well as in [the "Elixir News" section in the Elixir Forum](https://elixirforum.com/c/elixir-news).

Add a section about language development #1052

Add a section about language development #1052

Conversation

josevalim commented Oct 22, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

josevalim commented Oct 22, 2017