I’ve begun to think more about how the restrictions of contributing to Elm are communicated lately. The reason is that I’ve now seen two posts on reddit (on different sub-reddits, here and here ), which cautioned newcomers about those restrictions, and recommended they read about them by reading the …

I believe elm-community.github.io IS the “official” community website. From what I understand, repositories in elm-community are mostly forks of other repositories. The official way to get a repository added is to create a PR over at elm-community/Manifesto . This would mean that we would probably h…

Hm yeah, so the name should be more specific I guess, since what this thread is about, is bringing better documentation in terms of transparency and communication. So communicating this name clearly makes it easier to understand for other people what this repo is about … ‘elm-discussions’ is quite g…

Later on, we can pr-merge this or even multiple workgroup repos (for different purposes) anywhere we want, like into the official community repos.

[image] Lucas_Payr: I believe elm-community.github.io IS the “official” community website. Nowhere close to being official. The site says “unofficial” at the bottom, and I don’t think elm-lang.org even links to it

I’ve created the repos: [image] Orasund/elm-communication-workgroup A workgroup for writing a "Contribute to Elm" page But im not going to write the actual page, as I’m not a native speaker.

My solution has been less to fork and more to try to start from scratch. For me the biggest pain point is no language similar to Elm on the server side. Reading up on Evan’s thoughts there, it might as well compile to assembly so that’s what I’m doing. Target platform elf64. For naming, my core de…

Some thoughts on content for a contributing to Elm site: How to build and test a core package. I realise now, that the bugfix I contributed to elm/virtual-dom was never made into a PR. I’m fairly sure the bugfix is correct because it was quite trivial. But I had no easy way to try it out. Perhaps…

[image] rupert: How to build the compiler? Maybe someone already did this somewhere, never tried myself, so not really looked. That one I figured out already. This is for current Debian Stable (which does use quite old ghc). ; might need others also, but this is what I missed $ sudo apt-get …

[image] malaire: That one I figured out already. This is for current Debian Stable (which does use quite old ghc). Thanks - that was easy enough! I’m also a long time Debian user (since 1994). – Occurs to me, maybe its time Elm had an official Debian package.

It’s even easier on linux. There’s a docker file in the repo which has all the info you need. compiler/Dockerfile at master · elm/compiler · GitHub Worked very well for me.

Communicating about Elm Contributions

Learn

eimfach February 2, 2021, 9:11pm 58

Great to be back!

I also came to a similiar conclusion a while ago and proposed this

Topic		Replies	Views
The governance of elm docs and smaller tools Request Feedback	17	3267	November 19, 2019
How can the Elm community improve? Show and Tell	14	3076	June 7, 2019
Request: Elm 0.19.2: any update to help adoption to prove that Elm is not dead? Request Feedback	76	10903	February 9, 2023
Building and extending trust Request Feedback	33	2797	October 5, 2023
Clients expressing doubt about choosing Elm Request Feedback	97	10709	February 25, 2021

Communicating about Elm Contributions

Related topics