Installfest: Tutorial needed on setting up a computer for coding

[erickt]

@booyaa said he'd be interested in getting something together. @steveklabnik: do you already have any good materials for this?

[steveklabnik]

Some existing materials on this:

• http://docs.railsbridge.org/installfest/
• http://tutorials.jumpstartlab.com/topics/environment/environment.html

[broesamle]

anyone working on this, feel free to get inspiration from / refactor parts of https://github.com/broesamle/RustWorkshop/blob/master/minimals/countinghands.md into a the getting you and your machine ready for coding tutorial.

[brson]

Here's the book's instructions https://doc.rust-lang.org/nightly/book/getting-started.html

[jimmycuadra]

@leahscampoli and I are taking this.

[jimmycuadra]

Does #30 close this, or are there next steps we should take here?

[milibopp]

I think #30 does not entirely close this, as there are still some todos left. Someone could analyse that and make more specific issues out of it.

EDIT: by some todos, I meant Windows-specific instructions.

[broesamle]

this could/should include testing the instructions step by step (ideally on a linux/windows that was not used for development before -- presumably a VM)

[jimmycuadra]

Ah, yes, forgot about Windows. The OS X instructions were done from scratch (and therefore tested) on a Mac that hadn't been used for development before.

[broesamle]

Thats good, maybe you can just open a ticket so that somebody can test, what you could'nt test.

[broesamle]

Regarging windows, I have made a first (finally positive) experience with the following combination:
on Win10:

1. install MSYS2 cf build on windows guide, however, building rust from source failed.
2. a gcc command is needed for miniz-sys (at least it stopped complaining after installing the msys package and adding it to the path
3. use the rust windows binary offered at http://rustlang.org

Newcomers would need step by step instructions for setting up path variable and for finding the right gcc pacman package depending on 32/64 bit windows

[LeonardA-L]

I feel like the user-guide.md should simply be a link to the official getting started book, because that is going to be maintained.

The presentation-outline.md however is what we would want to focus on so that evangelists/speakers can animate workshops with it. It should be following the same workflow as the user guide, so that speakers can ask users to follow the tutorial, and have material to help them along the way. It should contain troubleshooting material for instance.

Regarding the editor configuration stuff, I don't know if it is a good thing to have it in a getting started doc, but I guess the best way to do it would be to have one separate file for each editor (atom, vim, sublime...) describing the process, so that they can be maintained independently, and one index to rule them all.